"facility","severity_id","mnemonic","vendor_message_text","vendor_explanation","vendor_recommended_action"
"AM","2","API_INIT","Failed to initialize %s API","An unrecoverable software error has occurred during the AM initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"AM","2","BAD_TIMER","%s","An unrecoverable software error has occurred during the AM initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"AM","2","CLI_INIT","Failed to initialize CLI","An unrecoverable software error has occurred during the AM initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"AM","2","INIT_FAIL","Initialization failure","An unrecoverable software error has occurred during the AM initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"AM","2","MQ_OPEN","Failed to open message queue %s: %s","An unrecoverable software error has occurred during the AM initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"AM","2","MTS_BIND","Failed to do mts_bind for %s: %s","An unrecoverable software error has occurred during the AM initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"AM","2","MTS_OPC_SET","Failed to register with opcode %d: %s","An unrecoverable software error has occurred during the AM initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"AM","2","MTS_RECV","MTS queue receive failed on %s queue: %s","An unexpected fatal error has occurred.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"AM","2","MTS_SADDR_GET","Failed to get source of mts queue %s: %s","An unrecoverable software error has occurred during the AM initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"AM","2","NO_WORKBIT","Failed to register %s too many notify clients","An unexpected fatal error has occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"AM","2","REQD_COMP_DOWN","Required component \%s\ has gone down.","An unexpected fatal error has occurred.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"AM","2","REQD_COMP_FAIL","Required component \%s\ has failed to initialize.","An unrecoverable software error has occurred during the AM initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"AM","2","SDB_CREAT","Failed to create shared database","An unrecoverable software error has occurred during the AM initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"AM","2","SDB_DESTROY","Failed to destroy shared database","An unrecoverable software error has occurred during the AM initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"AM","2","SDB_OPEN","Failed to open shared database","An unrecoverable software error has occurred during the AM initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"AM","2","SET_SCHED","Failed to set policy or priority","An unrecoverable software error has occurred during the AM initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"AM","2","SHM_CREAT","Failed to create shared memory: %s","An unrecoverable software error has occurred during the AM initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"AM","2","SHM_LOCK_CREAT","Failed to create shared memory lock: %s","An unrecoverable software error has occurred during the AM initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"AM","2","SVR_REG","Failed to register as a client of %s for VRF %s","An unrecoverable software error has occurred during the AM initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"AM","2","SYSMGR_NAME","Failed to get name from sysmgr during %s","An unrecoverable software error has occurred during the AM initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"AM","2","SYSMGR_NOTIFY","Bad notification from sysmgr for %s","An unrecoverable software error has occurred during the AM initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"AM","2","SYSMGR_QUERY","Failed to query sysmgr for %s","An unrecoverable software error has occurred during the AM initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"AM","2","SYSMGR_UUID","Failed to get uuid from sysmgr during %s","An unrecoverable software error has occurred during the AM initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"AM","2","THR_CREAT","Failed to create thread %s: error %d","An unrecoverable software error has occurred during the AM initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"AM","2","THREAD_FAIL","Failed to start %s thread","An unrecoverable software error has occurred during the AM initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"AM","2","URIB_PIB","Unable to get pib for %s VRF from URIB","An unrecoverable software error has occurred during the AM initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"AM","3","BAD_PARAMS","Called %s with address family %d, iod %d, l3address %s","An unexpected but recoverable error has occurred.","No action is required."
"AM","3","DEL_PROT_ADJ","Unable to delete protocol adjacency for %s, uuid %ld","An unexpected but recoverable error has occurred.","No action is required."
"AM","3","IF_INDEX","Invalid interface index received from %d","An unexpected but recoverable error has occurred.","No action is required."
"AM","3","IP_GLEAN_EXCESS_TRAFFIC","Excess traffic (%llu packets / %llu octets) were dropped in %s seconds for ungleaned prefix %s/32 on interface %s in vrf %s","This message indicates an informational log about a system event.","No action is required."
"AM","3","IPV6_GLEAN_EXCESS_TRAFFIC","Excess traffic (%llu packets / %llu octets) were dropped in %s seconds for ungleaned prefix %s/128 on interface %s in vrf %s","This message indicates an informational log about a system event.","No action is required."
"AM","3","MAC_REG_FAILED","Mac registration with L2FM failed for mac %s, iod %s, phy iod: %s","MAC registration with L2FM failed.","No action is required."
"AM","3","MAX_RETRIES","Notification retry limit exceeded for %s","Client is not replying to our notifications.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"AM","3","MQ_RECV","Message queue receive failed on %s queue: %s","An unexpected but recoverable error has occurred.","No action is required."
"AM","3","MQ_SEND","Failed to send %s to %s queue: %s","An unexpected but recoverable error has occurred.","No action is required."
"AM","3","MSG_TO_TLV","Notification message to TLV failed","An unexpected but recoverable error has occurred.","No action is required."
"AM","3","MTS_DROP","MTS drop failed on %s queue: %s","An unexpected but recoverable error has occurred.","No action is required."
"AM","3","MTS_SEND","Failed to send %s to %s queue: %s","An unexpected but recoverable error has occurred.","No action is required."
"AM","3","NO_AF","%s: Unable to get address family block for index %d","An unexpected but recoverable error has occurred.","No action is required."
"AM","3","NO_MEM","Malloc failed for %s %s","The system may be low on memory.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"AM","3","NO_PIB","Unable to get pib for client pid %d while processing %s","An unexpected but recoverable error has occurred.","No action is required."
"AM","3","NO_SMEM","Smalloc failed for %s %s","AM's shared memory quota may be used up, due to a large number of adjacencies or a memory leak.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"AM","3","PT_ADD","Pt_add failed for %s %s","An unexpected but recoverable error has occurred.","No action is required."
"AM","3","QUEUE","%s failed for %s","An unexpected but recoverable error has occurred.","No action is required."
"AM","3","READ_LOCK_HOLD","%s:%s():%d: Assert, read-lock not acquired","An unexpected but recoverable error has occurred.","No action is required."
"AM","3","RIB_RTE_CHG","Failed to send AM route changes to %s","An unexpected but recoverable error has occurred.","No action is required."
"AM","3","SHM_OPEN","Shared memory does not exist: %s","This message indicates an informational log about a system event.","No action is required."
"AM","3","THR_MUTEX_LOCK","Failed to thread mutex lock","Failed function pthread_mutex_lock.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"AM","3","THR_MUTEX_UNLOCK","Failed to thread mutex lock","Failed function pthread_mutex_unlock.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"AM","3","TLV_TO_STRUCT","Notification TLV to struct failed","An unexpected but recoverable error has occurred.","No action is required."
"AM","3","URIB_CNTXT","Failed to get Table_ID for %s on %s from %s (%ld)","An unrecoverable software error has occurred during the AM initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"AM","5","INVALID_NOTIFY","Received invalid notification message","An unexpected but recoverable error has occurred.","No action is required."
"AM","5","MQ_MAJOR","Received unknown major message type (%d) from %s","An unexpected but recoverable error has occurred.","No action is required."
"AM","5","MQ_MINOR","Received unknown minor message type (%d) from %s","An unexpected but recoverable error has occurred.","No action is required."
"AM","5","MQ_UNEXP","Received unexpected message (%d/%d) on %s queue","An unexpected but recoverable error has occurred.","No action is required."
"AM","5","MSG_UNK","Received unknown % type: %lu","An unexpected but recoverable error has occurred.","No action is required."
"AM","5","MTS_OPC_UNK","Received unknown MTS opcode %lu","An unexpected but recoverable error has occurred.","No action is required."
"AM","5","REG_DELAY","AM register %s delay: %d seconds","An unexpected but recoverable error has occurred.","No action is required."
"AM","6","FAILED_STATS","Failed to retrieve stats from FTM","This message indicates an informational log about a system event.","No action is required."
"AM","6","SYSMAN_CLEANUP","Terminated by SYSMAN cleanup signal ;",": Informational log about a system event. Explanation    The system has detected an error.","No action is required."
"AMT","2","SHM_LOCK_CREAT","Failed to create shared memory lock: %s","The system has failed to initialize.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"AMT","3","AMT_INIT","AMT init failed: %s","AMT process initialization failed.","Dump core, and then restart component."
"AMT","3","API_INIT","Couldn't initialize %s API","AMT failed to open API to interact with the component.","No action is required."
"AMT","3","BIND","bind() on %s failed: %s","AMT failed to bind UDP socket.","Dump core, and then restart component."
"AMT","3","COMP_DEREG","Unable to de-register with %s","AMT failed to de-register with a server component.","No action is required."
"AMT","3","COMP_REG","Unable to register with %s","AMT failed to register with a server component.","Dump core, and then restart component."
"AMT","3","DISC_NOT_ANYCAST","Relay Discovery packet from %s is addressed to %s, not an anycast address","An AMT Gateway sent Relay Discovery not using the Relay Anycast address.","Configure the network or router to decrease the number of routes."
"AMT","3","IP_TUNNEL_LIMIT","Reach IP tunnel limit of %d","AMT process failed to create tunnel because the policy limit has been reached.","Configure the network or router to decrease the number of routes."
"AMT","3","IPV6_TUNNEL_LIMIT","Reach IPv6 tunnel limit of %d","AMT process failed to create tunnel because the policy limit has been reached.","Configure the network or router to decrease the number of routes."
"AMT","3","LIB_API_INIT","Couldn't initialize %s API","Failed to open AMT API to interact with the component.","No action is required."
"AMT","3","LIB_SM_CLOSE","Couldn't close shm segment %s","Process failed to remove shared memory resource.","No action is required."
"AMT","3","LIB_SM_OPEN","Couldn't open shm segment %s","Process failed to access AMT's shared memory.","Dump core, and then restart component."
"AMT","3","MALLOC","Private mem malloc (%lu) failed in %s","AMT process is out of free private memory.","Configure the network or router to decrease the number of routes."
"AMT","3","MRIB_ADD_ROUTE","MRIB add route failed in %s","AMT failed to add route in MRIB.","No action is required."
"AMT","3","MRIB_DEL_ROUTE","MRIB delete route failed in %s","AMT failed to delete route in MRIB.","No action is required."
"AMT","3","MTS_DROP","Error returned from mts_drop(), errno: %s","AMT called an MTS API which returned an error.","Dump core, and then restart component."
"AMT","3","MTS_RECV","Error returned from mts_recv(), errno: %s","AMT called an MTS API which returned an error.","Dump core, and then restart component."
"AMT","3","NO_AMT_PAYLOAD","No AMT payload after stripping IP/IPv6 and UDP headers from %s, length: %d","AMT process received packet which is too short. The other side of the AMT tunnel has a protocol error.","Configure the network or router to decrease the number of routes."
"AMT","3","NO_M_COPYBACK","m_copyack() failed in amt_receive_multicast_data()","AMT process failed to copy AMT multicast data into an mbuf for IP to replicate the packet.","No action is required."
"AMT","3","NO_M_GET","amt_receive_multicast_data() could allocate mbuf data structure","AMT process failed to allocate an mbuf data structure to forward AMT encapsulated data in an AMT Gateway.","No action is required."
"AMT","3","NO_SET_PRIORITY","Failed to set policy or priority","AMT process could not set itself process priority, exiting.","No action is required."
"AMT","3","PKT_BAD_NONCE","Nonce from Relay Advertisement packet from %s does not match Relay Discovery packet nonce, received 0x%08x, expected 0x%08x","There is a possible AMT spoof attack since the Advertise and Disocvery nonces do not match.","Configure the network or router to decrease the number of routes."
"AMT","3","PKT_TOO_SHORT","Packet too short from %s","AMT process received packet which is too short. The other side of the AMT tunnel has a protocol error.","Configure the network or router to decrease the number of routes."
"AMT","3","PT_ADD","Couldn't add %s to Patricia Trie","AMT failed to update the tunnel Patricia Trie.","No action is required."
"AMT","3","PT_DEL","Couldn't delete %s from local PT","AMT failed to delete the local route-table entry.","No action is required."
"AMT","3","PTHREAD_CREATE","Couldn't create thread %s","AMT process failed to create a task thread.","Dump core, and then restart component."
"AMT","3","RESTART_REASON","AMT process has restarted, restart reason: %s\n","AMT is restoring the routes it had added in previous instance.","No action is required."
"AMT","3","RLIMIT","Couldn't set AMT data segment size to %lu","AMT process could not set a memory resource limit, exiting.","No action is required."
"AMT","3","SETSOCKOPT","setsockopt() on %s failed: %s","AMT failed in UDP socket operation.","Dump core, and then restart component."
"AMT","3","SLAB_CREATE","Slab alloc of type %s failed","AMT process failed to allocate Slab memory.","Configure the network or router to decrease the number of routes."
"AMT","3","SM_CREATE","Couldn't create shm segment %s","AMT process failed to initialize shared memory resource.","Dump core, and then restart component."
"AMT","3","SMALLOC","Shared mem malloc (%lu) failed in %s","AMT process is out of free shared memory.","Configure the network or router to decrease the number of routes."
"AMT","3","SOCKET","socket() for %s failed: %s","AMT failed to obtain UDP socket.","Dump core, and then restart component."
"AMT","3","TIMER_SET_INIT","Couldn't init %s active timer set","AMT failed to initialize timer resource.","Dump core, and then restart component."
"AMT","3","TUNNEL_FAILED","Could not allocate shared-memory for amt_tunneltype data structure","AMT process failed to create data structure to establish tunnel.","Configure the network or router to decrease the number of routes."
"AMT","3","UDP_SENDTO","udp_sendto() failed to %s in %s, error: %s","AMT failed to send over UDP socket.","No action is required."
"AMT","3","UNKNOWN_MTYPE","Unknown mtype: %d/%d in %s","AMT process received unknown Interprocess message, dropped.","No action is required."
"AMT","6","RESTART_SHUTDOWN","AMT shutting self down via restart command","AMT process is shutting itself down due to the restart command.","No action is required."
"AMT","6","SHUTDOWN","Shutting down AMT process","PIM received a shutdown request.","No action is required."
"AMT","6","SHUTDOWN_SELF","AMT shutting self down","AMT process is shutting itself down.","No action is required."
"AMT","6","UNKNOWN_OPC","Received unknown mts opcode %d","AMT process received unknown Interprocess message, dropped.","No action is required."
"ARP","2","AM_PIB","Failed to acquire AM handle %s","An unrecoverable software error has occurred during ARP initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"ARP","2","AM_REG","Failed to register as a client of AM %s","An unrecoverable software error has occurred during ARP initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"ARP","2","API_INIT","Failed to initialize %s API","An unrecoverable software error has occurred during ARP initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"ARP","2","API_INITIALIZE","Failed to initialize %s API with rc=0x%x, %s","An unrecoverable software error has occurred during ARP initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"ARP","2","CLI_INIT","Failed to initialize CLI","An unrecoverable software error has occurred during ARP initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"ARP","2","DUP_SRC_IP","Source address of packet received from %s on %s(%s) is duplicate of local, %s","There may be another router on this network that is configured with the same IP address.","Check all routers on the interface for a misconfiguration."
"ARP","2","DUP_SRCIP","Source address of packet received from %s on %s is duplicate of local, %s","There may be another router on this network that is configured with the same IP address.","Check all routers on the interface for a misconfiguration."
"ARP","2","INIT_FAIL","Initialization failure","An unrecoverable software error has occurred during ARP initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"ARP","2","MQ_OPEN","Failed to open message queue %s: %s","An unrecoverable software error has occurred during ARP initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"ARP","2","MQ_RECV","Message queue receive failed on %s queue: %s","An unexpected fatal error has occurred.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"ARP","2","MTS_BIND","Failed to do mts_bind for %s: %s","An unrecoverable software error has occurred during ARP initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"ARP","2","MTS_OPC_SET","Failed to register with opcode %d: %s","An unrecoverable software error has occurred during ARP initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"ARP","2","MTS_RECV","MTS queue receive failed on %s queue: %s","An unexpected fatal error has occurred.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"ARP","2","SET_SCHED","Failed to set policy or priority","An unrecoverable software error has occurred during ARP initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"ARP","2","SHM_ATTACH","Failed to attach %s shared memory","An unrecoverable software error has occurred during ARP initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"ARP","2","SVR_REG","Failed to register as a client of %s","An unrecoverable software error has occurred during ARP initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"ARP","2","SYSMGR_NOTIFY","Bad notification from sysmgr for %s","An unrecoverable software error has occurred during ARP initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"ARP","2","SYSMGR_QUERY","Failed to query sysmgr for %s","An unrecoverable software error has occurred during ARP initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"ARP","2","SYSMGR_UUID","Failed to get uuid from sysmgr during %s","An unrecoverable software error has occurred during ARP initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"ARP","2","THR_CREAT","Failed to create thread %s: error %d","An unrecoverable software error has occurred during ARP initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"ARP","2","THREAD_FAIL","Failed to start %s thread","An unrecoverable software error has occurred during ARP initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"ARP","2","TIMER_SET","Failed to initialize new timer set","An unrecoverable software error has occurred during ARP initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"ARP","2","TIMERS_INIT","Failed to initialize timers","An unrecoverable software error has occurred during ARP initialization.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"ARP","3","ADJ_ADD","Failed to add adjacency for received packet from %s on %s","Due to this failure, packet forwarding to this address will be affected until the next successful retry.","No action is required."
"ARP","3","ADJ_UPD","Failed to update adjacency for received packet from %s on %s","Due to this failure, packet forwarding will continue to use the existing ARP adjacency entry values.","No action is required."
"ARP","3","API_MQ_INVAL","ARP API Error: Invalid ARP message queue in %s","An unexpected but recoverable error has occurred.","No action is required."
"ARP","3","API_MQ_SEND","ARP API Error: Failed to send %s to %s queue: %s","An unexpected but recoverable error has occurred.","No action is required."
"ARP","3","API_MTS_INVAL","ARP API Error: Invalid ARP MTS queue in %s","An unexpected but recoverable error has occurred.","No action is required."
"ARP","3","API_MTS_SEND","ARP API Error: Failed to send %s to %s queue: %s","An unexpected but recoverable error has occurred.","No action is required."
"ARP","3","DAI_FETCH_ERR","DAI lookup failed, callback function returned 0x%x (%s) for %s %s","DAI lookup failed.","No action is required."
"ARP","3","DUP_VADDR_SRC_IP","Source address of packet received from %s on %s(%s) is duplicate of local virtual ip, %s","There may be another router on this network that is configured with the same IP address.","Check all routers on the interface for a misconfiguration."
"ARP","3","DUP_VADDR_SRCIP","Source address of packet received from %s on %s is duplicate of local virtual ip, %s","There may be another router on this network that is configured with the same IP address.","Check all routers on the interface for a misconfiguration."
"ARP","3","DUP_VIRT_SRC_IP","Source address of packet received from %s on %s(%s) is duplicate of local virtual ip, %s","There may be another router on this network that is configured with the same IP address.","Check all routers on the interface for a misconfiguration."
"ARP","3","DUP_VIRT_SRCIP","Source address of packet received from %s on %s is duplicate of local virtual ip, %s","There may be another router on this network that is configured with the same IP address.","Check all routers on the interface for a misconfiguration."
"ARP","3","GRAT_ETH","Sending gratuitous arp for %s on invalid interface %s, not ethernet","An unexpected but recoverable error has occurred.","No action is required."
"ARP","3","GRAT_IOD","Sending gratuitous ARP for %s on an invalid interface %u","An unexpected but recoverable error has occurred.","No action is required."
"ARP","3","GRAT_IP","Sending gratuitous ARP request for %s IP address %s on %s","An unexpected but recoverable error has occurred.","No action is required."
"ARP","3","GRAT_NON_AM","Sending gratuitous arp for %s on invalid interface %s","An unexpected but recoverable error has occurred.","No action is required."
"ARP","3","GRAT_P2P","Sending gratuitous arp for %s on invalid interface %s, point-to-point","An unexpected but recoverable error has occurred.","No action is required."
"ARP","3","HDR_ERR","Failed to get ARP header, expected %d, got %d bytes","An unexpected but recoverable error has occurred.","No action is required."
"ARP","3","HDR_L2LEN_ERR","Received packet with incorrect layer 2 address length (%d bytes)","An unexpected but recoverable error has occurred.","No action is required."
"ARP","3","HDR_L3LEN_ERR","Received packet with incorrect layer 3 address length (%d bytes)","An unexpected but recoverable error has occurred.","No action is required."
"ARP","3","IF_INDEX","Invalid interface index received from %d","An unexpected but recoverable error has occurred.","No action is required."
"ARP","3","IM_EXT","Couldn't set IM-extension for interface %s","ARP process failed to set IM extension.","No action is required."
"ARP","3","INVAL_HDR","Found incorrect hardware/protocol type in ARP header: %hu/%hu","An unexpected but recoverable error has occurred.","No action is required."
"ARP","3","INVAL_STATE","Unrecognized ARP entry state in timer callback: %lu","An unexpected but recoverable error has occurred.","No action is required."
"ARP","3","MAC_ERR","Failed to get MAC address on %s for %s","An unexpected but recoverable error has occurred.","No action is required."
"ARP","3","MBUF_ERR","Failed to get the remainder of packet, expected %d, got %d bytes","An unexpected but recoverable error has occurred.","No action is required."
"ARP","3","MTS_DROP","MTS drop failed on %s queue: %s","An unexpected but recoverable error has occurred.","No action is required."
"ARP","3","NO_MBUF","Failed to allocate buffer for %s","The system may have run out of packet memory buffers.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"ARP","3","NO_MEM","Malloc failed for %s %s","The system may be low on memory.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"ARP","3","PKT_ENCAP","Failed to encapsulate packet","An unexpected but recoverable error has occurred.","No action is required."
"ARP","3","PKT_OUT","Failed to send packet to PM","PM's message queue may be temporarily full.","No action is required."
"ARP","3","REQ_ADD","Failed to add adjacency while sending request for %s on %s, request from pid: %d","An unexpected but recoverable error has occurred.","No action is required."
"ARP","3","REQ_ETH","Sending ARP request for %s on invalid interface %s, not ethernet, request from pid: %d","An unexpected but recoverable error has occurred.","No action is required."
"ARP","3","REQ_IOD","Sending ARP request for %s on an invalid interface %u, request from pid: %d","An unexpected but recoverable error has occurred.","No action is required."
"ARP","3","REQ_IP","Sending ARP request for %s IP address %s on %s, request from pid: %d","An unexpected but recoverable error has occurred.","No action is required."
"ARP","3","REQ_NON_AM","Sending ARP request for %s on invalid interface %s request from pid: %d","An unexpected but recoverable error has occurred.","No action is required."
"ARP","3","REQ_P2P","Sending ARP request for %s on invalid interface %s, point-to-point, request from pid: %d","An unexpected but recoverable error has occurred.","No action is required."
"ARP","3","TIMER_RSTART","Failed to restart timer 0x%p for %s on %s","An unexpected but recoverable error has occurred.","No action is required."
"ARP","3","VRRP_ETH","Adding vrrp arp for %s: invalid interface %s, not ethernet","An unexpected but recoverable error has occurred.","No action is required."
"ARP","3","VRRP_IOD","Adding vrrp arp for %s: invalid interface %u","An unexpected but recoverable error has occurred.","No action is required."
"ARP","3","VRRP_NON_AM","Sending vrrp arp for %s on invalid interface %s","An unexpected but recoverable error has occurred.","No action is required."
"ARP","3","VRRP_P2P","Sending vrrp arp for %s on invalid interface %s, point-to-point","An unexpected but recoverable error has occurred.","No action is required."
"ARP","3","VRRPQ_ADD","Failed to add VRRP queue entry for %s, %s on %s","An unexpected but recoverable error has occurred.","No action is required."
"ARP","3","VRRPQ_IP","Trying to add invalid IP address %s on %s to vrrp queue","An unexpected but recoverable error has occurred.","No action is required."
"ARP","4","DIR_BCAST","%s address of packet received from %s on %s matches directed broadcast address, %s","There may be a configured subnet mask-length mismatch among router interfaces connected on this LAN.","Check all routers on the interface for a misconfiguration."
"ARP","4","DUP_IP","ARP entry found with duplicate IP address %s on %s","There may be another router on this network that is configured with the same IP address.","Check all routers on the interface for a misconfiguration."
"ARP","4","INVAL_IP","Received packet with invalid %s IP address (%s) from %s on %s","There may be a connected router sending packets with a bogus IP address.","Check all routers on the interface for a misconfiguration."
"ARP","4","INVAL_MAC","Received packet with invalid %s MAC address (%s) from %s on %s","There may be a connected router sending packets with a bogus MAC address.","Check all routers on the interface for a misconfiguration."
"ARP","4","OWN_SRCMAC","Received packet with a local source MAC address (%s) from %s on %s","There may be a connected router sending packets with local MAC address.","Check all routers on the interface for a misconfiguration."
"ARP","4","SRCIP_ERR","Source address of received packet (%s) does not match subnet on interface %s","There may be a configured subnet mismatch among router interfaces connected on the LAN.","Check all routers on the interface for a misconfiguration."
"ARP","5","MQ_MINOR","Received unknown minor message type (%d) from %s","An unexpected but recoverable error has occurred.","No action is required."
"ARP","5","MQ_UNEXP","Received unexpected message (%d/%d) on %s queue","An unexpected but recoverable error has occurred.","No action is required."
"ARP","5","MSG_UNK","Received unknown % type: %lu","An unexpected but recoverable error has occurred.","No action is required."
"ARP","5","MTS_OPC_UNK","Received unknown MTS opcode %lu","An unexpected but recoverable error has occurred.","No action is required."
"ARP","5","UNK_IP_NOTIF","Unrecognized IP address change notification type %lu","An unexpected but recoverable error has occurred.","No action is required."
"ARP","5","UNK_MSG_MINOR","Unrecognized %s message minor type %d","An unexpected but recoverable error has occurred.","No action is required."
"ARP","5","UNK_SIG","Received unknown signal %d ;",": An unexpected but recoverable error has occurred. Explanation    The system has detected an error.","No action is required."
"ARP","6","SYSMAN_CLEANUP","Terminated by SYSMAN cleanup signal ;",": Informational log about a system event. Explanation    The system has detected an error.","No action is required."
"ATIMERS","3","ERROR","%s","An active timer API has detected an error Parameters: Error ...","No action is required."
"ATIMERS","3","OPER","timer failed to %s, error %s","An active timer API has detected an error Parameters: timer operation, reason ...","No action is required."
"ATIMERS","3","START","starting timer 0x%p: heap not allocated for set id %u","An active timer API has detected an error Parameters: timer, Set ID ...","No action is required."
"ATIMERS","3","STOP","stopping timer 0x%p: heap not allocated for set id %u\n","An active timer API has detected an error Parameters: timer, Set ID ...","No action is required."
"BGP","1","FATAL","Fatal error: %s: %s","An unexpected fatal error has occurred. Parameters: Error Type, Error ...","Use the 'restart' command to restart the feature and clear this problem."
"BGP","1","UNKNOWNFATAL","Unknown fatal error %d: %s","An unexpected fatal error has occurred. Parameters: Error Type, Error ...","Use the 'restart' command to restart the feature and clear this problem."
"BGP","2","AFINIT","Error initializing address family, (%d)","An unrecoverable error has occurred during BGP initialization.","Use the 'restart' command to restart the feature and clear this problem."
"BGP","2","AFINITFUNCS","Error initializing address family function vectors, (%d)","An unrecoverable error has occurred during BGP initialization.","Use the 'restart' command to restart the feature and clear this problem."
"BGP","2","APIINIT","Unable to initialize %s API","An unrecoverable error has occurred during BGP initialization. Parameters: Server Name ...","Use the 'restart' command to restart the feature and clear this problem."
"BGP","2","APIMTSBIND","Unable to bind to MTS SAP for %s, sap %d: %s","BGP client was not able to create a message queue for communication. Parameters: Queue name, MTS SAP, Error ...","Use the 'restart' command to restart the feature and clear this problem."
"BGP","2","ATTACH","Unable to attach to %s","An unrecoverable error has occurred during BGP initialization. Parameters: Server Name ...","Use the 'restart' command to restart the feature and clear this problem."
"BGP","2","IPV6REG","Unable to register with IPv6","An unrecoverable error has occurred during BGP initialization.","Use the 'restart' command to restart the feature and clear this problem."
"BGP","2","MQLOOP_INIT","Message queue loop %s, %s, Error - %s","An unrecoverable error has occurred during BGP initialization. Parameters: MQLoop Type, Failure Type, Error ...","Use the 'restart' command to restart the feature and clear this problem."
"BGP","2","MTSBIND","Unable to bind to MTS SAP for %s, sap %d: %s","BGP was not able to create a message queue for communication. Parameters: Queue name, MTS SAP, Error ...","Use the 'restart' command to restart the feature and clear this problem."
"BGP","2","PEERSHALTED","BGP %s shutdown due to no memory condition (%s)","The system may be low on memory. Parameters: Peer(s), Error ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","2","PTHREAD","procket_pthread_create failed for %s: error %d","An unexpected fatal error has occurred. Parameters: Thread Name, Error ...","Use the 'restart' command to restart the feature and clear this problem."
"BGP","2","SRVREG","Unable to register with %s","An unrecoverable error has occurred during BGP initialization. Parameters: Server Name ...","Use the 'restart' command to restart the feature and clear this problem."
"BGP","2","SYSMGR_CONDVERIF","Sysmgr conditional verify failed","An internal software error occurred.","Use the 'restart' command to restart the feature and clear this problem."
"BGP","2","SYSMGR_QUERY","Failed to query sysmgr for %s","An internal software error occurred.","Use the 'restart' command to restart the feature and clear this problem."
"BGP","2","TSP_INIT","Unable to initialize with TSP","An unrecoverable error has occurred during BGP initialization.","Use the 'restart' command to restart the feature and clear this problem."
"BGP","2","U6RIBREG","Unable to register with U6RIB for [afi/safi:%d/%d]","An unrecoverable error has occurred during BGP initialization.","Use the 'restart' command to restart the feature and clear this problem."
"BGP","2","URIBREG","Unable to register with URIB for [afi/safi:%d/%d]","An unrecoverable error has occurred during BGP initialization.","Use the 'restart' command to restart the feature and clear this problem."
"BGP","3","ACLTESTADD","Failed to add %s peer policy test","An internal software error occurred. Parameters: ACL type ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","AGGADD","[%s] Couldn't add aggregate for %s/%d","BGP was unable to store an aggregate in an internal datastructure. The BGP process may have run out of memory.","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 available memory, restart BGP."
"BGP","3","AGGDEL","[%s] Couldn't delete aggregate for %s/%d","An unexpected but handleable event has occurred. Parameters: Address-family, Prefix/masklength ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","ALLOCFAIL","%s malloc (%ld) failed for: %s","The system may be low on memory. Parameters: Alloc Type, Size, Error ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","API_UNEXP_RESP","Received unexpected message from SAP %d, opcode %d, address %s, ignore it","An unexpected but handleable event has occurred. Parameters: MTS SAP, MTS Opcode, IP Address ...","No action is required."
"BGP","3","APIASSERT","%s:%d: Assertion `%s' failed.","An internal software error occurred. Parameters: File Name, Line Number, Assert Type ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","APIMTSDROP","MTS drop failed on %s queue: %s","An unexpected but handleable event has occurred. Parameters: Queue name, Error ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","APIMTSRECV","MTS receive failed on %s queue: %s","An unexpected but handleable event has occurred. Parameters: Queue name, Error ...","No action is required."
"BGP","3","APIMTSSEND","MTS send() error to SAP %d, opcode %d: %s","An unexpected but handleable event has occurred. Parameters: MTS SAP, MTS Opcode, Error ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","APPLY_BESTPATH_CFG","Failed to apply bestpath configuration: %s","An unexpected but handleable event has occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","ASLEN","AS-PATH prepend length exceeds internal limit","The system has exceeded an internal limit when prepending an AS path.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","ASPREPEND","Expected AS sequence or entry sequence, got %d/%d","The system has detected an error when prepending to an AS path. Parameters: Segment Type, Segment Length ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","ASSERT","%s:%d: Assertion `%s' failed.","An internal software error occurred. Parameters: File Name, Line Number, Assert Type ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","ATTRAVL_OP","Failed attribute external database operation: %s, id %lu","BGP was unable to perform an attribute external database operation Parameters: Operation, Attr ID ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","ATTRID_OP","Failed to %s attribute ID","BGP was unable to allocate or free an index for a BGP PATH attribute block Parameters: Allocate or free ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","BADNEXTHOP","[%s] Peer %s advertised non-mapped nexthop %s in MP reach attr [afi/safi:%d/%d], dropping NLRI","The router received a next-hop that was inconsistent with the address-family in the update message. Parameters: Address-family, Peer, Nexthop address, AFI, SAFI ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","BADPEERAS","VRF %s, Peer %s - bad remote-as, expecting %s received %s.","An unexpected but handleable event has occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","BFD_SEND_AUTO_EXPIRY","Unable to start BFD staling, error %s(0x%08x)","An unexpected but handleable event has occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","BFD_SEND_EXPIRE_NOW","Unable to expire staled BFD sessions, error %s(0x%08x)","An unexpected but handleable event has occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","BFD_SES_ADD","Unable to add BFD session for peer %s, error %s","An unexpected but handleable event has occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","BFD_SES_CREATE","Unable to create BFD session Id for peer %s, error %s","An unexpected but handleable event has occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","BFD_SES_REMOVE","Unable to remove BFD session for peer %s, error %s","An unexpected but handleable event has occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","BFD_SES_REMOVE_ALL","Unable to cleanup the BFD sessions during deconfiguration, error %s(0x%08x)","An unexpected but handleable event has occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","BRIB_ADD_INT","Internal error in adding to BRIB: %s","An internal error was encountered in adding a path to the BRIB. The BGP process may have run out of memory. Parameters: Error ...","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 available memory, restart BGP."
"BGP","3","BRIB_RDADD","[%s] Couldn't add rdinfo %s to BRIB","BGP was unable to add a prefix to the BGP RIB. The BGP process may have run out of memory. Parameters: Address-family, RDinformation...","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 available memory, restart BGP."
"BGP","3","BRIB_RDCLASH","VRF %s, %s: RD clash found during %s","BGP was unable to allocate RD for the BGP RIB. The BGP process may have run out of memory. Parameters: VRF Name, Address-family, Event ...","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 available memory, restart BGP."
"BGP","3","BRIB_RDDEL","[%s] Couldn't delete rdinfo %s from BRIB","BGP was unable to remove from BGP RIB. The BGP process may have run out of memory. Parameters: Address-family, RDinformation...","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 available memory, restart BGP."
"BGP","3","BRIBADD","[%s] Couldn't add dest to BRIB for %s","BGP was unable to add a prefix to the BGP RIB. The BGP process may have run out of memory. Parameters: Address-family, Prefix/masklength ...","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 available memory, restart BGP."
"BGP","3","BRIBDEL","[%s] Couldn't delete dest from BRIB for %s","An unexpected but handleable event has occurred. Parameters: Address-family, Prefix/masklength ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","CLISET","Unable to set %s inheritance for %s","An internal software error occurred. Parameters: Template type, Peer address ...","Use the 'restart' command to restart the feature and clear this problem."
"BGP","3","COMADD","Error occurred in community addition, no action taken","An internal error was encountered in adding a community.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","COMLEN","Community sets exceeded maximum allowed limit","An internal limit was hit in adding a community.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","CONDSRV_CLEANUP","Conditional Service cleanup request failed, %s","Sysmgr rejected BGP's request to shut down.","No action is required."
"BGP","3","CONFCHECK","confcheck API %s() failed with error: %s(0x%08x).\n","confcheck API has failed.","No action is required."
"BGP","3","DAMPCFG","Both policy and global dampconf exist","An internal software error occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","EBGPTTL","Unable to set EBGP TTL for peer %s, fd %d","An unexpected but handleable event has occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","EVENT_WAIT","Error while waiting for %s event, error - %s\n","An unexpected but handleable event has occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","EXTCOMADD","Error occurred in extended community addition, no action taken","An internal error was encountered in adding an extended community.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","FEATURE_STATUS","FM status for feature %s failed with error: %s(0x%08x).\n","FM get feature status failed.","No action is required."
"BGP","3","FINDAGGR","[%s] Did not find aggregate path for entry %s/%d","BGP was unable to find an internal datastructure for originating a configured aggregate.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","ILLARGS","%s called with illegal arguments","An internal software error occurred. Parameters: Function ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","INTERNAL","Internal error %d: %s","An internal software error occurred. Parameters: Error Type, Error ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","INVHDR","Peer %s sent unexpected header pattern","The marker pattern in the message header was invalid.","Check that the peer router is configured correctly. Clear the peer if necessary after any change."
"BGP","3","IPTOS","Unable to set IP TOS bits for %s, fd %d","An unexpected but handleable event has occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","LIST","%s","An internal software error occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","LISTEN_SOCK","Failed to listen on %s BGP TCP port","BGP_EXPL_SOCK_ERROR Parameters: Address-family ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","LOWMEM","Low on heap memory","The system may be low on memory.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","MD5PASS","Cannot set MD5 password %s for peer %s","An internal software error occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","MQLOOP_SHUTDOWN","Couldn't shut down %s message queue loop","An unexpected but handleable event has occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","MTSDROP","MTS drop failed on %s queue: %s","An unexpected but handleable event has occurred. Parameters: Queue name, Error ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","MTSRECV","MTS receive failed on %s queue: %s","An unexpected but handleable event has occurred. Parameters: Queue name, Error ...","No action is required."
"BGP","3","MTSSEND","MTS send() error to SAP %d, opcode %d: %s","An unexpected but handleable event has occurred. Parameters: MTS SAP, MTS Opcode, Error ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","NBRERR","%s Peer error: %s","An internal software error occurred. Parameters: Peer address, Error ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","NEGWRITE","Negative nr of %d bytes left to write to peer %s","An internal software error occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","NETWKRNHSETUP","Couldn't setup rnh notifications for network %s, error: %s","Could not setup RNH for network prefix Parameters: Network prefix, Error ...","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 available memory, restart BGP."
"BGP","3","NEXTHOPADD","[%s] Couldn't add next-hop to RNHDB for %s/%d, error %d","The router was unable to store a BGP next hop in an internal database, because it ran out of memory. Parameters: Address-family, Prefix/masklength, Error ...","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 available memory, restart BGP."
"BGP","3","NEXTHOPDEL","[%s] Couldn't delete next-hop from RNHDB for %s/%d, error %d","An unexpected but handleable event has occurred. Parameters: Address-family, Prefix/masklength, Error ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","NOBUF","[%s] Unable to get buffer for %s msg to peer %s","An internal software error occurred. Parameters: Address-family, Msg Type, Peer address ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","NOMEMORY","Could not allocate %s","The system may be low on memory. Parameters: Data Type ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","NONBESTPATH","[%s] Non bestpath in attr. path chain for %s/%d","An internal software error occurred. Parameters: Address-family, Prefix/masklength ...","Use the 'restart' command to restart the feature and clear this problem."
"BGP","3","PATH_DEL","Failed to destroy path (%s), error %d","The BGP process may have run out of memory. Parameters: Path Type, Error ...","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 available memory, restart BGP."
"BGP","3","PATH_STALE","[%s] %s path being %s, for %s from peer %s, should not be stale","An internal software error occurred. Parameters: Address-family, Path State, Operation, Prefix/masklength, Peer address ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","PEER","Peer %s, failed %s","An internal software error occurred. Parameters: Peer address, Operation ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","PFX_NOMEM","Could not allocate %s for %s/%d","The system may be low on memory. Parameters: Data Type, Prefix/masklength ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","PLCYOUT","Cannot add reference to policy out info for route-map %s","Use the 'restart' command to restart the feature and clear this problem.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","PLCYRNHATTACH","Couldn't attach to policy RNH info for policy %s, error: %s","An internal error occurred in using a policy. BGP_EXPL_NO_MEM_MAYBE.","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 available memory, restart BGP."
"BGP","3","PLCYRNHDETACH","Couldn't detach from policy RNH info for policy %s, error: %s","An internal software error occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","PLCYRNHSETUP","Couldn't setup rnh notifications for policy %s, error: %s","An internal error occurred in using a policy. BGP_EXPL_NO_MEM_MAYBE.","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 available memory, restart BGP."
"BGP","3","RDINFO","VRF %s, %s, table %s: rdinfo %s failed","BGP was unable to initialize an internal datastructure. The BGP process may have run out of memory. Parameters: VRF name, Address-family, Table name, Operation ...","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 available memory, restart BGP."
"BGP","3","RESTARTINIT","Unable to determine restart status and initialize","An unrecoverable error has occurred during BGP initialization.","Use the 'restart' command to restart the feature and clear this problem."
"BGP","3","RESTARTTYPE","Error in learning restart type","An internal software error occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","RNHCB","RNH %s error: %s","An internal software error occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","RPM_L3VPN_EXTCOMM","L3vpn extcommunity failure during %s","An unexpected but handleable event has occurred. Parameters: Type of operation ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","RPMBIND","RPM policy bind failed for %s %s","An unexpected but handleable event has occurred. Parameters: Policy type, Policy name ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","RPMHANDLE","RPM notification handle does not match existing handle for policy %s","An unexpected but handleable event has occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","RT_DB_ADD","Couldn't add route target %s into the database","The router could not add route-target in its internal database Parameters: Route-target ...","ACTION_BGP_REPORT_CS."
"BGP","3","SENDBUF","Error manipulating sendbuf: %s","An internal software error occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","SNMP_API_DATA","Message data is NULL","An SNMP message does not have enough memory to store data.","No action is required."
"BGP","3","SOCK_ACCEPT","Socket (%d/%d) accept: %s\n","BGP_EXPL_SOCK_ERROR Parameters: Socket fds, Error ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","SOCK_ERR","Socket (%d/%d): %s\n","BGP_EXPL_SOCK_ERROR Parameters: Socket fds, Error ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","SOCK_FDPOP","Unexpected error during socket fd population %s(%d)","An unexpected but handleable event has occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","SOCK_RECV","Unexpected error during socket data recv %s(%d)","An unexpected but handleable event has occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","SOCKBIND","Cannot bind local socket for peer %s: %s","An error occurred during a socket operation. Parameters: Peer address, Error ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","SOCKCREATE","Cannot create socket for peer %s: %s, stats: %lu/%lu/%lu/%lu/%lu","An error occurred during a socket operation. Parameters: Peer address, Error, Socket stats ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","SOCKNONBLOCK","Couldn't make fd %d non-blocking: %s","An error occurred during a socket operation. Parameters: Socket fd, Error ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","SOCKOPEN","TCP connection for peer %s already open, fd %d, state %s","An internal software error occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","SOFTINCAP","Peer %s not capable of soft refresh in, operator intervention needed: %s","The router is unable to do a soft refresh for the indicated peer.","If necessary, reset the connection with the peer."
"BGP","3","SRAND","Failed to set random seed","An unrecoverable error has occurred during BGP initialization.","Use the 'restart' command to restart the feature and clear this problem."
"BGP","3","TBLATTRAVL_OP","Failed table attribute database operation: %s, id %lu","BGP was unable to perform a table attribute database operation Parameters: Operation, Attr ID ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","TBLAVL_OP","Failed table database operation: %s, table %s id %lu","BGP was unable to perform a table database operation.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","TBLCTX_INIT","VRF %s, %s, table %s: Table initialization failed","BGP was unable to initialize an internal datastructure. The BGP process may have run out of memory. Parameters: VRF name, Address-family, Table name ...","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 available memory, restart BGP."
"BGP","3","THREAD_SHUTDOWN","Problem shutting down thread %s: Operation - %s, Error - %s\n","An unexpected but handleable event has occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","TIMER_START","Couldn't start %s timer %s","An internal software error occurred. Parameters: Timer Type, Data ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","U6RIBRNH","U6RIB RNH error: %s","An internal software error occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","ULIBREG","Unable to register with ULIB","An unrecoverable error has occurred during BGP initialization.","Use the 'restart' command to restart the feature and clear this problem."
"BGP","3","ULIBRNH","ULIB RNH error: %s","An internal software error occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","UNEXPECT","%s L%d: %s","An internal software error occurred. Parameters: File Name, Line Number, Unexpected condition ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","URIB_API","URIB API %s() failed\n","URIB API had failed.","No action is required."
"BGP","3","URIB_RT_MODIFY","URIB route modify operation failed during %s","An internal software error occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","URIBRNH","URIB RNH error: %s","An internal software error occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","URIBRT","URIB RT error: %s","An internal software error occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","VRF_CTX","VRF %s, failed %s","An internal software error occurred. Parameters: VRF Name, Operation ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","3","VRFAVL_OP","Failed vrf database operation: %s, vrf %s id %lu","BGP was unable to perform a vrf database operation.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","4","APIMTSNOMSG","No MTS payload found on %s queue, opc %d","An unexpected but handleable event has occurred. Parameters: Queue name, MTS Opcode ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","4","EXTCOMLEN","%s(): Extended communities(%u + %d) exceeded the max limit of %u","An internal limit was hit in adding an extended community.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","4","INVALIDIOD","Received interface(%s) %s notification from IM with zero iod","BGP received an IF notification from IM with zero or invalid iod Parameters: Interface name, Type of notification ...","No action is required."
"BGP","4","ISSU_CHECK","Not ready for ISSU: Graceful Restart or hold time check failed","No user action is required.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","4","ISSU_HOLDTIME","ISSU will be affected if hold time is less than or equal to system switchover time (%d seconds)\n","No user action is required.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","4","LDP_CONV_TIMER_EXP","[%s] Bestpath timer expired before LDP got converged vrf: %s","Bestpath timer expired before LDP got converged after SSO Parameters: Address-family,vrf ...","No action is required."
"BGP","4","MAXPEERS","Trying to configure more than %d neighbors","No user action is required.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","4","MQUNEXPECT","Recieved unexpected message (%d/%d) on %s queue","An unexpected but handleable event has occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","4","MTSNOMSG","No MTS payload found on %s queue, opc %d","An unexpected but handleable event has occurred. Parameters: Queue name, MTS Opcode ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","4","MTSUNKOPC","Recieved unknown MTS message on %s queue, opc %d","An unexpected but handleable event has occurred. Parameters: Queue name, MTS Opcode ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","4","NODAMPMEM","[%s] Unable to dampen prefix %s from peer %s due to no memory","BGP_EXPL_NO_MEMORY Parameters: Address-family, Prefix/masklength, Peer address ...","No action is required."
"BGP","4","NORID","Peer %s sent us 0.0.0.0 as its router-id","A BGP peer sent us an invalid router ID.","Check that the peer router is configured correctly. Clear the peer if necessary after any change."
"BGP","4","PFXEXCEED","[%s] No. of prefix received from %s exceeded configured limit %d","A peer sent more routes than BGP was configured to accept. Parameters: Address-family, Peer, Prefix limit ...","Check that the peer router is configured correctly. Clear the peer if necessary after any change."
"BGP","4","PFXWARN","[%s] Number of prefixes received from %s reached %d, maximum %d","The number of routes sent to us by a peer exceeded the threshold at which BGP should generate a warning. Parameters: Address-family, Peer, Warning limit, Max limit ...","Check that the peer router is configured correctly. Clear the peer if necessary after any change."
"BGP","4","RLIMIT","Error while setting rlimit, error - %s\n","An unexpected but handleable event has occurred.","No action is required."
"BGP","4","SAMERID","Peer %s uses same routerid as us","A BGP peer is using the same router ID as this router.","Configure either the local or remote router with a different router ID."
"BGP","4","SLAB_HOLD","Not able to hold element from %s slab","The system has detected an error.Parameters: Memory slab name ...","No action is required."
"BGP","4","SNMP_DEREGFAIL","Failed to deregister MIB with the SNMP agent (%s).\n","No user action is required.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","4","SNMP_REGFAIL","Failed to register MIB with the SNMP agent, the BGP MIB will be unavailable. (%s)\n","No user action is required.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","4","TXLIST","%s","An unexpected but handleable event has occurred. Parameters: Error message related to txlist ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"BGP","5","ADJCHANGE","neighbor %s %s %s","A BGP session has just been established. Or a session has just been shutdown. Parameters: Neighbor address, Up or Down, Reason ...","No action is required."
"BGP","5","BADSIG","Should not have received signal %d","An unexpected but handleable event has occurred.","No action is required."
"BGP","5","MAXMSGLIMIT","[%s] Failed to send update message with prefix %s for peer %s because the msg size(%u) exceeded the maximum limit(%u)","BGP Update message reached the maximum limit Parameters: Address-family, Prefix, Peer, Update Message Length, Update Max Message Length ...","No action is required."
"BGP","5","MEMALERT","BGP memory status changed from %s to %s","The system has detected an error.Parameters: Current memory status ...","No action is required."
"BGP","5","NO_RD","VRF %s : RD deconfigured","RD deconfigured from VRF. Parameters: VRF Name ...","No action is required."
"BGP","5","SHUTDOWN","BGP protocol administratively shutdown","BGP protocol was administratively shutdown.","No action is required."
"BGP","6","AS4AGG_INVALID","Received AS4_AGGREGATOR with invalid length %d in it from peer %s","The peer has sent AS4_AGGREGATOR with invalid attr length which would be discarded.","No action is required."
"BGP","6","AS4PATH_CONFED","Received AS4_PATH with CONFED related path segments in it from peer %s","The peer has sent AS4_PATH with confed based path segments which would be discarded.","No action is required."
"BGP","6","AS4PATH_SEGLEN","Received AS4_PATH with zero path segment length in it from peer %s","The peer has sent AS4_PATH with zero path segment length which would be discarded.","No action is required."
"BGP","6","AS4PATH_SEGTYPE","Received AS4_PATH with invalid path segment type in it from peer %s","The peer has sent AS4_PATH with invalid path segment type which would be discarded.","No action is required."
"BGP","6","BADASPATH","Long AS path %s received from peer %s: more than configured maxas-limit %d","Session can be brought up due to maximum-peer limit.","No action is required."
"BGP","6","EXIT_DECONFIG","BGP process exiting due to deconfiguration","The indicated BGP process has been deconfigured.","No action is required."
"BGP","6","EXIT_RESTART","BGP process exiting due to manual restart","The indicated BGP process is being restarted.","No action is required."
"BGP","6","EXIT_UNKNOWN","BGP process exiting due to unknown reason","The system has detected an error.","No action is required."
"BGP","6","IMPORT_DEFAULT_MAXPFX_LIMIT","%s Prefixes imported from vrf default to vrf %s reached the max limit %d","The system has detected an error.Parameters: Address family, Vrf, Max-prefix-limit check result ...","No action is required."
"BGP","6","MEMSTAT","Hit low memory condition - Free: %u MB, Min free: %u MB","The system has detected an error.Parameters: Current The system free memory, Minimum System free memory ...","No action is required."
"BGP","6","PATH_MAXASLIMIT","[%s] Path for %s from peer %s found to %s the maxas-limit","The system has detected an error.Parameters: Address family, Prefix Masklength, EBGP Peer that sent the route, Maxas-limit check result ...","No action is required."
"BGP","6","START","BGP process %s startup, reason: %s","The indicated BGP process has started. Parameters: Process name, Reason ...","No action is required."
"EIGRP","2","ALLOC_URIB_ADD","eigrp_smalloc() failed for URIB add-route buffer","Failed to allocateate URIB add-route buffer.","Configure the network or router to decrease the number of routes, or add additional memory to the router."
"EIGRP","2","ALLOC_URIB_DEL","eigrp_smalloc() failed for URIB delete-route buffer","Failed to allocateate URIB delete-route buffer.","Configure the network or router to decrease the number of routes, or add additional memory to the router."
"EIGRP","2","API_INIT","Couldn't initialize %s API","EIGRP failed to open API to interact with the component. Parameters: API name ...","Restart the component when the system is working."
"EIGRP","2","BFD_API_FAIL","bfd_send_remove_sessions","Failed to send bfd remove sessions.","No action is required."
"EIGRP","2","BFD_CREATE_SESSION_FAILED","BFD Session create failed.","Failed to create BFD session.","No action is required."
"EIGRP","2","CIB_CREATE_FAIL","eigrp_create_cib failed for context %s","Failed to create specified context. Parameters: Context name ...","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","2","CLEANUP_DREG","Failed to deregister with %s during eigrp_cleanup()","Failed to deregister with specified service during process shutdown. Parameters: Service name ...","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","2","CLI_INIT_FAILED","cli_init() failed in eigrp_init_cli()","EIGRP could not register with the CLI server process.","Restart the component when the system is working."
"EIGRP","2","ERR_FREEBUF","Illegal memory free in function %s","Illegal memory free detected. Parameters: Function ...","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","2","ERR_URIB_TID","Can't determine context from URIB table id %ld","Failed to determine context from URIB table id. Parameters: Table id ...","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","2","ILL_FUNCCALL","Illegal call to function %s","Illegal call to specified function. Parameters: Function ...","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","2","ILL_POLICY_TYPE","Illegal policy type in %s()","Illegal policy type in specified rpm callback. Parameters: Function ...","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","2","ILL_WORKTYPE","Illegal work type %d ipigrp2_process_workq()","Worker thread received illegal work type. Parameters: Work type ...","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","2","ILLEGAL_TIMER_ID","Illegal timer-id used in mgd_timer_init_leaf(), timer-id: %d","Illegal timer id was specified. Parameters: Managed timer id ...","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","2","IM_GET_NAME_FAILED","im_get_if_name failed for iod (%lu) with error (%d)","EIGRP could not get if_name from Interface Manager.","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","2","IM_REG_FAILED","im_register_client() failed in eigrp_init_im()","EIGRP could not register with the IM process.","Restart the component when the system is working."
"EIGRP","2","INIT","%s failed","EIGRP process initialization failed. Parameters: Init function ...","Restart the component when the system is working."
"EIGRP","2","IP_REG_FAILED","ip_register() failed in eigrp_init_ip()","EIGRP could not register with the IP process.","Restart the component when the system is working."
"EIGRP","2","L3VM_SOO_NOTIF","l3vm_get_if_soo_info failed for interface %s","EIGRP could not get SoO from L3VM for.","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","2","MGD_TIMER_CREATE_FAIL","Failed to create managed timer %d","Failed to create specified managed timer. Parameters: Managed timer id ...","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","2","MTS_BIND","mts_bind() failed in binding %s mts_q, error %s","Failed in binding to specified mts queue with error. Parameters: MTS queue name, Error string ...","Restart the component when the system is working."
"EIGRP","2","MTS_REQ_FM_STATUS","Failed in mts_register of MTS_OPC_FM_SRV_FEATURE_STATUS","Failed to request feature status notification.","Restart the component when the system is working."
"EIGRP","2","MTSBIND","Unable to bind to MTS SAP for %s, sap %d: %s","EIGRP was not able to create a message queue for communication. Parameters: Queue name, MTS SAP, Error ...","Use the 'restart' command to restart the feature and clear this problem."
"EIGRP","2","NO_MEMORY","Can't allocate memory in function %s","Cannot allocate memory in specified function. Parameters: Function ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","2","NO_SET_PRIORITY","Failed to set policy or priority","EIGRP process could not set itself process priority, exiting.","Restart the component when the system is working."
"EIGRP","2","PROCINFO_CREATE_FAIL","eigrp_procinfo creation failed","Failed to create procinfo.","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","2","PTHREAD_FAILED","%s failed in %s for thread %s","EIGRP process failed to create a task thread. Parameters: Pthread operation, Function, Thread name ...","Restart the component when the system is working."
"EIGRP","2","REG_L3VM","Failed to register with l3vm","Failed to register with the l3vm process.","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","2","REG_OPCODE","Could not register opcode 0x%x, reason %s","Could not register mts opcode with the reason. Parameters: Opcode, Reason ...","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","2","RLIMIT_FAILED","Couldn't set data segment size to %lu","EIGRP process could not set its memory resource limit, exiting. Parameters: Data segment size ...","Restart the component when the system is working."
"EIGRP","2","RPM_L3VPN_API","RPM_L3VPN_API failed : %s","EIGRP call tp RPM L3VPN API failed.","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","2","SBCR_INIT","Could not initialize shared database client, rc=0x%x [%s]","Failed to initialize shared database client with return error code. Parameters: Error code, Error string ...","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","2","TIMER_CREATE_FAIL","Failed to create %s active timer","Failed to create specified active timer. Parameters: Active timer name ...","Restart the component when the system is working."
"EIGRP","2","TIMER_SET_INIT","Couldn't init %s active timer set","EIGRP failed to initialize timer resource. Parameters: Timer set name ...","Restart the component when the system is working."
"EIGRP","2","URIB_ACK_ERROR","URIB ack not processed: %s","EIGRP could not find the xid for URIB ack.","No action is required."
"EIGRP","2","URIB_ADD_ROUTE","urib_add_route() failed","Failed to add routes to URIB.","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","2","URIB_DEREGISTER","Could not deregister with the URIB in %s","EIGRP could not deregister with URIB in specified function. Parameters: Function ...","Restart the component when the system is working."
"EIGRP","2","URIB_REDIST_LIMIT_WARNING","Redistribute threshold limit reached: %d%%.","EIGRP has reached the configured redistRIBute maximum-prefix threshold. Parameters: Threshold ...","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","2","URIB_REGISTER","EIGRP could not register with the URIB","At initialization time, EIGRP could not register with the URIB process.","Restart the component when the system is working."
"EIGRP","2","URIB_RT_MOD_INIT","URIB_RT_MOD_INIT failed","EIGRP call tp URIB_RT_MOD_INIT API failed.","Restart the component when the system is working."
"EIGRP","2","URIB_SEND_BUFFER","urib_rt_mod_send() failed","Failed to send add/delete buffer to URIB. The RIB and topology table might be inconsistent. Try restarting EIGRP to clear the issue.","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","2","VERIFY_PTAG","Could not verify process tag with sysmgr","Could not verify process tag with sysmgr.","Restart the component when the system is working."
"EIGRP","3","ANCHORCOUNT_DUAL","Anchor count negative","A software or hardware error occurred.","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","3","BADCOUNT_DUAL","Route %s, %d successors, %d rdbs","A software or hardware error occurred. Parameters: Route, Number of feasible successors, Number of successors ...","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac. ;."
"EIGRP","3","BFD_SEND_AUTO_EXPIRY","Unable to start BFD staling, error %s","EIGRP BFD staling API failed Parameters: Error string ...","Dump core, and then restart component."
"EIGRP","3","BUFFER_OVERFLOW","Buffer overflow: %s","Buffer overflow while writing EIGRP community.","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","3","CMI_NO_VRF_ERR","CMI error: No %s VRF information found","CMI returned an error Parameters: Error ...","No action is required."
"EIGRP","3","DUP_ADDR","Duplicate address %s detected on interface %s","The same IP address was configured on two EIGRP routers on the same subnet. Parameters: IP address, Interface ...","Do not configure the same IP address on multiple EIGRP routers in the same subnet."
"EIGRP","3","GR_OFF_DURING_UPG","Attempt to upgrade system with graceful-restart off.","Attempt to upgrade system with graceful-restart off.","Enable graceful-restart before attempting system upgrade."
"EIGRP","3","INTERNAL_DUAL","%s %d: Internal Error","EIGRP internal DUAL finite state error. Parameters: DUAL descriptor block name, Autonomous system number ...","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","3","MTS_DROP","Error returned from mts_drop(), errno: %s","EIGRP called an MTS API which returned an error. Parameters: Error string ...","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","3","MTS_RECV","Error returned from mts_recv(), errno: %s","EIGRP called an MTS API which returned an error. Parameters: Error string ...","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","3","MTS_REGISTER","mts_register failed for EIGRP: %s","EIGRP was unable to register an MTS notification.","No action is required."
"EIGRP","3","MTSDROP","MTS drop failed on %s queue: %s","EIGRP_EXPL_UNEXPECTED_EVENT Parameters: Queue name, Error ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","3","MTSRECV","MTS receive failed on %s queue: %s","EIGRP_EXPL_UNEXPECTED_EVENT Parameters: Queue name, Error ...","No action is required."
"EIGRP","3","MTSSEND","MTS send() error to SAP %d, opcode %d: %s","EIGRP_EXPL_UNEXPECTED_EVENT Parameters: MTS SAP, MTS Opcode, Error ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","3","MULTIFLOW_DUAL","Flow control error, %s, on %s","A software or hardware error occurred. Parameters: Error description, Interface ...","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","3","NOHANDLE_DUAL","Handle %d is not allocated in pool.","A software or hardware error occurred. Parameters: Peer handle ...","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","3","PEERSEXIST_DUAL","%d peers exist on IIDB %s","A software or hardware error occurred. Parameters: Peer count, Interface ...","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","3","PFXLIMIT_DUAL","%s %d %s prefix limit exceeded","Prefix limit threshold exceeded. Parameters: DUAL descriptor block name, Autonomous system number, Prefix type ...","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","3","PFXLIMITTHR_DUAL","%s %d %s reached prefix limit threshold","Prefix limit threshold reached. Parameters: DUAL descriptor block name, Autonomous system number, Prefix type ...","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","3","PROBESEQ_DUAL","Bad probe sequence %d from %s, expecting %d Parameters: Probe seq no received, Peer, Expected seq no ...","A software or hardware error occurred.","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","3","RDBLEFT_DUAL","dest %s, nexthop %s (%s), origin %s","A software or hardware error occurred. Parameters: Route, Next hop, Inteface Origin ...","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","3","REFCOUNT_DUAL","Negative refcount in pakdesc %x","A software or hardware error occurred. Parameters: Packet descriptor ...","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","3","RPM_REDIST_INIT","Couldn't initialize redistribution API for %s","EIGRP failed to open API to interact with the component. Parameters: RedistRIButed client ...","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","3","SIA_DUAL","Route %s stuck-in-active state in %s %d. Cleaning up","EIGRP route stuck-in-active, cleanup happened. Parameters: Route, DUAL descriptor block name, Autonomous system number ...","No action is required."
"EIGRP","3","SYSMGR_DISPATCH","Error returned from sysmgr_dispatch(), errno: %s","EIGRP called the system manager API which returned an error. Parameters: Error string ...","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","3","SYSMGR_QUERY","Sysmgr state query failed for uuid %d, tag %s","A software or hardware error occurred. Parameters: Service UUID, Process Tag ...","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","3","UNKNOWN_MTYPE","Unknown mtype: %d/%d in %s","EIGRP process received unknown Interprocess message, dropped. Parameters: Message major type, Message mior type, Function ...","No action is required."
"EIGRP","3","UNKTIMER_DUAL","Unknown timer type %d expiration Parameters: Managed timer id ...","A software or hardware error occurred.","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","4","MQUNEXPECT","Recieved unexpected message (%d/%d) on %s queue","EIGRP_EXPL_UNEXPECTED_EVENT.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","4","MTSNOMSG","No MTS payload found on %s queue, opc %d","EIGRP_EXPL_UNEXPECTED_EVENT Parameters: Queue name, MTS Opcode ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","4","MTSUNKOPC","Received unknown MTS message on %s queue, opc %d","EIGRP_EXPL_UNEXPECTED_EVENT Parameters: Queue name, MTS Opcode ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"EIGRP","4","PICOSEC_WARN","ip delay eigrp command accepted but did not take effect in 32 bit version mode","The command was issued when in 32bit metric version mode.","No action is required."
"EIGRP","5","EVENT_DUAL","%s, %s","DUAL event log message. Parameters: DUAL descriptor block name, Log message ...","No action is required."
"EIGRP","5","HA_INFO","EIGRP HA info msg - %s","EIGRP received a HA informational message Parameters: Message ...","No action is required."
"EIGRP","5","NBRCHANGE_DUAL","%s %d: Neighbor %s (%s) is %s: %s","A neighbor went up or down. Parameters: DUAL descriptor block name, Autonomous system number, Peer, Interface, State, Reason ...","No action is required."
"EIGRP","5","SHUTDOWN","Shutting down EIGRP process - %s","EIGRP received a shutdown request. Parameters: Reason ...","No action is required."
"EIGRP","6","UNEQUAL_METRICS","EIGRP: Unequal metric (%s), delay [%llu/%llu], bandwidth [%llu/%llu] , mtu [%u/%u], hopcount [%u/%u], reliability [%u/%u], load [%u/%u]","Unequal metrics detected and log-neighbor-warnings are enabled. Parameters: Route, Delay1, Delay2, Bandwidth1, Bandwidth2, Mtu1, Mtu2, Hopcount1, Hopcount2, Reliability1 Reliability2, Load1, Load2 ...","EIGRP process still operational. Send error log message and running configuration to the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"FTM","3","ERR_CFGFAILED","%s","Configuration Error.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"FTM","3","ERR_HWNOMEM","%s","H/W Mem Allocation Err.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"FTM","3","ERR_HWWRITE","%s","H/W Write Error.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"FTM","3","ERR_INTERNAL","%s","Internal Error.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"FTM","3","ERR_IPCFAILED","%s","IPC failure.","No action is required."
"FTM","3","ERR_NOACTION","%s","Internal Data structure error.","No action is required."
"FTM","3","ERR_SWNOMEM","%s","S/W Mem Error.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"FTM","3","WARN_INTERNAL","%s","Internal Warning.","No action is required."
"HEAP","3","HEAP_ERROR","%s","Heap routing library error.","No action is required."
"HEAP","4","HEAP_WARNING","%s","Heap malloc warning.","No action is required."
"ICMPv6","2","MALLOC_FAILED","malloc() failed for allocating %s in %s()","ICMPv6 process is out of heap memory. This could be due to temporary increase in the number of static or dynamic Neighbor Cache Entries(NCEs) to a very high value.","No action is required."
"ICMPv6","3","ADJ_ADD","Failed to add adjacency for received packet from %s on %s","Due to this failure, packet forwarding to this address will be affected until the next successful retry.","No action is required."
"ICMPv6","3","API_FAILED","%s failed in %s()","An unexpected but manageable event has occurred.;.","No action is required."
"ICMPv6","3","API_INIT_FAILED","%s failed in %s() with rc=0x%x, %s","An unexpected but manageable event has occurred.;.","No action is required."
"ICMPv6","3","API_INTERFACE_FAILED","%s failed for %s in %s()","An unexpected but manageable event has occurred.;.","No action is required."
"ICMPv6","3","BAD_INFO_RECEIVED","Invalid %s message type %d received in %s()","An unexpected but manageable event has occurred.;.","No action is required."
"ICMPv6","3","BITFIELD_FAILED","%s failed in %s","ICMPV6 process could not execute the bitfield operation. Parameters: Bitfield operation, Function name ...","Dump core, then reload the stack."
"ICMPv6","3","CV_INIT","Couldn't init cond var %s","ICMPV6 process failed to initialize conditional-variable resource. Parameters: Thread Name ...","Dump core, and then restart component."
"ICMPv6","3","FHRP_CTXT","Adding virtual ipv6 address for %s: non-ipv6 enabled interface %s in context %ld","UNEXPECTED_ERROR_EXPLANATION.","No action is required."
"ICMPv6","3","GROUP_PREFIX_IGNORE","Too many Groups in Group Prefix %s. Specify the prefix within /120","GPrefix yields too many Groups Parameters: Group Prefix ...","No action is required."
"ICMPv6","3","GROUP_RANGE_IGNORE","Too many Groups in Group Range %s - %s","Group Range yields too many Groups Parameters: Start Group, End Group ...","No action is required."
"ICMPv6","3","IF_INDEX","Invalid interface index received from %d","UNEXPECTED_ERROR_EXPLANATION.","No action is required."
"ICMPv6","3","MBUF_OP_FAILED","%s for size %d failed in %s()","An unexpected but manageable event has occurred.;.","No action is required."
"ICMPv6","3","MQ_FAILED","%s failed, errno: %s in %s()","An unexpected but manageable event has occurred.;.","No action is required."
"ICMPv6","3","MQ_FAILED_NAME","%s failed for client %s, errno: %s in %s()","An unexpected but manageable event has occurred.;.","No action is required."
"ICMPv6","3","MQ_FAILED_PID","%s failed to client pid: %d, errno: %s in %s()","An unexpected but manageable event has occurred.;.","No action is required."
"ICMPv6","3","MSG_TO_TLV","TLV Conversion failed (%d)","TLV conversion failed.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"ICMPv6","3","MTS_DROP","Error returned from mts_drop(), errno: %s","ICMPv6 called an MTS API which returned an error.","Dump core, and then restart component."
"ICMPv6","3","MTS_FAILED","%s failed, errno: %s in %s()","An unexpected but manageable event has occurred.;.","No action is required."
"ICMPv6","3","MTS_FAILED_NAME","%s failed for client %s, errno: %s in %s()","An unexpected but manageable event has occurred.;.","No action is required."
"ICMPv6","3","MTS_FAILED_PID","%s failed to client pid: %d, errno: %s in %s()","An unexpected but manageable event has occurred.;.","No action is required."
"ICMPv6","3","MTS_RECV","Error returned from mts_recv(), errno: %s","ICMPv6 called an MTS API which returned an error.","Dump core, and then restart component."
"ICMPv6","3","MUTEX_INIT","Couldn't init mutex %s","ICMPV6 process failed to initialize mutex system resource. Parameters: Thread Name ...","Dump core, and then restart component."
"ICMPv6","3","ND_LOG","%s","Neighbor Discovery process found erroroneous configuration on the network.","No action is required."
"ICMPv6","3","ND_RA_LOG","%s","Network configuration information obtained from Neighbor Discovery - Router Acknowledgement(RA) packet.","No action is required."
"ICMPv6","3","PACKET_LENGTH_ERROR","ICMPv6 packet from %s is smaller than payload length of %d bytes:%s()","An unexpected but manageable event has occurred.;.","No action is required."
"ICMPv6","3","PT_ADD","Couldn't add element to PT %s","ICMPv6 failed to update the local database entry. Parameters: Patricia tree name ...","No action is required."
"ICMPv6","3","PT_DEL","Couldn't delete element from PT %s","ICMPv6 failed to delete the local database entry. Parameters: Patricia tree name ...","No action is required."
"ICMPv6","3","RESERVE_LIMIT","Exceeded reserve-limit for interface %s - dropping","Exceeded 80% of the reserve-limit for interface Parameters: Interface ...","No action is required."
"ICMPv6","3","STATE_LIMIT","Exceeded state-limit for interface %s - dropping","Exceeded 80% of the state-limit for interface Parameters: Interface ...","No action is required."
"ICMPv6","3","SYSMGR_DISPATCH","Error returned from sysmgr_dispatch(), errno: %s","ICMPv6 called the system manager API which returned an error.","Dump core, and then restart component."
"ICMPv6","3","TIMER_FAILED","%s failed for %s in %s","The system has detected an error.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"ICMPv6","3","TLV_TO_STRUCT","TLV to Struct Conversion failed (%d)","TLV to Struct conversion failed.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"ICMPv6","3","TXLIST_CREATE","Couldn't create txlist for %s","ICMPV6 failed to create txlist resource. Parameters: Data type ...","Dump core, and then restart component."
"ICMPv6","3","VRF_CREATE","ICMPv6 VRF creation failed for vrf %s","ICMPv6 process could not create the VRF context. Parameters: VRF name ...","Dump core, then reload the stack."
"ICMPv6","6","FHRP_IOD","Adding virtual ipv6 address for %s: non-ipv6 enabled interface %s","UNEXPECTED_ERROR_EXPLANATION.","No action is required."
"ICMPv6","6","RESERVE_LIMIT_WARNING","Exceeded 80% of the reserve-limit for interface %s","Exceeded 80% of the reserve-limit for interface Parameters: Interface ...","No action is required."
"ICMPv6","6","STATE_LIMIT_WARNING","Exceeded 80% of the state-limit for interface %s","Exceeded 80% of the state-limit for interface Parameters: Interface ...","No action is required."
"ICMPv6","6","UNKNOWN_OPC","Received unknown mts opcode %d","ICMPv6 process received unknown Interprocess message, dropped.","No action is required."
"IGMP","2","STARTUP_DEBUG","%s %d","An unrecoverable software error has occurred during IGMP startup. Parameters: Failure reason ...","No action is required."
"IGMP","2","STARTUP_FAILURE","Startup failure: %s","An unrecoverable software error has occurred during IGMP startup. Parameters: Failure reason ...","No action is required."
"IGMP","3","ALREADY_RUNNING","IGMP already running, exiting","Another IGMP process is already running, this process will shut down.","No action is required."
"IGMP","3","API_FAILED","%s failed in %s","IGMP process failed in invoking an API. Parameters: API name, Function name ...","No action is required."
"IGMP","3","AVL_ERROR","AVL-tree operation %s failed for %s","IGMP process failed in an AVL-tree manipulation. Parameters: AVL tree operation, Tree name ...","No action is required."
"IGMP","3","BAD_MSG","Invalid %s message received from %s","IGMP received an invalid MTS message. Parameters: Message type, Process name ...","Dump core, and then restart component."
"IGMP","3","BF_CREATE","Couldn't create bitfield for %s","IGMP failed to create bitfield resource. Parameters: Data type ...","Dump core, and then restart component."
"IGMP","3","BITFIELD_FAILED","%s failed in %s","IGMP process could not execute the bitfield operation. Parameters: Bitfield operation, Function name ...","Dump core, then reload the stack."
"IGMP","3","CV_INIT","Couldn't init cond var %s","IGMP process failed to initialize conditional-variable resource. Parameters: Thread Name ...","Dump core, and then restart component."
"IGMP","3","GET_MAC_ADDR","%s failed in %s with error %s","IGMP process failed in getting mac addr Parameters: API name, Function name, Error String ...","No action is required."
"IGMP","3","GETRLIMIT_FAILED","Address Space size retrieval failed, reason %s","IGMP process could not retrieve memory resource limit.","No action is required."
"IGMP","3","GROUP_DEL","Couldn't delete group entry for %s (%s) due to %s from snooping database","IGMP failed to delete the snooping-db group entry. Parameters: Group address, Vlan-id, Failure reason ...","No action is required."
"IGMP","3","GROUP_PREFIX_IGNORE","Too many Groups in Group Prefix %s. Specify the prefix within /24","GPrefix yiels too many Groups Parameters: Group Prefix ...","No action is required."
"IGMP","3","GROUP_RANGE_IGNORE","Too many Groups in Group Range %s - %s","Group Range yields too many Groups Parameters: Start Group, End Group ...","No action is required."
"IGMP","3","HA_DB_REBUILD","HA run-time database buildup %s","IGMP-SNOOP stateful restart status Parameters: State description ...","No action is required."
"IGMP","3","HA_GLOBAL","HA %s operation on IGMP snooping global database failed","IGMP-SNOOP called a PSS API which returned an error. Parameters: Operation type ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IGMP","3","HA_GROUP","HA %s operation in vlan %d failed for (%s, %s)","IGMP-SNOOP called a PSS API which returned an error. Parameters: Operation type, Vlan-id, Group, Source ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IGMP","3","HA_OIF","HA %s operation on OIF %s for (%s, %s) in vlan %d failed","IGMP-SNOOP called a PSS API which returned an error. Parameters: Operation type, Interface, Group, Source, Vlan-id ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IGMP","3","HA_RPORT","HA %s operation on router-port %s for vlan %d failed","IGMP-SNOOP called a PSS API which returned an error. Parameters: Operation type, Interface, Vlan-id ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IGMP","3","HA_VLAN","HA %s operation for vlan %d failed","IGMP-SNOOP called a PSS API which returned an error. Parameters: Operation type, Vlan-id ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IGMP","3","IGMP_INIT","IGMP init failed: %s","IGMP process initialization failed. Parameters: Failure reason ...","Dump core, and then restart component."
"IGMP","3","IM_API_FAILED","%s failed in %s","IM API failed in MCEC IGMP Snoop. Parameters: API name, Function name ...","No action is required."
"IGMP","3","INVALID_OIF_LIST","IGMP Snooping invalid OIF list %s with %d iods in %s","IGMP-SNOOP has invalid number of iods. Parameters: OIF list, OIF count, Function name ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IGMP","3","LIB_API_FAILED","%s failed in %s","Process failed in invoking IGMP API. Parameters: API name, Function name ...","No action is required."
"IGMP","3","LIB_MTS_FAILED","%s failed in %s, errno: %s","Process failed to access the IGMP MTS-queue. Parameters: MTS IPC operation, Function name, Error ID ...","No action is required."
"IGMP","3","LVPORT_CREATE","IGMP Snooping couldn't create an leave-port in %s for group %s","IGMP-SNOOP called an API which returned an error. Parameters: Vlan ID, Group address ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IGMP","3","MALLOC_FAILED","%s failed in %s","IGMP process is out of free memory. Parameters: Structure type, Function name ...","Configure the network or router to decrease the number of routes."
"IGMP","3","MFDM_NO_BUF","Cannot find MFDM buffer from route-ack for xid 0x%x","IGMP process could not find a route buffer in its queue from the MFDM message, igored.","No action is required."
"IGMP","3","MTS_BIND","Error returned from mts_bind() for %s mts-q, errno: %s","IGMP called an MTS API which returned an error. Parameters: MTS Queue name, Error description ...","Dump core, and then restart component."
"IGMP","3","MTS_DROP","Error returned from mts_drop() for %s queue, errno: %s","IGMP called an MTS API which returned an error. Parameters: MTS Queue name, Error description ...","Dump core, and then restart component."
"IGMP","3","MTS_RECV","Error returned from mts_recv() for %s queue, errno: %s","IGMP called an MTS API which returned an error. Parameters: MTS Queue name, Error description ...","Dump core, and then restart component."
"IGMP","3","MTS_SEND","Error returned from mts_send() for %s queue, errno: %s","IGMP called an MTS API which returned an error. Parameters: MTS Queue name, Error description ...","Dump core, and then restart component."
"IGMP","3","MUTEX_INIT","Couldn't init mutex %s","IGMP process failed to initialize mutex system resource. Parameters: Thread Name ...","Dump core, and then restart component."
"IGMP","3","NO_SET_PRIORITY","Failed to set policy or priority","IGMP process could not set itself process priority, exiting.","No action is required."
"IGMP","3","NO_SHUTDOWN","Unable to shutdown %s","IGMP process unable to shut itself down. Parameters: Shutdown error information ...","Dump core, and then restart component."
"IGMP","3","PT_ADD","Couldn't add element to PT %s","IGMP failed to update the local snooping-db entry. Parameters: Patricia tree name ...","No action is required."
"IGMP","3","PT_DEL","Couldn't delete element from PT %s","IGMP failed to delete the local snooping-db entry. Parameters: Patricia tree name ...","No action is required."
"IGMP","3","PTHREAD_FAILED","%s failed in %s for thread %s","IGMP process failed to create a task thread. Parameters: Pthread operation, Function name, Thread name ...","Dump core, and then restart component."
"IGMP","3","PULLUP_FAILED","m_pullup() of %d bytes failed in %s","IGMP process failed to process the packet, dropping it. Parameters: Byte count, Function name ...","No action is required."
"IGMP","3","QUERIER_START_FAILED","%s failed in %s","IGMP snoop failed to start the querier. Parameters: Function name, Function name ...","No action is required."
"IGMP","3","RCOUNT_DELETE","Route count delete failed for %s","IGMP called an API which returned an error. Parameters: Interface ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IGMP","3","RCOUNT_UPDATE","Route count update failed for %s","IGMP called an API which returned an error. Parameters: Interface ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IGMP","3","RESERVE_LIMIT","Exceeded reserve-limit for interface %s - dropping","Exceeded the reserve-limit for interface Parameters: Interface ...","No action is required."
"IGMP","3","RESTART_REASON","IGMP process has restarted, restart reason: %s\n","IGMP is restoring the routes it had added in previous instance. Parameters: Restart reason ...","No action is required."
"IGMP","3","RPORT_UPDATE","Router-port update failed for %s (%s)","IGMP-SNOOP called an API which returned an error. Parameters: Interface, Vlan ID ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IGMP","3","SETRLIMIT_FAILED","Address space size increment of %ld failed, reason %s","IGMP process could not set a memory resource limit Parameters: Number of bytes ...","No action is required."
"IGMP","3","SNOOP_CONFIG_ERROR","SNOOP: Couldn't configure %s, please configure %s first.","IGMP snooping could not configure a parameter because of dependencies Parameters: Configuring parameter, Dependent parameter ...","No action is required."
"IGMP","3","SOURCE_DEL","Couldn't delete source entry for (%s, %s) (%s) due to %s from snooping database","IGMP failed to delete the snooping-db source entry. Parameters: Source address, Group address, Vlan-id, Failure reason ...","No action is required."
"IGMP","3","STATE_LIMIT","Exceeded state-limit for interface %s - dropping","Exceeded the state-limit for interface Parameters: Interface ...","No action is required."
"IGMP","3","SYSMGR_DISPATCH","Error returned from sysmgr_dispatch(), errno: %s","IGMP called the system manager API which returned an error. Parameters: Error description ...","Dump core, and then restart component."
"IGMP","3","TIMER_FAILED","%s failed for %s in %s","IGMP process failed to configure a timer event. Parameters: Timer operation, Timer name, Function name ...","Dump core, and then restart component."
"IGMP","3","TXLIST_CREATE","Couldn't create txlist for %s","IGMP failed to create txlist resource. Parameters: Data type ...","Dump core, and then restart component."
"IGMP","3","UNKNOWN_MFDM_OPC","igmp_snoop_mfdm_main(): reeceived unknown opcode %d","IGMP process received unknown Interprocess message from MFDM, dropped. Parameters: Operation code ...","No action is required."
"IGMP","3","UNKNOWN_MTYPE","Unknown mtype: %d/%d in %s, opc:%d, from:%s","IGMP process received unknown Interprocess message, dropped. Parameters: Major ID, Minor ID, Function name ...","No action is required."
"IGMP","3","VLAN_DEL","Couldn't delete vlan entry for %s due to %s from snooping database","IGMP failed to delete the snooping-db vlan entry. Parameters: Vlan-id, Failure reason ...","No action is required."
"IGMP","3","VLAN_EXISTS","SNOOP: Couldn't create %s, already esists","IGMP failed to create vlan resource. Parameters: VLAN ID ...","No action is required."
"IGMP","3","vPC_API_FAILED","%s%s","API failed in vPC IGMP snoop module. Parameters: Error message, Error ...","No action is required."
"IGMP","3","vPC_ERROR","%s%s","vPC related messages. Parameters: vPC related message, Error message ...","No action is required."
"IGMP","3","VRF_CREATE","IGMP VRF creation failed for vrf %s","IGMP process could not create the VRF context. Parameters: VRF name ...","Dump core, then reload the stack."
"IGMP","5","SNOOP_LOOKUP_MAC_FOR_ALL","Changed to MAC based lookup for ALL vlans\n","If a vlan lookup mode is MAC and vdc-mode is changed to mixed from non-mixed, lookup mode is changed to MAC for ALL VLANs.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IGMP","6","AS_LIMIT_INCREASED","Address space size for %s increased %d times","IGMP process incremented AS memory resource limit Parameters: Module name, Increment count ...","No action is required."
"IGMP","6","HA_SEQNO_SYNC","HA sequence number sync to standby failed, %s","IGMP-SNOOP HA sequence number synchronizationto standby failed Parameters: Error description ...","No action is required."
"IGMP","6","HA_STATEFUL","Stateful HA %s","IGMP-SNOOP stateful restart status Parameters: State description ...","No action is required."
"IGMP","6","HA_SYNC","HA sync to standby failed, %s","IGMP-SNOOP HA synchronizationmessage to standby failed Parameters: Error description ...","No action is required."
"IGMP","6","RECEIVE_QUERY","Received %s interface %s from %s","IGMP version mismatch, query still processed. Parameters: IGMP version mismatch, Interface, Source address ...","No action is required."
"IGMP","6","RESERVE_LIMIT_WARNING","Exceeded 80% of the reserve-limit for interface %s","Exceeded 80% of the reserve-limit for interface Parameters: Interface ...","No action is required."
"IGMP","6","RESTART_SHUTDOWN","IGMP shutting self down via restart command","IGMP process is shutting itself down due to the restart command.","No action is required."
"IGMP","6","SHUTDOWN","IGMP shutting self down","IGMP process is shutting itself down.","No action is required."
"IGMP","6","STATE_LIMIT_WARNING","Exceeded 80% of the state-limit for interface %s","Exceeded 80% of the state-limit for interface Parameters: Interface ...","No action is required."
"IGMP","6","UNKNOWN_OPC","Received unknown mts opcode %d","IGMP process received unknown Interprocess message, dropped. Parameters: Operation Code ...","No action is required."
"IGMP","6","vPC_INFO","%s%s","vPC related messages. Parameters: vPC related message, Info message ...","No action is required."
"IM","2","AM_GETPIB","Unable to get pib from AM (pibname %s)","Could not initialize with Adjacency Manager.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","APIINIT","Unable to initialize %s API","Could not initialize server APIs.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","APILAUNCH","Unable to start %s","Could not start the specified protocol component.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","APIREGISTER","Unable to register with %s API","Could not register with specified server component.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","ATTACH","Unable to attach to %s","Could not attach to server shared memory.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","BADTUN","Bad tunnel type","Could not set the tunnel to specified type.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","BFCLEAR","Cannot clear bit %d in %s","Could not clear a bit in the specified bitfield.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","BFCLEARALL","Cannot clear all bits in %s","Could not clear all in the specified bitfield.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","BFCREATE","Cannot create %s","Could not create specified bitfield.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","BFFULL","Bit field %s is full","Specified bitfield does not have any available space.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","BFINIT","%s","Specified bitfiled could not be initialized.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","BFSET","Cannot set bit %d in %s","Could not set a bit in the specified bitfield.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","BFSETALL","Cannot set all bits in %s","Could not set all bits in the specified bitfield.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","CLICOMMANDSINIT","CLI commands could not be requested","Request to CLI server for IM commands failed.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","CLT_GET_DRVINDICES","Could not get driver indices","Could not calculate the totoal number of interface driver components.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","CLTREGISTER","Client %s registration failed, %s","IM client could not be registered due to specified reason.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","CLTUNREGISTER","Client %s deregister failed, %s","IM client could not be deregistered due to specified reason.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","DSTADDPT","Could not add tunnel node to dest PT, reason %d","Could not add the tunnel destination information to the internal data structure Recommened action: Use the 'restart' command to restart the feature and clear this problem.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IM","2","GETCONTEXT","Unable to get context from URIB (contextname: %s)","Could not initialize with URIB server.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","INTTIMER","Interface %s, %s failed","Interface related timer could not be started.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","MQOPEN","unable to open mq %s: %s","The system is unable to open the specified message queue.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","NHADDPT","Could not add tunnel next-hop information to PT, reason %d","Could not add the next-hop information for the tunnel to the internal data structure.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","NOMEM","Malloc (%ld) failed for: %s","Memory allocation failed for the specified structure. We are running out of memory.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IM","2","PTHREAD","procket_pthread_create failed for %s: error %d","Could not create new thread.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","SHMCREATE","Cannot create shared memory, reason %d","IM is unable to create shared memory resources.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","SUPER_MEMBER_MISMATCH","super member: count %d, actual %d","Super interface member list is corrupted.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","SYSMGRNOTIFY","sysmgr notification for %s failed","Request for sysmgr notification for the specified component failed.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","TIMER","%s failed","Operation on the specified timer failed.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","TXLIST_BAD_OBJTYPE","Bad txlist object type %d","Unknown object type encountered in the transmit list. It could be indication of corrupted transmit list.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","TXLIST_CREATE","%s","Could not create transmit list.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","TXLIST_DELETE_MEMBER","txlist delete member failed for element %d","Could not remove client from the transmit list.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","TXLIST_INSERT_ELEMENT","txlist insert element failed for iod %d","Could not insert intreface in the transmit list.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","TXLIST_INSERT_MEMBER","txlist insert member failed for client %s","Could not insert client in the transmit list.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","TXTHREAD_INIT","%s","Could not initialize transmit list thread.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","URIB_GETPIB","Unable to get pib from URIB (pib 0x%p, pibname %s, context 0x%p, contexname %s","Could not initialize with URIB server.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","URIBRNH","URIB %s RNH failed for address %s","Could not setup request for RNH notification with URIB.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","WORKQ_ADD","Failed to add %s to work queue","Could not add the work item to the queue for worker thread.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","WORKQ_INIT","Failed to initialize work queue","Failed to initialize work queue.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","WORKQ_SYSMGR","%s is no longer alive, returning from %s","Server component is going down. Cannot do any more work for that server.","Use the 'restart' command to restart the feature and clear this problem."
"IM","2","WORKQ_WAIT","Error while waiting for work event, %d","Error while waiting for events in the worker thread.","Use the 'restart' command to restart the feature and clear this problem."
"IM","3","CLT_DIFF_EPID","epids differ, old %u, new %u","An older instance of the client is already registered with IM. The new instance will overwrite the old one.","No action is required."
"IM","3","CLTCLEAREXT","Client %s clear extension failed, %s","IM could not clear client extension for the specified interface.","No action is required."
"IM","3","CLTEXISTS","Client %s is already registered with IM via queue %s","An older instance of the client is already registered with IM. The new instance will overwrite the old one.","No action is required."
"IM","3","CLTSETEXT","Client %s set extension failed, %s","IM could not set client extension for the specified interface.","No action is required."
"IM","3","DFBADCLASS","Bad debug filter class 0x%x","Invalid class of debug filters.","No action is required."
"IM","3","ETH_BAD_STATS","snmp ether stats bad stats","Could not get interface statistics.","No action is required."
"IM","3","ETH_STATS_REQ","snmp ether stats bad send","Request to Ethernet driver to update statistics failed. This would lead to incorrect interface statistics value.","No action is required."
"IM","3","HEAP_SIZE_ERROR","Increase of heap size from %d to %d failed: %s","IM could not increase the size of the heap.","No action is required."
"IM","3","IF_CHANGE_MASK_UNKNOWN","Unknown if change mask for interface %s %s","Undefined change mask has been specified for the given interface.","No action is required."
"IM","3","IMTLV_BAD_MSGTYPE","IM bad tlv message type %d","Unknown message TLV encountered.","No action is required."
"IM","3","INTADD","Interface %s addition failed, %s","Interface could be created due to specified reason.","No action is required."
"IM","3","INTADDEXIST","Interface %s addition failed, %d already exists","Interface currently being added already exists.","No action is required."
"IM","3","INTADDFULL","Interface %s addition failed, Max. number of interfaces exceeded","Interface could not be configured as Interface Manager has reached its maximum capacity.","No action is required."
"IM","3","INTADDIFMSG","Could not process add interface %lx, %lx, %s","Received a corrupted message from interface driver.","No action is required."
"IM","3","INTADDPT","Interface %s addition failed, phyloc tree addition, reason %d","New interface could not added to internal data structure.","No action is required."
"IM","3","INTBAD","Invalid interface %d for %s","Specified action cannot be take on the interface.","No action is required."
"IM","3","INTDAMPINIT","Interface %s, could not initialize dampening","Interface dampening could not be initialized.","No action is required."
"IM","3","INTDEL","Interface %s deletion failed, %s","Interface could not be deleted due to specified reason.","No action is required."
"IM","3","INTDELIFMSGMASK","Could not process delete interface %lx bad mask %lx","Received a corrupted message from interface driver.","No action is required."
"IM","3","INTLSMSG","Could not process link state message %lx, %lx, %s","Received a corrupted message from interface driver.","No action is required."
"IM","3","MQSEND","mq_send() error %s while sending %s queue: %s","Specified message could not be sent to the IM client.","No action is required."
"IM","3","MQUNEXPECT","Recieved unexpected message (%d/%d) on %s queue","Received an unexpected message on the specified message queue.","No action is required."
"IM","3","MSGPROC","Could not process %s message from pid %d","Specified client request could not be completed.","No action is required."
"IM","3","MTS_DROP","Error returned from mts_drop(), errno: %s","IM called an MTS API which returned an error.","No action is required."
"IM","3","MTS_RECV","Error returned from mts_recv(), errno: %s","IM called an MTS API which returned an error.","No action is required."
"IM","3","NO_INTF_BLOCK","Interface block not found while processing %s, iod %d","Interface related internal data structure could be found.","No action is required."
"IM","3","SNMPAPIDATA","Message data is NULL","SNMP message does not have memory to store data.","No action is required."
"IM","3","SNMPAPIINIT","Function snmpd_api_init() was not invoked","SNAMP API is being invoked before it initilization.","No action is required."
"IM","3","SNOMEM","Smalloc (%ld) failed for: %s","Shared memory allocation failed. We are running out of shared memory resources.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IM","3","SONETINTTIMERFAIL","Sonet interval timer %s failed on %s","Specified timer could be initialized.","No action is required."
"IM","3","STATS_NODE_BAD","Invalid stats node for %s","Encountered invalid request to get/clear statistics.","No action is required."
"IM","3","STATS_NODE_NOT_FOUND","Cound not find stats node for %s","Could not find the internal data structure.","No action is required."
"IM","3","STATSQ_INIT","Failed to initialize stats queue","An internal software error occurred.","Use the 'restart' command to restart the feature and clear this problem."
"IM","3","VLANADDPT","Could not add Vlan information in tree, reason %d","VLAN interface information could not be added to internal data structure due to specified reason.","No action is required."
"IM","6","LINEPROTO","Line protocol on interface %s changed to state %s","Line protocol on the specified interface has changed.","No action is required."
"IM","6","MTS_UNKNOWN_MSG","Received unknown MTS message with opcde %d, dropping it","IM received an unknown MTS message. The message is dropped.","No action is required."
"IP","2","CRIT_FAILURE","Failed to %s","A critical operation has failed in the IP process.","Dump core, and then restart component."
"IP","2","IP_STARTUP_FAILURE","Failed to %s during startup. error %d","A critical operation has failed during startup of the IP process.","No action is required."
"IP","3","CV_INIT","Couldn't init cond var %s","IP process failed to initialize conditional-variable resource. Parameters: Thread Name ...","Dump core, and then restart component."
"IP","3","INVALID_IF_INDEX","Invalid interface index received from %d","Invalid interface index received Parameters: Thread Name ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IP","3","IP_CLIENT_GET","HA client filter recovery failed (%d)","HA client filter recovery failed.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IP","3","IP_CLNT_FAILURE","Invalid IP registration reply. Message major type %d, minor type %d","An IP client has failed in the registration process with IP.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IP","3","IP_FAILURE","Failed to %s","A critical operation has failed in the IP process.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IP","3","IP_HA_UPDATE","HA update failed (%d)","HA update failed.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IP","3","IP_INTERNAL_ERROR","%s","An internal error has occurred in the IP process.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IP","3","IP_MSG_TO_TLV","TLV Conversion failed (%d)","TLV conversion failed.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IP","3","IP_MTSDROP","Error returned from mts_drop(), errno: %s","IP called an MTS API which returned an error.","No action is required."
"IP","3","IP_MTSRECV","Error returned from mts_recv(), errno: %s","IP called an MTS API which returned an error.","No action is required."
"IP","3","IP_MTSSEND","Error returned from mts_send(), errno: %s","IP called an MTS API which returned an error.","No action is required."
"IP","3","IP_NO_MBUF","Failed to allocate mbuf %s","The IP process has run out of network buffers.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IP","3","IP_NO_MEM","Failed to allocate private memory for %s","The IP process has run out of private memory.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IP","3","IP_THR_CREATE","Failed to create %s thread. error %d","A failure occurred while creating a thread.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IP","3","IP_TLV_TO_STRUCT","TLV to Struct Conversion failed (%d)","TLV to Struct conversion failed.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IP","3","IP_UNK_MSG","Unrecognized message major type %d, minor type %d","An unknown message was received from another process.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IP","3","MRIB_ADD_ROUTE","MRIB add route failed in %s for VRF %s","IP failed to add route in MRIB. Parameters: Function Name, Context Name ...","No action is required."
"IP","3","MRIB_DELETE_ROUTE","MRIB delete route failed in %s for VRF %s","IP failed to delete route from MRIB. Parameters: Function Name, Context Name ...","No action is required."
"IP","3","MV_INIT","Couldn't init mutex %s","IP process failed to initialize mutex system resource. Parameters: Thread Name ...","Dump core, and then restart component."
"IP","3","NO_SH_MEM","Failed to allocate shared memory %s","The IP process has run out of shared memory.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IP","3","TXLIST_CREATE","Couldn't create txlist for %s","IP failed to create txlist resource. Parameters: Data type ...","Dump core, and then restart component."
"IP","3","URIB_ERR","Failed to %s urib","A failure occurred in a transaction with URIB.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IP","5","INVALID_NOTIFY","Received invalid notification message","UNEXPECTED_ERROR_EXPLANATION.","No action is required."
"IP","6","BAD_ICMP_PKT","Received ICMP packet with bad length (%d). Min len %d, Adv len %d, IP hdr length %d, Expected IP hdr len %d","An ICMP packet was received with a bad length.","No action is required."
"IP","6","IM_ERROR","Failed to get correct information for interface %s %d","IP could not get the requested informationfrom interface-mgr.","No action is required."
"IP","6","IM_RECOVER_ERROR","Failed to recover correct information for interface %s %d","IP could not recover theinformation forinterface.","No action is required."
"IP","6","IP_MTS_UNKNOWN_MSG","Received unknown MTS message with opcde %d, dropping it","IP received an unknown message. The message is dropped.","No action is required."
"IP","6","IP_UNK_MSG_MAJOR","Unrecognized message from %s. Major type %d","An unknown message (major) was received from another process.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IP","6","IP_UNK_MSG_MINOR","Unrecognized message from %s. Minor type %d","An unknown message (mior) was received from another process.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IP","6","MQ_FLUSH","Flushing %d messages from the MRIB message queue","The MRIB message queue was flushed after a restart of the IP process.","No action is required."
"IP","6","REG_SEND_MSG","Suppress PIM Data Register for (%s, %s) due to suppression-timer\n","Suppress PIM Data Register due to suppression-timer. Parameters: Source address, Group address ...","No action is required."
"IP","6","STATS_ERROR","Failed to get hardware statistics for interface %s, reason %s","IP could not get the requested statistics from the hardware.","No action is required."
"IP","6","SYSMAN_CLEANUP","Terminated by SYSMAN cleanup signal %d","The system Manager sent a cleanup signal to IP to exit the process.","No action is required."
"IPv6","2","RECURSIVE_LOOP","Recursive loop in %s","There is a recursive function calling loop.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IPv6","2","SDB_CREAT","Failed to create shared database","Component API call failed in IPv6.","No action is required."
"IPv6","2","SDB_DESTROY","Failed to destroy shared database","Component API call failed in IPv6.","No action is required."
"IPv6","2","SDB_OPEN","Failed to open shared database","Component API call failed in IPv6.","No action is required."
"IPv6","3","BAD_CONTEXT","Bad context-id %d in %s","The context cannot be found.","No action is required."
"IPv6","3","FRAME_GT_PAYLOAD","Frame length: %d greater than payload length: %d plus IPv6 header length, truncating packet received on interface %s","Mismatch in the packet's frame length and payload field, trimmed.","No action is required."
"IPv6","3","FRAME_LENGTH_LONG","Frame length: %d greater than maximum IPv6 payload size for packet received on interface %s","The packet has too big frame length, dropped.","No action is required."
"IPv6","3","FRAME_LENGTH_SHORT","Frame length: %d less than IPv6 payload length: %d for packet received on interface %s","The packet has invalid frame length, dropped.","No action is required."
"IPv6","3","GET_PIB_FAILED","%s failed in %s","IPv6 could not find client's PIB handle.","No action is required."
"IPv6","3","INVALID_VERSION","Invalid IPv6 version: %d for packet received on interface %s","The packet has invalid protocol version field, dropped.","No action is required."
"IPv6","3","IPV6_API_FAILED","%s failed in %s","Component API call failed in IPv6.","No action is required."
"IPv6","3","IPV6_CV_INIT","Couldn't init cond var %s","IPv6 process failed to initialize conditional-variable resource. Parameters: Thread Name ...","Dump core, and then restart component."
"IPv6","3","IPV6_MSG_TO_TLV","TLV Conversion failed (%d)","TLV conversion failed.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IPv6","3","IPV6_MTS_DROP","Error returned from mts_drop(), errno: %s","IPv6 called an MTS API which returned an error.","Dump core, and then restart component."
"IPv6","3","IPV6_MTS_RECV","Error returned from mts_recv(), errno: %s","IPv6 called an MTS API which returned an error.","Dump core, and then restart component."
"IPv6","3","IPV6_MTS_UNKNOWN_MSG","Received unknown MTS message with opcde %d, dropping it","IPv6 received an unknown message. The message is dropped.","No action is required."
"IPv6","3","IPV6_MV_INIT","Couldn't init mutex %s","IPv6 process failed to initialize mutex system resource. Parameters: Thread Name ...","Dump core, and then restart component."
"IPv6","3","IPV6_TLV_TO_STRUCT","TLV to Struct Conversion failed (%d)","TLV to Struct conversion failed.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"IPv6","3","IPV6_TXLIST_CREATE","Couldn't create txlist for %s","IPv6 failed to create txlist resource. Parameters: Data type ...","Dump core, and then restart component."
"IPv6","3","M6RIB_ADD_ROUTE","M6RIB add route failed in %s for VRF %s","IP failed to add route in M6RIB. Parameters: Function Name, Context Name ...","No action is required."
"IPv6","3","MALLOC_FAILED","%s failed in %s","IPv6 process is out of free memory.","No action is required."
"IPv6","3","MALLOC_FAILED_PREFIX","%s failed in %s for %s","IPV6 process is out of free memory.","No action is required."
"IPv6","3","MBUF_FAILED","%s failed in %s (%d bytes)","IPV6 process is out of mbufs.","No action is required."
"IPv6","3","MQ_FAILED","%s failed in %s, errno: %s","IPv6 failed to access message-queue resource.","No action is required."
"IPv6","3","MQ_FAILED_NAME","%s failed in %s for client %s, errno: %s","IPv6 failed to access message-queue resource for the client.","No action is required."
"IPv6","3","MQ_FAILED_PID","%s failed in %s to client pid: %d, errno: %s","IPv6 failed to access message-queue resource for the client.","No action is required."
"IPv6","3","MTS_FAILED","%s failed in %s, errno: %s","IPv6 failed to access mts-queue resource.","No action is required."
"IPv6","3","MTS_FAILED_NAME","%s failed in %s for client %s, errno: %s","IPv6 failed to access mts-queue resource for the client.","No action is required."
"IPv6","3","MTS_FAILED_PID","%s failed in %s to client pid: %d, errno: %s","IPv6 failed to access mts-queue resource for the client.","No action is required."
"IPv6","3","NO_PIB","IPv6 PIB not found for pid: %d/%d","IPv6 could not find client's PIB handle.","No action is required."
"IPv6","3","PID_CONFLICT","Client is using pid: %d/%d with different extended pid: %d","Multiple clients have same process ids.","No action is required."
"IPv6","3","PTHREAD_FAILED","%s failed for %s in %s","IPv6 process failed to create a task thread.","Dump core, then reload the stack."
"IPv6","3","REG_FAILED","Failed to register with IPv6","Component API call failed in IPv6.","No action is required."
"IPv6","3","SYSMGR_DISPATCH","Error returned from sysmgr_dispatch(), errno: %s","IPv6 called the system manager API which returned an error.","Dump core, and then restart component."
"IPv6","3","U6RIB_BAD_IPC","U6RIB corrupted IPC message suspected","IPv6 process received invalid IPC message from U6RIB.","No action is required."
"IPv6","3","UNKNOWN_MTYPE","Unknown mtype: %d/%d opcode %d in %s","IPv6 process received unknown Interprocess message, dropped.","No action is required."
"IPv6","6","IPV6_STATS_ERROR","Failed to get hardware statistics for interface %s, reason %s","IPv6 could not get the requested statistics from the hardware.","No action is required."
"IPv6","6","v6_REG_SEND_MSG","Suppress PIM6 Data Register for (%s, %s) due to suppression-timer\n","Suppress PIM6 Data Register due to suppression-timer. Parameters: Source address, Group address ...","No action is required."
"ISIS","2","AVL_FAIL","Add to CSNP cache failed: %s - %s","An unexpected but recoverable event has occurred. Parameters: Start LSP-ID, End LSP-ID ...","Use the 'restart' command to restart the feature and clear this problem."
"ISIS","2","HOLDDOWN","Failed to enable process after sequence number wrap holddown.","An unexpected but recoverable event has occurred.","Use the 'restart' command to restart the feature and clear this problem."
"ISIS","2","IIB_EXT","%s extension msg for %s (%d) - %s","An unexpected but recoverable event has occurred.","Use the 'restart' command to restart the feature and clear this problem."
"ISIS","2","IM_DEL","Delete msg for %s (%d) iib %p - iib iod %d mismatched","An unexpected but recoverable event has occurred. Parameters: Interface Name, Interface Ordinal, Interface Memory, Interface Memory Ordinal Value ...","Use the 'restart' command to restart the feature and clear this problem."
"ISIS","2","LSP_FREE_DELINK","L%d %s is not on free list","An unexpected but recoverable event has occurred. Parameters: Level, LSP-ID ...","Use the 'restart' command to restart the feature and clear this problem."
"ISIS","2","LSP_FREE_LINK","L%d %s is already on free list","An unexpected but recoverable event has occurred. Parameters: Level, LSP-ID ...","Use the 'restart' command to restart the feature and clear this problem."
"ISIS","2","MCAST_ADD","Failed to add L%d multicast address","Was unable to join to the appropriate multicast group on an interface. Parameters: Level ...","Use the 'restart' command to restart the feature and clear this problem."
"ISIS","2","MEM_ERR","Insufficient memory for %s","Memory is not available for adding SNP entries Parameters: Reason ...","Use the 'restart' command to restart the feature and clear this problem."
"ISIS","2","MQRCVD","%s thread - message queue receive failure <%d>","An unexpected but recoverable event has occurred. Parameters: Thread Name, Error Number ...","Use the 'restart' command to restart the feature and clear this problem."
"ISIS","2","REDIST_PIB_SHM","Failed to attach to redistributing PIB's SHM %s","An unexpected but recoverable event has occurred. Parameters: PIB Name ...","Use the 'restart' command to restart the feature and clear this problem."
"ISIS","2","ROUTE_BUF_OVERFLOW","%s route buffer overflow at entry %lu\n","An unexpected but recoverable event has occurred. Parameters: Address Family, Counter Location ...","Use the 'restart' command to restart the feature and clear this problem."
"ISIS","2","ROUTE_NOTIFY","Route notifications to the RIB are not possible. This will result in stale state in the FIB.","An unexpected but recoverable event has occurred.","Use the 'restart' command to restart the feature and clear this problem."
"ISIS","2","RUNTIME_CLEANUP_FAILURE","Unexpected runtime cleanup failure. Failed to %s","An unexpected software error has occurred while cleaning up a sub-component. Parameters: Reason ...","Use the 'restart' command to restart the feature and clear this problem."
"ISIS","2","RUNTIME_INIT_FAILURE","Unexpected runtime initialization failure. Failed to %s","An unexpected software error has occurred while initializing a sub-component. Parameters: Reason ...","Use the 'restart' command to restart the feature and clear this problem."
"ISIS","2","STARTUP_FAILURE","Startup failure: Failed to %s","An unrecoverable software error has occurred during startup. Parameters: Reason ...","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"ISIS","2","SUM_DIST","sum-addr %s/%d has zero route-dist candidate count","An unexpected but recoverable event has occurred. Parameters: Summary Address Prefix, Summary Address Mask ...","Use the 'restart' command to restart the feature and clear this problem."
"ISIS","2","TLV_MIGRATE","L%d %s still has TLV during migration","An unexpected but recoverable event has occurred. Parameters: Level, LSP-ID ...","Use the 'restart' command to restart the feature and clear this problem."
"ISIS","2","URIB_ADD_RNH_FAILURE","Cannot add RNH to %s","An unexpected but recoverable event has occurred. Parameters: RIB Address Family ...","Use the 'restart' command to restart the feature and clear this problem."
"ISIS","2","URIB_UPDATE","Failed to notify SPF thread about route update buffer availability","An unexpected but recoverable event has occurred.","Use the 'restart' command to restart the feature and clear this problem."
"ISIS","3","AVL_LOOKUP","Can't locate CSNP fragment for %s","SNP cache may get cleaned up during normal operation Parameters: LSP-ID ...","No action is required."
"ISIS","3","BFD_SESSION_REMOVE","Failed to remove BFD session, error %s","The system is unable to remove BFD sessions. Parameters: The system Error ...","No action is required."
"ISIS","3","ISIS_HA_PSS","HA Persistent-store failure for %s %s: %s","A software error has occurred during HA. Stateful HA recovery will be disabled.","No action is required."
"ISIS","3","LSP_REFRESH","Refresh non-self-originated level-%d LSP %s","An unexpected but recoverable event has occurred. Parameters: Level, LSP-ID ...","No action is required."
"ISIS","3","MBUF_COPY","Error 0x%08x copy %hu bytes packet from %s%s","An unexpected but recoverable event has occurred.","No action is required."
"ISIS","3","MCAST_DEL","Failed to remove L%d multicast address","Was unable to leave from the appropriate multicast group on an interface. Parameters: Level ...","No action is required."
"ISIS","3","MTS","Error returned from MTS operation %s, errno: %s","ISIS called an MTS API which returned an error. Parameters: Operation Description, Error Number ...","Dump core, and then restart component."
"ISIS","3","MTS_DROP","Error returned from mts_drop(), errno: %s","ISIS called an MTS API which returned an error. Parameters: Error Number ...","Dump core, and then restart component."
"ISIS","3","MTS_RECV","Error returned from mts_recv(), errno: %s","ISIS called an MTS API which returned an error. Parameters: Error Number ...","Dump core, and then restart component."
"ISIS","3","NO_HELPER_IIB","No helper iib for %s","An unexpected but recoverable event has occurred. Parameters: LSP-ID ...","No action is required."
"ISIS","3","NOTIFY_THREAD","Failed to notify %s thread - Reschedule","An unexpected but recoverable event has occurred. Parameters: Thread Name ...","No action is required."
"ISIS","3","OTV_INFO","Failed to retrieve OTV %s info %s","The system is unable to retrieve OTV information.","No action is required."
"ISIS","3","OTV_SITE_CAP","Failed to add/remove otv site/net-id capability conf check, error %s","The system is unable to add conf check.","No action is required."
"ISIS","3","PIB_UP","Failed to bring up protocol","An unexpected but recoverable event has occurred.","No action is required."
"ISIS","3","PT_ADD","Couldn't add entry to %s PT","ISIS failed to update a local database entry. Parameters: Entry name, Database name ...","No action is required."
"ISIS","3","PT_DEL","Couldn't delete entry for %s from %s PT","ISIS failed to delete an entry from a local database. Parameters: Entry name ...","No action is required."
"ISIS","3","RPM_CALLBACK","RPM Callback handle and/or user data missing","An attempt to obtain RPM Keychain information failed.","No action is required."
"ISIS","3","SELF_LSP_CLEANUP","Cleanup L%d LSP %s with non-null TLV list","An unexpected but recoverable event has occurred. Parameters: Level, LSP-ID ...","No action is required."
"ISIS","3","SLAB_ALLOC","Slab alloc of type %s failed for %s","ISIS process failed to allocate Slab memory. Parameters: Structure Type, Function Name ...","Configure the network or router to decrease the number of routes."
"ISIS","3","SPF_ADJ_DEL","Deleting SPF adj with refcount %lu\n","An unexpected but recoverable event has occurred. Parameters: RefCount ...","No action is required."
"ISIS","3","SWID_UPDATE","Switch-ID table update failed for %s","ISIS process failed to update Switch-ID database. Parameters: The system ID ...","Configure the network or router to decrease the number of routes."
"ISIS","3","UNK_DEB_FLAG","Ignore unrecognized debug flag \%s\","An unexpected but recoverable event has occurred. Parameters: Debug Flag ...","No action is required."
"ISIS","3","UNK_IP_NOTIF","Unrecognized IP address change notification type %lu","An unexpected but recoverable event has occurred. Parameters: IP Notification Type ...","No action is required."
"ISIS","3","UNK_LSP_TIMER","Unrecognized LSP timer type %d for level-%d LSP %s","An unexpected but recoverable event has occurred. Parameters: Timer Type, Level, LSP-ID ...","No action is required."
"ISIS","3","UNK_MSG_MAJOR","%s thread - Unrecognized message major type %d","An unexpected but recoverable event has occurred. Parameters: Thread Name, Message Major Type ...","No action is required."
"ISIS","3","UNK_MSG_MINOR","Unrecognized %s message minor type %d","An unexpected but recoverable event has occurred. Parameters: Component, Message Minor Type ...","No action is required."
"ISIS","3","UNK_MTS_OPC","%s thread - Unrecognized MTS opcode %d","An unexpected but recoverable event has occurred. Parameters: Thread Name, MTS Opcode ...","No action is required."
"ISIS","3","UNK_SYSMGR_NOTIFY","Unexpected registration received from process %u","An unexpected but recoverable event has occurred. Parameters: Base Process UUID ...","No action is required."
"ISIS","3","VLAN_MGR","Error in parsing %s message from VLAN Manager","An unexpected but recoverable event has occurred. Parameters: Message Type ...","No action is required."
"ISIS","3","WEIRD_CACHE","Inconsistent cache %x %s %s","An unexpected but recoverable event has occurred. Parameters: Cache Memory Location, Start LSP-ID, End LSP-ID ...","No action is required."
"ISIS","4","ADD_DEL_URIB_ERR","Failed to %s %lu %s route(s) xid %lu to URIB","IS-IS failed to update route information into URIB Parameters: Add/Delete, Route Count, Route Type, Transaction ID ...","Use the 'restart' command to restart the feature and clear this problem."
"ISIS","4","ADD_UNK_NH_ADDR","Attempt to add for L%d %s/%d on %s with unknown (zero) NH address","IS-IS has detected one or more routers at the same level to have a different set of address families enabled. Parameters: Level, Address Prefix, Mask, Interface Name ...","Configure all IS-IS routers at the same level to have the same address families enabled using the command address-family ip/ipv6 unicast."
"ISIS","4","ADJ_ADVT","Failed to advertise level %d adjacency %s","IS-IS was unable to advertise the indicated adjacency. Parameters: Level,Adjacency ID ...","No action is required."
"ISIS","4","ILLEGAL_PREFIX","Ignore internal L%d route %s/%d with external metric from %s","IS-IS has detected an internal route advertised with external metric, which is an illegal combination, by a router within the network Parameters: Level, Address Prefix, Mask, LSP Id ...","You must correct the remote system that is generating the incorrect information. Either reconfigure the remote system or update the system software to a version that does not originate incorrect information."
"ISIS","4","LAN_DUP_SYSID","L%d LAN IIH - Duplicate system ID %s detected over %s from %s","IS-IS has detected another system on the indicated LAN that is reusing the local system ID Parameters: Level,The system ID, Interface Name, MAC ID ...","Configure either the local or remote router with a different system ID using the command net."
"ISIS","4","LSP_DUP_SYSID","L%d LSP - Possible duplicate system ID %s detected","IS-IS has detected another non-directly connected system that is reusing the local system ID. Parameters: Level,The system ID ...","Configure either the local or remote router with a different system ID using the command net."
"ISIS","4","LSPFULL","L%d %s LSP space is full","There is no storage space left for routing information in the router's LSP Parameters: Level, LSP Type ...","Configure IS-IS so that less information will be distRIButed in the router's LSP, for example by reducing redistributed prefixes."
"ISIS","4","LSPFULL_FAILED_DROP","L%d %s LSP is full and couldn't remove lower priority TLVs to make room for type %d TLV","There is no storage space left for routing information in the router\sLSP,andanattempttodroplowerpriorityinformationhasfailed.'Parameters: Level, LSP Type, TLV Type ...","Configure IS-IS so that less information will be distRIButed in the router's LSP, for example by reducing redistributed prefixes."
"ISIS","4","LSPFULL_FORCED_DROP","L%d %s LSP is full, removed lower priority TLVs to make room for type %d TLV","There was no storage space left for important routing information in the router\sLSP,andsolowerpriorityinformation(e.g.,redistRIButedprefixes)hasbeendroppedtomakeroo m.'Parameters: Level, LSP Type, TLV Type ...","Configure IS-IS so that less information will be distRIButed in the router's LSP, for example by reducing redistributed prefixes."
"ISIS","4","NO_CID","Cannot allocate CID for %s\n - Over 255 LANs limit","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 igored internally until the total count drops below 255. Parameters: Interface Name ...","Disable IS-IS on one or more broadcast interfaces using the command no ip router isis, or convert the interface to point-to-point mode. using the CLI command medium p2p followed by ip router isis."
"ISIS","4","NO_MEM","No memory event detected","An attempt to allocate from free memory failed.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"ISIS","4","P2P_DUP_SYSID","P2P IIH - Duplicate system ID %s detected over %s","IS-IS has detected another system on the indicated P2P that is reusing the local system ID. Parameters: The system ID, Interface Name ...","Configure either the local or remote router with a different system ID using the command net."
"ISIS","4","PROC_NO_MEM","No memory event, shutting down process","Previously an allocation failed due to no available memory. IS-IS will shut down and wait for user to restart it.","Use the 'restart' command to restart the feature and clear this problem."
"ISIS","4","REDIST_MAX_ROUTE","Redistribution route limit has been reached - %d routes","ISIS redistRIBution: Max limit Parameters: Number of routes ...","No action is required."
"ISIS","4","REDIST_THR_ROUTE","Redistribution threshold has been reached - %d routes","ISIS redistRIBution: Threshold limit Parameters: Number of routes ...","No action is required."
"ISIS","4","SEQWRAP","Sequence number wraparound event detected","IS-IS has detected that an LSP's sequence number has wrapped. IS-IS will shut down and restart.","No action is required."
"ISIS","5","ADJCHANGE","%s adj L%s %s over %s - %s on MT-%d","The indicated adjacency has changed its state. Parameters: Interface Type, Level, The system ID, Interface Name, Reason ...","No action is required."
"ISIS","5","NH_DEL","Cleanup L%d route %s/%d has %s next hop","An unexpected but recoverable event has occurred. Parameters: Level, Address Prefix, Mask, Type ...","No action is required."
"ISIS","5","PROC_SEQWRAP","Handle sequence number wraparound - disabling process for %d secs","An LSP's sequence number has wrapped, and the process will be disabled for the correct length of time. Parameters: Time ...","No action is required."
"ISIS","6","JUMBO_PDU","Drop %hu bytes jumbo PDU with %hu bytes buffer from %s%s","IS-IS has received a packet that exceeds the maximum supported size. The packet will be dropped. Parameters: Packet Length,PDU Maximum Size, Interface Name, Source Destination Addr ...","No action is required."
"ISIS","6","MODE_NO_FUNC","No callback function registered for %s in %s mode","IS-IS encountered a problem where no callback function has been registered in the given mode Parameters: Function name, Mode name ...","No action is required."
"ISIS","6","SEQWRAP_HOLDDOWN","Sequence number wraparound holddown timer expired - enable process","The correct amount of time has elapsed after an LSP's sequence number wrapped so that IS-IS can resume normal operation.","No action is required."
"ISIS","6","SHUTDOWN_FAILURE","Shutdown failure. Failed to %s - %s ; Parameters: Reason, Reason Code ...","IS-IS request to system manager for permission to shutdown was declined.","No action is required."
"ISIS","6","START","Process start. Reason - %s","ISIS process start with specified reason Parameters: Reason ...","No action is required."
"ISIS","6","STOP","Process stop. Reason - %s","ISIS procss stop with specified reason Parameters: Reason ...","No action is required."
"ISIS","6","SYSMAN_CLEANUP","Terminated by SYSMAN cleanup signal ;",": IS-IS has been signaled to exit. Explanation    The system has detected an error.","No action is required."
"ISIS","6","UNK_NLPID","Unrecognized NLP ID %02X from %s%s","IS-IS has received a packet with an NLPID which it does not recognize. The packet will be dropped. Parameters: NLP Id, Interface Name, Source Destination Addr ...","No action is required."
"ISIS","6","UNK_PDU","Unrecognized PDU type %d from %s%s","IS-IS has received a packet of a type which it does not recognize. The packet will be dropped. Parameters: PDU Type, Source Addr, Destination Addr ...","No action is required."
"KSINK","3","API_FAILED","%s - failed in %s()","ksink called an API that has failed Parameters: Failed Operation, ksink Function ...","No action is required."
"KSINK","3","API_FAILED_HA","%s - %s:No access to PSS database %p, data file: %s, uri: %s","ksink called an API that has failed Parameters: Failed Operation, ksink Function ...","No action is required."
"KSINK","3","BUF_POOL","Pool 0x%p: double free of 0x%p attempted","Double free of buffer pool.","No action is required."
"KSINK","3","HA_INVALID_INDEX","HA %s sync message received for unknown PSS index %d","HA synchronizationmessage from active SUP references invalid PSS index.","No action is required."
"KSINK","3","INVALID_ARG","invalid arguments - %s - in %s()","Invalid arguments passed in an ksink function Parameters: Invalid Argument, ksink Function ...","No action is required."
"KSINK","3","MEM_ALLOC","Malloc Failure in %s[%d] for size %d","Failed to allocateate memory.","No action is required."
"KSINK","3","MEM_LOCK","mlockall failed, error %s","mmap API returned failure.","No action is required."
"KSINK","3","MTS","Error returned from %s, errno: 0x%08x (%s) in %s()","ksink called an MTS API which returned an error. Parameters: Failed API, Error Code, Error Description, ksink Function ...","No action is required."
"KSINK","3","PSS_CLOSE","Could not close PSS file, %s","PSS API which returned an error.","No action is required."
"KSINK","3","PSS_CREATE","Could not create PSS file %s, %s","PSS API which returned an error.","No action is required."
"KSINK","3","PSS_DELETE","PSS delete failed, %s","PSS API which returned an error.","No action is required."
"KSINK","3","PSS_DELETE_RANGE","PSS delete range failed, %s","PSS API which returned an error.","No action is required."
"KSINK","3","PSS_DESTROY","Could not destroy PSS file %s, %s","PSS API which returned an error.","No action is required."
"KSINK","3","PSS_GETPARAM","Could not retrieve PSS paramaeters, %s","PSS API which returned an error.","No action is required."
"KSINK","3","PSS_HA","%s, %s","PSS API which returned an error.","No action is required."
"KSINK","3","PSS_OPEN","Could not open PSS file %s, %s","PSS API which returned an error.","No action is required."
"KSINK","3","PSS_PURGE","PSS purge failed, %s","PSS API which returned an error.","No action is required."
"KSINK","3","PSS_SET_DBSIZE","Could not set database size %d for PSS file %s, %s","PSS API which returned an error.","No action is required."
"KSINK","3","PSS_SNAPSHOT","PSS snapshot failed for %s, %s","PSS API which returned an error.","No action is required."
"KSINK","3","PSS_UPDATE","PSS update failed, %s","PSS API returned an error.","No action is required."
"KSINK","3","RANDOM_SEED","Failed to set random seed","random seed API returned failure.","No action is required."
"KSINK","3","RRM","Error returned from %s, errno: 0x%08x (%s) in %s()","ksink called an resource manager API which returned an error. Parameters: Failed API, Error Code, Error Description, ksink Function ...","No action is required."
"KSINK","3","SETRLIMIT","Failed to open client shared memory \%s\: %s","The calling process failed with the shown error while trying to open the named U6RIB shared memory region. The status of the memory is shown in 'show process memory shared'. Parameters: Name of shared memory region ...","Use the 'restart' command to restart the feature and clear this problem."
"KSINK","3","TBUCKET","current time: %f , last update: %f","time stamp API returned an error.","No action is required."
"KSINK","6","HA_SEQNO_SYNC","HA sequence number sync to standby failed, %s","HA sequence number synchronizationto standby failed.","No action is required."
"KSINK","6","HA_SYNC","HA sync to standby failed, %s","HA synchronizationmessage to standby failed.","No action is required."
"KSINK","6","HA_UNINITIALIZED","ksink HA library not initialized, %s invoked","Service should provide its own high availability switchover callbacks.","No action is required."
"KSINK","6","MTS_UNK_OPC","Received unknown MTS message on %s queue with opcode %d","URIB received an unknown message. The message is dropped.","No action is required."
"L2F","2","APIINIT","Unable to initialize %s API","As self-explained by the message itself.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"L2F","2","APIREGISTER","Unable to register with %s","As self-explained by the message itself.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"L2F","2","SHMATTACH","Unable to attach to shared memory %s","As self-explained by the message itself.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"L2F","2","SHMCREATE","Unable to create shared memory %s error %d","As self-explained by the message itself.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"L2F","2","SUPERADD","Unable to add super member %s to %s","As self-explained by the message itself.","No action is required."
"L2F","2","THRCREATE","unable to create thread %s: %d","As self-explained by the message itself.","No action is required."
"L2F","3","BADSIG","Should not have received signal %d","As self-explained by the message itself.","No action is required."
"L2F","3","CREATENBR","Couldn't add neighbor %s on %s error %d","As self-explained by the message itself.","No action is required."
"L2F","3","DELETEIF","Could not delete interface on %s error %d","As self-explained by the message itself.","No action is required."
"L2F","3","DISABLEIF","Could not disable interface on %s error %d","As self-explained by the message itself.","No action is required."
"L2F","3","ENABLEIF","Could not enable interface on %s error %d","As self-explained by the message itself.","No action is required."
"L2F","3","ERROR","%s","As self-explained by the message itself.","No action is required."
"L2F","3","GETHOSTNAME","gethostname() failed with errno %d","As self-explained by the message itself.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"L2F","3","IF_CLR_EXT_FAIL","Could not clear interface on %s","As self-explained by the message itself.","No action is required."
"L2F","3","IF_SET_EXT_FAIL","Could not set interface on %s","As self-explained by the message itself.","No action is required."
"L2F","3","INIT","L2F initialization failed %s","As self-explained by the message itself.","No action is required."
"L2F","3","MSGBADMINOR","Unrecognized minor message %d","As self-explained by the message itself.","No action is required."
"L2F","3","MTS_BIND","Error returned from mts_bind() for %s, errno: %s","L2F called an MTS API which returned an error.","Dump core, and then restart component."
"L2F","3","MTS_DROP","Error returned from mts_drop(), errno: %s","L2F called an MTS API which returned an error.","Dump core, and then restart component."
"L2F","3","MTS_RECV","Error returned from mts_recv(), errno: %s","L2F called an MTS API which returned an error.","Dump core, and then restart component."
"L2F","3","MTS_UNKNOWN_MSG","Unknown error returned from MTS, errno: %d","L2F called an MTS API which returned an unknown error.","Dump core, and then restart component."
"L2F","3","NOMEM","malloc (%d) failed for: %s","As self-explained by the message itself.","add more memory to the router."
"L2F","3","RXCHKSUM","Bad checksum packet on interface %s","As self-explained by the message itself.","No action is required."
"L2F","3","RXCOPY","Copy packet error 0x%08x copy %hu bytes packet from %s:%s","As self-explained by the message itself.","No action is required."
"L2F","3","RXJUMBO","Jumbo packet %hu bytes jumbo PDU with %hu bytes buffer from %s:%s","As self-explained by the message itself.","No action is required."
"L2F","3","RXPARSE_BAD_IM_IOD","packets received from invalid interface (possibly just deleted)","As self-explained by the message itself.","No action is required."
"L2F","3","RXPARSE_BAD_L2F","packets received from invalid L2F interface (possibly just deleted)","As self-explained by the message itself.","No action is required."
"L2F","3","RXPARSE_BAD_NBR_TLV","Bad-formed neighbor name TLV","As self-explained by the message itself.","No action is required."
"L2F","3","RXPARSE_BAD_ROUTER_TLV","Bad-formed router name TLV","As self-explained by the message itself.","No action is required."
"L2F","3","RXPARSE_ETHER_ADDR_TLV_LEN","Bad Ethernet Address TLV in packet, len = %d","As self-explained by the message itself.","No action is required."
"L2F","3","RXPARSE_ETHER_ADDR_TLV_NONE","No Ethernet Address TLV in packet","As self-explained by the message itself.","No action is required."
"L2F","3","RXPARSE_NBR_TLV_LEN","Bad Neighbor Name TLV in packet, len = %d","As self-explained by the message itself.","No action is required."
"L2F","3","RXPARSE_NBR_TLV_NULL_TERM","Neighbor Name TLV is not NULL terminated","As self-explained by the message itself.","No action is required."
"L2F","3","RXPARSE_ROUTER_TLV_DUP","Duplicate Router Name TLV in packet","As self-explained by the message itself.","No action is required."
"L2F","3","RXPARSE_ROUTER_TLV_LEN","Bad Router Name TLV in packet, len = %d","As self-explained by the message itself.","No action is required."
"L2F","3","RXPARSE_ROUTER_TLV_NONE","No Router Name TLV in packet","As self-explained by the message itself.","No action is required."
"L2F","3","RXPARSE_ROUTER_TLV_NULL_TERM","Router Name TLV is not NULL terminated","As self-explained by the message itself.","No action is required."
"L2F","3","RXPARSE_ROUTER_TLV_OURS","Misconfigured router, has our name %s","As self-explained by the message itself.","No action is required."
"L2F","3","RXTRUNC","Received truncated packet, expected %hu bytes, got %hu bytes from %s:%s","As self-explained by the message itself.","No action is required."
"L2F","3","SYSMGR_DISPATCH","Error returned from sysmgr_dispatch(), errno: %s","L2F called the system manager API which returned an error.","Dump core, and then restart component."
"L2F","3","TXCOPY","Copy packet error 0x%08x copy %hu bytes","As self-explained by the message itself.","No action is required."
"L2F","3","TXENCAP_FAIL","Encapsulation failed on interface %d","As self-explained by the message itself.","No action is required."
"L2F","3","TXOUTPUT_FAIL","Output failed on interface %d","As self-explained by the message itself.","No action is required."
"L2F","6","BFINIT","Can't initialize plp debugging bits","As self-explained by the message itself.","No action is required."
"L2F","6","INFORMATION","%s","Informational messages as self-explained by the message itself.","No action is required."
"L2F","6","PKTBUFFER","%s","As self-explained by the message itself.","No action is required."
"L3VM","2","STARTUP_FAILURE","Startup failure: failed to %s in %s()","An unrecoverable software error has occurred during l3vm startup. Parameters: Startup Operation, L3vm Function ...","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"L3VM","2","TIB_ID_RAVL","%s failed with table id 0x%08x in %s()","L3vm called an AVL API that has failed Parameters: Failed Operation, Table Id, L3vm Function ...","No action is required."
"L3VM","3","API_FAILED","%s - failed in %s()","L3vm called an API that has failed Parameters: Failed Operation, L3vm Function ...","No action is required."
"L3VM","3","ASSERT_ERROR","%s:%d: Assertion \%s\ failed.","The system has detected an error.Parameters: Filename, Line number, Test ...","No action is required."
"L3VM","3","CLIENT_UNREGISTERED","%s() - Client not registered","Client has not registered its mts queue with l3vm library Parameters: L3vm Function ...","No action is required."
"L3VM","3","CMI_MTSSEND_FAILURE","mts_send() failure for client %s: %s","L3VM was unable to send mts message to a particular client. Parameters: Client name, Error ...","No action is required."
"L3VM","3","CMI_PAYLOAD_CONV_ERR","CMI payload conversion error failure from %s order to %s order","The cmi payload conversion did not occur successfully. Parameters: order, order ...","No action is required."
"L3VM","3","CONFCHECK","confcheck API %s() failed with error: %s(0x%08x).\n","confcheck API failed.","No action is required."
"L3VM","3","CONTEXT","Cannot find %s context in %s()","Cannot find a given context in the system Parameters: L3vm context, L3vm Function ...","No action is required."
"L3VM","3","IM","Error returned from %s, errno: 0x%08x (%s) in %s()","L3VM called a IM API which returned an error. Parameters: Failed API, Error Code, Error Description, L3vm Function ...","No action is required."
"L3VM","3","INVALID_ARG","invalid arguments - %s - in %s()","Invalid arguments passed in an l3vm function Parameters: Invalid Argument, L3vm Function ...","No action is required."
"L3VM","3","LIB_INVALID_ARG","invalid arguments - %s - in %s()","Invalid arguments passed in an l3vm function Parameters: Invalid Argument, L3vm Function ...","No action is required."
"L3VM","3","LIB_NOMEM","Failed to allocate %s in %s()","L3VM library has run out of memory. This can be caused by a general network or router misconfiguration, or the router might not have enough memory installed. Parameters: Allcated Data, L3vm Function ...","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"L3VM","3","LIBAPI_FAILED","%s - failed in %s()","L3vm called an API that has failed Parameters: Failed Operation, L3vm Function ...","No action is required."
"L3VM","3","LIBMTS","Error returned from %s, errno: 0x%08x (%s) in %s()","L3VM library called an MTS API which returned an error. Parameters: Failed API, Error Code, Error Description, L3vm Function ...","No action is required."
"L3VM","3","MTS","Error returned from %s, errno: 0x%08x (%s) in %s()","L3VM called an MTS API which returned an error. Parameters: Failed API, Error Code, Error Description, L3vm Function ...","No action is required."
"L3VM","3","MTS_DROP","Error returned from mts_drop(), error: %s","An MTS API returned an error when L3VM tried to drop a message. Parameters: Error String ...","No action is required."
"L3VM","3","MTS_NO_PAYLOAD_ERROR","Received MTS message with no payload on %s queue with opcode %d, dropping it","L3VM received an unknown message. The message is dropped.","No action is required."
"L3VM","3","NOMEM","Failed to allocate %s in %s()","L3VM has run out of memory. This can be caused by a general network or router misconfiguration, or the router might not have enough memory installed. Parameters: Allcated Data, L3vm Function ...","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"L3VM","3","PENDING_SDB_WRITE","SDB write operation is pending for %s in %s()","L3VM discovered that there is a pending sdb operation Parameters: Pending Key, L3vm Function ...","No action is required."
"L3VM","3","PSS","Error returned from %s, errno: 0x%08x (%s) in %s()","L3VM called a PSS API which returned an error. Parameters: Failed API, Error Code, Error Description, L3vm Function ...","No action is required."
"L3VM","3","RRM","Error returned from %s, errno: 0x%08x (%s) in %s()","L3VM called an resource manager API which returned an error. Parameters: Failed API, Error Code, Error Description, L3vm Function ...","No action is required."
"L3VM","3","SDB","Error returned from %s, errno: 0x%08x (%s) in %s()","L3VM called an SDB API which returned an error. Parameters: Failed API, Error Code, Error Description, L3vm Function ...","No action is required."
"L3VM","3","SDB_OPEN","Error opening %s, errno: 0x%08x (%s) in %s()","L3VM called sdb_open which returned an error. Parameters: Failed URI, Error Code, Error Description, L3vm Function ...","No action is required."
"L3VM","3","SDB_READ","Error reading %s, errno: 0x%08x (%s) in %s()","L3VM called sdb_read which returned an error. Parameters: Failed Key, Error Code, Error Description, L3vm Function ...","No action is required."
"L3VM","3","SYSMGR","Error returned from %s, errno: 0x%08x (%s) in %s()","L3VM called a system manager API which returned an error. Parameters: Failed API, Error Code, Error Description, L3vm Function ...","No action is required."
"L3VM","3","TLVU_API_FAIL","TLVU failure: %s","L3VM process failed in invoking a TLVU API. Parameters: Function ...","No action is required."
"L3VM","3","VDC","Error returned from %s in %s()","L3VM called an VDC API which returned an error. Parameters: Failed API, L3vm Function ...","No action is required."
"L3VM","3","VRF_ERROR","%s: %s","Illegal operation or command on a VRF Parameters: VRF name, Failed Operation ...","No action is required."
"L3VM","4","STATE_MISMATCH","state mismatch - %s - in %s()","L3VM was in an unexpected state Parameters: Name of state, L3vm Function ...","No action is required."
"L3VM","5","UNK_MSG_MINOR","Unrecognized message minor type %d in %s()","L3vm received an unrecognized MTS message format Parameters: Message Minor Type, L3vm Function ...","No action is required."
"L3VM","5","UNK_MTS_EVENT","Unrecognized MTS event for opcode %d in %s()","L3vm received an unexpected event on an MTS message Parameters: MTS opcode, L3vm Function ...","No action is required."
"L3VM","5","UNK_MTS_OPC","Unrecognized MTS opcode %d in %s()","L3vm received an unexpected MTS message opcode Parameters: MTS opcode, L3vm Function ...","No action is required."
"L3VM","6","RESTART_SHUTDOWN","L3VM shutting self down via restart command in %s()","L3VM process is shutting itself down Parameters: L3vm Function ...","No action is required."
"L3VM","6","UNKNOWN_SDB_CTX","L3VM received unknown gsdb context 0x%08x in %s()","L3VM process received ack for unknown operation on global database Parameters: GSDB Context, L3vm Function ...","No action is required."
"LDP","2","INITFAIL","Failure to create/initialize %s","During startup there were problems initializing local resources (data structures, MQ, shared memory).","No action is required."
"LDP","2","REGISTERFAIL","Failure to communicate with other components, error: %s failure","During startup there were problems in establishing communication channels with other components.","No action is required."
"LDP","2","THREADFAIL","Error creating thread %s (error %d)","LDP was unable to spawn a thread. The thread name and the error is printed in the message.","No action is required."
"LDP","3","ALLOCFAIL","Failure to allocate %s (%s)","LDP encountered a memory allocation failure.","No action is required."
"LDP","3","APIFAIL","Failed API call to %s for %s (%s)","An API call of the mentioned component failed. Information about the API call is printed in the syslog message.","No action is required."
"LDP","3","BADARG","Bad argument error: %s","A function call received an unexpected argument.","No action is required."
"LDP","3","BADMSG","BAD IPC message: %s","LDP received a message which has incorrect or unexpected information.","No action is required."
"LDP","3","FECLIST","Error: %s, FEC: %s","Error in adding/removing FEC struction from local data structures.","No action is required."
"LDP","3","FECNHUPD","Unable to add/update FEC Next-Hop information for FEC %s","The system is unable to create downstream label binding data structure (FEC NH).","No action is required."
"LDP","3","HALTPEERS","Unable to allocate memory for operation, shutting down all sessions","LDP is halts all peers when it runs out of memory. This message indicates this no memory condition.","No action is required."
"LDP","3","LISTERR","List Error: %s, operation: %s","LDP encountered an error in its internal list manipulation function.","No action is required."
"LDP","3","MBUFFAIL","MBUF failure: %s","LDP encounted an error while performing MBUF operation.","No action is required."
"LDP","3","MISCERR","Miscellaneous error: %s","These are miscellaneous errors. The message explains it all.","No action is required."
"LDP","3","MQSENDERR","Unable to send message, MQ name: %s","LDP is unable to send an IPC message to the specified message queue.","No action is required."
"LDP","3","MTS_BIND","Error returned from mts_bind(), errno: %s","LDP called an MTS API which returned an error.","Dump core, and then restart component."
"LDP","3","MTS_DROP","Error returned from mts_drop(), errno: %s","LDP called an MTS API which returned an error.","Dump core, and then restart component."
"LDP","3","MTS_RECV","Error returned from mts_recv(), errno: %s","LDP called an MTS API which returned an error.","Dump core, and then restart component."
"LDP","3","MTS_UNKNOWN_MSG","Unknown error returned from MTS, errno: %d","LDP called an MTS API which returned an unknown error.","Dump core, and then restart component."
"LDP","3","PCLERR","PCL error: %s, PCL name: %s","Error in PCL processing, error string indicates the specific error and the PCL name.","No action is required."
"LDP","3","PWEREGFAIL","PWE3 registeration failed: %s","PWE could not talk to LDP, reason specified in message.","No action is required."
"LDP","3","SESSERR","Session Error: %s, session %s","LDP encountered an error when talking with a particular neighbor.","No action is required."
"LDP","3","SESSFECERR","Unable to insert FEC %s from %s to session FEC db","Error in inserting downstream label binding informationin local data structure.","No action is required."
"LDP","3","SESSLIST","Error: %s, Session: %s","Error in adding/removing session structure from local data structures.","No action is required."
"LDP","3","SESSNHERR","Unable to create session next-hop for session %s","Unable creating next hop information given by this neighbor.","No action is required."
"LDP","3","SNMPFILLFAIL","SNMP failure, failed to fill %s in %s request","LDP encounted an error while trying to fill a response to an SNMP query.","No action is required."
"LDP","3","SOCKETERR","Socket Error: %s, Socket: %d, Session: %s, Errno: %d","LDP encountered an error when performing a socket operation.","No action is required."
"LDP","3","SYSMGR_DISPATCH","Error returned from sysmgr_dispatch(), errno: %s","LDP called the system manager API which returned an error.","Dump core, and then restart component."
"LDP","3","UDPLENERR","Wrong UDP length %d","LDP received a corrupt UDP message with a wrong length.","No action is required."
"LDP","3","UNKNOWNMSG","Received unknown IPC message major/minor: %d:%d","LDP received an IPC message which it does not know how to handle. It igores this message.","No action is required."
"LDP","4","DUPLABEL","Neighbor advertised duplicate label for PW FEC %s","LDP received a duplicate label for a FEC from a peer.","No action is required."
"LDP","4","LABELERR","Received label release without label from session %s","LDP received a label release without a label from peer.","No action is required."
"LDP","4","LABELRELERR","Invalid label %ld in label release message for fec %s from %s","LDP received an invalid label from a peer.","No action is required."
"LDP","4","MSGGENFAIL","Unable to format message to %s, error %s","LDP was unable to format a message to a peer.","No action is required."
"LDP","4","SHUTFAIL","Failed to shutdown: %s","An operation failed during shutting down.","No action is required."
"LDP","6","INFORM","%s","Informational message.","No action is required."
"LISP","2","SHM_LOCK_CREAT","Failed to create shared memory lock: %s","The system has failed to initialize.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"LISP","3","API_INIT","Couldn't initialize %s API","LISP failed to open API to interact with the component.","No action is required."
"LISP","3","COMP_DEREG","Unable to de-register with %s","LISP failed to de-register with a server component.","No action is required."
"LISP","3","COMP_REG","Unable to register with %s","LISP failed to register with a server component.","Dump core, and then restart component."
"LISP","3","LIB_API_INIT","Couldn't initialize %s API","LISP failed to open API to interact with the component.","No action is required."
"LISP","3","LISP_INIT","LISP init failed: %s","LISP process initialization failed.","Dump core, and then restart component."
"LISP","3","MALLOC","Private mem malloc (%lu) failed in %s","LISP process is out of free private memory.","Configure the network or router to decrease the number of routes."
"LISP","3","MTS_DROP","Error returned from mts_drop(), errno: %s","LISP called an MTS API which returned an error.","Dump core, and then restart component."
"LISP","3","MTS_RECV","Error returned from mts_recv(), errno: %s","LISP called an MTS API which returned an error.","Dump core, and then restart component."
"LISP","3","MTS_SEND","Error returned from mts_send(), errno: %s","LISP called an MTS API which returned an error.","Dump core, and then restart component."
"LISP","3","NO_SET_PRIORITY","Failed to set policy or priority","LISP process could not set itself process priority, exiting.","No action is required."
"LISP","3","OPCODE_REG","Could not register opcode 0x%x, reason %s","The system is unable to register opcodes Parameters: MTS Opcode, Error string ...","Dump core, and then restart component."
"LISP","3","PT_ADD","Couldn't add %s to Patricia Trie","LISP failed to update Patricia Trie.","No action is required."
"LISP","3","PT_DEL","Couldn't delete %s from Patricia Trie","LISP failed to delete entry from Patricia Trie.","No action is required."
"LISP","3","RLIMIT","Couldn't set LISP data segment size to %lu","LISP process could not set a memory resource limit, exiting.","No action is required."
"LISP","3","SHARED_DB_PUB_INIT","Could not do shared database publisher initialization for interfaces rc=0x%x [%s]","The system is unable to do shared db publisher initialization Parameters: Status Error, Syserror string ...","Dump core, and then restart component."
"LISP","3","SLAB_CREATE","Slab alloc of type %s failed","LISP process failed to allocate Slab memory.","Configure the network or router to decrease the number of routes."
"LISP","3","SM_CLOSE","Couldn't close shm segment %s","LISP process failed to remove shared memory resource.","No action is required."
"LISP","3","SM_CREATE","Couldn't create shm segment %s","LISP process failed to initialize shared memory resource.","Dump core, and then restart component."
"LISP","3","SM_OPEN","Couldn't open shm segment %s","LISP process failed to initialize shared memory resource.","Dump core, and then restart component."
"LISP","3","SMALLOC","Shared mem malloc (%s) failed in %s","LISP process is out of free shared memory.","Configure the network or router to decrease the number of routes."
"LISP","3","SUBCR_INIT","Could not initialize shared database client for interfaces rc=0x%x [%s]","The system is unable to do subscRIBer init to access IM shared-dbs Parameters: Status Error, Syserror string ...","Dump core, and then restart component."
"LISP","3","TIMER_SET_INIT","Couldn't init %s active timer set","LISP failed to initialize timer resource.","Dump core, and then restart component."
"LISP","3","UNKNOWN_MTYPE","Unknown mtype: %d/%d in %s","LISP process received unknown Interprocess message, dropped.","No action is required."
"LISP","6","RESTART_REASON","LISP process has restarted, restart reason: %s\n","LISP is restoring the routes it had added in previous instance.","No action is required."
"LISP","6","SHUTDOWN","Shutting down LISP process","LISP received a shutdown request.","No action is required."
"LISP","6","SHUTDOWN_SELF","LISP shutting self down","LISP process is shutting itself down.","No action is required."
"LISP","6","UFDM_REGACK_FAILED","Received IPC message from UFDM, Register-Ack failed","LISP process received unknown Interprocess message from the UFDM process, dropped.","No action is required."
"LISP","6","UNKNOWN_OPC","Received unknown mts opcode %d","LISP process received unknown Interprocess message, dropped.","No action is required."
"LISP","6","UNKNOWN_OPC_UFDM","Received unknown UFDM mts opcode %d","LISP process received unknown Interprocess message from the UFDM process, dropped.","No action is required."
"M6RIB","2","API_INIT_SEM","Failed to init the client API semaphore: %s, create: %s","M6RIB could not create the semaphore that protects access to the shared memory between M6RIB and its clients. Parameters: Operation, Error from the operation ...","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"M6RIB","2","RES_MGR","Error returned from %s for %d keys, errno: 0x%08x (%s) in %s(). Current reservation is %d, new size is %d","The resource manager returned an error to M6RIB, while M6RIB was performing an action relating to its shared memory Parameters: RM Function, Error Code, Error Description, Calling Function, Reserved resources, Reservation requested resources ...","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"M6RIB","2","STARTUP_FAILURE","Startup failure: %s","An unrecoverable software error has occurred during M6RIB startup.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"M6RIB","3","ACTIVE_TIMER_FAILED","active_timer_create() failed for m6rib_main()","M6RIB process failed to create a timer.","Dump core, then reload the stack."
"M6RIB","3","API_FAILED","%s failed","M6RIB process failed in invoking an API. Parameters: Function ...","No action is required."
"M6RIB","3","BITFIELD_FAILED","%s failed in %s","M6RIB process could not execute the bitfield operation. Parameters: Bitfield Operation, Function Name ...","Dump core, then reload the stack."
"M6RIB","3","CONTEXT_BF_FAILED","bitfield_create() failed for context %s","M6RIB process failed to create a bitfield for m6RIB_ cibtype. Parameters: Context Name ...","Dump core, then reload the stack."
"M6RIB","3","CV_INIT","Couldn't init cond var %s","M6RIB process failed to initialize conditional-variable resource. Parameters: Thread Name ...","Dump core, and then restart component."
"M6RIB","3","FTM_BAD_METER","%s failed for meter %s in %s","M6RIB process failed to configure the multicast meter. Parameters: FTM Operation, Type, Function ...","No action is required."
"M6RIB","3","FTM_BAD_MINOR","Unknown FTM mtype: 0x%4x","M6RIB process received unsupported message type from FTM, igored. Parameters: Minor Type ...","No action is required."
"M6RIB","3","FTM_NO_XID","Cannot find FTM buffer, xid: %d","M6RIB process could not match the sequence number for FTM message, igored. Parameters: Trasaction ID ...","No action is required."
"M6RIB","3","INHERIT_FAILED","m6rib_inherit_oifs(): bitfield is set but oif doesn't exist","M6RIB process failed in inheriting OIFs for the (S,G) from (*,G).","No action is required."
"M6RIB","3","INIT_SDB","%s Return Code: 0x%x Error String: %s","SDB initialization failed Parameters: Message Return Code Error String ...","No action is required."
"M6RIB","3","KSINK_LIB_ERROR","%s %s","A error was encountered during ksink operations. Parameters: Error Description, M6RIB Function ...","No action is required."
"M6RIB","3","LIB_API_FAILED","%s failed in %s","Process failed in invoking an M6RIB API. Parameters: API Call, Function ...","No action is required."
"M6RIB","3","LIB_DUP_REGISTER","m6rib_register(): duplicate register by \%s\","Dupilcate registration request to the M6RIB process, igored. Parameters: PIB Name ...","No action is required."
"M6RIB","3","LIB_MTS_FAILED","%s failed in %s, errno: %s, for %s","Failure in M6RIB library to access mts-queue Parameters: MTS Operation, Function, errorno, MTS Queue ...","No action is required."
"M6RIB","3","LIB_SEM_INVALID","%s:%d: semaphore invalid in %s","M6RIB semaphore was found to be invalid when performing a semaphore operation Parameters: Function Name, Line ...","No action is required."
"M6RIB","3","LIB_SEM_OP","%s:%d: semaphore operation %s failed","Caller failed to perform an operation on the M6RIB semaphore Parameters: Function Name, Line ...","No action is required."
"M6RIB","3","LIB_SM_FAILED","%s failed to access M6RIB shared memory in %s, errno: %s","Process failed to access the The system shared memory resource. Parameters: SM Operation, Function, errorno ...","No action is required."
"M6RIB","3","M6RIB_ALREADY_UP","m6rib already running, exiting","Another M6RIB process is already running, this process will shut down.","No action is required."
"M6RIB","3","MALLOC_FAILED","%s failed for %s","M6RIB process is out of free memory. Parameters: Alloc Routine, Structure Name ...","Configure the network or router to decrease the number of routes."
"M6RIB","3","MFDM_NO_BUF","Cannot find MFDM buffer from route-ack for context %s","M6RIB process could not find a route buffer in its queue from the MFDM message, igored. Parameters: Context Name ...","No action is required."
"M6RIB","3","MQ_FAILED","%s failed in %s, errno: %s, for %s","M6RIB process failed to access the message-queue.","No action is required."
"M6RIB","3","MTS_BIND","Error returned from mts_bind() for %s mts queue, errno: %s","M6RIB called an MTS API which returned an error. Parameters: Queue Name, errno ...","Dump core, and then restart component."
"M6RIB","3","MTS_DROP","Error returned from mts_drop(), errno: %s","M6RIB called an MTS API which returned an error. Parameters: errno ...","Dump core, and then restart component."
"M6RIB","3","MTS_FAILED","%s failed in %s, errno: %s, for %s","M6RIB process failed to access the The system shared memory resource. Parameters: SM Operation, Function, errorno ...","No action is required."
"M6RIB","3","MTS_NO_PAYLOAD_ERROR","Received MTS message with no payload on %s queue with opcode %d, dropping it","M6RIB received an unknown message. The message is dropped.","No action is required."
"M6RIB","3","MTS_RECV","Error returned from mts_recv(), errno: %s","M6RIB called an MTS API which returned an error. Parameters: errno ...","Dump core, and then restart component."
"M6RIB","3","MTS_SHORT_MSG_ERROR","Received short (%d < %d) MTS message on %s queue with opcode %d, dropping it","M6RIB received an unknown message. The message is dropped.","No action is required."
"M6RIB","3","MUTEX_INIT","Couldn't init mutex %s","M6RIB process failed to initialize mutex system resource. Parameters: Thread Name ...","Dump core, and then restart component."
"M6RIB","3","NO_FREE_GROUP","Unable to free group entry for %s in m6rib_delete_route_internal()","M6RIB process unable to delete a route-table entry. Parameters: Group ...","No action is required."
"M6RIB","3","NO_FREE_SOURCE","Unable to free source entry for %s in m6rib_delete_route_internal()","M6RIB process unable to delete a route-table entry. Parameters: Source ...","No action is required."
"M6RIB","3","NO_GROUP","Unable to create group entry for %s","M6RIB process unable to create the route entry in its route-table. Parameters: Group ...","No action is required."
"M6RIB","3","NO_MPIB","Unable to get mpib index in m6rib_register_internal()","M6RIB process cannot register the protocol as it has run out of PIB indices.","Dump core, then reload the stack."
"M6RIB","3","NO_SET_PRIORITY","Failed to set policy or priority","M6RIB process could not set itself process priority, exiting.","No action is required."
"M6RIB","3","NO_SOURCE","Unable to create source entry for %s","M6RIB process unable to create the route entry in its route-table. Parameters: Source ...","No action is required."
"M6RIB","3","NO_TIMER","Could not create stale timer for \%s\","M6RIB process cannot stale the routes for this procotol. Parameters: PIB Name ...","Dump core, then reload the stack."
"M6RIB","3","OPCODE_REGISTER","%s opcode: 0x%x ErrorString: %s","Opcdoe registration failed Parameters: Message Return Code Error String ...","No action is required."
"M6RIB","3","PSS","Error returned from %s, errno: 0x%08x (%s) in %s()","M6RIB called a PSS API which returned an error. The error reported should be examined for the cause. Parameters: Failed API, Error Code, Error Description, M6RIB Function ...","ERRMSG."
"M6RIB","3","PT_FAILED","%s failed in %s","M6RIB process failed to update route-table for this event. Parameters: PT Operation, Function Name ...","Dump core, then reload the stack."
"M6RIB","3","PTHREAD_FAILED","pthread_create() failed for m6rib_main()","M6RIB process failed to create a task thread.","Dump core, then reload the stack."
"M6RIB","3","RDLOCK_ASSERT","%s:%d: Assert, read-lock not acquired","Caller Failed to get M6RIB Shared Memory read lock Parameters: Function Name, Line ...","No action is required."
"M6RIB","3","SYSMGR_DISPATCH","Error returned from sysmgr_dispatch(), errno: %s","M6RIB called the system manager API which returned an error. Parameters: errno ...","Dump core, and then restart component."
"M6RIB","3","TIMER_FAILED","could not %s","M6RIB process failed to configure a timer event. Parameters: Message ...","Dump core, then reload the stack."
"M6RIB","3","UNKNOWN_M6RIB_MAJOR","m6rib_main(): unknown major mtype: %d","M6RIB process received unknown Interprocess message, dropped. Parameters: Major Type ...","No action is required."
"M6RIB","3","UNKNOWN_M6RIB_MINOR","m6rib_main(): unknown minor mtype: %d","M6RIB process received unknown Interprocess message, dropped. Parameters: Minor Type ...","No action is required."
"M6RIB","3","UNKNOWN_MFDM_OPC","m6rib_mfdm_main(): reeceived unknown opcode %d","M6RIB process received unknown Interprocess message from MFDM, dropped. Parameters: Opcode ...","No action is required."
"M6RIB","3","UNKNOWN_U6RIB","Received unknown U6RIB message type: %d","M6RIB process received unknown message from U6RIB, dropped. Parameters: Minor Type ...","No action is required."
"M6RIB","3","WRLOCK_ASSERT","%s:%d: Assert, write-lock not acquired","Caller Failed to get M6RIB Shared Memory write lock Parameters: Function Name, Line ...","No action is required."
"M6RIB","5","API_INIT_SEM_CLEAR","Cleared the API semaphore from %d","The API semaphore was in an unexpected state, and was restored to a correct value. Parameters: Value of semaphore ...","No action is required."
"M6RIB","5","RES_MGR_CHANGE","Changed m4route-mem from %d to %d","The requested limit-resource command was adapted to fit the limits in this version. Parameters: Requested Min, Requested Max, New Min, New Max ...","No action is required."
"M6RIB","6","MEMORY_OPTION","memory size must be >= 16MB and <= 2GB","Invalid memory size specified for M6RIB process.","No action is required."
"M6RIB","6","SHUTDOWN","Shutting down M6RIB process","M6RIB process is shutting itself down.","No action is required."
"M6RIB","6","SHUTDOWN_FAILED","Shutting down of M6RIB process failed: %s","M6RIB process is shutting itself down. Parameters: Error String ...","No action is required."
"M6RIB","6","USAGE","Usage: m6rib [-h] [-d] [-m <memory-in-mb>]","Usage for starting M6RIB process.","No action is required."
"MCASTFWD","2","SHM_LOCK_CREAT","Failed to create shared memory lock: %s","The system has failed to initialize. Parameters: Error Name ...","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"MCASTFWD","2","STARTUP_FAILURE","Startup failure: %s","An unrecoverable software error has occurred during MCASTFWD startup. Parameters: Failure reason ...","No action is required."
"MCASTFWD","3","ALREADY_RUNNING","MCASTFWD already running, exiting","Another MCASTFWD process is already running, this process will shut down.","No action is required."
"MCASTFWD","3","API_FAILED","%s failed in %s","MCASTFWD process failed in invoking an API. Parameters: API name, Function name ...","No action is required."
"MCASTFWD","3","AVL_ERROR","AVL-tree operation %s failed for %s","MCASTFWD process failed in an AVL-tree manipulation. Parameters: AVL tree operation, Tree name ...","No action is required."
"MCASTFWD","3","BAD_MSG","Invalid %s message received from %s","MCASTFWD received an invalid MTS message. Parameters: Message type, Process name ...","Dump core, and then restart component."
"MCASTFWD","3","BF_CREATE","Couldn't create bitfield for %s","MCASTFWD failed to create bitfield resource. Parameters: Data type ...","Dump core, and then restart component."
"MCASTFWD","3","BITFIELD_FAILED","%s failed in %s","MCASTFWD process could not execute the bitfield operation. Parameters: Bitfield operation, Function name ...","Dump core, then reload the stack."
"MCASTFWD","3","CV_INIT","Couldn't init cond var %s","MCASTFWD process failed to initialize conditional-variable resource. Parameters: Thread Name ...","Dump core, and then restart component."
"MCASTFWD","3","GETRLIMIT_FAILED","Address Space size retrieval failed, reason %s","MCASTFWD process could not retrieve memory resource limit.","No action is required."
"MCASTFWD","3","GROUP_PREFIX_IGNORE","Too many Groups in Group Prefix %s. Specify the prefix within /24","GPrefix yiels too many Groups Parameters: Group Prefix ...","No action is required."
"MCASTFWD","3","GROUP_RANGE_IGNORE","Too many Groups in Group Range %s - %s","Group Range yields too many Groups Parameters: Start Group, End Group ...","No action is required."
"MCASTFWD","3","HA_DB_REBUILD","HA run-time database buildup %s","MCASTFWD-SNOOP stateful restart status Parameters: State description ...","No action is required."
"MCASTFWD","3","HA_GROUP","HA %s operation in vlan %d failed for (%s, %s)","MCASTFWD-SNOOP called a PSS API which returned an error. Parameters: Operation type, Vlan-id, Group, Source ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"MCASTFWD","3","HA_OIF","HA %s operation on OIF %s for (%s, %s) in vlan %d failed","MCASTFWD-SNOOP called a PSS API which returned an error. Parameters: Operation type, Interface, Group, Source, Vlan-id ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"MCASTFWD","3","HA_RPORT","HA %s operation on router-port %s for vlan %d failed","MCASTFWD-SNOOP called a PSS API which returned an error. Parameters: Operation type, Interface, Vlan-id ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"MCASTFWD","3","HA_VLAN","HA %s operation for vlan %d failed","MCASTFWD-SNOOP called a PSS API which returned an error. Parameters: Operation type, Vlan-id ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"MCASTFWD","3","IM_API_FAILED","%s failed in %s","IM API failed in MCEC MCASTFWD Snoop. Parameters: API name, Function name ...","No action is required."
"MCASTFWD","3","INVALID_OIF_LIST","MCASTFWD Snooping invalid OIF list %s with %d iods in %s","MCASTFWD-SNOOP has invalid number of iods. Parameters: OIF list, OIF count, Function name ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"MCASTFWD","3","LIB_API_FAILED","%s failed in %s","Process failed in invoking MCASTFWD API. Parameters: API name, Function name ...","No action is required."
"MCASTFWD","3","LIB_API_INIT","Couldn't initialize %s API","MCASTFWD failed to open API to interact with the component. Parameters: Component Name ...","No action is required."
"MCASTFWD","3","LIB_MALLOC","Private mem malloc (%lu) failed in %s","Process is out of free private memory. Parameters: Type of malloc(size), Function Name ...","Configure the network or router to decrease the number of routes."
"MCASTFWD","3","LIB_MTS_FAILED","%s failed in %s, errno: %s","Process failed to access the MCASTFWD MTS-queue. Parameters: MTS IPC operation, Function name, Error ID ...","No action is required."
"MCASTFWD","3","LIB_SM_CLOSE","Couldn't close shm segment %s","MCASTFWD process failed to remove shared memory resource. Parameters: Shared Memory Segment Name ...","No action is required."
"MCASTFWD","3","LIB_SM_OPEN","Couldn't open shm segment %s","MCASTFWD process failed to initialize shared memory resource. Parameters: Shared Memory Segment Name ...","Dump core, and then restart component."
"MCASTFWD","3","LVPORT_CREATE","MCASTFWD Snooping couldn't create an leave-port in %s for group %s","MCASTFWD-SNOOP called an API which returned an error. Parameters: Vlan ID, Group address ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"MCASTFWD","3","MALLOC_FAILED","%s failed in %s","MCASTFWD process is out of free memory. Parameters: Structure type, Function name ...","Configure the network or router to decrease the number of routes."
"MCASTFWD","3","MCASTFWD_INIT","MCASTFWD init failed: %s","MCASTFWD process initialization failed. Parameters: Failure reason ...","Dump core, and then restart component."
"MCASTFWD","3","MFDM_NO_BUF","Cannot find MFDM buffer from route-ack for xid 0x%x","MCASTFWD process could not find a route buffer in its queue from the MFDM message, igored.","No action is required."
"MCASTFWD","3","MFWD_NO_MEM","Failed to allocate private memory for %s","The MCASTFWD process has run out of private memory.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"MCASTFWD","3","MTS_BIND","Error returned from mts_bind() for %s mts-q, errno: %s","MCASTFWD called an MTS API which returned an error. Parameters: MTS Queue name, Error description ...","Dump core, and then restart component."
"MCASTFWD","3","MTS_DROP","Error returned from mts_drop() for %s queue, errno: %s","MCASTFWD called an MTS API which returned an error. Parameters: MTS Queue name, Error description ...","Dump core, and then restart component."
"MCASTFWD","3","MTS_RECV","Error returned from mts_recv() for %s queue, errno: %s","MCASTFWD called an MTS API which returned an error. Parameters: MTS Queue name, Error description ...","Dump core, and then restart component."
"MCASTFWD","3","MTS_SEND","Error returned from mts_send() for %s queue, errno: %s","MCASTFWD called an MTS API which returned an error. Parameters: MTS Queue name, Error description ...","Dump core, and then restart component."
"MCASTFWD","3","MUTEX_INIT","Couldn't init mutex %s","MCASTFWD process failed to initialize mutex system resource. Parameters: Thread Name ...","Dump core, and then restart component."
"MCASTFWD","3","NO_MBUF","Failed to allocate mbuf %s","The MCASTFWD process has run out of network buffers.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"MCASTFWD","3","NO_SET_PRIORITY","Failed to set policy or priority","MCASTFWD process could not set itself process priority, exiting.","No action is required."
"MCASTFWD","3","NO_SH_MEM","Failed to allocate shared memory %s","The MCASTFWD process has run out of shared memory Parameters: Allocation type ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"MCASTFWD","3","NO_SHUTDOWN","Unable to shutdown %s","MCASTFWD process unable to shut itself down. Parameters: Shutdown error information ...","Dump core, and then restart component."
"MCASTFWD","3","PT_ADD","Couldn't add element to PT %s","MCASTFWD failed to update the local snooping-db entry. Parameters: Patricia tree name ...","No action is required."
"MCASTFWD","3","PT_DEL","Couldn't delete element from PT %s","MCASTFWD failed to delete the local snooping-db entry. Parameters: Patricia tree name ...","No action is required."
"MCASTFWD","3","PTHREAD_FAILED","%s failed in %s for thread %s","MCASTFWD process failed to create a task thread. Parameters: Pthread operation, Function name, Thread name ...","Dump core, and then restart component."
"MCASTFWD","3","PULLUP_FAILED","m_pullup() of %d bytes failed in %s","MCASTFWD process failed to process the packet, dropping it. Parameters: Byte count, Function name ...","No action is required."
"MCASTFWD","3","QUERIER_START_FAILED","%s failed in %s","MCASTFWD snoop failed to start the querier. Parameters: Function name, Function name ...","No action is required."
"MCASTFWD","3","RCOUNT_DELETE","Route count delete failed for %s","MCASTFWD called an API which returned an error. Parameters: Interface ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"MCASTFWD","3","RCOUNT_UPDATE","Route count update failed for %s","MCASTFWD called an API which returned an error. Parameters: Interface ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"MCASTFWD","3","RDLOCK_ASSERT","%s:%d: Assert, read-lock not acquired","Caller Failed to get MCASTFWD Shared Memory read lock Parameters: Function Name, Line ...","No action is required."
"MCASTFWD","3","RESERVE_LIMIT","Exceeded reserve-limit for interface %s - dropping","Exceeded the reserve-limit for interface Parameters: Interface ...","No action is required."
"MCASTFWD","3","RESTART_REASON","MCASTFWD process has restarted, restart reason: %s\n","MCASTFWD is restoring the routes it had added in previous instance. Parameters: Restart reason ...","No action is required."
"MCASTFWD","3","RPORT_UPDATE","Router-port update failed for %s (%s)","MCASTFWD-SNOOP called an API which returned an error. Parameters: Interface, Vlan ID ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"MCASTFWD","3","SETRLIMIT_FAILED","Address space size increment of %ld failed, reason %s","MCASTFWD process could not set a memory resource limit Parameters: Number of bytes ...","No action is required."
"MCASTFWD","3","SLAB_CREATE","Slab alloc of type %s failed","MCASTFWD process failed to allocate Slab memory. Parameters: Structure Type ...","Configure the network or router to decrease the number of routes."
"MCASTFWD","3","SMALLOC","Shared mem malloc (%lu) failed in %s","MCASTFWD process is out of free shared memory. Parameters: Type of malloc(size), Function Name ...","Configure the network or router to decrease the number of routes."
"MCASTFWD","3","STATE_LIMIT","Exceeded state-limit for interface %s - dropping","Exceeded the state-limit for interface Parameters: Interface ...","No action is required."
"MCASTFWD","3","SYSMGR_DISPATCH","Error returned from sysmgr_dispatch(), errno: %s","MCASTFWD called the system manager API which returned an error. Parameters: Error description ...","Dump core, and then restart component."
"MCASTFWD","3","TIMER_FAILED","%s failed for %s in %s","MCASTFWD process failed to configure a timer event. Parameters: Timer operation, Timer name, Function name ...","Dump core, and then restart component."
"MCASTFWD","3","TXLIST_CREATE","Couldn't create txlist for %s","MCASTFWD failed to create txlist resource. Parameters: Data type ...","Dump core, and then restart component."
"MCASTFWD","3","UNKNOWN_MTYPE","Unknown mtype: %d/%d in %s with opcode %d","MCASTFWD process received unknown Interprocess message, dropped. Parameters: Major ID, Minor ID, Function name ...","No action is required."
"MCASTFWD","3","VLAN_EXISTS","SNOOP: Couldn't create %s, already esists","MCASTFWD failed to create vlan resource. Parameters: VLAN ID ...","No action is required."
"MCASTFWD","3","vPC_API_FAILED","%s%s","API failed in vPC MCASTFWD snoop module. Parameters: Error message, Error ...","No action is required."
"MCASTFWD","3","vPC_ERROR","%s%s","vPC related messages. Parameters: vPC related message, Error message ...","No action is required."
"MCASTFWD","3","VRF_CREATE","MCASTFWD VRF creation failed for vrf %s","MCASTFWD process could not create the VRF context. Parameters: VRF name ...","Dump core, then reload the stack."
"MCASTFWD","6","AS_LIMIT_INCREASED","Address space size for %s increased %d times","MCASTFWD process incremented AS memory resource limit Parameters: Module name, Increment count ...","No action is required."
"MCASTFWD","6","HA_SEQNO_SYNC","HA sequence number sync to standby failed, %s","MCASTFWD-SNOOP HA sequence number synchronizationto standby failed Parameters: Error description ...","No action is required."
"MCASTFWD","6","HA_STATEFUL","Stateful HA %s","MCASTFWD-SNOOP stateful restart status Parameters: State description ...","No action is required."
"MCASTFWD","6","HA_SYNC","HA sync to standby failed, %s","MCASTFWD-SNOOP HA synchronizationmessage to standby failed Parameters: Error description ...","No action is required."
"MCASTFWD","6","RECEIVE_QUERY","Received %s interface %s from %s","MCASTFWD version mismatch, query still processed. Parameters: MCASTFWD version mismatch, Interface, Source address ...","No action is required."
"MCASTFWD","6","REG_SEND_MSG","Suppress PIM Data Register for (%s, %s) due to suppression-timer\n","Suppress PIM Data Register due to suppression-timer. Parameters: Source address, Group address ...","No action is required."
"MCASTFWD","6","RESERVE_LIMIT_WARNING","Exceeded 80% of the reserve-limit for interface %s","Exceeded 80% of the reserve-limit for interface Parameters: Interface ...","No action is required."
"MCASTFWD","6","RESTART_SHUTDOWN","MCASTFWD shutting self down via restart command","MCASTFWD process is shutting itself down due to the restart command.","No action is required."
"MCASTFWD","6","SHUTDOWN","MCASTFWD shutting self down","MCASTFWD process is shutting itself down.","No action is required."
"MCASTFWD","6","STATE_LIMIT_WARNING","Exceeded 80% of the state-limit for interface %s","Exceeded 80% of the state-limit for interface Parameters: Interface ...","No action is required."
"MCASTFWD","6","UNKNOWN_OPC","Received unknown mts opcode %d","MCASTFWD process received unknown Interprocess message, dropped. Parameters: Operation Code ...","No action is required."
"MRIB","2","API_INIT_SEM","Failed to init the client API semaphore: %s, create: %s","MRIB could not create the semaphore that protects access to the shared memory between MRIB and its clients. Parameters: Operation, Error from the operation ...","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"MRIB","2","RES_MGR","Error returned from %s for %d keys, errno: 0x%08x (%s) in %s(). Current reservation is %d, new size is %d","The resource manager returned an error to MRIB, while MRIB was performing an action relating to its shared memory Parameters: RM Function, Error Code, Error Description, Calling Function, Reserved resources, Reservation requested resources ...","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"MRIB","2","STARTUP_FAILURE","Startup failure: %s","An unrecoverable software error has occurred during MRIB startup.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"MRIB","3","ACTIVE_TIMER_FAILED","active_timer_create() failed for mrib_main()","MRIB process failed to create a timer.","Dump core, then reload the stack."
"MRIB","3","API_FAILED","%s failed","MRIB process failed in invoking an API. Parameters: Function ...","No action is required."
"MRIB","3","BITFIELD_FAILED","%s failed in %s","MRIB process could not execute the bitfield operation. Parameters: Bitfield Operation, Function Name ...","Dump core, then reload the stack."
"MRIB","3","CONTEXT_BF_FAILED","bitfield_create() failed for context %s","MRIB process failed to create a bitfield for mRIB_ cibtype. Parameters: Context Name ...","Dump core, then reload the stack."
"MRIB","3","CV_INIT","Couldn't init cond var %s","MRIB process failed to initialize conditional-variable resource. Parameters: Thread Name ...","Dump core, and then restart component."
"MRIB","3","FTM_BAD_METER","%s failed for meter %s in %s","MRIB process failed to configure the multicast meter. Parameters: FTM Operation, Type, Function ...","No action is required."
"MRIB","3","FTM_BAD_MINOR","Unknown FTM mtype: 0x%4x","MRIB process received unsupported message type from FTM, igored. Parameters: Minor Type ...","No action is required."
"MRIB","3","FTM_NO_XID","Cannot find FTM buffer, xid: %d","MRIB process could not match the sequence number for FTM message, igored. Parameters: Trasaction ID ...","No action is required."
"MRIB","3","INHERIT_FAILED","mrib_inherit_oifs(): bitfield is set but oif doesn't exist","MRIB process failed in inheriting OIFs for the (S,G) from (*,G).","No action is required."
"MRIB","3","INIT_SDB","%s Return Code: 0x%x Error String: %s","SDB initialization failed Parameters: Message Return Code Error String ...","No action is required."
"MRIB","3","INVALID_GROUP","Operation for invalid group %s received in %s","MRIB process received invalid group. Parameters: Group, Function ...","No action is required."
"MRIB","3","KSINK_LIB_ERROR","%s %s","A error was encountered during ksink operations. Parameters: Error Description, MRIB Function ...","No action is required."
"MRIB","3","LIB_API_FAILED","%s failed in %s","Process failed in invoking an API. Parameters: API Call, Function ...","No action is required."
"MRIB","3","LIB_DUP_REGISTER","mrib_register(): duplicate register by \%s\","Dupilcate registration request to the MRIB process, igored. Parameters: PIB Name ...","No action is required."
"MRIB","3","LIB_MTS_FAILED","%s failed in %s, errno: %s, for %s","Failure in MRIB library to access mts-queue Parameters: MTS Operation, Function, errorno, MTS Queue ...","No action is required."
"MRIB","3","LIB_SEM_INVALID","%s:%d: semaphore invalid in %s","MRIB semaphore was found to be invalid when performing a semaphore operation Parameters: Function Name, Line ...","No action is required."
"MRIB","3","LIB_SEM_OP","%s:%d: semaphore operation %s failed","Caller failed to perform an operation on the MRIB semaphore Parameters: Function Name, Line ...","No action is required."
"MRIB","3","LIB_SM_FAILED","%s failed to access MRIB shared memory in %s, errno: %s","Process failed to access the The system shared memory resource. Parameters: SM Operation, Function, errorno ...","No action is required."
"MRIB","3","MALLOC_FAILED","%s failed for %s","MRIB process is out of free memory. Parameters: Alloc Routine, Structure Name ...","Configure the network or router to decrease the number of routes."
"MRIB","3","MDT_API_FAILED","%s failed in %s","MRIB process failed in invoking an API. Parameters: API, Function ...","No action is required."
"MRIB","3","MFDM_NO_BUF","Cannot find MFDM buffer from route-ack for context %s","MRIB process could not find a route buffer in its queue from the MFDM message, igored. Parameters: Context Name, Address of the received buffer ...","No action is required."
"MRIB","3","MQ_FAILED","%s failed in %s, errno: %s, for %s","MRIB process failed to access the The system shared memory resource. Parameters: SM Operation, Function, errorno ...","No action is required."
"MRIB","3","MRIB_ALREADY_UP","mrib already running, exiting","Another MRIB process is already running, this process will shut down.","No action is required."
"MRIB","3","MTS_BIND","Error returned from mts_bind() for %s mts queue, errno: %s","MRIB called an MTS API which returned an error. Parameters: Queue Name, errno ...","Dump core, and then restart component."
"MRIB","3","MTS_DROP","Error returned from mts_drop(), errno: %s","MRIB called an MTS API which returned an error. Parameters: errno ...","Dump core, and then restart component."
"MRIB","3","MTS_NO_PAYLOAD_ERROR","Received MTS message with no payload on %s queue with opcode %d, dropping it","MRIB received an unknown message. The message is dropped.","No action is required."
"MRIB","3","MTS_RECV","Error returned from mts_recv(), errno: %s","MRIB called an MTS API which returned an error. Parameters: errno ...","Dump core, and then restart component."
"MRIB","3","MTS_SHORT_MSG_ERROR","Received short (%d < %d) MTS message on %s queue with opcode %d, dropping it","MRIB received an unknown message. The message is dropped.","No action is required."
"MRIB","3","MUTEX_INIT","Couldn't init mutex %s","MRIB process failed to initialize mutex system resource. Parameters: Thread Name ...","Dump core, and then restart component."
"MRIB","3","NO_FREE_GROUP","Unable to free group entry for %s","MRIB process unable to delete a route-table entry. Parameters: Group ...","No action is required."
"MRIB","3","NO_FREE_SOURCE","Unable to free source entry for %s","MRIB process unable to delete a route-table entry. Parameters: Source ...","No action is required."
"MRIB","3","NO_GROUP","Unable to create group entry for %s","MRIB process unable to create the route entry in its route-table. Parameters: Group ...","No action is required."
"MRIB","3","NO_MARKER","Unable to find the txlist marker for VRF:%s for the client: %s","MRIB failed to find txlist resource. Parameters: VRF name, client name ...","ACTION_SW_KEEP_RUNNING."
"MRIB","3","NO_MPIB","Unable to get mpib index in mrib_register_internal()","MRIB process cannot register the protocol as it has run out of PIB indices.","Dump core, then reload the stack."
"MRIB","3","NO_MPIB_FOR_ROUTE","Unable to creates mpib entry for %s for mpib %s in VRF %s","MRIB process unable to create the route entry in its route-table. Parameters: Address, Protocol Name, VRF Name ...","No action is required."
"MRIB","3","NO_SET_PRIORITY","Failed to set policy or priority","MRIB process could not set itself process priority, exiting.","No action is required."
"MRIB","3","NO_SOURCE","Unable to create source entry for %s","MRIB process unable to create the route entry in its route-table. Parameters: Source ...","No action is required."
"MRIB","3","NO_TIMER","Could not create stale timer for \%s\","MRIB process cannot stale the routes for this procotol. Parameters: PIB Name ...","Dump core, then reload the stack."
"MRIB","3","NOTIFY_BUF_FAILED","Unable to create notification buffer's for client %s, aborting registration.","MRIB failed to create notification buffer for a client Parameters: client name ...","ACTION_SW_KEEP_RUNNING."
"MRIB","3","OPCODE_REGISTER","%s opcode: 0x%x ErrorString: %s","Opcdoe registration failed Parameters: Message Return Code Error String ...","No action is required."
"MRIB","3","PSS","Error returned from %s, errno: 0x%08x (%s) in %s()","MRIB called a PSS API which returned an error. The error reported should be examined for the cause. Parameters: Failed API, Error Code, Error Description, MRIB Function ...","ERRMSG."
"MRIB","3","PT_FAILED","%s failed in %s","MRIB process failed to update route-table for this event. Parameters: PT Operation, Function Name ...","Dump core, then reload the stack."
"MRIB","3","PTHREAD_FAILED","pthread_create() failed for mrib_main()","MRIB process failed to create a task thread.","Dump core, then reload the stack."
"MRIB","3","RDLOCK_ASSERT","%s:%d: Assert, read-lock not acquired","Caller Failed to get MRIB Shared Memory read lock Parameters: Function Name, Line ...","No action is required."
"MRIB","3","SYSMGR_DISPATCH","Error returned from sysmgr_dispatch(), errno: %s","MRIB called the system manager API which returned an error. Parameters: errno ...","Dump core, and then restart component."
"MRIB","3","TIMER_FAILED","could not %s","MRIB process failed to configure a timer event. Parameters: Message ...","Dump core, then reload the stack."
"MRIB","3","TXLIST_CREATE","Couldn't create txlist for %s in VRF:%s","MRIB failed to create txlist resource. Parameters: Data type, The VRF that failure occurred in ...","ACTION_SW_KEEP_RUNNING."
"MRIB","3","UNKNOWN_MFDM_OPC","mrib_mfdm_main(): reeceived unknown opcode %d","MRIB process received unknown Interprocess message from MFDM, dropped. Parameters: Opcode ...","No action is required."
"MRIB","3","UNKNOWN_MRIB_MAJOR","mrib_main(): unknown major mtype: %d","MRIB process received unknown Interprocess message, dropped. Parameters: Major Type ...","No action is required."
"MRIB","3","UNKNOWN_MRIB_MINOR","mrib_main(): unknown minor mtype: %d","MRIB process received unknown Interprocess message, dropped. Parameters: Minor Type ...","No action is required."
"MRIB","3","UNKNOWN_URIB","Received unknown URIB message type: %d","MRIB process received unknown message from URIB, dropped. Parameters: Minor Type ...","No action is required."
"MRIB","3","WRLOCK_ASSERT","%s:%d: Assert, write-lock not acquired","Caller Failed to get MRIB Shared Memory write lock Parameters: Function Name, Line ...","No action is required."
"MRIB","5","API_INIT_SEM_CLEAR","Cleared the API semaphore from %d","The API semaphore was in an unexpected state, and was restored to a correct value. Parameters: Value of semaphore ...","No action is required."
"MRIB","5","RES_MGR_CHANGE","Changed m4route-mem from (%d, %d) to (%d, %d)","The requested limit-resource command was adapted to fit the limits in this version. Parameters: Requested Min, Requested Max, New Min, New Max ...","No action is required."
"MRIB","6","MEMORY_OPTION","memory size must be >= 16MB and <= 2GB","Invalid memory size specified for MRIB process.","No action is required."
"MRIB","6","SHUTDOWN","Shutting down MRIB process","MRIB process is shutting itself down.","No action is required."
"MRIB","6","SHUTDOWN_FAILED","Shutting down of MRIB process failed: %s","MRIB process is shutting itself down. Parameters: Error String ...","No action is required."
"MRIB","6","USAGE","Usage: mrib [-h] [-d] [-m <memory-in-mb>]","Usage for starting MRIB process.","No action is required."
"MSDP","2","NO_ENQUEUE","Unable to enqueue send element for peer %s","MSDP process failed to send a message over the TCP socket to peer. Parameters: Peer IP address ...","No action is required."
"MSDP","2","NO_LISTEN_SOCKET","Fatal error, can't get listen socket setup in %s","MSDP process failed to obtain TCP packet. Parameters: Function name ...","Dump core, and then restart component."
"MSDP","2","OUT_OF_SYNC_TCP_LEN","TCP data stream may be out of sync, suspect TLV length of %d from peer %s","MSDP process received invalid packet length from peer. Parameters: TLV length, Peer IP address ...","No action is required."
"MSDP","2","OUT_OF_SYNC_TCP_TYPE","TCP data stream may be out of sync, suspect TLV type of %d from peer %s","MSDP process received malformed TLV from peer. Parameters: TLV type, Peer IP address ...","No action is required."
"MSDP","2","SEND_QUEUE_CORRUPT","Send queue corrupted for peer %s","The TCP socket send queue is corrupted. Connection to peer will be reset. Parameters: Peer IP address ...","No action is required."
"MSDP","3","ACCEPT","In %s, %s failed with errmsg: %s","MSDP process failed to accept connection. Parameters: Function name, TSP API, Error message ...","No action is required."
"MSDP","3","ALREADY_RUNNING","MSDP already running, exiting - %s","Another MSDP process is already running, this process will shut down. Parameters: Error message ...","No action is required."
"MSDP","3","API_FAILED","%s failed in %s","MSDP process failed in invoking an API. Parameters: API name, Function in which API failed ...","No action is required."
"MSDP","3","AS_NUMBER","MSDP/BGP local AS number is - %s","MSDP process local AS number Parameters: AS number ...","No action is required."
"MSDP","3","CV_INIT","Couldn't init cond var %s","MSDP process failed to initialize conditional-variable resource. Parameters: Thread Name ...","Dump core, and then restart component."
"MSDP","3","FM_ERROR","FM could not shut down MSDP process","MSDP could not process the disable-req from FM.","Dump core, and then restart component."
"MSDP","3","INVALID_TLV","Invalid TLV, type: %d, length: %d from peer %s","MSDP process received an invalid packet. Appropriate error packet returned. Parameters: TLV type, TLV length, Peer IP address ...","No action is required."
"MSDP","3","LIB_MTS_FAILED","%s failed in %s, errno: %s","Process failed to access the MSDP mts-queue. Parameters: MTS function name, Function in which MTS function failed, Error message ...","No action is required."
"MSDP","3","MALLOC_FAILED","%s failed in %s","MSDP process is out of free memory. Parameters: Malloc function, Function in which Malloc failed ...","Configure the network or router to decrease the number of routes."
"MSDP","3","MQ_FAILED","%s failed in %s, errno: %s","MSDP process failed to access the message-queue. Parameters: MQ function name, Function in which MQ function failed, Error message ...","No action is required."
"MSDP","3","MRIB_ROUTE","In %s, %s failed to add mrib route","MSDP process failed to add mRIB routes. Parameters: Function name, mrib_add_route ...","No action is required."
"MSDP","3","MSDP_INIT","MSDP init failed: %s","MSDP process initialization failed. Parameters: Component Name ...","Dump core, and then restart component."
"MSDP","3","MTS_BIND","In %s, %s failed due to %s","MSDP called an MTS API which returned an error. Parameters: Function name,MTS API,Error message ...","Dump core, and then restart component."
"MSDP","3","MTS_DROP","Error returned from mts_drop(), errmsg: %s","MSDP called an MTS API which returned an error. Parameters: Error message ...","Dump core, and then restart component."
"MSDP","3","MTS_FAILED","%s failed in %s, errno: %s","MSDP process failed to access the mts-queue. Parameters: MTS function name, Function in which MTS function failed, Error message ...","No action is required."
"MSDP","3","MTS_RECV","Error returned from mts_recv(), errmsg: %s","MSDP called an MTS API which returned an error. Parameters: Error message ...","Dump core, and then restart component."
"MSDP","3","MUTEX_INIT","Couldn't init mutex %s","MSDP process failed to initialize mutex system resource. Parameters: Thread Name ...","Dump core, and then restart component."
"MSDP","3","NO_SET_PRIORITY","Failed to set policy or priority in %s","MSDP process could not set itself process priority, exiting. Parameters: Function name ...","No action is required."
"MSDP","3","NO_SHUTDOWN","Unable to shutdown msdp_main_thread - %s","MSDP process unable to shut itself down. Parameters: Message ...","Dump core, and then restart component."
"MSDP","3","NOSOURCE","Resetting peer due to VRF change for connect-source %s","The configured interface used for the connect-source has moved to another VRF.","No action is required."
"MSDP","3","PTHREAD_FAILED","%s failed in %s for thread %s","MSDP process failed to create a task thread. Parameters: PTHREAD function name, Function in which PTHREAD function failed, Error message ...","Dump core, and then restart component."
"MSDP","3","RESTART_REASON","MSDP process has restarted, restart reason: %s\n","MSDP is restoring the routes it had added in previous instance. Parameters: Restart reason ...","No action is required."
"MSDP","3","SDB_CLIENT_ERROR","Failed to initialize shared database client with status %x and errmsg: %s\n","MSDP process could not initialize shared database, client. Parameters: Status,Error Message ...","No action is required."
"MSDP","3","SELECT","In %s, %s failed with errmsg: %s","MSDP process failed to select. Parameters: Function name, TSP API, Error message ...","No action is required."
"MSDP","3","SET_SOCKET_OPTIONS","In %s, %s failed for %s","MSDP process failed while setting socket options. Parameters: Function name, API, Socket option ...","No action is required."
"MSDP","3","SETRLIMIT_FAILED","Data segment allocation of %ld failed","MSDP process could not set a memory resource limit, exiting. Parameters: Size ...","No action is required."
"MSDP","3","SETSOCKOPT","In %s, %s failed while setting %s option with errmsg: %s","MSDP process failed while setting tsp socket options. Parameters: Function name, TSP API, Socket option, Error message ...","No action is required."
"MSDP","3","SETUPSOCKET_ERROR","In %s, %s failed to create connection with %s","MSDP process failed to select. Parameters: Function name, TSP API, IP address ...","No action is required."
"MSDP","3","SM_FAILED","%s failed in %s, errno: %s","MSDP process failed to access the The system shared memory resource. Parameters: SM function name, Function in which SM function failed, Error message ...","No action is required."
"MSDP","3","SOCKET_BIND","In %s, %s failed with errmsg %s for %s","MSDP process failed to bind. Parameters: Function name, TSP API, Error message, IP address ...","No action is required."
"MSDP","3","SOCKET_CONNECT","In %s, %s failed to connect %s with context name:%s and errmsg: %s","MSDP process failed to connect to peer. Parameters: Function name, TSP API, Peer IP address, Context name, Error message ...","No action is required."
"MSDP","3","SOCKET_ERROR","In %s, %s failed with errmsg: %s","MSDP process failed to create socket. Parameters: Function name, TSP API, Error message ...","No action is required."
"MSDP","3","SYSMGR_DISPATCH","Error returned from sysmgr_dispatch(), errmsg: %s","MSDP called the system manager API which returned an error. Parameters: Error message ...","Dump core, and then restart component."
"MSDP","3","SYSMGR_INIT","Error in %s while %s","MSDP called a active timer API which returned an error. Parameters: Function name,Cause ...","Dump core, and then restart component."
"MSDP","3","TXLIST_CREATE","Couldn't create txlist for %s in VRF:%s","MSDP failed to create txlist resource. Parameters: Data type, The VRF that failure occurred in ...","Dump core, and then restart component."
"MSDP","3","UNKNOWN_MTYPE","Unknown mtype: %d/%d in %s","MSDP process received unknown Interprocess message, dropped. Parameters: Major type, Minor type, Function name ...","No action is required."
"MSDP","6","RESTART_SHUTDOWN","MSDP shutting self down via restart command","MSDP process is shutting itself down due to the restart command.","No action is required."
"MSDP","6","SHUTDOWN","Shutting down MSDP - %s","MSDP process is shutting itself down. Parameters: Reason for shutdown ...","No action is required."
"MSDP","6","UNKNOWN_OPC","Received unknown mts opcode %d in %s","MSDP process received unknown Interprocess message, dropped. Parameters: MTS opcode, Function name ...","No action is required."
"OSPF","1","INIT","Unable to %s %s","An internal software error occurred. Parameters: Action, Error ...","Use the 'restart' command to restart the feature and clear this problem."
"OSPF","1","LOWMEM","Low memory condition: %s","The router did not have enough memory to store certain data structures. Parameters: Error ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"OSPF","1","MCASTJOIN","Unable to join %s group on interface %s","An internal software error occurred. Parameters: Multicast Group, Interface Id ...","Use the 'restart' command to restart the feature and clear this problem."
"OSPF","1","MCASTLEAVE","Unable to leave %s group on interface %s","An internal software error occurred. Parameters: Multicast Group, Interface Id ...","Use the 'restart' command to restart the feature and clear this problem."
"OSPF","1","MQSEND","Unable to send message %s to %s","An internal software error occurred. Parameters: Message, Destination ...","Use the 'restart' command to restart the feature and clear this problem."
"OSPF","1","NOMEM","Malloc (%ld bytes) failed for: %s","The router did not have enough memory to store mentioned data structures. Parameters: Size, Error ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"OSPF","1","SLABS","Could not create %s slabs","The router did not have enough memory to reserve space in advance for certain slab data structures. Parameters: Slab Type ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"OSPF","1","STARTTHREAD","Unable to start thread %s (%d), error %s","An internal software error occurred. Parameters: Thread name, Thread Id, Error ...","Use the 'restart' command to restart the feature and clear this problem."
"OSPF","1","TAG","Unable to retrieve service tag on %s supervisor","An internal software error occurred. Parameters: Active or Standby Supervisor ...","Use the 'restart' command to restart the feature and clear this problem."
"OSPF","1","TIMER","Unable to create %s timer on interface %s","An internal software error occurred. Parameters: Timer, Interface Id ...","Use the 'restart' command to restart the feature and clear this problem."
"OSPF","2","REDIST_VPN","Received VPN routes without extended community for %s/%d","An internal error Parameters: None ...","No action is required."
"OSPF","3","BFD_SEND_AUTO_EXPIRY","BFD send auto expiry %s","OSPF could not send BFD auto expiry Parameters: Status ...","No action is required."
"OSPF","3","CLI_ALL_CMDS","Timed out waiting for CLI configuration (%s)","OSPF timed out waiting for CLI Server to send all OSPF configs Parameters: Error ...","No action is required."
"OSPF","3","CLI_NON_IF_CMDS","Timed out waiting for router mode CLI configuration (%s)","OSPF timed out waiting for CLI Server to send router mode OSPF configs Parameters: Error ...","No action is required."
"OSPF","3","CMI_ERR","CMI error: %s.","CMI returned an error Parameters: Error ...","No action is required."
"OSPF","3","CMI_NO_VRF_ERR","CMI error: No %s VRF information found","CMI returned an error Parameters: Error ...","No action is required."
"OSPF","3","CTX","Error in subrouter context %s: %s","Error related to multiple subrouters and contexts Parameters: Context, Error ...","No action is required."
"OSPF","3","CTX_IF","Error in subrouter context for interface %s: %s","Error related to interface context Parameters: Interface Id, Error ...","No action is required."
"OSPF","3","HA_AREA","Unable to recreate area %d","OSPF could not do stateful restart Parameters: Area Id ...","No action is required."
"OSPF","3","HA_INTF","Unable to recreate interface %s","OSPF could not do stateful restart Parameters: Interface Id ...","No action is required."
"OSPF","3","HA_INTF_AREA","Unable to add interface %s to area %s","OSPF could not do stateful restart Parameters: Interface Id, Area Id ...","No action is required."
"OSPF","3","HA_LSDB_AREA","Unable to find LSA area %s","OSPF could not do stateful restart Parameters: Area Id ...","No action is required."
"OSPF","3","HA_LSDB_INSTALL","Unable to install LSA %s, area %s %s","OSPF could not do stateful restart Parameters: LSA, Area Id, Interface Id ...","No action is required."
"OSPF","3","HA_LSDB_LINK","Unable to find link LSA interface/area","OSPF could not do stateful restart.","No action is required."
"OSPF","3","HA_LSID","Unable to reserve LSID %d for %s LSA %s","OSPF could not do stateful restart Parameters: LSA type, Interface name ...","No action is required."
"OSPF","3","HA_NBR","Unable to recreate neighbor %s","OSPF could not do stateful restart Parameters: Neighbor Id ...","No action is required."
"OSPF","3","HA_NBR_INTF","Unable to find interface index %ld for neighbor %s","OSPF could not do stateful restart Parameters: Interface Index, Neighbor Id ...","No action is required."
"OSPF","3","HA_NO_SR","Unable to find sr %d","OSPF could not do stateful restart Parameters: Subrouter Id ...","No action is required."
"OSPF","3","HA_SR","Unable to recreate sr %d","OSPF could not do stateful restart Parameters: Subrouter Id ...","No action is required."
"OSPF","3","HEAPSIZE","Error increasing heap size to %d, error %d","Reduced heap size will limit the LSDB size. Parameters: Size, Error ...","No action is required."
"OSPF","3","IF_INVALID","Unable to find interface %s","OSPF could not find an interface Parameters: Interface name ...","No action is required."
"OSPF","3","INVALID_TLV","Found corrupted TLV, LSA %s","Error while parsing TLV. Parameters: LSA ...","No action is required."
"OSPF","3","ISSU_GR_DISABLED","Aborting ISSU, GR is disabled in %d out of %d contexts Parameters: Contexts, Contexts ...","ISSU requires OSPF GR to be enabled for all contexts.","No action is required."
"OSPF","3","ISSU_GR_FAILED","Aborting ISSU, GR failed in %d out of %d contexts Parameters: Contexts, Contexts ...","ISSU requires successful OSPF GR in all contexts.","No action is required."
"OSPF","3","ISSU_GR_IN_HELPER_MODE","Aborting ISSU, OSPF in GR helper mode in %d contexts Parameters: Contexts ...","ISSU requires stable OSPF topology in all contexts.","No action is required."
"OSPF","3","ISSU_GR_IN_PROGRESS","Aborting ISSU, GR in progress in %d out of %d contexts Parameters: Contexts, Contexts ...","ISSU requires stable OSPF topology in all contexts.","No action is required."
"OSPF","3","MAXIFS","Exceeded the limit on interfaces per area [i.e %d]","Restricting the number of interfaces per area to avoid problems during lsa generation. Parameters: Interface Limit ...","Reduce the number of interfaces per area."
"OSPF","3","MAXLSAS","Maximum number of LSAs in domain has been reached","The OSPF domain contains more LSAs than this router can store.","Redesign the network to redistRIBute less external routes into the OSPF domain."
"OSPF","3","MIB_FAIL","Failed to %s the MIB","Error while loading or unloading the MIB. Parameters: action ...","No action is required."
"OSPF","3","MTS_BIND","Error returned from mts_bind(), errno: %s","OSPF called an MTS API which returned an error. Parameters: Error ...","No action is required."
"OSPF","3","MTS_DROP","Error returned from mts_drop(), errno: %s","OSPF called an MTS API which returned an error. Parameters: Error ...","No action is required."
"OSPF","3","MTS_NOTIFY","Error returned from mts_send_notify(), errno: %s","OSPF called an MTS API which returned an error. Parameters: Error ...","No action is required."
"OSPF","3","MTS_RECV","Error returned from tsp_mts_recv(), errno: %s","OSPF called an MTS API which returned an error. Parameters: Error ...","No action is required."
"OSPF","3","PSS_AREA","PSS %s for area %ld failed","OSPF called a PSS API which returned an error. Parameters: Action, Area Id ...","No action is required."
"OSPF","3","PSS_GLOBAL","PSS %s for global data failed","OSPF called a PSS API which returned an error. Parameters: Action ...","No action is required."
"OSPF","3","PSS_INTF","PSS %s for interface %s failed","OSPF called a PSS API which returned an error. Parameters: Action, Interface Id ...","No action is required."
"OSPF","3","PSS_LSDB","PSS %s for LSA %s failed","OSPF called a PSS API which returned an error. Parameters: Action, LSA ...","No action is required."
"OSPF","3","PSS_NBR","PSS %s for neighbor %s failed","OSPF called a PSS API which returned an error. Parameters: Action, Neighbor Id ...","No action is required."
"OSPF","3","PSS_READ","PSS read for %s information failed","The system has detected an error.Parameters: Data ... ; Explanation: OSPF called a PSS API which returned an error.","No action is required."
"OSPF","3","PSS_SR","PSS %s for sr %ld failed","OSPF called a PSS API which returned an error. Parameters: Action, Subrouter Id ...","No action is required."
"OSPF","3","ROUTEDEL","Route deletion %s/%d failed","Internal Error. Parameters: Prefix, Length ...","No action is required."
"OSPF","3","SMALLBUF","%s packet doesn't fit in buffer (packet %d/ buffer %d)","The router has allocated a packet buffer that was too small. Parameters: Packet Type, Packet Size, Buffer Size ...","No action is required."
"OSPF","3","TLV_INTF","Failed to convert to %s for %s","OSPF called an TLV intf which returned an error. Parameters: Action, Data ...","No action is required."
"OSPF","3","UNAWAKABLE","Trying to awake unawakable thread %s","Thread cannot be wokenup at this time Parameters: Thread Name ...","No action is required."
"OSPF","3","UNKNOWNSIG","Received unknown signal: %d","An unexpected software interruption was received. Parameters: Signal ...","No action is required."
"OSPF","4","AF_NO_FUNC","Function %s not supported by OSPF version %s","Function is not specified for the current address family Parameters: Function Name, OSPF Version ...","No action is required."
"OSPF","4","AREA_ERR","Packet from %s on %s received for wrong area %s","A OSPF packet not belonging to this area was received Parameters: Source IP address, Interface name, Area ID ...","No action is required."
"OSPF","4","AUTH_ERR","Received packet from %s on %s with bad authentication %hx","A OSPF packet with mismatched authentication type was received Parameters: Source IP address, Interface name, Type ...","No action is required."
"OSPF","4","CKSM_ERR","Bad OSPF checksum in packet %hx computed %hx from %s on %s","A OSPF packet with invalid checksum was received Parameters: Checksum value, Checksum value, Source IP address, Interface name ...","No action is required."
"OSPF","4","CLEANUP","OSPF is exiting, reason %s(0x%x) ; Parameters: Reason string, Reason no. ...","OSPF has been deconfigured or restarted.","No action is required."
"OSPF","4","DEST_INVALID","Bad destination address %s","A OSPFv3 packet with muticast source address was received Parameters: Source IP address ...","No action is required."
"OSPF","4","DUPRID","Router %s on interface %s is using our routerid, packet dropped","Two routers are configured with the same router ID. Parameters: Router Id, Interface Id ...","Check all routers on the indicated interface for misconfigurations."
"OSPF","4","IF_ERR","Packet from %s received on %s interface %s","A OSPF packet not belonging to this interface was received Parameters: Source IP address, reason, Interface ...","No action is required."
"OSPF","4","INVALIDOUT","Trying to send packet with packettype %d to %s on %s","The router tried to send unknown OSPF packet. Parameters: Packet Type, Destination, Interface Id ...","No action is required."
"OSPF","4","NEIGH_ERR","Neighbor %s not found, packet dropped","A non-hello OSPF packet with no neighbor was received Parameters: Source IP address ...","No action is required."
"OSPF","4","PKTLEN_ERR","Packet received from %s on %s has length %d which is less than %s %d","A OSPF packet with invalid length was received Parameters: Source IP address, Interface name, Packet length, Type, Header length ...","No action is required."
"OSPF","4","PKTTYPE_ERR","Unknown type %d received from %s on %s","A OSPF packet with incorrect packet type was received Parameters: Packet type, Source IP address, Interface name ...","No action is required."
"OSPF","4","REDIST_MAX_PFX","Redistribution prefix limit has been reached - %d prefixes","Check if redistRIBution of large number of prefixes is desired and has not been configured by mistake Parameters: Number of prefixes ...","No action is required."
"OSPF","4","REDIST_THR_PFX","Redistribution prefix threshold has been reached - %d prefixes","Check if redistRIBution of large number of prefixes is desired and has not been configured by mistake Parameters: Number of prefixes ...","No action is required."
"OSPF","4","RESTART_SHUTDOWN","OSPF shutting self down via restart command","OSPF process is shutting itself down due to the restart command.","No action is required."
"OSPF","4","SELF_LSA","context %s: %s","Router received a 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. Parameters: Context, Message ...","Verify if the router ID for the router is unique in the network."
"OSPF","4","SOURCE_ERR","Bad source address %s - ours on %s","A OSPF packet with our own source address was received Parameters: IP address, Interface name ...","No action is required."
"OSPF","4","SRC_INVALID","Invalid src address %s, should not be seen on %s","A OSPF packet packet with source address not on this network was received Parameters: Source IP address, Interface name ...","No action is required."
"OSPF","4","SRC_MCAST","Bad source address %s - multicast on %s","A OSPFv3 packet with muticast source address was received Parameters: Source IP address ...","No action is required."
"OSPF","4","VERSION_ERR","Bad ospf version %d received from %s on %s","A OSPF packet with incorrect version number was received Parameters: Version number, Source IP address, Interface name ...","No action is required."
"OSPF","4","WRONGQ","Found wrong type of packet (%d) on internal %s queue","Did not expect the specified packet type on the given incoming message queue Parameters: Packet Type, Queue ...","No action is required."
"OSPF","5","ADJCHANGE","Nbr %s on %s went %s","An OSPF neighborship has just been established. Or a neighborship has just been shutdown. Parameters: Neighbor Id, Interface Id, New State ...","No action is required."
"OSPF","5","BFD_DOWN","BFD state Down for %s on %s (area %s) BFD code %d","The system has detected an error.Parameters: Neighbor Id, Interface Id, Area Id, BFD code ... Explanation: OSPF received BFD down notification.","No action is required."
"OSPF","5","NBRSTATE","Process %s, Nbr %s on %s from %s to %s, %s","The system has detected an error.Parameters: Process tag, Neighbor Id, Interface Id, Old State, New State, Event ... Explanation: An OSPF neighbor has just changed its state.","No action is required."
"OSPF","6","DECONFIG_SHUTDOWN","OSPF shutting self down via deconfiguration","OSPF process is shutting itself down due to the deconfiguration command.","No action is required."
"OSPF","6","HA_DB_REBUILD","HA run-time database buildup %s","OSPF stateful restart status Parameters: Action ...","No action is required."
"OSPF","6","HA_STATEFUL","Stateful HA %s","OSPF stateful restart status Parameters: Action ...","No action is required."
"OSPF","6","MTS_UNKNOWN_MSG","Received unknown MTS message with opcode %d, dropping it","OSPF received an unknown MTS message. The message will be dropped Parameters: MTS Opcode ...","No action is required."
"OSPF","6","SHUTDOWN_REQUEST_FAIL","OSPF shutdown request failed, %s","OSPF request to system mananger for permission to shutdown was turned down. Parameters: Error ...","No action is required."
"OSPF","6","START","Starting OSPF %s, %s","OSPF process is starting due to the specified reason. Parameters: Process name, Reason ...","No action is required."
"OSPF","6","UNKNOWN_SHUTDOWN","OSPF shutting self down due to unknown reason","OSPF process is shutting itself down due to unknown reason.","No action is required."
"PCL","2","MALLOC_FAILED","malloc() failed for allocating %s in %s()","PCL process is out of heap memory.","No action is required."
"PCL","2","SLAB_ALLOC_FAILED","slab_calloc() failed for allocating %s in %s()","PCL process is out of heap memory.","No action is required."
"PCL","2","SMALLOC_FAILED","smalloc() failed for allocating %s in %s()","PCL process is out of shared memory. This could be due to temporary increase in the number of policies configured to a very high value.","No action is required."
"PCL","3","API_FAILED","%s - failed in %s()","An unexpected but manageable event has occurred.;.","No action is required."
"PCL","3","API_FAILED_NUM","%s - failed for %d in %s()","An unexpected but manageable event has occurred.;.","No action is required."
"PCL","3","API_FAILED_NUM_NUM","%s - failed for %d %d in %s()","An unexpected but manageable event has occurred.;.","No action is required."
"PCL","3","API_FAILED_STR","%s - failed for %s in %s()","An unexpected but manageable event has occurred.;.","No action is required."
"PCL","3","API_FAILED_STR_NUM","%s - failed for %s %d in %s()","An unexpected but manageable event has occurred.;.","No action is required."
"PCL","3","API_FAILED_STR_STR","%s - failed for %s %s in %s()","An unexpected but manageable event has occurred.;.","No action is required."
"PCL","3","MQ_FAILED","%s failed, errno: %s in %s()","An unexpected but manageable event has occurred.;.","No action is required."
"PCL","3","MQ_FAILED_NAME","%s failed for client %s, errno: %s in %s()","An unexpected but manageable event has occurred.;.","No action is required."
"PCL","3","MQ_FAILED_PID","%s failed to client pid: %d, errno: %s in %s()","An unexpected but manageable event has occurred.;.","No action is required."
"PCL","3","MTS_DROP","Error returned from mts_drop(), errno: %s","PCL called an MTS API which returned an error.","No action is required."
"PCL","3","MTS_RECV","Error returned from tsp_mts_recv(), errno: %s","PCL called an MTS API which returned an error.","No action is required."
"PCL","3","WORK_THREAD_FAILIURE","%s failed for policy %s %s to client %s count %d in %s()","PCL work thread item failed after repeated attempts. This could be either due to too many policies configured or some of PCL client's message queues are full.","No action is required."
"PCL","6","MTS_UNKNOWN_MSG","Received unknown MTS message with opcde %d, dropping it","PCL received an unknown message. The message is dropped.","No action is required."
"PCL","6","PKT_LOG","%s","Packet header logging by access-rules.","No action is required."
"PCL","7","DEBUG","%s","PCL Debug information.","No action is required."
"PIM","2","SHM_LOCK_CREAT","Failed to create shared memory lock: %s","The system has failed to initialize. Parameters: Error Name ...","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"PIM","2","STARTUP_DEBUG","%s in %s","The system has failed to initialize. Parameters: Error, Function Name ...","No action is required."
"PIM","3","ADD_ROUTE","Couldn't add PIM route %s in %s","PIM failed to update the local route-table entry. Parameters: Addresses, Function Name ...","No action is required."
"PIM","3","API_CLOSE","Couldn't close %s API","PIM failed to close API opened with the component. Parameters: Component Name ...","No action is required."
"PIM","3","API_FAILED","%s failed in %s","PIM process failed in invoking an API. Parameters: Function Name ...","No action is required."
"PIM","3","API_INIT","Couldn't initialize %s API","PIM failed to open API to interact with the component. Parameters: Component Name ...","No action is required."
"PIM","3","ATTACH_SHM","Couldn't attach to shm of %s","PIM process failed to open a shared memory resource. Parameters: Shared Memory Segment Name ...","Dump core, and then restart component."
"PIM","3","AVL_ERROR","AVL-tree operation %s failed for %s","PIM process failed in an AVL-tree manipulation. Parameters: AVL tree operation, Tree name ...","No action is required."
"PIM","3","BF_CONVERT","bitfield_convert() failed","PIM failed to convert a compressed bitfield.","Dump core, and then restart component."
"PIM","3","BF_CREATE","Couldn't create %s bitfield","PIM failed to create bitfield resource. Parameters: List Name ...","Dump core, and then restart component."
"PIM","3","BFD_ADD_FAIL","%s request for interface %s failed in %s",": BFD session add failed Explanation    The system has detected an error.Parameters: API name, Interface name, Function name ...","Dump core, and then restart component."
"PIM","3","BFD_API_FAIL","%s request failed in %s",": BFD API failed Explanation    The system has detected an error.Parameters: API name, Function name ...","Dump core, and then restart component."
"PIM","3","BFD_SEND_AUTO_EXPIRY","Unable to start BFD staling, error %s","PIM BFD staling API failed Parameters: Error string ...","Dump core, and then restart component."
"PIM","3","BFD_SES_REMOVE_ALL","Unable to cleanup the BFD sessions during deconfiguration, error %s","The system is unable to cleanup BFD sessions Parameters: Error string ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"PIM","3","BIND","bind() on %s failed: %s","PIM failed to bind UDP socket. Auto-RP will not work. Parameters: Function Error String ...","Dump core, and then restart component."
"PIM","3","COMP_DEREG","Unable to de-register with %s","PIM failed to de-register with a server component. Parameters: Component Name ...","No action is required."
"PIM","3","COMP_REG","Unable to register with %s","PIM failed to register with a server component. Parameters: Component Name ...","Dump core, and then restart component."
"PIM","3","CONFCHECK","Failed to %s Tunnel multicast concheck Capability. error: %s","Could not add/delete confcheck capability Parameters: Operation, Error ...","No action is required."
"PIM","3","CREATE_ROUTE","Couldn't create PIM route for %s in %s","PIM failed to update the local route-table entry. Parameters: Addresses, Function Name ...","No action is required."
"PIM","3","CV_INIT","Couldn't init cond var %s","PIM process failed to initialize conditional-variable resource. Parameters: Thread Name ...","Dump core, and then restart component."
"PIM","3","DEL_IF","Couldn't delete interface %s from PIM route %s in %s ;",": PIM failed to delete the outgoing interface from route-table entry. Explanation    The system has detected an error.Parameters: Interface, Addresses, Function Name ...","No action is required."
"PIM","3","DEL_ROUTE","Couldn't delete PIM route %s in %s","PIM failed to delete the local route-table entry. Parameters: Addresses, Function Name ...","No action is required."
"PIM","3","FREE_ROUTE","Couldn't free PIM route %s in %s","PIM failed to delete the route-table entry. Parameters: Addresses, Function Name ...","No action is required."
"PIM","3","GET_RP_FAIL","%s: %s for group %s","PIM API for getting RP address failed Parameters: Function Name, reason, group address ...","No action is required."
"PIM","3","HEARTBEAT_TIMER","Unable to create heartbeat timer in %s","The system is unable to create heartbeat timer Parameters: Function Name ...","Dump core, and then restart component."
"PIM","3","IGMP_DOWN","Couldn't enable PIM on %s, IGMP is not up","PIM is not enabled on the interface, as it requires IGMP to be up. Parameters: Interface ...","No action is required."
"PIM","3","IM_EXT","Couldn't set IM-extension for interface %s","PIM process failed to set IM extension. Parameters: Interface ...","Dump core, and then restart component."
"PIM","3","INIT_MTS_SAP","mts_bind() failed in pim_init_mts(), errno: %s","The system is unable to open MTS SAP Parameters: Error String ...","Dump core, and then restart component."
"PIM","3","LIB_API_FAILED","%s failed in %s","PIM client failed in invoking an API. Parameters: Function Name ...","No action is required."
"PIM","3","LIB_API_INIT","Couldn't initialize %s API","PIM failed to open API to interact with the component. Parameters: Component Name ...","No action is required."
"PIM","3","LIB_MALLOC","Private mem malloc (%lu) failed in %s","Process is out of free private memory. Parameters: Type of malloc(size), Function Name ...","Configure the network or router to decrease the number of routes."
"PIM","3","LIB_MTS_SEND","mts_send() failed for %s, errno: %s","Process called an MTS API which returned an error. Parameters: Error String ...","Dump core, and then restart component."
"PIM","3","LIB_SM_CLOSE","Couldn't close shm segment %s","PIM process failed to remove shared memory resource. Parameters: Shared Memory Segment Name ...","No action is required."
"PIM","3","LIB_SM_OPEN","Couldn't open shm segment %s","PIM process failed to initialize shared memory resource. Parameters: Shared Memory Segment Name ...","Dump core, and then restart component."
"PIM","3","MALLOC","Private mem malloc (%lu) failed in %s","PIM process is out of free private memory. Parameters: Type of malloc(size), Function Name ...","Configure the network or router to decrease the number of routes."
"PIM","3","MCEC_MSG","%s","PIM VPC related messages Parameters: String ...","Dump core, and then restart component."
"PIM","3","MQCLOSE","Couldn't close %s mq: %s","PIM failed to close the message-queue resource.","No action is required."
"PIM","3","MQFLUSH","Couldn't flush %s mq: %s","PIM failed to remove stale messages from the message-queue.","No action is required."
"PIM","3","MQLOOP_CREATE","Couldn't create %s mqloop: %s","PIM failed to create the mqloop resource. Parameters: MSG Queue Name, Error String ...","Dump core, and then restart component."
"PIM","3","MQLOOP_REGHAND","Couldn't register all handlers for %s mqloop","PIM failed to initialize handlers the mqloop resource. Parameters: MSG Queue Name ...","Dump core, and then restart component."
"PIM","3","MQLOOP_SHUTDOWN","Couldn't shutdown %s mqloop","PIM failed to shutdown the mqloop resource. Parameters: MSG Queue Name ...","No action is required."
"PIM","3","MQLOOP_START","Couldn't start %s mqloop","PIM failed to initialize the mqloop resource. Parameters: MSG Queue Name, Error String ...","Dump core, and then restart component."
"PIM","3","MQOPEN","Couldn't open %s mq: %s","PIM failed to open the message-queue resource. Parameters: Component, Function Name ...","Dump core, and then restart component."
"PIM","3","MQSEND","mq_send() error on %s queue in %s","PIM failed to send an IPC message on the message-queue. Parameters: Component, Function Name ...","No action is required."
"PIM","3","MRIB_ADD_ROUTE","MRIB add route failed in %s","PIM failed to add route in MRIB. Parameters: Function Name ...","No action is required."
"PIM","3","MRIB_DEL_ROUTE","MRIB delete route failed in %s","PIM failed to delete route in MRIB. Parameters: Function Name ...","No action is required."
"PIM","3","MRIB_NO_SHARED_TREE","MRIB shared tree entry absent for group %s/%d","MRIB route unexpectedly absent for a group entry. Parameters: Group address Group mask length ...","No action is required."
"PIM","3","MSDP_ORIG_DATASA","Couldn't originate MSDP data SA in %s","PIM failed to notify MSDP to originate data SA message. Parameters: Function Name ...","No action is required."
"PIM","3","MTS_DROP","Error returned from mts_drop(), errno: %s","PIM called an MTS API which returned an error. Parameters: Error String ...","Dump core, and then restart component."
"PIM","3","MTS_INIT","Could not initialize MTS for %s","The system is unable to register opcodes Parameters: Service / Queue description ...","Dump core, and then restart component."
"PIM","3","MTS_RECV","Error returned from mts_recv(), errno: %s","PIM called an MTS API which returned an error. Parameters: Error String ...","Dump core, and then restart component."
"PIM","3","MTS_REGISTER","mts_register failed for PIM: %s","PIM was unable to register an MTS notification.","No action is required."
"PIM","3","MTS_SEND","mts_send() failed for %s, errno: %s","PIM called an MTS API which returned an error. Parameters: Error String ...","Dump core, and then restart component."
"PIM","3","MTS_UNBIND","mts_unbind() failed in %s for queue %s with err: %s","mts_unbind failure Parameters: Function name, Queue name, Error String ...","Dump core, and then restart component."
"PIM","3","MTSOPEN","Couldn't bind %s mts-q: %s","PIM failed to open the MTS-queue resource. Parameters: MSG Queue Name, Error String ...","Dump core, and then restart component."
"PIM","3","MUTEX_INIT","Couldn't init mutex %s","PIM process failed to initialize mutex system resource. Parameters: Thread Name ...","Dump core, and then restart component."
"PIM","3","MV_INIT","Couldn't init mutex %s","PIM process failed to initialize mutex system resource. Parameters: Data type ...","Dump core, and then restart component."
"PIM","3","NO_SET_PRIORITY","Failed to set policy or priority","PIM process could not set itself process priority, exiting.","No action is required."
"PIM","3","OIM_REGISTER_FAIL","Unable to register with OIM module in %s",": MVPN module couldnt register with OIM module Explanation    The system has detected an error.Parameters: API name, Function name ...","Dump core, and then restart component."
"PIM","3","OPCODE_REG","Could not register opcode 0x%x, reason %s","The system is unable to register opcodes Parameters: MTS Opcode, Error string ...","Dump core, and then restart component."
"PIM","3","PIM_API_NOT_INIT","PIM API not initialized","PIM API is not initialized.","No action is required."
"PIM","3","PIM_CIB","Couldn't find PIM VRF for %s","PIM failed to obtain its VRF information block. Parameters: Interface ...","Dump core, and then restart component."
"PIM","3","PIM_EXISTS","PIM is already running, process exiting","Another PIM process is already running, this process will shut down.","No action is required."
"PIM","3","PIM_INIT","PIM init failed: %s","PIM process initialization failed. Parameters: Component Name ...","Dump core, and then restart component."
"PIM","3","POLICY_INVALID_BINDACK","Invalid RPM bind ack in %s","PIM received invalid policy response from RPM.","No action is required."
"PIM","3","POLICY_INVALID_TYPE","Invalid RPM type %d in %s","PIM received invalid policy-type from RPM.","No action is required."
"PIM","3","PSS_FAILED","PSS operation %s failed","PIM process failed in a PSS operation. Parameters: Operation Name ...","No action is required."
"PIM","3","PT_ADD","Couldn't add %s to local PT","PIM failed to update the local route-table entry. Parameters: Addresses ...","No action is required."
"PIM","3","PT_DEL","Couldn't delete %s from local PT","PIM failed to delete the local route-table entry. Parameters: Address ...","No action is required."
"PIM","3","PTHREAD_CREATE","Couldn't create thread %s","PIM process failed to create a task thread. Parameters: Thread Name ...","Dump core, and then restart component."
"PIM","3","RDLOCK_ASSERT","%s:%d: Assert, read-lock not acquired","Caller Failed to get PIM Shared Memory read lock Parameters: Function Name, Line ...","No action is required."
"PIM","3","RESERVE_LIMIT","Exceeded reserve-limit for VRF %s - dropping","Exceeded the reserve-limit for VRF Parameters: VRF ...","No action is required."
"PIM","3","RESTART_REASON","PIM process has restarted, restart reason: %s\n","PIM is restoring the routes it had added in previous instance. Parameters: Restart Reason ...","No action is required."
"PIM","3","RLIMIT","Couldn't set PIM data segment size to %lu","PIM process could not set a memory resource limit, exiting. Parameters: Segment Size ...","No action is required."
"PIM","3","ROUTE_LOOKUP","Couldn't find PIM route %s","PIM failed to find entry in the local route-table. Parameters: Address ...","No action is required."
"PIM","3","SETSOCKOPT","setsockopt() on %s failed: %s","PIM failed in UDP socket operation. Auto-RP will not work. Parameters: Message String Error String ...","Dump core, and then restart component."
"PIM","3","SETUP_ROUTE","Couldn't setup PIM route %s in %s","PIM failed to install route in the local route-table. Parameters: Address, Function Name ...","No action is required."
"PIM","3","SG_EXP_TMR_VRF","\ip pim sg-expiry-timer\ value in VRF %s not supported in %s, please reconfigure within range %d-%d","Configuration not supported in ISSU target version, please reconfigure Parameters: VRF name, lower bound, upper bound ...","ACTION_SW_NONE."
"PIM","3","SG_EXP_TMR_VRFS","\ip pim sg-expiry-timer\ value in %d VRFs not supported in %s, please reconfigure within range %d-%d","Configuration not supported in ISSU target version, please reconfigure Parameters: VRF count, lower bound, upper bound ...","ACTION_SW_NONE."
"PIM","3","SHARED_DB_PUB_INIT","Could not do shared database publisher initialization for interfaces rc=0x%x [%s]","The system is unable to do shared db publisher initialization Parameters: Status Error, Syserror string ...","Dump core, and then restart component."
"PIM","3","SHUTDOWN_FM","FM could not shut down PIM process","FM could not shut down PIM process.","Dump core, and then restart component."
"PIM","3","SLAB_ALLOC","Slab alloc of type %s failed in %s","PIM process failed to allocate Slab memory. Parameters: Structure Type, Function Name ...","Configure the network or router to decrease the number of routes."
"PIM","3","SLAB_CREATE","Slab alloc of type %s failed","PIM process failed to allocate Slab memory. Parameters: Structure Type ...","Configure the network or router to decrease the number of routes."
"PIM","3","SM_CREATE","Couldn't create shm segment %s","PIM process failed to initialize shared memory resource. Parameters: Shared Memory Segment Name ...","Dump core, and then restart component."
"PIM","3","SMALLOC","Shared mem malloc (%lu) failed in %s","PIM process is out of free shared memory. Parameters: Type of malloc(size), Function Name ...","Configure the network or router to decrease the number of routes."
"PIM","3","SOCKET","socket() for %s failed: %s","PIM failed to obtain UDP socket. Auto-RP will not work. Parameters: Function Error String ...","Dump core, and then restart component."
"PIM","3","STATE_LIMIT","Exceeded state-limit for VRF %s - dropping","Exceeded the state-limit for VRF Parameters: VRF ...","No action is required."
"PIM","3","SUBCR_INIT","Could not initialize shared database client for interfaces rc=0x%x [%s]","The system is unable to do subscRIBer init to access IM shared-dbs Parameters: Status Error, Syserror string ...","Dump core, and then restart component."
"PIM","3","SYSMGR_DISPATCH","Error returned from sysmgr_dispatch(), errno: %s","PIM called the system manager API which returned an error.","Dump core, and then restart component."
"PIM","3","THREAD_SHUTDOWN","Couldn't shutdown thread %s","PIM failed to shut down a task thread. Parameters: Thread Name ...","No action is required."
"PIM","3","TIMER_CREATE","Couldn't create %s timer for %s","PIM failed to initialize timer resource. Parameters: Timer Name, Timer description ...","Dump core, and then restart component."
"PIM","3","TIMER_SET_INIT","Couldn't init %s active timer set","PIM failed to initialize timer resource. Parameters: Timer Name ...","Dump core, and then restart component."
"PIM","3","TIMER_START","Couldn't start %s timer","PIM failed to initialize timer resource. Parameters: Timer Name ...","Dump core, and then restart component."
"PIM","3","TUNNEL_ADD_TLV_FAIL","Unable to add tunnel tlv %s into the list for vrf %s",": MVPN tunnel setup failed Explanation    The system has detected an error.Parameters: Tlv Type, VRF name ...","Dump core, and then restart component."
"PIM","3","TUNNEL_CREATE_FAIL","Unable to setup tunnel interface for vrf %s failed in %s",": MVPN tunnel setup failed Explanation    The system has detected an error.Parameters: VRF name, Function name ...","Dump core, and then restart component."
"PIM","3","TXLIST_CREATE","Couldn't create txlist for %s","PIM failed to create txlist resource. Parameters: Data type ...","Dump core, and then restart component."
"PIM","3","UDP_READ","Error reading UDP socket","UDP Socket Error.","Dump core, and then restart component."
"PIM","3","UDP_SENDTO","udp_sendto() on %s failed: %s","PIM failed to send over UDP socket. Parameters: Message String Error String ...","No action is required."
"PIM","3","URIB_CONTEXT","Couldn't get URIB VRF %s","PIM failed to obtain unicast routing VRF from URIB.","Dump core, and then restart component."
"PIM","3","WRLOCK_ASSERT","%s:%d: Assert, write-lock not acquired","Caller Failed to get PIM Shared Memory write lock Parameters: Function Name, Line ...","No action is required."
"PIM","4","DUP_VPC_NBR","Unexpected 2nd vPC peer %s detected (peer %s) on %s (domain %d misconfig?)","The system is unable to register opcodes Parameters: Service / Queue description ...","Dump core, and then restart component."
"PIM","4","HELLO_INT","Configured PIM hello interval %d on interface %s is less than the supported minimum value of %d, updating the interval to minimum value\n","PIM minimum hello interval. Parameters: Hello interval, Interface, Min Hello interval ...","No action is required."
"PIM","5","DR_CHANGE","DR change from %s to %s on interface %s","PIM Designated router changed on the interface. Parameters: Old DR address, New DR address, Interface ...","No action is required."
"PIM","5","NBR_CHANGE","Neighbor %s %s on interface %s","PIM neighbor went up/down due to Hello-message seen/lost. Parameters: Neighbor IP address, Neighbor state, Interface ...","No action is required."
"PIM","6","IF_DEPEND","Removed interface (%s) has %s dependency","There is residual configuration on the deleted interface. Parameters: Interface name, Dependent Config Command ...","No action is required."
"PIM","6","MAX_GRANGES","Max Granges allowed to be configured for use shared tree config is %d","Exceeded the group range limit.","No action is required."
"PIM","6","MAX_RPS","Cannot store bidir-RP %s, a maximum of %d are supported","Due to hardware limitations, there is a maximum number of Bidir-PIM RPs that can be stored.","No action is required."
"PIM","6","MQFLUSHED","Flushing %lu messages from %s mq","Flushing old residual messages fom the message-queue.","No action is required."
"PIM","6","MQLOOP_UNKNOWN_MSG","Received unknown message %d/%d","PIM process received unknown Interprocess message, dropped.","No action is required."
"PIM","6","NEGATIVE_PREFIX","Group prefix %s/%d from RP %s has negative-bit set, ignore group entry","The RP is advertising a group range to be in dense-mode. This implementation only supports sparse-mode so the group entry will be igored. Parameters: Group Address, Mask length, RP Address ...","No action is required."
"PIM","6","RESERVE_LIMIT_WARNING","Exceeded 80% of the reserve-limit for VRF %s","Exceeded 80% of the reserve-limit for VRF Parameters: VRF ...","No action is required."
"PIM","6","RESTART_SHUTDOWN","PIM shutting self down via restart command","PIM process is shutting itself down due to the restart command.","No action is required."
"PIM","6","SHUTDOWN","Shutting down PIM process","PIM received a shutdown request.","No action is required."
"PIM","6","SHUTDOWN_SELF","PIM shutting self down","PIM process is shutting itself down.","No action is required."
"PIM","6","STATE_LIMIT_WARNING","Exceeded 80% of the state-limit for VRF %s","Exceeded 80% of the state-limit for VRF Parameters: VRF ...","No action is required."
"PIM","6","UNKNOWN_OPC","Received unknown mts opcode %d","PIM process received unknown Interprocess message, dropped. Parameters: MTS Opcode ...","No action is required."
"PIM6","2","SHM_LOCK_CREAT","Failed to create shared memory lock: %s","The system has failed to initialize. Parameters: Error Name ...","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"PIM6","2","STARTUP_DEBUG","%s in %s","The system has failed to initialize. Parameters: Error, Function Name ...","No action is required."
"PIM6","3","ADD_ROUTE","Couldn't add PIM6 route %s in %s","PIM6 failed to update the local route-table entry. Parameters: Addresses, Function Name ...","No action is required."
"PIM6","3","API_CLOSE","Couldn't close %s API","PIM6 failed to close API opened with the component. Parameters: Component Name ...","No action is required."
"PIM6","3","API_FAILED","%s API failed in %s","API call failed in PIM6.","No action is required."
"PIM6","3","API_INIT","Couldn't initialize %s API","PIM6 failed to open API to interact with the component. Parameters: Component Name ...","No action is required."
"PIM6","3","ATTACH_SHM","Couldn't attach to shm of %s","PIM6 process failed to open a shared memory resource. Parameters: Shared Memory Segment Name ...","Dump core, and then restart component."
"PIM6","3","BF_CONVERT","bitfield_convert() failed","PIM6 failed to convert a compressed bitfield. Parameters: Function Name ...","Dump core, and then restart component."
"PIM6","3","BF_CREATE","Couldn't create %s bitfield","PIM6 failed to create bitfield resource. Parameters: List Name ...","Dump core, and then restart component."
"PIM6","3","BIND","bind() on %s failed: %s","PIM6 failed to bind UDP socket. Auto-RP will not work. Parameters: Function Error String ...","Dump core, and then restart component."
"PIM6","3","COMP_DEREG","Unable to de-register with %s","PIM6 failed to de-register with a server component. Parameters: Component Name ...","No action is required."
"PIM6","3","COMP_REG","Unable to register with %s","PIM6 failed to register with a server component. Parameters: Component Name ...","Dump core, and then restart component."
"PIM6","3","CREATE_ROUTE","Couldn't create PIM6 route for %s in %s","PIM6 failed to update the local route-table entry. Parameters: Addresses, Function Name ...","No action is required."
"PIM6","3","CV_INIT","Couldn't init cond var %s","PIM6 process failed to initialize conditional-variable resource. Parameters: Thread Name ...","Dump core, and then restart component."
"PIM6","3","DEL_IF","Couldn't delete interface %s from PIM6 route %s in %s","PIM6 failed to delete the outgoing interface from route-table entry. Parameters: Interface, Addresses, Function Name ...","No action is required."
"PIM6","3","DEL_ROUTE","Couldn't delete PIM6 route %s in %s","PIM6 failed to delete the local route-table entry. Parameters: Addresses, Function Name ...","No action is required."
"PIM6","3","FREE_ROUTE","Couldn't free PIM6 route %s in %s","PIM6 failed to delete the route-table entry. Parameters: Addresses, Function Name ...","No action is required."
"PIM6","3","HEARTBEAT_TIMER","Unable to create heartbeat timer in %s","The system is unable to create heartbeat timer Parameters: Function Name ...","Dump core, and then restart component."
"PIM6","3","INIT_MTS_SAP","mts_bind() failed in pim_init_mts(), errno: %s","The system is unable to open MTS SAP Parameters: Error String ...","Dump core, and then restart component."
"PIM6","3","INVALID_MBUF","Received invalid mbuf pointer in %s","PIM6 received invalid data buffer, discarded.","No action is required."
"PIM6","3","LIB_API_FAILED","%s API failed in %s","API call failed in PIM6 library.","No action is required."
"PIM6","3","LIB_API_INIT","Couldn't initialize %s API","PIM6 failed to open API to interact with the component. Parameters: Component Name ...","No action is required."
"PIM6","3","LIB_MALLOC","Private mem malloc (%lu) failed in %s","Process is out of free private memory. Parameters: Type of malloc(size), Function Name ...","Configure the network or router to decrease the number of routes."
"PIM6","3","LIB_SM_CLOSE","Couldn't close shm segment %s","PIM6 process failed to remove shared memory resource. Parameters: Shared Memory Segment Name ...","No action is required."
"PIM6","3","LIB_SM_OPEN","Couldn't open shm segment %s","PIM6 process failed to initialize shared memory resource. Parameters: Shared Memory Segment Name ...","Dump core, and then restart component."
"PIM6","3","M6RIB_ADD_ROUTE","M6RIB add route failed in %s","PIM6 failed to add route in MRIB. Parameters: Function Name ...","No action is required."
"PIM6","3","M6RIB_DEL_ROUTE","M6RIB delete route failed in %s","PIM6 failed to delete route in MRIB. Parameters: Function Name ...","No action is required."
"PIM6","3","M6RIB_NO_SHARED_TREE","M6RIB shared tree entry absent for group %s/%d","M6RIB route unexpectedly absent for a group entry. Parameters: Group address Group mask length ...","No action is required."
"PIM6","3","MALLOC","Private mem malloc (%lu) failed in %s","PIM6 process is out of free private memory.","Configure the network or router to decrease the number of routes."
"PIM6","3","MQCLOSE","Couldn't close %s mq: %s","PIM6 failed to close the message-queue resource. Parameters: MSG Queue Name, Error String ...","No action is required."
"PIM6","3","MQFLUSH","Couldn't flush %s mq: %s","PIM6 failed to remove stale messages from the message-queue.","No action is required."
"PIM6","3","MQLOOP_CREATE","Couldn't create %s mqloop: %s","PIM6 failed to create the mqloop resource.","Dump core, and then restart component."
"PIM6","3","MQLOOP_REGHAND","Couldn't register all handlers for %s mqloop","PIM6 failed to initialize handlers the mqloop resource. Parameters: MSG Queue Name ...","Dump core, and then restart component."
"PIM6","3","MQLOOP_SHUTDOWN","Couldn't shutdown %s mqloop","PIM6 failed to shutdown the mqloop resource. Parameters: MSG Queue Name ...","No action is required."
"PIM6","3","MQLOOP_START","Couldn't start %s mqloop","PIM6 failed to initialize the mqloop resource. Parameters: MSG Queue Name, Error String ...","Dump core, and then restart component."
"PIM6","3","MQOPEN","Couldn't open %s mq: %s","PIM6 failed to open the message-queue resource. Parameters: Component, Function Name ...","Dump core, and then restart component."
"PIM6","3","MQSEND","mq_send() error on %s queue in %s","PIM6 failed to send an IPC message on the message-queue. Parameters: Component, Function Name ...","No action is required."
"PIM6","3","MTS_DROP","Error returned from mts_drop(), errno: %s","PIM6 called an MTS API which returned an error. Parameters: Error String ...","Dump core, and then restart component."
"PIM6","3","MTS_INIT","Could not initialize MTS for %s","The system is unable to register opcodes Parameters: Service / Queue description ...","Dump core, and then restart component."
"PIM6","3","MTS_RECV","Error returned from mts_recv(), errno: %s","PIM6 called an MTS API which returned an error. Parameters: Error String ...","Dump core, and then restart component."
"PIM6","3","MTSOPEN","Couldn't open %s mts-q: %s","PIM6 failed to open the MTS-queue resource. Parameters: MSG Queue Name, Error String ...","Dump core, and then restart component."
"PIM6","3","MUTEX_INIT","Couldn't init mutex %s","PIM6 process failed to initialize mutex system resource. Parameters: Thread Name ...","Dump core, and then restart component."
"PIM6","3","NO_SET_PRIORITY","Failed to set policy or priority","PIM6 process could not set itself process priority, exiting.","No action is required."
"PIM6","3","OPCODE_REG","Could not register opcode 0x%x, reason %s","The system is unable to register opcodes Parameters: MTS Opcode, Error string ...","Dump core, and then restart component."
"PIM6","3","PIM6_API_NOT_INIT","PIM6 API not initialized","PIM6 API is not initialized. Parameters: Thread Name ...","No action is required."
"PIM6","3","PIM6_CIB","Couldn't find PIM6 VRF for %s","PIM6 failed to obtain its VRF information block.","Dump core, and then restart component."
"PIM6","3","PIM6_EXISTS","PIM6 is already running, process exiting","Another PIM6 process is already running, this process will shut down.","No action is required."
"PIM6","3","PIM6_INIT","PIM6 init failed: %s","PIM6 process initialization failed. Parameters: Component Name ...","Dump core, and then restart component."
"PIM6","3","POLICY_INVALID_BINDACK","Invalid RPM bind ack in %s","PIM6 received invalid policy response from RPM.","No action is required."
"PIM6","3","POLICY_INVALID_TYPE","Invalid RPML type %d in %s","PIM6 received invalid policy-type from RPM.","No action is required."
"PIM6","3","PSS_FAILED","PSS operation %s failed","PIM6 process failed in a PSS operation. Parameters: Operation Name ...","No action is required."
"PIM6","3","PT_ADD","Couldn't add %s to local PT","PIM6 failed to update the local route-table entry. Parameters: Addresses ...","No action is required."
"PIM6","3","PT_DEL","Couldn't delete %s from local PT","PIM6 failed to delete the local route-table entry. Parameters: Address ...","No action is required."
"PIM6","3","PTHREAD_CREATE","Couldn't create thread %s","PIM6 process failed to create a task thread. Parameters: Thread Name ...","Dump core, and then restart component."
"PIM6","3","RDLOCK_ASSERT","%s:%d: Assert, read-lock not acquired","Caller Failed to get PIM6 Shared Memory read lock Parameters: Function Name, Line ...","No action is required."
"PIM6","3","RESERVE_LIMIT","Exceeded reserve-limit for VRF %s - dropping","Exceeded the reserve-limit for VRF Parameters: VRF ...","No action is required."
"PIM6","3","RESTART_REASON","PIM6 process has restarted, restart reason: %s\n","PIM6 is restoring the routes it had added in previous instance. Parameters: Restart Reason ...","No action is required."
"PIM6","3","RLIMIT","Couldn't set PIM6 data segment size to %lu","PIM6 process could not set a memory resource limit, exiting. Parameters: Segment Size ...","No action is required."
"PIM6","3","ROUTE_LOOKUP","Couldn't find PIM6 route %s","PIM6 failed to find entry in the local route-table. Parameters: Address ...","No action is required."
"PIM6","3","SETSOCKOPT","setsockopt() on %s failed: %s","PIM6 failed in UDP socket operation. Auto-RP will not work. Parameters: Message String Error String ...","Dump core, and then restart component."
"PIM6","3","SETUP_ROUTE","Couldn't setup PIM6 route %s in %s","PIM6 failed to install route in the local route-table. Parameters: Addresses, Function Name ...","No action is required."
"PIM6","3","SHARED_DB_PUB_INIT","Could not do shared database publisher initialization for interfaces rc=0x%x [%s]","The system is unable to do shared db publisher initialization Parameters: Status Error, Syserror string ...","Dump core, and then restart component."
"PIM6","3","SHUTDOWN_FM","FM could not shut down PIM6 process","FM could not shut down PIM6 process.","Dump core, and then restart component."
"PIM6","3","SLAB_ALLOC","Slab alloc of type %s failed in %s","PIM6 process failed to allocate Slab memory.","Configure the network or router to decrease the number of routes."
"PIM6","3","SLAB_CREATE","Slab alloc of type %s failed","PIM6 process failed to allocate Slab memory.","Configure the network or router to decrease the number of routes."
"PIM6","3","SM_CREATE","Couldn't create shm segment %s","PIM6 process failed to initialize shared memory resource. Parameters: Shared Memory Segment Name ...","Dump core, and then restart component."
"PIM6","3","SMALLOC","Shared mem malloc (%lu) failed in %s","PIM6 process is out of free shared memory.","Configure the network or router to decrease the number of routes."
"PIM6","3","SOCKET","socket() for %s failed: %s","PIM6 failed to obtain UDP socket. Auto-RP will not work. Parameters: Function Error String ...","Dump core, and then restart component."
"PIM6","3","STATE_LIMIT","Exceeded state-limit for VRF %s - dropping","Exceeded the state-limit for VRF Parameters: VRF ...","No action is required."
"PIM6","3","SUBCR_INIT","Could not initialize shared database client for interfaces rc=0x%x [%s]","The system is unable to do subscRIBer init to access IM shared-dbs Parameters: Status Error, Syserror string ...","Dump core, and then restart component."
"PIM6","3","SYSMGR_DISPATCH","Error returned from sysmgr_dispatch(), errno: %s","PIM6 called the system manager API which returned an error.","Dump core, and then restart component."
"PIM6","3","THREAD_SHUTDOWN","Couldn't shutdown thread %s","PIM6 failed to shut down a task thread.","No action is required."
"PIM6","3","TIMER_CREATE","Couldn't create %s timer","PIM6 failed to initialize timer resource. Parameters: Timer Name ...","Dump core, and then restart component."
"PIM6","3","TIMER_SET_INIT","Couldn't init %s active timer set","PIM6 failed to initialize timer resource. Parameters: Timer Name ...","Dump core, and then restart component."
"PIM6","3","TIMER_START","Couldn't start %s timer","PIM6 failed to initialize timer resource. Parameters: Timer Name ...","Dump core, and then restart component."
"PIM6","3","U6RIB_CONTEXT","Couldn't get U6RIB VRF %s","PIM6 failed to obtain unicast routing VRF from URIB. Parameters: Interface ...","Dump core, and then restart component."
"PIM6","3","UDP_READ","Error reading UDP socket","UDP Socket Error.","Dump core, and then restart component."
"PIM6","3","UDP_SENDTO","udp_sendto() on %s failed: %s","PIM6 failed to send over UDP socket. Parameters: Message String Error String ...","No action is required."
"PIM6","3","WRLOCK_ASSERT","%s:%d: Assert, write-lock not acquired","Caller Failed to get PIM6 Shared Memory write lock Parameters: Function Name, Line ...","No action is required."
"PIM6","4","HELLO_INT","Configured PIM hello interval %d on interface %s is less than the supported minimum value of %d, updating the interval to minimum value\n","PIM minimum hello interval. Parameters: Hello interval, Interface, Min Hello interval ...","No action is required."
"PIM6","5","DR_CHANGE","DR change from %s to %s on interface %s","PIM Designated router changed on the interface. Parameters: Old DR address, New DR address, Interface ...","No action is required."
"PIM6","5","NBR_CHANGE","Neighbor %s %s on interface %s","PIM neighbor went up/down due to Hello-message seen/lost. Parameters: Neighbor IPv6 address, Neighbor state, Interface ...","No action is required."
"PIM6","6","IF_DEPEND","Removed interface (%s) has %s dependency","There is residual configuration on the deleted interface. Parameters: Interface name, Dependent Config Command ...","No action is required."
"PIM6","6","MAX_GRANGES","Max Granges allowed to be configured for use shared tree config is %d","Exceeded the group range limit.","No action is required."
"PIM6","6","MAX_RPS","Cannot store bidir-RP %s, a maximum of %d are supported","Due to hardware limitations, there is a maximum number of Bidir-PIM6 RPs that can be stored.","No action is required."
"PIM6","6","MQFLUSHED","Flushing %lu messages from %s mq","Flushing old residual messages fom the message-queue.","No action is required."
"PIM6","6","MQLOOP_UNKNOWN_MSG","Received unknown message %d/%d","PIM6 process received unknown Interprocess message, dropped.","No action is required."
"PIM6","6","NEGATIVE_PREFIX","Group prefix %s/%d from RP %s has negative-bit set, ignore group entry","The RP is advertising a group range to be in dense-mode. This implementation only supports sparse-mode so the group entry will be igored. Parameters: Type of malloc(size), Function Name ...","No action is required."
"PIM6","6","PRESERVE_ROUTES","Preserving routes from last instantiation","PIM6 is restoring the routes it had added in previous instance.","No action is required."
"PIM6","6","RESERVE_LIMIT_WARNING","Exceeded 80% of the reserve-limit for VRF %s","Exceeded 80% of the reserve-limit for VRF Parameters: VRF ...","No action is required."
"PIM6","6","RESTART_SHUTDOWN","PIM6 shutting self down via restart command","PIM6 process is shutting itself down due to the restart command.","No action is required."
"PIM6","6","SHUTDOWN","Shutting down PIM6 process","PIM6 received a shutdown request.","No action is required."
"PIM6","6","SHUTDOWN_SELF","PIM6 shutting self down","PIM6 process is shutting itself down.","No action is required."
"PIM6","6","STATE_LIMIT_WARNING","Exceeded 80% of the state-limit for VRF %s","Exceeded 80% of the state-limit for VRF Parameters: VRF ...","No action is required."
"PIM6","6","UNKNOWN_OPC","Received unknown mts opcode %d","PIM6 process received unknown Interprocess message, dropped. Parameters: MTS Opcode ...","No action is required."
"PM","2","STARTUP_FAILURE","Failed to %s during startup. error %d","A critical operation has failed during startup of the PM process.","No action is required."
"PM","3","API_FAILED","External API failed (%d)","External API failed.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"PM","3","API_FAILED","External API failed (%s)","External API failed.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"PM","3","ARG_ERR","Argument error (%s): %s","An argument to a PM call is invalid.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"PM","3","CLNT_FAILURE","Failed to %s from client","A PM client operation has failed.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"PM","3","CPI_ERR","%s","A failure occurred in the communication with the CPI.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"PM","3","DUP_REG_ERR","%s is already registered with PM","A PM client tried to register more than once with PM.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"PM","3","ERROR","Failed to %s","A critical operation has failed in the PM process.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"PM","3","ETH_STUB_ERR","%s","A failure occurred in the Ethernet stub module.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"PM","3","HA_UPDATE","HA update failed (%d)","HA update failed.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"PM","3","IF_INDEX","Invalid interface index received from %d","Invalid interface index received.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"PM","3","INTERNAL_ERROR","%s","An internal error has occurred in the PM process.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"PM","3","IPC_ERR","%s","A failure occurred while communicating with another process.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"PM","3","MQ_SEND","Failed to send message %s (err: %s)","A message queue send operation failed.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"PM","3","MSG_TO_TLV","TLV Conversion failed (%d)","TLV conversion failed.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"PM","3","MTS_DROP","%s:Error returned from mts_drop(), errno: %s opcode %d","PM called an MTS API which returned an error.","No action is required."
"PM","3","MTS_DROP","Error returned from mts_drop(), errno: %s","PM called an MTS API which returned an error.","No action is required."
"PM","3","MTS_RECV","Error returned from mts_recv(), errno: %s","PM called an MTS API which returned an error.","No action is required."
"PM","3","MTS_SEND","Failed to send message %s (err: %s)","PM called an MTS API which returned an error.","No action is required."
"PM","3","NO_MBUF","Failed to allocate mbuf %s","The PM process has run out of network buffers.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"PM","3","NO_MEM","Failed to allocate private memory for %s","The PM process has run out of private memory.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"PM","3","PSS_API_INIT","Ksink pss API init failed (%d)","Ksink pss API init failed.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"PM","3","PSS_REGISTER","PSS register failed (%d)","PSS register failed.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"PM","3","RP2RP_ERR","%s","A failure occurred in the communication with the other RP.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"PM","3","THR_CREATE","Failed to create %s thread. error %d","A failure occurred while creating a thread.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"PM","3","TLV_TO_STRUCT","TLV to Struct Conversion failed (%d)","TLV to Struct conversion failed.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"PM","3","UNK_MSG","Unrecognized message in %s thread. major type %d, minor type %d","An unknown message was received from another process.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"PM","3","UNK_MSG_MAJOR","Unrecognized message from %s. Major type %d","An unknown message (major) was received from another process.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"PM","3","UNK_MSG_MINOR","Unrecognized message from %s. Minor type %d","An unknown message (mior) was received from another process.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"PM","5","NOTICE","%s","An unexpected event has occurred.","No action is required."
"PM","6","CLIENT_GET","HA client filter recovery failed (%d)","HA client filter recovery failed.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"PM","6","IF_INIT","Interface %s has been initialised","An interface has been initialized.","No action is required."
"PM","6","IF_MEMB_GET","HA if-membership recovery failed (%d)","HA if-membership recovery failed.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"PM","6","MSG","%s","A generic message to the user.","No action is required."
"PM","6","MTS_UNKNOWN_MSG","Received unknown MTS message with opcde %d, dropping it","PM received an unknown message. The message is dropped.","No action is required."
"PM","6","VDC_MEMB_GET","HA vdc-membership recovery failed (%d)","HA vdc-membership recovery failed.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"PMALLOC","3","BITMAP_MEM_CHECK","Failed to allocate bitmap for memory checking in %s\n","In PMALLOC lib, process failed to allocate bitmap for memory check ing. Parameters: Function name ...","No action is required."
"PMALLOC","3","MALLOC_ENABLE_CHECKER","Malloc enable checker failed in %s\n","In PMALLOC lib, process failed to turn on memory accesses. Parameters: Function name ...","No action is required."
"PMALLOC","3","MALLOC_ENABLE_CHECKER_INFO","%d bytes already allocated\n","In PMALLOC lib, warn if some bytes have already been allocated. Parameters: Number of bytes ...","No action is required."
"PMALLOC","3","MALLOC_FAILURE","Malloc failure in %s\n","In PMALLOC lib, Malloc failed. Parameters: Function name ...","No action is required."
"PMALLOC","3","NOT_ALLOCATED_SM_MALLOC_STR","%s failed in %s\n","In PMALLOC lib, invalid memory block/excess block request. Parameters: Function name,Function name ...","No action is required."
"PMALLOC","3","SEGMENT_NOT_INIT","Segment 0x%p not initialized for memory checking\n","In PMALLOC lib, segment is not initialized for memory check ing. Parameters: Shared memory segment ...","No action is required."
"PMALLOC","3","SM_INIT_CHECKING","%s failed in %s\n","In PMALLOC lib, function failed to initialized. Parameters: Function name,Function name ...","No action is required."
"PMALLOC","6","BLOCKED_MEMSEG_MUTEX","Blocked for memseg_mutex\n","In PMALLOC lib, process is blocked for memseg_mutex.","No action is required."
"PMALLOC","6","LARGE_MEM","Large mem: shared %d\n","In PMALLOC lib, large memory requested. Parameters: Shared memory segment ...","No action is required."
"PMALLOC","6","MMAP_SIZE","MMAP size is: %d\n","In PMALLOC lib, Memory map size. Parameters: Memory Map size ...","No action is required."
"PMALLOC","6","SBRK_FAILURE","sbrk failed in %s\n","In PMALLOC lib, return vlaue from MORECORE failed. Parameters: Function name ...","No action is required."
"PT","4","PT_WARNING","%s","Patricia Tree API warning.","No action is required."
"PWE","2","ERROR","%s","As self-explained by the message itself.","Use the 'restart' command to restart the feature and clear this problem."
"PWE","2","FAILURE","Failed to %s","As self-explained by the message itself.","Use the 'restart' command to restart the feature and clear this problem."
"PWE","2","FAILURE_LXC_ADD","add create-lxc to ipc txlist for iod %d and %d\n","As self-explained by the message itself.","Use the 'restart' command to restart the feature and clear this problem."
"PWE","2","FAILURE_THREAD","Failed to create %.20s - %d","As self-explained by the message itself.","Use the 'restart' command to restart the feature and clear this problem."
"PWE","2","FAILURE_TOLERANT","Failed to %s","The system errors as self-explained by the message itself.","No action is required."
"PWE","2","NO_MEM","No memory event detected","The router did not have enough memory to store certain data structures.","Add more memory to the router."
"PWE","2","NO_SH_MEM","No shared memory available for %s","Pre-allocated shared memory is not enough for too-large configs.","add more shared memory to pwe."
"PWE","3","CORRUPT_DATA","corrupt data %s","self-explanatory.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"PWE","3","INIT","PWE initialization failed %s","pwe cannot be initialized.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"PWE","3","MTS_BIND","Error returned from mts_bind(), errno: %s","PWE called an MTS API which returned an error.","Dump core, and then restart component."
"PWE","3","MTS_DROP","Error returned from mts_drop(), errno: %s","PWE called an MTS API which returned an error.","Dump core, and then restart component."
"PWE","3","MTS_RECV","Error returned from mts_recv(), errno: %s","PWE called an MTS API which returned an error.","Dump core, and then restart component."
"PWE","3","MTS_UNKNOWN_MSG","Unknown error returned from MTS, errno: %d","PWE called an MTS API which returned an unknown error.","Dump core, and then restart component."
"PWE","3","SYSMGR_DISPATCH","Error returned from sysmgr_dispatch(), errno: %s","PWE called the system manager API which returned an error.","Dump core, and then restart component."
"PWE","6","EXIT_OUT","Exit with status 0x%x","pwe exits.","No action is required."
"PWE","6","INFORMATION","%s","Informational messages as self-explained by the message itself.","No action is required."
"PWE","6","IP_ADDRESS_NONE","empty IP address for iod %d","self-explained.","No action is required."
"PWE","6","SYSMAN_CLEANUP","Terminated by SYSMAN cleanup signal ;",": pwe has been deconfigured or restarted or killed Explanation    The system has detected an error.","No action is required."
"REGEX","3","BACKSLASH","Trailing \ error in %s\n","In REGEX lib, trailing backslash error. Parameters: Function name ...","No action is required."
"REGEX","3","CORRPTD_OPCODE","Corrupted opcode in %s\n","In REGEX lib, corrupted opcode. Parameters: Function name ...","No action is required."
"REGEX","3","CORRPTD_PGM","Corrupted program in %s\n","In REGEX lib, corrupted program. Parameters: Function name ...","No action is required."
"REGEX","3","CORRPTD_POINTERS","Corrupted pointers in %s\n","In REGEX lib, corrupted pointers. Parameters: Function name ...","No action is required."
"REGEX","3","DMG_REGEX","Damaged regexp fed to regsub in %s\n","In REGEX lib, damaged regexp fed to regsub. Parameters: Function name ...","No action is required."
"REGEX","3","EXP_TOO_BIG","Expression too big in %s\n","In REGEX lib, expression too big. Parameters: Function name ...","No action is required."
"REGEX","3","INTERNAL_URP","Internal urp in %s\n","In REGEX lib, internal urp error. Parameters: Function name ...","No action is required."
"REGEX","3","INTR_FOULUP","Internal foulup in %s\n","In REGEX lib, internal foulup. Parameters: Function name ...","No action is required."
"REGEX","3","INVALID_BRCKT_RANGE","Invalid [] range in %s\n","In REGEX lib, invalid [] range. Parameters: Function name ...","No action is required."
"REGEX","3","INVALID_LENGTH","Invalid character position in %s\n","In REGEX lib, invalid character position. Parameters: Function name ...","No action is required."
"REGEX","3","JUNK","Junk characters at the end in %s\n","In REGEX lib, junk characters at the end. Parameters: Function name ...","No action is required."
"REGEX","3","MEMORY_CORRUPTION","Memory corruption in %s\n","In REGEX lib, memory corruption. Parameters: Function name ...","No action is required."
"REGEX","3","MEMORY_ERR","Not enough memory in %s\n","In REGEX lib, not enough memory. Parameters: Function name ...","No action is required."
"REGEX","3","NESTED_SYMBOL","Nested *?+ in %s\n","In REGEX lib, nested *?+ symbols. Parameters: Function name ...","No action is required."
"REGEX","3","NULL_PARM_REGSUB","NULL parameter to regsub in %s\n","In REGEX lib, NULL parameter to regsub. Parameters: Function name ...","No action is required."
"REGEX","3","NULL_PGM_PARM","Null program parameter %s\n","In REGEX lib, null program parameter. Parameters: Function name ...","No action is required."
"REGEX","3","NULL_STR_PARM","NULL string parameter in %s\n","In REGEX lib, null string parameter. Parameters: Function name ...","No action is required."
"REGEX","3","OPND_EMPTY","*+ operand could be empty in %s\n","In REGEX lib, *+ operand could be empty. Parameters: Function name ...","No action is required."
"REGEX","3","PTTRN_LONG","Pattern substitution too long in %s\n","In REGEX lib, pattern substitution too long. Parameters: Function name ...","No action is required."
"REGEX","3","SYMBOL_ERR","?+* follows nothing in %s\n","In REGEX lib, symbol error. Parameters: Function name ...","No action is required."
"REGEX","3","TOO_MANY_PRNTHSIS","Too many paranthesis in %s\n","In REGEX lib, too many parenthesis. Parameters: Function name ...","No action is required."
"REGEX","3","UNMATCHED_BRCKT","Unmatched [] in %s\n","In REGEX lib, unmatched []. Parameters: Function name ...","No action is required."
"REGEX","3","UNMATCHED_PRNTHSIS","Unmatched paranthesis in %s\n","In REGEX lib, unmatched parenthesis. Parameters: Function name ...","No action is required."
"RIP","2","STARTUP_DEBUG","%s","A startup debug of rip process RIP process Parameters: Event ...","No action is required."
"RIP","2","STARTUP_FAILURE","Failed to %s during startup","A critical operation has failed during startup of the RIP process Parameters: Event ...","No action is required."
"RIP","3","AUTH_SEND_FAILURE","%s %s","The RIP process failed to send a message to a neighbor Parameters: Failure Reason, Interface Name ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"RIP","3","FAILURE","Failed to %s","A critical operation has failed in the RIP process Parameters: Event ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"RIP","3","GENERIC","%s","An error occurred Parameters: Error ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"RIP","3","IM_DEL","IOD in IM delete message for %s (%d) mismatches with RIP interface %p (iod %d)","There is a mismatch of interface IODs in IM and RIP Parameters: Interface Name, Interface ID, Interface Name, Interface ID ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"RIP","3","INTERNAL_ERROR","%s","An internal error has occurred in the RIP process Parameters: Error ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"RIP","3","MQ_RCVD","%s thread - message queue receive failure (%d)","An error occurred while trying to receive a message from another process Parameters: Thread Name, Failure Reason ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"RIP","3","MTS_DROP","Error returned from mts_drop(), errno: %s","RIP called an MTS API which returned an error. Parameters: Error Number ...","No action is required."
"RIP","3","MTS_RECV","Error returned from mts_recv(), errno: %s","RIP called an MTS API which returned an error. Parameters: Error Number ...","No action is required."
"RIP","3","POLICY_ERROR","%s","An error has occurred when processing policies Parameters: Error ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"RIP","3","PROCESS_STOP","Process shutting down: %s","RIP called a sysmgr API which returned an error. Parameters: Stop Reason ...","No action is required."
"RIP","3","SEND_FAILURE","Failed to send message. %s","The RIP process failed to send a message to a neighbor Parameters: Failure Reason ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"RIP","3","SYSMGR_CLEANUP","Error returned from sysmgrcb_conditional_srv_cleanup_status(): %d","RIP called a sysmgr API which returned an error. Parameters: Status ...","No action is required."
"RIP","3","UNK_MSG_MAJOR","%s thread - Unrecognized message major type %d","An unknown message was received from another process Parameters: Thread Name, Major Type ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"RIP","3","UNK_MSG_MINOR","%s thread - Unrecognized message minor type %d","An unknown message (mior) was received from another process Parameters: Thread Name, Minor Type ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"RIP","4","IF_DOWN_OVERLOAD","Interface %s brought down due to overload condition for %s af","The interface has been brought down due to an overload condition Parameters: Interface Name, Address Family ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"RIP","4","NO_MEM","Failed to allocate private memory","The RIP process has run out of private memory.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"RIP","4","VALIDATE_ENTRY","%s","A route entry in an incoming response packet is invalid Parameters: Error ...","No action is required."
"RIP","4","VALIDATE_SRC","%s %s","An incoming packet has failed validation Parameters: Failure Reason, Interface Name ...","No action is required."
"RIP","5","TOO_BIG_KEY_SIZE","Authentication key %s is > 16 characters in keychain %s","Authentication key size is > 16 characters. Parameters: Authentication Key, Keychain Name ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"RIP","5","U6RIB_API_FAILURE","Failed to %s routes %s U6RIB","An API call to U6RIB has failed Parameters: Event, To/From ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"RIP","5","URIB_API_FAILURE","Failed to %s routes %s URIB","An API call to URIB has failed Parameters: Event, To/From ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"RIP","6","MTS_UNKNOWN_MSG","Received unknown MTS message with opcde %d, dropping it","RIP received an unknown message. The message is dropped Parameters: Opcode ...","No action is required."
"RIP","6","SYSMAN_CLEANUP","Terminated by SYSMAN cleanup signal ;",": System Manager sent a cleanup signal to RIP to exit the process Explanation    The system has detected an error.","No action is required."
"RIP","6","UNK_DEB_FLAG","Ignore unrecognized debug flag \%s\","An unknown command line debug option was entered Parameters: Debug Flag ...","No action is required."
"RPM","2","LIB_MALLOC_FAILED","malloc() failed for allocating %s in %s()","RPM API library is out of heap memory Parameters: Data, RPM Function ...","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"RPM","2","MALLOC_FAILED","malloc() failed for allocating %s in %s()","RPM process is out of heap memory Parameters: Data, RPM Function ...","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"RPM","2","PPF_SES_ABORT","PPF session abort failed in client %s with an error 0x%08x(%s)","RPM encountered an error during PPF abort operation. Parameters: PPF-Client, Error code, Error message ...","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"RPM","2","PPF_SES_COMMIT","PPF session commit failed in client %s with an error 0x%08x(%s)","RPM encountered a serious error while committing the verified PBR policy changes to PBR clients Parameters: PPF-Client, Error code, Error message ...","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"RPM","2","PPF_SES_RQST","PPF session request failed in client %s with an error 0x%08x(%s)","RPM encountered an error while requesting PBR statistics from PBR clients Parameters: PPF-Client, Error code, Error message ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"RPM","2","PPF_SES_VERIFY","PPF session verify failed in client %s with an error 0x%08x(%s)","RPM encountered an error while pushing PBR policy changes during the verify stage to PBR clients Parameters: PPF-Client, Error code, Error message ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"RPM","2","PSS_SYNC_BUFFER","Crossed pss sync buffer size limit of %d with payload size %d - in %s()","RPM tried to PSS synchronizationa message exceeding the maximum allowed size Parameters: Pss sync buffer size, Message payload size, RPM Function ...","No action is required."
"RPM","2","PTHREAD","%s failed with error - %d in %s()","RPM_UNEXPECTED_EXPLANATION Parameters: Failed Function, Error Code, RPM Function ...","No action is required."
"RPM","2","SMALLOC_FAILED","smalloc() failed for allocating %s in %s()","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 Parameters: Data, RPM Function ...","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"RPM","2","SRV_INIT_API_FAIL","%s failed during initialization in %s()","RPM called a server API during initialization which returned an error. Parameters: Init. Function, RPM Function ...","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"RPM","3","API_FAILED","%s - failed in %s()","RPM invoked an API which failed. This is an unexpected but manageableevent. Parameters: Failed API, RPM Function ...","No action is required."
"RPM","3","API_FAILED_NUM","%s - failed for %d in %s()","RPM invoked an API which failed. This is an unexpected but manageableevent. Parameters: Failed API, Number, RPM Function ...","No action is required."
"RPM","3","API_FAILED_STR","%s - failed for %s in %s()","RPM invoked an API which failed. This is an unexpected but manageableevent. Parameters: Failed API, String1, RPM Function ...","No action is required."
"RPM","3","API_FAILED_STR_NUM","%s - failed for %s %d in %s()","RPM invoked an API which failed. This is an unexpected but manageableevent. Parameters: Failed API, String, Number, RPM Function ...","No action is required."
"RPM","3","API_FAILED_STR_STR","%s - failed for %s %s in %s()","RPM invoked an API which failed. This is an unexpected but manageableevent. Parameters: Failed API, String1, String2, RPM Function ...","No action is required."
"RPM","3","BUILD_LIC_REQ","%s failed with error - %s (0x%08x) - in %s()","API failed to build a license request to recheckout a license. Parameters: Failed API, Error, Error Code, RPM Function ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"RPM","3","INFRA_SYSERR","%s failed with error - %s (0x%08x) - in %s()","RPM called an infra API which returned an error. Parameters: Failed Function, Error, Error Code, RPM Function ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"RPM","3","INT_ERROR","%s in %s()","RPM encountered an error during internal processing Parameters: Error, RPM Function ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"RPM","3","ISSU_PREUPG_FAILED","ISSU Preupgrade failed","Please remove the incompatible RPM/PBR config and restart ISSU.","No action is required."
"RPM","3","LIB_API_FAILED","%s - failed in %s()","RPM invoked an API which failed. This is an unexpected but manageableevent. Parameters: Failed API, RPM Function ...","No action is required."
"RPM","3","LIB_API_FAILED_NUM","%s - failed for %d in %s()","RPM invoked an API which failed. This is an unexpected but manageableevent. Parameters: Failed API, Number, RPM Function ...","No action is required."
"RPM","3","LIB_API_FAILED_NUM_NUM","%s - failed for %d %d in %s()","RPM invoked an API which failed. This is an unexpected but manageableevent. Parameters: Failed API, Number1, Number2, RPM Function ...","No action is required."
"RPM","3","LIB_API_FAILED_STR","%s - failed for %s in %s()","RPM invoked an API which failed. This is an unexpected but manageableevent. Parameters: Failed API, String1, RPM Function ...","No action is required."
"RPM","3","LIB_INT_ERROR","%s in %s()","RPM API encountered an error during internal processing Parameters: Error, RPM Function ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"RPM","3","LIB_KEYCHAIN","Unexpected keychain result :%s","Unexpected result during RPM keychain API processing Parameters: Keychain Result ...","No action is required."
"RPM","3","LIB_MTS_SEND","Error returned from mts_send(), errno: %s in %s()","An MTS API returned an error while RPM was sending an MTS message. Parameters: Error, RPM Function ...","No action is required."
"RPM","3","LIC_CHECKIN_FAILED","%s failed with error - %s (0x%08x) - in %s()","Licensing API failed to check in a license. Parameters: Failed API, Error, Error Code, RPM Function ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"RPM","3","LIC_CHECKOUT_FAILED","%s failed with error - %s (0x%08x) - in %s()","Licensing API failed to check out a license. Parameters: Failed API, Error, Error Code, RPM Function ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"RPM","3","LIC_REG_FAILED","%s failed with error - %s (0x%08x) - in %s()","Licensing API failed while registering for license change notifications. Parameters: Failed API, Error, Error Code, RPM Function ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"RPM","3","LOAD_PARSE_TREE","%s failed with error - %s (0x%08x) - in %s()","API failed to load parse tree for PBR commands. Parameters: Failed API, Error, Error Code, RPM Function ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"RPM","3","MTS_DROP","Error returned from mts_drop(), errno: %s (0x%08x) in %s()","An MTS API returned an error when RPM tried to drop a message Parameters: Error, Error Code, RPM Function ...","No action is required."
"RPM","3","MTS_RECV","Error returned from tsp_mts_recv(), errno: %s (0x%08x) in %s()","An MTS API returned an error while RPM was receiving on an MTS queue Parameters: Error, Error Code, RPM Function ...","No action is required."
"RPM","3","MTS_SEND","Error returned from mts_send(), errno: %s (0x%08x) in %s()","An MTS API returned an error while RPM was sending an MTS message Parameters: Error, Error Code, RPM Function ...","No action is required."
"RPM","3","UNLOAD_PARSE_TREE","%s failed with error - %s (0x%08x) - in %s()","API failed to unload parse tree for PBR commands. Parameters: Failed API, Error, Error Code, RPM Function ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"RPM","6","LIB_MATCH_IGNORED","The command %s in seq. %u of route-map %s is ignored in %s()","A route-map match command has been igored. Parameters: Match Command, Seq No., Route-map, RPM Function ...","No action is required."
"RPM","6","MTS_UNKNOWN_MSG","Received unknown MTS message with opcode %d, dropping it in %s()","RPM received an unknown message. The message is dropped Parameters: MTS Opcode, RPM Function ...","No action is required."
"RPM","6","RESTART_SHUTDOWN","RPM shutting self down via restart command in %s()","RPM process is shutting itself down due to the restart command. Parameters: RPM Function ...","No action is required."
"SLAB_LIB","2","SLAB_ELEM_ERR","Slab element Alloc PC: %p, Element index: %d","An error occurred in a call to the slab library.","No action is required."
"SLAB_LIB","3","SLAB_ERR","Slab error [%s] in %s","An error occurred in a call to the slab library.","No action is required."
"SMM","0","SM_CREATE_ORIG_VAL","%s with the %u value failed. Retrying with the lower value %u size","SMM could not create requested size, trying for a create for a lower size succeeded. Parameters: Function name, Original requested size, Lower size being retried ...","No action is required."
"SMM","0","SM_RECREATE_LOW_VAL","Reallocate with new value %u bytes (%u MB) failed, but we were able to allocate a segment with a lower value.","SMM could not recreate requested size, but create for a lower size succeeded. Parameters: SHM size bytes, SHM size MB ...","No action is required."
"SMM","2","SAME_REGION","Same region allocated on recreate request, from addr %p with size %d","A client requested for a new region to be created, but got the same region back. Parameters: memory address, size ...","No action is required."
"SMM","2","SM_API_FAILED","%s failed in %s() with error \%s\ for SHM size %u bytes (%u MB). Trying to allocate shared memory with lower value now.","SMM could not recreate a shared-memory segment. Parameters: SMM API, Function name, Error, SHM size bytes, SHM size in MB ...","No action is required."
"SMM","3","API_FAILED","%s failed in %s","Component API call failed in SMM. Parameters: API name, Function name ...","No action is required."
"SMM","3","API_MTS_FAILED","%s failed in %s, errno: %s","SMM failed using the MTS API. Parameters: API name, function name, Error number ...","No action is required."
"SMM","3","API_SM_FAILED","Could not allocate shared-memory segment. %s failed in %s with error %s","SMM process could not allocate shared-memory. Parameters: SMM API, Function name, Error ...","No action is required."
"SMM","3","BAD_API_PARAM","%s API failed because %s","Illegal arguments were provided for an SMM API Parameters: API name, reason ...","Use the 'restart' command to restart the feature and clear this problem."
"SMM","3","BAD_SEG_TYPE","SMM API %s failed for %s, %s shared memory segment expected","Incorrect SMM API called for the type (static/dynamic) shared memory segment Parameters: SMM API, Segment name, Segment type ...","No action is required."
"SMM","3","FTRUNCATE_FAILED","%s failed in %s with error %s","SMM could not truncate process memory segment. Parameters: SM API, Function name, Error ...","No action is required."
"SMM","3","GET_SHM_INFO_FAILED","Failed to get SHM info in function %s with error: %s","Failed to get SHM information. Parameters: Function name, Error ...","No action is required."
"SMM","3","GETRLIMIT_FAILED","Getrlimit failed in %s, reason %s","SMM API could not set memory resource limit for a client Parameters: Function name, Error string ...","Use the 'restart' command to restart the feature and clear this problem."
"SMM","3","HA_FAILED","SMM HA:%s","SMM process restart recovery has succeeded / failed. Parameters: Reason string ...","No action is required."
"SMM","3","INVALID_STEP_SIZE","%s: Invalid step sizes specified for dynamic SHM, incr size: %u, decr_size: %u","Illegal arguments were provided for an SMM API Parameters: Function name, Increment step size, Decrement step size ...","Use the 'restart' command to restart the feature and clear this problem."
"SMM","3","LSEEK_FAILED","Failed to seek to offset %u for file %s","Lseek operation on a shared memory file failed Parameters: Address, Segment name ...","No action is required."
"SMM","3","MALLOC_FAILED","%s failed in %s","SMM process is out of free memory. Parameters: API name, Function name ...","No action is required."
"SMM","3","MEMORY_API_ERROR","%s failed in %s with error %s","Memory API failed. Parameters: SM API, Function name, Error ...","No action is required."
"SMM","3","MMAP_FAILED","%s failed in %s with error %s for segment %s. Requested map from %p for size %d","MMAP failed. Parameters: SM API, Function name, Error ...","No action is required."
"SMM","3","MQ_FAILED","%s failed in %s, errno: %s","SMM failed to access message-queue resource. Parameters: API name, function name, Error number ...","No action is required."
"SMM","3","MTS_DROP","Error returned from mts_drop()","SMM called an MTS API which returned an error.","Dump core, and then restart component."
"SMM","3","MTS_FAILED","%s failed in %s, errno: %s","SMM failed using the MTS API. Parameters: API name, function name, Error number ...","No action is required."
"SMM","3","MTS_RECV","Error returned from mts_recv()","SMM called an MTS API which returned an error.","Dump core, and then restart component."
"SMM","3","NO_REGION","No corresponding region found for segment %s","SMM library could not find the region data structure which corresponds to each shared memory segment Parameters: Segment name ...","No action is required."
"SMM","3","PSS_REPORT","SMM HA:%s","Persistent DB reports for SMM. Parameters: Reason string ...","No action is required."
"SMM","3","PTHREAD_FAILED","%s failed for %s in %s","SMM process failed to create a task thread. Parameters: API name, function name, Error number ...","Dump core, then reload the stack."
"SMM","3","REFCOUNT_ERR","%s: Refcount of shared memory segment %s is %d, expected refcount %d","There are more/less readers of the same shared memory segment than expected for the API to succeed.","No action is required."
"SMM","3","REGION_FAILED","Failed to create SMM region %s","SMM API failed in %s to create a region %s for the shared memory this client is trying to open. Parameters: Function name, Region name ...","Use the 'restart' command to restart the feature and clear this problem."
"SMM","3","SETRLIMIT_FAILED","Address space size increment of %d failed in %s, reason %s","SMM API could not set memory resource limit for a client Parameters: Number of bytes, Function name, Error string ...","No action is required."
"SMM","3","SHM_CLEANUP_FAILED","Failed to cleanup SHM info for %s in %s with error: %s","Failed to cleanup shared memory for recreate API Parameters: SHM name, Function Name, Error string ...","No action is required."
"SMM","3","SM_CREATE_FAILED","Failed to create %s shared memory segment %s of size %d (max %d)","SMM failed to create a shared memory segment. Parameters: SHM type, SHM name, SHM size, Max size for dynamic SHM ...","Use the 'restart' command to restart the feature and clear this problem."
"SMM","3","SM_FAILED","Could not allocate shared-memory segment","SMM process could not allocate shared-memory.","No action is required."
"SMM","3","SM_GET_NEW_REGION_FAILED","Failed to get shared memory region for %s of size %d","SMM failed to get a new region of the requested size Parameters: SHM name, size ...","Use the 'restart' command to restart the feature and clear this problem."
"SMM","3","SM_INFO_FOR_SMM","Received request %s for SMM's segment, unexpected","SMM received a request to open its own shared memory segment Parameters: API name ...","No action is required."
"SMM","3","SM_OPEN_FAILED","%s failed in %s with error %s","SMM could not open a shared-memory segment. Parameters: SM API, Function name, Error ...","No action is required."
"SMM","3","SMM_API_FAILED","%s failed in %s","Component API call failed in SMM. Parameters: API name, Function name ...","No action is required."
"SMM","3","SYSMGR_DISPATCH","Error returned from sysmgr_dispatch()","SMM called the system manager API which returned an error.","Dump core, and then restart component."
"SMM","3","TIMER_FAILED","active_timer_create() failed in %s for %s timer","SMM failed to initialize timer resource. Parameters: timer type (heap/wheel) ...","Dump core, and then restart component."
"SMM","3","TIMER_SET_INIT","Couldn't init %s active timer set","SMM failed to initialize timer resource. Parameters: timer type (heap/wheel) ...","Dump core, and then restart component."
"SMM","3","UNKNOWN_SMM_MTYPE","Unknown %s in mtype: %d/%d (major/minor) in %s","SMM process received unknown Interprocess message, dropped. Parameters: Major/Minor type, Major number, Minor number, Function name ...","No action is required."
"SMM","5","UNKNOWN_OPC","Unknown MTS opcode %d in %s","The system has detected an unexpected error. Parameters: MTS opcode, Function name ...","No action is required."
"SMM","6","SUP_SWITCHOVER","Received %s SUP switchover message.","Events related to changing SUP state from standby to active.","No action is required."
"SMM","6","SUP_SWOVER_DONE","%s","Events related to changing SUP state from standby to active.","No action is required."
"SYSLOG","0","SL_MSG_EMERG","%s","Syslog API Emergency.","No action is required."
"SYSLOG","1","SL_MSG_ALERT","%s","Syslog API Alert.","No action is required."
"SYSLOG","2","DT_TEST","Test Syslog facility: %s","The system has detected an error.","No action is required."
"SYSLOG","2","DT_TEST_LIB","Test Syslog library facility: %s","The system has detected an error.","No action is required."
"SYSLOG","2","SL_MSG_CRIT","%s","Syslog API Critical.","No action is required."
"SYSLOG","3","NOTSET","Trying to print uninitialized error message","An internal software error occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"SYSLOG","3","SL_MSG_ERR","%s","Syslog API Error.","No action is required."
"SYSLOG","3","TOOLONG","Error message too long: %s","An internal software error occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"SYSLOG","3","UNKNOWN","Unknown facility/severity: %x","An internal software error occurred.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"SYSLOG","4","SL_MSG_WARNING","%s","Syslog API Warning.","No action is required."
"SYSLOG","5","SL_MSG_NOTICE","%s","Syslog API Notice.","No action is required."
"SYSLOG","6","SL_MSG_INFO","%s","Syslog API Info.","No action is required."
"SYSLOG","7","SL_MSG_DEBUG","%s","Syslog API Debug.","No action is required."
"SYSWRAP_LIB","2","SYSWRAP_ERR","Error condition in stack: %s tid=%lu: %#x bytes left on stack of %#lx bytes","An error occurred in a call to the syswrap library.","No action is required."
"TCP","2","APICLOSE","%s: Unable to close %s API","Cannot close API.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"TCP","2","APIINIT","%s: Unable to initialize %s API","Cannot init API.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"TCP","2","ATTACH","%s: Unable to attach to %s","Cannot attach shared memoty.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"TCP","2","COND_DESTROY","%s: pthread_cond_destroy failed, error %s","No system resources.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"TCP","2","COND_INIT","%s: pthread_cond_init failed, error %s","No system resources.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"TCP","2","COND_WAIT","%s: pthread_cond_wait failed, error %s","No system resources.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"TCP","2","DEREGISTER","%s: Unable to deregister to %s","Cannot deregister with component.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"TCP","2","ENQUEUE","%s: Unable to enqueue %s to %s","Cannot insert client structure in client list.","Use the 'restart' command to restart the feature and clear this problem."
"TCP","2","LARGE_PKT","%s: Packet size greater than 65535 bytes, len %d","Packet size greater than 65535 bytes.","Use the 'restart' command to restart the feature and clear this problem."
"TCP","2","MGETHDR","%s: MGETHDR failed, error %s","No system resources.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"TCP","2","MISMATCH_LEN","%s: Mismatch in mbuf len (%d) and IP len (%d)","Mismatch in mbuf len and IP len.","Use the 'restart' command to restart the feature and clear this problem."
"TCP","2","MPREPEND","%s: m_prepend failed for connection, L: %s.%d, F: %s.%d, error %s","No system resources.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"TCP","2","MPULLUP","%s: m_pullup failed for %s, error %s","No system resources.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"TCP","2","MTS_BIND","%s: Unable to bind to %s mts queue: %s","TCP called an MTS API which returned an error.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"TCP","2","MUTEX_DESTROY","%s: pthread_mutex_destroy failed, error %s","No system resources.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"TCP","2","MUTEX_INIT","%s: pthread_mutex_init failed, error %s","No system resources.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"TCP","2","MUTEX_LOCK","%s: pthread_mutex_lock failed, error %s","No system resources.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"TCP","2","MUTEX_TRYLOCK","%s: pthread_mutex_trylock failed, error %s","No system resources.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"TCP","2","MUTEX_UNLOCK","%s: pthread_mutex_unlock failed, error %s","No system resources.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"TCP","2","PANIC","%s: PANIC: %s","Internal TCP error.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"TCP","2","PTHREAD","%s: procket_pthread_create failed for %s: error %d","No system resources.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"TCP","2","REGISTER","%s: %s failed","Cannot register with component.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"TCP","2","SETSCHED","%s: Could not set scheduling or priority","Could not set scheduling or priority.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"TCP","2","TSP_INIT","%s: Could not initialize tsp locking library","Could not initilize locking library.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"TCP","3","ALLOC","Error returned from calloc(), errno: %s","TCP called a calloc API which returned an error.","No action is required."
"TCP","3","BADSIG","%s: Should not have received signal %d","Unexpected signal.","No action is required."
"TCP","3","CLIENT_DELETE","%s: Could not delete client \%s\ pid %d error %s","Cannot delete client from clients list.","Use the 'restart' command to restart the feature and clear this problem."
"TCP","3","CLIENT_NULL","%s: Client struct for pid %d not found","Cannot find client for pid.","Use the 'restart' command to restart the feature and clear this problem."
"TCP","3","DOMAININIT","%s: domaininit: %s sw[%d] has no usrreqs","Bkoken domain structure.","Use the 'restart' command to restart the feature and clear this problem."
"TCP","3","FORK_ERROR","%s: Parent of the forked child did not create state for child %d:%d","Parent process did not create state necessary for child process registeration.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"TCP","3","INVALIDPARAM","%s: Invalid %s","Invalid parameter.","Use the 'restart' command to restart the feature and clear this problem."
"TCP","3","IP_PROT_UNKNOWN","%s: Unknown protocol in IP message %d","IP sent a packet with unknown protocol ID.","Use the 'restart' command to restart the feature and clear this problem."
"TCP","3","MBUF_COPY","%s: Unable to do m_copyback","No system resources.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"TCP","3","MSG_MAJOR_UNKNOWN","%s: Unknown message major %d, minor %s","Unknown major type.","Use the 'restart' command to restart the feature and clear this problem."
"TCP","3","MSG_MINOR_UNKNOWN","%s: Unknown minor message type %d from %s","Unknown mior type.","Use the 'restart' command to restart the feature and clear this problem."
"TCP","3","MTS_RESPOND","Error returned from mts_send_response(), errno: %s","TCP called an MTS API which returned an error.","No action is required."
"TCP","3","NOMBUF","%s: Unable to get mbuf","No system resources.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"TCP","3","NOMEM","%s: malloc failed for: %s","No system resources.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"TCP","3","PROCTERM_NOTIFY","%s: Termination notification request failed for pid %d","Request for process termination notification has failed. This could lead to TCP memory leak over period of time.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"TCP","3","SM_CREATE","%s: Shared memory \%s\ create failed, error %d","No system resources.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"TCP","3","SOCKET_COLL","%s: Socket collision, old client: \%s\, pid: %d, new client: \%s\, pid: %d","Two clients selected on the same socket.","No action is required."
"TCP","3","SOCKET_COLL_FOUND","%s: Socket collision found for client: \%s\, pid %d","Two clients selected on the same socket.","No action is required."
"TCP","3","SOCREATE","%s: socreate create failed for client \%s\ pid %d error %s","Cannot create socket. See errorno for details Reload software if no memory.","Use the 'restart' command to restart the feature and clear this problem."
"TCP","3","TCP_MD5_ERROR","%s:%s","General MD5 error messages.","No action is required."
"TCP","3","TCP_MTS_DROP","Error returned from mts_drop(), errno: %s","TCP called an MTS API which returned an error.","No action is required."
"TCP","3","TCP_MTS_RECV","%s: mts_recv() failed on %s queue: %s","TCP called an MTS API which returned an error.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"TCP","3","TCP_STRUCT_TO_TLV","Structure to TLV failed, errno: %s","TLV conversion failed.","No action is required."
"TCP","3","TCP_TLV_TO_STRUCT","Structure to TLV failed, errno: %s","TLV conversion failed.","No action is required."
"TCP","3","TIMER_CANCEL","%s: Timer cancel failed for %s","No system resources.","Use the 'restart' command to restart the feature and clear this problem."
"TCP","3","TIMER_CREATE","%s: Timer create failed for %s","No system resources.","Use the 'restart' command to restart the feature and clear this problem."
"TCP","3","TIMER_INIT","%s: Timer init failed","No system resources.","Use the 'restart' command to restart the feature and clear this problem."
"TCP","3","TIMER_START","%s: Timer start failed for %s","No system resources.","Use the 'restart' command to restart the feature and clear this problem."
"TCP","6","EXISTS","%s: Child Exists: %d, ppid %d","Child already registered.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"TCP","6","NOT_FOUND","%s: Parent not found: %d, cpid %d","Parent process not found.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"TCP","6","TCP_MD5_AUTH_FAILURE","%s:Dropping packets from src:%s.%d,dst:%s.%d","TCP received packet which fails authentication. The packet is dropped.","No action is required."
"TCP","6","TCP_MTS_UNKNOWN_MSG","Received unknown MTS message with opcde %d, dropping it","TCP received an unknown MTS message. The message is dropped.","No action is required."
"TSP","3","INIT_PROC","%s%s","Failed to init process with TSP. Parameters: Reason, Error string ...","No action is required."
"TSP","3","INIT_THREAD","%s%s","Failed to init thread with TSP. Parameters: Reason, Error string ...","No action is required."
"TSP","3","INVALID_LOCK_INDEX","Lock index invalid","Lock index is invalid.","No action is required."
"TSP","3","INVALID_THREAD_ID","Invalid thread id: %d","Invalid thread id. Parameters: Thread id ...","No action is required."
"TSP","3","LOCK_MODE_CONFLICT","Lock mode conflict","Lock R/W mode conflct.","No action is required."
"TSP","3","LOCK_RELEASE_ORDER","Lock release out of order","Releasing locks out of order.","No action is required."
"TSP","3","LOCK_STACK_EMPTY","Lock stack empty","Lock stack is empty.","No action is required."
"TSP","3","LOCK_STACK_FULL","Lock stack full","Lock stack is full.","No action is required."
"TSP","3","MUTEX_LOCK_FAIL","pthread_mutex_lock() failed: %s","Failed to lock mutex. Parameters: Error string ...","No action is required."
"TSP","3","MUTEX_UNLOCK_FAIL","pthread_mutex_unlock() failed: %s","Failed to unlock mutex. Parameters: Error string ...","No action is required."
"TSP","3","RWSEM_CREATE_FAIL","rwsem_create(sap=%u, flags=%#x) err %#x - %s","Failed to create rwsem. Parameters: Lock SAP id, Flags, Error code, Error string ...","No action is required."
"TSP","3","RWSEM_HAVE_LOCK_FAIL","rwsem_have_lock(sap=%u, flags=%#x) err %#x - %s","Failed to query rwsem status. Parameters: Lock SAP id, Flags, Error code, Error string ...","No action is required."
"TSP","3","RWSEM_INIT_FAIL","rwsem_lib_init(vdc=%u, uuid=%u, tid=%u) err %#x - %s","Failed to initialize rwsem. Parameters: VDC id, UUID, TID, Error code, Error string ...","No action is required."
"TSP","3","RWSEM_LOCK_FAIL","rwsem_lock_no_sig(%s SAP %u) failed: %s","Failed to lock rwsem. Parameters: R/W, Lock SAP id, Error string ...","No action is required."
"TSP","3","RWSEM_UNLOCK_FAIL","rwsem_unlock(%s SAP %u) failed: %s","Failed to unlock rwsem. Parameters: R/W, Lock SAP id, Error string ...","No action is required."
"TSP","6","SUTIME_BACKWARDS","Getrusage s/utime went backwards %lu.%06lu -> %lu.%06lu","CPU usage counters went backwards Parameters: old s/utime, current s/utime ...","No action is required."
"TX","3","TXLIST_ERROR","%s","TXLIST API returned an error.","No action is required."
"TX","3","TXLIST_PERROR","%s","TXLIST API returned a perror.","No action is required."
"TX","3","TXTHREAD_ERROR","%s","TXTHREAD API returned an error.","No action is required."
"TX","3","TXTHREAD_PERROR","%s","TXTHREAD API returned a perror.","No action is required."
"U6RIB","2","API_INIT_SEM","Failed to init the API semaphore: open: %s, create: %s","U6RIB could not create the semaphore that protects access to the shared memory between U6RIB and its clients. Parameters: Error from open, Error from create ...","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"U6RIB","2","NOPMEM","Failed to allocate private memory for %s","U6RIB 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.","Configure the network or router to decrease the number of routes, or add additional memory to the router."
"U6RIB","2","NOSMEM","Failed to allocate shared memory for %s","U6RIB has run out of shared memory to store routes. This can be caused by a temporary increase of the number of routes in the network, or a general network or router misconfiguration.","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 <min> max <max> limit-resource u6route-mem min <min> max <max>."
"U6RIB","2","RES_MGR","Error returned from %s, errno: 0x%08x (%s) in %s()","The resource manager returned an error to U6RIB, while U6RIB was performing an action relating to its shared memory Parameters: RM Function, Error Code, Error Description, Calling Function ...","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"U6RIB","2","STARTUP_FAILURE","Startup failure: %s","An unrecoverable software error has occurred during u6RIB startup.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"U6RIB","2","TIMER_LIB","%s %s","The timer library returned an error, causing an unrecoverable problem for U6RIB.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"U6RIB","2","TOO_MANY_CLIENTS","%s client \%s\","U6RIB cannot add this client because the U6RIB client limit has already been reached. Parameters: Resource, Client ...","Restart the component when the system is working."
"U6RIB","3","ADD_PATH","%s: could not add path %s/%u via %s, %s for client \%s\.","A route add operation has failed for the given client. There may be a previous error message that further explains the problem. Parameters: Function, Prefix, Mask-len, NextHop, Interface, Client ...","No action is required."
"U6RIB","3","ADD_TPATH","Client \%s\ added %s/%u via tableid 0x%08x : %s","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. Parameters: Client, Prefix, Mask-len, Table-Id, Error ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"U6RIB","3","ADD_TPATH_ROUTE","Client \%s\ added %s/%u%%%s","A route add operation has failed for the given client. This was because the route could not be found. This may be a transient error. Parameters: Client, Prefix, Mask-len, Table-name ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"U6RIB","3","ASSERT_ERROR","%s:%d: Assertion \%s\ failed.","An internal software error has occurred. An assertion held to be true failed. Parameters: Filename, Line number, Expression ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"U6RIB","3","AVLADD_ERROR","Could not add %s (0x%08x) to the %s avl","U6RIB was unable to add a piece of data to an AVL data structure. Parameters: Data item, Memory address, Data structure ...","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"U6RIB","3","AVLINIT_ERROR","Could not init %s avl for VRF %s","U6RIB was unable to correctly initialize an AVL data structure. Parameters: AVL name, VRF-name ...","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"U6RIB","3","CMI_MTSSEND_FAILURE","mts_send failure for client %s: %s","U6RIB was unable to send MTS message to a particular client Parameters: Client name, Error ...","Use the 'system switchover' 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."
"U6RIB","3","CMI_PAYLOAD_CONV_ERR","CMI payload conversion error failure from %s order to %s order","The cmi payload conversion did not occur successfully. Parameters: order, order ...","No action is required."
"U6RIB","3","ECMP_LDSHR","%s","Error related to ECMP load-share configuration which will affect load-sharing for software-switched packets. If parity between hardware and software switching is important, perform a switchover.","Requires operator to intervene."
"U6RIB","3","GET_INSTANCE_ERROR","instance not found for client \%s\ in VRF %s","U6RIB 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 <vrf-name>' Parameters: Client, VRF ...","Requires operator to intervene."
"U6RIB","3","HTADD_ERROR","Could not add %s to the %s hash table","A severe hash table error was encountered. The system may run into more errors because of this problem.","Use the 'system switchover' 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."
"U6RIB","3","INCONSISTENT_RNH","%s: %s/%d","The system has detected an error.Parameters: Owner, Prefix, Length ...","No action is required."
"U6RIB","3","INCONSISTENT_ROUTE","%s: %s/%d via %s","The system has detected an error.Parameters: Owner, Prefix, Length, Next-hop ...","No action is required."
"U6RIB","3","INCONSISTENT_STRUCTURE","%s","Unexpected remaining state during RIB cleanup.","No action is required."
"U6RIB","3","INCONSISTENT_SUMMARY","%s: routes %d, rnh's %d","Unexpected remaining state for client during RIB cleanup, see following for state: 'show routing ipv6 unicast internal event-history errors' Parameters: Owner, Routes, RNHs ...","No action is required."
"U6RIB","3","INSTANCE_CREATE_ERROR","Failed to create routing instance info for client \%s\, VRF %s","U6RIB 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 <vrf-name>' Parameters: Client, VRF ...","Requires operator to intervene."
"U6RIB","3","KSINK_LIB_ERROR","%s %s","A error was encountered during ksink operations. The system may run into more errors because of this problem.","No action is required."
"U6RIB","3","MOD_ERROR","Client \%s\ requested modify route for %s/%d: %s","The named client sent a modify route request, which generated the shown error. Parameters: Client, Prefix, Prefix-Length, Error ...","No action is required."
"U6RIB","3","MORE_INFO_ERROR","Client \%s\: %s","This error provides further information about the previous error. Action should be taken depending on the previous error logged. Parameters: Client, Message ...","No action is required."
"U6RIB","3","MORE_MTS_INFO_ERROR","source SAP is: %d dest SAP is: %d","This error provides further information about the previous MTS error. Action should be taken depending on the previous error logged.","No action is required."
"U6RIB","3","MTS_BIND","mts_bind failed for %s: %s","U6RIB was unable to bind to an MTS queue SAP. Parameters: MTS queue name, Error ...","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"U6RIB","3","MTS_DEREGISTER","mts_deregister failed for u6rib: %s","U6RIB was unable to deregister client from U6RIB notifications, causing an unrecoverable error.","Use the 'restart' command to restart the feature and clear this problem."
"U6RIB","3","MTS_DROP","Error returned from mts_drop(), errno: %s","An MTS API returned an error when U6RIB tried to drop a message.","No action is required."
"U6RIB","3","MTS_NO_PAYLOAD_ERROR","Received MTS message with no payload on %s queue with opcode %d, dropping it","U6RIB received an unknown message. The message is dropped.","No action is required."
"U6RIB","3","MTS_OPTIONS","MTS option set failed for opcode %s: %s (%d)","U6RIB was unable to set options for an MTS opcode Parameters: Requestor, Error String, Error ...","Use the 'system switchover' 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."
"U6RIB","3","MTS_RECV","Error returned from mts_recv(%s), errno: %s","An MTS API returned an error while U6RIB was receiving on an MTS queue. Parameters: Queue name, Error ...","No action is required."
"U6RIB","3","MTS_REGISTER","mts_register failed for u6rib: %s","U6RIB was unable to register client for U6RIB notifications, causing an unrecoverable error.","Use the 'restart' command to restart the feature and clear this problem."
"U6RIB","3","NO_L3VM_INFO_ERROR","no L3VM info for table id 0x%08x from client \%s\ - unknown to L3VM","A client tried to add some information to U6RIB, and provided a Table-Id that is unknown in the system. The client should be restarted. Parameters: Table-Id Client name ...","Use the 'restart' command to restart the feature and clear this problem."
"U6RIB","3","NO_L3VM_LIMITS","Could not get routing table limits from L3VM","U6RIB could not pull the routing limits for the table. L3VM should be restarted.","Use the 'restart' command to restart the feature and clear this problem."
"U6RIB","3","NOT_INIT_L3VM_ERROR","L3VM info for table id 0x%08x from client \%s\ not available - U6RIB not initialised with L3VM","A client tried to add some information to the U6RIB, before U6RIB has registered for table information. The client should be restarted. Parameters: Table-Id, Client name ...","Use the 'restart' command to restart the feature and clear this problem."
"U6RIB","3","OPEN_CLIENT_SHM_ERROR","Failed to open client shared memory \%s\: %s","The calling process failed with the shown error while trying to open the named U6RIB shared memory region. The status of the memory is shown in 'show process memory shared'. Parameters: Name of shared memory region ...","Use the 'restart' command to restart the feature and clear this problem."
"U6RIB","3","PSS","Error returned from %s, errno: 0x%08x (%s) in %s()","U6RIB called a PSS API which returned an error. The error reported should be examined for the cause. Parameters: Failed API, Error Code, Error Description, u6RIB Function ...","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"U6RIB","3","PTADD_ERROR","Could not add %s/%d to the %s pt, error code %d","A severe route table error was encountered. The system may run into more errors because of this problem.","Use the 'system switchover' 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."
"U6RIB","3","QADD_ERROR","Could not add %s to the %s queue","A severe queue error was encountered. The system may run into more errors because of this problem.","Use the 'system switchover' 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."
"U6RIB","3","QDEL_ERROR","Could not delete %s from the %s queue","A severe queue error was encountered. The system may run into more errors because of this problem.","Use the 'system switchover' 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."
"U6RIB","3","RANGE_CHECK_ERR","Range check of %s failed from %s (0x%08x)","The value provided is outside of the acceptable range. Parameters: Range, Provider of value, Value Provided ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"U6RIB","3","RNH_LOOP_ERROR","Number of prefixes forming rnh loop exceeds %d\n Flagging route %s/%d from client \%s\ with nh %s, rnh %s/%d\n as causing rnh loop","U6RIB detected a loop between routes installed in the RIB. Check the message to see which client caused the loop, and take appropriate ation. Parameters: Max RNH Loop, Prefix, Prefix Length, Client, Next-hop, Prefix, Prefix Length ...","Requires operator to intervene."
"U6RIB","3","ROUTECOUNT_UNDERFLOW","Routing table statistic current tried to underflow deleting %s/%d","The system tried to decrement the current number of routes in the table, but the statistic was already zero. Parameters: Prefix, Mask Len ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"U6RIB","3","ROUTELIMIT_EXCEEDED","Number of routes (%llu) reached or exceeds configured limit (%lu); dropped (%llu)","The number of routes in the named routing table has reached the configured limit. No further routes will be added to the table Parameters: Current number of routes, Configured limit, Dropped routes ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"U6RIB","3","ROUTELIMIT_NOT_ENFORCED","Number of routes (%llu) already exceeds newly configured limit (%lu); dropped (%llu)","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. Parameters: Current number of routes, Configured limit, Dropped routes ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"U6RIB","3","ROUTELIMIT_WARNING","Number of routes (%llu) exceeds warning limit (%lu)","The number of routes in the named routing table has reached the configured warning limit. Parameters: Current number of routes, Warning limit ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"U6RIB","3","RPM_LIB_ERROR","%s %d","An RPM library function returned an error. Parameters: Function, RPM Error Code ...","No action is required."
"U6RIB","3","SDWRAP_LIB_ERROR","%s %s","A SDWrap library function returned an error. Parameters: Function, SDWrap Error Code ...","No action is required."
"U6RIB","3","SEND_FROM_ERROR","Send from U6RIB to client \%s\ failed: %s","U6RIB was unable to send a message to the shown client. Parameters: Client, Error ...","Use the 'restart' command to restart the feature and clear this problem."
"U6RIB","3","SEND_TO_ERROR","Send to u6rib failed: %s","The calling process was unable to send a message to U6RIB.","Use the 'restart' command to restart the feature and clear this problem."
"U6RIB","3","STRUCT_ERROR","Structural error: %s, client \%s\, table id 0x%08x.","A severe data structural error was encountered. The system may run into more errors because of this problem. Parameters: Problem, Client, Table id ...","Use the 'system switchover' 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."
"U6RIB","3","TABLE_CREATE_ERROR","Failed to create table info for VRF %s for client \%s\","U6RIB 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 <vrf-name>' Parameters: VRF, Client ...","Requires operator to intervene."
"U6RIB","3","TABLE_STATE_ERROR","Table state %s for VRF %s for client \%s\","U6RIB received a request from a client for a given VRF, but the given VRF was in a state where that request is not permitted Parameters: State, VRF, Client ...","Requires operator to intervene."
"U6RIB","3","UFDM_MTSSEND_FAILURE","MTS send to UFDM failed with unexpected error %d","U6RIB was unable to send a route update to UFDM. This means there will be a route missing from the FIB.","Use the 'system switchover' 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."
"U6RIB","3","UNCONVERGED_ROUTING_CLIENT","Client \%s\ did not signal convergence","The named Client did not signal convergence as expected, within a default time frame. Parameters: Client ...","No action is required."
"U6RIB","3","UNKNOWN_ROUTING_CLIENT","Client \%s\ trying to perform unexpected routing operation","The named Client is calling a routing API, but U6RIB does not expect this client to perform route operations. Parameters: Client ...","No action is required."
"U6RIB","4","COMM_BUFF_ERROR","Only created %d %s communication buffers of size %d","Fewer communication buffers were created than expected. This will have been caused by a low memory condition. Examine the logs for the low memory error.","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 <min> max <max> limit-resource u6route-mem min <min> max <max>."
"U6RIB","4","NHLFE_OWNER","%s/%d via %s%%%s: NHLFE owner changed from client \%s\ to \%s\","A given path can only have one Next-Hop Label Forwarding Entry. Thus this warning indicates that configuration has generated a conflict. Parameters: Prefix, Prefix Length, Next-hop, Interface, Original Client, New Client ...","Requires operator to intervene."
"U6RIB","4","UFDM_ACKNOT_FOUND","Could not find UFDM buffer with ptr 0x%08x","Ack received for a UFDM buffer that U6RIB does not know about. Parameters: Memory address of UFDM buffer ...","No action is required."
"U6RIB","5","API_INIT_SEM_CLEAR","Cleared the API semaphore from %d","The API semaphore was in an unexpected state, and was restored to a correct value. Parameters: Value of semaphore ...","No action is required."
"U6RIB","5","BOGUS_INTF","Client \%s\ tried to add %s/%d via %s with interface %s","A bad interface was received in a path add from the client. Parameters: Client, Prefix, Prefix Length, Next-hop, Interface ...","No action is required."
"U6RIB","5","CLT_EVENT_STATE","Client \%s\ unexpected %s event state %d != %d","An unexpected but recoverable event has occurred.","No action is required."
"U6RIB","5","CLT_NO_BUF","Client \%s\ %s event has no buffer","An unexpected but recoverable event has occurred.","No action is required."
"U6RIB","5","DUP_REGISTER","Client \%s\ register more than once with same pid","A client tried to register more than once with U6RIB. The re-registration was igored.","No action is required."
"U6RIB","5","GENERAL_FAILURE","Failed to %s","The logged action failed.","Use the 'system switchover' 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."
"U6RIB","5","NOTIFY_THREAD","Failed to notify %s thread - Reschedule","An unexpected but recoverable event has occurred.","No action is required."
"U6RIB","5","NULL_WORKITEM_PIB","No client info found for work item type %d table %08lu","An unexpected but recoverable event has occurred.","No action is required."
"U6RIB","5","PID_CHANGED","Client \%s\ register with new pid","A client re-registered with a new pid. This is likely if the client restarts. U6RIB accepted the re-registration.","No action is required."
"U6RIB","5","RES_MGR_CHANGE","Changed u6route-mem from (%d, %d) to (%d, %d)","The requested limit-resource command was adapted to fit the limits in this version. Parameters: Requested Min, Requested Max, New Min, New Max ...","No action is required."
"U6RIB","5","UNK_MSG_MINOR","Unrecognised %s message minor type %d","U6RIB received an unknown message. The message is dropped.","No action is required."
"U6RIB","5","UNK_MTS_OPC","%s thread - Unrecognised MTS opcode %d","U6RIB received an unknown message. The message is dropped Parameters: Thread name, Op-code ...","No action is required."
"U6RIB","6","GENERAL_INFO","%s","Informational message only.","No action is required."
"U6RIB","6","MTS_SHORT_MSG_ERROR","Received short (%d < %d) MTS message on %s queue with opcode %d, dropping it","U6RIB received an unknown message. The message is dropped.","No action is required."
"U6RIB","6","NH_DELETED_NIB_INFO","Found hidden next-hop %s (%d) for client \%s\ in deleted NIB","U6RIB found a hidden next-hop for the client While a client was deregistering for a table. Parameters: Next-hop, Interface, Client ...","No action is required."
"U6RIB","6","NO_MTS_PAYLOAD","Received MTS message with no payload in thread %s from sap %d, dropping it","U6RIB received an unknown message. The message is dropped.","No action is required."
"U6RIB","6","ROUTELIMIT_OVERFLOWED","Routing table statistic \%s\ overflowed 32 bits","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. Parameters: Statistic name ...","No action is required."
"U6RIB","6","ROUTELIMIT_RECOVERED","Number of routes (%llu) is below the configured limit (%lu)","The number of routes in the named routing table has fallen below the configured limit. The routing table has recovered Parameters: Current number of routes, Configured limit ...","No action is required."
"U6RIB","6","ROUTELIMIT_REINSTALL","Routing table was reinstalled","The routing table was automatically reloaded to allow the new routing limit or because the reinstall threshold was crossed.","No action is required."
"U6RIB","6","TRACE_OVERFLOW","Trace buffer %s overflowed","The given event trace overflowed. This is normal behavior. Parameters: Trace name ...","No action is required."
"URIB","2","API_INIT_SEM","Failed to init the client API semaphore: open: %s, create: %s","URIB could not create the semaphore that protects access to the shared memory between URIB and its clients. Parameters: Error from open, Error from create ...","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"URIB","2","BAD_PT","Possible Patricia tree corruption in %s","An unrecoverable software error has occurred because of a bad route table.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"URIB","2","NOPMEM","Failed to allocate private memory for %s","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.","Configure the network or router to decrease the number of routes, or add additional memory to the router."
"URIB","2","NOSMEM","Failed to allocate shared memory for %s","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.","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 <min> max <max> limit-resource u6route-mem min <min> max <max>."
"URIB","2","RES_MGR","Error returned from %s, errno: 0x%08x (%s) in %s()","The resource manager returned an error to URIB, while URIB was performing an action relating to its shared memory Parameters: RM Function, Error Code, Error Description, Calling Function ...","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"URIB","2","STARTUP_FAILURE","Startup failure: %s","An unrecoverable software error has occurred during URIB startup.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"URIB","2","TIMER_LIB","%s %s","The timer library returned an error, causing an unrecoverable problem for URIB.","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"URIB","2","TOO_MANY_CLIENTS","%s client \%s\","URIB cannot add this client because the URIB client limit has already been reached. Parameters: Resource, Client ...","Restart the component when the system is working."
"URIB","3","ADD_ERROR","Client \%s\ could not add %s/%d to the %s","A error was encountered. The system may run into more errors because of this problem. Parameters: Client, Prefix, Length, Target ...","Use the 'system switchover' command to switchover to the standby supervisor. If no standby is present, or the standby is not ready, use the 'reload' CLI command to reload the system. The state of the standby can be checked using the 'show system redundancy ha status' CLI command."
"URIB","3","ADD_PATH_ERROR","%s: could not add path for client \%s\.","A route add operation has failed for the given client. There may be a previous error message that further explains the problem. Parameters: Function, Client ...","No action is required."
"URIB","3","ADD_RPATH","Client \%s\ added %s/%u via not found rnh %s/%u%%%s","A route add operation has failed for the given client. This may be a transient error. Parameters: Client, Prefix, Mask-len, Recursive Prefix, Recursive Mask-len, Table ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"URIB","3","ADD_TPATH","Client \%s\ added %s/%u via tableid 0x%08x : %s","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. Parameters: Client, Prefix, Mask-len, Table-Id, Error ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"URIB","3","ADD_TPATH_ROUTE","Client \%s\ added %s/%u%%%s","A route add operation has failed for the given client. This was because the route could not be found. This may be a transient error. Parameters: Client, Prefix, Mask-len, Table-name ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"URIB","3","ASSERT_ERROR","%s:%d: Assertion \%s\ failed.","An internal software error has occurred. An assertion held to be true failed. Parameters: Filename, Line number, Expression ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"URIB","3","AVLADD_ERROR","Could not add %s (0x%08x) to the %s avl","URIB was unable to add a piece of data to an AVL data structure. Parameters: Data item, Memory address, Data structure ...","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"URIB","3","AVLINIT_ERROR","Could not init %s avl for VRF %s","URIB was unable to correctly initialize an AVL data structure. Parameters: AVL name, VRF-name ...","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"URIB","3","CMI_MTSSEND_FAILURE","mts_send failure for client %s: %s","URIB was unable to send MTS message to a particular client Parameters: Client name, Error ...","Use the 'system switchover' command to switchover to the standby supervisor. If no standby is present, or the standby is not ready, use the 'reload' CLI command to reload the system. The state of the standby can be checked using the 'show system redundancy ha status' CLI command."
"URIB","3","CMI_PAYLOAD_CONV_ERR","CMI payload conversion error failure from %s order to %s order","The cmi payload conversion did not occur successfully. Parameters: order, order ...","No action is required."
"URIB","3","COPY_ERROR","Could not copy %s for %s/%d","A error was encountered during route optimization. The system may run into more errors because of this problem.","No action is required."
"URIB","3","DEL_ERROR","Could not delete %s/%d from %s","A error was encountered. The system may run into more errors because of this problem.","Use the 'system switchover' command to switchover to the standby supervisor. If no standby is present, or the standby is not ready, use the 'reload' CLI command to reload the system. The state of the standby can be checked using the 'show system redundancy ha status' CLI command."
"URIB","3","DEL_PATH_ERROR","%s: could not del path for client \%s\.","A route add operation has failed for the given client. There may be a previous error message that further explains the problem. Parameters: Function, Client ...","No action is required."
"URIB","3","EPID_MIS_MATCH_ERROR","\%s\ epid (%u) does not match known epid (%u)","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. Parameters: Client, Expected epid, Received epid ...","Use the 'restart' command to restart the feature and clear this problem."
"URIB","3","FILE_OPEN_ERROR","File open error: %s","This message is for internal debugging only.","No action is required."
"URIB","3","FILE_WRITE_ERROR","File write error: %s","This message is for internal debugging only.","No action is required."
"URIB","3","GENERAL_CRIB_ERROR","%s","CRIB not in use.","No action is required."
"URIB","3","GENERAL_PTHREAD_ERROR","Thread %d: %s","The POSIX pthread library returned an error to URIB. Parameters: Thread name, Thread operation ...","Use the 'system switchover' command to switchover to the standby supervisor. If no standby is present, or the standby is not ready, use the 'reload' CLI command to reload the system. The state of the standby can be checked using the 'show system redundancy ha status' CLI command."
"URIB","3","GENERAL_UI_ERROR","%s","The shown error occurred while the user interface was processing a request. The request should be tried again. Parameters: Error ...","Requires operator to retry the request."
"URIB","3","GET_INSTANCE_ERROR","instance not found for client \%s\ in VRF %s","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 <vrf-name>' Parameters: Client, VRF ...","Requires operator to intervene."
"URIB","3","HTADD_ERROR","Could not add %s to the %s hash table","A severe hash table error was encountered. The system may run into more errors because of this problem.","Use the 'system switchover' command to switchover to the standby supervisor. If no standby is present, or the standby is not ready, use the 'reload' CLI command to reload the system. The state of the standby can be checked using the 'show system redundancy ha status' CLI command."
"URIB","3","INCONSISTENT_RNH","%s: %s/%d","Unexpected remaining recursive next-hop removed during RIB cleanup Parameters: Owner, Prefix, Length ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"URIB","3","INCONSISTENT_ROUTE","%s: %s/%d via %s","Unexpected remaining route removed during RIB cleanup. Parameters: Owner, Prefix, Length, Next-hop ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"URIB","3","INCONSISTENT_STRUCTURE","%s","Unexpected remaining state removed during RIB cleanup.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"URIB","3","INCONSISTENT_SUMMARY","%s: routes %d, rnh's %d","Unexpected remaining state for client during RIB cleanup. Use the 'show routing ipv4 unicast internal event-history errors' command for more information. Parameters: Owner, Routes, RNHs ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"URIB","3","INSTANCE_CREATE_ERROR","Failed to create routing instance info for client \%s\, VRF %s","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 <vrf-name>' Parameters: Client, VRF ...","Requires operator to intervene."
"URIB","3","KSINK_LIB_ERROR","%s %s","A error was encountered during ksink operations. The system may run into more errors because of this problem.","No action is required."
"URIB","3","LABELCOUNT_UNDERFLOW","Label count tried to underflow for %s","The client tried to decrement the current number of labels, but the statistic was already zero. Parameters: Pib ...","No action is required."
"URIB","3","MOD_ERROR","Client \%s\ could not modify %s/%d: %s","A error was encountered. The system may run into more errors because of this problem. Parameters: Client, Prefix, Length, Reason ...","Use the 'system switchover' command to switchover to the standby supervisor. If no standby is present, or the standby is not ready, use the 'reload' CLI command to reload the system. The state of the standby can be checked using the 'show system redundancy ha status' CLI command."
"URIB","3","MORE_INFO_ERROR","Client \%s\: %s","This error provides further information about the previous error. Action should be taken depending on the previous error logged. Parameters: Client, Message ...","No action is required."
"URIB","3","MORE_MTS_INFO_ERROR","source SAP is: %d dest SAP is: %d","This error provides further information about the previous MTS error. Action should be taken depending on the previous MTS error logged.","No action is required."
"URIB","3","MTS_BIND","mts_bind failed for %s: %s","URIB was unable to bind to an MTS queue SAP, causing an unrecoverable error. Parameters: MTS queue name, Error ...","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"URIB","3","MTS_DEREGISTER","mts_deregister failed for urib: %s","URIB was unable to deregister client from URIB notifications, causing an unrecoverable error.","Use the 'restart' command to restart the feature and clear this problem."
"URIB","3","MTS_DROP","Error returned from mts_drop(), error: %s","An MTS API returned an error when URIB tried to drop a message.","No action is required."
"URIB","3","MTS_NO_CLIENT_SAP","%s: client \%s\ has not provided a SAP for ack","A client registered with URIB, but did not provide a SAP for URIB to send reply messages to. This caused an unrecoverable error.","Use the 'restart' command to restart the feature and clear this problem."
"URIB","3","MTS_NO_PAYLOAD_ERROR","Received MTS message with no payload on %s queue with opcode %d, dropping it. src SAP: %d dst SAP: %d","URIB received an unknown message. The message is dropped.","No action is required."
"URIB","3","MTS_OPTIONS","MTS option set failed for opcode %s: %s (%d)","URIB was unable to set options for an MTS opcode Parameters: Requestor, Error String, Error ...","Use the 'system switchover' command to switchover to the standby supervisor. If no standby is present, or the standby is not ready, use the 'reload' CLI command to reload the system. The state of the standby can be checked using the 'show system redundancy ha status' CLI command."
"URIB","3","MTS_RECV","Error returned from mts_recv(%s), errno: %s","An MTS API returned an error while URIB was receiving on an MTS queue. Parameters: Queue name, Error ...","No action is required."
"URIB","3","MTS_REGISTER","mts_register failed for urib: %s","URIB was unable to register client for URIB notifications, causing an unrecoverable error.","Use the 'restart' command to restart the feature and clear this problem."
"URIB","3","MTS_SHORT_MSG_ERROR","Received short (%d < %d) MTS message on %s queue with opcode %d, dropping it. src SAP: %d dst SAP: %d","URIB received an unknown message. The message is dropped.","No action is required."
"URIB","3","MTS_SIZE_ERROR","%s: incorrect %s message size from client %s: %d (should be %d)","The size of a URIB message is incorrect for the type of message. The message is dropped.","No action is required."
"URIB","3","MTS_UBIND","mts_unbind failed for %s: %s","URIB was unable to unbind from an MTS queue SAP, causing an unrecoverable error. Parameters: MTS queue name, Error ...","Use the 'system switchover' command to switchover to the standby supervisor. If no standby is present, or the standby is not ready, use the 'reload' CLI command to reload the system. The state of the standby can be checked using the 'show system redundancy ha status' CLI command."
"URIB","3","MTS_UNK_OPC","Received unknown MTS message on %s queue with opcode %d, dropping it. src SAP: %d dst SAP: %d","URIB received an unknown message. The message is dropped Parameters: Queue name, Op-code, SAP number, SAP number ...","No action is required."
"URIB","3","NH_RESOLV_ADD_ERROR","Could not add %s/%d to the %s (%d) resolve buffer","A error was encountered. The system may run into more errors because of this problem.","Use the 'system switchover' command to switchover to the standby supervisor. If no standby is present, or the standby is not ready, use the 'reload' CLI command to reload the system. The state of the standby can be checked using the 'show system redundancy ha status' CLI command."
"URIB","3","NO_L3VM_INFO_ERROR","no L3VM info for table id 0x%08x from client \%s\ - unknown to L3VM","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. Parameters: Table-Id Client name ...","Use the 'restart' command to restart the feature and clear this problem."
"URIB","3","NO_L3VM_LIMITS","Could not get routing table limits from L3VM","URIB could not pull the routing limits for the table. L3VM should be restarted.","Use the 'restart' command to restart the feature and clear this problem."
"URIB","3","NOT_INIT_L3VM_ERROR","L3VM info for table id 0x%08x from client \%s\ not available - URIB not initialised with L3VM","A client tried to add some information to the URIB, before URIB has registered for the table information. The client should be restarted. Parameters: Table-Id, Client name ...","Use the 'restart' command to restart the feature and clear this problem."
"URIB","3","OPEN_CLIENT_SHM_ERROR","Failed to open client shared memory \%s\: %s","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'. Parameters: Name of shared memory region ...","Use the 'restart' command to restart the feature and clear this problem."
"URIB","3","PSS","Error returned from %s, errno: 0x%08x (%s) in %s()","URIB called a PSS API which returned an error. The error reported should be examined for the cause. Parameters: Failed API, Error Code, Error Description, URIB Function ...","Use 'reload' command to reload the system. Be aware that this problem affects all VDCs on the system."
"URIB","3","PTADD_ERROR","Could not add %s/%d to the %s pt, error code %d","A severe route table error was encountered. The system may run into more errors because of this problem.","Use the 'system switchover' command to switchover to the standby supervisor. If no standby is present, or the standby is not ready, use the 'reload' CLI command to reload the system. The state of the standby can be checked using the 'show system redundancy ha status' CLI command."
"URIB","3","PTDEL_ERROR","Could not delete %s/%d from the URIB pt, error code %d","A severe route table error was encountered. The system may run into more errors because of this problem.","Use the 'system switchover' command to switchover to the standby supervisor. If no standby is present, or the standby is not ready, use the 'reload' CLI command to reload the system. The state of the standby can be checked using the 'show system redundancy ha status' CLI command."
"URIB","3","QADD_ERROR","Could not add %s to the %s queue","A severe queue error was encountered. The system may run into more errors because of this problem.","Use the 'system switchover' command to switchover to the standby supervisor. If no standby is present, or the standby is not ready, use the 'reload' CLI command to reload the system. The state of the standby can be checked using the 'show system redundancy ha status' CLI command."
"URIB","3","RANGE_CHECK_ERR","Range check of %s failed from %s (0x%08x)","The value provided is outside of the acceptable range. Parameters: Range, Provider of value, Value Provided ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"URIB","3","RNH_LOOP_ERROR","Number of prefixes forming rnh loop exceeds %d\n Flagging route %s/%d from client \%s\ with rnh %s/%d\n as causing rnh loop","URIB detected a loop between routes installed in the RIB. The message shows which client caused the loop. Parameters: Max RNH Loop, Prefix, Prefix Length, Client, Prefix, Prefix Length ...","Requires operator to intervene."
"URIB","3","RNH_REFCOUNT","Client \%s\ deleting RNH %s/%u with refcount %u","A client tried to delete a Recursive Next-hop while that RNH was still in use. Parameters: Client, Prefix, Mask-len, Reference count ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"URIB","3","ROUTECOUNT_UNDERFLOW","Routing table statistic current tried to underflow deleting %s/%d","The system tried to decrement the current number of routes in the table, but the statistic was already zero. Parameters: Prefix, Mask Len ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"URIB","3","RPM_LIB_ERROR","%s %d","An RPM library function returned an error. Parameters: Function, RPM Error Code ...","No action is required."
"URIB","3","SDWRAP_LIB_ERROR","%s %s","A SDWrap library function returned an error. Parameters: Function, SDWrap Error Code ...","No action is required."
"URIB","3","SEND_FROM_ERROR","Send from URIB to client \%s\ failed: %s","URIB was unable to send a message to the shown client. Parameters: Client, Error ...","Use the 'restart' command to restart the feature and clear this problem."
"URIB","3","SEND_NOTIF_ERROR","Failed to send %s notification buffer to client \%s\; retried %lu times","URIB was unable to send a notification to a client. Parameters: Type of Notify, Client, Retries ...","Use the 'restart' command to restart the feature and clear this problem."
"URIB","3","SEND_TO_ERROR","Send to URIB failed: %s","The calling process was unable to send a message to URIB.","Use the 'restart' command to restart the feature and clear this problem."
"URIB","3","TABLE_CREATE_ERROR","Failed to create table info for VRF %s for client \%s\","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 <vrf-name>' Parameters: VRF, Client ...","Requires operator to intervene."
"URIB","3","TABLE_STATE_ERROR","Table state %s for VRF %s for client \%s\","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 Parameters: State, VRF, Client ...","Requires operator to intervene."
"URIB","3","UFDM_MTSSEND_FAILURE","MTS send; to UFDM failed with unexpected error %d","URIB was unable to send a route update to UFDM. This means there will be a route missing from the FIB.","Use the 'system switchover' command to switchover to the standby supervisor. If no standby is present, or the standby is not ready, use the 'reload' CLI command to reload the system. The state of the standby can be checked using the 'show system redundancy ha status' CLI command."
"URIB","3","UNEXPECTED_MESSAGE","%s %d. src SAP: %d dst SAP: %d","An unexpected interprocess message was received.","No action is required."
"URIB","3","XRI_TYPE_ERROR","Unknown XRI type %u","URIB detected unknown eXtended route information while displaying a next-hop address.","No action is required."
"URIB","4","INVALID_PIB","%s %s","A bad protocol information block was encountered in the given situation. Parameters: Situation, Message ...","No action is required."
"URIB","4","NH_RESOLV_LUKUP","Could not find %s/%d while processing %s (%d) resolve buffer","Unresolved nexthop not cleaned up properly.","No action is required."
"URIB","4","NHLFE_OWNER","%s/%d via %s%%%s: NHLFE owner changed from client \%s\ to \%s\","A given path can only have one Next-Hop Label Forwarding Entry. Thus this warning indicates that configuration has generated a conflict. Parameters: Prefix, Prefix Length, Next-hop, Interface, Original Client, New Client ...","Requires operator to intervene."
"URIB","4","ROUTELIMIT_EXCEEDED","Number of routes (%llu) reached or exceeds configured limit (%lu); dropped (%llu)","The number of routes in the named routing table has reached the configured limit. No further routes will be added to the table Parameters: Current number of routes, Configured limit, Dropped routes ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"URIB","4","ROUTELIMIT_NOT_ENFORCED","Number of routes (%llu) already exceeds newly configured limit (%lu); dropped (%llu)","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. Parameters: Current number of routes, Configured limit, Dropped routes ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"URIB","4","ROUTELIMIT_WARNING","Number of routes (%llu) exceeds warning limit (%lu)","The number of routes in the named routing table has reached the configured warning limit. Parameters: Current number of routes, Warning limit ...","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"URIB","4","RTDEL_ERROR","Could not find prefix %s/%d, client \%s\sdeleterequest'","Route delete request was received for a non-existing route. Parameters: Prefix, Prefix Length, Client ...","No action is required."
"URIB","4","UFDM_ACKNOT_FOUND","Could not find UFDM buffer with ptr 0x%08x","Ack received for a UFDM buffer that URIB does not know about. Parameters: Memory address of UFDM buffer ...","No action is required."
"URIB","4","UNEXPECTED_VALUE","Unexpected value for %s","An unexpected value was encountered for the logged event.","No action is required."
"URIB","4","XL_LICENSE_MEMORY","XL License installed; use \show routing memory estimate\ and see VDC resource u4route-mem documentation.","An XL License was just installed in the system. The memory currently configured for URIB may not be big enough to hold all the routes the hardware can install. Check VDC resource u4route-mem, then switchover to apply.","No action is required."
"URIB","4","ZERO_NEXTHOP","Client \%s\ added 0.0.0.0 next hop and interface %s is not point-to-point","The client protocol added a 0.0.0.0 next-hop address on a nonpoint-to-point interface Parameters: Client, Interface ...","No action is required."
"URIB","5","API_INIT_SEM_CLEAR","Cleared the API semaphore from %d","The API semaphore was in an unexpected state, and was restored to a correct value. Parameters: Value of semaphore ...","No action is required."
"URIB","5","BOGUS_INTF","Client \%s\ tried to add %s/%d via %s with invalid iod %d","A bad interface was received in a path add from the client. Parameters: Client, Prefix, Prefix Length, Next-hop, Iod ...","Use the 'restart' command to restart the feature and clear this problem."
"URIB","5","BOGUS_MASK","Client \%s\ tried to add %s/%d","A bogus mask was received from the client. Parameters: Client, Prefix, Prefix Length ...","Use the 'restart' command to restart the feature and clear this problem."
"URIB","5","BOGUS_PREFIX","\%s\ tried to add %s/%d","A bogus prefix was received from the client. Parameters: Client, Prefix, Prefix Length ...","Use the 'restart' command to restart the feature and clear this problem."
"URIB","5","BOGUS_RNH","\%s\ tried to add %s/%d with RNH %s/%d","A bogus update with unexpected RNH was received from the client. Parameters: Client, Prefix, Prefix Length, RNH, RNH Length ...","Use the 'restart' command to restart the feature and clear this problem."
"URIB","5","GENERAL_FAILURE","Failed to %s","The logged action failed, causing an unrecoverable error. ; Recommened action: Use the 'system switchover' 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.","Contact the Cisco Technical Assistance Center (TAC) through the Cisco Support web site http://www.cisco.com/tac."
"URIB","5","PATH_DELETE","Could not find %s for client \%s\, prefix %s/%d nexthop %s, %s","URIB could not find the path that a client tried to delete. Parameters: Structure, Client, Prefix, Prefix Length, Next-hop, Interface ...","No action is required."
"URIB","5","RES_MGR_CHANGE","Changed u4route-mem from (%d, %d) to (%d, %d)","The requested limit-resource command was adapted to fit the limits in this version. Parameters: Requested Min, Requested Max, New Min, New Max ...","No action is required."
"URIB","5","RPATH_DELETE","Could not find %s for client \%s\, prefix %s/%d rnh %s/%u","URIB could not find the recursive path that a client tried to delete. Parameters: Structure, Client, Prefix, Prefix Length, Recursive Prefix, Recursive Mask-len ...","No action is required."
"URIB","6","GENERAL_INFO","%s","Informational message only.","No action is required."
"URIB","6","NH_DELETED_NIB_INFO","Found hidden rnh %s/%d for client \%s\ in deleted NIB","URIB found a hidden next-hop for a client while the client was deregistering for a table. Parameters: Prefix, Mask Length, Interface, Client ...","No action is required."
"URIB","6","ROUTELIMIT_OVERFLOWED","Routing table statistic \%s\ overflowed 32 bits","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. Parameters: Statistic name ...","No action is required."
"URIB","6","ROUTELIMIT_RECOVERED","Number of routes (%llu) is below the configured limit (%lu)","The number of routes in the named routing table has fallen below the configured limit. The routing table has recovered Parameters: Current number of routes, Configured limit ...","No action is required."
"URIB","6","ROUTELIMIT_REINSTALL","Routing table was reinstalled","The routing table was automatically reloaded to allow the new routing limit or because the reinstall threshold was crossed.","No action is required."
"URIB","6","TRACE_OVERFLOW","Trace buffer %s overflowed","The given event trace overflowed. This is normal behavior. Parameters: Trace name ...","No action is required."
"URIB","6","UFDM_MGMT","Route %s/%d in VRF management not sent to ufdm","URIB tried to give a route in the management VRF to UFDM Parameters: Prefix, Prefix Length ...","No action is required."
"AAA","1","AAA_SESSION_LIMIT_REJECT","aaa request rejected as maximum aaa sessions are in progress","Aaa request rejected as the limit for maximum concurrent aaa sessions is reached","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"AAA","2","AAA_NVRAM_UPGRADE_FAILURE","upgrading of accounting log failed. [chars]","Upgrading of accounting log failed.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"AAA","2","AAA_PROGRAM_EXIT","aaa daemon exiting: [chars]","Aaa daemon is exiting.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"AAA","3","AAA_NVRAMFAILURE","nvram failure","Nvram can not be read/written to. Hence accounting log can not be stored there","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"AAA","6","AAA_ACCOUNTING_MESSAGE","[chars]","Accounting Message","No action is required."
"AAM","2","ELS_FC2_GL_SINDEX_LOOKUP_FAILED","Failed to lookup global port index for interface [[chars]]","Failed to lookup global port index for interface [chars]","No action is required."
"AAM","3","ALLOC_FAILED","Failed in File:[chars] Line:[dec] for type [dec] size [dec]","AAM process could not allocate heap memory in File:[chars], at line:[dec], for memory-type:[dec] of Size:[dec]","No action is required."
"AAM","3","ASSERTION_FAILED","Failed in File:[chars] Line:[dec]","AAM Process assertion failed in File:[chars], at line:[dec]","No action is required."
"ACLLOG","4","ACLLOG_MAXFLOW_REACHED","[chars]","Max flow reached in current interval: [chars]","No action is required."
"ACLLOG","4","ACLLOG_THRESHOLD","[chars]","Threshold Reached for Flow: [chars]","No action is required."
"ACLLOG","6","ACLLOG_FLOW_INTERVAL","[chars]","Flow info in current alert interval: [chars]","No action is required."
"ACLLOG","6","ACLLOG_NEW_FLOW","[chars]","New Acllog Flow: [chars]","No action is required."
"ACLMGR","2","ACLMGR_COMMIT_FAIL","Commit failed: [chars]","The PPF commit failed","No action is required."
"ACLMGR","2","ACLMGR_NO_ERRDISABLED","[chars] event on interface [chars] ([hex]) allowed to succeed in spite of access-list failure","Although an access-list operation failed during a port event, the port event still finished successfully because errdisable is disallowed","No action is required."
"ACLMGR","2","EXITING","Exit reason: [chars]","The ACLMGR service process has exited due to [char]. The process has probably been restarted automatically.","No action is required."
"ACLMGR","2","INITFAIL","ACLMGR Service Init failed: [chars]","ACLMGR Service initialization failed. [chars] explains the reason for the failure.","No action is required."
"ACLMGR","2","MALLOC_ERROR","Size [dec] bytes","The ACLMGR service could not allocate memory.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"ACLMGR","2","PSS_ERROR","[chars]: PSS ret. val=[dec]","The ACLMGR service encountered error while operating on a persistent storage database.","No action is required."
"ACLMGR","3","ACLMGR_DB_LOCK_MSG","ACL database message, reason: [chars], session 0x%llx, type: [chars]","ACL PPF database lock acquire/release related message.","No action is required."
"ACLMGR","3","ACLMGR_GSYNC_ERROR","Error occured during global sync of ACL runtime database to standby, reason: [chars] , [chars]","ACL snapshot to send the copy of runtime database to standby failed","No action is required."
"ACLMGR","3","ACLMGR_PPF_ERROR","PPF error: [chars]","The PPF generated error","No action is required."
"ACLMGR","3","ACLMGR_PSS_CORRUPTED","[chars] PSS found corrupted","The ACLMGR service has detected corruption in one of its persistent information database. The database would be recreated.","No action is required."
"ACLMGR","3","ACLMGR_STAT_CONSOLIDATION_FAILURE","ACL statistic parsing or consolidation failed","A statistic update failed during the parsing or consolidation step; statistics may have been lost","No action is required."
"ACLMGR","3","ACLMGR_VACL_REDIRECTION_DISABLED_REMOVAL","VACL redirection to interface [chars] ([hex]) disabled: the port has been removed","A VACL redirection to the port has been deactivated because the port has been removed","No action is required."
"ACLMGR","3","ACLMGR_VERIFY_FAIL","Verify failed: [chars]","The PPF Verify failed","No action is required."
"ACLMGR","3","ACLMGR_COMMIT_FAIL","Commit failed: [chars]","The PPF commit failed","No action is required."
"ACLMGR","3","MTSERROR","[chars]","ACLMGR Service encountered an MTS error. [chars] specifies the context where the error occured.","No action is required."
"ACLMGR","4","ACLMGR_PPF_WARNING","PPF warning: [chars]","The PPF generated warning","No action is required."
"ACLMGR","4","ACLMGR_VACL_REDIRECTION_DISABLED_PCM","VACL redirection to interface [chars] ([hex]) disabled: the port became a portchannel member","A VACL redirection to the port has been temporarily deactivated because it is now a member in a port channel","No action is required."
"ACLMGR","4","PSS_VERSION_MISMATCH","PSS [dec] Code [dec]","There was a version mismatch between the ACLMGR service and one of its persistent storage databases. The persistent information has been translated to the new format.","No action is required."
"ACLMGR","6","ACLMGR_PPF_NOTIF","PPF notification: [chars]","The PPF generated notification","No action is required."
"ACLMGR","6","BECAME_ACTIVE","Became ACTIVE from standby mode","The ACLMGR service on the standby supervisor became active and it is ready to serve client requests.","No action is required."
"ACLMGR","6","BECAME_STDBY","Became STANDBY from active mode","The ACLMGR service became standby from active mode.","No action is required."
"ACLMGR","6","FAILED_TO_SEND_HEARTBEAT","Failed to send heartbeat to system manager: Reason=[chars]","The ACLMGR service was unable to send heartbeat to the system manger","No action is required."
"ACLMGR","6","SERVICE_UP","Initialized [chars]","The ACLMGR service is up and ready The service was initialized in [char] mode.","No action is required."
"ACLMGR","6","SRVEXIT","ACLMGR Service shutting down gracefully","ACLMGR Service is shutting down gracefully. This is an informational message.","No action is required."
"ACLMGR","6","SWITCHOVER","Switching Over to other Sup.","The ACLMGR service has successfully switched over to the standby supervisor card.","No action is required."
"ACLQOS-SLOT#","2","ACLQOS_FAILED","ACLQOS failure: [chars]","ACLQOS operation failed in the aclqos client","No DDTS."
"ACLQOS-SLOT#","2","ACLQOS_INBAND_INTERFACE_FAILURE","Inband interface lif lookup failed ([chars])","Inband interface lif lookup failed","No DDTS."
"ACLQOS-SLOT#","2","ACLQOS_MALLOC_FAILED","Memory allocation failed. [chars]","Memory allocation failed. This is a critical failure","No DDTS."
"ACLQOS-SLOT#","2","ACLQOS_OOTR","Tcam resource exhausted: [chars]","Tcam resources to program acls exhausted","No DDTS."
"ACLQOS-SLOT#","2","PPF_FAILED","Database failure: [chars]","Database operation failed in the aclqos client","No DDTS."
"ACLQOS-SLOT#","3","ACLQOS_CC_INVALID","Invalid Congestion Control parameters: [chars]","Invalid Congestion Control parameters","No DDTS."
"ACLQOS-SLOT#","3","ACLQOS_MCM_ERROR","MCM Message Inconsistent. Please collect MCM and ACLMgr Tech Support for all VDCs","MCM Message Inconsistent","No DDTS."
"ACLQOS-SLOT#","3","ACLQOS_PAUSE_INVALID","Invalid Pause parameters: [chars]","Invalid Pause parameters","No DDTS."
"ACLQOS-SLOT#","3","ACLQOS_QUEUING_ERROR","ACL/QoS queuing error: [chars]","Internal error in ACL/QoS queuing config","No DDTS."
"ACLQOS-SLOT#","4","ACLQOS_ATOMIC_ERR","[chars]","Tcam will be overused, please turn off atomic update","No DDTS."
"ACLQOS-SLOT#","4","ACLQOS_BC_OVER_THRESHOLD","Bank Chaining enabled: Inst [dec]susagehasreacheditsthreshold'","Tcam is almost full","No DDTS."
"ACLQOS-SLOT#","4","ACLQOS_FC_WARNING","Found stale FCoE entry in instance [dec]. VSAN: [dec], SID: [hex], DID: [hex], SI:[dec], SI_MASK:[dec], RW_VSAN: [dec], RW_VSAN_FLAG: [dec], RW_SID: [hex], RW_SID_FLAG: [dec], RW_DID: [hex]. RW_DID_FLAG: [dec] Cleaning it up.","Found stale FCoE entry in instance [dec]. VSAN: [dec], SID: 0x[hex], DID: 0x[hex], SI:[dec], SI_MASK:[dec], RW_VSAN:[dec], RW_VSAN_FLAG: [dec], RW_SID: 0x[hex], RW_SID_FLAG:[dec], RW_DID: 0x[hex]. RW_DID_FLAG: [dec] Cleaning it up.","No DDTS."
"ACLQOS-SLOT#","4","ACLQOS_MATCH_ALL_MERGE_UPDATE","Warning (match_all merging): [chars]","Warning (match_all merging)","No DDTS."
"ACLQOS-SLOT#","4","ACLQOS_OVER_THRESHOLD","Inst [dec] Tcam [dec] Bank [dec]susagehasreacheditsthreshold'","Tcam is almost full","No DDTS."
"ACLQOS-SLOT#","4","ACLQOS_QUEUING_COS2Q_INVALID","ACL/QoS invalid queuing policy because of cos map change: [chars] queue [chars], interface [chars]","Attemped to configure an invalid queuing policy","No DDTS."
"ACLQOS-SLOT#","4","ACLQOS_QUEUING_INVALID","ACL/QoS invalid queuing policy: [chars]","Attemped to configure an invalid queuing policy","No DDTS."
"ACLQOS-SLOT#","4","ACLQOS_UNDER_THRESHOLD","Tcam [dec] Bank [dec]'s usage is below the threshold now","Tcam's usage is below the threshold","No DDTS."
"ACLQOS-SLOT#","4","ACLQOS_WARNING","ACLQOS Warning: [chars]","ACLQOS Warnings","No DDTS."
"ACLQOS-SLOT#","5","ACLQOS_DISRUPTIVE_IPv6_UPDATE","Disruptive update of IPv6 compression entries","Disruptive IPv6 compression entries update","No DDTS."
"ACLQOS-SLOT#","5","ACLQOS_NON_ATOMIC","Non atomic ACL/QoS policy update done for [chars]","Non atomic ACL/QoS policy update was done","No DDTS."
"ACLTCAM","2","ACL_TCAM_ADJ_EXHAUSTED","ACLTCAM failed to program route for VSAN: [dec], SID: [chars] DID: [chars], error: [chars].","ACLTCAM process experienced a failure while programming route for VSAN [dec] SID [chars] DID [chars] due to resource exhaustion. [chars] is the error code.","No action is required."
"ACLTCAM","2","ACL_TCAM_ALMOST_FULL","TCAM close to FULL. [chars] TCAM Usage ([dec]/[dec]) exceeded [dec]% fwd-eng: [dec], [chars]","[chars] TCAM usage [dec]/[dec] exceeded [dec] percent on fwd-engine [dec], [chars]","No action is required."
"ACLTCAM","2","ACL_TCAM_CONFIG_READ_FROM_DRIVER_FAILED","[chars] [dec], Error: [hex].","Unable to read configuration from forwarding engine ASIC driver. [chars] [dec], Error: 0x[hex].","No action is required."
"ACLTCAM","2","ACL_TCAM_CONFIG_WRITE_TO_DRIVER_FAILED","[chars] [dec], Error: [hex].","Unable to write configuration to forwarding engine ASIC driver. [chars] [dec], Error: 0x[hex].","No action is required."
"ACLTCAM","2","ACL_TCAM_FLOW_STATS_READ_FAILED","Hardware flow stats read failed(ASIC: [dec], [chars] TCAM, Address: [dec], Num Entries: [dec], Error: [chars]).","Hardware flow stats read failed(ASIC: [dec], [chars] TCAM, Address: [dec], Num Entries: [dec] Error: [chars]).","No action is required."
"ACLTCAM","2","ACL_TCAM_INCONSISTENT_DATABASE","Database found inconsistent.","Database found inconsistent.","No action is required."
"ACLTCAM","2","ACL_TCAM_INCONSISTENT_TCAM_CONTENTS","TCAM contents found inconsistent.","TCAM contents are found inconsistent.","No action is required."
"ACLTCAM","2","ACL_TCAM_INIT_FAILED","Initialization failed for forwarding engine ASIC: [dec], [chars] TCAM.","Initialization failed for forwarding engine ASIC [dec], in [chars] TCAM.","No action is required."
"ACLTCAM","2","ACL_TCAM_INIT_REGIONS_FAILED","Initialization failed for forwarding engine ASIC: [dec], [chars] TCAM, [chars] Region.","Initialization of regions failed for forwarding engine ASIC [dec], in [chars] TCAM, for [chars] Region.","No action is required."
"ACLTCAM","2","ACL_TCAM_MALLOC_FAILURE","Memory allocation failed for size [dec].","Memory allocation is failed for size [dec] bytes.","Restart the process."
"ACLTCAM","2","ACL_TCAM_MTS_FAILURE","MTS operation failed: [chars].","MTS operation failed. [chars] is the reason.","No action is required."
"ACLTCAM","2","ACL_TCAM_MTS_Q_FULL","MTS queue for SAP [dec] is full","MTS queue for SAP [dec] is full","No action is required."
"ACLTCAM","2","ACL_TCAM_MTS_REGISTRATION_FAILED","MTS registration failed for opCode: [dec].","MTS registration failed for opCode: [dec].","No action is required."
"ACLTCAM","2","ACL_TCAM_NO_ROUTE","ACLTCAM failed to get route for VSAN: [dec], Rewrite: [chars] DID: [chars] DID MASK: [chars], error: [hex].","ACLTCAM process experienced a failure while getting route for VSAN [dec] Rewrite [chars] DID [chars] DID Mask [chars]. [hex] is the error code.","No action is required."
"ACLTCAM","2","ACL_TCAM_NO_TCAM_LEFT","ACLTCAM resource exhausted for interface : [chars]","ACLTCAM hardware resource is completely used.","No action is required."
"ACLTCAM","2","ACL_TCAM_PHY_TCAM_READ_FAILED","[chars] read from hardware TCAM failed(ASIC: [dec], [chars] TCAM, Address: [dec], Num Entries: [dec], Error: [chars]).","[chars] read from hardware TCAM failed(ASIC: [dec], [chars] TCAM, Address: [dec], Num Entries: [dec] Error: [chars]).","No action is required."
"ACLTCAM","2","ACL_TCAM_PHY_TCAM_READ_INVALID","Invalid([chars], value: [dec]) TCAM entry read from hardware TCAM (FWD-Engine: [dec], [chars] TCAM, Address: [dec]), Ignoring this entry.","Invalid([chars], value: [dec]) TCAM entry from hardware TCAM(FWD-Engine: [dec], [chars] TCAM, Address: [dec]) Ignoring this entry","No action is required."
"ACLTCAM","2","ACL_TCAM_PHY_TCAM_WRITE_FAILED","[chars] write to hardware TCAM failed(ASIC: [dec], [chars] TCAM, Address: [dec], Num Entries: [dec], Error: [chars]).","[chars] write to hardware TCAM failed(ASIC: [dec], [chars] TCAM, Address: [dec], Num Entries: [dec] Error: [chars]).","No action is required."
"ACLTCAM","2","ACL_TCAM_PSS_FAILURE","Failed to do PSS operation: [chars], reason: [hex].","Failed to do PSS operation [chars]. [hex] is the reason.","No action is required."
"ACLTCAM","2","PSS_OPEN_FAILED","PSS open failed - [hex].","Persistent database handle could not obtained for ACLTCAM. [hex] is the error.","No action is required."
"ACLTCAM","2","RECONS_FAILED","Reconstruction of TCAM contents failed during upgrade - [hex].","During non-disruptive upgrade, the ACLTCAM contents are not properly reconstructed. [hex] is the error.","No action is required."
"ACLTCAM","3","ACL_TCAM_INV_TCAM_SYNC_ATTEMPT","Attempt to write invalid shadow entry: [dec] ([dec]/[dec]) to TCAM, fwd-engine: [dec] ([chars]), change-array: [dec]/[dec], <MSG_EXPL","TL Port Manager initialization failed. [chars] explains the reason for the failure.","No action is required."
"ACLTCAM","3","ACL_TCAM_MTS_Q_LEAK","Possible MTS buffer leak for SAP [dec]","Possible MTS buffer leak for SAP [dec]","No action is required."
"ACLTCAM","3","ALLOCFAIL","Heap Memory allocation failed: [chars]","TL Port Manager is out of dynamic memory. [chars] specifies the context where the failure occured.","No action is required."
"ACLTCAM","3","FC2ERROR","[chars]","TL Port Manager encountered an FC2 error. [chars] specifies the context where the error occured.","No action is required."
"ACLTCAM","3","GENERROR","[chars]","TL Port Manager encountered a general error, one that does not fall in any of the above categories. [chars] describes the error and its context.","No action is required."
"ACLTCAM","3","MTSERROR","[chars]","TL Port Manager encountered an MTS error. [chars] specifies the context where the error occured.","No action is required."
"ACLTCAM","3","PSSERROR","[chars]","TL Port Manager encountered a PSS error. [chars] specifies the context where the failure occured.","No action is required."
"ACLTCAM","3","REGISTER_FAILED","Could not register to MTS opcode [chars] - error [hex].","ACLTCAM process could not register to the notifications mentioned by [chars]. [hex] is the error.","No action is required."
"ACLTCAM","4","ACL_TCAM_BELOW_THRESHOLD","[chars] TCAM usage ([dec]/[dec]) fell below [dec]% fwd-eng: [dec], [chars]","[chars] TCAM usage [dec]/[dec] fell below [dec] percent on fwd-engine [dec], [chars]","No action is required."
"ACLTCAM","4","ACL_TCAM_BEYOND_THRESHOLD","[chars] TCAM usage ([dec]/[dec]) exceeded [dec]% fwd-eng: [dec], [chars]","[chars] TCAM usage [dec]/[dec] exceeded [dec] percent on fwd-engine [dec], [chars]","No action is required."
"ACLTCAM","4","ACL_TCAM_FLOW_COUNTER_INVALIDATED","Flow counter for flow: vsan: [dec], sid: [hex], did: [hex] with statistics: frames = %llu & bytes = %llu was invalidated due to: [chars]","ACLTCAM process invalidated the flow counter for flow VSAN [dec] SID [hex] DID [hex] with collected stats of [dec] frames and [dev] bytes was invalidated because of reason [[chars]].","No action is required."
"ACLTCAM","4","ACL_TCAM_FLOW_COUNTER_VALIDATED","Flow counter for flow: vsan: [dec], sid: [hex], did: [hex] is now valid","ACLTCAM process validated the flow counter for flow VSAN [dec] SID [hex] DID [hex].","No action is required."
"ACLTCAM","4","ACL_TCAM_MTS_Q_HIGH","MTS queue for SAP [dec] is close to full","MTS queue for SAP [dec] is close to full","No action is required."
"ACLTCAM","4","TLPM_ALPA_CACHE_FULL","Translation Port ALPA cache is full. Some new entries may not be cached","TL Port cache is currently fully populated with active entries. Hence, there is no available cache space to be assigned any newly created alpa entry on a TL Port. This is an informational message.","No action is required."
"ACLTCAM","6","ACL_TCAM_STATUS","Status: [chars].","ACLTCAM status is reported as: [chars].","No action is required."
"ACLTCAM","6","MGRCREATED","Translation Port Manager created.","TL Port Manager was created successfully and is up and running. This is an informational message.","No action is required."
"ACLTCAM","6","MGREXIT","Translation Port Manager shutting down gracefully.","TL Port Manager is shutting down gracefully. This is an informational message.","No action is required."
"ACLTCAM","6","PORTDOWN","Translation Port [chars] DOWN.","A port configured as TL Port is DOWN and out of operation. [chars] is the interface-id string that identifies the TL Port. This is an informational message.","No action is required."
"ACLTCAM","6","PORTUP","Translation Port [chars] UP.","A port configured as TL Port is UP and operational. [chars] is the interface-id string that identifies the TL Port. This is an informational message.","No action is required."
"ACL","2","ACL_HA_FAILURE","Failed to do high availability operation: [chars].","Failed to do high availability operation. [chars] is the reason.","No action is required."
"ACL","2","ACL_INIT_FAILED","Initialization failed for ACL: [chars], reason: [hex].","Initialization failed for ACL due to [chars], reason: [hex].","No action is required."
"ACL","2","ACL_LINECARD_STATUS","Status from linecard: [dec], for module: [chars](ID: [dec]), status : [dec], error_id: [hex], catastrophic: [chars], restart count: [dec].","Status from linecard: [dec], for module: [chars](ID: [dec]), status : [dec], error_id: [hex], catastrophic: [chars], restart count: [dec].","No action is required."
"ACL","2","ACL_MTS_FAILURE","Failed to do MTS operation: [chars].","Failed to do MTS operation. [chars] is the reason.","No action is required."
"ACL","2","ACL_MTS_Q_FULL","MTS queue for SAP [dec] is full","MTS queue for SAP [dec] is full","No action is required."
"ACL","2","ACL_MTS_REGISTRATION_FAILED","MTS options setting to [hex] failed for opCode: [dec].","MTS options setting to [hex] failed for opCode: [dec].","No action is required."
"ACL","2","ACL_PENDING_MSG_ARR_FULL","ACL Upgrade Pending Messages Array is Full with [dec] messages. Failing the MTS message with Opc: [dec], RR_TOKEN: [hex]","ACL Upgrade Pending Messages Array is Full with [dec] messages. Failing the MTS message with Opc: [dec], RR_TOKEN: [hex]","No action is required."
"ACL","2","ACL_PSS_FAILURE","Failed to do PSS operation: [chars], reason: [hex].","Failed to do PSS operation [chars]. [hex] is the reason.","No action is required."
"ACL","2","ACL_PSS_VER_FAIL","PSS file [chars] has version [dec].[dec].[dec], expected version [dec].[dec].[dec].","There was a mismatch in the PSS version. [chars] indicates the PSS service, [dec].[dec].[dec] its current version number and [dec].[dec].[dec] the expected version.","No action is required."
"ACL","2","ACL_RUNTIME_FAILURE","[chars] [dec], Error: [hex]","ACL runtime failure is reported as [chars] [dec], reason: [hex].","No action is required."
"ACL","2","ACL_TCAM_FAILURE","Failed to do TCAM operation: [chars].","Failed to do TCAM operation. [chars] is the reason.","No action is required."
"ACL","3","ACL_MTS_Q_LEAK","Possible MTS buffer leak for SAP [dec]","Possible MTS buffer leak for SAP [dec]","No action is required."
"ACL","4","ACL_MTS_Q_HIGH","MTS queue for SAP [dec] is close to full","MTS queue for SAP [dec] is close to full","No action is required."
"ACL","4","ACL_WARNING","[chars] [dec]","ACL warning messages is reported as [chars] [dec].","No action is required."
"ACL","5","ACL_ADJ_SHARING_STATUS","Successfully completed [chars] on Generation 2 linecards.","Successfully completed the command \[chars]\ on Generation 2 linecards.","No action is required."
"ACL","6","ACL_DIAG_EVENT_STATUS","[chars] [hex].","ACL system health management event status is reported as [chars] [hex].","No action is required."
"ACL","6","ACL_E_PORT_EVENT_STATUS","[chars] [chars].","ACL xEport event status is reported as [chars] [chars].","No action is required."
"ACL","6","ACL_FCC_EVENT_STATUS","[chars] [chars].","ACL FCC event status is reported as [chars] [chars].","No action is required."
"ACL","6","ACL_LINECARD_EVENT_STATUS","[chars] [hex].","ACL linecard event status is reported as [chars] [dec].","No action is required."
"ACL","6","ACL_MCAST_EVENT_STATUS","[chars] [chars].","ACL multicast event status is reported as [chars] [chars].","No action is required."
"ACL","6","ACL_NX_PORT_EVENT_STATUS","[chars] [chars].","ACL Nx Port event status is reported as [chars] [chars].","No action is required."
"ACL","6","ACL_PORT_MODE_EVENT_STATUS","[chars] [chars].","ACL portmode event status is reported as [chars] [chars].","No action is required."
"ACL","6","ACL_RUNTIME_STATUS","[chars] [dec]","ACL runtime status is reported as [chars] [dec].","No action is required."
"ACL","6","ACL_SPAN_DEST_CONFIG_STATUS","[chars] [chars].","ACL SPAN destination config event status is reported as [chars] [chars].","No action is required."
"ACL","6","ACL_SPAN_SRC_CONFIG_STATUS","[chars] [chars].","ACL SPAN source config event status is reported as [chars] [chars].","No action is required."
"ACL","6","ACL_STATUS","ACL Status: [chars].","ACL status is reported as [chars].","No action is required."
"ACL","6","ACL_UPDATE_SSRAM_QOS_EVENT_STATUS","[chars] [chars].","ACL update SSRAM for QoS event status is reported as [chars] [chars].","No action is required."
"AGNI-DPP","2","AGNI_DPP_PRINT_2HEX","[chars] [hex] [hex]","Print a string and 1 value","No action is required."
"AGNI-DPP","2","AGNI_DPP_PRINT_HEX","[chars] [hex]","Print a string and 1 value","No action is required."
"AGNI-DPP","2","AGNI_DPP_PRINT_INT","[chars] [dec]","Print a string and 1 value","No action is required."
"AGNI-DPP","2","AGNI_DPP_PRINT_STR","[chars] [chars]","Print a string and 1 value","No action is required."
"AGNI-DPP","2","AGNI_DPP_PRINT","[chars]","Print a string","No action is required."
"AGNI-DPP","6","AGNI_DPP_DEBUG_MSG","[chars]","Debug log message","No action is required."
"AGNIL2F","6","AGNIL2F_DEBUG_MSG","[chars]","Debug log message","No action is required."
"ALI_LC","2","INIT_FAIL","[chars]","Initialization failed","No action is required."
"ALI_LC","2","INTERNAL_PORT_FAILURE","Internal port [dec] reinit failed due to [chars]","An Internal port number [dec] on the board has failed due to reason [chars]. The corresponding ethernet port may become unusable","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"ALI_LC","2","INTERNAL_PORT_REINIT","Internal port [dec] has been reinitialized due to [chars]","An Internal port number [dec] on the board was reinitialized due to reason [chars]. The corresponding ethernet port may experience some packet drops","No action is required."
"ALI_LC","2","MTS_FAILURE","[chars]","MTS send/receive failed","No action is required."
"AMM-SLOT#","0","CLI_INIT_FAILED","CLI library initialization failed!","AMM failed to initialize CLI infrastructure\sbackendlibrary.Thisisafatalerror.'","No action is required."
"AMM-SLOT#","0","TIMER_INIT_FAILED","Timer subsystem initialization failed!","AMM failed to initialize timer library. This is a fatal error.","No action is required."
"AMM-SLOT#","2","AMM_MEM_ALLOC","Memory allocation failed. [chars]","Memory allocation failed. This is a critical failure","No action is required."
"AMM-SLOT#","2","AMM_RECOVERY_ERROR","Error in Recovery: [chars]","AMM failed to recover after a re-start. This is a fatal error.","No action is required."
"AMM-SLOT#","6","INITIALIZED","Internal state created [chars]","AMM has created its internal state stateless/stateful [chars].","No action is required."
"ARBITER","2","CATASTROPHIC_FAILURE","Arbiter Catastrophic interrupt:[chars]","Arbiter trigerred Catastrophic error interrupt","Please contact your support representative"
"ARBITER","2","MBIST_FAIL","Arbiter MBIST failed:[chars]","Arbiter failed built in self test","Please contact your support representative"
"ASCII-CFG","2","ACFG_CONFIGURATION_APPLY_ERROR","Error encountered while Ascii configuration was being applied. Please use show startup-config log to view details","At least one command failed while Ascii configuration was being applied","No action is required."
"ASCII-CFG","2","ACFG_LIB_INVOKE_ERR","Ascii config library invocation error: [chars]","Error encountered while library function was being invoked to display Ascii configuration","No action is required."
"ASCII-CFG","2","ACFG_OPER_FAIL","Operation failed because of [chars]","Operation failed","No action is required."
"ASCII-CFG","2","ACFG_ROLLBACK_FAILED","Rollback to checkpoint [chars] Failed, Going to undo the changes (atomic option)","Rollback operation failed for atomic option","No action is required."
"ASCII-CFG","2","ACFG_ROLLBACK_UNDO_FAILED","Undo failed for atomic Rollback, Please correct the error manually and retry rollback","Undoing the rollback changes (for atomic behavior) Failed","No action is required."
"ASCII-CFG","2","ACFG_SYSLOG_INIT_FAILED","Ascii config Syslog Init Error","Error encountered while Initializing Syslog for Ascii Config","No action is required."
"ASCII-CFG","2","PSS_VER_FAIL","PSS file [chars] has version [dec].[dec].[dec], expected version [dec].[dec].[dec]","There was a mismatch in the PSS version. [chars] indicates the PSS service, [dec].[dec].[dec] its current version number and [dec].[dec].[dec] the expected version","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"ASCII-CFG","3","ACFG_MTSERROR","[chars]","Ascii-cfg-server (rollback process) encountered an MTS error. [chars] specifies the context where the error occurred.","No action is required."
"ASCII-CFG","6","ACFG_CHECKPOINT_CLEAR_DATABASE","cleared all the configuration checkpoints","Cleared all the configuration checkpoints","No action is required."
"ASCII-CFG","6","ACFG_CHECKPOINT_CREATED","Created configuration checkpoint [chars]","Created configuration checkpoint","No action is required."
"ASCII-CFG","6","ACFG_CHECKPOINT_DELETED","Deleted configuration checkpoint [chars]","Deleted configuration checkpoint","No action is required."
"ASCII-CFG","6","ACFG_MAX_CHECKPOINTS","Maximum no of checpoints reached, Removing the oldest checkpoint","Maximum no.of checkpoints reached, removing the oldest checkpoint","No action is required."
"ASCII-CFG","6","ACFG_ROLLBACK_ATOMIC","Performing configuration rollback to checkpoint [chars] (with atomic option)","Performing configuration rollback with atomic option","No action is required."
"ASCII-CFG","6","ACFG_ROLLBACK_BEST","Performing configuration rollback to checkpoint [chars] (with best-effort option)","Performing configuration rollback with best-effort option","No action is required."
"ASCII-CFG","6","ACFG_ROLLBACK_FIRST_ERR","Performing configuration rollback to checkpoint [chars] (with stop-at-first failure option)","Performing configuration rollback with stop-at-first-failure option","No action is required."
"ASCII-CFG","6","INFORMATION","[chars]","An event happend that affects Acfg-Rollback. [chars] indicates the event","No action is required."
"ASCII-CFG","6","PSS_ERR","[chars]","An error occurred during an Acfg PSS operation. [chars] indicates the PSS operation that caused the error","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"ASSOC_MGR","0","EMERGENCY_MSG","[chars]","Association Manager Emergency Message","Please file the bug for Association Manager Component thro' CDETS"
"ASSOC_MGR","1","ALERT_MSG","[chars]","Association Manager Alert Message","Association Manager Internal Operation Alert"
"ASSOC_MGR","2","CRITICAL_MSG","[chars]","Association Manager Critical Message","No action is required."
"ASSOC_MGR","3","ERROR_MSG","[chars]","Association Manager Error Message","No action is required."
"ASSOC_MGR","4","WARN_MSG","[chars]","Association Manager Warning Message","No action is required."
"ASSOC_MGR","5","NOTIF_MSG","[chars]","Association Manager Notification Message","No action is required."
"ASSOC_MGR","6","ASSOC_ACTIVATED","Association Activated for vlan id:[dec] <--> vsan id:[dec]","Association Activated","No action is required."
"ASSOC_MGR","6","ASSOC_CREATED","Association Created for vlan id:[dec] <--> vsan id:[dec]","Association Created","No action is required."
"ASSOC_MGR","6","ASSOC_DEACTIVATED","Association Deactivated for vlan id: [dec] <--> vsan id: [dec]","Association Deactivated","No action is required."
"ASSOC_MGR","6","ASSOC_DELETED","Association Deleted for vlan id: [dec] <--> vsan id: [dec]","Association Deleted","No action is required."
"ASSOC_MGR","6","ASSOC_MGR_STATEFULL_RESTART","Association Manager Statefull Restart","Association Manager Stateful Restart","No action is required."
"ASSOC_MGR","6","ASSOC_MGR_STATELESS_RESTART","Association Manager Stateless Restart","Association Manager Stateless Restart","No action is required."
"ASSOC_MGR","6","ASSOC_OPER_STATUS_CHG","Association status for vlan id: [dec] <--> vsan id: [dec] changed from [chars] to [chars]","Association Operational State Change","No action is required."
"ASSOC_MGR","6","INFO_MSG","[chars]","ASSOC Manager Informational Message","No action is required."
"ASSOC_MGR","7","DEBUG_MSG","[chars]","Association Manager Debug Message","No action is required."
"ATLANTIS_APP-SLOT#","2","ATLANTIS_APP_EXITED","Atlantis driver application exited (syserr = [dec], errno = [dec])","Atlantis driver application exited","No action is required."
"AZUMA","2","DPFPGA_HW_PROG_FAIL","DPFPGA [dec] hardware initialization failed - [chars]","DPFPGA hardware initialization failureIf hardware configure fails, please do the parallel epld upgrade again.AZUMA-6Error Message      AZUMA-6-DPFPGA_DEBUG_MSG: [chars] Explanation    Debug log message","No action is required."
"BET","6","BET_DEBUG_MSG","[chars]","Debug log message","No action is required."
"BFDC-SLOT#","2","BFDC_GENERAL_FAILURE","General failure. [chars]","General failure. This is a critical failure","No DDTS."
"BFDC-SLOT#","2","BFDC_MALLOC_FAILED","Memory allocation failed. [chars]","Memory allocation failed. This is a critical failure","No DDTS."
"BFDC-SLOT#","2","BFDC_MTS_FAILURE","MTS failure. [chars]","MTS related failure. This is a critical failure","No DDTS."
"BFD","3","REACHED_CAPACITY_LIMIT","BFD session [chars] creation on interface [chars] failed due to capacity limit [dec]","BFD session [chars] creation on interface [chars] failed due to current capacity limit [dec]","Please remove current bfd sessions to make room for new ones"
"BFD","3","SESSION_ACL_INSTALL_GAVE_UP","BFD session [chars] installation failed due to ACL installation failure interface [chars]","BFD session [chars] installation failed due to ACL installation failure interface [chars","Maximum acl install retries exceeded. Please to free up acl resources"
"BFD","3","SESSION_ACL_REMOVE_GAVE_UP","BFD session [chars] removal failed due to ACL removal failure interface [chars]","BFD session [chars] removal failed due to ACL removal failure interface [chars","Maximum acl removal retries exceeded. Please manually remove bfd sessions"
"BFD","3","SESSION_CREATE_FAIL","Failed to create BFD session to neighbor [chars] over intertface [chars]. Reason [chars]","Failed to create BFD session to neighbor [chars] over intertface [chars] Reason [chars]","SYSLOGDPC_NO_ACTION"
"BFD","4","INVALID_NBR","Attempt to BFD session failed for application [chars].","Attempt to BFD session failed for application [chars].","No action is required."
"BFD","4","SESSION_DELETE_FAIL","Attempt to delete BFD session for neighbor [chars] failed: Reason [chars] ([hex]).","Attempt to delete BFD session for neighbor [chars] failed: Reason [chars] (0x[hex]).","No action is required."
"BFD","5","BFD_DISABLED","BFD Disabled","BFD Service Disabled","No action is required."
"BFD","5","BFD_ENABLED","BFD Enabled","BFD Service enabled","No action is required."
"BFD","5","SESSION_ACTIVE_PARAMS_CHANGE","Local parameter of BFD session [hex] has changed [chars]","Local parameter of BFD session 0x[hex] has changed [chars]","No action is required."
"BFD","5","SESSION_CREATED","BFD session to neighbor [chars] on interface [chars] has been created","BFD session to neighbor [chars] on interface [chars]","No action is required."
"BFD","5","SESSION_LOCAL_PARAMS_CHANGE","Local parameter of BFD session [hex] has changed [chars]","Local parameter of BFD session 0x[hex] has changed [chars]","No action is required."
"BFD","5","SESSION_MOVED","BFD session [hex]: [chars]","BFD session 0x[hex]: [chars]","No action is required."
"BFD","5","SESSION_NO_RESOURCES","No resource for session to neighbor [chars] on interface [chars]","The BFD session can not be created or modified due to lack of resources. [[[ It has reached the maximum number of packets per second allowed on the linecard.]]] No resources for session to neighbor [chars]","Remove other BFD sessions [[[ or reduce the Tx/Rx timers ]]] to free resources for this session"
"BFD","5","SESSION_REMOVED","BFD session to neighbor [chars] on interface [chars] has been removed","BFD session to neighbor [chars] on interface [chars]","No action is required."
"BFD","5","SESSION_STATE_DOWN","BFD session [chars] to neighbor [chars] on interface [chars] has gone down. Reason: [hex].","BFD session [chars] to neighbor [chars] on interface [chars] has gone down. Reason: 0x[hex]. This may be as a result of the forwarding path being down.","No action is required."
"BFD","5","SESSION_STATE_UP","BFD session [chars] to neighbor [chars] on interface [chars] is up.","BFD session [chars] to neighbor [chars] on interface [chars] is up.","No action is required."
"BFD","6","SESSION_ACL_INSTALL_FAILED","BFD session [chars] failed due to missing ACL resources for interface [chars]","BFD session [chars] failed due to missing ACL resources for interface [chars]","No action is required."
"BFD","6","SESSION_ACL_REMOVE_FAILED","BFD session [chars] removal failed due to missing ACL resources for interface [chars]","BFD session [chars] removal failed due to missing ACL resources for interface [chars]","No action is required."
"BIOS_DAEMON","2","BIOS_DAEMON_FLASH_WARNING","Flash chip not supported by running image. Skipping bios upgrade.","BIOS CHIP NOT SUPPORTED","No action is required."
"BIOS_DAEMON","2","BIOS_DAEMON_PRI_BOOT_FAIL","System booted from Alternate BIOS Flash","Boot from Alternate","SYSLOGDOC_NOACTION"
"BIOS_DAEMON","2","BIOS_DAEMON_SUP_ERROR","BIOS Sector ([dec]) is write protected","BIOS WRITE PROTECTED","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"BIOS_DAEMON","5","BIOS_DAEMON_PRI_BOOT","System booted from Primary BIOS Flash","Boot from Primary","SYSLOGDOC_NOACTION"
"BIOS_DAEMON-SLOT#","2","BIOS_DAEMON_LC_ERROR","BIOS Sector ([dec]) is write protected","BIOS WRITE PROTECTED","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"BIOS_DAEMON-SLOT#","2","BIOS_DAEMON_LC_PRI_BOOT_FAIL","System booted from Alternate BIOS Flash","Boot from Alternate","SYSLOGDOC_NOACTION"
"BIOS_DAEMON-SLOT#","5","BIOS_DAEMON_LC_PRI_BOOT","System booted from Primary BIOS Flash","Boot from Primary","SYSLOGDOC_NOACTION"
"BLOGGERD","2","BLOGGERD_SYSLOG_TRANSFER_ERROR_DISABLED","[chars]","Blogger Log Transfer has been error disabled","Please collect BloggerD tech support using showtechbloggerd-all''"
"BLOGGERD","3","BLOGGERD_INVALID_VDC","At [chars]([dec]) Invalid VDC [dec]","Invalid VDC ID","Please collect BloggerD tech support using showtechbloggerd-all''"
"BLOGGERD","3","BLOGGERD_LOG_DUMP_THROTTLED","VDC [dec] Comp: [chars] Buf_uuid: [dec] Buf_inst: [dec] sap: [chars]. Please collect showsysteminternalsdwrapbufferssap[dec]detailed'frommodule[dec]Wiki:https://and-sw-web.cisco.com/twiki/bin/view/Sw/LogDumpThrottle'","Log Dump Throttled","Please collect BloggerD tech support using showtechbloggerd-all''"
"BLOGGERD","3","BLOGGERD_MOVE_LOGS_SCRIPT_NOT_FOUND","At [chars]([dec]) Move Logs Script Not Found at [chars]","Move Log Script Not Found","Please collect BloggerD tech support using showtechbloggerd-all''"
"BLOGGERD","3","BLOGGERD_PATH_NOT_FOUND","At [chars]([dec]) Path [chars] NOT found","Required Path Not Found","Please collect BloggerD tech support using showtechbloggerd-all''"
"BLOGGERD","3","BLOGGERD_SYSLOG_CONFIG_PULL_FAILED","At [chars]([dec]) Config Pull Failed. Returned [hex]([chars])","Blogger Config Pull Failed","Please collect BloggerD tech support using showtechbloggerd-all''"
"BLOGGERD","3","BLOGGERD_SYSLOG_MTS_UNDROP","MTS is not dropped by Node [hex] SAP [dec]","MTS not dropped","Please collect BloggerD tech support using showtechbloggerd-all''"
"BLOGGERD","3","BLOGGERD_SYSLOG_PSS_FAILURE","At [chars]([dec]) Internal PSS Error. Returned: [hex]([chars])","PSS Operation Failed","Please collect BloggerD tech support using showtechbloggerd-all''"
"BLOGGERD","3","BLOGGERD_SYSLOG_SDWRAP_INIT_FAILED","At [chars]([dec]) sdwrap initialization failed. Returned: [hex]([chars])","SDWrap Debug Init failed","Please collect BloggerD tech support using showtechbloggerd-all''"
"BLOGGERD","3","BLOGGERD_SYSLOG_THREAD_CREATE_FAILED","At [chars]([dec]) Thread Creation Failed [hex] errno: [dec]([chars])","Thread Creation Failed","Please collect BloggerD tech support using showtechbloggerd-all''"
"BLOGGERD","4","BLOGGERD_FLOW_CONTROL_ENABLED","Temporarily suspending BloggerD Log Transfer from Modules due to lack of space (available: %ld MB) on Active SUP","Flow Control Enabled. Transfer from Modules temporarily suspended","Please collect BloggerD tech support using showtechbloggerd-all''"
"BLOGGERD","4","BLOGGERD_FLOW_CONTROL_RESET","Revoking temporary Log Transfer Suspension from Modules. Space available now: %ld MB","Flow Control Reset. Transfer from Modules re-enabled","Please collect BloggerD tech support using showtechbloggerd-all''"
"BLOGGERD","6","BLOGGERD_INFO","[chars]","Info","Please collect BloggerD tech support using showtechbloggerd-all''"
"BOOTUP_TEST","2","EOBC_FAIL","Module [dec] has failed test [chars] on EOBC due to error [chars]","Online diagnostics EOBC test has failed","No action is required."
"BOOTUP_TEST","2","EOBC_SKIP","Module [dec] has failed test [chars] on EOBC due to error [chars]","Online diagnostics ManagementPort test has failed","No action is required."
"BOOTUP_TEST","2","MGMT_PORT_FAIL","Module [dec] has failed test [chars] on Management Port due to error [chars]","Online diagnostics ManagementPort test has failed","No action is required."
"BOOTUP_TEST","2","MGMT_PORT_SKIP","Module [dec] has skipped test [chars] on Management Port due to error [chars]","Online diagnostics ManagementPort test is skipped","No action is required."
"BOOTVAR","2","ALLOC_MEMORY","Memory allocation failed","The service failed to allocate memory.","Check if the system is low on memory, if so reset the switch."
"BOOTVAR","2","AUTOCOPY_FAILED","Autocopy of file [chars] to standby failed. [chars] (Error-id: [hex])","The image deemed to be copied to standby via the auto-copy feature failed.","Check error id for specified reason."
"BOOTVAR","2","AUTOSYNC_FAILED","Image autosync failed. Reason: [chars] ([hex])","Image synchronization failed.","Check that there is enough space on the flash, as well as system high availability status."
"BOOTVAR","2","CONFIG_ERROR","Failed to update boot configuration","An error has occurred during the update of the boot configuration files","Check that there is enough space on the flash, show boot to check the configured image names, show loader internal configuration to compare them with the current bootloader configuration, if they are not coherent do write erase and retry to save the configuration."
"BOOTVAR","2","IMAGE_NOT_COMPATIBLE","Warning: image [chars] is not compatible with the current platform in SUP [dec]","The input image name is not compatible with the current platform.","Make sure a right image is specified before reboot."
"BOOTVAR","3","AUTOCOPY_FAILED_STANDBY_FULL","Autocopy of file [chars] to standby failed due to not enough disk space on standby","There is not enough disk space on the standby for the file to be copied.","Clear space on the standby disk."
"BOOTVAR","3","INIT_FAILED","Initialization failed: Component [chars]","The service failed to start The failure occurs during initialization of the component [chars].","Show processes to check the status of the other processes, pay attention to the specified component."
"BOOTVAR","3","LOAD_VERIFY_LIB_FAILED","Fetching library [chars] failed, reason=[chars]","Failed to load bootvar specified verification library.","No action is required."
"BOOTVAR","3","MODULE_LOCK_FAIL","Unable to get module lock, please don't reload <error-id:[hex]>","Unable to acquire modlock to prevent user to reload during auto-sync.","No action is required."
"BOOTVAR","3","NEIGHBOR_REJECT_AUTOCOPY","auto-copy failed - not supported by neighbor supervisor.","Standby supervisor does not support auto-copy, thus failed.","No action is required."
"BOOTVAR","3","VERIFY_FAILED","Image [chars] for bootvar [chars] verification failed, reason=[chars]","The image set for this bootvar has failed the verification process, this is just a warning.","Check reason to determine actions."
"BOOTVAR","5","AUTOCOPY_SUCCEED","auto-copy of file [chars] to standby supervisor succeed","Auto copy of the file succeed, image integrity verified by standby.","No action is required."
"BOOTVAR","5","AUTOCOPY_VERIFY_SEND_FAILED","Unable to ask standby to verify file [chars], error = [hex]","Upon copied the image to standby, failed to send message to ask standby to verify integrity.","Turn auto-copy off and back on."
"BOOTVAR","5","AUTOSYNC_DONE","Image autosync done","The image synchronization done successfully.","No action is required."
"BOOTVAR","5","AUTOSYNC_REBOOT","Rebooting standby after successful autosync","Image autosync has been successful, resetting the standby supervisor to load the new image.","Check that the standby sup reloads correctly."
"BOOTVAR","5","AUTOSYNC_START","Starting image autosync. Please wait until completion...","The standby-sup has requested the sync of the current image.","No action is required."
"BOOTVAR","5","IMAGE_NOTEXISTS","Warning: image [chars] doesn't exist on sup[dec]","The input image name doesn't exist on the specified supervisor.","Check whether the input image name you entered exists and make sure that you have the image on the flash before reboot."
"BOOTVAR","5","NEIGHBOR_UPDATE_AUTOCOPY","auto-copy supported by neighbor supervisor, starting...","Info log reporting standby's support of auto-copy. Auto-copy is being started.","No action is required."
"BOOTVAR","6","ALREADY_IN_SYNC","Image already in sync","No need to update the image on the standby-sup.","No action is required."
"BOOTVAR","6","AUTOCOPY_DID_NOT_START","Autocopy of file [chars] to standby did not start. [chars] (Error-id: [hex])","Autocopy of the file did not start as the remote copy location does not exist","No action is required."
"BOOTVAR","6","CONFIG_UPDATED","Boot configuration updated","The boot-loader configuration files have been successfully updated.","No action is required."
"BOOTVAR","6","STARTING","Boot configuration initialized","The service has successfully started.","No action is required."
"CALLHOME","2","EVENT","[chars]","Callhome event [chars] occurred.","If you have configured your email address to receive callhome notifications, please check your email for more details about this callhome event. If callhome was not enabled, please execute CLI commands relevant to the callhome event to get more information about the error"
"CALLHOME","2","PROGRAM_EXIT","callhome process ending: [chars]","Callhome process is exiting with reason [chars].","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"CALLHOME","3","CALLHOME_CFS_MERGE_OPERATION_FAILED","[chars]","[chars1]","Please check the reason for the failure of the cfs operation and rectify the problem"
"CALLHOME","3","CALLHOME_CFS_OPERATION_FAILED","[chars] : [chars]","[chars1] [chars2]","Please check the reason for the failure of the cfs operation and rectify the problem"
"CALLHOME","3","CALLHOME_MAX_ALERT_MSG","[chars]","[chars]","Please check the reason for the generation of the callhome messages and rectify the problem"
"CALLHOME","3","EVENT_PROCESS_ERROR","error in processing callhome event [chars] reason:[chars]","Error in processing callhome event [chars] reason:[chars]","Please check your callhome configuration for proper configuration. Please check SMTP server address, email addresses for destination profiles and enable status of callhome. Use 'show callhome' commands for displaying configuration."
"CALLHOME","3","MESSAGE_SIZE_EXCEED","message size for callhome alert:[chars] exceeds maximum limit for destination profile:[chars]","Message size for callhome alert:[chars] exceeds maximum limit for destination profile:[chars]","Please check the maximum message size for the destination profile under question. Increase it if possible to match the maximum limit allowed by your email destinations."
"CALLHOME","6","NONCRIT_EVENT","[chars]","Non-critical Callhome event [chars] occurred.","If you have configured your email address to receive callhome notifications, please check your email for more details about this callhome event. If callhome was not enabled, please execute CLI commands relevant to the callhome event to get more information about the error"
"CARDCLIENT","2","CARDCL_CRIT","[chars]","CardClient Critical Message","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"CARDCLIENT","2","ONL","[chars]","Online Message","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"CARDCLIENT","2","REG","[chars]","CardClient Console Message","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"CARDCLIENT","2","SSE","[chars]","CardClient Console Message","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"CARDCLIENT","3","CARDCL_ERR","[chars]","CardClient Error","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"CARDCLIENT","3","CARDCL_INFO","[chars]","CardClient Flow Message","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"CARDCLIENT-SLOT#","2","ERR","[chars]","CardClient Remote Syslog msg","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"CARDCLIENT-SLOT#","2","IMG_ERR","[chars]","CardClient Remote Syslog msg","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"CDP","2","INITFAIL","CDP Daemon Initialization failed: [chars]","CDP Daemon Initialization failed. [chars] explains the reason for the failure.","No action is required."
"CDP","3","ALLOCFAIL","Heap Memory allocation failed: [chars]","CDP Daemon is out of dynamic memory. [chars] specifies the context where the failure occurred.","No action is required."
"CDP","3","GENERROR","[chars]","CDP Daemon encountered a general error, one that does not fall in any of the above categories. [chars] describes the error and its context.","No action is required."
"CDP","3","MCASTBINDFAIL","Failed to bind for CDP multicast address on interface [hex] - [chars]","An attempt to register for packets destined to the CDP multicast address failed. [dec] identifies the interface [char] identifies the reason.","No action is required."
"CDP","3","MTSERROR","[chars]","CDP Daemon encountered an MTS error. [chars] specifies the context where the error occurred.","No action is required."
"CDP","3","PKTRECVFAIL","Failed to receive packet - [chars]","Failed to receive packet. [char] identifies the reason.","No action is required."
"CDP","3","PKTSENDFAIL","Failed to send packet, interface [hex] - [chars]","Failed to send packet. [dec] identifies the interface [char] identifies the reason.","No action is required."
"CDP","3","PSSERROR","[chars]","CDP Daemon encountered a PSS error. [chars] specifies the context where the failure occurred.","No action is required."
"CDP","3","SOCKBINDFAIL","Failed to bind to raw socket, interface [hex] - [chars]","Failed to bind to raw socket. [dec] identifies the interface [char] identifies the reason.","No action is required."
"CDP","3","SOCKOPENFAIL","Failed to open socket for receiving raw 802_2 packets - [chars]","An attempt to open a socket for receiving raw 802_2 packets failed. [char] identifies the reason.","No action is required."
"CDP","4","DUPLEX_MISMATCH","Duplex mismatch discovered on [chars], with [chars]","Duplex mismatch discovered from the received cdp packet This is a warning message.","No action is required."
"CDP","4","NATIVE_VLAN_MISMATCH","Native VLAN mismatch discovered on [chars]([dec]), with [chars]([dec])","Native VLAN mismatch discovered This is a warning message.","No action is required."
"CDP","5","DISABLED","CDP is disabled","CDP is disabled on the device.","No action is required."
"CDP","5","ENABLED","CDP is enabled","CDP is enabled on the device.","No action is required."
"CDP","5","NEIGHBOR_ADDED","Device [chars] discovered of type [chars] with port [chars] on incoming port [chars] with ip addr [chars] and mgmt ip [chars]","Discovered a neighbor device. This is an informational message.","No action is required."
"CDP","5","NEIGHBOR_REMOVED","CDP Neighbor [chars] on port [chars] has been removed","Deleted a neighbor device. This is an informational message.","No action is required."
"CDP","6","CDPDUP","CDP Daemon Up.","CDP Daemon was created successfully and is up and running. This is an informational message.","No action is required."
"CDP","6","CDPEXIT","CDP Daemon shutting down gracefully.","CDP Daemon is shutting down gracefully. This is an informational message.","No action is required."
"CDP","6","PORTDISABLE","CDP disabled on port [chars]","CDP was disabled on a given port. [chars] is the interface-ID string that identifies the port. This is an informational message.","No action is required."
"CDP","6","PORTDOWN","A CDP enabled port [chars] went down.","A CDP enabled port became un-operational. [chars] is the interface-ID string that identifies the port. This is an informational message.","No action is required."
"CDP","6","PORTENABLE","CDP enabled on port [chars]","CDP was enabled on a given port. [chars] is the interface-ID string that identifies the port. This is an informational message.","No action is required."
"CDP","6","PORTUP","A CDP enabled port [chars] came up.","A CDP enabled port became operational. [chars] is the interface-ID string that identifies the port. This is an informational message.","No action is required."
"CERT_ENROLL","2","CERT_EN_PROGRAM_EXIT","cert_enroll daemon exiting: [chars]","Cert_enroll daemon is exiting.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"CERT_ENROLL","3","CERT_EN_ERROR_MESSAGE","[chars]","CERT_ENROLL Error Message","No action is required."
"CERT_ENROLL","3","CERT_EN_FIPS_MODE_INIT_ERROR","Could not initialize FIPS mode : [chars]","FIPS mode initialization error","No action is required."
"CERT_ENROLL","6","CERT_EN_MESSAGE","[chars]","CERT_ENROLL Message","No action is required."
"CFGD-SLOT#","2","7","ERROR: Component ([chars]) caused critical error please reboot SSM","Component caused critical error","Restart the linecard."
"CFS","2","CFS_REJECT","CFS reject: [chars]: Switch WWN [chars], ip [chars], reason [chars]","CFS reject: [chars] Switch WWN [chars], ip [chars], reason [chars]","No action is required."
"CFS","2","EXITING","Exit reason: [chars]","The CFS service process has exited due to [char]. The process has probably been restarted automatically.","No action is required."
"CFS","2","GENERAL_ERROR","[chars]","The CFS service has encountered an critical error. The description of error is [str.]","No action is required."
"CFS","2","INITFAIL","CFS Service Init failed: [chars]","CFS Service initialization failed. [chars] explains the reason for the failure.","No action is required."
"CFS","2","LOCK_FAILED","lock failed for sap [dec] due to internal error.","Lock failed due to Unrestricted uncoordinated count is out of sync for sap [dec]","To recover from this state run command cfsinternaldecrement-unrestricted<app-sap"
"CFS","2","MALLOC_ERROR","Size [dec] bytes","The CFS service could not allocate memory.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"CFS","2","MTS_REJECT","Verification failed reject MTS message SAP [dec]:RR-token [hex]","This MTS message could have been posted by the previous active running pre 3.x; MTS structure has changed since then hence ignore the MTS message, Source SAP [dec]; RR-token [hex]","No action is required."
"CFS","2","PSS_ERROR","[chars]: PSS ret. val=[dec]","The CFS service encountered error while operating on a persistent storage database.","No action is required."
"CFS","2","VDC_MGR_FAIL","Failed to get a valid switch mac from VDC Manager: [chars]","VDC manager did not respond with a proper MAC address. It could have been because of a timeout in MTS received","No action is required."
"CFS","3","ALLOCFAIL","Heap Memory allocation failed: [chars]","CFS Service is out of dynamic memory. [chars] specifies the context where the failure occured","No action is required."
"CFS","3","APP_MERGE_FAILED","Merge failed for app [chars], local switch wwn [chars], remote switch wwn [chars].Please check showcfsmergestatusname[chars]'formoreinformation'","The CFS service has detected a merge failure.","No action is required."
"CFS","3","CFS_PSS_CORRUPTED","[chars] PSS found corrupted","The CFS service has detected corruption in one of its persistent information database. The database would be recreated.","No action is required."
"CFS","3","DBERROR","[chars]","CFS Service encountered a database error. [chars] specifies the context where the failure occured.","No action is required."
"CFS","3","FAILURE_RESPONSE","[chars] [hex]","CFS Service failed to get response [chars][hex] specify the context where the failure occured.","No action is required."
"CFS","3","FIPS_TEST_FAILED","FIPS compliance test failed","FIPS compliance test failed","No action is required."
"CFS","3","GENERROR","[chars]","CFS Service encountered a general error, one that does not fall in any of the above categories. [chars] describes the error and its context.","No action is required."
"CFS","3","LICERR","[chars]","CFS Service failed to get license.","No action is required."
"CFS","3","MERGE_FAILED","Merge failed for app [chars], local switch wwn [chars],ip [chars], remote switch wwn [chars], ip [chars]","The CFS service has detected a merge failure.","No action is required."
"CFS","3","MTSERROR","[chars]","CFS Service encountered an MTS error. [chars] specifies the context where the error occured.","No action is required."
"CFS","3","PSSERROR","[chars]","CFS Service encountered a PSS error. [chars] specifies the context where the failure occured.","No action is required."
"CFS","3","TIMEOUT_ERROR","[chars] [hex]","CFS Service encountered a timeout [chars][hex] specify the context where the failure occured.","No action is required."
"CFS","3","UNKNOWN_MSG","Recvd. from Node=[dec] SAP=[dec]","The CFS service has received an unknown message from [dec]].[dec]. This information is for debugging only.","No action is required."
"CFS","4","LICEXP","[chars]","CFS Service license is going to expire. [chars] gives the expected time of expiry","No action is required."
"CFS","4","PSS_VERSION_MISMATCH","PSS [dec] Code [dec]","There was a version mismatch between the CFS service and one of its persistent storage databases. The persistent information has been translated to the new format.","No action is required."
"CFS","6","BECAME_ACTIVE","Became ACTIVE from standby mode","The CFS service on the standby supervisor became active and it is ready to serve client requests.","No action is required."
"CFS","6","BECAME_STDBY","Became STANDBY from active mode","The CFS service became standby from active mode.","No action is required."
"CFS","6","EXCESSIVE_DELAY","[chars]","Excessive time taken for a processing event. The description of the event is [str.]","No action is required."
"CFS","6","FAILED_TO_SEND_HEARTBEAT","Failed to send heartbeat to system manager: Reason=[chars]","The CFS service was unable to send heartbeat to the system manger","No action is required."
"CFS","6","GENERAL_EVENT","[chars]","The CFS service has generated an important event. The description of the event is [str.]","No action is required."
"CFS","6","INVALID_CHECKSUM","Received packet from peer on if-index([hex]) with corrupted checksum","This could be because of errors in the link","No action is required."
"CFS","6","INVALID_IF_INDEX","Received packet on if-index([hex]) which is not recognized by CFS","The if-index does not match with the if-index used in discovery or we might have already recieved an adjacency cleanup message for this if-index. Check if the if-index is that of the port-channel or a physical if-index","No action is required."
"CFS","6","LOGICAL_DISTRIBUTION_INFO","vsan [dec], source wwn [chars], ip [chars] app-id [dec], session-id [dec], user [chars], [chars]","Vsan [dec], source wwn [chars], ip [chars], app-id [dec], user [chars], event [chars]","No action is required."
"CFS","6","PHY_DISTRIBUTION_INFO","source wwn [chars], ip [chars], app-id [dec], session-id [dec], user [chars], [chars]","Source wwn [chars], ip [chars], app-id [dec], session-id [dec], user [chars], event [chars]","No action is required."
"CFS","6","PSS_CREATED","[chars] PSS Created","One of the persistent information database of CFS service has been recreated","No action is required."
"CFS","6","PSS_DESTROYED","[chars] PSS Destroyed","One of the persistent information databases of CFS Service has been intentionally destroyed and would be recreated.","No action is required."
"CFS","6","REGION_CTX_REMOVED","Region info is deleted for [chars]","[chars] is in logical scope. Regions are supported only physical scope applications","No action is required."
"CFS","6","SERVICE_UP","Initialized [chars]","The CFS service is up and ready to accept client requests The service was initialized in [char] mode.","No action is required."
"CFS","6","SRVCREATED","CFS Service created","CFS Service was created successfully and is up and running. This is an informational message.","No action is required."
"CFS","6","SRVEXIT","CFS Service shutting down gracefully","CFS Service is shutting down gracefully. This is an informational message.","No action is required."
"CFS","6","SWITCHOVER","Switching Over to other Sup.","The CFS service has successfully switched over to the standby supervisor card.","No action is required."
"CIMSRVPROV","2","CIM_SYSLOG_EXIT","Message:[chars] errcode:[dec]","Exit due to critical error","No action is required."
"CIMSRVPROV","2","CIM_SYSLOG_PSS_SNAPSHOT_ERR","Source URI:[chars] Destination URI:[chars] errcode:[dec]","PSS snapshot error","No action is required."
"CIMSRVPROV","2","CIM_SYSLOG_SDWRAP_ERR","Description:[chars] errcode:[dec]","Debug infrastructure error","No action is required."
"CIMSRVPROV","3","CIM_SYSLOG_COPY_CONFIG_ERR","Message:[chars] URI:[chars] errcode:[dec]","Copy running startup error","No action is required."
"CIMSRVPROV","3","CIM_SYSLOG_FILE_ERR","Purpose:[chars] Filename:[chars] errcode:[dec]","File handling error","No action is required."
"CIMSRVPROV","3","CIM_SYSLOG_MTS_ERR","message [chars]","MTS message handling error","No action is required."
"CIMSRVPROV","3","CIM_SYSLOG_PSS_ERR","Purpose:[chars] URI:[chars] errcode:[dec]","PSS handling error","No action is required."
"CIMSRVPROV","6","LOG_CIM_CERTIFICATE_CLEARED","Cleared certificate [chars]","Cleared a certificate named [chars].","No action is required."
"CIMSRVPROV","6","LOG_CIM_CERTIFICATE_INSTALLED","Installed certificate [chars]","Installed a certificate named [chars].","No action is required."
"CLIS","5","CLIS_SYSLOG_CMD_REMOVED","Command deleted from the NVDB: [chars]","Command removal due to configuration change","No action is required."
"CLIS","6","CLIS_SYSLOG_CMD_REMOVED","Command deleted from the NVDB: [chars]","Command removal due to configuration change","No action is required."
"CLK_MGR","2","CLK_MGR_FC2_CRIT","CLK_MGR critical error: [chars]","CLK_MGR fc2 clock synchronization critical error","No action is required."
"CLK_MGR","5","CLK_MGR_CLI_CONFIG","CLK_MGR clock is synchronized by [chars] from VDC [dec]","CLK_MGR clock is synchronized by [chars] from VDC","No action is required."
"CLK_MGR","6","CLK_MGR_TSTAMP_CHKS_DISABLED","CLK_MGR timestamp checks disabled: [chars]","CLK_MGR timestamp checks disabled","No action is required."
"CLK_MGR","6","CLK_MGR_TSTAMP_CHKS_ENABLED","CLK_MGR timestamp checks enabled","CLK_MGR timestamp checks enabled","No action is required."
"CLOUD","2","PROGRAM_EXIT","cloud-discovery process ending: [chars]","Cloud-discovery process is exiting with reason [chars].","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"CLOUD","3","CLOUD_CFS_MERGE_OPERATION_FAILED","[chars]","[chars1]","Please check the reason for the failure of the cfs operation and rectify the problem"
"CLOUD","3","CLOUD_CFS_OPERATION_FAILED","[chars] : [chars]","[chars1] [chars2]","Please check the reason for the failure of the cfs operation and rectify the problem"
"CLOUD","3","CLOUD_FEATURE_MANAGER_ERROR","[chars] : [chars]","[chars1] [chars2]","Please check the reason for error using feature manager and rectify the problem"
"CLOUD","3","CLOUD_PSS_OPERATION_FAILED","[chars] : [chars]","[chars1] [chars2]","Please check the reason for the failure of the pss operation and rectify the problem"
"CLOUD","6","CLOUD_DISCOVERY_DONE","discovery over","Cloud-discovery started","Check cloud membership"
"CLOUD","6","CLOUD_DISCOVERY_STARTED","[chars] discovery started","Cloud-discovery started","Check cloud-discovery status after sometime"
"CLP_FWD","6","CLF_DEBUG_MSG","[chars]","Debug log message","No action is required."
"CLP_L3","6","CLP_L3_DEBUG_MSG","[chars]","Debug log message","No action is required."
"CLP_MAC","6","CLM_DEBUG_MSG","[chars]","Debug log message","No action is required."
"CLP_XBAR","2","FR_CRC","[chars]","Clipper received packets with CRC error from fabric","No action is required."
"CLP_XBAR","6","CLX_DEBUG_MSG","[chars]","Debug log message","No action is required."
"CLUSTER_TEST_APP","5","CLUSTER_TEST_APP_DISABLED","CLUSTER_TEST_APP Disabled","CLUSTER_TEST_APP Service Disabled","No action is required."
"CLUSTER_TEST_APP","5","CLUSTER_TEST_APP_ENABLED","CLUSTER_TEST_APP Enabled","CLUSTER_TEST_APP Service nabled","No action is required."
"CLUSTER_TEST_APP","5","CLUSTER_TEST_APP_TEST_STARTED","Traffic test started","CLUSTER_TEST_APP Test started","No action is required."
"CLUSTER_TEST_APP","5","CLUSTER_TEST_APP_TEST_STOPPED","Traffic test stopped","CLUSTER_TEST_APP Test stopped","No action is required."
"CLUSTER","2","CLUSTER_CAP_ADD_FAIL","Failed to add cluster capability [dec]","Cluster capability addition failed","No action is required."
"CLUSTER","2","CLUSTER_CAP_DEL_FAIL","Failed to delete cluster capability [dec]","Cluster capability deletion failed","No action is required."
"CLUSTER","2","CLUSTER_CAP_DEL_FAIL","Failed to delete cluster capability [dec]","Cluster capability deletion failed","No action is required."
"CLUSTER","2","CLUSTER_CONF_MGR_FAIL","Configuration manager failed to handle '[chars]' ([dec]) status=[hex]","Cluster Config Manager failed","No action is required."
"CLUSTER","2","CLUSTER_DB_SYNC_FAIL_CLIENT","Client on node 0x%llx for cluster 0x%llx application [dec] dataset [dec] received database synchronization failed, reason='[chars]' from application","Cluster database synchronization failed","No action is required."
"CLUSTER","2","CLUSTER_DB_SYNC_FAIL_MANAGER","Manager on node 0x%llx for cluster 0x%llx application [dec] dataset [dec] received database synchronization failed, reason='[chars]' from server on node 0x%llx","Cluster database synchronization failed","No action is required."
"CLUSTER","2","CLUSTER_DB_SYNC_FAIL_SERVER","Server on node 0x%llx for cluster 0x%llx application [dec] dataset [dec] received database synchronization failed, reason='[chars]' from client on node 0x%llx","Cluster database synchronization failed","No action is required."
"CLUSTER","2","CLUSTER_DB_SYNC_FAIL","Cluster 0x%llx application [dec] dataset [dec] database synchronization failed, reason='[chars]'","Cluster database synchronization failed","No action is required."
"CLUSTER","2","CLUSTER_LEADER_ANNOUNCE","Node 0x%llx is the new Master of cluster 0x%llx of [dec] nodes","Leader announcement of cluster","No action is required."
"CLUSTER","2","CLUSTER_LEAVE_REQ_FAIL","Node failed to send LEAVE request to Cluster 0x%llx","Failed to send Leave Request","No action is required."
"CLUSTER","2","CLUSTER_LEAVE_RESP_FAIL","Bad response to LEAVE request for Cluster 0x%llx","Received Bad Leave response","No action is required."
"CLUSTER","2","CLUSTER_LOCAL_NODE_EXIT","Local Node 0x%llx has left the Cluster 0x%llx Reason:[chars]","Node is not part of cluster","No action is required."
"CLUSTER","2","CLUSTER_QUORUM_LOSS","Cluster 0x%llx has lost quorum; number of nodes=[dec]","Cluster has lost quorum","No action is required."
"CLUSTER","2","CLUSTER_RGC_TRANSACTION_FAIL","Cluster 0x%llx RGC transaction application=[dec] dataset=[dec] failed reason='[chars]'","Cluster RGC transaction failed","No action is required."
"CLUSTER","2","CLUSTER_TRANSPORT_FAIL","Cluster 0x%llx transport failed to send message from node 0x%llx to 0x%llx error=[dec]","Cluster transport failed to send message","No action is required."
"CLUSTER","5","CLUSTER_ADD","Cluster 0x%llx added","Cluster Added","No action is required."
"CLUSTER","5","CLUSTER_DISABLED","CLUSTER Disabled","CLUSTER Service Disabled","No action is required."
"CLUSTER","5","CLUSTER_ENABLED","CLUSTER Enabled","CLUSTER Service Enabled","No action is required."
"CLUSTER","5","CLUSTER_NODE_ADD","Node 0x%llx added to cluster 0x%llx","Node added to cluster","No action is required."
"CLUSTER","5","CLUSTER_NODE_JOIN","Node 0x%llx joined cluster 0x%llx","Node joined cluster","No action is required."
"CLUSTER","5","CLUSTER_NODE_LEAVE_EXPLICIT","Remote Node 0x%llx has left the Cluster 0x%llx voluntarily","Remote Node Left voluntarily","No action is required."
"CLUSTER","5","CLUSTER_NODE_LEAVE","Node 0x%llx not in cluster 0x%llx","Node not in cluster","No action is required."
"CLUSTER","5","CLUSTER_NODE_REMOVE","Node 0x%llx removed from cluster 0x%llx","Node removed from cluster","No action is required."
"CLUSTER","5","CLUSTER_REMOVE","Cluster 0x%llx removed","Cluster removed","No action is required."
"CLUSTER","5","CLUSTER_RX_JOIN_REQ","Node 0x%llx received JOIN request from node=0x%llx","Cluster received JOIN request","No action is required."
"CLUSTER","5","CLUSTER_RX_JOIN_RESP","Node 0x%llx received JOIN response from node=0x%llx result='[chars]'","Cluster received JOIN response","No action is required."
"CLUSTER","5","CLUSTER_RX_PROBE","Node 0x%llx received PROBE from node=0x%llx","Cluster received PROBE message","No action is required."
"CLUSTER","5","CLUSTER_STARTED","CLUSTER 0x%llx Started","CLUSTER Started","No action is required."
"CLUSTER","5","CLUSTER_STOPPED","CLUSTER 0x%llx Stopped","CLUSTER Stopped","No action is required."
"CLUSTER","5","CLUSTER_TRANSPORT_DOWN","Cluster 0x%llx transport down for node=0x%llx for Remote Port :[dec] Local Port :[dec]","Cluster Transport Connection DOWN","No action is required."
"CLUSTER","5","CLUSTER_TRANSPORT_UP","Cluster 0x%llx transport up for node=0x%llx","Cluster Transport Connection UP","No action is required."
"CLUSTER","5","CLUSTER_TX_JOIN_REQ","Node 0x%llx sending JOIN request to node=0x%llx","Cluster sending JOIN request","No action is required."
"CLUSTER","5","CLUSTER_TX_JOIN_RESP","Node 0x%llx sending JOIN response to node=0x%llx result='[chars]'","Cluster sending JOIN request","No action is required."
"CMOND","2","CMOND_ALERT_MSG","[chars]","Alert message","No action is required."
"CMOND","2","CMOND_ERROR_MSG","[chars]","Error message","No action is required."
"CMPPROXY","2","LOG_CMP_IS_NOT_UP","Connectivity Management processor (on module [dec]) did not come up","Connectivity Management processor is not sending heartbeats on this module","No action is required."
"CMPPROXY","2","LOG_CMP_UP","Connectivity Management processor(on module [dec]) is now UP","Connectivity Management processor has come up and is exchanging heartbeats with CP on this SUP slot","No action is required."
"CMPPROXY","2","LOG_CMP_WENT_DOWN","Connectivity Management processor (on module [dec]) went DOWN","Connectivity Management processor has either gone down or is not sending heartbeats for a long time","No action is required."
"CMPPROXY","5","LOG_CMP_AAA_FAILURE","Authentication failed for a login from CMP (on module [dec])","A login attempt has been denied access from Connectivity management processor (CMP) as authentication did not succeed","No action is required."
"CMPPROXY","5","MALLOC_FAILURE","Memory allocation failure","Memory allocation in a call to malloc/calloc has failed.","No action is required."
"CMPPROXY","6","LOG_CMP_AAA_SUCCESS","Authentication succeeded for a login from CMP (on module [dec])","A login attempt has succeeded from Connectivity management processor (CMP) in getting access as AAA succeeded","No action is required."
"COPP","1","COPP_DROPS1","CoPP drops exceed threshold in class: [chars], check show policy-map interface control-plane for more info.","There are CoPP drops, [chars] tell which class has dropped packets.","No action is required."
"COPP","2","COPP_DROPS2","CoPP drops exceed threshold in class: [chars], check show policy-map interface control-plane for more info.","There are CoPP drops, [chars] tell which class has dropped packets.","No action is required."
"COPP","2","COPP_INIT_FAIL","CoPP Initialization failed: [chars]","CoPP Initialization failed. [chars] explains the reason for the failure.","No action is required."
"COPP","2","COPP_MTS_FAIL","Failed to do MTS operation: [chars]","Failed to do MTS operation. [chars] explains the reason for the failure.","No action is required."
"COPP","2","COPP_NO_POLICY","Control-plane is unprotected.","There is no policy to configured toprotect the control-plane.'","When such a syslog appears, the user should protect the control plane by giving the appropriate CoPP commands, either of:"
"COPP","2","COPP_PROFILE_DIFF","CoPP Default Profile may have changed, please check the diffs using show copp diff profile <profile-type","CoPP Default Profile may have changed, please check the diffs using show copp diff profile <profile-type","No action is required."
"COPP","3","COPP_ALLOC_FAIL","Memory allocation failure: [chars]","Failed to alloc required memory. [chars] explains the reason for the failure.","No action is required."
"COPP","3","COPP_DROPS3","CoPP drops exceed threshold in class: [chars], check show policy-map interface control-plane for more info.","There are CoPP drops, [chars] tell which class has dropped packets.","No action is required."
"COPP","3","COPP_PPF_FAIL","Error during PPF operation: [chars]","Failed to do PPF operation. [chars] explains the reason for the failure.","No action is required."
"COPP","3","COPP_PSS_FAIL","Error during PSS operation: [chars]","Failed to do PSS operation. [chars] explains the reason for the failure.","No action is required."
"COPP","4","COPP_DROPS4","CoPP drops exceed threshold in class: [chars], check show policy-map interface control-plane for more info.","There are CoPP drops, [chars] tell which class has dropped packets.","No action is required."
"COPP","5","COPP_DISABLED","COPP Disabled","COPP Service Disabled","No action is required."
"COPP","5","COPP_DROPS5","CoPP drops exceed threshold in class: [chars], check show policy-map interface control-plane for more info.","There are CoPP drops, [chars] tell which class has dropped packets.","No action is required."
"COPP","5","COPP_ENABLED","COPP Enabled","COPP Service nabled","No action is required."
"COPP","5","COPP_INIT","COPP initialized","COPP Service Initialized","No action is required."
"COPP","6","COPP_DROPS6","CoPP drops exceed threshold in class: [chars], check show policy-map interface control-plane for more info.","There are CoPP drops, [chars] tell which class has dropped packets.","No action is required."
"COPP","6","COPP_POLICY_ATTACHED","CoPP policy has been attached to control plane interface.","CoPP policy has been attached to control plane interface.","No action is required."
"COPP","6","COPP_POLICY_DETACHED","CoPP policy has been detached from control plane interface.","CoPP policy has been detached from control plane interface.","No action is required."
"COPP","7","COPP_DROPS7","CoPP drops exceed threshold in class: [chars], check show policy-map interface control-plane for more info.","There are CoPP drops, [chars] tell which class has dropped packets.","No action is required."
"CORE-DMON","2","MODULE_COREDUMP_DONE","kernel coredump completed on module:[dec]","Kernel coredump finishing on a module","No action is required."
"CORE-DMON","2","MODULE_COREDUMP_STARTED","kernel coredump started on module:[dec]","Kernel coredump starting on a module","No action is required."
"CORE-DMON","3","NO_SPACE","Failed to save core file [chars]. Try removing existing core files.","Not enough space to save new core files","No action is required."
"CRDCFG","2","CRDCFG_SRV_CRIT","[chars]","CardConfig CRITICAL ERROR","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"CRDCFG","3","CRDCFG_ERR","[chars]","CardConfig error mesage","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"CRDCFG","3","CRDCFG_MSG","[chars]","CardConfig log mesage","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"CRDCFG","3","CRDCFG_SRV_ERR","[chars]","CardConfigServer error mesage","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"CRDCFG","3","CRDCFG_SRV_MSG","[chars]","CardConfigServer log mesagePlease contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.CRDCFG-SLOT#-2Error Message    CRDCFG-SLOT#-2-CONFIG_ERR: [chars] Explanation    CardConfig Failed to find matching cardid, pnum in database","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"CREDITMON-SLOT#","2","SYSERR_CREDITMON_APP_EXITED","[chars]","Credit Monitor application exited","No action is required."
"CREDITMON-SLOT#","2","SYSERR_CREDITMON_MTS_INIT_ERR","[chars]","Credit Monitor error binding to MTS","No action is required."
"CTS","2","CTS_AUTHENT_FAILURE","CTS Authentication failure on Port [chars] (CTS Failure Reason: [chars] [chars])","Fibre-Channel Authentication failure on Port [chars].(Reason Code [chars] Detail [chars]). Please check password configurations and ensure appropriate security modes on this port as well as peer port","No action is required."
"CTS","2","CTS_FIPS_BYPASS_TEST_FAILED","FIPS bypass test failed for interface: [chars]",".","No action is required."
"CTS","2","CTS_SAP_FAILED","SAP exchange failed on interface [chars]. (Reason: [chars])",".","No action is required."
"CTS","2","CTS_SAP_REKEY_FAILED","SAP exchange failed on interface [chars]. (Reason: [chars])",".","No action is required."
"CTS","2","DBG_INIT_FAILED","Debug Infrastructure Initialization failed ( [chars] )",".","No action is required."
"CTS","2","FC2_E_INIT_FAILED","Fibre-Channel Initialization of an E_Port failed ( [chars] )","CTS Manager has been unable to initialize with the FC-2 E-Port infrastructure.","No action is required."
"CTS","2","FC2_F_INIT_FAILED","Fibre-Channel Initialization of an F_Port failed ( [chars] )","CTS Manager has been unable to initialize with the FC-2 F-Port infrastructure.","No action is required."
"CTS","2","FC2_UNKNOWN_FRM_RECD_CRIT","Received an unexpected/unknown FC-2 frame on [chars]",".","No action is required."
"CTS","2","FSMU_INIT_FAILED","State Machine Infrastructure Initialization failed ( [chars] )",".","No action is required."
"CTS","2","IPC_INIT_FAILED","IPC (Inter Process Communication) Initialization failed ( [chars] )","CTS Manager has been unable to initialize with the IPC infrastructure.","No action is required."
"CTS","2","LICENSE_UNAVAILABLE","License:[chars] unavailable, service exiting","License of [chars] is unavailable. Service will exit now","Please install the license file to continue using the feature."
"CTS","2","MEM_FAILED","Memory operations failed File: [chars] Line [dec] for size [hex] bytes",".","No action is required."
"CTS","2","POST_INIT_FAILED","Post-Initialization failed ( [chars] )",".","No action is required."
"CTS","2","PSS_INIT_FAILED","PSS Infrastructure Initialization failed ( [chars] )",".","No action is required."
"CTS","2","RBACL_ENFORCEMENT_FAILED","Failed to [chars] RBACL enforcement on [chars] %lu",".","No action is required."
"CTS","2","RBACL_LC_INSERT_FAILED","RBACL programming failed for inserted module [dec]",".","No action is required."
"CTS","2","RBACL_TCAM_SPACE_NOT_ENOUGH","Not enough free space left on TCAM",".","No action is required."
"CTS","2","RBACL_UNABLE_PARSE_ACE","Unable to parse RBACL ACE substring: [chars]",".","No action is required."
"CTS","2","RBACL_UPDATE_FAILED","Failed to [chars] RBACL [chars]",".","No action is required."
"CTS","3","DOT1X_AUTHC_FAILED","DOT1X authentication failed on port: [chars]","DOT1X authentication failed on the port","No action is required."
"CTS","5","CTS_IP_SGT_MAP_DELETE","IP-SGT mapping deleted for [chars] on [chars] %lu",".","No action is required."
"CTS","5","CTS_IP_SGT_MAP_UPDATE","[chars] assigned SGT [chars]",".","No action is required."
"CTS","6","CTS_FIPS_BYPASS_TEST_PASSED","FIPS bypass test passed for interface: [chars]",".","No action is required."
"CTS","6","SXP_BIND_FAIL","CTS SXP socket bind failed for [chars]",".","No action is required."
"CTS","6","SXP_CONFIG_MODE_MISMATCH","CTS SXP config mode mis-match with peer [chars] during [chars]",".","No action is required."
"CTS","6","SXP_CONFIG_VER_MISMATCH","CTS SXP config version mis-match with peer [chars] during [chars]",".","No action is required."
"CTS","6","SXP_CONN_PURGED","CTS SXP connection purged: vrf [dec], peer: [chars]",".","No action is required."
"CTS","6","SXP_CONN_STATE_CHG_OFF","CTS SXP connection state for peer [chars] changed to off",".","No action is required."
"CTS","6","SXP_DEFAULT_PASSWORD_RESET","CTS SXP default password reset",".","No action is required."
"CTS","6","SXP_DEFAULT_PASSWORD_SET","CTS SXP default password set",".","No action is required."
"CTS","6","SXP_DEFAULT_SRC_IP_RESET","CTS SXP default source IP address reset to [chars]",".","No action is required."
"CTS","6","SXP_DEFAULT_SRC_IP_SET","CTS SXP default source IP address set to [chars]",".","No action is required."
"CTS","6","SXP_INTERNAL_FAIL","CTS SXP internal failure",".","No action is required."
"CTS","6","SXP_LISTEN_FAIL","CTS SXP socket listen failed",".","No action is required."
"CTS","6","SXP_RX_UNKNOWN_MSG_TYPE","CTS SXP received unknown message type [chars]",".","No action is required."
"CTS","6","SXP_RX_UNKNOWN_OPC_TYPE","CTS SXP received unknown opcode type [dec] for peer [chars]",".","No action is required."
"CTS","6","SXP_STATE_CHANGE","CTS SXP [chars]",".","No action is required."
"CTS","7","CTS_PACE","[chars]",".","No action is required."
"CTS","7","CTS_PPF_RBACL_ENABLE","[chars]",".","No action is required."
"CTS","7","CTS_PPF_SESS_STATE","[chars] Session id [dec] ([hex])",".","No action is required."
"CTS","7","CTS_PPF_SGT_DGT","[chars] rbacl [chars] sgt [dec] dgt [dec]",".","No action is required."
"CTS","7","CTS_PPF","[chars]",".","No action is required."
"CTS","7","CTS_SAL","CTS: [chars]",".","No action is required."
"CTS","7","SGT_MAP_INIT","CTS: [chars]",".","No action is required."
"DCEFIB-SLOT#","0","CLI_INIT_FAILED","CLI library initialization failed!","L2mp unicast fib failed to initialize CLI infrastructure's backend library. This is a fatal error.","No action is required."
"DCEFIB-SLOT#","0","TIMER_INIT_FAILED","Timer subsystem initialization failed!","L2mp unicast fib failed to initialize timer library. This is a fatal error.","No action is required."
"DCEFIB-SLOT#","2","DCEFIB_MEM_ALLOC","Memory allocation failed. [chars]","Memory allocation failed. This is a critical failure","No action is required."
"DCEFIB-SLOT#","2","DCEFIB_RECOVERY_ERROR","Error in Recovery: [chars]","L2mp unicast fib failed to recover after a re-start. This is a fatal error.","No action is required."
"DCEFIB-SLOT#","2","U2FIB_ERR","[chars]","L2mp unicast fib encountered an error","No action is required."
"DCEFIB-SLOT#","6","INITIALIZED","Internal state created [chars]","L2mp unicast fib has created its internal state stateless/stateful [chars].","No action is required."
"DCEFIB-SLOT#","6","U2FIB_INFO","[chars]","L2mp unicast fib notice","No action is required."
"DCEFIB-SLOT#","6","VDC_CREATED","VDC [dec] created","Request to create VDC [dec] in l2mp unicsat fib was successful.","No action is required."
"DCEFIB-SLOT#","6","VDC_REMOVED","VDC [dec] Removed","L2mp unicast fib has successfully removed VDC [dec] from its databases.","No action is required."
"DEBUGPROXY","6","SSM_DEBUG_PROXY_COMMON","SSM debug proxy [chars] [dec]","General SSM debug proxy information","No action is required."
"DEVICE-ALIAS","2","ALLOC_FAILED","Memory allocation failed for size:[dec] type:[dec]","Memory allocation failed for size [dec] type [dec]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"DEVICE-ALIAS","2","INIT_FAILED","[chars]","An error occurred during initialization. [chars] indicates the reason for failure.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"DEVICE-ALIAS","3","CFS_OPER_FAILED","[chars]","An error occurred while performing a CFS operation. [chars] indicates the CFS operation and the reason for failure.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"DEVICE-ALIAS","3","CLEAR_FAILED","[chars]","An error occurred while clearing the session. [chars] indicates the reason for failure.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"DEVICE-ALIAS","3","COMMIT_FAILED","[chars]","An error occurred while committing the database. [chars] indicates the reason for failure.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"DEVICE-ALIAS","3","COMMIT_REJECTED","[chars]","Commit request received from remote switch is rejected. [chars] indicates the reason for failure.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"DEVICE-ALIAS","3","LOCK_FAILED","[chars]","An error occurred while acquiring the lock. [chars] indicates the reason for failure.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"DEVICE-ALIAS","3","LOCK_REJECTED","[chars]","Lock request received from remote switch is rejected. [chars] indicates the reason for failure.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"DEVICE-ALIAS","3","MERGE_ACTIVATION_FAILED","[chars]","An error occurred while activating the merged database. [chars] indicates the reason for failure.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"DEVICE-ALIAS","3","MERGE_ACTIVATION_REJECTED","[chars]","Merge activation request received from remote switch is rejected. [chars] indicates the reason for failure.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"DEVICE-ALIAS","3","MERGE_FAILED","[chars]","An error occurred during merge operation. [chars] indicates the reason for failure.","Compare device-alias configuration with the other switches in the fabric, resolve the conflicts if any and commit the changes."
"DEVICE-ALIAS","3","MERGE_MREQ_REJECTED","[chars]","MREQ received from remote switch is rejected. [chars] indicates the reason for failure.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"DEVICE-ALIAS","3","MERGE_MRESP_REJECTED","[chars]","MRESP received from remote switch is rejected. [chars] indicates the reason for failure.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"DEVICE-ALIAS","3","MERGE_VALIDATION_FAILED","[chars]","An error occurred while validating the merged database. [chars] indicates the reason for failure.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"DEVICE-ALIAS","3","MERGE_VALIDATION_REJECTED","[chars]","Merge validation request received from remote switch is rejected. [chars] indicates the reason for failure.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"DEVICE-ALIAS","3","MTS_OPER_FAILED","[chars]","An error occurred during MTS operation. [chars] indicates the MTS operation and the reason for failure.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"DEVICE-ALIAS","3","PSS_OPER_FAILED","[chars]","An error occurred during PSS operation. [chars] indicates the PSS operation and the reason for failure.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"DEVICE-ALIAS","3","UNLOCK_FAILED","[chars]","An error occurred while releasing the lock. [chars] indicates the reason for failure.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"DEVICE-ALIAS","3","UNLOCK_REJECTED","[chars]","Unlock request received from remote switch is rejected. [chars] indicates the reason for failure.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"DEVICE-ALIAS","3","VALIDATION_FAILED","[chars]","An error occurred while validating the database. [chars] indicates the reason for failure.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"DEVICE-ALIAS","3","VALIDATION_REJECTED","[chars]","Validation request received from remote switch is rejected. [chars] indicates the reason for failure.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"DEVICE-ALIAS","6","CLEAR_FAILED_INFO","[chars]","An error occurred while clearing the session. [chars] indicates the additional information regarding failure.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"DEVICE-ALIAS","6","COMMIT_FAILED_INFO","[chars]","An error occurred while committing the database. [chars] indicates the additional information regarding failure.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"DEVICE-ALIAS","6","IMPORT_DEFINITION_CONFLICT","Fcalias [chars] could not be imported due to definition conflict","Fcalias [chars] could not be imported due to definition conflict. Either there is already a device-alias configuration present with the same definition OR another VSAN specified in the import VSAN range has an fcalias with the same definition.","Resolve the conflict and issue the import command again."
"DEVICE-ALIAS","6","IMPORT_MEMBER_TYPE_CONFLICT","Fcalias [chars] could not be imported due to having unsupported member type","Fcalias [chars] could not be imported due to having unsupported member types. Fcalias can be imported only if it has Port WWN based members..","Make sure that the fcalias has Port WWN based members and issue the import command again."
"DEVICE-ALIAS","6","IMPORT_NAME_CONFLICT","Fcalias [chars] could not be imported due to name conflict","Fcalias [chars] could not be imported due to name conflict. Either there is already a device-alias configuration present with the same name OR another VSAN specified in the import VSAN range has an fcalias with the same name.","Resolve the conflict and issue the import command again."
"DEVICE-ALIAS","6","IMPORT_NUM_MEMBERS_CONFLICT","Fcalias [chars] could not be imported due to having unsupported number of members","Fcalias [chars] could not be imported due to having unsupported number of members. Fcalias can be imported only if it has exactly one member..","Make sure that the fcalias has exactly one member and issue the import command again."
"DEVICE-ALIAS","6","LOCK_FAILED_INFO","[chars]","An error occurred while acquiring the lock. [chars] indicates the additional information regarding failure.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"DEVICE-ALIAS","6","MERGE_ACTIVATION_FAILED_INFO","[chars]","An error occurred while activating the merged database. [chars] indicates the additional information regarding failure.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"DEVICE-ALIAS","6","MERGE_VALIDATION_FAILED_BUSY","[chars]","Merged database could not be validated as some of the applications returned busy. [chars] indicates information about the application returned busy. There is no user intervention necessary. The validation would be automatically retried after some time.","No DDTS."
"DEVICE-ALIAS","6","MERGE_VALIDATION_REJECTED_BUSY","[chars]","Merged database received from the remote switch could not be validated as some of the applications returned busy. [chars] indicates information about the application returned busy. There is no user intervention necessary. The validation would be automatically retried after some time.","No DDTS."
"DEVICE-ALIAS","6","UNLOCK_FAILED_INFO","[chars]","An error occurred while releasing the lock. [chars] indicates the additional information regarding failure.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"DEVICE-ALIAS","6","VALIDATION_ABORTED","[chars]","Local validation is aborted. [chars] indicates the reason why validation is aborted.","No DDTS."
"DEVICE_TEST","2","ASIC_REG_CHECK_FAIL","Module [dec] has failed test [chars] [dec] times on device [chars] [chars] [dec] [chars] due to error [chars]","Online diagnostics ASICRegisterCheck test has failed","No action is required."
"DEVICE_TEST","2","COMPACT_FLASH_FAIL","Module [dec] has failed test [chars] [dec] times on device Compact Flash due to error [chars]","Online diagnostics CompactFlash test has failed","No action is required."
"DEVICE_TEST","2","CRYPTO_DEVICE_FAIL","Module [dec] has failed test [chars] [dec] times on Crypto device due to error [chars]","Online diagnostics CryptoDevice test has failed","No action is required."
"DEVICE_TEST","2","EOBC_FAIL","Module [dec] has failed test [chars] on EOBC due to error [chars]","Online diagnostics EOBC test has failed","No action is required."
"DEVICE_TEST","2","FAN_MOD_FAIL","Module [dec] has failed test [chars] [dec] times on System Mgmt Bus for chassis [chars] instance [dec] due to error [chars] error number [hex]","Online diagnostics SystemMgmtBus test has failed","No action is required."
"DEVICE_TEST","2","MALLOC_FAILURE","Memory allocation failed","Device Test process could not allocate memory","No action is required."
"DEVICE_TEST","2","MGMT_PORT_SKIP","Module [dec] has skipped test [chars] on Management Port due to error [chars]","Online diagnostics ManagementPort test is skipped","No action is required."
"DEVICE_TEST","2","NVRAM_FAIL","Module [dec] has failed test [chars] [dec] times on device NVRAM due to error [chars]","Online diagnostics NVRAM test has failed","No action is required."
"DEVICE_TEST","2","OBFL_FAIL","Module [dec] has failed test [chars] [dec] times on device OBFL due to error [chars]","Online diagnostics OBFL test has failed","No action is required."
"DEVICE_TEST","2","POWER_SUPPLY_FAIL","Module [dec] has failed test [chars] [dec] times on System Mgmt Bus for chassis [chars] instance [dec] due to error [chars] error number [hex]","Online diagnostics SystemMgmtBus test has failed","No action is required."
"DEVICE_TEST","2","PRIMARY_BOOTROM_FAIL","Module [dec] has failed test [chars] [dec] times on device Primary BootROM due to error [chars]","Online diagnostics PrimaryBootROM test has failed","No action is required."
"DEVICE_TEST","2","PWR_MGMT_BUS_FAIL","Module [dec] has failed test [chars] [dec] times on device Power Mgmt Bus on slot [dec] due to error [chars] error number [hex]","Online diagnostics PwrMgmtBus test has failed","No action is required."
"DEVICE_TEST","2","RTC_FAIL","Module [dec] has failed test [chars] [dec] times on device RealTimeClock due to error [chars]","Online diagnostics RealTimeClock test has failed","No action is required."
"DEVICE_TEST","2","SECONDARY_BOOTROM_FAIL","Module [dec] has failed test [chars] [dec] times on device Secondary BootROM due to error [chars]","Online diagnostics SecondaryBootROM test has failed","No action is required."
"DEVICE_TEST","2","SPINE_CONTROL_BUS_FAIL","Module [dec] has failed test [chars] [dec] times on device Spine Control Bus on slot [dec] due to error [chars] error number [hex]","Online diagnostics SpineControlBus test has failed","No action is required."
"DEVICE_TEST","2","STANDBY_LOOPBACK_TEST_FAIL","Module [dec] has failed test [chars] [dec] times on [chars] [dec] due to error [chars]","Online diagnostics StandbyFabricLoopback test has failed","No action is required."
"DEVICE_TEST","2","TWOWIRE_STW_FAIL","Module [dec] has failed test [chars] [dec] times on Status Bus on slot [dec] due to error [chars]","Online diagnostics Status bus test has failed","No action is required."
"DEVICE_TEST","2","USB_FAIL","Module [dec] has failed test [chars] [dec] times on device USB due to error [chars]","Online diagnostics USB test has failed","No action is required."
"DEVICE_TEST","3","STANDBY_TEST_GET_DIAG_VQI_FAIL","Standby test get diag vqi failed due to error [hex]","Device Test StandbyLoopback Test failed get vqi","No action is required."
"DEVICE_TEST","3","STANDBY_TEST_GET_SPINE_FAIL","Standby test get spines failed due to error [hex]","Device Test StandbyFabricLoopback Test get spine failed","No action is required."
"DEVICE_TEST","3","STANDBY_TEST_INIT_FAIL","Init for standby test failed due to error [hex]","Device Test StandbyFabricLoopback Test failed init process","No action is required."
"DEVICE_TEST","3","STANDBY_TEST_MTS_FAIL","Mts Init for standby test failed due to error [hex]","Device Test StandbyFabricLoopback Test failed mts init","No action is required."
"DEVICE_TEST","3","STANDBY_TEST_SOCKET_FAIL","Standby test socket error [chars]: [hex]","Device Test StandbyFabricLoopback Test Socket error","No action is required."
"DEVICE_TEST","4","THREAD_CREATE_FAIL","Thread creation failed","Device Test process could not create threads","No action is required."
"DEVICE_TEST","4","TIMER_CREATE_FAIL","Timer creation failed","Device Test process could not create timer","No action is required."
"DEVICE_TEST","4","TIMER_START_FAIL","Timer start failed","Device Test process could not start timer","No action is required."
"DEVICE_TEST","5","NOTICE_TEST","Memory allocation failed notice","Device Test process could not allocate memory","No action is required."
"DEVICE_TEST","6","INFO_TEST","Memory allocation failed info","Device Test process could not allocate memory","No action is required."
"DEV_LOG_SUP","3","ERROR","[chars]","Dev_log_sup encountered an error","No action is required."
"DEV_LOG","3","ERROR","[chars]","Dev_log_lc encountered an error","No action is required."
"DEV_LOG-SLOT#","4","DEV_LOG_LC_ERROR","[chars]","Dev_log_lc encountered an error","No action is required."
"DFTM-SLOT#","2","DFTM_INTF_NOT_FOUND","Interface [chars] not found in DFTM database [chars]","DFTM database doesnthavetheinterface.'","No action is required."
"DFTM-SLOT#","2","DFTM_INVALID_FTAG_NUM","DFTM received invalid number of FTags [dec] from M2RIB","DFTM recvd invalid number of FTags from M2RIB.","No action is required."
"DFTM-SLOT#","2","DFTM_INVALID_INTF_NUM","DFTM has invalid number of interfaces [dec] in the DB","DFTM has invalid number of interfaces in the DB.","No action is required."
"DFTM-SLOT#","2","DFTM_PC_NUM_MEMB_INVALID","DFTM received invalid number of PC members [dec] from ELTM","DFTM recvd invalid number of PC members from ELTM.","No action is required."
"DFTM-SLOT#","2","DFTM_VLAN_NOT_FOUND","VLAN [dec] not found in DFTM database [chars]","DFTM database doesnthavetheVLAN.'","No action is required."
"DFTM-SLOT#","3","DFTM_BDDB_PROG_FAILED","DFTM failed to program BDDB Entry","DFTM failed to program BDDB Entry","No action is required."
"DFTM-SLOT#","3","DFTM_BDT_PROG_FAILED","DFTM failed to program BD Table Entry","DFTM failed to program BD Table Entry","No action is required."
"DFTM-SLOT#","3","DFTM_IFIDX_INVALID_PORT_LAYER","Invalid Port Layer Received for interface: [chars]","Invalid Port Layer Received for interface","No action is required."
"DFTM-SLOT#","3","DFTM_IFIDX_INVALID_PORT_MODE","Invalid Port Mode Received for interface: [chars]","Invalid Port Mode Received for interface","No action is required."
"DFTM-SLOT#","3","DFTM_IFIDX_INVALID_PORT_TYPE","Invalid Port Type Received for interface: [chars]","Invalid Port Type Received for interface","No action is required."
"DFTM-SLOT#","3","DFTM_IFIDX_TYPE_ERROR","Failed to get type for interface: [chars]","Failed to get type for the interface","No action is required."
"DFTM-SLOT#","3","DFTM_INVALID_PRIM_SEC_VLAN_REQ","DFTM received prim-sec request for a non-exiting sec vlan [dec] on primary [dec]","DFTM recvd prim-sec vlan mapping request for a non-existing sec vlan on prim vlan","No action is required."
"DFTM-SLOT#","3","DFTM_L2L3CT_PROG_FAILED","DFTM failed to program L2L3 Consistency Table Entry","DFTM failed to program L2L3 Consistency Table Entry","No action is required."
"DFTM-SLOT#","3","DFTM_MFT_PROG_FAILED","DFTM failed to program Multicast FTag Table Entry","DFTM failed to program Multicast Ftag Table Entry","No action is required."
"DFTM-SLOT#","3","DFTM_SDT_PROG_FAILED","DFTM failed to program SGT DGT Table Entry","DFTM failed to program SGT DGT Table Entry","No action is required."
"DFTM-SLOT#","3","DFTM_VTT_PROG_FAILED","DFTM failed to program VLAN Translation Table Entry for vlan [dec], xlt_vlan [dec] on fe [dec]","DFTM failed to program VLAN Translation Table","No action is required."
"DHCP_SNOOP","2","DHCP_SNOOP_PROGRAM_EXIT","[chars]","DHCP snoop process did an abnormal exit","No action is required."
"DHCP_SNOOP","2","HWPGMFAILURE","Hardware programming has failed: [chars]","Hardware programming has failed. [chars] explains the reason for the failure.","No action is required."
"DHCP_SNOOP","2","INITFAIL","DHCP Daemon Initialization failed: [chars]","DHCP Daemon Initialization failed. [chars] explains the reason for the failure.","No action is required."
"DHCP_SNOOP","2","PSSERROR","[chars]","DHCP Daemon encountered a PSS error. [chars] specifies the context where the failure occurred.","No action is required."
"DHCP_SNOOP","2","REGPARTREE","Unable to register par tree: [chars]","Could not register par tree. [chars] explains the reason for the failure.","No action is required."
"DHCP_SNOOP","3","ALLOCFAIL","Heap Memory allocation failed: [chars]","DHCP Daemon is out of dynamic memory. [chars] specifies the context where the failure occurred.","No action is required."
"DHCP_SNOOP","3","ASSERTION_FAILED","[chars]:[dec]","DHCP Snoop process has hit an assert condition at file [chars] line number [dec]","No action is required."
"DHCP_SNOOP","3","DHCPDENIEDARP","ARP frame denied due to DHCP snooping binding on interface [chars] vlan [dec] sender mac [chars] sender ip [chars] target mac [chars] target ip [chars].","[chars] identifies interface and [dec] identifies the vlan on which ARP packets have been denied. [chars] identifies sender mac and [chars] identifies the sender ip. [chars] identifies the target mac and [chars] identifies the target ip.","No action is required."
"DHCP_SNOOP","3","DHCPRATELIMIT","Interface [chars] has been error disabled due to excessive ingress rate [dec] of DHCP packets.","[chars] identifies the interface which has been error disabled due to excessive ingress rate [dec].","No action is required."
"DHCP_SNOOP","3","HWPGMFAILURE","Hardware programming has failed: [chars]","Hardware programming has failed. [chars] explains the reason for the failure.","No action is required."
"DHCP_SNOOP","3","INVDHCPPKTS","Validation errors while processing DHCP packet received on interface [chars] vlan [dec] Reason:[chars]. Dropping the packet","Validation errors DHCP packet receieved on the interface [chars] vlan [[dec]]. Reason:[chars]","No action is required."
"DHCP_SNOOP","3","MTSERROR","[chars]","DHCP Daemon encountered an MTS error. [chars] specifies the context where the error occurred.","No action is required."
"DHCP_SNOOP","3","PKTDROP","Packet dropped. Reason - [chars]","Dropping the packet. [char] identifies the reason.","No action is required."
"DHCP_SNOOP","3","PKTRECVFAIL","Failed to receive packet - [chars]","Failed to receive packet. [char] identifies the reason.","No action is required."
"DHCP_SNOOP","3","PKTSENDFAIL","Failed to send packet, - [chars]","Failed to send packet. [char] identifies the reason.","No action is required."
"DHCP_SNOOP","3","SOCKBINDFAIL","Failed to bind to raw socket - [chars]","Failed to bind to socket. [char] identifies the reason.","No action is required."
"DHCP_SNOOP","3","SOCKOPENFAIL","Failed to open socket for receiving DHCP packets - [chars]","An attempt to open a socket for receiving DHCP packets failed. [char] identifies the reason.","No action is required."
"DHCP_SNOOP","4","ACL_DENY","[dec] Invalid ARP messages ([chars]) on [chars], vlan [dec]. ([[chars]/[chars]/[chars]/[chars]/[chars]])","Packet-count [dec] Invalid ARPs (arp-type [chars]) on interface [chars], vlan [dec]. ([sender-mac [chars]/sender-ip [chars]/ target-mac [chars]/target-ip [chars]/ time-of-day [chars]])","No action is required."
"DHCP_SNOOP","4","DHCP_SNOOPING_DENY","[dec] Invalid ARP messages ([chars]) on [chars], vlan [dec]. ([[chars]/[chars]/[chars]/[chars]/[chars]])","Packet-count [dec] Invalid ARPs (arp-type [chars]) on interface [chars], vlan [dec]. ([sender-mac [chars]/sender-ip [chars]/ target-mac [chars]/target-ip [chars]/ time-of-day [chars]])","No action is required."
"DHCP_SNOOP","4","ERROR_DISABLED","Interface [chars] has moved to error disabled state due to excessive rate [dec] of ingress ARP packets","Interface [chars] has moved to error disabled state due to excessive rate [dec] of ingress ARP packets","No action is required."
"DHCP_SNOOP","4","INVALID_ARP","[dec] Invalid ARP messages ([chars]) on [chars], vlan [dec]. ([[chars]/[chars]/[chars]/[chars]/[chars]])","Packet-count [dec] Invalid ARPs (arp-type [chars]) on interface [chars], vlan [dec]. ([sender-mac [chars]/sender-ip [chars]/ target-mac [chars]/target-ip [chars]/ time-of-day [chars]])","No action is required."
"DHCP_SNOOP","4","SMARTRELAYMAXIPADDR","Smart relay is supported only on first [dec] IP addresses of the interface [chars].","There are more than SMARTRELAYMAXIPADDR addresses configured on the interface. [dec] is the number of IP addresses with which smart relay supported [chars] identifies the interface. This is an informational message.","No action is required."
"DHCP_SNOOP","4","SMARTRELAYMAXLMT","Smart relay MAX limit [dec] reached. All subsequent DHCP packets will be relayed with primary address of inbound interface as relay agent address.","Smart relay MAX limit reached. [dec] is the number of smart relay bindings This is an informational message.","No action is required."
"DHCP_SNOOP","4","SUBNETBCASTRELAYMAXIPADDR","subnet-broadcast relay is supported only on first [dec] IP addresses of the interface [chars].","There are more than SUBNETBCASTRELAYMAXIPADDR addresses configured on the interface. [dec] is the number of IP addresses with which subnet-broadcast relay supported [chars] identifies the interface. This is an informational message.","No action is required."
"DHCP_SNOOP","5","ACL_PERMIT","[dec] ARP messages ([chars]) on [chars], vlan [dec]. ([[chars]/[chars]/[chars]/[chars]/[chars]])","Packet-count [dec] ARPs (arp-type [chars]) on interface [chars], vlan [dec]. ([sender-mac [chars]/sender-ip [chars]/ target-mac [chars]/target-ip [chars]/ time-of-day [chars]])","No action is required."
"DHCP_SNOOP","5","DHCPHOSTADD","A new Host is [chars] connected to interface [chars] in VLAN [dec] and is allocated IP address [chars] for [dec] secs.","A Host identified by [chars] has been added. [chars] identifies the interface. [dec] identifies the VLAN. [chars] identifies IP address. [dec] identifies the lease time in secs. This is an informational message.","No action is required."
"DHCP_SNOOP","5","DHCPLEASEEXPIRE","Lease expired for host [chars] having IP address [chars] connected to interface [chars] in VLAN [dec] for lease [dec] secs.","The lease for host identified by [chars] with IP address [chars] connected to interface [chars] in VLAN [dec] with lease [dec] has expired.","No action is required."
"DHCP_SNOOP","5","DHCP_SNOOPING_PERMIT","[dec] ARP messages ([chars]) on [chars], vlan [dec]. ([[chars]/[chars]/[chars]/[chars]/[chars]])","Packet-count [dec] ARPs (arp-type [chars]) on interface [chars], vlan [dec]. ([sender-mac [chars]/sender-ip [chars]/ target-mac [chars]/target-ip [chars]/ time-of-day [chars]])","No action is required."
"DHCP_SNOOP","5","VLANDISABLE","DHCP Snooping disabled on vlan [dec]","DHCP Snooping was disabled on a given vlan. [dec] is the VLAN-ID that identifies the vlan. This is an informational message.","No action is required."
"DHCP_SNOOP","5","VLANENABLE","DHCP Snooping enabled on vlan [dec]","DHCP Snooping was enabled on a given vlan. [dec] is the VLAN-ID that identifies the vlan. This is an informational message.","No action is required."
"DHCP_SNOOP","6","DAIVLANDISABLE","DAI disabled on vlan [dec]","Dynamic ARP Inspection was disabled on a given vlan. [dec] is the VLAN-ID that identifies the vlan. This is an informational message.","No action is required."
"DHCP_SNOOP","6","DAIVLANENABLE","DAI enabled on vlan [dec]","Dynamic ARP Inspection was enabled on a given vlan. [dec] is the VLAN-ID that identifies the vlan. This is an informational message.","No action is required."
"DHCP_SNOOP","6","DHCPBINDSYNC","Binding entry with MAC [chars] interface [chars] VLAN [dec] IP address [chars] and lease time [dec] secs is synced.","Binding entry identified by [chars] has been synced. [chars] identifies the interface. [dec] identifies the VLAN. [chars] identifies IP address. [dec] identifies the lease time in secs. This is an informational message.","No action is required."
"DHCP_SNOOP","6","DHCPEXIT","DHCP Daemon shutting down gracefully.","DHCP Daemon is shutting down gracefully. This is an informational message.","No action is required."
"DHCP_SNOOP","6","DHCPPERMITTEDARP","ARP frame permitted due to DHCP snooping binding on interface [chars] vlan [dec] sender mac [chars] sender ip [chars] target mac [chars] target ip [chars].","[chars] identifies interface and [dec] identifies the vlan on which ARP packets have been permitted. [chars] identifies sender mac and [chars] identifies the sender ip. [chars] identifies the target mac and [chars] identifies the target ip.","No action is required."
"DHCP_SNOOP","6","DHCPPKTFWD","Gracefully forwarding DHCP packet. Reason: [chars]","Gracefully forwarding DHCP packet. reason [chars]","No action is required."
"DHCP_SNOOP","6","DHCPUP","DHCP Daemon Up.","DHCP Daemon was created successfully and is up and running. This is an informational message.","No action is required."
"DHCP_SNOOP","6","INFO","[chars]","An event during switchover. [chars] explains the reason for the failure.","No action is required."
"DHCP_SNOOP","6","INTFDISABLE","IP Src Guard disabled on intf [chars]","IP Src Guard was disabled on a given intf. [chars] is the intf-ID string that identifies the intf. This is an informational message.","No action is required."
"DHCP_SNOOP","6","INTFENABLE","IP Src Guard enabled on intf [chars]","IP Src Guard was enabled on a given intf. [chars] is the intf-ID string that identifies the intf. This is an informational message.","No action is required."
"DHCP_SNOOP","6","NONDHCPPKTFWD","Non DHCP packet with src port:[dec] dst port:[dec] on intf:[chars] vlan:[dec]. Forwarding on [chars]","Non DHCP packet arrived with UDP src/dst ports [dec], [dec] on interface [chars], vlan [dec]. Forwarding the packet on [chars]","No action is required."
"DHCP_SNOOP","6","OPT82INSTFAIL","[chars] [chars]","Insertion of Option82 suboptions failed. [chars] tells the failure. [chars] explains the reason for failure. This is an informational message.","No action is required."
"DIAGCLIENT","2","DIAG_BOOTUP_COMPLETE","Module <[dec]","Bootup Test completed","Nothing to be done if the test reports SUCCESS otherwise copy the error message exactly as it appears on the console, gather the output of show tech-support, and contact your Cisco technical support representative with the gathered information"
"DIAGCLIENT","2","EEM_ACTION_HM_SHUTDOWN","Test <[chars]","Informational Syslog","No action is required."
"DIAGCLIENT","2","PSS_READ_FAILURE","Read from PSS failed on Module <[dec]","Read operation from PSS store failed","No action is required."
"DIAGCLIENT","2","PSS_WRITE_FAILURE","Write to PSS failed on Module <[dec]","Write operation on PSS store failed","No action is required."
"DIAGCLIENT","3","ONDEMAND_FAIL_EXCESS","Module <[dec]","Ondemand test has failed more than configured number of times","Copy the error message exactly as it appears on the console, gather the output of show tech-support, and contact your Cisco technical support representative with the gathered information"
"DIAGCLIENT","4","LC_OFFLINE_FOR_CURR_SLOT","Received LC offline event for the current slot:[dec]. Ignoring it","Informational Syslog","No action is required."
"DIAGCLIENT","4","MTS_SEND_FAILURE","MTS send failed, mts_opc: [chars], dest slot: [dec], dest SAP: [dec], error-id: [hex]","MTS send reports failure","No action is required."
"DIAGCLIENT","5","CALLOC_FAILURE","Memory allocation failed","DiagClient process could not allocate memory","No action is required."
"DIAGCLIENT","5","DIAG_ONDEMAND_TEST_FINISH","Module [dec]: Ondemand test [chars] finished","Informational Syslog","No action is required."
"DIAGCLIENT","5","DIAG_ONDEMAND_TEST_START","Module [dec]: Ondemand test [chars] started","Informational Syslog","No action is required."
"DIAGCLIENT","5","DIAG_ONDEMAND_TEST_STOP","Module [dec]: Ondemand test [chars] stopped","Informational Syslog","No action is required."
"DIAGCLIENT","5","DIAG_SCHED_COMPLETE","Module <[dec]","A scheduled Test was completed","No action is required."
"DIAGCLIENT","5","ONDEMAND_FAIL","Module <[dec]","The specified test has reported FAILURE in this Iteration","No action is required."
"DIAGCLIENT","5","ONDEMAND_SUCCESS","Module <[dec]","The specified test has reported SUCCESS in this Iteration","No action is required."
"DIAGCLIENT","7","DIAG_HM_FAIL","Module <[dec]","A Health Monitoring Test has reported failure","Ensure the line card is firmly in the slot, reseat if necessary, and attempt to run the test again if the line card is not seated properly in the slot. If the line card was properly seated in the slot, copy the error message exactly as it appears on the console, gather the output of show tech-support, and contact your Cisco technical support representative with the gathered information."
"DIAGCLIENT","7","PER_PORT_TEST_FAIL","Module <[dec]","Per Port Test has failed on the above all ports","No action is required."
"DIAGMGR","2","MTS_SEND_FAILURE","MTS send failed, mts_opc: [chars], dest slot: [dec], dest SAP: [dec], error-id: [hex]","MTS send reports failure","No action is required."
"DIAGMGR","2","PSS_DELETE_FAILURE","Read from PSS failed on Module <[dec]","Read operation from PSS store failed","No action is required."
"DIAGMGR","2","PSS_WRITE_FAILURE","Write to PSS failed on Module <[dec]","Write operation on PSS store failed","No action is required."
"DIAGMGR","3","DIAG_MAJOR_DEFECT","Module <[dec]","A major error was detected during diagnostic testing","Re-seat the card and retry the test. If the same result occurs after reseating the card and retrying the test, copy the error message exactly as it appears on the screen and gather the output of show tech-support and any other relevant information. Contact your technical support representative with the gathered information."
"DIAGMGR","3","DIAG_MINOR_DEFECT","Module <[dec]","A minor error was detected during diagnostic testing","Re-seat the card and retry the test. If the same result occurs after reseating the card and retrying the test, copy the error message exactly as it appears on the screen and gather the output of show tech-support and any other relevant information. Contact your technical support representative with the gathered information"
"DIAGMGR","3","GET_CURR_SLOT_FAIL","Failed to get the current slot for the process. Error:[chars]","The process initialization failed to get the current slot.","This is an informational message stating that a process initialization failure."
"DIAGMGR","4","CURR_SLOT_OFFLINE","Recevied an LC offline event for the current slot:[dec]. Ignoring it","The process received an offline event for the slot it is running. Ignoring it.","This is an informational message stating that an unexpected event has been encountered."
"DIAGMGR","4","DISRPT_TST_START","Starting Test <[chars]","Starting a Disruptive Test can disturb the systemsnormalfunctionality'","Reset target module"
"DIAGMGR","4","FIXED_INTRVL_CHANGED","The users are not allowed to change monitoring interval of Test <[chars]","The specified health monitoring test interval is not user-configurable and therefore cannot be changed","Nothing. The specific health monitoring interval is not user- configurable by design so nothing can be done to change the interval"
"DIAGMGR","5","BOOTUP_CONF","Diagnostic Bootup Level: <[chars]","Current Diagnostic BootUp Level being configure or changed","No action is required."
"DIAGMGR","5","CALLOC_FAILURE","Memory allocation failure","Memory allocation in a call to malloc/calloc has failed","No action is required."
"DIAGMGR","5","CHANGE_ALWAYS_HM","Health Monitoring test <[chars]","The specified health monitoring test must be run and cannot be disabled","Nothing. The specific health monitoring test cannot be disabled by design. The system is working properly."
"DIAGMGR","5","HM_START","Health monitoring test <[chars]","Health Monitoring Test started","No action is required."
"DIAGMGR","5","HM_STOP","Disabling health monitoring test <[chars]","Health Monitoring Test has been stopped It can be enabled through the diagnostic monitor..... command","No action is required."
"DIAGMGR","5","INTRVL_INCORRECT","Monitoring Interval is less than minimum of [dec] seconds required for Module <[dec]","Health Monitoring cannot be enabled for the specified test because the interval for the test has been incorrectly set","The system is working properly and no user action is required. If you want to specify a smaller testing interval, the error message text provides the lowest possible configurable interval for the specified monitoring interval"
"DIAGMGR","5","MODULE_MISSING","Diagnostic command issued on non-existing Module <[dec]","A line card could not be located in a slot where a diagnostic action was requested","Ensure the targeted line card is properly seated in the specified slot. If the line card is properly seated, ensure the correct slot was indicated in the command-line interface. If the line card is well-seated and the correct slot was specified, copy the error message exactly as it appears on the screen as well as the output of show tech-support and paste the output into a separate file. Contact your technical support representative with the gathered information"
"DIAGMGR","5","NONHM_AS_HM","The Test <[chars]","Non-HM test cannot be scheduled to run as a Health Monitoring test","No action is required."
"DIAGMGR","6","BOOTUP_DIAG_OK","Module <[dec]","The diagnostic tests did not detect any error on the card.","This is an informational message stating that the line card passed the diagnostic tests."
"DIAGMGR","6","BOOTUP_TEST_STARTED","Module <[dec]","Starting bootup testing for above module","No action is required."
"DIAG_PORT_LB","2","FIPS_RANDOM_ERROR","Random Number Generation Failure","Random Number genration failed in FIPS module","No action is required."
"DIAG_PORT_LB","2","LCM_RESP_SEND_FAILURE","LC Inserted request response send to Module Manager failed . Error:[chars]","Failed to send the response for LC insertion to Module Manager.","No action is required."
"DIAG_PORT_LB","2","LIF_GET_ERROR","[chars]([dec]) [chars] Error:[chars]","Port Loopback test process failed to get Diagnostic LIF id","No action is required."
"DIAG_PORT_LB","2","MALLOC_FAILURE","[chars]([dec]) Memory allocation failed.","Port Loopback test process could not allocate memory","No action is required."
"DIAG_PORT_LB","2","PORTLOOPBACK_TEST_FAIL","Module:[dec] Test:PortLoopback failed [dec] consecutive times. Faulty module:[chars] [chars] Error:[chars]","PortLoopback test failed on the module consecutively","No action is required."
"DIAG_PORT_LB","2","PROC_INIT_FAILURE","[chars]([dec]) [chars] Error:[chars]","Port Loopback test process failed in process initialization","No action is required."
"DIAG_PORT_LB","2","REWRITE_ENGINE_LOOPBACK_TEST_FAIL","Module:[dec] Test:RewriteEngine Loopback failed [dec] consecutive times. Faulty module:[chars] [chars] Error:[chars]","Rewrite Engine Loopback test failed on the module consecutively","No action is required."
"DIAG_PORT_LB","2","SNAKE_TEST_LOOPBACK_TEST_FAIL","Module:[dec] Test:SnakeLoopback failed [dec] consecutive times. Faulty module:[chars] affected ports:[chars] Error:[chars]","Snake test failed on the module consecutively","No action is required."
"DIAG_PORT_LB","3","DIAG_FWD_PATH_SETUP_FAILURE","[chars]. Module:[dec] Error:[chars].","Forwarding path setup for port loopback tests failed","No action is required."
"DIAG_PORT_LB","3","DIAG_PKT_SEND_FAILURE","[chars]([dec]) [chars]. Error:[chars]","Port Loopback test process failed to send loopback packets.","No action is required."
"DIAG_PORT_LB","3","FSM_LIB_ERROR","[chars]([dec]) [chars]. Error:[chars]","Port Loopback test process failed in MTS API.","No action is required."
"DIAG_PORT_LB","3","GET_DIAG_BD_FAIL","[chars]([dec]) Failed to get the BD for Diag VLAN:[dec]. Error:[chars].","Failed to get the BD corresponding to the Diag VLAN","No action is required."
"DIAG_PORT_LB","3","IFINDEX_LIB_FAILURE","[chars]([dec]) [chars] [chars]:[hex] [chars] [chars]","Port Loopback test process failed in if_index library API","No action is required."
"DIAG_PORT_LB","3","INVALID_TEST_REQUEST","[chars]([dec]) [chars]:[dec]","Port Loopback test process failed to get test request info.","No action is required."
"DIAG_PORT_LB","3","INVALID_TEST_RUN","[chars]([dec]) [chars]:[dec]","Port Loopback test process failed to get the current test run information","No action is required."
"DIAG_PORT_LB","3","PDB_LIB_API_ERROR","Failed to [chars]. Error:[dec].","The port loopback test was not able to get chassis info","No action is required."
"DIAG_PORT_LB","3","PIXM_LIB_ERROR","[chars]([dec]) Failed to convert [chars]:[hex] to [chars]. Error:[chars]","Port Loopback test process failed to convert port ifindex <-","No action is required."
"DIAG_PORT_LB","3","PORT_CLIENT_LIB_ERROR","[chars]([dec]) [chars]. Error:[chars]","Port Loopback test process failed in Port Client API.","No action is required."
"DIAG_PORT_LB","3","RESULT_ADD_FAILURE","[chars]([dec]) [chars]:[dec]","Port Loopback test process failed to add the port test result","No action is required."
"DIAG_PORT_LB","3","RESULT_SEND_FAILURE","[chars]([dec]) [chars]","Port Loopback test process failed to send the test results","No action is required."
"DIAG_PORT_LB","3","RW_ENGINE_LOOPBACK_TEST_SPINE_PATH_FAIL","Module:[dec] Test:RewriteEngine Loopback Spine path:[dec] failed [dec] consecutive times. Error:[chars]","Rewrite Engine Loopback test failed on the spine path consecutively","No action is required."
"DIAG_PORT_LB","3","SOCKET_ERROR","[chars]([dec]) [chars] Error:[chars]","Port Loopback test process failed in socket operations","No action is required."
"DIAG_PORT_LB","3","STATS_LIB_ERROR","[chars]([dec]) [chars]:[dec]","Port Loopback test process failed in stats infra lib API.","No action is required."
"DIAG_PORT_LB","3","TEST_RES_SEND_FAIL","Failed to send [chars] test results back to Diagnostics Infrastucture. Error:[chars].","The port loopback test was not able to send the test results","No action is required."
"DIAG_PORT_LB","3","TIMER_LIB_ERROR","[chars]([dec]) [chars]","Port Loopback test process timer handling failure.","No action is required."
"DIAG_PORT_LB","3","VLAN_ERROR","[chars]([dec]) [chars] Error:[chars]","Port Loopback test process failed to get Diagnostic VLAN info","No action is required."
"DIAG_PORT_LB","3","VQI_GET_FAIL","Failed to get the Diag VQi from XBM. Error:[chars]","Rewrite Engine Loopback test failed to get the Diag VQi from XBAR Mgr","No action is required."
"DIAG_PORT_LB","3","XBM_CFG_REQ_FAIL","Failed to conigure the XBAR mask while running the RewriteEngineLoopback test. Error:[chars]. Module:[dec] could have gone offline","Rewrite Engine Loopback test failed to set the XBAR mask while running the test. The target module could have gone offline","No action is required."
"DIAG_PORT_LB","4","MTS_LIB_ERROR","[chars]([dec]) [chars]. Warning:[chars]","Port Loopback test process failed in MTS API.","No action is required."
"DIAG_PORT_LB","4","PORT_CFG_REQ_SEND","[chars]([dec]) Failed to send request to configure port ifindex:[dec] for port loopback test","Failed to configure/restore the port to do/cleanup port loopback testing","No action is required."
"DIAG_PORT_LB","5","DIAG_PORT_LB_DISABLED","DIAG_PORT_LB Disabled","DIAG_PORT_LB Service Disabled","No action is required."
"DIAG_PORT_LB","5","DIAG_PORT_LB_ENABLED","DIAG_PORT_LB Enabled","DIAG_PORT_LB Service nabled","No action is required."
"DMM-SLOT#","2","DMM_LOG","[chars]","Temp main log","No action is required."
"DMM-SLOT#","5","LOG_ERR_DMM_NEW_NPORT_SRVR_ZONE","Job Id:%Ld VSAN :[dec] New N-Port FCID :[hex] Server FCID:[hex] are in the same zone. ALERT!!","A New N-Port has come up which is zoned in the same zone as the Server","No action is required."
"DMM-SLOT#","5","LOG_ERR_DMM_NEW_NPORT_STG_ZONE","Job Id:%Ld VSAN :[dec] New N-Port FCID :[hex] Storage FCID:[hex] are in the same zone. ALERT!!","A New N-Port has come up which is zoned in the same zone as the Storage","No action is required."
"DMM-SLOT#","5","LOG_ERR_DMM_SRVR_RSCN","Job Id:%Ld Server N-Port pWWN:0x%Lx [chars]","An RSCN event was received for the Server associated with a Job","No action is required."
"DMM-SLOT#","5","LOG_ERR_DMM_STG_RSCN","Job Id:%Ld N-Port pWWN:0x%Lx Storage:[chars] [chars]","An RSCN event was received for the Storage associated with a Job","No action is required."
"DMM-SLOT#","5","LOG_EV_DMM_JOB_COMPLETE","Job Id:%Ld NumSession:[dec]","Event indicating the completion of a Data Migration Job","No action is required."
"DMM-SLOT#","5","LOG_EV_DMM_JOB_ERROR_LOST_SSM_PEER_CONNECTION","Job Id:%Ld NumSession:[dec]","Event indicating the Suspension of Data Migration Job due to loss in ip connectivity to peer ssm","No action is required."
"DMM-SLOT#","5","LOG_EV_DMM_JOB_ERROR","Job Id:%Ld NumSession:[dec]","Event indicating the Suspension of Data Migration Job","No action is required."
"DMM-SLOT#","5","LOG_EV_DMM_JOB_FINISH","Job Id:%Ld NumSession:[dec]","Event indicating Finish-request for a Method-2 Data Migration Job","No action is required."
"DMM-SLOT#","5","LOG_EV_DMM_JOB_START","Job Id:%Ld NumSession:[dec]","Event indicating the start of a Data Migration Job","No action is required."
"DMM-SLOT#","5","LOG_EV_DMM_JOB_STOP","Job Id:%Ld NumSession:[dec]","Event indicating that the Data Migration Job was stopped by Administrator","No action is required."
"DMM-SLOT#","5","LOG_EV_DMM_JOB_TCP_CONNECTION_DOWN","Job Id:%Ld lost connection to peer [chars]. Job may be RESET","Event indicating IP Connectivity loss to peer SSM. Affected Job maybe be RESET","No action is required."
"DMM-SLOT#","5","LOG_EV_DMM_JOB_VERIFY_COMPLETE","Job Id:%Ld NumSession:[dec]","Event indicating the completion of a Data Migration Job Verification","No action is required."
"DMM-SLOT#","5","LOG_EV_DMM_JOB_VERIFY_ERROR","Job Id:%Ld NumSession:[dec]","Event indicating the Suspension of Data Migration Job Verification due to an error","No action is required."
"DMM-SLOT#","5","LOG_EV_DMM_JOB_VERIFY_START","Job Id:%Ld NumSession:[dec]","Event indicating the start of a Data Migration Job Verification","No action is required."
"DMM-SLOT#","5","LOG_EV_DMM_JOB_VERIFY_STOP","Job Id:%Ld NumSession:[dec]","Event indicating the Suspension of Data Migration Job Verification by the user","No action is required."
"DOT1X","2","DOT1X_INIT","Dot1x unable to start","The system failed to create the Dot1x process","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"DOT1X","3","DOT1X_ENABLE_STATIC_MAC_FOUND","Static mac found on an interface [chars], dot1x enable failed in ethpm pre-cfg","Dot1x is not supported on an interface which is configured with static mac entries","Remove the static mac entry on the interface"
"DOT1X","3","ERR_SPANDST","It is configured as a SPAN Dest port.","Dot1x and SPAN Dest ports are mutually exclusive features.","Disable SPAN destination port configuration first before reconfiguring Dot1x on the port."
"DOT1X","3","INVALID_INPUT","Invalid on interface [chars].","The Dot1x interface parameter is out of the specified range or is invalid.","Refer to the CLI help documentation to determine the valid 802.1x parameters."
"DOT1X","3","MEM_UNAVAIL","perform the 802.1X action.","Insufficient system memory is available to perform the Dot1x Authentication.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"DOT1X","3","NOT_DOT1X_CAPABLE","[chars].","Dot1x Authentication can only be enabled on physical Ethernet interfaces.","Enable Dot1x Authentication on physical Ethernet interfaces only."
"DOT1X","3","SECURE_MAC_INSERT_FAILED","address [chars] could not be secured on interface [chars]","The interface specified in the error message could not secured supplicant mac. The port has been Error disabled.","Mac address could not be added into mac address table. Enter the <Cmd"
"DOT1X","3","SECURITY_VIOLATION","New MAC address [chars] is seen on interface [chars] in [chars] mode","The port on the interface specified in the error message is configured in single host mode. Any new host that is detected on the interface is treated as a security violation. The port has been Error disabled.","Ensure that the port is configured to use only one host. Enter the <Cmd"
"DOT1X","3","SM_INIT","Internal error while initializing state machine [chars], state [chars]: [chars]","An attempt was made to initialize an invalid state machine.","Initialize dot1x state machine"
"DOT1X","4","BADEVENT","Event [chars] is invalid for the current state [chars]: [chars] [chars]","An attempt was made to post an event to a state machine that is invalid for the current state.","Initialize dot1x state machine"
"DOT1X","4","MAB_DISABLED_ON_PCM","Interface [chars] is a member of portchannel, MAB is not supported on this port","MAB is not supported on portchannel member port","To enable MAB make sure that port is not member of portchannel"
"DOT1X","4","MAB_DISABLED","Interface [chars] is in Trunk mode, MAB is not supported on this port","MAB is not supported on Trunk port","To enable MAB make sure that port is not in trunk mode"
"DOT1X","4","MULTIHOST_ON_PCM","Interface [chars] is a member of portchannel, dot1x host mode will be multi-host and changing it to single-host mode wontbesupported'","Current Port is a member of portchannel, so dot1x host mode has to be in multi-host mode.","To change host mode, ensure that port is not a member of portchannel"
"DOT1X","4","PSEC_ON_PCM","Interface [chars] is a member port or portchannel interface with port security configration","Dot1x is not supported on member ports or port channel with port security configuration","Remove port security configuration on the member port or port channel interface"
"DOT1X","4","STOPPED","Event [chars] ignored because the state machine is stopped: [chars] [chars]","An attempted was made to post an event to a state machine that has already been stopped.","An internal error has occurred with the state machine. The traceback should indicate the guilty party."
"DOT1X","4","TO_MULTIHOST","Interface [chars] is in trunk mode, dot1x host mode will be multi-host and changing it to single-host mode wontbesupported'","Current Port is in trunk mode, so dot1x host mode has to be in multi-host mode.","To change host mode, ensure that port is not in trunk mode"
"DOT1X","5","DOT1X_DISABLED","dot1x Disabled","Dot1x Service Disabled","No action is required."
"DOT1X","5","DOT1X_ENABLED","dot1x Enabled","Dot1x Service Enabled","No action is required."
"DOT1X","5","DOT1X_NOTIF","[chars]","Dot1x Notification","No action is required."
"DOT1X","5","INVALID_MAC","broadcast or multicast mac address) [chars] is trying to authenticate.","Authentication using 802.1x is not allowed for zero, broadcast, and multicast source MAC addresses.","Connect a Dot1x supported Host to the Dot1x enabled port."
"DOT1X","5","PAC_STATUS","PAC provisioning for the server [chars] through the vrf [chars] [chars]","PAC provisioning status","No action is required."
"DOT1X","5","SESSION_CREATION","Dot1x authentication session initiated in interface [chars] using authentication method [chars]","Dot1x authentication session has been created after successful authentication of supplicant","No action is required."
"DOT1X","5","SESSION_TERMINATION","Dot1x authentication session in interface [chars] using authentication method [chars] is terminated because of [chars] and port moved to [chars] state","Dot1x authentication session has been terminated","No action is required."
"DOT1X","5","STATUS","Dot1x interface [chars] status changed from [chars] to [chars]","Dot1x authenticator has changed its internal state","No action is required."
"DOT1X","6","NOT_DOT1X_CAPABLE_SAT_FABRIC","[chars].","Dot1x Authentication can only be enabled on physical Ethernet interfaces.","Enable Dot1x Authentication on physical Ethernet interfaces only."
"DPP_DEBUG","2","DPP_CRIT","[DPP[dec]] [chars]","A DPP generated a critical message","No action is required."
"DPVM","2","ALLOC_FAILED","Memory allocation failed for size:[dec] for [chars]","Memory allocation failed for size [dec] for [chars]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"DPVM","2","DPVM_DUPL_REJECT","[chars]","Rejected duplicate pwwn query","Dpvm overwrite-duplicate-pwwn"
"DPVM","3","DB_ERR","[chars]","An error occured during an DPVM database operation. [chars] indicates the reason for the error","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"DPVM","3","DDAS_MODE_INVALID","[chars]","DDAS mode Invalid. [chars]","Flip DDAS mode"
"DPVM","3","INIT_FAIL","[chars]","An error happened during DPVM Initialization. [chars] indicates the reason for failure","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"DPVM","3","MTS_ERR","[chars]","An error occured in processing of an MTS message. [chars] indicates the error that occured","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"DPVM","3","PSS_ERR","[chars]","An error occured during an DPVM PSS operation. [chars] indicates the PSS operation that caused the error","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"DPVM","4","ACTIVATION_FAIL","[chars]","Activation of DPVM device mappings failed due to [chars]","Correct the error and reactivate database again"
"DPVM","4","FEATURE_DISABLED","[chars]","DPVM is unavailable and disabled now","No action is required."
"DPVM","6","FEATURE_ENABLED","[chars]","DPVM is available and enabled now","No action is required."
"DPVM","6","INFO","[chars]","An event happened that affects DPVM. [chars] indicates the event","No action is required."
"DSTATS","2","PSS_INIT_FAIL","pss initialization failed due to error: [hex]","Dstats process pss initialization failure due to error [hex].","Collect more information using command showflash'.Seepsssystemerrorcodesforreason.'"
"DSTATS","3","PSS_CREATE_FAIL","pss create runtime database failed due to error: [hex]","Dstats process pss create runtime database failure due to error [hex].","Collect more information using command showflash'.Seepsssystemerrorcodesforreason.'"
"DSTATS","3","PSS_DELETE_FAIL","pss delete runtime entry key:[hex] failed due to error: [hex]","Dstats process pss delete runtime entry key [hex] failure due to error [hex].","Collect more information using command showflash'.Seepsssystemerrorcodesforreason.'"
"DSTATS","3","PSS_MAX_KEY_FAIL","pss set runtime max key failed due to error: [hex]","Dstats process pss set runtime max key failure due to error [hex].","Collect more information using command showflash'.Seepsssystemerrorcodesforreason.'"
"DSTATS","3","PSS_MAX_VALUE_FAIL","pss set runtime max value failed due to error: [hex]","Dstats process pss set runtime max value failure due to error [hex].","Collect more information using command showflash'.Seepsssystemerrorcodesforreason.'"
"DSTATS","3","PSS_OPEN_FAIL","pss open runtime database failed due to error: [hex]","Dstats process pss open runtime database failure due to error [hex].","Collect more information using command showflash'.Seepsssystemerrorcodesforreason.'"
"DSTATS","3","PSS_RELOAD_FAIL","pss reload runtime database failed due to error: [hex]","Dstats process pss reload runtime database failure due to error [hex].","Collect more information using command showflash'.Seepsssystemerrorcodesforreason.'"
"DSTATS","3","PSS_SNAPSHOT_DEBUG_FAIL","pss snapshot runtime debug to uri:[chars] failed due to error: [hex]","Dstats process pss snapshot of runtime debug to uri [string] failed due to error [hex].","Collect more information using command showflash'.Seepsssystemerrorcodesforreason.'"
"DSTATS","3","PSS_SNAPSHOT_FAIL","pss snapshot runtime to uri:[chars] failed due to error: [hex]","Dstats process pss snapshot of runtime to uri [string] failed due to error [hex].","Collect more information using command showflash'.Seepsssystemerrorcodesforreason.'"
"DSTATS","3","PSS_STORE_FAIL","pss store runtime entry key:[hex] val:[hex] failed due to error: [hex]","Dstats process pss store runtime entry key [hex] value [hex] failure due to error [hex].","Collect more information using command showflash'.Seepsssystemerrorcodesforreason.'"
"DT_HELPER","2","MALLOC_FAILURE","Memory allocation failed","GOLD Test Helper process could not allocate memory","No action is required."
"ELTMC","2","MAX_PORT_PER_VLAN","Hit max ports per vlan [dec] count [dec]","ELTM hit a internal error. Collect show tech-support eltm for futher analysis.","No action is required."
"ELTMC-SLOT#","2","ELTMC_GENERIC_DEBUG","[chars]","Logging some generic debugging info","No action is required."
"ELTMC-SLOT#","2","ELTMC_INTERFACE_INTERNAL_ERROR","Internal error: [chars]:[chars], collect output of show tech-support eltm","ELTM hit a internal error. Collect show tech-support eltm for futher analysis.","No action is required."
"ELTMC-SLOT#","2","ELTMC_INTERNAL_ERROR","Internal error: [chars], collect output of show tech-support eltm","ELTM hit a internal error. Collect show tech-support eltm for futher analysis.","No action is required."
"ELTMC-SLOT#","2","ELTMC_INTF_NOT_FOUND","Interface [chars] not found in ELTM database [chars]","ELTM database doesnthavetheinterface.'","No action is required."
"ELTMC-SLOT#","2","ELTMC_INTF_NOT_SUPP","Interface [chars] not supported by ELTM [chars]","ELTM doesntsupporttheinterfaceforthespecifiedoperation'","No action is required."
"ELTMC-SLOT#","2","ELTMC_INTF_TO_LTL","Failed to get LTL for interface [chars] return status [chars]","ELTM Failed to get LTL for interface. Packets received on this interface might not be handled correctly by the forwarding engine","No action is required."
"ELTMC-SLOT#","2","ELTMC_INTF_TO_SLOT","Failed to get slot for interface [chars] return status [chars]","ELTM Failed to get Slot for interface. Port-channels and L2 Learning might be effected","No action is required."
"ELTMC-SLOT#","2","ELTMC_L2_LIF_ALLOC_FAIL_INTF","Failed to allocate L2 LIF entries in forwarding engine for interfac [chars]","ELTM Failed to allocate L2 LIF entries in forwarding engine. This will effect Layer 2 and Layer 3 forwarding for the interface","No action is required."
"ELTMC-SLOT#","2","ELTMC_L2_LIF_ALLOC_FAIL_VDC","Failed to allocate L2 LIF entries in forwarding engine","ELTM Failed to allocate L2 LIF entries in forwarding engine. This will effect Layer 2 and Layer 3 forwarding in this VDC","No action is required."
"ELTMC-SLOT#","2","ELTMC_L2_LIF_REALLOC_FAIL_INTF","Failed to realloc L2 LIF entries in forwarding engine for interface [chars]","ELTM Failed to allocate L2 LIF entries in forwarding engine. This will effect Layer 2 and Layer 3 forwarding for the interface. ISSU failed for certain interfaces","No action is required."
"ELTMC-SLOT#","2","ELTMC_L3_INGRESS_LIF_ALLOC_FAIL_INTF","Failed to allocate L3 Ingress LIF entries in forwarding engine for interfac [chars]","ELTM Failed to allocate L3 Ingress LIF entries in forwarding engine. This will effect Layer 3 forwarding for the interface","No action is required."
"ELTMC-SLOT#","2","ELTMC_LDB_REALLOC_FAIL","Failed to realloc LDB in forwarding engine for interface [chars] for non-XL linecard","ELTM Failed to allocate L2 LIF entries in forwarding engine. ISSU failed for this VDC. Shutdown the interfaces","No action is required."
"ELTMC-SLOT#","2","ELTMC_LTL_ISSUE_EXT_COMP","Critical LTL clean-up issue (either ETHPM/PIXM) [chars]","LTL didnt get cleaned-up either bcos of ETHPM not sending DELETE or PIXM issuing a duplicate LTL","No action is required."
"ELTMC-SLOT#","2","ELTMC_NONXL_LDB_REALLOC_FAIL","Failed to realloc LDB in forwarding engine for certain interfaces for non-XL linecard","ELTM Failed to allocate L2 LIF entries in forwarding engine. ISSU failed for this VDC. Shutdown the interfaces","No action is required."
"ELTMC-SLOT#","2","ELTMC_PVLAN_XLT_ADD_FAIL","Failed to apply translation table add [chars]","ELTM Failed to apply vlan tranlation table on an interface add","No action is required."
"ELTMC-SLOT#","2","ELTMC_PVLAN_XLT_DEL_FAIL","Failed to apply translation table del [chars]","ELTM Failed to apply vlan tranlation table on an interface del","No action is required."
"ELTMC-SLOT#","2","ELTMC_RSVD_VLAN","Failed to get the reserved vlans. Failed with error [chars]","ELTM Failed to get the reserved vlans.ThiswilleffectmulticastforwardingonSVIinterfaces'","No action is required."
"ELTMC-SLOT#","2","ELTMC_VDC_LIF_REALLOC_FAIL","Failed to realloc LDB in forwarding engine for vdc [dec]. Reload VDC after config reduction","ELTM Failed to allocate L2 LIF entries in forwarding engine. ISSU failed for this VDC. Remove the interfaces and then reload VDC","No action is required."
"ELTMC-SLOT#","2","ELTMC_VLAN_INTERNAL_ERROR","Internal error: VLAN [dec]:[chars], collect output of show tech-support eltm","ELTM hit a internal error. Collect show tech-support eltm for futher analysis.","No action is required."
"ELTM","2","INTERFACE_INTERNAL_ERROR","Internal error: [chars]:[chars], collect output of show tech-support eltm","ELTM hit a internal error. Collect show tech-support eltm for futher analysis.","No action is required."
"ELTM","2","INTERNAL_ERROR","Internal error: [chars], collect output of show tech-support eltm","ELTM hit a internal error. Collect show tech-support eltm for futher analysis.","No action is required."
"ELTM","2","INTF_NOT_FOUND","Interface [chars] not found in ELTM database [chars]","ELTM database doesnthavetheinterface.'","No action is required."
"ELTM","2","INTF_NOT_SUPP","Interface [chars] not supported by ELTM [chars]","ELTM doesntsupporttheinterfaceforthespecifiedoperation'","No action is required."
"ELTM","2","INTF_TO_LTL","Failed to get LTL for interface [chars] return status [chars]","ELTM Failed to get LTL for interface. Packets received on this interface might not be handled correctly by the forwarding engine","No action is required."
"ELTM","3","OTV_FEATURE_FAIL","Feature OTV failed : [chars]","Error in ELTM while handling feature OTV request from OIM","No action is required."
"ELTM","5","EXT_COMP_ERR","[chars] component error [chars]","Recently applied Multicast config on the interface was unsuccessful, so reverting to the old state (before config)","No action is required."
"ELTM","6","ELTM_MTS_SEND_FAILED","Failed to send MTS message errno [hex] opcode [dec]","No action is required.","Eltm"
"EOU","2","PBACL_APPLICATION_FAILURE","[chars] of host [chars] to/from pbacl group [chars] failed. Error : [chars]","Failure of host addition/deletion to/from pbacl group","Please verify the addition/deletion of the host using the cli 'show object-group'. If it was a delete request that failed, manual deletion of the host from the group is recommended"
"EOU","5","L2NAC_DISABLED","EOU Disabled","Service EOU Disabled","No action is required."
"EOU","5","L2NAC_ENABLED","EOU Enabled","Service EOU enabled","No action is required."
"EOU","6","AAA_DOWN","Default Policy ip: [chars]:retained","Policy retained","No action is required."
"EOU","6","AUTHTYPE","Authtype: ip: [chars] Authtype:[chars]","Authentication type","No action is required."
"EOU","6","BAD_PKT","Bad Packet: ip: [chars] Why: [chars]","Bad Packet because of reason specified","No action is required."
"EOU","6","CTA","CTA: ip: [chars] status(detected/not detected): [chars]","CTA detected or not","No action is required."
"EOU","6","IDENTITY_MATCH","Identity Match: ip: [chars] Policy: [chars]","Identity Matched or not","No action is required."
"EOU","6","PBACL_APPLICATION_STATUS","[chars] of host [chars] to/from pbacl group [chars] succeeded","Status of host addition/deletion to pbacl group","No action is required."
"EOU","6","POLICY","Policy on ip: [chars]: [chars]: [chars]","Policy applied","No action is required."
"EOU","6","POSTURE","Posture:ip: [chars] Status: [chars], Interface: [chars]","Posture of host","No action is required."
"EOU","6","SESSION","Session ip: [chars] Action:[chars] , Interface: [chars]","Session detected","No action is required."
"EOU","6","SOCKET","Service eou on port: [dec]","Eou using above port","No action is required."
"EOU","6","SQ_EAP_MSG","Status Query: ip: [chars] status: [chars]","Status query state","No action is required."
"EOU","6","UNKN_EVENT_ERR","Unknow Event Err: ip: [chars] Message: [chars]","Error due to unknown event","No action is required."
"EOU","6","VERSION_MISMATCH","Eou version mismatch ip: [chars] and version [dec]","Eou version mismatch","No action is required."
"EOU","7","EOU_DISABLED_INTF","eou disabled on interface [chars]","Eou service disabled on interface","No action is required."
"EOU","7","EOU_ENABLED_INTF","eou enabled on interface [chars]","Eou service enabled on interface","No action is required."
"EPLD_AUTO","2","AUTO_UPGRADE_CHECK","Automatic EPLD upgrade check for module [dec]: [chars]","Automatic upgrade pre upgrade notice.","No action is required."
"EPLD_AUTO","2","AUTO_UPGRADE_ENDED","Automatic EPLD Upgrade completed for module [dec]","Automatic upgrade of module completed.","No action is required."
"EPLD_AUTO","2","AUTO_UPGRADE_STARTED","Automatic EPLD Upgrade started for module [dec]","Automatic upgrade of module started.","No action is required."
"EPLD_AUTO","2","AUTO_UPGRADE_STATUS","[chars]","Automatic upgrade status notice.","No action is required."
"EPLD_UPGRADE","2","ACTIVE_SINGLE_SUP_UPGRADE","install all epld does not upgrade Active Supervisor module [dec].","Install all epld does not upgrade Active Supervisor in a switch with a single supervisor.","No action is required."
"EPLD_UPGRADE","2","ACTIVE_SUP_UPGRADE","install all epld does not upgrade Active Supervisor module [dec]. Please do a switchover and upgrade the EPLDs on module [dec].","Install all epld did not upgrade Active Supervisor.","No action is required."
"EPP","5","EPP_FAILURE","Interface [chars] EPP Failure","Trunk protocol failed","showeppinternalevent-historyerr'willindicatetheerrorsencountered'"
"EPP","5","EPP_LOOPBACK","Interface [chars] is looped back to the same switch","The interface is looped back to another interface on the same switch","Check the connectivity of this interface and ensure that it is connected to another switch"
"EPP","5","EPP_TRUNK_PROTOCOL_STATUS","epp trunk protocol is [chars] on switch","Epp trunk protocol enabled/disabled on the switch","No action is required."
"ETH-PORT-SEC","3","ETH_PORT_SEC_CONFIG_MAC_FAILED","Failed to configure MACs","Failed to configure MACs","No action is required."
"ETH-PORT-SEC","3","ETH_PORT_SEC_INVALID_VLAN","Invalid VLAN configuration","Invalid VLAN configuration","No action is required."
"ETH-PORT-SEC","3","ETH_PORT_SEC_SECURITY_VIOLATION_ANOTHER_PORT","Host [chars] bound to Port [chars] in Vlan [dec] is trying to access Port [chars] in Vlan [dec]","Moved the port to violation state due to a mac address seen on one port being seen on another","No action is required."
"ETH-PORT-SEC","3","ETH_PORT_SEC_SECURITY_VIOLATION_MAX_MAC_VLAN","Port [chars] moved to [chars] state as host [chars] is trying to access the port in vlan [dec]","Moved the port to violation state due to exceeding address count","No action is required."
"ETH-PORT-SEC","3","ETH_PORT_SEC_UNABLE_TO_DISABLE","Unable to disable eth_port_sec [chars].","Unable to disable eth_port_sec Service","No action is required."
"ETH-PORT-SEC","3","ETH_PORT_SEC_UNABLE_TO_ENABLE","Unable to enable eth_port_sec [chars].","Unable to enable eth_port_sec Service","No action is required."
"ETH-PORT-SEC","3","ETH_PORT_SEC_VIOL_UPDATE_FAILED","Failed to update violation mode","Failed to update violation mode","No action is required."
"ETH-PORT-SEC","5","ETH_PORT_SEC_AGE_TIME_EXPIRY","Age Time expired for host [chars] in VLAN [dec] in port [chars]","Age time expired for host","No action is required."
"ETH-PORT-SEC","5","ETH_PORT_SEC_DISABLED","eth_port_sec Disabled on if_index:[hex]","Eth_port_sec Service Disabled","No action is required."
"ETH-PORT-SEC","5","ETH_PORT_SEC_DYNAMIC_MAC_ADDRESS_CLEARED","Dynamic MAC addresses for port [chars] cleared","Dynamic MAC address for port cleared","No action is required."
"ETH-PORT-SEC","5","ETH_PORT_SEC_ENABLED","eth_port_sec Enabled on if_index:[hex]","Eth_port_sec Service Enabled","No action is required."
"ETH-PORT-SEC","5","ETH_PORT_SEC_HOST_ADDITION","A new Host [chars] learnt on Port [chars] in Vlan [dec]","A new host is learnt on a port","No action is required."
"ETH-PORT-SEC","5","ETH_PORT_SEC_HOST_DELETION","Host [chars] bound to secure port [chars] in Vlan [dec] has been removed","A host has been removed","No action is required."
"ETHPORT","2","IF_CRITICAL_FAILURE","(Debug syslog)Critical failure: [chars], [chars]","There was a critical failure in the component.","Please follow instructions on the syslog."
"ETHPORT","2","IF_DOWN_ERROR_DISABLED","Interface [chars] is down (Error disabled. Reason:[chars])","The interface encountered an error while configuring it","Collect more information about failed interface using command showportinternalallinterface[char]'.Inmostcases,youcanrecoverusinga'shutdown'followeda'noshutd own'ontheinterfaceorremovingandre-insertingthefibreopticcable.'"
"ETHPORT","2","IF_SEQ_ERROR","Error ([chars]) communicating with [chars] for opcode [chars] ([chars])","Some component returned system error as a response to one of the port event sequence.","None"
"ETHPORT","2","SEQ_TIMEOUT","Component [chars] timed out on response to opcode [chars] ([chars])","Some component did not respond to a request in stipulated time.","None"
"ETHPORT","2","SYSLOG_ETHPM_CRITICAL","Critical failure: [chars]","There was a critical failure in the component.","Please collect system tech-support"
"ETHPORT","3","IF_DOWN_CHANNEL_ERR_DISABLED","Interface [chars] is down (Channel error disabled)","This interface belongs to a PortChannel and the PortChannel is error disabled","Perform shut'and'noshutdown'onthePortChannelinterfacethatitbelongsto'"
"ETHPORT","3","IF_ERROR_VLANS_REMOVED","VLANs [chars] on Interface [chars] are removed from suspended state.","The VLANs on an interface are being removed from the suspended state","No action is required."
"ETHPORT","3","IF_ERROR_VLANS_SUSPENDED","VLANs [chars] on Interface [chars] are being suspended. (Reason: [chars])","The VLANs on an interface are being suspended due to some protocol action","No action is required."
"ETHPORT","3","IF_SFP_ALARM","Interface [chars], [chars]","There was an alarm on the transceiver module","Please do show interface transceiver details to obtain more information"
"ETHPORT","3","IF_SFP_ERROR","Interface [chars], [chars]","There was an error on the transceiver module","Please do show interface transceiver details to obtain more information"
"ETHPORT","3","IF_UNSUPPORTED_TRANSCEIVER","Transceiver on interface [chars] is not supported","The transceiver for the interface specified in the error message is not a Cisco supported module","Replace the module with a compatible transceiver. If the transceiver was purchased from Cisco, please contact Cisco TAC to get the transceiver replaced"
"ETHPORT","3","IF_XCVR_ALARM","Interface [chars], [chars]","There was an alarm on the transceiver module","Please do show interface transceiver details to obtain more information"
"ETHPORT","3","IF_XCVR_ERROR","Interface [chars], [chars]","There was an error on the transceiver module","Please do show interface transceiver details to obtain more information"
"ETHPORT","4","IF_NON_QUALIFIED_TRANSCEIVER","Non-qualified transceiver on interface [chars] was detected","The transceiver for the interface specified has not been qualified on this platform for this software release","Replace the module with a supported transceiver. Contact Cisco TAC to get platform transceiver qualification details"
"ETHPORT","4","IF_SFP_WARNING","Interface [chars], [chars]","There was an warning on the transceiver module","Please do show interface transceiver details to obtain more information"
"ETHPORT","4","IF_XCVR_WARNING","Interface [chars], [chars]","There was an warning on the transceiver module","Please do show interface transceiver details to obtain more information"
"ETHPORT","5","IF_ADMIN_UP","Interface [chars] is admin up [chars]","Interface is admin up","No action is required."
"ETHPORT","5","IF_BANDWIDTH_CHANGE","Interface [chars],bandwidth changed to [chars] Kbit","Bandwidth of the interface (port channel) has changed and this change is updated","No action is required."
"ETHPORT","5","IF_DOWN_ADMIN_DOWN","Interface [chars] is down (Administratively down)","Interface has been configured to be administratively down","Perform noshutdown''"
"ETHPORT","5","IF_DOWN_CFG_CHANGE","Interface [chars] is down(Config change)","FCIP interface temporarily down due to reconfiguration","No action is required."
"ETHPORT","5","IF_DOWN_CHANNEL_ADMIN_DOWN","Interface [chars] is down (Channel admin down)","This interface belongs to a PortChannel and the PortChannel is configured to be administratively down","Perform noshutdown'onthePortChannelinterfacethatitbelongsto'"
"ETHPORT","5","IF_DOWN_CHANNEL_MEMBERSHIP_UPDATE_IN_PROGRESS","Interface [chars] is down (Channel membership update in progress)","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","Retry the configuration again"
"ETHPORT","5","IF_DOWN_DOMAIN_ADDR_ASSIGN_FAILURE_ISOLATION","Interface [chars] is down (Isolation due to domain id assignment failure)","Isolated due to a failure while assigning a domain","No action is required."
"ETHPORT","5","IF_DOWN_DOMAIN_INVALID_RCF_RECEIVED","Interface [chars] is down (Isolation due to invalid fabric reconfiguration)","Invalid RCF received","No action is required."
"ETHPORT","5","IF_DOWN_DOMAIN_MANAGER_DISABLED","Interface [chars] is down (Isolation due to domain manager disabled)","Isolated due to domain manager being disabled","No action is required."
"ETHPORT","5","IF_DOWN_DOMAIN_MAX_RETRANSMISSION_FAILURE","Interface [chars] is down (Isolation due to domain manager other side not responding)","Remote end domain manager not responding","No action is required."
"ETHPORT","5","IF_DOWN_DOMAIN_OTHER_SIDE_EPORT_ISOLATED","Interface [chars] is down (Isolation due to domain other side eport isolated)","Isolating this interface due to the remote end being isolated","No action is required."
"ETHPORT","5","IF_DOWN_DOMAIN_OVERLAP_ISOLATION","Interface [chars] is down (Isolation due to domain overlap)","Isolated due to domain overlap","No action is required."
"ETHPORT","5","IF_DOWN_ELP_FAILURE_ISOLATION","Interface [chars] is down (Isolation due to ELP failure)","ELP failed on the interface","Check the output of showportinternalinfo'inthe'ELPfailurereason'field'"
"ETHPORT","5","IF_DOWN_EPP_FAILURE","Interface [chars] is down (Error Disabled - EPP Failure)","Trunk protocol failed","showportinternalevent-historymsgs'willindicatethetrunkprotocolexchangestodeterminewhyitfailed'"
"ETHPORT","5","IF_DOWN_ESC_FAILURE_ISOLATION","Interface [chars] is down (Isolation due to ESC failure)","ESC failed on the interface","Check the output of showportinternalevent-history'todeterminetheESCprotocolexchangestodeterminehowitfailed'"
"ETHPORT","5","IF_DOWN_ETH_IF_DOWN","Interface [chars] is down(Tunnel port src interface down)","Ethernet link to which the FCIP interface is bound is down","Ensure that the ethernet cable is connected, the interface is administratively enabled"
"ETHPORT","5","IF_DOWN_ETH_LINK_DOWN","Interface [chars] is down(Tunnel port src interface link down)","Ethernet link to which the FCIP interface is bound is down","Ensure that the ethernet cable is connected and the remote end is also active"
"ETHPORT","5","IF_DOWN_FCOT_NOT_PRESENT","Interface [chars] is down (FCOT not present)","The FCOT has been removed","Insert an FCOT"
"ETHPORT","5","IF_DOWN_FCOT_VENDOR_NOT_SUPPORTED","Interface [chars] is down (Error disabled - Fcot vendor not supported)","Fcot inserted is not a supported one","Please contact customer support for a list of authorized transceiver vendors"
"ETHPORT","5","IF_DOWN_HW_FAILURE","Interface [chars] is down (Hardware Failure)","The moduleshardwarehasfailed'","Collect more information about failed module using command showmoduleinternalallmodule''"
"ETHPORT","5","IF_DOWN_INACTIVE","Interface [chars] is down (Inactive)","The port VSAN has been suspended or deleted","Assign a new active port VSAN to the interface"
"ETHPORT","5","IF_DOWN_INCOMPATIBLE_ADMIN_MODE","Interface [chars] is down (Error disabled - Incompatible admin port mode)","The configured mode is not supported on this interface","Perform a showportinternalinfo'todeterminethelistofmodessupportedonthisinterface'"
"ETHPORT","5","IF_DOWN_INCOMPATIBLE_ADMIN_RXBBCREDIT","Interface [chars] is down (Error disabled - Incompatible admin port rxbbcredit)","The configured receive B2B credit size is not supported","Get the allowed receive B2B credit size from showportinternalinfo''"
"ETHPORT","5","IF_DOWN_INCOMPATIBLE_ADMIN_RXBUFSIZE","Interface [chars] is down (Error disabled - Incompatible admin port rxbufsize)","The configured receive buffer size is not supported","Get the allowed receive buffer size from showportinternalinfo''"
"ETHPORT","5","IF_DOWN_INCOMPATIBLE_ADMIN_SPEED","Interface [chars] is down (Error disabled - Incompatible admin port speed)","The configured speed is not supported on this interface","Perform a showportinternalinfo'todeterminetherangeofspeedsupportedonthisinterface'"
"ETHPORT","5","IF_DOWN_INITIALIZING","Interface [chars] is down (Initializing)","The interface is in the process of coming up","If the interface is stuck in this state for a while, check the output of showportinternalevent-history'todeterminewhatitiswaitingfor'"
"ETHPORT","5","IF_DOWN_INTERFACE_REMOVED","Interface [chars] is down (Interface removed)","Interface removed","No action is required."
"ETHPORT","5","IF_DOWN_LINK_FAILURE","Interface [chars] is down (Link failure)","The physical link has gone down","Ensure that the cable is connected and the remote end is not shut down"
"ETHPORT","5","IF_DOWN_LOOPBACK_DIAG_FAILURE","Interface [chars] is down (Diag failure)","Diag failed on the interface","Collect more information about failed interface using command attachmodule'toconnecttomodule'"
"ETHPORT","5","IF_DOWN_LOOPBACK_ISOLATION","Interface [chars] is down (Isolation due to port loopback to same switch)","The interface is looped back to another interface on the same switch","Check the connectivity of this interface and ensure that it is connected to another switch"
"ETHPORT","5","IF_DOWN_MODULE_REMOVED","Interface [chars] is down (module removed)","Interface is down because the module was removed","No action is required."
"ETHPORT","5","IF_DOWN_NONE","Interface [chars] is down ([chars])","Interface is down with a possible reason.","Collect more information about port using command showportinternalinfo/event-history'todeterminewhyitwentdown'"
"ETHPORT","5","IF_DOWN_NON_PARTICIPATING","Interface [chars] is down (Non participating)","The loop port has been put into non participating mode","No action is required."
"ETHPORT","5","IF_DOWN_OFFLINE","Interface [chars] is down (Offline)","The interface has been placed into the offline state","No action is required."
"ETHPORT","5","IF_DOWN_PARENT_ADMIN_DOWN","Interface [chars] is down (Parent interface down)","Parent interface is down","No action is required."
"ETHPORT","5","IF_DOWN_PARENT_DOWN","Interface [chars] is down (Parent interface is down)","The physical link on the parent interface has gone down","No action is required."
"ETHPORT","5","IF_DOWN_PEER_CLOSE","Interface [chars] is down(TCP conn. closed by peer)","The FCIP peer connected to this interface closed the TCP connection","This command will provide the peer IP address of this FCIP interface: show interface. Check to see why the peer closed the TCP connection"
"ETHPORT","5","IF_DOWN_PEER_RESET","Interface [chars] is down(TCP conn. reset by peer)","TCP connection to the FCIP peer got reset","The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Check to see why the peer reset the TCP connection"
"ETHPORT","5","IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN","Interface [chars] is down (No operational members)","This is a PortChannel interface and all its members are operationally down","Enable at least one of the PortChannelsmembers'"
"ETHPORT","5","IF_DOWN_PORT_VSAN_MISMATCH_ISOLATION","Interface [chars] is down (Isolation due to port vsan mismatch)","Isolated due to a mismatch in the configured port VSAN of the local and remote ends","Configure the port VSAN of the local and remote interfaces to be the same and perform a shutdown'anda'noshutdown''"
"ETHPORT","5","IF_DOWN_RCF_IN_PROGRESS","Interface [chars] is down (RCF in progress)","There is an RCF in progress","No action is required."
"ETHPORT","5","IF_DOWN_SOFTWARE_FAILURE","Interface [chars] is down (Port software failure)","The software servicing the data path on the port has failed","No action is required."
"ETHPORT","5","IF_DOWN_SRC_MOD_NOT_ONLINE","Interface [chars] is down(Tunnel source module not online)","Module that has the tunnel source port of this FCIP interface is not fully online","The module that has the tunnel src port is coming online. Please use show mod to find module status"
"ETHPORT","5","IF_DOWN_SRC_PORT_NOT_BOUND","Interface [chars] is down (Tunnel port src interface unbound)","Tunnel port source interface unbound","No action is required."
"ETHPORT","5","IF_DOWN_SRC_PORT_REMOVED","Interface [chars] is down(Tunnel src port removed)","Tunnel source port of this FCIP interface has been removed","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"
"ETHPORT","5","IF_DOWN_SUSPENDED_BY_MODE","Interface [chars] is down (Suspended due to incompatible mode)","This interface belongs to a PortChannel and operational mode of the interface is different from that of the PortChannel","Change the mode and the trunking mode of the PortChannel from auto'andchecktoensurethattheremoteendoftheinterfacealsobelongstothesamePortChannel'"
"ETHPORT","5","IF_DOWN_SUSPENDED_BY_SPEED","Interface [chars] is down (Suspended due to incompatible speed)","This interface belongs to a PortChannel and operational speedode of the interface is different from that of the PortChannel","Change the speed of the PortChannel from auto'andchecktoensurethattheremoteendoftheinterfacealsobelongstothesamePortChannel'"
"ETHPORT","5","IF_DOWN_SUSPENDED_BY_WWN","Interface [chars] is down (Suspended due to incompatible remote switch WWN)","This interface belongs to a PortChannel and remote switch WWN of the interface is different from that of the PortChannel","Ensure that this interface is connected to the same remote switch as all the other interfaces in the PortChannel"
"ETHPORT","5","IF_DOWN_SUSPENDED","Interface [chars] is down (Suspended)","This interface belongs to a PortChannel and has been suspended due to an error while bringing it up","Perform a shutdown'anda'noshutdown'.Ifthishappensagainobtainoutputof'showportinternalinfo/event-history' ontheinterface'"
"ETHPORT","5","IF_DOWN_TCP_KEEP_ALIVE_EXPIRED","Interface [chars] is down(TCP conn. closed - Keep alive expired)","TCP session to the FCIP peer got closed due to loss of TCP keep alive","This may be due to loss of IP connectivity. The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Please do a trace route to check the connectivity to the peer using command:traceroute ipaddr"
"ETHPORT","5","IF_DOWN_TCP_MAX_RETRANSMIT","Interface [chars] is down(TCP conn. closed - retransmit failure)","Interface is down due to maximum retransmission failure","This may be due to loss of IP connectivity. The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Please do a trace route to check the connectivity to the peer using command:traceroute ipaddr"
"ETHPORT","5","IF_DOWN_TCP_PERSIST_TIMER_EXPIRED","Interface [chars] is down(TCP conn. closed - Persist timer expired)","TCP session to the FCIP peer closed because TCP persist timer expired","This may be due to loss of IP connectivity. The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Please do a trace route to check the connectivity to the peer using command:traceroute ipaddr"
"ETHPORT","5","IF_DOWN_UPGRADE_IN_PROGRESS","Interface [chars] is down (Linecard upgrade in progress)","Upgrade of the linecard software is in progress","No action is required."
"ETHPORT","5","IF_DOWN_VRF_UNUSABLE","Interface [chars] is down (Vrf down)","The vrf for which this interface is a member is removed","No action is required."
"ETHPORT","5","IF_DOWN_VSAN_MISMATCH_ISOLATION","Interface [chars] is down (Isolation due to vsan mismatch)","This is a trunking interface and the VSANs configured do not match with the VSANs configured on the remote end","Check the VSANs configured on the local end with the remote end"
"ETHPORT","5","IF_DOWN_ZONE_MERGE_FAILURE_ISOLATION","Interface [chars] is down (Isolation due to zone merge failure)","Isolated due to a failure during zone merge","No action is required."
"ETHPORT","5","IF_DOWN_ZONE_REMOTE_NO_RESP_ISOLATION","Interface [chars] is down (Isolation due to remote zone server not responding)","Isolated due to remote zone server not responding","No action is required."
"ETHPORT","5","IF_DUPLEX","Interface [chars], operational duplex mode changed to [chars]","Operational duplex mode has changed when link came up","No action is required."
"ETHPORT","5","IF_ERRDIS_RECOVERY","Interface [chars] is being recovered from error disabled state (Last Reason:[chars])","Interface is being recovered from error disabled state","No action is required."
"ETHPORT","5","IF_HARDWARE","Interface [chars], hardware type changed to [chars]","There was a change in the hardware characteristic of an interface, such as a transceiver module plugged in or removed","No action is required."
"ETHPORT","5","IF_L2MP_MODE","Interface [chars], l2mp-mode changed to [chars]","The l2mp-mode on the port has changed","No action is required."
"ETHPORT","5","IF_RX_FLOW_CONTROL","Interface [chars], operational Receive Flow Control state changed to [chars]","Operational receive flow control has changed when link came up","No action is required."
"ETHPORT","5","IF_TRUNK_DOWN","Interface [chars], vlan [chars] down","Interface [chars] is trunking, VLANs [chars] are down","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"
"ETHPORT","5","IF_TRUNK_UP","Interface [chars], vlan [chars] up","Interface [chars] is trunking, VLANs [chars] are up","No action is required."
"ETHPORT","5","IF_TX_FLOW_CONTROL","Interface [chars], operational Transmit Flow Control state changed to [chars]","Operational transmit flow control has changed when link came up","No action is required."
"ETHPORT","5","IF_UP","Interface [chars] is up [chars]","Interface is up in mode specified, if applicable","No action is required."
"ETHPORT","5","SPEED","Interface [chars], operational speed changed to [chars]","Operational speed has changed when link came up","No action is required."
"ETHPORT","5","STORM_CONTROL_ABOVE_THRESHOLD","Traffic in port [chars] exceeds the configured threshold [chars]","Traffic on specified port is beyond the configured storm-control threshold, and the excess traffic is being dropped","Identify source of traffic storm"
"ETHPORT","5","STORM_CONTROL_BELOW_THRESHOLD","Traffic in port [chars] has fallen below the configured threshold [chars]","Traffic on specified port has returned to within configured storm-control threshold","No action is required."
"ETH_PORT_CHANNEL","1","LC_CFG_FAILURE","configuring module [dec] failed [[chars]]","Module configuration failed","Module will be automatically reset"
"ETH_PORT_CHANNEL","1","MALLOC_FAILED","cannot allocate memory (size [dec])","No enough memory","No action is required."
"ETH_PORT_CHANNEL","1","MAP_PARAM_FAILURE","mapping parameter failed for [chars] [[chars]]","Parameter mapping failed","Specified service is misbehaving; check its status"
"ETH_PORT_CHANNEL","1","MCAST_SEND_FAILURE","failed to send multicast [chars]: [chars]","Failed to send a multicast message to all modules, usually because some module went down","Run show port-channel consistency to check consistency"
"ETH_PORT_CHANNEL","2","RESET_MODULE","reset module [dec] for not responding or returning error","A module is reset for not responding or returning error","No action is required."
"ETH_PORT_CHANNEL","3","ADD_REM_MEMBERS_FAILURE","[chars]","Some service(s) failed to add or remove ports to port-channel","None"
"ETH_PORT_CHANNEL","3","ALL_DROP_TIMEOUT","Some component(s) (sap:[chars]) timed out on dropping notif:[chars] (for:[chars]); Please collect <show system internal mts buffers details","Some component did not respond to a request in stipulated time.","None"
"ETH_PORT_CHANNEL","3","COMPAT_CHECK_FAILURE","[chars] is not compatible","Compatibility check failed when adding ports to port-channel","Make sure the compatibility parameters are consistent while adding ports to port-channel, or use force option"
"ETH_PORT_CHANNEL","3","GENERAL_ERROR","[chars]","General error","No action is required."
"ETH_PORT_CHANNEL","3","MSG_SEND_FAILURE","failed to send [chars] to sap [dec]: [chars]","Failed to send a message","No action is required."
"ETH_PORT_CHANNEL","3","NUM_ACTIVE_PORTS_ERROR","Port-channel:[chars] active_nports [dec]; No member is active; Please collect <show tech-support port-channel/ethpm","Port-channel num active ports error","None"
"ETH_PORT_CHANNEL","3","PCM_HWCFG_FAIL_ERROR","Port-channel:[chars] mbr:[chars] SAP [dec] returned error [chars] for opc [chars]; if lacp port-channel please collect <show tech-support lacp all","Port-channel hwcfg fail error","None"
"ETH_PORT_CHANNEL","3","PCM_INTERNAL_ERROR","Port-channel:[chars] mbr:[chars]; if lacp port-channel please collect <show tech-support lacp all","Port-channel internal error","None"
"ETH_PORT_CHANNEL","3","PCM_PORT_DEL_IN_PC_UP_ERROR","Port-channel:[chars] mbr:[chars]; if lacp port-channel please collect <show tech-support lacp all","Port-channel port del in pc_up. Shut resp recvd before bundle member down","None"
"ETH_PORT_CHANNEL","3","PCM_PORT_DOWN_IN_PC_UP_ERROR","Port-channel:[chars] mbr:[chars]; if lacp port-channel please collect <show tech-support lacp all","Port-channel port down in pc_up. No bundle member down","None"
"ETH_PORT_CHANNEL","3","PORT_CHANNEL_NOT_FOUND","[chars] is not found","Cannot find port-channel in its database, which indicates an inconsistency with an external component","No action is required."
"ETH_PORT_CHANNEL","3","RESOURCE_ALLOC_FAILED_PORT_CHANNEL_DELETED","[chars] deleted","Port-channel deleted from running config","May need to re-configure the port-channel and its members"
"ETH_PORT_CHANNEL","3","RSP_TIMEOUT","Component [chars] timed out on response to opcode:[chars] (for:[chars])","Some component did not respond to a request in stipulated time.","None"
"ETH_PORT_CHANNEL","3","TIMEOUT","timed out after [dec] seconds [type [chars], state [chars]]","Some operation timed out","Run show port-channel consistency to check all module connectivity and consistency"
"ETH_PORT_CHANNEL","3","SHADOW_MBR_CHANGE_FAILURE","[chars]","Some service failed shadow member change to port-channel","None"
"ETH_PORT_CHANNEL","3","SHADOW_PC_CREATE_FAILURE","[chars]","Some service failed shadow port-channel create","None"
"ETH_PORT_CHANNEL","3","SHADOW_PC_DELETE_FAILURE","[chars]","Some service failed shadow port-channel delete","None"
"ETH_PORT_CHANNEL","4","PORT_CFG_DELETED","[chars] removed from [chars] (different module inserted)","Port is removed from a port-channel because a different module was inserted to the same slot","You lost some ports from port-channel, check if you want to add ports in the new module to the same port-channel."
"ETH_PORT_CHANNEL","4","PORT_INDIVIDUAL","port [chars] is operationally individual","The port is operating as an individual link even though it is locally or remotely configured to be part of a port channel","Check the configuration of the port locally and remotely to ensure that it can operate as part of a port channel"
"ETH_PORT_CHANNEL","4","PORT_NOT_FOUND","port [chars] is not part of port-channel","Cannot find the port in port-channel database, which indicates an inconsistency with an external component","No action is required."
"ETH_PORT_CHANNEL","4","RACE_WARN","[chars]","Warning of possible race condition","No action is required."
"ETH_PORT_CHANNEL","4","UNEXPECTED_RESPONSE","unexpected response [chars] from [chars]","Received an unexpected response and discarded","No action is required."
"ETH_PORT_CHANNEL","5","AUTO_CREATE_FAILURE","[chars] [chars]","Auto create process on the port failed","No action is required."
"ETH_PORT_CHANNEL","5","CREATED","[chars] created","A port-channel is created","No action is required."
"ETH_PORT_CHANNEL","5","DELETED","[chars] deleted","A port-channel is deleted","No action is required."
"ETH_PORT_CHANNEL","5","FOP_CHANGED","[chars]: first operational port changed from [chars] to [chars]","The first operational port in a port-channel is changed","No action is required."
"ETH_PORT_CHANNEL","5","IF_DOWN_SUSPENDED_BY_MODE","Interface [chars] is down (Suspended due to incompatible mode","Compatibility check failed when adding ports to port-channel","Make sure the compatibility parameters are consistent between the ports and the port-channel"
"ETH_PORT_CHANNEL","5","IF_DOWN_SUSPENDED_BY_SPEED","Interface [chars] is down (Suspended due to incompatible speed","Operational compatibility check failed on the port in a port-channel","Make sure the compatibility parameters are consistent between the ports and the port-channel"
"ETH_PORT_CHANNEL","5","MAX_CHANNEL_DISALLOWED","Module failed to come online because port channel interface <port-channel number","The port-channel number configured on the switch is larger than 128","Delete the set of port channel interface <port-channel interface"
"ETH_PORT_CHANNEL","5","PORT_ADDED","[chars] added to [chars]","Ports are added to a port-channel","No action is required."
"ETH_PORT_CHANNEL","5","PORT_DOWN","[chars]: [chars] is down","Port goes down in a port-channel","No action is required."
"ETH_PORT_CHANNEL","5","PORT_HOT_STANDBY_DOWN","[chars]: hot-standby port [chars] is down","Port-channel hot-standby member goes down","No action is required."
"ETH_PORT_CHANNEL","5","PORT_HOT_STANDBY","[chars]: [chars] goes to hot-standby","Port goes to hot-standby in a port-channel","No action is required."
"ETH_PORT_CHANNEL","5","PORT_INDIVIDUAL_DOWN","individual port [chars] is down","Port-channel member operating in individual mode goes down","No action is required."
"ETH_PORT_CHANNEL","5","PORT_REMOVED","[chars] removed from [chars]","Ports are removed from a port-channel","No action is required."
"ETH_PORT_CHANNEL","5","PORT_SUSPENDED","[chars]: [chars] is suspended","Port is suspended in a port-channel","No action is required."
"ETH_PORT_CHANNEL","5","PORT_UP","[chars]: [chars] is up","Port comes up in a port-channel","No action is required."
"ETH_PORT_CHANNEL","5","SUBGROUP_ID_CHANGE","Interface [chars] in port-channel[dec] subgroup-id changed from [dec] to [dec]","The portssubgroup-idgotchanged'","No action is required."
"ETH_PORT_CHANNEL","6","RESYNC","resyncing [chars] with all modules","Resync modules with sup after an error or switchover","No action is required."
"ETH_PORT_CHANNEL","7","GSYNC_DONE","global synchronization is done","Port-channel manager finished global synchronization","No action is required."
"ETH_PORT_CHANNEL","7","GSYNC_REQ","requesting global synchronization","Port-channel manager requested a global synchronization from active sup","No action is required."
"ETH_PORT_CHANNEL","7","START_ACTIVE","started in active mode","Port-channel manager started in active mode","No action is required."
"ETH_PORT_CHANNEL","7","START_DEFAULT","started with default configuration","Port-channel manager started with default configuration","No action is required."
"ETH_PORT_CHANNEL","7","START_STANDBY","started in standby mode","Port-channel manager started in standby mode","No action is required."
"ETH_PORT_CHANNEL","7","START_STATEFUL","started statefully","Port-channel manager started with running configuration","No action is required."
"ETH_PORT_CHANNEL","7","START_STATELESS","started statelessly","Port-channel manager started with startup configuration","No action is required."
"EUREKA_USD","3","MSG1","[chars]","Eureka log message","No action is required."
"EVMC","3","MTS_OPERATION_FAILED","[chars]([dec]): [chars]","Internal IPC operation failed in Event Manager Client","No action is required."
"EVMC","4","ACTION_CFG_MONITOR_COLLECT","[chars]([dec]): Action configuration disallowed for Monitor Collect Policy","Configuring Policy Action for Monitor Collect Policy isnot allowed and hence, has been rejected","No action is required."
"EVMC","5","AVL_CREATE_FAIL","[chars]([dec]): AVL Tree creation failure","Event Manager could not initialize local policy store","No action is required."
"EVMC","5","MALLOC_FAILURE","[chars]([dec]): Memory allocation failure","Event Manager Client process could not allocate memory","No action is required."
"EVMC","5","RT_PSS_OP_FAILURE","[chars]([dec]): Failed to [chars]. Error:[chars]","Event Manager Client could not access HA store","No action is required."
"EVMED","2","EVMED_PSS_DELETE_FAILURE","Delete from PSS failed","Delete from PSS failed","No action is required."
"EVMED","2","EVMED_PSS_WRITE_FAILURE","Write to PSS failed","Write to PSS failed","No action is required."
"EVMED","5","EVMED_DISABLED","Event Detectors Disabled","Event manager event detector service disabled","No action is required."
"EVMED","5","EVMED_ENABLED","Event Detectors Enabled","Event manager event detector service enabled","No action is required."
"EVMS","2","EVMS_PSS_DELETE_FAILURE","Delete from PSS failed","Delete from PSS failed","No action is required."
"EVMS","2","EVMS_PSS_WRITE_FAILURE","Write to PSS failed","Write to PSS failed","No action is required."
"EVMS","2","EVMS_SHOW_POLICY_ALLOC_FAILURE","Insufficient memory: policy information shown will be incomplete","Memory allocation failed. so complete requested information is not being shown","No action is required."
"EVMS","4","EVMS_APPLET_NO_ACTION_DEFAULT","WARNING: The default system policy actions are being skipped","The default system policy actions are being skipped","No action is required."
"EVMS","6","EVMS_LOGGING_NO_SPACE","logflash full, so deleting first event archive file","As the logflash is full, first of the present event archive files is deleted","No action is required."
"EXAMPLE_TEST","5","EXAMPLE_TEST_DISABLED","EXAMPLE_TEST Disabled","EXAMPLE_TEST Service Disabled","No action is required."
"EXAMPLE_TEST","5","EXAMPLE_TEST_ENABLED","EXAMPLE_TEST Enabled","EXAMPLE_TEST Service nabled","No action is required."
"EXCEPTIONLOG-SLOT#","2","LC_EXP_MSG","Linecard exception: [chars] is the affected Port bit map. [dec] Additional information - [chars]","LC Exception event.","No action is required."
"EX_SYSLOG","0","EMER_MSG","Emergency Message - [dec]","A Dummy emergency message to test syslogd from ex_syslog. [dec] is the message count","No action is required."
"EX_SYSLOG","1","ALERT_MSG","Alert Message - [chars] [dec]","A Dummy alert message to test syslogd from ex_syslog. [chars] is the a dummy text. [dec] is the message count","No action is required."
"EX_SYSLOG","2","CRIT_MSG","Critical Message - [dec]","A Dummy critical message to test syslogd from ex_syslog. [dec] is the message count","No action is required."
"EX_SYSLOG","3","ERR_MSG","Error Message - [dec]","A Dummy error message to test syslogd from ex_syslog. [dec] is the message count","No action is required."
"EX_SYSLOG","4","WARNING_MSG","Warning Message - [dec]","A Dummy warning message to test syslogd from ex_syslog. [dec] is the message count","No action is required."
"EX_SYSLOG","5","NOTICE_MSG","Notice Message - [dec]","A Dummy notice message to test syslogd from ex_syslog. [dec] is the message count","No action is required."
"EX_SYSLOG","6","INFO_MSG","Info Message - [dec]","A Dummy info message to test syslogd from ex_syslog. [dec] is the message count","No action is required."
"EX_SYSLOG","7","DEBUG_MSG","Debug Message - [dec]","A Dummy debug message to test syslogd from ex_syslog. [dec] is the message countNo action is required.F16_CMN_USD MessagesThis section contains the F16_CMN_USD messages.F16_CMN_USD-6Error Message    F16_CMN_USD-6-F16_CMN_DEBUG_MSG: [chars] Explanation    Debug log message","No action is required."
"F16_FWD_USD","6","F16_FWD_DEBUG_MSG","[chars]","Debug log message","No action is required."
"F16_MAC_USD","3","F16_MAC_ERR_MSG","[chars]","Error log message","No action is required."
"F16_MAC_USD","6","F16_MAC_DEBUG_MSG","[chars]","Debug log message","No action is required."
"F16_QUE_USD","6","F16_QUE_DEBUG_MSG","[chars]","Debug log message","No action is required."
"F16_XBAR_USD","6","F16_XBAR_DEBUG_MSG","[chars]","Debug log message","No action is required."
"FABRICPATH","2","FABRICPATH_LINK_BRINGUP_STALLED_STATIC","Link bringup stalled due to conflicts","Interface is disabled due to conflicts","No action is required."
"FABRICPATH","4","FABRICPATH_ES_REMOTE_CONFLICT","Remote ES Switch-id collides with local/remote switch-id in database","Conflict between Remote ES switch-id and non ES switch-id in database","No action is required."
"FABRICPATH","4","FABRICPATH_INVALID_FTAG","Invalid ftag [dec] received","Invalid ftag is received from remote","No action is required."
"FABRICPATH","4","FABRICPATH_INVALID_SWITCH_ID","Invalid switch-id [dec] received","Invalid switch-id is received from remote","No action is required."
"FABRICPATH","4","FABRICPATH_LOCAL_SWID_UNKNOWN","Local Switch-id is not known to Resource Allocation manager","Resource Allocation Manager was not able to recover the local switch-idError Message     No action is required. FABRICPATH-6Error Message      FABRICPATH-6-FABRICPATH_LINK_BRINGUP_RESOLVE_COLLISION: Resolving Collision for switch-id [dec] Explanation    Resolving Collision for switch-id","No action is required."
"FABRICPATH","6","FABRICPATH_LINK_BRINGUP_STALLED_CLEARED","LINK bringup cleared for [chars] after collision resolution","Link bringup temporarily suspended due to conflicts","No action is required."
"FABRICPATH","6","FABRICPATH_LINK_BRINGUP_STALLED","LINK bringup suspended for [chars] due to conflicts","Link bringup temporarily suspended due to conflicts","No action is required."
"FABRICPATH","6","FABRICPATH_NEW_ES_SWITCH_ID","New Emulated switch-id [chars] received","New Emulated switch-id received","No action is required."
"FABRICPATH","6","FABRICPATH_NEW_SWITCH_ID","New switch-id [chars] received","New switch-id received","No action is required."
"FABRICPATH","6","FABRICPATH_SWID_CHANGED","Switch-id [dec] is assigned with [chars] state","Local switch-id is changed","No action is required."
"FABRICPATH","6","FABRICPATH_SWID_CONFLICTS","Switch-id [dec] is in conflict with device [chars]","Local switch-id collision with other device","No action is required."
"FABRICPATH","6","FABRICPATH_SWID_PRI_SEC_CHANGED","Switch-id [dec] is changed to [chars]","Local switch-id status changed","No action is required."
"FABRICPATH","6","FABRICPATH_SWID_STATE_CHANGED","Switch-id [dec] status changed to [chars]","Local switch-id status changed","No action is required."
"FALCON-SLOT#","2","FALCON_EXITED","Falcon exited (syserr = [dec], errno = [dec])","Falcon exited","No action is required."
"FC-REDIRECT","2","ACL_ERR_ADD_HOST","Unable to FC-Redirect Host [chars] traffic going to Target [chars] for application [chars] on Switch [chars] because of ACL module error: [hex] ([chars]) on Module [dec]","FC-Redirect is unable to program ACL entries. ACL module returned an error.","No action is required."
"FC-REDIRECT","2","ACL_ERR_FLOGI_NOT_ALLOWED","FLOGI from device [chars] connected at interface [chars] is denied because of ACL module error: [hex] ([chars]) on Module [dec]","FC-Redirect is unable to program ACL entries. ACL module returned an error.","No action is required."
"FC-REDIRECT","2","ACL_ERR_NEW_CFG","Unable to Process Configuration Created by [chars] on Switch [chars] for Target [chars] because of ACL module error: [hex] ([chars]) on Module [dec]","FC-Redirect is unable to program ACL entries. ACL module returned an error.","No action is required."
"FC-REDIRECT","2","ACL_ERR_TRUNK_PORT_UP","Unable to program trunk port I/F [chars] because of ACL module error: [hex] ([chars]) on Module [dec]","FC-Redirect is unable to program ACL entries. ACL module returned an error.","No action is required."
"FC-REDIRECT","2","ACL_ERR_UPG_MODULE_REGION1_V1","Unable to program ACL entries on module [dec] because of ACL error: [hex] ([chars]). Hitless Upgrade for Module Rejected","FC-Redirect is unable to program ACL entries. ACL module returned an error. Hitless upgrade for the module rejected. The module will reload now.","No action is required."
"FC-REDIRECT","2","ACL_ERR_UPG_MODULE_REGION2_V1","Unable to program ACL entries on module [dec] because of ACL error: [hex] ([chars]). Hitless Upgrade for Module Rejected","FC-Redirect is unable to program ACL entries. ACL module returned an error. Hitless upgrade for the module rejected. The module will reload now.","No action is required."
"FC-REDIRECT","2","ACL_ERR_UPG_MODULE_REGION2_V2","Unable to program ACL entries on module [dec] because of ACL error: [hex] ([chars]). Hitless Upgrade for Module Rejected.","FC-Redirect is unable to program ACL entries. ACL module returned an error. Hitless upgrade for the module rejected. The module will reload now.","No action is required."
"FC-REDIRECT","2","ACL_ERR_UPG_MODULE_REGION3","Unable to program ACL entries on module [dec] because of ACL error: [hex] ([chars]). Hitless Upgrade for Module Rejected","FC-Redirect is unable to program ACL entries. ACL module returned an error. Hitless upgrade for the module rejected. The module will reload now.","No action is required."
"FC-REDIRECT","2","ACL_MAX_REACHED_ADD_HOST","Unable to FC-Redirect Host [chars] traffic going to Target [chars] for application [chars] on Switch [chars] because of insufficent TCAM resources on Module [dec]","FC-Redirect is unable to program ACL entries possible cause can be more than allowed re-directable targets on the same switch and more than normal Host(s) are zoned with the Storage Port","No action is required."
"FC-REDIRECT","2","ACL_MAX_REACHED_FLOGI_NOT_ALLOWED","FLOGI from device [chars] connected at interface [chars] is denied as Maximum Allowable Configuration Reached on Module [dec]","FC-Redirect is unable to program ACL entries possible cause can be more than allowed re-directable targets on the same switch or more ISLsareco-locatedonasinglelinecardormorethannormalHost(s)arezonedwiththeStoragePort'","No action is required."
"FC-REDIRECT","2","ACL_MAX_REACHED_NEW_CFG","Unable to Process Configuration Created by [chars] on Switch [chars] for Target [chars] because of insufficient TCAM Resources on Module [dec]","FC-Redirect is unable to program ACL entries possible cause can be more than allowed re-directable targets on the same switch and more than normal Host(s) are zoned with the Storage Port","No action is required."
"FC-REDIRECT","2","ACL_MAX_REACHED_TRUNK_PORT_UP","Maximum Allowable Configuration Reached, Unable to program trunk port I/F [chars] on Module [dec]","FC-Redirect is unable to program ACL entries possible cause can be more than allowed re-directable targets on the same switch and more than normal Host(s) are zoned with the Storage Port","No action is required."
"FC-REDIRECT","2","ACL_TIMEOUT_ADD_HOST","Unable to FC-Redirect Host [chars] traffic going to Target [chars] for application [chars] on Switch [chars] because ACL module timed out on Module [dec]","FC-Redirect is unable to program ACL entries. Possible cause can be linecard is being upgraded/rebooted.","No action is required."
"FC-REDIRECT","2","ACL_TIMEOUT_FLOGI_NOT_ALLOWED","FLOGI from device [chars] connected at interface [chars] is denied because ACL module timed out on Module [dec]","FC-Redirect is unable to program ACL entries. Possible cause can be linecard is being upgraded/rebooted.","No action is required."
"FC-REDIRECT","2","ACL_TIMEOUT_NEW_CFG","Unable to Process Configuration Created by [chars] on Switch [chars] for Target [chars] because ACL module timed out on Module [dec]","FC-Redirect is unable to program ACL entries. Possible cause can be linecard is being upgraded/rebooted.","No action is required."
"FC-REDIRECT","2","ACL_TIMEOUT_TRUNK_PORT_UP","Unable to program trunk port I/F [chars] because ACL module timed out on Module [dec]","FC-Redirect is unable to program ACL entries. Possible cause can be linecard is being upgraded/rebooted.","No action is required."
"FC-REDIRECT","2","FC_REDIRECT_SYSMGR_INSTALL_FAIL_ACTIVE_CONFIG","FC-Redirect Active Config Exists. Hitful Downgrade Rejected","FC-Redirect Downgrade to versions 3.2 and lower is not supported, if Active Configs Exist. Hitfull Downgrade for the module is rejected. Please use showfc-redirectconfigs'andremoveappropriateconfigsfromtheapplications'","No action is required."
"FC-REDIRECT","2","FC_REDIRECT_SYSMGR_INSTALL_FAIL_PASSIVE_CONFIG","FC-Redirect Configs Exist. Hitful Downgrade Rejected","FC-Redirect Downgrade to versions 3.2 and lower is not supported, if Configs Exist on this switch. Hitful Downgrade for the module is rejected. Before doing a HITFUL downgrade to any version lower than 3.2.1, Please use clearfc-redirectdecommission-switch''","No action is required."
"FC-REDIRECT","2","FC_REDIRECT_SYSMGR_INSTALL_FAIL_V2_CONFIG","FC-Redirect V2 Configs Exist. Hitful Downgrade Rejected","FC-Redirect Downgrade to versions 3.3.1 and lower is not supported, if Version-2 Configs Exist. Hitfull Downgrade for the module is rejected.","No action is required."
"FC-REDIRECT","2","FC_REDIRECT_SYSMGR_INSTALL_FAIL","Hitful Downgrade Rejected. Reason: [chars]","FC-Redirect Downgrade to NXOS 4.x or lower is not allowed if the following is true: 1) IVR support is enabled IVR is enabled locally or if FCR app has crested some configurations on local switch 2) FCR has some configs for local FPC devices Hitfull Downgrade for the module is rejected.","No action is required."
"FC-REDIRECT","2","FLOGI_REJECTED_DEV_ONLINE_WITH_DIFFERENT_FCID","Vsan: [dec], Interface: [chars] on Module [dec], Device PWWN: [chars], Existing fcid: [hex], New_fcid: [hex]","FC-Redirect Rejected FLOGI request as it already has the pwwn with a different FCID in its database.","No action is required."
"FC-REDIRECT","2","FLOGI_REJECTED_FCR_IVR_FLOW_LC1_USED","[chars] [chars], Vsan: [dec], Interface: [chars] on Module [dec], fcr_cfg_vsan: [dec], other_dev_in_flow: [chars] [chars]","FC-Redirect Rejected FLOGI request as the port is on a Gen-1 Line Card and is part of IVR flow with FC-Redirect configuration in vsan fcr_cfg_vsan'.'","No action is required."
"FC-REDIRECT","2","INCOMPATIBLE_SWITCH_IN_FABRIC","An Incompatible Switch [chars] added to fabric when FC-Redirect is configured in Version 2 Mode.","FC-Redirect is Configured in Version 2 Mode. A switch with FC-Redirect version 3.2.x in the fabric is NOT supported in this mode. FC-Redirect has locked the Fabric. No more FC-Redirect configuration changes would be allowed till this switch is disconnected.","No action is required."
"FC-REDIRECT","2","IVR_DEV_UP_REJECTED_DEV_ONLINE_WITH_DIFFERENT_FCID","Vsan: [dec], Device PWWN: [chars], Existing fcid: [hex], New_fcid: [hex]","FC-Redirect Rejected Device UP request from IVR as it already has the pwwn with a different FCID in its database.","No action is required."
"FC-REDIRECT","2","IVR_SUPPORT_ENABLE_REJECTED_IVR_FCR_CFG_ALREADY_EXISTS","Req Src: [chars]","FC-Redirect service rejected a request to enable support for IVR flows as it received an error when registering with AAM module. FCR config for IVR virtual devices already exixts though IVR support is not enabled. This is not supported. Please remove the appropriate FCR application config and retry again.","No action is required."
"FC-REDIRECT","2","IVR_SUPPORT_ENABLE_REJECTED","Req Src: [chars], Error Code: [hex] ([chars])","FC-Redirect service rejected a request to enable support for IVR flows as it received an error when registering with AAM module.","No action is required."
"FC-REDIRECT","2","PCMAP_ERR_TRUNK_PORT_UP","PORT_UP request for first member of Port-channel [chars]'FailedduetoPCMAPErrorseenbyFC-Redirect'","FC-Redirect encountered a PCMAP Error (Internal Error) when processing PORT_UP request for the first member in port channel. The PORT_UP request was rejected.","No action is required."
"FC-REDIRECT","2","TGT_NOT_ATTACHED_TO_FCR_SWITCH","FC-Redirect Configuration vsan: [dec], Tgt: [chars] VT: [chars] - Tgt is online, but not connected to a switch running FC-Redirect.","FC-Redirect requires that targets must be connected to a switch running FC-Redirect. Please Check Config.","No action is required."
"FC-REDIRECT","2","TRUNK_PORT_UP_REJ_FCR_IVR_FLOW_LC1_USED","Vsan: [dec], trunk port I/F [chars] on Module [dec], dev: [chars], dev_type: [chars], dev_vsan: [dec]","FC-Redirect Rejected Port Bringup request as the port is on a Gen-1 Line Card and the Vsan is used by FC-Redirect/IVR flow FC-Redirect does NOT support Gen-1 LineCards for IVR virtual devices with FC-Redirect Configuration.","No action is required."
"FC-REDIRECT","2","V2_ENABLE_CFG_CHG_CFS_SW_ERR","Error_Switch: [chars] did not respond to request to change all configurations to Version 2 Mode.","FC-Redirect did not receive a response from Error_Switch'foraCFSbroadcasttoupdateallconfigurationstoVersion2mode.AttempttoconfigureVers ion2modeFailed.AllFC-RedirectswitchesarenowinErrorMode.Pleasemakesurethefabricisstableandr etrytheConfigurationcommand:'fc-redirectversion2enable''","No action is required."
"FC-REDIRECT","2","V2_ENABLE_UNLOCK_V1_TO_V2_DONE_CFS_SW_ERR","Error_Switch: [chars] did not respond to request to unlock FC-Redirect Configurations after configuring Version 2 Mode.","FC-Redirect did not receive a response from Error_Switch'foraCFSbroadcasttounlockFC-RedirectconfigurationsafterconvertingthemtoVersion2 mode.AttempttoconfigureVersion2modeFailed.AllFC-RedirectswitchesarenowinErrorMode.Please makesurethefabricisstableandretrytheConfigurationcommand:'fc-redirectversion2enable''","No action is required."
"FC-REDIRECT","2","V2_ENABLE_UNLOCK_V2_TO_V1_DONE_CFS_SW_ERR","Error_Switch: [chars] did not respond to request to unlock FC-Redirect Configurations after disabling Version 2 Mode.","FC-Redirect did not receive a response from Error_Switch'foraCFSbroadcasttounlockFC-RedirectconfigurationsafterdisablingVersion2mode.At tempttodisableVersion2modeFailed.AllFC-RedirectswitchesarenowinErrorMode.Pleasemakesureth efabricisstableandretrytheConfigurationcommand:'nofc-redirectversion2enable''","No action is required."
"FC-REDIRECT","3","CFG_REQ_REJECTED_APPL_SW_LOWER_VER","vsan: [dec], Tgt: [chars], VT: [chars], Appl_Switch: [chars], Slot: [dec], Service: [chars] ([dec]), ivr_dev: [chars], req_type: [chars], appl_sw_ver: [dec]","FC-Redirect rejected configuration request for IVR Virtual device as the application switch has NXOS lower than 5.x. FC-Redirect requires the following to be configured before FC-Redirect based applications can create configuration for IVR Virtual devices: 1) IVR AAM register be enabled (config command) 2) FC-Redirect ivr-support enable (Config command) 3) All IVR enabled switches and FC-Redirect application switches must be running NXOS version 5.x or higher.","No action is required."
"FC-REDIRECT","3","CFG_REQ_REJECTED_IVR_AAM_NOT_REGISTERED","vsan: [dec], Tgt: [chars], VT: [chars], Switch: [chars], Slot: [dec], Service: [chars] ([dec]), ivr_dev: [chars], req_type: [chars]","FC-Redirect rejected configuration request for IVR Virtual device as IVR-Support is disabled. FC-Rediredct requires the following to be configured before FC-Redirect based applications can create configuration for IVR Virtual devices: 1) IVR AAM register be enabled (config command) 2) FC-Redirect ivr-support enable (Config command)","No action is required."
"FC-REDIRECT","3","CFG_REQ_REJECTED_IVR_SUPPORT_DISABLED","vsan: [dec], Tgt: [chars], VT: [chars], Switch: [chars], Slot: [dec], Service: [chars] ([dec]), ivr_dev: [chars], req_type: [chars]","FC-Redirect rejected configuration request for IVR Virtual device as IVR-Support is disabled. FC-Rediredct requires the following to be configured before FC-Redirect based applications can create configuration for IVR Virtual devices: 1) IVR AAM register be enabled (config command) 2) FC-Redirect ivr-support enable (Config command) 3) All IVR enabled switches and FC-Redirect application switches must be running NXOS version 5.x or higher.","No action is required."
"FC-REDIRECT","3","CFS_PRE_CHK_FCR_ERR","Pre-chk request Rejected by FC-Redirect on Peer Switch: Err Sw: [chars], status: [dec] ([chars])","The Pre-Chk message is currently used when enabling/disabling Version 2 or ivr-support in fc-redirect. An appropriate syserr would be generated for the purpose.","No action is required."
"FC-REDIRECT","3","CFS_PRE_CHK_SW_ERR","FC-Redirect did not recv. rsp from Peer switch. Error Switch: [chars], CFS rc: [dec], rsp size: [dec]","The Pre-Chk message is currently used when enabling/disabling Version 2 or ivr-support in fc-redirect. An appropriate syserr would be generated for the purpose.","No action is required."
"FC-REDIRECT","3","CFS_REQ_SEND_ERR","req_type: [dec], req_size = [dec], Error = [dec] ([chars])","FC-Redirect Failed to send CFS request.","No action is required."
"FC-REDIRECT","3","CFS_RSP_SEND_ERR","req_type: [dec], rrtoken = [dec], rsp_size = [dec], error = [dec] ([chars])","FC-Redirect Failed to send CFS response.","No action is required."
"FC-REDIRECT","3","CFS_SEND_REGISTER_ERR","syserr: [hex] ([chars])","FC-Redirect Failed to send register request to CFS.","No action is required."
"FC-REDIRECT","3","DELETE_CFG_CFS_FCR_ERR_PEER_IN_ERR_STATE","Tgt: [chars], VT: [chars], Switch [chars], Slot: [dec], Service [chars], Error_Switch: [chars]","FC-Redirect on switch Error_Switch'rejecteddelete_configbroadcastasitisin'Error'state.FC-Redirectconfigurationisoutofsy ncacrossthefabric.Ifthisdelete_cfgwasdonetoresolvetheerrorstate,ignorethiserror.Ifnot,resolvetheco nflictthatcausedtheerrorstateandforce'Error_Switch'tosyncwiththefabricagainusing'testfc-redirectc onfigsync-with-fabric'command.'","No action is required."
"FC-REDIRECT","3","DELETE_CFG_CFS_FCR_ERR","Tgt: [chars], VT: [chars], Switch: [chars], Slot: [dec], Service: [chars], Error_Switch: [chars], FCR CFS error code = [dec] ([chars])","FC-Redirect on switch Error_Switch'rejecteddelete_configbroadcast.Ignorethiserrorifthiswascausedby'testfc-redirectconfi gsync-with-fabric'command.Ifnot,FC-Redirectconfigurationisoutofsyncacrossthefabric.Pleaseforce 'Error_Switch'tosyncwiththefabricagainusing'testfc-redirectconfigsync-with-fabric'command.'","No action is required."
"FC-REDIRECT","3","DELETE_CFG_CFS_SW_ERR","vsan: [dec], Tgt: [chars], VT: [chars], Switch: [chars], Slot: [dec], Service: [chars], Error_Switch: [chars], CFS error code = [dec]","FC-Redirect did not receive a response from Error_Switch'fordelete_cfgCFSbroadcast.FC-Redirectconfigurationisoutofsyncacrossthefabric.Ple asedeletethisconfigurationandretryit.'","No action is required."
"FC-REDIRECT","3","FAILOVER_CFG_PRE_CHK_CFS_FCR_ERR_PEER_IN_ERR_STATE","Tgt: [chars], Old VT: [chars], New VT: [chars], Switch: [chars], Slot: [dec], Service: [chars] ([dec]), Error_Switch: [chars]","FC-Redirect on switch Error_Switch'rejectedConfigPRE_CHECKbroadcastfornew_configasitisin'Error'state.CreateFailov erConfigrequestfromtheapplicationwasrejected.Pleaseresolvetheconflictthatcausedtheerrorstateand force'error-switch'tosyncwiththefabricagainusing'testfc-redirectconfigsync-with-fabric'command.'","No action is required."
"FC-REDIRECT","3","FAILOVER_CFG_PRE_CHK_CFS_FCR_ERR","Tgt: [chars], Old VT: [chars], New VT: [chars], Switch: [chars], Slot: [dec], Service: [chars] ([dec]), Error_Switch: [chars], FCR CFS error code = [dec] ([chars])","FC-Redirect on switch Error_Switch'rejectedConfigpre-checkbroadcastforCreateConfig.Create_Failover_Configrequestfr omapplicationwasrejected.'","No action is required."
"FC-REDIRECT","3","FAILOVER_CFG_PRE_CHK_CFS_SW_ERR","Tgt: [chars], Old VT: [chars], New VT: [chars], Switch: [chars], Slot: [dec], Service: [chars] ([dec]), Error_Switch: [chars], CFS error code = [dec]","FC-Redirect did not receive a response from Error_Switch'forConfigPreCheckCFSbroadcastforCreateFailoverConfig.CreateFailoverConfigrequ estwasrejected.'","No action is required."
"FC-REDIRECT","3","FC_REDIRECT_CFG_REJECTED_DEFAULT_ZONE_ENTRY_PERMIT","CFG Rejected: Application: [chars], Target: [chars], vsan: [dec]","FC-Redirect rejected configuration request from the Application as default zone entry for the VSAN is configured as PERMIT. FC-Redirect requires that the default zone entry be DENY for all VSANs with FC-Redirect configuration. FC-Redirect will reject all further FC-Redirect configurations in this vsan till default zone entry is set to DENY. Please set default zone entry to DENY.","No action is required."
"FC-REDIRECT","3","FC_REDIRECT_CFS_NEW_CFG_REJECTED_ZONE_DEFAULT_ENTRY_PERMIT","Default Zone Entry is permit in vsan [dec]. New CFG from switch [chars] rejected. App: [chars], tgt: [chars], vt: [chars].","FC-Redirect requires the default zone entry be configured as DENY for vsans with devices that have FC-Redirect configurations. But the specified vsan has default entry permit. FC-Redirect rejected new cfg request from app'onthespecifiedswitch.PleasechangetheDefaultzoneentrytoDENYforthevsan.'","No action is required."
"FC-REDIRECT","3","FC_REDIRECT_FC2_UNEXPECTED_FRAME_FRM_AAM","Unexpected FC2 Frame received by FC-Redirect SID: [hex], DID: [hex], VSAN: [dec], IFindex: [chars]","FC-Redirect received a FC2 frame for some unknown WWN, which it is not expecting. FC-Redirect cannot handle this frame and hence dropping it. This is an internal AAM Error and shouldnt have been forwarded to Fc-Redirect.","No action is required."
"FC-REDIRECT","3","FC_REDIRECT_REJECT_IVR_VIRT_DEV_BRINGUP_FCR_VIRT_DEV","Vsan: [dec], IVR Virtual Device: [chars], FCR Virtual Dev Type: [chars].","IVR is trying to bring up a Virtual device whose PWWN is same as FC-Redirect Virtual Device. This is a mis-configuration.","No action is required."
"FC-REDIRECT","3","FC_REDIRECT_REJECT_IVR_VIRT_DEV_BRINGUP_IVR_SUPPORT_DISABLED","Vsan: [dec], IVR Virtual Device: [chars]","IVR is trying to bring up a Virtual device. FC-Redirect already has a configuration for that device - But FC-Redirect IVR-Support is currently disabled. This is a mis-Configuration. FC-Redirect IVR-Support must be enabled before configuring FC-Redirect based appliactions to use IVR Virtual devices. FC-Redirect rejected IVR device bring-up. Please delete the relevant application configuration before proceeding further.","No action is required."
"FC-REDIRECT","3","FC_REDIRECT_REJECT_IVR_VIRT_DEV_BRINGUP_SANITY_ERR","Vsan: [dec], IVR Virtual Device: [chars], Action: [dec].","IVR is trying to bring up a Virtual device - But the Message has some Sanity Errors. FC-Redirect failed IVR Device Bringup.","No action is required."
"FC-REDIRECT","3","FC_REDIRECT_ZONE_DEFAULT_ENTRY_PERMIT","Default zone entry set to PERMIT in vsan [dec]. This vsan has FC-Redirect configs. FC-redirect requires Default Zone be DENY. All further FC-Redirect configuration requests in this vsan will be rejected till default zone entry is configured as DENY.","FC-Redirect requires the default zone entry be configured as DENY for vsans with devices that have FC-Redirect configurations. But the specified vsan has default zone entry configured as permit. FC-Redirect will reject all further FC-Redirect configuration in this vsan till default entry is configured as DENY. Please set default zone entry to DENY.","No action is required."
"FC-REDIRECT","3","GCD_CFS_SW_ERR","CFS Error. Error_Switch: [chars], VT: [chars], CFS swresp_reason_code: [chars]([dec]), swresp_size: [dec], cfs_sanity_error_code: [dec], attempt: [dec]/[dec]","CFS failure. FC-Redirect moved peer to Error state","No action is required."
"FC-REDIRECT","3","GCS_CFS_SW_ERR","CFS Error. Error_Switch: [chars], CFS swresp_reason_code: [chars]([dec]), swresp_size: [dec], cfs_sanity_error_code: [dec], attempt: [dec]/[dec]","CFS failure. FC-Redirect moved peer to Error state","No action is required."
"FC-REDIRECT","3","INTERNAL_ERROR","[chars]","FC-Redirect Encountered an Internal Error.","No action is required."
"FC-REDIRECT","3","IVR_SUPPORT_DISABLE_REJECTED_PEER_SW_ERR_STATE","Failed to Disable IVR Support - Error_Switch: [chars], peer_in_err_state: [chars]","The command nofc-redirectivr-supportenable'Failed.FC-Redirectonswitch'Error_Switch'rejectedpre-checkforIVR SupportDisablerequestasithasoneofitspeerswitches'peer_in_err_state'inErrorstate.Pleaseresolvethe conflictthatcausedtheerrorstateandforce'error-switch'tosyncwiththefabricagainusing'testfc-redirectc onfigsync-with-fabric'command.'","No action is required."
"FC-REDIRECT","3","IVR_SUPPORT_DISABLE_REJ_PEER_WITH_CFG_FOR_IVR_VIRT_DEV","Failed to Disable IVR Support - Error_Switch: [chars]","The command nofc-redirectivr-supportenable'Failed.FC-Redirectonswitch'Error_Switch'rejectedpre-checkforIVR SupportDisablerequestasithasFC-RedirectconfigurationforIVRVirtualDevices.Pleaseremovethecon cernedapplicationconfigurationandretrythecommand'","No action is required."
"FC-REDIRECT","3","IVR_SUPPORT_DISABLE_REJ_PRECHK_CFS_FCR_ERR","Failed to Disable IVR Support - Error_Switch: [chars]","The command nofc-redirectivr-supportenable'Failed.FC-Redirectonswitch'Error_Switch'rejectedthepre-chkreques t.'","No action is required."
"FC-REDIRECT","3","IVR_SUPPORT_DISABLE_REJ_PRECHK_CFS_SW_ERR","Failed to Disable IVR Support - Error_Switch: [chars]","The command nofc-redirectivr-supportenable'Failed.FC-Redirectonswitch'Error_Switch'didnotrespondtopre-chec kforIVRSupportDisablerequest'","No action is required."
"FC-REDIRECT","3","IVR_VIRT_DEV_BRINGUP_REJECTED_LC1_ACTIVE","Curr_Vsan: [dec], IVR Virtual Device: [chars], vsan_with_gen1_ISL: [dec]","IVR is trying to bring up a Virtual device in Curr_Vsan'forwhichFC-Redirectconfigurationexistsonthisswitch.Thisisamis-configuration.FC-Red irectdoesNOTsupportports(FXorISLs)onGen-1CardsifthereisconfigurationforIVRVirtualDevices.P leaseshutdownthegen-1portsinvolvedinFCR-IVRflowsandretryagain'","No action is required."
"FC-REDIRECT","3","MODIFY_CFG_CFS_FCR_ERR_PEER_IN_ERR_STATE","Tgt: [chars], VT: [chars], Switch [chars], Slot: [dec], Service [chars], Error_Switch: [chars]","FC-Redirect on switch Error_Switch'rejectedmodify_configbroadcastasitisin'Error'state.FC-Redirectconfigurationisoutofs yncacrossthefabric.Pleaseresolvetheconflictthatcausedtheerrorstateandforce'Error_Switch'tosyncw iththefabricagainusing'testfc-redirectconfigsync-with-fabric'command.'","No action is required."
"FC-REDIRECT","3","MODIFY_CFG_CFS_FCR_ERR","Tgt: [chars], VT: [chars], Switch [chars], Slot: [dec], Service: [chars], Error_Switch: [chars], FCR CFS error code = [dec] ([chars])","FC-Redirect on switch Error_Switch'rejectedmodify_configbroadcast.FC-Redirectconfigurationisoutofsyncacrossthefabri c.Pleasedeletethisconfigurationandretryit.'","No action is required."
"FC-REDIRECT","3","MODIFY_CFG_CFS_SW_ERR","vsan: [dec], Tgt: [chars], VT: [chars], Switch: [chars], Slot: [dec], Service: [chars], Error_Switch: [chars], CFS error code = [dec]","FC-Redirect did not receive a response from Error_Switch'formodify_cfgCFSbroadcast.FC-Redirectconfigurationisoutofsyncacrossthefabric.Pl easedeletethisconfigurationandretryit.'","No action is required."
"FC-REDIRECT","3","MTS_RSP_SEND_ERR","MTS Opcode: [dec], rrtoken = [dec], rsp_size = [dec], errno = [dec] ([chars])","FC-Redirect Failed to send MTS response.","No action is required."
"FC-REDIRECT","3","NEW_CFG_CFS_FCR_ERR_PEER_IN_ERR_STATE","Tgt: [chars], VT: [chars], Switch [chars], Slot: [dec], Service: [chars], Error_Switch: [chars]","FC-Redirect on switch Error_Switch'rejectednew_configbroadcastasitisin'Error'state.FC-Redirectconfigurationisoutofsyn cacrossthefabric.Pleaseresolvetheconflictthatcausedtheerrorstateandforce'error-switch'tosyncwitht hefabricagainusing'testfc-redirectconfigsync-with-fabric'command.'","No action is required."
"FC-REDIRECT","3","NEW_CFG_CFS_FCR_ERR","Tgt: [chars], VT: [chars], Switch [chars], Slot: [dec], Service: [chars], Error_Switch: [chars], FCR CFS error code = [dec] ([chars])","FC-Redirect on switch Error_Switch'rejectednew_configbroadcast.FC-Redirectconfigurationisoutofsyncacrossthefabric.Pl easedeletethisconfigurationandretryit.'","No action is required."
"FC-REDIRECT","3","NEW_CFG_CFS_SW_ERR","vsan: [dec], Tgt: [chars], VT: [chars], Switch: [chars], Slot: [dec], Service: [chars], Error_Switch: [chars], CFS error code = [dec]","FC-Redirect did not receive a response from Error_Switch'fornew_cfgCFSbroadcast.FC-Redirectconfigurationisoutofsyncacrossthefabric.Pleas edeletethisconfigurationandretryit.'","No action is required."
"FC-REDIRECT","3","NEW_CFG_PRE_CHK_CFS_FCR_ERR_PEER_IN_ERR_STATE","Tgt: [chars], VT: [chars], Switch: [chars], Slot: [dec], Service: [chars] ([dec]), Error_Switch: [chars]","FC-Redirect on switch Error_Switch'rejectedConfigPRE_CHECKbroadcastfornew_configasitisin'Error'state.NEW_CON FIGrequestfromtheapplicationwasrejected.Pleaseresolvetheconflictthatcausedtheerrorstateandforce 'error-switch'tosyncwiththefabricagainusing'testfc-redirectconfigsync-with-fabric'command.'","No action is required."
"FC-REDIRECT","3","NEW_CFG_PRE_CHK_CFS_FCR_ERR","Tgt: [chars], VT: [chars], Switch: [chars], Slot: [dec], Service: [chars] ([dec]), Error_Switch: [chars], FCR CFS error code = [dec] ([chars])","FC-Redirect on switch Error_Switch'rejectedConfigpre-checkbroadcastforCreate_Config.Create_configrequestfromapplic ationwasrejected.'","No action is required."
"FC-REDIRECT","3","NEW_CFG_PRE_CHK_CFS_SW_ERR","Tgt: [chars], VT: [chars], Switch: [chars], Slot: [dec], Service: [chars] ([dec]), Error_Switch: [chars], CFS error code = [dec]","FC-Redirect did not receive a response from Error_Switch'forConfigPreCheckCFSbroadcastfornewconfig.CreateConfigrequestwasrejected.'","No action is required."
"FC-REDIRECT","3","REPLACE_VT_CFG_CFS_FCR_ERR_PEER_IN_ERR_STATE","Tgt: [chars], VT: [chars], Switch [chars], Slot: [dec], Service: [chars], Error_Switch: [chars]","FC-Redirect on switch Error_Switch'rejectedreplace_vtrequestasitisin'Error'state.FC-Redirectconfigurationisoutofsyncacr ossthefabric.Pleaseresolvetheconflictthatcausedtheerrorstateandforce'Error_Switch'tosyncwiththef abricagainusing'testfc-redirectconfigsync-with-fabric'command.'","No action is required."
"FC-REDIRECT","3","UNKNOWN_CFS_REQ_ERR","CFS req_type: [dec], Error_Switch: [chars]","FC-Redirect on switch Error_Switch'rejectedCFSRequestoftype'req_type'.'","No action is required."
"FC-REDIRECT","3","V2_ENABLE_ERR_CFS_SW_ERR","Error_Switch: [chars] did not respond to request to abort fc-redirectversion2enable'command.'","FC-Redirect did not receive a response from Error_Switch'foraCFSbroadcasttoabort'fc-redirectversion2enable'command.AttempttoconfigureVe rsion2modeFailed.PleasemakesurethefabricisstableandretrytheConfigurationcommand:'fc-redirect version2enable''","No action is required."
"FC-REDIRECT","3","V2_ENABLE_LOCK_CFS_SW_ERR","Error_Switch: [chars] did not respond to lock FC-Redirect configurations.","FC-Redirect did not receive a response from Error_Switch'forCHG_MODE_LOCKCFSbroadcast.AttempttoconfigureVersion2modeFailed.'","No action is required."
"FC-REDIRECT","3","V2_ENABLE_PRECHK_CFS_SW_ERR","Error_Switch: [chars] did not respond to pre-check request for fc-redirectversion2enable'command.'","FC-Redirect did not receive a response from Error_Switch'foraCFSbroadcasttocheckif'fc-redirectversion2enable'commandcanbeexecuted.Atte mpttoconfigureVersion2modeFailed.PleasemakesurethefabricisstableandretrytheConfigurationcom mand:'fc-redirectversion2enable''","No action is required."
"FC-REDIRECT","3","V2_ENABLE_UNLOCK_V1_TO_V2_ABORT_CFS_SW_ERR","Error_Switch: [chars] did not respond to request to unlock FC-Redirect Configurations.","FC-Redirect did not receive a response from Error_Switch'foraCFSbroadcasttounlockFC-Redirectconfigurationswhenabortingtheattempttoconfi gureVersion2Mode.AttempttoconfigureVersion2modeFailed.Pleasemakesurethefabricisstableandre trytheConfigurationcommand:'fc-redirectversion2enable''","No action is required."
"FC-REDIRECT","3","V2_ENABLE_UNLOCK_V2_TO_V1_ABORT_CFS_SW_ERR","Error_Switch: [chars] did not respond to request to unlock FC-Redirect Configurations","FC-Redirect did not receive a response from Error_Switch'foraCFSbroadcasttounlockFC-Redirectconfigurationswhenabortingtheattempttodisab leVersion2Mode.AttempttodisableVersion2modeFailed.Pleasemakesurethefabricisstableandretryth eConfigurationcommand:'nofc-redirectversion2enable''","No action is required."
"FC-REDIRECT","5","ADD_HOST_APPL_REQ","FC-Redirect Configuration Host added for Service [chars] enabled on Switch [chars] Slot [dec] Tgt: [chars] Vt: [chars] Host: [chars] Vi: [chars] vsan: [dec]","Redirect Service requested for the Host / Tgt Pair","No action is required."
"FC-REDIRECT","5","DECOMMISSIONED_SWITCH","FC-Redirect Decommissioned [chars] on Local Switch","FC-Redirect Service has been decommissioned on this Switch.","No action is required."
"FC-REDIRECT","5","DEL_HOST_APPL_REQ","Service [chars] enabled on Switch [chars] Slot [dec] no longer requires FC-Redirect services for Host [chars] Tgt [chars] pair, vsan: [dec]","Redirect Service removed for the Host / Tgt Pair","No action is required."
"FC-REDIRECT","5","DEL_VT_APPL_REQ","FC-Redirect Configuration vsan: [dec], Tgt: [chars] VT: [chars] Deleted for Service [chars] Created by Switch [chars] Slot [dec] on application request","Application has requested this deletion","No action is required."
"FC-REDIRECT","5","DEL_VT_CLI_CLEAR_CFG","FC Redirect Configuration deleted. vsan: [dec], Tgt: [chars], VT: [chars], Service: [chars], Switch [chars], Slot [dec].","FC Redirect Configuration deleted because of the cli command clearfc-redirectconfigvt<vt-pwwn","No action is required."
"FC-REDIRECT","5","DEL_VT_DECOM_SW","FC Redirect Configuration deleted: vsan: [dec], Tgt: [chars], VT: [chars], Service: [chars], Switch [chars], Slot [dec].","FC Redirect Configuration deleted because FC Redirect on this switch was decommissioned","No action is required."
"FC-REDIRECT","5","DEL_VT_LOCAL_CFG_REQ_FROM_PEER","FC Redirect Configuration deleted: vsan: [dec], Tgt: [chars], VT: [chars], Service: [chars], Switch: [chars], Slot: [dec], Peer Switch : [chars].","FC Redirect Configuration deleted because of request from peer.","No action is required."
"FC-REDIRECT","5","DEL_VT_PENDING_DEL","FC Redirect Configuration deleted. vsan: [dec], Tgt: [chars], VT: [chars], Service: [chars], Switch: [chars], Slot: [dec], Peer Switch: [chars].","Peer_Switch'haddeletedtheconfigurationwhenitlostconnectivitywiththisswitch.Configurationonthis switchisnowdeletedwhenconnectionwasrestoredandFCRedirectsyncedwiththePeer_Switch.'","No action is required."
"FC-REDIRECT","5","DEL_VT_REMOTE_CFG_REQ","FC Redirect Configuration deleted: vsan: [dec], Tgt: [chars], VT: [chars], Service: [chars], Switch [chars], Slot [dec].","FC Redirect Configuration created by a peer deleted because of local application request.","No action is required."
"FC-REDIRECT","5","DEL_VT_SYNC_UP_WITH_PEER","FC Redirect Configuration deleted. vsan: [dec], Tgt: [chars], VT: [chars], Service: [chars], Switch [chars], Slot [dec].","FC Redirect Configuration deleted as the peer switch that created the configuration has deleted it. This happenned when FC Redirect synced with the peer switch.","No action is required."
"FC-REDIRECT","5","DEL_VT_TIMEOUT","FC-Redirect Configuration vsan: [dec], Tgt:[chars] VT:[chars] Deleted for Service [chars] Created by Switch [chars] Slot [dec] because of Timeout","Application has not become online within configured timeout value","No action is required."
"FC-REDIRECT","5","DEL_VT_VSAN_DEL","FC-Redirect Configuration Tgt: [chars] VT: [chars] Deleted for Service [chars] Created by Switch [chars] Slot [dec] because of VSAN [dec] deletion","Required Vsan for this configuration deleted in this switch","No action is required."
"FC-REDIRECT","5","INFO","[chars]","FC-Redirect informational message.","No action is required."
"FC-REDIRECT","5","IVR_SUPPORT_DISABLED","IVR Support Disabled in FC_Redirect. Source: [chars]","Admin has Disabled FC_Redirect support for IVR flows.","No action is required."
"FC-REDIRECT","5","IVR_SUPPORT_DISABLE_REJECTED","Req Src: [chars], Reason: [chars]","FC-Redirect service rejected a request to disable support for IVR flows","No action is required."
"FC-REDIRECT","5","IVR_SUPPORT_ENABLED","IVR Support Enabled in FC_Redirect. Source: [chars]","Admin has enabled FC_Redirect support for IVR flows.","No action is required."
"FC-REDIRECT","5","REPLACE_VT_APPL_REQ","FC Redirect delete configuration request: vsan: [dec], Tgt: [chars], VT: [chars], Created by Switch: [chars], Slot: [dec], for Service: [chars] requested by app on switch [chars].","FC Redirect has received a request from local Application to delete a config created by a remote switch.","No action is required."
"FC-REDIRECT","5","SYNC_WITH_FABRIC_BY_APP","FC-Redirect started Syncing with peers in Fabric because of request by Service [chars]","A local Service request FC-Redirect to sync FC-Redirect Configuration with the peer switches.","No action is required."
"FC-REDIRECT","5","SYNC_WITH_FABRIC_CLI_CMD","FC-Redirect started Syncing with peers in Fabric on CLI Command","testfc-redirectconfigsync-with-fabric'commandwasissuedonthisswitch.'","No action is required."
"FC-REDIRECT","5","SYNC_WITH_FABRIC_REQ_FROM_PEER","FC-Redirect started Syncing with peers in Fabric because of request from peer Switch [chars].","FC-Redirect on Peer switch requested FC-Redirect to sync FC-Redirect Configuration with peer switches.","No action is required."
"FC-REDIRECT","5","VT_CREATE_APPL_REQ","FC-Redirect Configuration created for Service [chars] enabled on Switch [chars] Slot [dec] Tgt: [chars] Vt: [chars], vsan: [dec]","Configuration created because of Application Request","No action is required."
"FC-REDIRECT","5","VT_CREATE_POWER_UP","FC-Redirect Configuration created for Service [chars] enabled on Switch [chars] Slot [dec] Tgt: [chars] Vt: [chars], vsan: [dec]","Configuration created after Power-Up","No action is required."
"FC-REDIRECT","5","VT_CREATE_PROCESS_RESTART","FC-Redirect Configuration created for Service [chars] enabled on Switch [chars] Slot [dec] Tgt: [chars] Vt: [chars], vsan: [dec]","Configuration created after Process Restart","No action is required."
"FC-REDIRECT","5","VT_CREATE_SWITCHOVER","FC-Redirect Configuration created for Service [chars] enabled on Switch [chars] Slot [dec] Tgt: [chars] Vt: [chars], vsan: [dec]","Configuration created after SUP Switchover","No action is required."
"FC-TUNNEL","3","INTERNAL_ERROR","Internal error: [chars]","FCMPLS tunnel process encountered a general error, one that does not fall in any of the categories. [chars] describes the error and its context.","No action is required."
"FC-TUNNEL","3","IPFC_ERROR","IPFC API, [chars], failed with error [hex]","FCMPLS tunnel invoked IPFC API and received the error code. [chars] describes the API and 0x[hex] specifies the error","No action is required."
"FC-TUNNEL","3","MTS_ERROR","MTS message transmission failed with error [dec]","FCMPLS tunnel process unsuccessfully tried to send a MTS message. MTS errro number is specified in [dec]","No action is required."
"FC-TUNNEL","3","NS_ERROR","FCNS API, [chars], failed with error [hex]","FCMPLS tunnel invoked FCNS API and received the error code. [chars] describes the API and 0x[hex] specifies the error","No action is required."
"FC-TUNNEL","3","PM_ERROR","Port Manager API, [chars], failed with error [hex]","FCMPLS tunnel invoked Port Manager API and received the error code. [chars] describes the API and 0x[hex] specifies the error","No action is required."
"FC-TUNNEL","3","PSS_CFG_RESTORE_ERROR","Configuration restoration for [chars] failed with error [hex]","FCMPLS tunnel read the saved configuration and encountered an error while rebuilding the runtime configuration. [chars] describes the configuration which the process tried to restore and 0x[hex] is the system error code","No action is required."
"FC-TUNNEL","3","PSS_ERROR","PSS operation [chars] returned error: [hex]","[chars] specifies the context where the failure occurred and 0x[hex] specifies the error","No action is required."
"FC-TUNNEL","3","PSS_RTDB_RESTORE_ERROR","Runtime database restoration for [chars] failed with error [hex]","FCMPLS tunnel read the saved runtime database and encountered an error while rebuilding the runtime database. [chars] describes the runtime database which the process tried to restore and 0x[hex] is the system error code","No action is required."
"FC-TUNNEL","3","RIB_ERROR","RIB API, [chars], failed with error [hex]","FCMPLS tunnel invoked RIB API and received the error code. [chars] describes the API and 0x[hex] specifies the error","No action is required."
"FC-TUNNEL","3","RSVP_PROTO_ERROR","RSVP protocol error: [chars]","RSVP-TE protocol error is encountered. [chars] describes the error and its context.","No action is required."
"FC-TUNNEL","3","UNEXPECTED_MTS_MSG","Unexpected MTS message, opcode [dec], is received","FCMPLS tunnel process received unexpected MTS event. MTS opcode is specified in [dec]","No action is required."
"FC-TUNNEL","5","MSG_INTERFACE_DOWN","Interface [chars] is down","The logical fc tunnel interface is down. This may be due to a reconfiguration on the fc tunnel, or issues on the underlying physical interface","If this is not due to a known reconfiguration, you should verify connectivity at the physical port level, and then on then on the fc tunnel interface. Furthermore, verify the physical ports along the fc tunnel path operate in the TE mode"
"FC-TUNNEL","5","MSG_INTERFACE_UP","Interface [chars] is up","The fc interface is up","No action is required."
"FCC_LC","2","ERROR_SENDING_HEART_BEAT","Error sending heart beat [dec]","FCC_LC has error sending heart beat","No action is required."
"FCC_LC","2","EXITING","Exiting fcc_lc: [chars]","FCC_LC exiting","No action is required."
"FCC_LC","2","HEART_BEAT_NOT_SENT","Heart beat not sent for [dec] millisecs","FCC_LC has not sent heart beat","No action is required."
"FCC_LC","2","SHUTDOWN","Process shutting down: [chars]","FCC_LC Process is shutting down","No action is required."
"FCC_LC","2","UNABLE_READ_DATA","Unable to read fcc data ([chars])","FCC is unable to read and process relevant FCC data","No action is required."
"FCC_LC","5","BAD_MSG","Received bad message: [chars]","FCC_LC has received a malformed/unrecognized message","No action is required."
"FCC_LC","5","DISABLE","FCC_LC has been disabled","FCC_LC has been disabled","No action is required."
"FCC_LC","5","ENABLE","FCC_LC has been enabled","FCC_LC has been enabled","No action is required."
"FCC_LC","5","STARTING","FCC_LC process started","Process started successfully","No action is required."
"FCC_LC","6","PRIO_UPDATE","Updated enable priority to [dec]","FCC_LC is active for packets with priority <= [threshold]","No action is required."
"FCC","2","SHUTDOWN","Process shutting down: [chars]","FCC Process is shutting down","No action is required."
"FCC","5","BAD_MSG","Received bad message: [chars]","FCC has received a malformed/unrecognized message","No action is required."
"FCC","5","CONGESTION_STATE_CHANGE_NOTIF","Received Congestion State Change notification to state: [dec]","FCC has received a Contestion State Change Notification","No action is required."
"FCC","5","DISABLE","FCC has been disabled","FCC has been disabled","No action is required."
"FCC","5","ENABLE","FCC has been enabled","FCC has been enabled","No action is required."
"FCC","5","RATE_LIMIT_END_NOTIF","Received Rate Limit End notification","FCC has received a Rate Limit End Notification","No action is required."
"FCC","5","RATE_LIMIT_START_NOTIF","Received Rate Limit Start notification","FCC has received a Rate Limit Start Notification","No action is required."
"FCC","5","STARTING","FCC process started","Process started successfully","No action is required."
"FCC","6","PRIO_UPDATE","Updated enable priority to [dec]","FCC is active for packets with priority <= [threshold]","No action is required."
"FCDDH-SLOT#","3","LOG_FCDDH_ERR","Nonrecoverable error - exiting: [chars]","Errors which cause program to exit occurred","No action is required."
"FCDDH-SLOT#","4","LOG_FCDDH_WARNING","Serious error: [chars]","Serious errors which affect all normal operations occurred","No action is required."
"FCDDH-SLOT#","5","LOG_FCDDH_DEBUG","Unexpected error: [chars]","Unexpected errors which affect some normal operations occurred","No action is required."
"FCDDH-SLOT#","5","LOG_FCDDH_NOTICE","[chars]","Major configuration changes","No action is required."
"FCDD-SLOT#","3","LOG_FCDD_ERR","Nonrecoverable error - exiting: [chars]","Errors which cause program to exit occurred","No action is required."
"FCDD-SLOT#","4","LOG_FCDD_WARNING","Warning!: [chars]","Serious errors which affect all normal operations occurred","No action is required."
"FCDD-SLOT#","5","LOG_FCDD_GCONF_FSM","[chars]","Illegal event received in Global Configuration FSM","No action is required."
"FCDD-SLOT#","5","LOG_FCDD_NOTICE","[chars]","Major configuration changes","No action is required."
"FCDD-SLOT#","5","LOG_FCDD_RESCAN_FSM","[chars]","Illegal event received in Rescan FSM","No action is required."
"FCDD-SLOT#","5","LOG_FCDD_TZONE_FSM","[chars]","Illegal event received in Twilight Zone Remover FSM","No action is required."
"FCDD-SLOT#","5","LOG_FCDD_VCONF_FSM","[chars]","Illegal event received in VSAN Configuration FSM","No action is required."
"FCDD-SLOT#","5","LOG_FCDD_VNO_FSM","[chars]","Illegal event received in VSAN Normal Operation FSM","No action is required."
"FCDD-SLOT#","7","LOG_FCDD_DEBUG","[chars]","Unexpected errors which affect some normal operations occurred","No action is required."
"FCDOMAIN","2","DOMS_CONFLICT","Conflict detected: ([dec]) domain ID [dec] WWN [chars]","Conflict detected ([dec]) domain ID [dec] with WWN [chars].","Check which switches have the same WWN and change either one; then change either's domain ID."
"FCDOMAIN","2","EPORT_ISOLATED","Isolation of interface [chars] (reason: [chars])","Fcdomain has isolated interface [chars] (reason: [chars].) Perform a show interface. Based on the reason specified, you might have to ensure domains are adequate and unique in the VSAN and perform a disruptive restart [fcdomain restart disruptive vsan <vsan-id>] or to reinitialize the port.","No action is required."
"FCDOMAIN","2","FC2BIND_FAILED","Bind to FC2 Service failed","Fcdomain has not been able to contact the FC2 module.","No action is required."
"FCDOMAIN","2","FC2_INITIALIZATION_FAILED","FC initialization sequence failed","The fcdomain has not been able to complete the initialization sequence with the Fibre Channel subsystem. fcdomain depends on resources not available at the moment: the switch might be short in memory or some other component might be unable to provide the necessary information to fcdomain.","No action is required."
"FCDOMAIN","2","FC2_SET_SOCKOPT_DM_SOCK_FAILED","set sockopt to FC2 Service failed","Fcdomain has not been able to setsockopt to the FC2 module.","No action is required."
"FCDOMAIN","2","FCID_PERSISTENT_TBL_COMPLETELY_FULL","FCID persistent table is completely full","The FCID persistent table is full. Perform [show fcdomain fcid persistent vsan <vsan-id>] to view the entries currently in the table. No more entries can be saved as persistent FCIDs across reboots.","Purge stale entries [purge fcdomain fcid] to obtain more free entries OR disable the feature on certain VSANs which are not critical enough [no fcdomain fcid persistent]."
"FCDOMAIN","2","HIGH_PRIORITY_MTSBIND_FAILED","Bind for high priority IPC failed","Fcdomain has not been able to contact the Inter Process Communication (IPC) module for its high priority queue.","No action is required."
"FCDOMAIN","2","INITIALIZATION_FAILED","Initialization sequence failed","The fcdomain has not been able to complete the initialization sequence. fcdomain depends on resources not available at the moment: the switch might be short in memory or some other component might be unable to provide the necessary information to fcdomain.","No action is required."
"FCDOMAIN","2","MTSBIND_FAILED","Bind to IPC failed","Fcdomain has not been able to contact the Inter Process Communication (IPC) module.","No action is required."
"FCDOMAIN","2","MTSREGISTRATION_FAILED","Registration of opcodes with IPC Service failed","Fcdomain has not been able to register its messages with the Inter Process Communication (IPC) module.","No action is required."
"FCDOMAIN","2","MTS_INITIALIZATION_FAILED","IPC initialization sequence failed","The fcdomain has not been able to complete the initialization sequence with the IPC (Inter Process Communication) subsystem. fcdomain depends on resources not available at the moment: the switch might be short in memory or some other component might be unable to provide the necessary information to fcdomain.","No action is required."
"FCDOMAIN","2","MY_NON_VIRTUAL_DOM_CONFLICTS","During VSAN merge detected that the local switch has the same domain ID [dec] and WWN [chars] of another switch","It has been detected that the local switch has the same domain ID [dec] and WWN [chars] of another switch.","Check which switches have the same WWN and change either one; then change either's domain ID."
"FCDOMAIN","2","NON_VIRTUAL_DOMS_CONFLICTS","During VSAN merge detected conflict between two switches having the same non-virtual domain ID [dec] and the same WWN [chars]","It has been detected that two switches have the same non-virtual domain ID [dec] and the same WWN [chars].","Check which switches have the same WWN and change either one; then change either's domain ID."
"FCDOMAIN","2","PSSBIND_FAILED","Bind to Persistent Storage Service failed","Fcdomain has not been able to contact the Persistent Storage Service (PSS).","No action is required."
"FCDOMAIN","2","RDIRJT","Rejected request for domain ID [dec], WWN requestor [chars] (reason code [dec])","An invalid request for domain IDs has been rejected by fcdomain.","Perform [show fcdomain vsan <vsan-id>] for all the switches in the affected VSAN; if a switch does not have a valid current domain ID, configure preferred domain ID zero, then perform [fcdomain restart vsan <vsan-id>] in the affected VSAN."
"FCDOMAIN","2","SYSBIND_FAILED","Bind to System Manager service failed","Fcdomain has not been able to contact the System Manager.","No action is required."
"FCDOMAIN","2","SYSMGR_INITIALIZATION_FAILED","System Manager initialization sequence failed","The fcdomain has not been able to complete the initialization sequence with the System Manager. fcdomain depends on resources not available at the moment: the switch might be short in memory or some other component might be unable to provide the necessary information to fcdomain.","No action is required."
"FCDOMAIN","3","COMMITERRORLOCALINVALIDALLOWEDDOMS","A remote switch attempted to locally apply an illicit allowed domains configuration","A remote switch attempted to locally apply an allowed domains configuration that doesn't include all currently assigned domains or the locally configured domain.","No action is required."
"FCDOMAIN","3","COMMITERRORREMOTEINVALIDALLOWEDDOMS","A remote switch (domain ID [dec], WWN [chars]) refuses to locally apply the proposed allowed domains","The remote switch with domain ID [dec] and WWN [chars] refuses to locally apply the proposed allowed domains probably due to incompatibility with its local configured domain or the domain ID list.","Check the configuration on the remote switch, and make sure that the proposed allowed domains include it. Also, make sure that the the proposed allowed domains include all the domains in the domain ID list."
"FCDOMAIN","3","MTSOPENTRX_FAILED","IPC failure (opening of a transaction failed)","Fcdomain was not able to open a transaction( HA Purposes.)","No action is required."
"FCDOMAIN","3","MTSRECV_FAILED","IPC failure (receiving of a message failed)","Fcdomain has not been able to receive a message from the Inter Process Communication (IPC) module.","Please perform fcdomain restart in the affected VSAN (non disruptive.)"
"FCDOMAIN","3","MTSRESP_FAILED","IPC failure replying to a request message (error [hex])","Fcdomain has not been able to reply to a request coming from the Inter Process Communication (IPC) module (error [hex]).","Please perform fcdomain restart in the affected VSAN (non disruptive)."
"FCDOMAIN","3","MTSSENDREQ_FAILED","IPC failure (sending of a request failed)","Fcdomain was not able to send a request using the Inter Process Communication module.","Please perform [fcdomain restart vsan <vsan-id>] in the affected VSAN (non disruptive.)"
"FCDOMAIN","3","MTSSEND_FAILED","IPC failure (sending of a message (syserr [hex], opc [dec], mtsq [dec], sap.node [hex], sap_addr [dec]) failed)","Fcdomain has not been able to send a message to the Message Transactional Service (MTS).","Please perform [fcdomain restart vsan <vsan-id>] in the affected VSAN (non disruptive)."
"FCDOMAIN","3","MTS_H_RECV_FAILED","IPC failure (receiving of a message failed)","Fcdomain has not been able to receive a message from the Inter Process Communication (IPC) module.","Please perform fcdomain restart in the affected VSAN (non disruptive.)"
"FCDOMAIN","3","NVRAMFAILURE","NVRAM open failed","Reading the last assigned runtime domain IDs from Non Volatile RAM (NVRAM) failed.","Fcdomain is able to continue without access to the Non Volatile RAM (NVRAM.)"
"FCDOMAIN","3","PORT_SUSPENDED","Response (Cmd Code [hex]) for SWILS [hex] intended for [chars] is received on [chars]","An FC2 response frame (Command Code [hex]) for SWILS [hex] that was intended for interface [chars] has been received on [chars] instead.","Check the configuration of both interfaces on the local switch and the interfaces on the other side of their corresponding links. In particular, check whether they should all belong to the same port-channel."
"FCDOMAIN","3","SDWRAPBIND_FAILED","Bind to debug server failed","Fcdomain feature has not been able to contact the debug service. Any problems occurring in the fcdomain feature will not be logged.","No action is required."
"FCDOMAIN","3","SDWRAPHISTINIT_FAILED","Initialization of history message list failed.","Fcdomain feature has not been able to contact the debug history service. Any problems occurring in the fcdomain feature will not be logged to this debug history.","No action is required."
"FCDOMAIN","3","VSAN_MERGE_DETECTED","Merge detected with VSAN [dec] (Common Fabric Name [chars])","The local VSAN and VSAN [dec] have the same principal switch [chars], hence are connected in the same logical fabric.","No action is required."
"FCDOMAIN","4","DM_ALLOWED_DM_LIST_MOD_ON_SUBORDINATE","Allowed domain list for vsan [dec] modified on subordinate switch with fcdomain distribution enabled","When distribution is enabled, it is recommended to modify the allow domain list on the principal switch only.","Abort the current session on the local switch and start a new one on the principal switch."
"FCDOMAIN","4","FABRICCONFSTARTRCF","Disruptive reconfiguration started","A disruptive reconfiguration (RCF phase) of the VSAN has started. This can happen when two or more fabrics merge disruptively, or when the user manually triggers a diruptive reconfiguration of the VSAN.","No action is required."
"FCDOMAIN","4","FC2_CORRUPTED","Received malformed FC2 [chars] frame","Fcdomain received a malformed FC2-SWILS frame.","No action is required."
"FCDOMAIN","4","FCID_PERSISTENT_TBL_ALMOST_FULL","FCID persistent table is almost full","Fcdomain has 80% or more of the FCID persistent table full with entries. Perform [show fcdomain fcid persistent vsan <vsan-id>] to view the entries currently in the table.","Purge stale entries [purge fcdomain fcid] to obtain more free entries."
"FCDOMAIN","5","DOMAIN_TYPE_IS_PREFERRED","The domain ID type is currently configured as preferred in all the existing VSANs","All the currently existing VSANs have the domain ID type configured as preferred. This means that with a low probability the domain ID of the local VSAN might change afer a reconfiguration. A reconfiguration can happen when two or more VSANs are merged or a principal link flaps. A principal link is either an upstream or a downstream link.","Type [fcdomain domain <dom-id> static vsan <vsan-id>] to configure as static the domain ID type in an existing VSAN."
"FCDOMAIN","5","FCIDP_DISABLED","FCID persistency feature is currently not enabled in any of the existing VSANs","All the currently existing VSANs have the FCID persistency feature disabled.","Type [fcdomain fcid persistent vsan <vsan-id>] to enable FCID persistency in an existing VSAN. Type [fcdomain fcid persistent global-enable] to automatically enable the FCID persistency feature on all newly created VSANs."
"FCDOMAIN","5","FCID_PERSISTENT_TBL_HALF_FULL","FCID persistent table is half full","Fcdomain has 50% of the FCID persistent table full with entries. Perform [show fcdomain fcid persistent vsan <vsan-id>] to view the entries currently in the table.","You may want to purge stale entries [purge fcdomain fcid] to obtain more free entries."
"FCDOMAIN","5","UNKNOWNDOMAININCFSDATAREQUEST","Received CFS Data request from unknown domain [dec].","A CFS Data request from the unknown domain [dec] has been received.","No action is required."
"FCDOMAIN","5","UNKNOWNDOMAININCFSLOCKREQUEST","Received CFS Lock request from unknown domain [dec].","A CFS Lock request from the unknown domain [dec] has been received.","No action is required."
"FCDOMAIN","5","UNKNOWNDOMAININCFSRELEASEREQUEST","Received CFS Release request from unknown domain [dec].","A CFS Release request from the unknown domain [dec] has been received.","No action is required."
"FCDOMAIN","5","UNKNOWNDOMAININUNKNOWNCFSREQUEST","Received CFS request from unknown domain [dec].","A CFS request from the unknown domain [dec] has been received.","No action is required."
"FCDOMAIN","6","BF_STARTED","BF started by [chars]","Build Fabric has been started in this VSAN","No action is required."
"FCDOMAIN","6","CANNOTFREESINGLEFCID","Impossible to free single FCIDs","Impossible to free single FCIDs.","No action is required."
"FCDOMAIN","6","CLEARLOCKNOTIFICATIONRECEIVED","Implict lock release.","Lock has been implicitly released due to a clear session operation.","No action is required."
"FCDOMAIN","6","DEVICEALREADYOWNSDIFFERENTFCIDS","The device already owns different FCIDs","Requested different FCIDs without any freeing in between.","No action is required."
"FCDOMAIN","6","DOMAINID_INVALID","Local domain ID invalid","The local domain ID is invalid.","No action is required."
"FCDOMAIN","6","DOMAINID_VALID","Local domain ID [dec] available","The domain ID [dec] is available.","No action is required."
"FCDOMAIN","6","DOWNSTREAM_SWITCHED","Downstream interface has been fast-switched from [chars] to [chars]","Because of a link failure the downstream interface has been fast-switched from [dec] to [dec].","No action is required."
"FCDOMAIN","6","EPORT_ALREADY_CREATED","Interface [chars] already created","Interface [chars] already created.","No action is required."
"FCDOMAIN","6","EPORT_ALREADY_DOWN","Interface [chars] is already down","Interface [chars] already down.","No action is required."
"FCDOMAIN","6","EPORT_CLEANUP","Interface [chars] received cleanup request","Fcdomain on interface [chars] has received a cleanup request.","No action is required."
"FCDOMAIN","6","EPORT_CREATED","Creation of interface [chars]","Fcdomain is going to create interface [chars].","No action is required."
"FCDOMAIN","6","EPORT_DOWN","Interface [chars] is down","Fcdomain is going to remove interface [chars] from its database.","No action is required."
"FCDOMAIN","6","FABRICCONFSTARTBF","Non disruptive reconfiguration started","A non disruptive reconfiguration (BF phase) of the VSAN has started. This can happen when two or more fabrics merge, or when the user manually triggers a non diruptive reconfiguration of the VSAN.","No action is required."
"FCDOMAIN","6","FABRICNAME_INVALID","Fabric name not available","Fabric name not available.","No action is required."
"FCDOMAIN","6","FABRICNAME_VALID","Fabric name [chars] available","Fabric name [chars] available.","No action is required."
"FCDOMAIN","6","FCIDALREADYFREE","FCIDs already free","FCIDs already free.","No action is required."
"FCDOMAIN","6","FCIDNOTSTORED","FCIDs not stored","FCIDs not stored.","No action is required."
"FCDOMAIN","6","FCIDP_ENABLED_DOM_TYPE_PREFERRED","FCID persistency is enabled, but the domain ID type is configured as preferred","The FCID persistency feature is enabled, but the domain ID type is configured as preferred. This means that with a low probability the domain ID of the local VSAN might change afer a reconfiguration. A reconfiguration can happen when two or more VSANs are merged or a principal link flaps. A principal link is either an upstream or a downstream link. Should the domain ID change, all the FCIDs associated with it would be invalidated.","Type [fcdomain domain <dom-id> static vsan <vsan-id>] to configure as static the domain ID type in an existing VSAN."
"FCDOMAIN","6","FCIDS_ASSIGNED","Assigned a sequence of 256 contiguous FCIDs starting from FCID [hex]:[hex]:[hex]","Assigned a sequence of 256 contiguous FCIDs starting from FCID [hex]:[hex]:[hex].","No action is required."
"FCDOMAIN","6","FCIDS_FREED","Freed a sequence of 256 contiguous FCIDs starting from FCID [hex]:[hex]:[hex]","Freed a sequence of 256 contiguous FCIDs starting from FCID [hex]:[hex]:[hex].","No action is required."
"FCDOMAIN","6","FCID_ASSIGNED","Assigned single FCID [hex]:[hex]:[hex]","Assigned single FCID [hex]:[hex]:[hex].","No action is required."
"FCDOMAIN","6","FCID_FREED","Freed single FCID [hex]:[hex]:[hex]","Freed single FCID [hex]:[hex]:[hex].","No action is required."
"FCDOMAIN","6","INCORRECTDOMAINRANGE","Requested FCIDs with domain field not in expected range","Requested FCIDs with domain field not in expected range.","No action is required."
"FCDOMAIN","6","INCORRECTDOMAIN","Requested FCIDs with domain field different from local domain","Requested FCIDs with domain field different from local domain.","No action is required."
"FCDOMAIN","6","INVALIDARG","Requested FCID of type 00.00.YY, but specifying an entire area","Requested FCID of type 00.00.YY, but specifying an entire area.","No action is required."
"FCDOMAIN","6","MY_SAME_WWN_DIFFERENT_DOMS_CONFLICTS","During VSAN merge detected local WWN [chars] is already in use by another switch (the two switches have different domain IDs: [dec] (local) and [dec])","It has been detected that the local switch has the same WWN [chars] of another switch, and that they have different domain IDs: [dec] (local) and [dec].","Check which switches have the same WWN and change either one."
"FCDOMAIN","6","NODOMAIN","Local domain not available","The local domain is not available yet.","No action is required."
"FCDOMAIN","6","NOFREEFCID","No free FCIDs","No free FCIDs.","No action is required."
"FCDOMAIN","6","NOTOWNER","Feature [dec] cannot free FCID [dec]:[dec]:[dec] (feature [dec] is the actual owner)","Feature UUID [dec] cannot free FCID [dec]:[dec]:[dec] because it is not its owner (UUID actual owner is [dec]).","No action is required."
"FCDOMAIN","6","OTHER_SIDE_VIRTUAL_IVR_DOMS_OVERLAPPING","During VSAN merge detected overlap with virtual IVR domain ID [dec] from across the link","It has been detected an overlap with the virtual IVR domain ID [dec] from across the link during an attempt to merge the local VSAN.","No action is required."
"FCDOMAIN","6","PSWSSTARTED","Principal Switch Selection started","Fcdomain started a principal switch selection phase to elect a principal switch in this VSAN.","No action is required."
"FCDOMAIN","6","RCF_STARTED","RCF started by [chars]","Reconfigure Fabric has been started in this VSAN","No action is required."
"FCDOMAIN","6","REQSINGLEFCIDWITHINRESERVEDRANGE","Requested single FCIDs in area [dec] within the reserved range","Requested single FCIDs in area [dec] within the reserved range.","No action is required."
"FCDOMAIN","6","REQUESTEDFCIDNOTFREE","Requested FCIDs not free","Requested FCIDs not free.","No action is required."
"FCDOMAIN","6","REQUESTEDFCIDRESERVED","Requested reserved FCIDs","Requested reserved FCIDs.","No action is required."
"FCDOMAIN","6","REQUESTEDRESERVEDFCIDMISMATCH","Requested persistent FCIDs, but there is a mismatch","Requested persistent FCIDs, but there is a mismatch.","No action is required."
"FCDOMAIN","6","SAME_WWNS_DIFFERENT_DOMS_CONFLICTS","During VSAN merge detected two switches with same WWN [chars] and different non-virtual domain IDs [dec] and [dec]","It has been detected that two switches have the same WWN [chars], but different non-virtual domain IDs: [dec] and [dec].","Check which switches have the same WWN and change either one."
"FCDOMAIN","6","TIMER_UNKNOWN","fcdomain has received a notification for an unknown timer expiration","A timer unknown to fcdomain has expired.","No action is required."
"FCDOMAIN","6","UPSTREAM_SWITCHED","Upstream interface has been fast-switched from [chars] to [chars]","Because of a link failure the upstream interface has been fast-switched from [dec] to [dec].","No action is required."
"FCDOMAIN","6","UUIDNOSPACEFOUND","No available space to store the identity of the requestor the FCIDs","No available space to store the identity of the requestor the FCIDs.","No action is required."
"FCDOMAIN","6","UUIDNOTFOUND","Universal Unique ID (UUID) not found","Universal Unique ID (UUID) not found.","No action is required."
"FCDOMAIN","6","VIRTUAL_IVR_DOMS_OVERLAPPING","During VSAN merge detected overlap with local virtual IVR domain ID [dec]","It has been detected an overlap with the local virtual IVR domain ID [dec] during an attempt to merge the local VSAN.","No action is required."
"FCDOMAIN","7","EPORT_ALREADY_ISOLATED","Interface [chars] is already isolated or down","Fcdomain was going to isolate interface [chars], but the interface is already isolated.","No action is required."
"FCDOMAIN","7","FABRICCONFCOMPLETEDBF","Non disruptive reconfiguration completed","A non disruptive reconfiguration (BF phase) completed. This can happen when two or more fabrics merged, or when the user manually triggered a non diruptive reconfiguration of the VSAN.","No action is required."
"FCDOMAIN","7","FABRICCONFCOMPLETEDRCF","Disruptive reconfiguration completed","A disruptive reconfiguration (RCF phase) of the VSAN has completed. This can happen when two or more fabrics merged disruptively, or when the user manually triggered a diruptive reconfiguration of the VSAN.","No action is required."
"FCDOMAIN","7","FC2_RETRY","Retransmission of FC2 frame on interface [chars] (Cmd Code: [hex])","Fcdomain is retrying an FC2 frame on interface [chars] due to loss/no response. The Command Code of the frame is [hex].","No action is required."
"FCDOMAIN","7","FCID_IN_USE_PURGING_FOR_FICON_MGR","FICON needs to purge the persistent FCID table, but at least one FCID is still in use, preventing this purge from completely remove all entries belonging to the VSAN.","There may be a problem in the sequence that shuts down all interfaces before fcdomain receives a request from FICON Manager to purge the persistent FCID table.","No action is required."
"FCDOMAIN","7","FSM_FAILED","FSM transition failed on interface [chars] (current state [chars])","Fcdomain state machine generated an invalid event on interface [chars], for which no proper action was defined (current state [chars].)","No action is required."
"FCDOMAIN","7","FSM_FORBIDDEN_TRANSITION","fcdomain state machine has hit a forbidden transition","Fcdomain state machine has tried to execute a forbidden transition.","No action is required."
"FCDOMAIN","7","INTERFACERDY","Interface [chars] ready","Interface [chars] is ready.","No action is required."
"FCDOMAIN","7","PREACTIONTYPE_UNKNOWN","fcdomain state machine has hit an unknown pre-action type","An undefined pre-action type has been used.","No action is required."
"FCDOMAIN","7","PSWSCOMPLETED","Principal Switch Selection completed","A Principal Switch Selection (PSwS phase) completed.","No action is required."
"FCDOMAIN","7","RDIACC","Assigned domain ID [dec], WWN of requestor [chars] (requested domain ID [dec])","Domain ID [dec] has been received by VSAN with WWN [chars] (requested domain ID was [dec].)","No action is required."
"FCD","7","SB3_ABTS_EXCHANGE","sb3 aborted exchange [hex] from vsan:[dec] ch:[hex] chi:[hex] ccw:[hex] token:[hex] cmd:[hex] reason:[chars] state:[chars]:[dec]","SB3 aborted exchange due to reason given. Aborts are caused by either the channel or control unit detecting a device protocol error. Recovery actions are performed to restore communication. In certain circumstances aborts occur in normal operations.","No action is required if communication with CUP device is still operational."
"FCD","7","SB3_UCS_PER_FILE_FN","VSAN:[dec] Unit Check for perform file function, reason: [chars]","SB3 failed perform file function. Failure is caused by error in the file main frame sent to director.","No action is required if communication with CUP device is still operational."
"FCFWD","3","ERROR","[chars]","Fcfwd encountered an error","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"FCFWD","4","WARNING","[chars]","Fcfwd is generating a relevant notification","No action is required."
"FCFWD","6","INFO","[chars]","An fcfwd event occurred","No action is required."
"FCNS","2","DB_FULL","the database; max entries [dec] exceeded","Name server database is full. The max number of entries, [dec], of ports is already present in the database","No action is required."
"FCNS","2","INIT_FAILURE",": [chars]","Fcns initialisation has failed due to [chars].","No action is required."
"FCNS","2","NO_RESPONSE","for query [chars] from domain [dec]","No response for query [chars] from domain [dec].","No action is required."
"FCNS","2","PSS_VERSION_MISMATCH",": for [chars]","Version mismatch for pss of type [chars].","No action is required."
"FCNS","2","RELOAD_FAILURE",": [chars]","Failed to reload information from PSS: [chars].","No action is required."
"FCNS","3","BAD_FRAME",": [chars]","Received a bad frame from the network: [chars].","No action is required."
"FCNS","3","CFG_FAILURE",": [chars]","A failure related to fcns configuration: [chars].","No action is required."
"FCNS","3","CHUNK_FAILURE",": [chars]","Chunk memory failure: [chars].","No action is required."
"FCNS","3","DB_FAILURE",": [chars]","A failure occured in fcns database: [chars].","No action is required."
"FCNS","3","MALLOC_FAILURE",": [chars]","Malloc failed: [chars].","No action is required."
"FCNS","3","MTS_FAILURE",": [chars] [chars]","Failure occured trying to do an MTS operation: [chars] [chars].","No action is required."
"FCNS","3","PSS_FAILURE",": [chars]","Pss failure: [chars].","No action is required."
"FCNS","4","QUERY_NO_RESPONSE","for query [chars] from domain [dec]","No response for query [chars] from domain [dec].","No action is required."
"FCNS","6","DB_INFO",": [chars] [hex]","Database modification:[chars] for entry [hex].","No action is required."
"FCNS","6","STATUS_INFO",": [chars]","A change in fcns status: [chars].","No action is required."
"FCOE_MGR","2","FCOE_MGR_MODULE_NOT_LICENSED","FCoE Manager Module:[dec] not licensed","FCOE_MGR Line Card not licensed","No action is required."
"FCOE_MGR","2","FCOE_MGR_PSS_RESTORE_FAILED","FCoE Manager PSS Restore operation failed, error: [chars]","FCoE Manager PSS Restore operation failed","No action is required."
"FCOE_MGR","5","FCOE_MGR_DISABLED","FCOE_MGR Disabled","FCOE_MGR Service Disabled","No action is required."
"FCOE_MGR","5","FCOE_MGR_ENABLED","FCOE_MGR Enabled","FCOE_MGR Service nabled","No action is required."
"FCOE_MGR","5","FCOE_MGR_INFO","[chars]","FCoE Manager general info","No action is required."
"FCOE_MGR","5","FCOE_MGR_MODULE_LICENSE_CHECKIN","FCoE Manager License Checkin:[dec]","FCOE_MGR Line Card license checked in","No action is required."
"FCOE_MGR","5","FCOE_MGR_MODULE_LICENSE_CHECKOUT","FCoE Manager License Checkout:[dec]","FCOE_MGR Line Card license checked out","No action is required."
"FCOE_MGR","5","FCOE_MGR_SOLICITATION_FROM_SAME_MAC","FCoE Manager received Mulicast Solication from same MAC: [chars]","FCoE Manager received Mulicast Solication from same MAC","No action is required."
"FCOE_MGR","5","FCOE_MGR_VE_DUPLICATE_PEER_MAC","FCoE Manager has already received unicast advertisement from MAC [chars] on a different VE link. Bringing down this link","FCoE Manager has already received unicast advertisement from same MAC on a different VE link","No action is required."
"FCOE","5","FCOE_DISABLED","FCOE Disabled","FCOE Service Disabled","No action is required."
"FCOE","5","FCOE_ENABLED","FCOE Enabled","FCOE Service Enabled","No action is required."
"FCSP-MGR","2","DBG_INIT_FAILED","Debug Infrastructure Initialization failed ( [chars] )","The system has detected an error.","No action is required."
"FCSP-MGR","2","FC2_E_INIT_FAILED","Fibre-Channel Initialization of an E_Port failed ( [chars] )","FC-SP Manager has been unable to initialize with the FC-2 E-Port infrastructure.","No action is required."
"FCSP-MGR","2","FC2_F_INIT_FAILED","Fibre-Channel Initialization of an F_Port failed ( [chars] )","FC-SP Manager has been unable to initialize with the FC-2 F-Port infrastructure.","No action is required."
"FCSP-MGR","2","FC2_UNKNOWN_FRM_RECD_CRIT","Received an unexpected/unknown FC-2 frame on [chars]","The system has detected an error.","No action is required."
"FCSP-MGR","2","FCSP_AUTHENT_FAILURE","FC-SP Authentication failure on Port [chars] (FC-SP Failure Reason: [chars] [chars])","Fibre-Channel Authentication failure on Port [chars].(Reason Code [chars] Detail [chars]). Please check password configurations and ensure appropriate security modes on this port as well as peer port","No action is required."
"FCSP-MGR","2","FCSP_ESP_MISMATCH","ESP parameters mismatch failure on Port [chars] (reason:[chars])","Fibre-Channel ESP parameters mismatch with the peer on Port [chars].(Reason: [chars]). Please check ESP configurations on both side of the link and ensure appropriate ESP mode on this port as well as peer port","No action is required."
"FCSP-MGR","2","FSMU_INIT_FAILED","State Machine Infrastructure Initialization failed ( [chars] )","The system has detected an error.","No action is required."
"FCSP-MGR","2","IPC_INIT_FAILED","IPC (Inter Process Communication) Initialization failed ( [chars] )","FC-SP Manager has been unable to initialize with the IPC infrastructure.","No action is required."
"FCSP-MGR","2","LICENSE_UNAVAILABLE","License:[chars] unavailable, service exiting","License of [chars] is unavailable. Service will exit now","Please install the license file to continue using the feature."
"FCSP-MGR","2","MEM_FAILED","Memory operations failed File: [chars] Line [dec] for size [hex] bytes","The system has detected an error.","No action is required."
"FCSP-MGR","2","POST_INIT_FAILED","Post-Initialization failed ( [chars] )","The system has detected an error.","No action is required."
"FCSP-MGR","2","PSS_INIT_FAILED","PSS Infrastructure Initialization failed ( [chars] )","The system has detected an error.","No action is required."
"FCS","2","ALLOC_FAILED","Memory allocation failed for size:[dec]","Memory allocation failed for size [dec]","Restart the process"
"FCS","2","CHUNK_ALLOC_FAILED","Chunk memory allocation failed for [chars] chunk","Chunk memory allocation failed. [chars] indicates the chunk name","Restart the process"
"FCS","2","NO_RESPONSE","Retried maximum number of times for [chars] to domain [dec] in VSAN [dec]","Maximum number of retires completed for [chars] form domain [dec] in VSAN [dec].","No action is required."
"FCS","2","PSS_VER_FAIL","PSS file [chars] has version [dec].[dec].[dec], expected version [dec].[dec].[dec]","There was a mismatch in the PSS version. [chars] indicates the PSS service, [dec].[dec].[dec] its current version number and [dec].[dec].[dec] the expected version","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"FCS","2","RANDNUM_FAIL","[chars]","There was a critical error during random number generation. [chars] indicates details of the error","No action is required."
"FCS","3","DB_ERR","[chars]","An error occurred during an FCS database operation. [chars] indicates the reason for the error","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"FCS","3","INIT_FAIL","[chars]","An error happened during FCS Initialization. [chars] indicates the reason for failure","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"FCS","3","MTS_API_ERR","[chars] : [chars]","An error occurred in send or receive of an MTS message. [chars] indicates the error that occurred and [chars] indicates the error number","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"FCS","3","MTS_ERR","[chars]","An error occurred in processing of an MTS message. [chars] indicates the error that occurred","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"FCS","3","NO_MTS_RESP","[chars]","There was no response to an MTS request. [chars] indicates details of the MTS message","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"FCS","3","NO_REMOTE_RESP","No response for request [chars] from domain [dec] in VSAN [dec]","There was no response to an FC2 request. [chars] indicates FCS request [dec] indicates the remote domain and [dec] the VSAN ID","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"FCS","3","OTHER_ERR","[chars]","An FCS generic error occurred. [chars] indicates the description of the error","No action is required."
"FCS","3","PSS_ERR","[chars]","An error occurred during an FCS PSS operation. [chars] indicates the PSS operation that caused the error","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"FCS","3","SOCK_ERR","sd: [dec], [chars]","An FC-2 Socket error occurred on socket-ID [dec]. [chars] indicates the reason for failure","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"FCS","5","API_FAIL","[chars]: [chars]","An API called by FCS failed. [chars] indicates the API name failed and [chars] the reason for failure","If this message is seen during a cold boot, it means that the queried module came up after FCS and this case can be ignored"
"FCS","5","DB_NOTICE","[chars]","An error occurred during an FCS database operation. [chars] indicates the reason for the error","No action is required."
"FCS","6","BAD_CT_FRAME","Invalid FCS frame: [chars] received from [hex]","An invalid FCS FC-CT frame with [chars] received from FC-ID [hex].","No action is required."
"FCS","6","INFORMATION","[chars]","An event happend that affects FCS. [chars] indicates the event","No action is required."
"FCS","6","REXMIT_PKT","Retransmitting request [chars] to domain [dec] in VSAN [dec]","There was a retransmission of an FC2 request. [chars] indicates FCS request [dec] indicates the remote domain and [dec] the VSAN ID","No action is required."
"FDMI","2","FDMI_INIT_FAILED","FDMI initialization failed : [chars]","Fdmi process encountered error while starting","No action is required."
"FDMI","2","MTS_ERROR","MTS message transmission failed with error [dec]","Fdmi process unsuccessfully tried to send a MTS message. MTS errro number is specified in [dec]","No action is required."
"FDMI","2","PSS_CFG_RESTORE_ERROR","Configuration restoration for [chars] failed with error [hex] for key type [dec]","Fdmi read the saved configuration and encountered an error while rebuilding the runtime configuration. [chars] describes the configuration which the process tried to restore and 0x[hex] is the system err code","No action is required."
"FDMI","2","PSS_RTDB_RESTORE_ERROR","Runtime database restoration for [chars] failed with error [hex]","Fdmi read the saved runtime database and encountered an error while rebuilding the runtime database. [chars] describes the runtime database which the process tried to restore and 0x[hex] is the system err code","No action is required."
"FDMI","3","BAD_FRAME","Malformed frame received: [chars]","Fdmi process received malformed frame. [chars] describes the malformation","No action is required."
"FDMI","3","BAD_RESPONSE","response with command code: [hex]","Fdmi process received bad payload in response","No action is required."
"FDMI","3","INTERNAL_ERROR","Internal err: [chars]","Fdmi process encountered a general error, one that does not fall in any of the categories. [chars] describes the error and its context.","No action is required."
"FDMI","3","MTS_API_ERROR","API, [chars] returned [hex]","Fdmi invoked API [chars], received the error code specified in 0x[hex]","No action is required."
"FDMI","3","MTS_FORMAT_ERROR","Unknown MTS message format in opcode [dec] from module [chars]","Fdmi received message from module [chars] which contains unknown message format. MTS opcode is specified in [dec]","No action is required."
"FDMI","3","NO_RESPONSE","No response from switch whose domain id is [dec]","Fdmi process sents a inter-switch packets to switches and has not received the response","No action is required."
"FDMI","3","PSS_ERROR","PSS operation [chars] returned err: [hex]","[chars] specifies the context where the failure occured and 0x[hex] specifies the err","No action is required."
"FDMI","3","UNEXPECTED_MTS_MSG","Unexpected MTS message, opcode [dec], is received","Fdmi process received unexpected MTS event. MTS opcode is specified in [dec]","No action is required."
"FDMI","4","SW_REJ_RESPONSE","Reject response [chars] from switch whose domain id is [dec]","Fdmi process sents a inter-switch packets to switches and has received the reject response with reason code in [chars]","No action is required."
"FDMI","6","DEBUG_INFO","[chars]","Fdmi process debug info","No action is required."
"FEATURE-MGR","2","FM_AUTOCKPT_FAILED","AutoCheckpoint [chars] failed to be created for reason: [chars] ([hex])","AutoCheckpoint with the given name has been created successfully","No action is required."
"FEATURE-MGR","2","FM_FEATURE_LICENSE_ERROR","the license operation for feature failed [hex] [chars]","License operation was not successful, check license validity for the feature","Please contact FM team"
"FEATURE-MGR","2","FM_FEATURE_LICENSE_ERROR","license [chars] checkout failure for [chars], error [hex] ([chars])","License operation was not successful, check license validity for the feature","Please contact FM team"
"FEATURE-MGR","2","FM_FEATURE_OP_TIMEOUT_ERROR","feature [chars] operation failed on response timeout from service: [chars] with uuid ([hex])","The error seen at FM and service communication","Please contact service owner with given uuid and FM team"
"FEATURE-MGR","2","FM_FSET_ADD_CONFCHECK_ERROR","failed to add confcheck [hex] ([chars]) at installing feature-set [chars]","Failed to add confcheck at enabling feature-set","Please contact FM/sysmgr team"
"FEATURE-MGR","2","FM_FSET_CFG_ALLOW_ERROR","Potential vdc_mgr issue: the allow request failed [hex] ([chars])","Vdc_mgr failed to response the allow request","Please contact FM/vdc_mgr team"
"FEATURE-MGR","2","FM_FSET_CKPT_ERROR","Checkpoint issue: failed on checkpoint with error [hex] ([chars]) at feature-set [chars]","Checkpoint did not response","Please contact FM/vdc_mgr and rollback team"
"FEATURE-MGR","2","FM_FSET_DISABLE_ERROR","Potential sysmgr issue: disable feature-set [chars] on sup failed with error [hex] ([chars])","Some issues while disabling feature-set","Please contact FM/sysmgr team"
"FEATURE-MGR","2","FM_FSET_DISABLE_FEATURES_ERROR","features failed to disable at feature-set [chars] with error [hex] ([chars])","Failed to disable feature at disabling feature-set","Please contact FM/sysmgr team"
"FEATURE-MGR","2","FM_FSET_DISABLE_FEATURES_TIMEOUT","Potential [chars] issue: feature [chars] did not complete its disabling","Failed to disable feature at disabling feature-set","Please contact FM/sysmgr team and the feature owner"
"FEATURE-MGR","2","FM_FSET_INSTALL_ERROR","install feature-set [chars] returns error 0X[hex] ([chars])","Somes issues during install feature-set","Please contact FM/sysmgr team"
"FEATURE-MGR","2","FM_FSET_LCS_DISABLE_ERROR","Potential sysmgr issue: disable feature-set [chars] failed on module [dec] with error [hex] ([chars])","Some issues on the lc while disabling feature-set","Please contact FM/sysmgr team"
"FEATURE-MGR","2","FM_FSET_LCS_ENABLE_ERROR","enabling feature-set [chars] on module [dec] returns error 0X[hex] ([chars])","Somes issue on the lc while enabling feature-set","Please contact FM/sysmgr team"
"FEATURE-MGR","2","FM_FSET_PRESEQ_REJECT","It rejects pre-sequence due to a service with sap [dec]: [chars]","The message seen when an application rejects feature-set disable request","Please contact FM/sysmgr team"
"FEATURE-MGR","2","FM_FSET_SUP_ENABLE_ERROR","enabling feature-set [chars] on sup returns error 0X[hex] ([chars])","Some issues during enabling feature-set","Please contact FM/sysmgr team"
"FEATURE-MGR","2","FM_FSET_UNGRACEFUL_DISABLE_ERROR","Potential sysmgr issue: ungraceful disable feature-set [chars] failed with error [hex] ([chars])","Some issues while ungraceful disable feature-set","Please contact FM/sysmgr team"
"FEATURE-MGR","2","FM_FSET_UNGRACEFUL_UNINSTALL_ERROR","Potential sysmgr issue: ungraceful uninstall feature-set [chars] failed with error [hex] ([chars])","Some issues while ungraceful uninstall feature-set","Please contact FM/sysmgr team"
"FEATURE-MGR","2","FM_FSET_UNINSTALL_ERROR","Potential sysmgr issue: uninstall feature-set [chars] failed with error [hex] ([chars])","Some issues while uninstall feature-set","Please contact FM/sysmgr team"
"FEATURE-MGR","2","FM_FSET_VMM_OP_ERROR","[chars]","The error seen at FM and VMM interaction","Please contact FM/VMM team"
"FEATURE-MGR","2","MODULE_FM_DONE","feature manager completed","Feature manager completed","No action is required."
"FEATURE-MGR","2","MODULE_FM_STARTED","feature manager started","Feature manager started","No action is required."
"FEATURE-MGR","6","FM_AUTOCKPT_IN_PROGRESS","AutoCheckpoint [chars]screationinprogress...'","AutoCheckpoint creation has been requested and it should be in progress","No action is required."
"FEATURE-MGR","6","FM_AUTOCKPT_SUCCEEDED","AutoCheckpoint [chars] created successfully","AutoCheckpoint with the given name has been created successfully","No action is required."
"FEATURE-MGR","6","FM_FCOE_AUTOINSTALL_ON_NOT_ISOLA","auto-install feature-set fcoe on non-isola","Auto-install feature-set fcoe could be done on isola only","Please contact FM team"
"FEATURE-MGR","6","FM_FSET_ENABLED_AT_UNINSTALL","Uninstall aborted because feature set is still enabled in vdc [dec]","Feature set is in enabled state","No action is required."
"FEX","2","FEX_NOT_ONLINE_SUP_ISSU","FEX [dec] did not come online after SUP ISSU","FEX did not come online after sup ISSU","No action is required."
"FEX","2","FEX_OFFLINE","FEX [dec] has gone OFFLINE","FEX has gone OFFLINE","No action is required."
"FEX","2","FEX_ONLINE","FEX [dec] has come ONLINE","FEX has come ONLINE","No action is required."
"FEX","2","FEX_PORT_STATUS_CRIT","Uplink-ID [dec] of Fex [dec] that is connected with [chars] changed its status from [chars] to [chars]","Fex [decimal-digit] changed port status","No action is required."
"FEX","2","NOHMS_ENV_FEX_OFFLINE","[chars]","Fex off-line","Show inventory"
"FEX","2","NOHMS_ENV_FEX_ONLINE","[chars]","Fex on-line","Show inventory"
"FEX","4","FEX_SCALING_LIMITS_REACHED","You have exceeded the advisable FEX scaling limits.","More FEX/FEX ports in the system than recommended by Cisco.","No action is required."
"FEX","5","FEX_DISABLED","FEX Disabled","FEX Service Disabled","No action is required."
"FEX","5","FEX_ENABLED","FEX Enabled","FEX Service Enabled","No action is required."
"FEX","5","FEX_PORT_STATUS_NOTI","Uplink-ID [dec] of Fex [dec] that is connected with [chars] changed its status from [chars] to [chars]","Fex [decimal-digit] changed port status","No action is required."
"FEX","5","PINNING_CHANGED","Fex [dec] pinning information is changed","Fex pinning information changed","No action is required."
"FEX","5","SATMGR_DISABLE_FAILED","Disabling of feature FEX failed. Please remove FEX related configs from interfaces","Disabling of FEX feature failed","No action is required."
"FIB-SLOT#","0","EMERG","[chars]","Fib caused a system failure","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"FIB-SLOT#","1","ALERT","[chars]","Fib caused failures in other services","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"FIB-SLOT#","1","HW_RESOURCE","[chars]","Hardware resources are approaching limit.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"FIB-SLOT#","2","CRIT","[chars]","Fib encountered a catastrophic error","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"FIB-SLOT#","2","FIB_TCAM_HA_ERROR","FIB recovery errors, please capture showtechforwardingl3unicast'and'showtechforwardingl3multicast''","FIB had some HA recovery failures for certain prefixes/labels.","No action is required."
"FIB-SLOT#","2","FIB_TCAM_RESOURCE_EXHAUSTION","FIB TCAM exhausted for [chars]","The TCAM device in the L3 forwarding ASIC has reached its system limits.","No action is required."
"FIB-SLOT#","3","ERR","[chars]","Fib encountered an error","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"FIB-SLOT#","3","FIB_URPF_RESOURCE_EXHAUSTION","uRPF memory exhausted - Failed to add uRPF interface(s)","The URPF memory in the L3 forwarding ASIC has reached its system limits.","No action is required."
"FIB-SLOT#","3","HW_FAIL","[chars]","Failed to program route into the hardware.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"FIB-SLOT#","3","NO_MEM","Out of memory","Fib does not have enough memory to continue proper operation.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"FIB-SLOT#","3","SEND_SUP","Cannot talk to supervisor","Fib to supervisor IPC failure","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"FIB-SLOT#","4","CPU_HOG","Inactive or busy","Either fib was not scheduled to run, or fib was busy, and fib did not service the message or timer queue for an extended period.","Please perform debugfiberror',thenrecreatetheoperationscenario,tofindoutmoredetails.'"
"FIB-SLOT#","4","FIB_ADJ_UTIL_WARNING","Adjacency memomry utilization is at [dec] percent","Adjacency memory utilization has is above its threshold","No action is required."
"FIB-SLOT#","4","FIB_TCAM_ADJ_EXHAUSTED","Adjacency allocation failed for [chars]","Failed to allocate an adjacency. Adjacency memory could have been exhausted","No action is required."
"FIB-SLOT#","4","FIB_TCAM_AF_INSERT_FAIL","FIB TCAM prefix insertion fail for [chars]","The TCAM device in the L3 forwarding ASIC failed to install prefix. Utilization above threshold.","No action is required."
"FIB-SLOT#","4","FIB_TCAM_PF_INSERT_FAIL","FIB TCAM prefix insertion fail for [chars]","The TCAM device in the L3 forwarding ASIC failed to install prefix. Utilization below threshold.","No action is required."
"FIB-SLOT#","4","FIB_TCAM_RESOURCE_EXCEP_CLRD","FIB TCAM resource usage exception cleared for [chars] [chars]","The TCAM device in the L3 forwarding ASIC is within system limits.","No action is required."
"FIB-SLOT#","4","FIB_TCAM_RESOURCE_WARNING","FIB TCAM usage is at 90 percent for [chars]","The TCAM device in the L3 forwarding ASIC is reaching its system limits.","No action is required."
"FIB-SLOT#","4","WARN","[chars]","Fib encountered a possible error","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"FIB-SLOT#","6","FIB_INFO","[chars]","Information that a corrective action was taken by FIB","Message is informational only"
"FICON","2","E_DUPLICATE_PN_BRINGUP_FAIL","[chars]","This port has the same port number assigned to other port in the same FICON VSAN. No more than one port with duplicate port number can be up in each FICON VSAN","Avoid duplicate number assignment in each FICON VSAN"
"FICON","2","E_PN_PA_NOT_IN_BOUND","[chars]","Port number or port address in startup-configure is out of bound.","Change ficon port number assign configuration and save to startup-configure."
"FICON","2","E_SAVE_FILE","[chars]","Failed to save file. Possibly due to asymmetric pdcm matrix. Look for retval for actual reason.","Configure port prohibits in symmetrically."
"FICON","2","SHUTDOWN","FICON Manager process shutting down: [chars]","FICON Manager shutting down","This is a severe error. Provide the reason given in the message."
"FICON","3","E_ASSIGN_BINDING_PN_FAIL","[chars]","Port number has fcip or port channle binding can not be removed nor changed.","Remove port number binding of the logical interface first."
"FICON","3","E_ASSIGN_INVALID_PN_PARAM","[chars]","Invalid port number parameters in command.","Check port numbers in the command.\n"
"FICON","3","E_ASSIGN_OVERLAP_PN_FAIL","[chars]","Port number assigned to physical and logical can not overlap.","Check port numbers in the command.\n"
"FICON","3","E_ASSIGN_PN_NOT_DOWN_FAIL","[chars]","Only port number assigned to a port in down state can be removed or changed.","Bring down the port first.\n"
"FICON","3","E_ASSIGN_PROHIBIT_PN_FAIL","[chars]","Logical port address can not be prohibited.","Check port numbers in the command.\n"
"FICON","3","E_DUPLICATE_PN_ASSIGN_WARNING","[chars]","This port has the same port number assigned to other port in the same FICON VSAN. No more than one port should have the same port number in each FICON VSAN","Avoid duplicate number assignment in each FICON VSAN\n"
"FICON","3","E_INVALID_PA_BRINGUP_FAIL","[chars]","This port either has an invalid port address assigned or has no port address assigned.","Assign a valid ficon port number to the port.\n"
"FICON","3","E_PORT_PROHIBIT_BRINGUP_FAIL","[chars]","This port has been prohibited. Prohibiting E or TE ports is not allowed. This port can not be configured in E mode or TE mode until the prohibit mask configuration is changed","Correct the prohibit mask (PDCM) for this port if you wish to bring it up as an E or TE port in a FICON VSAN\n"
"FICON","3","E_UNASSIGN_NO_PN_FAIL","[chars]","Only port number already assigned can be removed.","Check port numbers in the command.\n"
"FICON","3","PDCM_CHANGE_REJ_E_PORT","[chars]","The FICON Prohibit Dynamic Connectivity Mask(PDCM) change rejected because an E or TE port is being prohibited. Prohibiting an E or TE port in not allowed","Correct the prohibit mask (PDCM) for this port if you wish to bring the port up as an E or TE port in a FICON VSAN."
"FICON","5","STARTING","FICON Manager process starting","FICON Manager process is being started","No action is required."
"FICON","6","PDCM_CHANGE","VSAN [dec] port-address [dec] prohibit mask set to [chars]","The FICON Prohibit Dynamic Connectivity Mask (PDCM) for this port has changed. VSAN [dec], port address [dec] prohibit mask (PDCM) is now set to [chars]","No action is required."
"FICON","6","PORT_SWAP","port number [dec] [dec] swapped","FICON portnumbers swapped","No action is required."
"FICON","6","VSAN_DISABLED","FICON disabled on VSAN [dec]","FICON has been disabled on the given VSAN","No action is required."
"FICON","6","VSAN_ENABLED","FICON enabled on VSAN [dec]","FICON has been enabled on the given VSAN","No action is required."
"FIPSM","5","SPLITTER_DISABLED","SPLITTER Disabled","SPLITTER Service Disabled","No action is required."
"FIPSM","5","SPLITTER_ENABLED","SPLITTER Enabled","SPLITTER Service nabled","No action is required."
"FIPS","0","FIPS_POST_CLEANUP_FAILED","Error cleaning up keys in FIPS mode : [chars]","FIPS cleanup failed [chars]","No action is required."
"FIPS","0","SET_FIPS_MODE_FAILED","Error when setting FIPS mode : [chars]","FIPS mode failed [chars]","No action is required."
"FIPS","6","SET_FIPS_MODE","FIPS mode is [chars] for service [chars]","FIPS mode is changed [chars] [chars]","No action is required."
"FLN_EM","6","FLN_EM_DEBUG_MSG","[chars]","Debug log message","No action is required."
"FLN_FCP","6","FLN_FCP_DEBUG_MSG","[chars]","Debug log message","No action is required."
"FLN_FCP-SLOT#","2","FLN_FIB_TCAM_RESOURCE_EXHAUSTION","FIB TCAM exhausted for [chars] on instance [dec]","The TCAM device in the L3 forwarding ASIC has reached its system limits.No action is required.FLN_FCP-SLOT#-3Error Message    FLN_FCP-SLOT#-3-FLN_FIB_URPF_RESOURCE_EXHAUSTION: uRPF memory exhausted - Failed to add uRPF interface(s) on instance [dec] Explanation    The URPF memory in the L3 forwarding ASIC has reached its system limits.","No action is required."
"FLN_FCP-SLOT#","4","FLN_FIB_ADJ_EXHAUSTED","Adjacency allocation failed on instance [dec]","Failed to allocate an adjacency. Adjacency memory could have been exhausted","No action is required."
"FLN_FCP-SLOT#","4","FLN_FIB_LSMET_EXHAUSTED","ls-met entry allocation from [chars] failed on instance [dec]","Failed to allocate a ls-met entry. LS-MET table region for this entry could have been exhausted","No action is required."
"FLN_FCP-SLOT#","4","FLN_FIB_MCASTMET_EXHAUSTED","Met entry allocation from [chars] failed on instance [dec]","Failed to allocate a multicast met entry. Met table region for this entry could have been exhausted","No action is required."
"FLN_FCP-SLOT#","4","FLN_FIB_MCAST_OIFLIST_INSERT_FAIL","oiflist insertion failed [chars]","L3 oiflist insertion failed becuase Max supported l3 oiflist size is 4k","No action is required."
"FLN_FCP-SLOT#","4","FLN_FIB_MDT_EXHAUSTED","mdt entry allocation from [chars] failed on instance [dec]","Failed to allocate a mdt entry. Mdt table region for this entry could have been exhausted","No action is required."
"FLN_FCP-SLOT#","4","FLN_FIB_TCAM_AF_INSERT_FAIL","FIB TCAM prefix insertion failed for [chars] on instance [dec]","The TCAM device in the L3 forwarding ASIC failed to install prefix. Utilization above threshold.","No action is required."
"FLN_FCP-SLOT#","4","FLN_FIB_TCAM_PF_INSERT_FAIL","FIB TCAM prefix insertion failed for [chars] on instance [dec]","The TCAM device in the L3 forwarding ASIC failed to install prefix. Utilization below threshold.","No action is required."
"FLN_FCP-SLOT#","4","FLN_FIB_TCAM_RESOURCE_EXCEP_CLRD","FIB TCAM resource usage exception cleared for [chars] on instance [dec]","The TCAM device in the L3 forwarding ASIC is within system limits.","No action is required."
"FLN_FCP-SLOT#","4","FLN_FIB_TCAM_RESOURCE_WARNING","FIB TCAM usage is at [dec] percent for [chars] on instance [dec]","The TCAM device in the L3 forwarding ASIC is reaching its system limits.","No action is required."
"FLN_FWD_USD","2","CRIT_MSG","[chars]","Critical log message","No action is required."
"FLN_FWD_USD","6","FLN_FWD_DEBUG_MSG","[chars]","Debug log message","No action is required."
"FLN_L3","6","FLN_L3_DEBUG_MSG","[chars]","Debug log message","No action is required."
"FLN_QUE","6","FLN_QUE_DEBUG_MSG","[chars]","Debug log message","No action is required."
"FLN_XBAR","2","FLN_XBAR_FR_CRC","[chars]","Flanker received packets with CRC error from fabric","No action is required."
"FLN_XBAR","6","FLN_XBAR_DEBUG_MSG","[chars]","Debug log message","No action is required."
"FLOGI","1","MSG_FDISC_REJECT_TOO_MANY_LOGINS","[VSAN [dec], Interface [chars]] FDISC rejected - this interface has reached the max num of N-Ports ([dec])","An FDISC was rejected because the F-Port has reached the maximum allowed number of devices.","Check the configuration of the NPIV device connected to the port."
"FLOGI","1","MSG_FLOGI_REJECT_FCID_ERROR","[VSAN [dec], Interface [chars]] FLOGI rejected - FCID allocation failed.","An FLOGI was rejected because the FCID allocation failed.","Check the fcid-interop configuration, purge the persistency table and check the output of show flogi database details and see if any of the A area FCID allocation entries can be turned to single fcid allocation as per Configuration Guide"
"FLOGI","1","MSG_FLOGI_REJECT_TOO_MANY_LOGINS","[VSAN [dec], Interface [chars]] FLOGI rejected - this interface has reached the max num of NL-Ports ([dec])","An FLOGI was rejected because the FL-Port has reached the maximum allowed number of devices.","Reduce the number of devices on the loop"
"FLOGI","1","MSG_NPIV_NOT_SUPPORTED_WITH_TRUNKING","[VSAN [dec], Interface [chars]] NPIV not supported - on this platform, NPIV is not supported on trunking interfaces","The N_Port requested NPIV, but this platform does not support NPIV on trunking F_Ports.","Disable NPIV, or move the N_Port to a switch that supports NPIV on trunking F_Ports"
"FLOGI","2","MSG_FLOGI_REJECT_NO_ACL_TCAM_AVAILABLE","[VSAN [dec], Interface [chars]] FLOGI rejected - ACLTCAM resource exausted","An FLOGI was rejected because the ACLTCAM hardware resource is completely used.","Reduce the number of nodes."
"FLOGI","4","MSG_VF_FLOGI_FROM_NON_CISCO_OUI","[VSAN [dec], Interface [chars]] FLOGI with VF bit set from OUI [hex]:[hex]:[hex] (nwwn: [chars])","This interface received an FLOGI with VF bit set from a non CISCO OUI; in this release Virtual Fabrics are not supported on interfaces connected to third-party devices","Set the trunk mode of this interface to off"
"FLOGI","5","MSG_FLOGI_DROP_DUE_TO_SUSPENDED_VSAN","[VSAN [dec], Interface [chars]] FLOGI (pwwn: [chars]) has been dropped because the VSAN is suspended on this trunking interface","The switch received an FLOGI from a trunking interface on a VSAN which has been suspended; the FLOGI frame has been dropped.","To bring up the VSAN again on the trunking port, remove it from the allowed VSAN list and add it again"
"FLOGI","5","MSG_FLOGI_DUPLICATE_WWPN","[VSAN [dec], Interface [chars]] FLOGI (pwwn: [chars]) has been dropped because the host has a duplicate WWPN","The switch received an FLOGI from the interface, which has a duplicate PWWN value.","No action is required."
"FLOGI","5","MSG_IF_REINIT_ALPA_CONFLICT","[VSAN [dec], Interface [chars]] FL/TL interface [chars] re-initialized as ALPA - PWWN map conflict occurred.","The FL/TL interface is re-initialized as ALPA used by device conflicts with an existing FLOGI session after the Loop Initialization Protocol (LIP). All the devices will re-login with new ALPA and PWWN mapping","No action is required."
"FLOGI","5","MSG_PORT_LOGGED_IN","[VSAN [dec], Interface [chars]] Nx Port [chars] with FCID [chars] logged IN.","Nx port logged in with the specified information.","No action is required."
"FLOGI","5","MSG_PORT_LOGGED_OUT","[VSAN [dec], Interface [chars]] Nx Port [chars] logged OUT.","Nx port logged out. The following commands will help determine why this Nx port logged out: 'show interface, show VSAN, show module'","No action is required."
"FS-DAEMON","2","FSD_ENOSPC_BOOTFLASH","Due to insufficient space, [chars] image could not be copied to standby bootflash. [chars] image is not present on standby. Please copy \[chars]\'manually.'","Move system images from RAM to bootflash to free up some memory","Please remove some unnecessary files on bootflash using \delete\'CLIcommandandcopyimagesfromactivesupervisororfromremotelocation'"
"FS-DAEMON","6","FSD_ENOSPC_LOGFLASH","System logflash usage has reached [dec]%. You may delete some old files on logflash to free up space","System logflash space is almost full","Use 'clear core archived' or 'delete' CLI to free up space on logflash"
"FS-DAEMON","6","FSD_ENOSPC_ROOT","System root usage has reached [dec]%. You may delete some old files from root or /var/log to free up space","System root space is almost full","Use 'clear core archived' or 'delete' CLI to free up space on root dir or /var/log"
"FS-DAEMON","6","FSD_ENOSPC_TMP","System temporary directory usage has reached [dec]%.","System /tmp space usage.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"FS-DAEMON","6","FSD_REEXPORT_NFS","Re-exported NFS mounts","Exported NFS mounts are not visible in kernel and had to be reexported","Please use showsysteminternalflash'tomakesuretherearenoStaleNFShandles'"
"FSCM","2","FABRIC_START_CFG_MGR_PROGRAM_EXIT","Fabric Start Cfg Mgr daemon exiting: [chars]","FABRIC_START_CFG_MGR daemon is exiting.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"FSPF","2","SHUTDOWN","Routing daemon shutting down : [chars]","FSPF routing daemon is shutting down because of [chars] reason.","This is a severe bug. Provide the reason provided and the log files for FSPF."
"FSPF","3","BAD_FC2_PKT","Received bad FC2 packet on interface [chars] : [chars]","FSPF received a bad FC2 packet on [chars] interface , error description is [chars].","FSPF daemon has received a bad FC frame. Provide the output of 'debug fc2 pkt '."
"FSPF","3","CHECKSUM_FAIL","Checksum test failed for LSR domain [dec]","Periodic database checksum test failed for LSR for domain [dec]","This indicates that the internal database got corrupted because of some memory corruption bug. Provide output of 'show fspf database '. May need to power cycle the switch"
"FSPF","3","FC2_PROC_ERR","Error in processing [chars] packet on interface [chars], Error = [chars]","An error occurred in processing a [chars] FC2 packet on [chars] interface. The internal error code is [chars].","Turn on 'debug fspf error' to get more information. Make sure there is no misconfiguration of FSPF parameters on the two ends of the interface. Provide output of 'show fspf vsan x' 'show fspf vsan x interface' and 'debug fspf fc pkt ' for the specific interface"
"FSPF","3","FLOOD_ERR","Error in flooding the local LSR , Error = [chars]","FSPF had an error in flooding the local LSR , error description is [chars].","Provide output of 'debug fspf flood' , 'debug fspf error'. If error is reported in transmitting packet check if interface is up and turn on 'debug fc2 error'"
"FSPF","3","HELLO_MISMATCH","Mismatch in [chars] in the Hello packet on interface [chars]","There is a mismatch in the [chars] entry in the hello packet received on interface [chars]. The packet will be dropped.","Check the configuration of hello or dead interval on the switches on the two ends of the interface to see if there is a mismatch."
"FSPF","3","INTF_TIMER_ERR","Error in processing interface timer event [chars] for interface [chars] , error = [chars]","FSPF had an error in processing timer event for interface chars, error is [chars].","Provide output of 'debug fspf error'"
"FSPF","3","IPC_PROC_ERR","Error in processing IPC message : Opcode = [dec], Error code = [hex]","FSPF had an error in processing message of [dec] opcode , the internal error code is [dec].","Possibly some wrong IPC message is received by FSPF . Provide output of 'debug fspf mts pkt' and 'debug fspf error ' trace."
"FSPF","3","LOCK_FAIL","FSPF failure in gaining lock","There is a software failure in gaining lock of the shared resource between FSPF threads.","Provide output of 'debug fspf all '"
"FSPF","3","MTS_MSG_BEFORE_GSYNC","FSPF in standby received MTS message opcode = [hex] before GSYNC","FSPF in standby received an MTS message of opcode [dec] before receiving the GSYNC message.","Provide output of 'debug fspf mts pkt '"
"FSPF","3","RIB_ERR","Error in RIB : [chars]","FSPF had an error in interacting with RIB, error description is [chars].","Check if rib application is running using 'show processes'. Provide output of 'debug fspf route' and RIB debug traces."
"FSPF","3","ROUTE_COMPUTE_ERR","Error in computing or sending routes : Error = [chars]","FSPF had an error in computing routes , error description is [chars].","Provide the error code and output of 'debug fspf error' and 'debug fspf route' if problem is reproducible"
"FSPF","3","UNLOCK_FAIL","FSPF failure in releasing lock","There is a software failure in releasing lock of the shared resource between FSPF threads.","Provide output of 'debug fspf all '"
"FSPF","3","VSAN_TIMER_ERR","Error in processing VSAN timer event [chars], error description = [chars]","FSPF had an internal error in processing timer event , error description is [chars].","Provide output of 'debug fspf error'"
"FSPF","4","FC2_DOWN_INTF","Received FC2 packet on DOWN interface [chars]","FSPF received a FC2 packet on inactive interface [chars] .","This message may be printed for the first FSPF packet when an interface is brought up. If the message is seen continuously check if FSPF is disabled on one end for the interface or the VSAN. Otherwise check 'show interface ' output to see if interface is physically up only on one side. Also check if there is any error message printed for IPC_PROC_ERR"
"FSPF","4","FC2_DOWN_VSAN","Received FC2 packet on inactive vsan","FSPF received a FC2 packet on inactive vsan.","If message seen continuously check if FSPF is disabled on the VSAN Investigate if VSAN is active and valid domain has been assigned on the switch Also check if IPC_PROC_ERR message is printed in the syslog"
"FSPF","4","ILLEGAL_FSM_EVENT","Illegal FSM event for state [chars] in interface [chars]","An illegal protocol event has occurred for the FSPF state machine. The old state was [chars] for the interface [chars].","It is possible to get this message if some protocol packet gets dropped but the it should recover and move back to FULL state. Do 'show fspf interface' to check the state of the interface. If it is stuck in state other than FULL provide output of 'debug fspf event' and 'debug fspf fc pkt ' for the interfaces involved."
"FSPF","4","LSR_DROPPED","[chars], Dropping LSR [dec] received on interface [chars]","A LSR packet is dropped due to [chars] reason. LSR belonged to domain [dec] and was received on interface [chars].","Provide the reason given for dropping the LSR and output of 'debug fspf fc pkt' If the reason is checksum failure investigate possible packet corruption or truncation"
"FSPF","4","LSR_MIN_LS_ARRIVAL","Packet arrived before MIN_LS_ARRIVAL, Dropping LSR [dec] on interface [chars]","A LSR packet is dropped as it arrived before MIN_LS_ARRIVAL. LSR belonged to domain [dec] and was received on interface [chars].","This can occur in transient situation and protocol recovers by retransmitting the LSR. If the message is seen continuously provide output of 'debug fspf flood ' , 'debug fspf retrans' and 'debug fspf error '. The message may be seen more often when interoperating with other vendors"
"FSPF","4","LSU_RX_INIT","Dropping LSU received in state INIT on interface [chars]","A LSU packet is dropped as interface [char] is in INIT state when it received the LSU.","This can occur in some transient situation. If the problem persists provide output of 'show fspf vsan x interface' and 'debug fspf fc pkt ' and 'debug fspf event vsan x'"
"FSPF","5","STARTING","Routing daemon started","FSPF routing daemon has been started.","No action is required."
"FSPF","6","ADD_LSR","New LSR added for domain [dec]","A new LSR is added to the database for domain [dec] .","No action is required."
"FSPF","6","DELETE_LSR","LSR deleted for domain [dec]","The LSR for domain [dec] is deleted from the database.","No action is required."
"FSPF","6","INTF_OPER_DOWN","Down on interface [chars]","FSPF has become operationally down on interface [chars].","No action is required."
"FSPF","6","INTF_OPER_UP","Up on interface [chars]","FSPF has become operational on interface [chars].","No action is required."
"FSPF","6","MAX_AGE","LSR [dec] reached Maxage","The LSR for domain [dec] reached the maximum age and will be deleted from all the connected switches .","No action is required."
"FSPF","6","ROLLOVER","Rolling over the incarnation number of Local LSR","The incarnation number of local LSR reached the maximum value and is rolling over.","No action is required."
"FSPF","6","SELF_ORIGINATED","Received local LSR with higher incarnation number","A LSR for the local domain was received with incarnation number higher than the one in database. This situation should only occur initially on a topology change. If this situation persists the domain assignment of switches may not be unique","If this message is received continuously check if domain assignment is unique in the fabric."
"FSPF","6","STATE_CREATED","Internal state created [chars]","FSPF has created its internal state stateless/stateful [chars].","No action is required."
"FSPF","6","VSAN_OPER_DOWN","Down on vsan","FSPF has become operationally down on VSAN.","No action is required."
"FSPF","6","VSAN_OPER_UP","Up with local domain [dec]","FSPF has started with local domain [dec].","No action is required."
"FSPF","7","ROUTE_THREAD_STARTED","Thread number [dec] started","Route computation thread number [dec] has been started for FSPF.","No action is required."
"FVP","2","GENERAL_ERROR","[chars]","The FVP Manager has encountered an critical error. The description of error is [str.]","No action is required."
"FVP","2","MALLOC_ERROR","Size [dec] bytes","The FVP Manager could not allocate memory.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"FVP","2","PSS_BKP_PSS_MISMATCH","Block [dec]: PSS: Not Free; BKPLN PROM: Free","This FVP Manager detected a discrepancy between the information on the chassis and that in its persistent information databases. The persistent information database has been updated with the information on the chassis.","No action is required."
"FVP","2","PSS_ERROR","[chars]","The FVP Manager encountered error while operating on a persistent storage database.","No action is required."
"FVP","3","FVPD_PSS_CORRUPTED","[chars] PSS found corrupted","The FVP Manager has detected corruption in one of its persistent information database. The database would be recreated.","No action is required."
"FVP","3","PSS_SYNC_TO_STNDBY_FAILED","PSS TYPE=[chars] KEY=[chars]","Could not send PSS Sync. notification to Standby Supervisor. PSS Type=[str.] Operation=[.str] Key=[Str.]","No action is required."
"FVP","3","RELEASE_ERR_FREE","Already free FVP [chars]","A client of FVP Manager attempted to remove a FVP [char] which is not present. This information is for debugging only.","No action is required."
"FVP","3","RELEASE_ERR_UNKNOWN","Unknown FVP [chars]","FVP Manager received a request to release a FVP [char] that could not have been allocated by this FVP Manager.","No action is required."
"FVP","3","RELEASE_ERR","Cant Rel. FVP [chars]","FVP Manager received a request to remove a FVP that cannot be removed.","No action is required."
"FVP","3","TOOMANY_REQ_REL","FVPs [chars] = [dec]","The FVP Manager received a request to allocate [dec] more than the maximum number of FVPs that can be allocated/released in a single request.","No action is required."
"FVP","3","UNKNOWN_MSG","Recvd. from Node=[dec] SAP=[dec] Opcode=[dec]","The FVP Manager has received an unknown message from [dec]].[dec] with opcod [dec]. This information is for debugging only.","No action is required."
"FVP","4","EXITING","Exited due to [chars]","The FVP Manager process has exited due to [char]. The process has probably been restarted automatically.","No action is required."
"FVP","4","PSS_VERSION_MISMATCH","PSS [dec] Code [dec]","There was a version mismatch between the FVP Manager and one of its persistent storage databases. The persistent information has been translated to the new format.","No action is required."
"FVP","6","BECAME_ACTIVE","Became ACTIVE from standby mode","The FVP Manager on the standby supervisor became active and it is ready to serve client requests for FVPs.","No action is required."
"FVP","6","BECAME_STDBY","Became STANDBY from active mode","The FVP Manager became standby from active mode.","No action is required."
"FVP","6","CREATED_FV_PORT","ifIndex: [dec]","The FVP Manager has created a new fv port with ifIndex= [dec].","No action is required."
"FVP","6","EXCESSIVE_DELAY","[chars]","Excessive time taken for a processing event. The description of the event is [str.]","No action is required."
"FVP","6","FAILED_TO_SEND_HEARTBEAT","Failed to send heartbeat to system manager: Reason=[chars]","The FVP Manager was unable to send heartbeat to the system manger","No action is required."
"FVP","6","GENERAL_EVENT","[chars]","The FVP Manager has generated an important event. The description of the event is [str.]","No action is required."
"FVP","6","PSS_CREATED","[chars] PSS Created","One of the persistent information database os FVP Manager has been recreated","No action is required."
"FVP","6","PSS_DESTROYED","[chars] PSS Destroyed","One of the persistent information databases has been intentionally destroyed and would be recreated.","No action is required."
"FVP","6","REMOVED_FV_PORT","IfIndex: [dec]","The FVP Manager has removed an fv port with ifIndex= [dec].","No action is required."
"FVP","6","SERVICE_UP","Initialized [chars]","The FVP Manager is up and ready to accept client requests for FVPs. The service was initialized in [char] mode.","No action is required."
"FVP","6","SWITCHOVER","Switching Over to other Sup.","The FVP Manager has successfully switched over to the standby supervisor card.","No action is required."
"GARUDA_USD","6","GARUDA_DEBUG_MSG","[chars]","Debug log message","No action is required."
"GLBP","2","GLBP_URIB_INIT_ERROR","[chars]","Unicast routing initialization failed and the GLBP process terminated","Please check syslog messages for URIB failures and rectify the problem"
"GLBP","3","GLBP_ARP_ADD_FAILED","failed to add [chars]/[chars] in arp table","The system was unable to add the GLBP vIP into the arp table","Please check syslog messages for ARP failures and rectify the problem"
"GLBP","3","GLBP_ARP_DEL_FAILED","failed to delete [chars]/[chars] in arp table","The system was unable to delete the GLBP vIP from the arp table","Please check syslog messages for ARP failures and rectify the problem"
"GLBP","3","GLBP_FEATURE_MANAGER_ERROR","[chars]: [chars]","There was a problem in GLBP interaction with feature manager.","Please check the reason for error using feature manager and rectify the problem"
"GLBP","3","GLBP_IP_JOIN_GROUP_FAILED","[chars]: failed to join glbp multicast address group","The system was unable to peform a join to start receiving GLBP protocol packets.","Please check syslog messages for IP failures and rectify the problem"
"GLBP","3","GLBP_IP_LEAVE_GROUP_FAILED","[chars]: failed to leave glbp multicast address group","The system was unable to peform a leave to stop receiving GLBP protocol packets.","Please check syslog messages for IP failures and rectify the problem"
"GLBP","3","GLBP_MAC_ADD_FAILED","fwd [dec] failed to add [chars] in mac table (error [hex])","The system was unable to add the GLBP mac address into the mac addresss table","Please check syslog messages for L2FM failures and rectify the problem"
"GLBP","3","GLBP_MAC_DEL_FAILED","fwd [dec] failed to delete [chars] in mac table (error [hex])","The system was unable to delete the GLBP mac address from the mac addresss table","Please check syslog messages for L2FM failures and rectify the problem"
"GLBP","3","GLBP_ROUTE_ADD_FAILED","failed to add [chars] in routing table","The system was unable to add the GLBP vIP address into the unicast routing table","Please check syslog messages for URIB failures and rectify the problem"
"GLBP","3","GLBP_ROUTE_DEL_FAILED","failed to delete [chars] in routing table","The system was unable to delete the GLBP vIP address from the unicast routing table","Please check syslog messages for URIB failures and rectify the problem"
"GLBP","4","BADAUTH","Bad authentication received from [chars]","Two routers participating in a Gateway Load Balancing Protocol group have a valid authentication string that does not match.","Use the glbp authentication interface command to repair the Gateway Load Balancing Protocol authentication discrepancy between the local system and the one whose IP address is reported"
"GLBP","4","BADVIP1","address [chars] is in the wrong subnet for this interface","The Gateway Load Balancing Protocol virtual IP address is not within the subnet configured on this interface.","Configure the virtual IP address of Gateway Load Balancing Protocol to be within the subnet configured on this interface."
"GLBP","4","BADVIP2","address [chars] in the wrong subnet for this interface is not learned","The Gateway Load Balancing Protocol virtual IP address contained in the hello message cannot be learned. It is not within the subnet configured on this interface.","Check the configuration on all Gateway Load Balancing Protocol routers."
"GLBP","4","BADVIP3","address [chars] is the broadcast address for this interface","The Gateway Load Balancing Protocol virtual IP address is a broadcast address for this interface.","Configure the virtual IP address of Gateway Load Balancing Protocol to be a non broadcast address."
"GLBP","4","DIFFVIP1","active router virtual IP address [chars] is different from the locally configured virtual IP address [chars]","The Gateway Load Balancing Protocol virtual IP address contained in the Hello message from the Active router is different to that configured locally.","Check the configuration on all Gateway Load Balancing Protocol routers"
"GLBP","4","DUPADDR","Duplicate address on [chars]","The IP address in a Gateway Load Balancing Protocol message received on the interface is the same as the IP address of its own router. This condition may be caused by a misconfiguration or because of a malfunctioning switch.","Check the configurations on all the Gateway Load Balancing Protocol routers, and ensure that any switches are functioning properly"
"GLBP","4","DUPVIP1","address [chars] already assigned to interface [chars] grp [dec]","The Gateway Load Balancing Protocol virtual IP address contained in the hello message cannot be learned. It is already assigned to a different Gateway Load Balancing Protocol group.","Check the configuration on all Gateway Load Balancing Protocol routers"
"GLBP","4","DUPVIP2","address [chars] already assigned to this interface","The Gateway Load Balancing Protocol virtual IP address contained in the hello message cannot be learned. It is already assigned to this interface.","Check the configuration on all Gateway Load Balancing Protocol routers."
"GLBP","4","DUPVIP3","address [chars] already assigned to another interface [chars]","The Gateway Load Balancing Protocol virtual IP address contained in the hello message cannot be learned. It is already assigned to, or overlaps with, an address on another interface or application.","Check the configuration on all Gateway Load Balancing Protocol routers."
"GLBP","4","GLBP_ARP_RESP_FAILED","failed to send arp response [chars]/[chars]","The system was unable to send the arp response for vIP","Please check syslog messages for ARP failures and rectify the problem"
"GLBP","5","ACTIVE_CHANGE","Active gateway is [chars]","The Gateway Load Balancing Protocol has changed active gateway.","No action is required"
"GLBP","5","FWDSTATECHANGE","fwd [dec] state changed from [chars] to [chars]","The Gateway Load Balancing Protocol forwarder has changed state.","No action is required"
"GLBP","5","FWD_CREATE","fwd [dec] created","The Gateway Load Balancing Protocol forwarder has been created.","No action is required"
"GLBP","5","FWD_DELETE","fwd [dec] deleted","The Gateway Load Balancing Protocol forwarder has been removed.","No action is required"
"GLBP","5","FWD_OWNER","fwd [dec] owner mac is [chars]","The Gateway Load Balancing Protocol forwarder has changed the owner MAC address.","No action is required"
"GLBP","5","FWD_VMAC","fwd [dec] virtual mac is [chars]","The Gateway Load Balancing Protocol forwarder has changed the virtual MAC address.","No action is required"
"GLBP","5","FWD_WEIGHTING","fwd [dec] weighting is [dec]","The Gateway Load Balancing Protocol forwarder has changed the weighting.","No action is required"
"GLBP","5","GRPSTATECHANGE","state changed from [chars] to [chars]","The Gateway Load Balancing Protocol gateway has changed state.","No action is required"
"GLBP","5","MEMBER_ADD","member [chars] [chars] added","The Gateway Load Balancing Protocol gateway has added a member.","No action is required"
"GLBP","5","MEMBER_REMOVE","member [chars] [chars] removed","The Gateway Load Balancing Protocol gateway has removed a member.","No action is required"
"GLBP","5","PRIORITY","[chars] gateway priority changed to [dec]","The Gateway Load Balancing Protocol gateway has changed priority.","No action is required"
"GLBP","5","STANDBY_CHANGE","Standby gateway is [chars]","The Gateway Load Balancing Protocol has changed standby gateway.","No action is required"
"GLBP","5","TIMER","[chars] timer changed to [chars]","The Gateway Load Balancing Protocol gateway has learnt timers.","No action is required"
"GLBP","5","VIPLEARN","learnt virtual ip address [chars]","The Gateway Load Balancing Protocol gateway has learnt virtual IP address.","No action is required"
"GLBP","5","VIPUNLEARN","unlearnt virtual ip address [chars]","The Gateway Load Balancing Protocol gateway has unlearnt virtual IP address.","No action is required"
"GLBP","5","WEIGHTING","weighting changed to [dec]","The Gateway Load Balancing Protocol gateway has changed the weighting.","No action is required"
"HSRP_ENGINE","3","BFD_GLOBAL_SESSION_REMOVAL_ERROR","Failed to remove all the HSRP-BFD sessions([hex] [hex]), Refer logs","Refer logs for more details","No action is required."
"HSRP_ENGINE","3","BFD_IF_SESSION_REMOVAL_ERROR","Failed to remove few HSRP-BFD sessions([hex] [hex]), Refer logs","Refer logs for more details.","No action is required."
"HSRP_ENGINE","3","BFD_SESSION_ADD_ERROR","Failed to add few HSRP-BFD sessions([hex] [hex]), Refer logs","TRefer logs for more details.","No action is required."
"HSRP_ENGINE","3","BFD_SESSION_CREATION_ERROR","Failed to create BFD session information([hex] [hex]), Refer logs","Refer logs for more details.","No action is required."
"HSRP_ENGINE","3","BFD_SESSION_REMOVAL_ERROR","Failed to remove few HSRP-BFD sessions([hex] [hex]), Refer logs","Refer logs for more details.","No action is required."
"HSRP_ENGINE","3","ERROR_IN_ADD_VIP_TO_U6RIB","Failed to Add VIP [chars] to U6RIB (errno [hex]), Refer logs","Refer logs for more details.","No action is required."
"HSRP_ENGINE","3","ERROR_IN_DEL_VIP_FROM_U6RIB","Failed to delete VIP [chars] from U6RIB (errno [hex]), Refer logs","Refer logs for more details.","No action is required."
"HSRP_ENGINE","3","NOSOCKET","Unable to open socket","The system was unable to initialize an IP connection for the Hot Standby protocol.","Make sure that there is at least one interface configured to run IP."
"HSRP_ENGINE","4","BADAUTH2","Bad authentication from [chars]","Two routers participating in HSRP disagree on the valid authentication string.","Use the HSRP authentication command to repair the HSRP authentication discrepancy between the local system and the one whose IP address is reported."
"HSRP_ENGINE","4","BADAUTH","Bad authentication from [chars], group [dec], remote state [chars]","Two routers participating in HSRP disagree on the valid authentication string.","Use the HSRP authentication command to repair the HSRP authentication discrepancy between the local system and the one whose IP address is reported."
"HSRP_ENGINE","4","DIFFVIP1","[chars] Grp [dec] active routers virtual IP address [chars] is different to the locally configured address [chars]","The HSRP virtual IP address contained in the Hello message from the Active router is different to that configured locally.","Check the configuration on all HSRP routers."
"HSRP_ENGINE","4","DUPADDR","Duplicate address %i on [chars], sourced by %e","The IP address in an HSRP message received on the interface is the same as the routersownIPaddress.Thismaybebecauseofmisconfiugration,orbecauseofamalfunctioningswitch'","Check the configurations on all the HSRP routers, and make sure that any switches you have are functioning properly."
"HSRP_ENGINE","4","DUPVIP1","[chars] Grp [dec] address [chars] is already assigned to a HSRP group on this interface","The HSRP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to a different HSRP group.","Check the configuration on all HSRP routers."
"HSRP_ENGINE","4","DUPVIP2","[chars] Grp [dec] address [chars] is already assigned on this interface","The HSRP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to this interface.","Check the configuration on all HSRP routers."
"HSRP_ENGINE","4","DUPVIP3","[chars] Grp [dec] address [chars] is already assigned to, or overlaps with, an address on another interface or application","The HSRP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to, or overlaps with, an address on another interface or application.","Check the configuration on all HSRP routers."
"HSRP_ENGINE","5","ACTIVEROUTERPRIORITY","Interface [chars] [chars] Grp [dec] Active router priority changed to [dec]","The priority of the Active router for the group has changed.","No action is required."
"HSRP_ENGINE","5","ACTIVE_CHANGE","Interface [chars] [chars] Grp [dec] Active router is [chars]","The Active router for the group has changed.","No action is required."
"HSRP_ENGINE","5","AUTOCONFIG_VIPLEARN","Interface [chars] grp [dec] learnt autoconfig virtual ip address [chars]","The local router has generate virtual ip address","No action is required."
"HSRP_ENGINE","5","GRPSTATECHANGE","Interface [chars] [chars] Grp [dec] state changed from [chars] to [chars] reason [chars]","The HSRP router has changed state","No action is required."
"HSRP_ENGINE","5","MACADDRESS_CHANGE","Interface [chars] [chars] Grp [dec] mac-address changed to [chars]","The mac address of the group has changed.","No action is required."
"HSRP_ENGINE","5","PRIORITY","Interface [chars] [chars] Grp [dec] priority changed to [dec]","The current priority of the HSRP group has changed.","No action is required."
"HSRP_ENGINE","5","STANDBYROUTERPRIORITYCHANGE","Interface [chars] [chars] Grp [dec] Standby router priority changed to [dec]","The priority of the Standby router for the group has changed.","No action is required."
"HSRP_ENGINE","5","STANDBY_CHANGE","Interface [chars] [chars] Grp [dec] Standby router is [chars]","The Standby router for the group has changed.","No action is required."
"HSRP_ENGINE","5","TIMER","Interface [chars] [chars] Grp [dec] [chars] timer changed to [dec] [chars]","The hello/hold timer value for the HSRP group has changed","No action is required."
"HSRP_ENGINE","5","VIPLEARN","Interface [chars] [chars] Grp [dec] learnt virtual ip address [chars]","The local router has learnt virtual ip address from the incoming HSRP packet.","No action is required."
"HSRP_ENGINE","6","STATECHANGE2","[chars] [chars] Grp [dec] state moving from [chars]","The router has changed state","No action is required."
"HSRP_ENGINE","6","STATECHANGE","[chars] [chars] Grp [dec] state move to [chars]","The router has changed state","No action is required."
"IDEHSD","1","MANUAL_FORMAT","logflash needs to be formatted","Logflash is not accessible; use format logflash: to format it","No action is required."
"IDEHSD","2","AUTO_FORMAT","logflash auto-format [chars]","Logflash auto-format event","No action is required."
"IDEHSD","2","DISK_BUSY_FAILED","Cannot umount [chars],","The specified disk interface is in use it can not be un mounted, The user may experience file system correuption","Make sure slot0 is not being used either by mounting or by any command and re-insert the disk again"
"IDEHSD","2","DISK_FSCK_FAIL","file system check returned error on slot [dec]","Flash fliesyetm may be corrupted, the flash was taken while it was being accessed","Reformat the extarnal flash"
"IDEHSD","2","DISK_MOUNT_FAIL","disk mount unsuccessful on [chars]","Unknown flash filesystem or not cleanly un mounted","Use vfat flash only and make sure external slot is not being accessed then re-insert flash"
"IDEHSD","2","DISK_RESCAN_FAIL","disk rescan unsuccessful on [chars]","Flash fliesyetm was not cleanly un mounted","Make sure external slot is not being accessed and re-inset the flash"
"IDEHSD","2","DISK_UMOUNT_FAIL","disk umount unsuccessful for [chars]","Flash fliesyetm is busy the system could noy un-mount it","Make sure external slot is not being accessed and re-inset the flash"
"IDEHSD","2","FORK","fork failed ([chars] process)","The flash daemon failed to fork","No action is required."
"IDEHSD","2","INTERNAL_ERROR","Internal Error [dec]","The flash daemon interface returns error","Restart the idehsd deamon"
"IDEHSD","2","MOUNT","[chars] online","Flash daemon mounting slot","No action is required."
"IDEHSD","2","UMOUNT","[chars] offline","Flash daemon un mounting slot","No action is required."
"IDEHSD","2","USB_SWAP","USB insertion or removal detected","USB swap event","No action is required."
"IDEHSD","3","DEVICEOPEN_FAILED","device open failed. Component [chars]","The flash daemon device open failed The failure is due to the sub-component [chars]","No action is required."
"IDEHSD","5","DISK_SWAP","[chars] [chars]","Compach flash swap event","No action is required."
"IDEHSD","6","DISK_BUSY","trying to un mount disk [chars]","Flash daemon trying to umount busy slot","No action is required."
"IDEHSD","6","DISK_EVENT","slot [dec] [chars]","Flash daemon found a disk hotswap handler event","No action is required."
"IDEHSD","6","IDEHSD_INFO","[chars]","Flash daemon informational message","No action is required."
"IDEHSD","6","IOCTL","ioctl: [chars] returns [dec]","Flash daemon trying to umount busy slot","No action is required."
"IDEHSD","6","STARTING","deamon started","The compact flash swap daemon successfully started","No action is required."
"IDEHSD","7","IDEHSD_TRACE","[chars]() [chars]:[dec] disk=[dec]","Flash daemon debug message to trace code path","No action is required."
"IFTMC-SLOT#","1","IFTMC_GENERIC_ERROR","[chars]","[chars]","No action is required."
"IFTMC-SLOT#","2","ELTMC_INTERFACE_INTERNAL_ERROR","Internal error: [chars]:[chars], collect output of show tech-support eltm","IFTMC hit a internal error. Collect show tech-support eltm for futher analysis.","No action is required."
"IFTMC-SLOT#","2","ELTMC_INTERNAL_ERROR","Internal error: [chars], collect output of show tech-support eltm","IFTMC hit a internal error. Collect show tech-support eltm for futher analysis.","No action is required."
"IFTMC-SLOT#","2","ELTMC_INTF_NOT_FOUND","Interface [chars] not found in IFTMC database [chars]","IFTMC database doesnthavetheinterface.'","No action is required."
"IFTMC-SLOT#","2","ELTMC_INTF_NOT_SUPP","Interface [chars] not supported by IFTMC [chars]","IFTMC doesntsupporttheinterfaceforthespecifiedoperation'","No action is required."
"IFTMC-SLOT#","2","ELTMC_INTF_TO_LTL","Failed to get LTL for interface [chars] return status [chars]","IFTMC Failed to get LTL for interface. Packets received on this interface might not be handled correctly by the forwarding engine","No action is required."
"IFTMC-SLOT#","2","ELTMC_INTF_TO_SLOT","Failed to get slot for interface [chars] return status [chars]","IFTMC Failed to get Slot for interface. Port-channels and L2 Learning might be effected","No action is required."
"IFTMC-SLOT#","2","ELTMC_INVALID_FTAG_NUM","IFTMC received INVALID Number of FTAGs in the message.. [chars]","IFTMC Failed: Received INVALID Ftags","No action is required."
"IFTMC-SLOT#","2","ELTMC_L2_LIF_ALLOC_FAIL_INTF","Failed to allocate L2 LIF entries in forwarding engine for interfac [chars]","IFTMC Failed to allocate L2 LIF entries in forwarding engine. This will effect Layer 2 and Layer 3 forwarding for the interface","No action is required."
"IFTMC-SLOT#","2","ELTMC_L2_LIF_ALLOC_FAIL_VDC","Failed to allocate L2 LIF entries in forwarding engine","IFTMC Failed to allocate L2 LIF entries in forwarding engine. This will effect Layer 2 and Layer 3 forwarding in this VDC","No action is required."
"IFTMC-SLOT#","2","ELTMC_L3_INGRESS_LIF_ALLOC_FAIL_INTF","Failed to allocate L3 Ingress LIF entries in forwarding engine for interfac [chars]","IFTMC Failed to allocate L3 Ingress LIF entries in forwarding engine. This will effect Layer 3 forwarding for the interface","No action is required."
"IFTMC-SLOT#","2","ELTMC_RSVD_VLAN","Failed to get the reserved vlans. Failed with error [chars]","IFTMC Failed to get the reserved vlans.ThiswilleffectmulticastforwardingonSVIinterfaces'","No action is required."
"IFTMC-SLOT#","2","ELTMC_VLAN_INTERNAL_ERROR","Internal error: VLAN [dec]:[chars], collect output of show tech-support eltm","IFTMC hit a internal error. Collect show tech-support eltm for futher analysis.","No action is required."
"IFTMC-SLOT#","2","IFTMC_BD_NULL_WARN","IFTMC BD is zero: [chars]","IFTMC BD is zero, SVI create beafore vlan create","No action is required."
"IFTMC-SLOT#","2","IFTMC_FCOE_FEATURE_REQ_FAIL","FCOE feature request for interface [chars] cannot be processed","FCOE feature request cannot be processed with ILM sharing, failure status does not get returned to calling app. Possible ACLQOS verify/commit fail prior to this feature request.","No action is required."
"IFTMC-SLOT#","2","IFTMC_FTAG_PROG_FAIL","Failed to program ftag list as it exceeds the platform limit [dec]","IFTM Failed to apply ftag list on an interface","No action is required."
"IFTMC-SLOT#","2","IFTMC_PVLAN_XLT_FAIL","Failed to apply translation table [chars]","IFTM Failed to apply vlan tranlation table on an interface","No action is required."
"IFTMC-SLOT#","2","IFTMC_RES_ALLOC_FAIL","IFTMC resource allocation failure: [chars]","IFTMC failed resource allocation","No action is required."
"IFTMC-SLOT#","2","IFTMC_RES_ALLOC_WARN","IFTMC resource allocation warning: [chars]","IFTMC resource usage has exceeded a preset threshold","No action is required."
"IFTMC-SLOT#","2","IFTMC_RSVD_VLAN","FEX_RESERVED_VLAN_ERR: [chars]","VLAN_MGR SDB call returned FAILURE for FEXNo action is required.IKE MessagesThis section contains the IKE messages.IKE-3Error Message      IKE-3-CRYPTO_INIT_ERROR: IKEv2 crypto init error: [chars] Explanation    Crypto initialization error","No action is required."
"IKE","3","ENABLE_ERROR","Unable to store enable flag in configuration (error-id [hex]).","Service failed to store the enable flag in configuration. As a result, it will exit","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IKE","3","FIPS_MODE_ERROR","Could not set FIPS mode","The FIPS mode could not be set by IKE","No action is required."
"IKE","3","IKE_PROGRAM_EXIT","[chars]","IKE process did an abnormal exit","No action is required."
"IKE","3","MAX_HALF_CONN_LIMIT_REACHED","IKEv1 : Exceeded the limit for number of half open Phase 1 connections","The number of half open connections has exceeded the maximum limit","No action is required."
"IKE","3","PHASE1_NEGOTIATION_FAILED","IKEv1: Phase 1 negotiation failed for peer [chars]","IKE policy negotiation failed for peer [chars].","No action is required."
"IKE","3","PHASE1_PROPOSAL_MISMATCH","IKEv1: No matching phase 1 proposal found for peer [chars]","There is a IKE policy mismatch for the peer.","No action is required."
"IKE","3","PHASE2_NEGOTIATION_FAILED","IKEv1: Phase 2 negotiation failed for peer [chars]","IPsec policy negotiation failed for peer [chars].","No action is required."
"IKE","3","PHASE2_PROPOSAL_MISMATCH","IKEv1: No matching phase 2 proposal found for peer [chars]","There is a IPsec policy mismatch for the peer.","No action is required."
"IKE","3","UNSUPPORTED_EXCHANGE","IKEv1: Unsupported exchange [dec] received from [chars]","A unsupported IKE exchange type [digits] was received from [chars]","No action is required."
"IKE","4","INVALID_PAYLOAD_APPEAR","IKEv2 received message (from [chars]) with payload ([chars]) appeared in [chars]([chars])","Received a payload in an inappropriate exchange","No action is required."
"IKE","4","MESSAGE_ERROR","IKEv2 message (from [chars]) message error: [chars]","Received a malformed message which doesntadheretotheprotocol'","No action is required."
"IKE","4","PARSING_ERROR","IKEv2 message (from [chars]) parsing error: [chars]","Received a malformed message which can not be parsed appropriately","No action is required."
"IKE","4","UNKNOWN_PAYLOAD","IKEv2 received message (from [chars]) with un-recognized payload ([chars])","Received an invalid payload","No action is required."
"IKE","4","UNSUPPORT","[chars] is not supported (message from [chars])","Received something unsupported","No action is required."
"IKE","6","POLL_START_DONE","IKE is exiting since it is not enabled","IKE is exiting since it is not enabled in the configuration","No action is required."
"ILC-SPAN","3","ERROR","[chars]","Ilc_span_mgr encountered an error","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"ILC_HELPER","2","NO_LICENSE_REBOOT","Linecard [dec] will reboot now.","SSE License has expired, hence the linecard will be rebooted.","Install appropriate SSE license to be able to use SSM features normally"
"ILC_HELPER","3","INVALID_SSI","[chars]","The ssi boot variable is configured to an invalid image. So, the linecard will be bought online in basic mode instead of advanced SSI mode","Configure a proper image for the ssi boot variable"
"ILC_HELPER","6","LICENSE_VALID","A valid license for linecard [dec] has been obtained","A valid license has been obtained for the SSM","No action is required."
"ILC_HELPER","6","UPGRADE_DELAY","The SSI upgrade on slot [dec] is delayed by [dec] secs.","The SSI upgrade is delayed due to the configured ssm upgrade delay command","No action is required."
"IMAGE_DNLD-SLOT#","2","ADDON_IMG_DNLD_FAILED","Module image download process failed. [chars]","Addon image download to module failed. This module is not operational until an addon image has been successfully installed.","Verify the location and version of your module image. Use the install module cli command to download a new module image."
"IMAGE_DNLD-SLOT#","2","IMG_DNLD_COMPLETE","Module image download process. [chars]","Image download completed. Module image is being installed.","No action is required."
"IMAGE_DNLD-SLOT#","2","IMG_DNLD_FAILED","Module image download process. [chars]","Image download failed. Module may be inoperable.","Use show module cli command to verify the state of this module. Retry image download with install module cli command."
"IMAGE_DNLD-SLOT#","2","IMG_DNLD_FILE_SYSTEM_CHECK_ERROR","File System check failed: [chars]","File system consistency check failed","File-system repair is needed using fsck"
"IMAGE_DNLD-SLOT#","2","IMG_DNLD_STARTED","Module image download process. [chars]","Image download started. Module image downloads are non-disruptive to module operation.","No action is required."
"IMAGE_DNLD-SLOT#","4","IMG_DNLD_FILE_SYSTEM_RECREATION","[chars]. Partition was erased and successfully recreated.","File system checking and recreation if necessary for /images.","No action is required."
"IMAGE_DNLD-SLOT#","5","ADDON_IMG_DNLD_COMPLETE","Addon module image download process completed. [chars]","Addon image download to module has completed.The module should now be installing this new image.","This message is informational only."
"IMAGE_DNLD-SLOT#","5","ADDON_IMG_DNLD_STARTED","Addon module image download process started. [chars]","Addon image download to module has started. This is a disruptive download and this module will be inoperable until this download process is complete.","This message is informational only."
"IMAGE_DNLD-SLOT#","5","ADDON_IMG_DNLD_SUCCESSFUL","Addon module image download and install process successful. [chars]","Addon image download and install to module is successful.","Use the show module cli command to verify the modulesoperationalstatus.'"
"IMAGE_UPGRADE-SLOT#","2","IMAGE_UPGRADE_ERROR","[chars]","Image Upgrade Error","No action is required."
"IMAGE_UPGRADE-SLOT#","4","IMAGE_UPGRADE_INFO","[chars]","Image Upgrade Info","No action is required."
"IM","3","IM_IF_FEATURE_BIND_FAILURE","Interface feature bind failed [chars]","Interface feature bind failed, so applications in that feature set may not behave correctly.","No action is required."
"IM","3","IM_LC_OFFLINE_ERROR","LC Offline could not be sent to vdc:[dec]","LC Offline was not relayed to some vdc, so applications may not behave correctly.","No action is required."
"IM","3","IM_RESP_ERROR","Component [chars] opcode:[chars] in vdc:[dec] returned error:[chars]","Some component returned an error.","No action is required."
"IM","3","IM_SEQ_ERROR","Error ([chars]) while communicating with component [chars] opcode:[chars] (for:[chars])","Some component did not respond to a request in stipulated time.","No action is required."
"IM","5","IM_DEMUX_ERROR","[chars]","Demux function returned error","No action is required."
"IM","5","IM_INTERNAL_ERROR","[chars]","Internal error occurred","No action is required."
"IM","5","IM_INTF_STATE","[chars] [chars] in vdc [dec]","Management interface state changed.","No action is required."
"IM","5","IM_UNKNOWN_INTERFACE","[chars]","Interface is not supported or not found","No action is required."
"INSTALLER","1","UPGRADE_EXCEEDED_DOWNTIME","Switch control plane down more than 80 seconds.","This message indicates that control plane was down for more than 80 seconds.","No action is required."
"INSTALLER","5","UPGRADE_ABORTED","System upgrade aborted.","This message indicates that system wide upgrade has aborted.","No action is required."
"INSTALLER","5","UPGRADE_COMPLETED","System upgrade completed.","This message indicates system wide upgrade has completed.","No action is required."
"INSTALLER","5","UPGRADE_INITIATED","System upgrade initiated.","System wide upgrade has been initiated by the user.","No action is required."
"INSTALLER","5","UPGRADE_STOPPED","System upgrade stopped.","This message indicates that system wide upgrade has been stopped by the user.","No action is required."
"INTERFACE_VLAN","4","SVI_IF_CONFIG_DELETED_NOTIF_DELAYED_DROPPED","Interface VLAN Delete Notification Not Processed on Time by SAP [dec] ([chars])","This SAP took long time in processing Interface VLAN delete notification and caused timeout","No action is required."
"INTERFACE_VLAN","4","SVI_IF_CONFIG_REMOVED_NOTIF_DELAYED_DROPPED","Interface VLAN Remove Notification Not Processed on Time by SAP [dec] ([chars])","This SAP took long time in processing Interface VLAN remove notification and caused timeout","No action is required."
"INTERFACE_VLAN","4","SVI_VLAN_DOES_NOT_EXIST","Vlan [dec] does not exist","Vlan not created before assignment","Interface-vlan"
"INTERFACE_VLAN","4","SVI_WARN_SVI_UP_IN_NON_ROUTABLE_VDC","Interface VLAN [dec] is being kept up in non-routable VDC. Reason: management configuration enabled. Please disable all the routing protocols","Keeping Interface VLAN up in non-routable VDC may cause potenital traffic blackhole","No action is required."
"INTERFACE_VLAN","5","IF_DOWN_ADMIN_DOWN","Interface [chars] is down(Administratively Down)","Interface has been configured to be administratively down","No action is required."
"INTERFACE_VLAN","5","IF_DOWN_ERROR_DISABLED","Interface [chars] is down. Reason [dec]","The interface encountered an error while configuring it","No action is required."
"INTERFACE_VLAN","5","IF_DOWN_INACTIVE","Interface [chars] is down (Inactive)","Interface VLAN has been suspended or deleted","No action is required."
"INTERFACE_VLAN","5","SVI_DISABLED","SVI Disabled","SVI Service Disabled","No action is required."
"INTERFACE_VLAN","5","SVI_ENABLED","SVI Enabled","SVI Service Enabled","No action is required."
"INTERFACE_VLAN","5","SVI_GET_MAC_FAILED","Failed to acquire MAC address for SVI [hex]","SVI failed to acquire MAC address","No action is required."
"INTERFACE_VLAN","5","SVI_INIT","SVI intialization failed with error [hex]","SVI initialziation error","No action is required."
"INTERFACE_VLAN","5","SVI_IOD_RELEASE_ERROR_RESPONSE","IM failed to release SVI IOD error [hex]","IM failed to release SVI IOD","No action is required."
"INTERFACE_VLAN","5","SVI_MTS_SEND_FAILURE","MTS send failure for opcode [dec], error [hex]","SVI encountered an error in with MTS message","No action is required."
"INTERFACE_VLAN","5","SVI_MTS_TIME_OUT","MTS send timed out","SVI did not recieve response for mts message","No action is required."
"INTERFACE_VLAN","5","SVI_RSRVD_VLAN_FAILED","Failed to get list of reserved vlans [hex]","SVI failed to get the list reserved vlans","No action is required."
"INTERFACE_VLAN","5","SVI_SDB_UPDATE_FAILED","sdb update failed with ret_val [dec]","SDB updated failed for SVI","No action is required."
"INTERFACE_VLAN","5","SVI_SEC_VLAN_FAILED","Failed to get list of secondary vlans [hex]","SVI failed to get the list of secondary vlans","No action is required."
"INTERFACE_VLAN","5","UPDOWN","Line Protocol on Interface [chars], changed state to [chars]","Line protocol status changed for an interface","No action is required."
"IOA_LC","5","IOA_DISABLED","IOA Disabled","IOA Service Disabled","No action is required."
"IOA_LC","5","IOA_ENABLED","IOA Enabled","IOA Service nabled","No action is required."
"IPACL","0","EMERG","[chars]","Ipacl caused a system failure","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IPACL","1","ALERT","[chars]","Ipacl caused failures in other services","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IPACL","2","CRIT","[chars]","Ipacl encountered a catastrophic error","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IPACL","3","ERR","[chars]","Ipacl encountered an error","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IPACL","4","WARN","[chars]","Ipacl ignored the unexpected condition","Please perform debugipaclall',thenrecreatetheoperationscenario,tofindoutmoredetails.'"
"IPACL","5","NOTE","[chars]","Ipacl does not support this operation","Please perform debugipaclall',thenrecreatetheoperationscenario,tofindoutmoredetails.'"
"IPACL","6","INFO","[chars]","Ipacl event occurred","No action is required."
"IPFC","2","ALLOC_MEMORY","Memory allocation failed","The service failed to allocate a block of dynamic memory.","No action is required."
"IPFC","3","INIT_FAILED","Initialization failed. Component [chars]","The service failed to start. The failure occurred while initializing the component [chars].","Show processes to check the status of the other processes, debug the specified component."
"IPFC","3","IOCTL_FAILED","IOCTL failed","An IOCTL to the character device failed.","Show IPFC internal interface VSAN <number"
"IPFC","3","PSSERROR","[chars]","IPFC manager encountered a PSS error.","No action is required."
"IPFC","5","CONFIG_EVENT","VSAN interface [dec] [chars]","The specified VSAN Interface has been successfully [chars].","No action is required."
"IPFC","5","STATE_CHANGE","VSAN interface [dec] [chars]","The specified VSAN Interface is [chars].","No action is required."
"IPFC","6","STARTING","IP Over Fiber Channel service started","The service has successfully started.","No action is required."
"IPQOSMGR","2","QOSMGR_DCBXP_PFC_CMP_FAIL_MSG","[chars] - qos config [chars] not compatible with the peer","Port_id [chars] has qos config [chars] which is incompatible with the peer.","No action is required."
"IPQOSMGR","2","QOSMGR_HA_FAILURE","Failed to do high availability operation: [chars].","Failed to do high availability operation. [chars] is the reason.","No action is required."
"IPQOSMGR","2","QOSMGR_INIT_FAILED","Initialization failed for QoS Manager: [chars], reason: [hex].","Initialization failed for QoS Manager due to [chars], reason: [hex].","No action is required."
"IPQOSMGR","2","QOSMGR_MTS_FAILURE","Failed to do MTS operation: [chars].","Failed to do MTS operation. [chars] is the reason.","No action is required."
"IPQOSMGR","2","QOSMGR_MTS_REGISTRATION_FAILED","MTS options setting to [hex] failed for opCode: [dec].","MTS options setting to [hex] failed for opCode: [dec].","No action is required."
"IPQOSMGR","2","QOSMGR_NETWORK_QOS_POLICY_CHANGE","Policy [chars] is now active","[chars] is the new active network-qos policy","No action is required."
"IPQOSMGR","2","QOSMGR_PSS_FAILURE","Failed to do PSS operation: [chars], reason: [hex].","Failed to do PSS operation [chars]. [hex] is the reason.","No action is required."
"IPQOSMGR","2","QOSMGR_PSS_VER_FAIL","PSS file [chars] has version [dec].[dec].[dec], expected version [dec].[dec].[dec].","There was a mismatch in the PSS version. [chars] indicates the PSS service, [dec].[dec].[dec] its current version number and [dec].[dec].[dec] the expected version.","No action is required."
"IPQOSMGR","3","QOSMGR_CONFIG_ERROR","Configuration error: [chars].","Configuration error. [chars] is the reason.","No action is required."
"IPQOSMGR","3","QOSMGR_NVDC_PFF_ERROR","PPF verify/commit failed in vdc [dec] error: [hex] for global qos command","For global qos command, PPF verify/commit failed in vdc [dec] with reason [hex].","No action is required."
"IPQOSMGR","3","QOSMGR_PPF_ERROR","PPF library error: [chars].","PPF library errors. [chars] is the reason.","No action is required."
"IPQOSMGR","4","QOSMGR_LC_ERROR_MSG","Linecard [dec] returned an error: [chars]","Linecard [dec] returned an error message which is reported as [chars].","No action is required."
"IPQOSMGR","4","QOSMGR_POLICIES_PRESENT_ON_DELETED_VLANS","Some VLANs (id: [chars]) which are getting deleted now are still having qos service-policy attached. These policies will be effective only when the VLANs get created again.","VLAN(s) [chars] is(are) getting deleted now. This is an informationsl message to notify that qos service-policies are present when the vlan is deleted. If the service-policies are not needed, please detach them from the vlans","No action is required."
"IPQOSMGR","4","QOSMGR_PPF_WARNING","PPF library warning: [chars].","PPF library warning. [chars] is the reason.","No action is required."
"IPQOSMGR","4","QOSMGR_WARNING_MSG","[chars] [dec]","QOSMGR warning messages is reported as [chars] [dec].","No action is required."
"IPQOSMGR","6","QOSMGR_DCBXP_CMP_FAIL_MSG","[chars] - qos config [chars] not compatible with the peer","Dcbxp warning: Port_id [chars] has qos config [chars] which is incompatible with the peer.","No action is required."
"IPQOSMGR","6","QOSMGR_STATUS","QOSMGR Status: [chars].","QOSMGR status is reported as [chars].","No action is required."
"IPSEC","2","IPSEC_INIT","IPSec initialization of [chars] [chars]","IPSec initialization failed","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IPSEC","2","IPSEC_SPD_OVERFLOW_DUE_TO_ACL","SPD Overflow on interface due to IP ACL [chars] bound to crypto map [chars] [dec]","Modifying IP ACL caused Security Policy Database on the interface to overflow, IP ACL filter not applied to security policy database","Undo IP ACL change"
"IPSEC","3","14_2_MODULE_PACKETS_DROPPED","[chars]: packets were dropped in the module","Packets dropped in the 14/2 module. Please collect drop statistics using show ipsec internal crypto-acc interface gigabit <slot/port","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IPSEC","3","IPSEC_FIPS_TEST_FAILED","IPSEC FIPS compliance test failed","IPSEC FIPS compliance test failed","No action is required."
"IPSEC","3","IPSEC_MSG_SEND_FAILURE","failed to send [chars] to sap [dec]: [chars]","Failed to send a message","No action is required."
"IPSEC","5","IPSEC_CMS_IF_ACL_UPDATED","IP ACL [chars] updated while Crypto map [chars] [dec] bound to interface(s)","IP ACL updated while it is mapped to a crypto map that is bound to interface(s)","No action is required."
"IPSEC","5","IPSEC_DISABLED_LIC_EXPIRED","IPSec Disabled due to License Expiry","IPSec Disabled due to License Expiry","No action is required."
"IPSEC","5","IPSEC_DISABLED","IPSec Disabled","IPSec Disabled","No action is required."
"IPSEC","5","IPSEC_ENABLED","IPSec Enabled","IPSec Enabled","No action is required."
"IPSEC","5","IPSEC_SA_CREATED","[chars]: IPSec SA created: local_ip: [chars], peer_ip: [chars], [chars] SPI: [dec] ([hex])","IPSec SA created","No action is required."
"IPSEC","5","IPSEC_SA_DELETED","[chars]: IPSec SA deleted: local_ip: [chars], peer_ip: [chars], [chars] SPI: [dec] ([hex]), reason: [chars]","IPSec SA deleted","No action is required."
"IPSEC","5","IPSEC_SA_REKEYED","[chars]: IPSec SA rekeyed: local_ip: [chars], peer_ip: [chars], [chars] SPI: [dec] ([hex])","IPSec SA rekeyed","No action is required."
"IPSEC","5","IPSEC_TUNNEL_CREATED","[chars]: IPSec tunnel created: local_ip: [chars], peer_ip: [chars], id: [dec], protocol: [chars], traffic:: local: [chars]/[chars], port: [chars], remote: [chars]/[chars], ports: [chars]","IPSec tunnel created","No action is required."
"IPSEC","5","IPSEC_TUNNEL_DELETED","[chars]: IPSec tunnel deleted: local_ip: [chars], peer_ip: [chars], id: [dec], protocol: [chars], traffic:: local: [chars]/[chars], ports: [chars] remote: [chars]/[chars], ports: [chars]","IPSec tunnel deleted","No action is required."
"IPSEC","5","IPSEC_TUNNEL_REKEYED","[chars]: IPSec tunnel rekeyed: local_ip: [chars], peer_ip: [chars], id: [dec], protocol: [chars] traffic:: local: [chars]/[chars], ports: [chars] remote: [chars]/[chars], ports: [chars]","IPSec tunnel rekeyed","No action is required."
"IPS_SB_MGR-SLOT#","2","NODE_CORE_NOT_RESPONDING","[Node [dec], Core [dec]]: Not responding to heartbeats, state=[hex]","Node is not incrementing heartbeats periodically","Potential node software issue. Please contact your support representative"
"IPS_SB_MGR-SLOT#","2","NODE_NOT_RESPONDING","[Node [dec], Core [dec]] : Not responding to heartbeats","Node manager is not receiving heartbeat responses from the node","Potential node software issue. Please contact your support representative"
"IPS_SB_MGR-SLOT#","2","NODE_REIMAGE_PREPARE_FAIL","[Node [dec]]: Disk formatting failed during node install","There was a problem during the partitioning of disk and creation of file systems during node install.","Potential node software issue. Please contact your support representative"
"IPS_SB_MGR-SLOT#","2","PORT_SOFTWARE_FAILURE","Port software failure, module [dec] port [dec]","The software servicing the data path on the port has failed","No action is required."
"IPS_SB_MGR-SLOT#","3","COMP_FAILURE","Heartbeat failure in compression engine (error [hex])","The compression engine did not respond to heartbeats, due to some failure. SAN-OS will restart the compression engine to clear the problem.","No action is required."
"IPS_SB_MGR-SLOT#","3","CRYPTO_FAILURE","Heartbeat failure in encryption engine (error [hex])","The encryption engine did not respond to heartbeats, due to some failure. SAN-OS will restart the encryption engine to clear the problem.","No action is required."
"IPS_SB_MGR-SLOT#","3","FIPS_SELF_TEST_FAILURE","[chars] Restarting the octeon...","FIPS self test failed for the algorithm. Restarting the octeon.","No action is required."
"IPS_SB_MGR-SLOT#","4","NODE_NOT_COMPAT_WITH_ADD_ON","svc-node[dec] image is not compatible with svclc image","The svc image on the node is not compatible with the add on image running on the linecard.","Please contact your support representative"
"IPS_SB_MGR-SLOT#","4","NODE_NOT_COMPAT_WITH_CURRENT","svc-node[dec] image is not compatible with current node image","The new svc image is not compatible with the svc image currently running on the node","Please contact your support representative"
"IPS_SB_MGR-SLOT#","4","NODE_NOT_COMPAT_WITH_SUP","svc-node[dec] image is not compatible with system image","The svc image on the node is not compatible with the supervisor image.","Please contact your support representative"
"IPS_SB_MGR-SLOT#","6","SBMGR_EVENT","Sbmgr event: [chars]","This is an event log of sb_mgr relating to a port/node","No action is required."
"IPS","2","ISCSI_IPS_INIT","IPS initialization of [chars] [chars]","IPS initialization failed","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IPS","3","DUP_IPV4_ADDR_DETECTED","duplicate IP address ([chars]) sent from link address ([chars])","Duplicate IPv4 address is configured in the network","No action is required."
"IPS","3","FCIP_FTA_ACCEL_CHAIN_ABORTED","Exch Aborted FC oxid [hex] My oxid [hex] State [chars] Event [chars] CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec] (Internal [hex]:[hex])","FTA Exch being aborted","Informational no action required"
"IPS","3","FCIP_FTA_DATA_SENSE","Sense data with ERA [hex] sent to CH FCID: [hex] CHI: [hex] from FCIP CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]","Sense data with ERA sent","SYSLOGDOC_CONTACT_TAC"
"IPS","3","FCIP_FTA_ERA_35","ERA 0x35 presented to CH FCID: [hex] CHI: [hex] from FCIP CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]","FCIP got an ERA 35","SYSLOGDOC_CONTACT_TAC"
"IPS","3","FCIP_FTA_ERA_38","ERA 0x38 received CH FCID: [hex] CHI: [hex] from FCIP CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec] at tape capacity: [dec] MB","FCIP got an ERA 38","SYSLOGDOC_CONTACT_TAC"
"IPS","3","FCIP_FTA_LOCATE_RBID_MISMATCH","Permanent Error due to Locate RBID Mismatch, CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]","FCIP-FTA got a Permanent Error","Informational no action required"
"IPS","3","FCIP_FTA_PERM_ERR","Permanent Error, ERA [hex] rcvd CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec] sense_byte[2,6]: [[hex], [hex]]","FCIP-FTA got a Permanent Error","Informational no action required"
"IPS","3","FCIP_FTA_RETRY_ERROR","[chars] retries [dec] FC oxid [hex] My oxid [hex] State [chars] Event [chars] CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]","FTA Command timed out","Informational no action required"
"IPS","3","FCIP_LINK_STAT_LOSS_OF_SYNC","[chars]: Loss of Sync ([chars])","FCIP Link Failed with Loss of Sync.","No action is required."
"IPS","3","IPS_CRYPTO_FIPS_FAILED","IPS module [dec] has failed FIPS tests. FIPS info - [chars]","FIPS error occurred in the IPS module.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IPS","3","IPS_EGRESS_PERR","Parity error on dma-bridge egress. Count: [dec]","Parity error occured in dma-bridge egress direction.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IPS","3","IPS_FIPS_MODE_ERROR","IPS FIPS error: [chars]","IPS module FIPS mode error","No action is required."
"IPS","3","IPS_FIPS_TEST_FAILED","IPS FIPS compliance test failed","IPS FIPS compliance test failed","No action is required."
"IPS","3","IPS_INGRESS_PERR","Parity error on dma-bridge ingress. Count: [dec]","Parity error occured in dma-bridge ingress direction.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IPS","3","ISLB_CFS_CLEAR_FAILED","[chars]","An error occurred while clearing the CFS lock. The reason for the failure : [chars]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IPS","3","ISLB_CFS_COMMIT_FAILED","[chars]; [chars]","An error occurred while commiting the cfs config data. The reason for the failure : [chars]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IPS","3","ISLB_CFS_CONFIG_FAILED","[chars]; [chars]","An error occurred while distributing the CFS config data. The reason for the failure : [chars]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IPS","3","ISLB_CFS_LOCK_FAILED","[chars]","An error occurred while acquiring the CFS lock. The reason for the failure : [chars]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IPS","3","ISLB_CFS_MERGE_ACTIVATION_FAILED","[chars]; [chars]","An error occurred while activating merged configuration. The reason for the failure : [chars]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IPS","3","ISLB_CFS_MERGE_CLEARED","[chars]","Merge cleared, reason: [chars]","No action is required."
"IPS","3","ISLB_CFS_MERGE_COMMIT_FAILED","[chars]; [chars]","An error occurred while commiting the cfs merge config data. The reason for the failure : [chars]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IPS","3","ISLB_CFS_MERGE_CONFIG_FAILED","[chars]; [chars]","An error occurred while distributing the CFS merge config data. The reason for the failure : [chars]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IPS","3","ISLB_CFS_MERGE_FAILED","[chars]; [chars]","An error occurred while merging the iSLB CFS fabrics. The reason for the failure : [chars]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IPS","3","ISLB_CFS_MERGE_PRECOMMIT_FAILED","[chars]; [chars]","An error occurred while precommiting merge data. The reason for the failure : [chars]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IPS","3","ISLB_CFS_MERGE_REQ_REJECTED","[chars]","Merge requested rejected, reason: [chars]","No action is required."
"IPS","3","ISLB_CFS_MERGING_CONFIG_DB_FAILED","[chars]; [chars]","An error occurred while merging the config data. The reason for the failure : [chars]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IPS","3","ISLB_CFS_PRECOMMIT_FAILED","[chars]; [chars]","An error occurred while precommiting data. The reason for the failure : [chars]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IPS","3","ISLB_CFS_PWWN_RESV_CLAIM_FAILED","[chars]","PWWN reservation claim failed. The reason for the failure : [chars]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IPS","3","ISLB_CFS_PWWN_RESV_RELEASE_FAILED","[chars]","PWWN reservation release failed. The reason for the failure : [chars]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IPS","3","ISLB_CFS_UNLOCK_FAILED","[chars]","An error occurred while releasing the CFS lock. The reason for the failure : [chars]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IPS","3","ISLB_CFS_VRRP_DIST_FAILED","[chars]","An error occurred while distributing the VRRP CFS runtime data. The reason for the failure : [chars]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IPS","3","ISLB_ZONE_ACTIVATION_FAILED","iSLB zoneset activation returned [hex] for VSAN [dec]","ISLB zoneset activation failed.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IPS","3","ISLB_ZONE_ACTIVATION_RETRY","iSLB zoneset activation returned [hex] for VSAN [dec]","ISLB zoneset activation failed. Zone server busy.","Retry the iSLB zonest activation."
"IPS","3","ISLB_ZONE_NO_ACTIVE_ZONESET","iSLB zoneset activation returned [hex] for VSAN [dec]","ISLB zoneset activation failed. No active zoneset.","Activate a zoneset in the specified VSAN and retry"
"IPS","3","RED_PACKET_DROPS","Congestion detected on GigabitEthernet port (buffer pool size: [dec])","Congestion detected on GigabitEthernet port due to RED threshold limit","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IPS","4","FCIP_FTA_CFG_MISMATCH","[chars]: Mismatch in FCIP Ficon Tape Acceleration configuration with peer","The FCIP Ficon Tape Acceleration configuration does not match with peersconfiguration'","Fix the FCIP Ficon Tape Acceleration configuration to be consistent with the peer"
"IPS","4","FCIP_FTA_VSAN_UPDATE_WARNING","FCIP FICON tape acceleration VSAN update had an error ([chars]) on interface [chars] causing a flap of the interface","The FCIP FICON tape acceleration VSAN configuration experienced an error when disabling and enabling the VSAN over the FCIP tunnel. The FCIP tunnel was disabled and re-enabled as a result of this error to ensure data integrity.","No action is required."
"IPS","4","FCIP_LICENSE_BIND_FAILED","Bind failed for [chars] due to [chars] for license failure; configuration accepted but bind failed","The FCIP configuration was accepted, but the FCIP interface did not bind to a physical interface because the appropriate license was not available. If a license becomes available in the future, this FCIP interface will bind to a physical interface automatically.","Check the license state with 'show license usage' and acquire the necessary FCIP license"
"IPS","4","FCIP_XRCE_LICENSE_FAILED","XRC Acceleration deactivated due to license failure","The XRC Acceleration configuration was accepted, but will remain inactive until a valid license is available. When the appropriate license is installed, XRC accelaration will be activated.","Check the license state with 'show license usage' and acquire the necessary XRC_ACCL license"
"IPS","4","FCIP_XRCE_LICENSE_INSTALLED","XRC Acceleration activated due to valid license","The XRC Acceleration configuration is activated as a valid license has been installed.","No action is required."
"IPS","5","FCIP_BIND_FAILED","Bind failed for [chars] due to [chars] for [chars]","FCIP/ISCSI Interface bind to Ethernet port failed","No action is required."
"IPS","5","FCIP_BPORT_KEEPALIVES_NOT_SUPPORTED","Bport Keepalives not supported for FCIP [chars]","Bport Keepalives not supported in this release","Informational no action required"
"IPS","5","FCIP_BPORT_NOT_SUPPORTED","Bport not supported for FCIP [chars]","Bport not supported in this releas","Informational no action required"
"IPS","5","FCIP_FTA_ALREADY_OFF","FTA Already Off, [chars] VSAN: [dec]","FTA Already Off","Informational no action required"
"IPS","5","FCIP_FTA_ALREADY_ON","FTA Already ON, [chars] VSAN: [dec]","FTA Already ON","Informational no action required"
"IPS","5","FCIP_FTA_CB_DOWN","FTA [chars] is DOWN","FTA is DOWN","Informational no action required"
"IPS","5","FCIP_FTA_CB_UP","FTA [chars], is UP","FTA is UP","Informational no action required"
"IPS","5","FCIP_FTA_DISBAND_GRP_CMD","Disband Group message processed PGID: [chars] CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]","FCIP Disbanded a Group","Informational no action required"
"IPS","5","FCIP_FTA_EST_GRP_CMD","Path Group establised for PGID: [chars] CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]","FCIP established a Path Group","Informational no action required"
"IPS","5","FCIP_FTA_NPORT_PATH_RSCN_CLNUP_PASS1","RSCN Cleanup Pass1 [chars] FCID1: [hex] FCID2: [hex] VSAN: [dec]","Doing RSCN Cleanup, Pass 1","Informational no action required"
"IPS","5","FCIP_FTA_NPORT_PATH_RSCN_CLNUP_PASS2","RSCN Cleanup Pass2 [chars] FCID1: [hex] FCID2: [hex] VSAN: [dec]","Doing RSCN Cleanup, Pass 2","Informational no action required"
"IPS","5","FCIP_FTA_RESIGN_GRP_CMD","Resign group processed for PGID: [chars] CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]","FCIP Resigned a Group","Informational no action required"
"IPS","5","FCIP_FTA_RESP_3490","3490 device discovered by FCIP CH FCID: [hex] CHI: [hex] device at CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]","Device type discovered is 3490","Informational no action required"
"IPS","5","FCIP_FTA_RESP_3590","3590 device discovered by FCIP CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]","Device type discovered is 3590","Informational no action required"
"IPS","5","FCIP_FTA_RESP_NOT_TAPE","Non-tape device discovered by FCIP CH FCID: [hex] CHI: [hex] device at CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]","FCIP discovered a non-tape device","Informational no action required"
"IPS","5","FCIP_FTA_TURN_OFF_LAST_VSAN","FTA turned off for the Last VSAN, [chars] VSAN: [dec]","FTA turned off for the Last Vsan","Informational no action required"
"IPS","5","FCIP_FTA_TURN_OFF_NONLAST_VSAN","FTA turned off for the Non-Last VSAN, [chars] VSAN: [dec]","FTA turned off for the Non-Last Vsan","Informational no action required"
"IPS","5","FCIP_FTA_TURN_ON","Turn ON FTA, [chars] VSAN: [dec]","FTA turned ON","Informational no action required"
"IPS","5","FCIP_FTA_WARNING","FTA Warning :[chars]","Generic FTA Warning","Informational no action required"
"IPS","5","FCIP_FTRA_CFG_MISMATCH","[chars]: Mismatch in FCIP FICON Tape Read Accelerator configuration with peer","The FCIP FICON Tape Read Accelerator configuration does not match with peersconfiguration'","Fix the FCIP FICON Tape Read Accelerator configuration to be consistent with the peer"
"IPS","5","FCIP_IF_CR_DEL","Interface [chars] [chars]","FCIP Interface was Created or Deleted","No action is required."
"IPS","5","FCIP_MODE1_CHANGED_TO_MODE2","Changing mode1 compression to mode2 for [chars], on a MSM/SSN-16 linecard","Change mode1 compression to mode2 on a MSM/SSN-16 linecard","Informational no action required"
"IPS","5","FCIP_NUM_TCP_CONNS_MISMATCH","[chars]: configured for 2 tcp connections but currently operating with 1 connection","Number of configured tcp connections dontmatchnumberofconnectionscurrentlyup'","No action is required."
"IPS","5","FCIP_PEER_CAVIUM","Peer FCIP [chars] is a MSM/SSN-16 linecard","Peer linecard is a MSM/SSN-16","Informational no action required"
"IPS","5","FCIP_PEER_NON_CAVIUM","Peer FCIP [chars] is a non MSM/SSN-16 linecard","Peer linecard is non MSM/SSN-16","Informational no action required"
"IPS","5","FCIP_RA_CFG_MISMATCH","[chars]: Mismatch in FCIP Tape Read Acceleration capability with peer","The FCIP Tape Read Acceleration capability does not match with peersconfiguration'","Fix the FCIP Tape Read Acceleration capability to be consistent with the peer"
"IPS","5","FCIP_SF_NOT_SUPPORTED","Special-Frame not supported for FCIP [chars]","Spl-Frame not supported in this release","Informational no action required"
"IPS","5","FCIP_TA_CFG_MISMATCH","[chars]: Mismatch in FCIP Tape Acceleration configuration with peer","The FCIP Tape Acceleration configuration does not match with peersconfiguration'","Fix the FCIP Tape Acceleration configuration to be consistent with the peer"
"IPS","5","FCIP_TA_ITL_MISMATCH","[chars]: Mismatch in FCIP Write/Tape Acceleration software capability with peer","The FCIP Write/Tape Acceleration software capability does not match with peerssoftwarecapability'","Fix the FCIP software to be consistent with the peer"
"IPS","5","FCIP_TSTAMP_CHK_FAILED","[chars]: Timestamp check failed on ingressing frames","Timestamp between local and remote side exceeds the configured tolerance","No action is required."
"IPS","5","FCIP_UNBIND_FAILED","UNBIND failed for [chars] due to [chars] for [chars]","FCIP/ISCSI Interface UNBIND from Ethernet port failed","No action is required."
"IPS","5","FCIP_WA_CFG_MISMATCH","[chars]: Mismatch in FCIP Write Acceleration configuration with peer","The FCIP Write Acceleration configuration does not match with peersconfiguration'","Fix the FCIP Write Acceleration configuration to be consistent with the peer"
"IPS","5","FCIP_WA_XFER_RDY_ERR","[chars]: FCIP Write Acceleration received XFER-RDY after exhcange cleanup. Host [hex] Target [hex]","FCIP Write/Tape Acceleration received XFER-RDY after exchange cleanup","No action is required."
"IPS","5","FCIP_XRCE_CFG_MISMATCH","[chars]: Mismatch in FCIP XRC Emulator configuration with peer","The FCIP XRC Emulator configuration does not match with peersconfiguration'","Fix the FCIP XRC Emulator configuration to be consistent with the peer"
"IPS","5","IPS_IPACL_LOG_MSG","[chars]","Details of the packet dropped due to ACLs","No action is required."
"IPS","5","IPS_MGR_FEATURE_ENABLE","ips:[dec] iscsi:[dec] fcip:[dec] iscsi-intf-vsan:[dec] ips-lc:[dec]","IPS Manager feature enabled/disabled","No action is required."
"IPS","5","IPS_TCP_PORT_IN_USE","Cannot bringup interface [chars], local port already in use","FCIP and iSCSI interface are trying to use the same local port, please use different ports","No action is required."
"IPS","5","ISCSI_BAD_DATA_DIGEST_CRC","iSCSI ingress data digest error from initiator [chars] alias [chars] S_ID [hex] to D_ID [hex]","ISCSI Ingress Data Digest CRC failed","No action is required."
"IPS","5","ISCSI_CONN_DOWN_BATCH","[chars]: [dec] iSCSI sessions failed in last [chars], reason: [chars]","Number of iSCSI session down during the last time interval","No action is required."
"IPS","5","ISCSI_CONN_DOWN","[chars]: iSCSI session down from initiator [chars] alias [chars] ip [chars] to target [chars], reason: [chars]","ISCSI session goes down","No action is required."
"IPS","5","ISCSI_CONN_UP","[chars]: iSCSI session up from initiator [chars] alias [chars] ip [chars] to target [chars]","ISCSI session comes up and reaches Full-Feature phase","No action is required."
"IPS","5","ISCSI_PORT_FAILOVER","[chars]: iSCSI initiator [chars] alias [chars] ip [chars] target [chars]. FC session failed over to port [chars]","FC session for the iSCSI session failed over to newly active port","No action is required."
"IPS","5","ISCSI_SB_GET_TGT","iSCSI SB get [dec] targets, initiator [chars] alias [chars] ip [chars]","ISCSI FCNS query response","No action is required."
"IPS","5","ISCSI_SESSION_CREATE_FAILURE","[chars]: iSCSI Session initiator [chars] target [chars] create failed. [chars]","ISCSI Session Create failed","No action is required."
"IPS","5","ISCSI_SESSION_CREATE_REDIRECT","[chars]: iSCSI Session initiator [chars] target [chars] redirected to [chars]/[chars]","ISCSI Session Create redirected","No action is required."
"IPS","5","ISCSI_SESSION_REDIRECT_TIMEOUT","iSCSI Session initiator [chars] to [chars] redirected to [chars] timeout","ISCSI Session Redirect timeout","No action is required."
"IPS","5","ISLB_CFS_SESSION_CLEARED","CFS Session Cleared","CFS Session Cleared by user","No action is required."
"IPS","5","LRTP_HDR_FCID_MISMATCH","LRTP header s_id([hex]) d_id([hex]) do not match Inner header s_id([hex]) d_id([hex]) Initiator ([chars]) Target([chars])","The s_id and/or the d_id field in the framesLRTPheaderdoesnotmatchthes_idord_idfieldintheinnerheader'","No action is required."
"IPS","5","PORT_IPCFG_FAILED","Cannot configure IP address for interface [chars]","Cannot configure IPS port IP address","No action is required."
"IPS","5","SB_MGR_CORE_FAILED","Ethernet Processing core [chars] failed due to [chars]","Ethernet Processing Core failed","No action is required."
"IPS","5","SFRAME_ENTITY_ID_MISMATCH","[chars]: special frame profile ID mismatch","Special frame received and destination profile ID does not match local profile ID","No action is required."
"IPS","5","SFRAME_FABRIC_WWN_MISMATCH","[chars]: special frame fabric wwn mismatch","Special frame received and source/destination fabric wwn does not match local destination/ source fabric wwn","No action is required."
"IPS","5","SFRAME_IF_ADMIN_DOWN","[chars]: special frame received if down","Special frame received and interface is admin down","No action is required."
"IPS","5","SFRAME_IF_NOT_ENABLED","[chars]: special frame not enabled","Special frame received and interface special frame configuration is disabled","No action is required."
"IPS","5","SFRAME_INVALID_NONCE","[chars]: special frame response has invalid nonce for FCIP","Special frame response has a different nonce than was originally sent in the special frame","No action is required."
"IPS","5","SFRAME_NOT_RECV","[chars]: special frame was not received by passive-side FCIP","Special frame was not received by the passive-side of the FCIP TCP tunnel within given time period","No action is required."
"IPS","5","SFRAME_RESP_MISMATCH","[chars]: special frame response has byte mismatch for FCIP","Special frame response has a mismiatch in one of the bytes from what was sent from the FCIP special frame sender","No action is required."
"IPS","5","SFRAME_RESP_NOT_RECV","[chars]: special frame response was not received by active-side FCIP","Special frame response was not received by the active-side of the FCIP TCP tunnel within given time period","No action is required."
"IPS","6","FCIP_FTA_READ_ACCEL_STARTED","Read Acceleration started for CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]","FCIP-FTA Read Acceleration started","Informational no action required"
"IPS","6","FCIP_FTA_READ_ACCEL_STOPPED","Read Acceleration stopped for CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec] due to [chars] after [dec] MB reads","FCIP-FTA Read Acceleration stopped","Informational no action required"
"IPS","6","FCIP_FTA_WRITE_ACCEL_STARTED","Write Acceleration started for CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec]","FCIP-FTA Write Acceleration started","Informational no action required"
"IPS","6","FCIP_FTA_WRITE_ACCEL_STOPPED","Write Acceleration stopped for CH FCID: [hex] CHI: [hex] CU FCID [hex] CUI: [hex] DA [hex] VSAN: [dec] due to [chars] after [dec] MB writes","FCIP-FTA Write Acceleration stopped","Informational no action required"
"IPS","7","ISCSI_FCNS_QUERY_REQ","return [hex], wait [dec], VSAN [dec], Init: [chars]","ISCSI FCNS query","No action is required."
"IPS","7","ISCSI_FCNS_QUERY_RESP","result [hex], [dec] targets, wait [dec], Init: [chars]","ISCSI FCNS query response","No action is required."
"IPS","7","ISCSI_NEW_FCNS_QUERY_REQ","return [hex], VSANs [chars], Init: [chars]","ISCSI FCNS query","No action is required."
"IPS","7","ISCSI_NEW_FCNS_QUERY_RESP","result [hex], [dec] entries, [dec] targets, [dec] total targets Init: [chars]","ISCSI FCNS query response","No action is required."
"IPS","7","ISNS_SVR_ERR_RESPONSE","iSNS server returned following error code on iSNS request for interface [chars] : [dec]","ISNS server returned an error for register/deregister request. For select error codes iSNS client would retry and re-register all target nodes corresponding to the interface","No action is required."
"IPV6","2","ALLOC_MEMORY","Memory allocation failed","The IP Configuration Manager failed to allocate a block of dynamic memory.","No action is required."
"IPV6","3","FILE_WRITE_FAILED","Writing to file [chars] failed - error: [chars]","Writing to a file failed probably due to no space.","Ipv6"
"IPV6","3","INIT_FAILED","Initialization failed. Component [chars]","The service failed to start. The failure occurred while initializing the component [chars].","Show processes to check the status of the other processes, debug the specified component."
"IPV6","4","DAD_FAILED_EVENT","Duplicate address detection failed for [chars] on [chars]","Duplicate address detection for IP address failed.","Ipv6"
"IPV6","6","CONFIG_EVENT","IP Configuration Msg: [chars]","Configuration message that needs to be logged.","No action is required."
"IPV6","6","INTERFACE_DELETED","The interface [chars] has been deleted","The specified interface has been deleted. The service will delete all the configuration on that interface.","No action is required."
"IPV6","6","INTERFACE_EVENT","IP address [chars] [chars] on interface [chars]","The IP address [chars] has been successfully [chars] on the interface [chars].","No action is required."
"IPV6","6","ROUTE_NOT_ACTIVE","The [chars] is not active","The specified route is successfully configured but currently is not active.","Check that the route is correct and the outgoing interface is operationally up."
"IPV6","6","STARTING","IP configuration Manager started","The IP Configuration Manager service has successfully started.","No action is required."
"IP","1","DHCP_CLIENT_FAILED","dhcp-client failed to get the ip address","Dhcp-client failed to get the ip from server, probably due to server lease unavailability or cable disconnectivity.","Ip"
"IP","2","ALLOC_MEMORY","Memory allocation failed","The IP Configuration Manager failed to allocate a block of dynamic memory.","No action is required."
"IP","3","FILE_WRITE_FAILED","Writing to file [chars] failed - error: [chars]","Writing to a file failed probably due to no space.","Ip"
"IP","3","INIT_FAILED","Initialization failed. Component [chars]","The service failed to start. The failure occurred while initializing the component [chars].","Show processes to check the status of the other processes, debug the specified component."
"IP","4","DAD_FAILED_EVENT","Duplicate address detected for [chars] on [chars]","Duplicate address detected for IP address.","Ip"
"IP","6","CONFIG_EVENT","IP Configuration Msg: [chars]","Configuration message that needs to be logged.","No action is required."
"IP","6","DHCP_CLIENT_SUCCESS","dhcp_client got ip address:[chars],netmask:[chars] for mgmt interface,got from server:[chars]","Dhcp-client is able to get the ip address from server,","No action is required."
"IP","6","INTERFACE_DELETED","The interface [chars] has been deleted","The specified interface has been deleted. The service will delete all the configuration on that interface.","No action is required."
"IP","6","INTERFACE_EVENT","IP address [chars] [chars] on interface [chars]","The IP address [chars] has been successfully [chars] on the interface [chars].","No action is required."
"IP","6","ROUTE_NOT_ACTIVE","The [chars] is not active","The specified route is successfully configured but currently is not active.","Check that the route is correct and the outgoing interface is operationally up."
"IP","6","STARTING","IP configuration Manager started","The IP Configuration Manager service has successfully started.","No action is required."
"ISAPI-SLOT#","0","INVISTA_EMERG","[chars]","Isapi-invista software messages","No action is required."
"ISAPI-SLOT#","0","MSM_EMERG","[chars]","Isapi software messages","No action is required."
"ISAPI-SLOT#","0","NSP_EMERG","[chars]","Isapi-nsp software messages","No action is required."
"ISAPI-SLOT#","0","SSM_EMERG","[chars]","Isapi software messages","No action is required."
"ISAPI-SLOT#","0","SSN_EMERG","[chars]","Isapi software messages","No action is required."
"ISAPI-SLOT#","1","INVISTA_ALERT","[chars]","Isapi-invista software messages","No action is required."
"ISAPI-SLOT#","1","MSM_ALERT","[chars]","Isapi software messages","No action is required."
"ISAPI-SLOT#","1","NSP_ALERT","[chars]","Isapi-nsp software messages","No action is required."
"ISAPI-SLOT#","1","SSM_ALERT","[chars]","Isapi software messages","No action is required."
"ISAPI-SLOT#","1","SSN_ALERT","[chars]","Isapi software messages","No action is required."
"ISAPI-SLOT#","2","INVISTA_CRIT","[chars]","Isapi-invista software messages","No action is required."
"ISAPI-SLOT#","2","MSM_CRIT","[chars]","Isapi software messages","No action is required."
"ISAPI-SLOT#","2","NSP_CRIT","[chars]","Isapi-nsp software messages","No action is required."
"ISAPI-SLOT#","2","SSM_CRIT","[chars]","Isapi software messages","No action is required."
"ISAPI-SLOT#","2","SSN_CRIT","[chars]","Isapi software messages","No action is required."
"ISAPI-SLOT#","3","INVISTA_ERROR","[chars]","Isapi-invista software messages","No action is required."
"ISAPI-SLOT#","3","MSM_ERROR","[chars]","Isapi software messages","No action is required."
"ISAPI-SLOT#","3","NSP_ERROR","[chars]","Isapi-nsp software messages","No action is required."
"ISAPI-SLOT#","3","SSM_ERROR","[chars]","Isapi software messages","No action is required."
"ISAPI-SLOT#","3","SSN_ERROR","[chars]","Isapi software messages","No action is required."
"ISAPI-SLOT#","4","INVISTA_WARN","[chars]","Isapi-invista software messages","No action is required."
"ISAPI-SLOT#","4","MSM_WARN","[chars]","Isapi software messages","No action is required."
"ISAPI-SLOT#","4","NSP_WARN","[chars]","Isapi-nsp software messages","No action is required."
"ISAPI-SLOT#","4","SSM_WARN","[chars]","Isapi software messages","No action is required."
"ISAPI-SLOT#","4","SSN_WARN","[chars]","Isapi software messages","No action is required."
"ISAPI-SLOT#","5","INVISTA_NOTICE","[chars]","Isapi-invista software messages","No action is required."
"ISAPI-SLOT#","5","MSM_NOTICE","[chars]","Isapi software messages","No action is required."
"ISAPI-SLOT#","5","NSP_NOTICE","[chars]","Isapi-nsp software messages","No action is required."
"ISAPI-SLOT#","5","SSM_NOTICE","[chars]","Isapi software messages","No action is required."
"ISAPI-SLOT#","5","SSN_NOTICE","[chars]","Isapi software messages","No action is required."
"ISAPI-SLOT#","6","INVISTA_INFO","[chars]","Isapi-invista software messages","No action is required."
"ISAPI-SLOT#","6","MSM_INFO","[chars]","Isapi software messages","No action is required."
"ISAPI-SLOT#","6","NSP_INFO","[chars]","Isapi-nsp software messages","No action is required."
"ISAPI-SLOT#","6","SSM_INFO","[chars]","Isapi software messages","No action is required."
"ISAPI-SLOT#","6","SSN_INFO","[chars]","Isapi software messages","No action is required."
"ISAPI-SLOT#","7","INVISTA_DEBUG","[chars]","Isapi-invista software messages","No action is required."
"ISAPI-SLOT#","7","MSM_DEBUG","[chars]","Isapi software messages","No action is required."
"ISAPI-SLOT#","7","NSP_DEBUG","[chars]","Isapi-nsp software messages","No action is required."
"ISAPI-SLOT#","7","SSM_DEBUG","[chars]","Isapi software messages","No action is required."
"ISAPI-SLOT#","7","SSN_DEBUG","[chars]","Isapi software messages","No action is required."
"ISCM","2","APBR_CORRUPT","RISE APBR: in Corrupt State, RS IP: [chars], port: [dec], Proto: [dec], nhop IP: [chars], slot ID: [dec], vlan: [dec]. Reason: [chars].","RMAP","ACL cannot be completely deleted."
"ISCM","2","LICENSE_EXPIRED","RISE License: LAN_ENTERPRISE_SERVICES_PKG license has expired. RISE feature is being disabled.","License or grace-period has expired.","Take steps to renew license. Feature will be disabled."
"ISCM","2","LICENSE_MISSING","RISE License: LAN_ENTERPRISE_SERVICES_PKG does not exist.","License does not exist when attempting to enable RISE feature.","Acquire license or grace-period permission."
"ISCM","3","APBR_ACLMGR_ERROR","RISE APBR: ACL was not [chars], apbr payload: [chars].","Acl was not created/deleted.","Check TCAM resource limit, and the sys admin."
"ISCM","3","APBR_INGRESS_INT_NOT_FOUND","RISE APBR: cantfindtheingressinterfaceforRSIP:[chars].'","7K cannot find a route to the real server.","Check real server network reachablity in the current switch."
"ISCM","3","APBR_PURGE_ERROR","RISE APBR: Purge failure, slot id: [dec].","PBR entriles for RISE cannot be deleted cleanly.","Manually delete pbr entries."
"ISCM","3","APBR_RPM_ERROR","RISE APBR: RPM returns internal error, rpm resp status: [dec], apbr payload: [chars].","Rmap step was not completed.","Check TCAM resource limit, or rmap collision on the same interface, and the sys admin."
"ISCM","3","RHI_ROUTE_ISSUE","RISE RHI: slot [dec] route [chars] cannot be [chars]. Reason:[chars].","URIB dropped this RHI request. See reason string with the following possibilities: 1. SVI for data vlan [dec] does not exist. 2. SVI for data vlan [dec] is down. 3. urib issues.","Take corrective action per the reason."
"ISCM","4","APBR_MAX_LIMIT","RISE APBR: Reached max apbr entries [dec] per RISE. slot id: [dec].","PBR entriles for RISE cannot be deleted cleanly.","Manually delete pbr entries."
"ISCM","4","APBR_PBR_DISABLED","RISE APBR: feature PBR Disabled.","APBR will not function correctly without pbr feature.","Manually enable pbr feature."
"ISCM","4","DISCOVERY_CHANNEL_DOWN","RISE Channel down, slot id: [dec], Reason: [chars]","See reason string in the error message with the following possibilities: 1. Error in bootstrap/health-monitorying response. 2. Timed out while waiting for bootstrap/health-monitoring response. 3. Failed to send bootstrap/health-monitorying message. 4. Control VLAN interface is not operational. 5. RISE interface [chars] is not operational. 6. RISE interface [chars] does not have control VLAN [dec] as trunk member. 7. Control VLAN ([dec]) interface does not have valid IP. 8. RISE port channel po [dec] has no member ports. 9. Failed to send vlan-group. 10. RISE IP [chars] is already assigned to another service, slot id [dec].","Take corrective action per the reason"
"ISCM","4","ISSU_PRE_UPGRADE_TIMEOUT","RISE ISSU: pre-upgrade timed out, reason: [chars].","See the reason.","Try again with the upgrade."
"ISCM","4","ISSU_UNEXPECTED_SLOT_MSG","RISE ISSU: unexpected msg from slot [dec], opcode: [dec].","Application should not send msg during ISSU. iSCM will ignore.","No action is required."
"ISCM","4","LICENSE_EXPIRING","RISE License: LAN_ENTERPRISE_SERVICES_PKG license will expiry in [dec] days [dec] hours [chars]econds.","License or grace-period expiration warning.","Take steps to renew license. Prepare for feature disable."
"ISCM","5","TRANSPORT_ISSUE","RISE Transport: slot [dec] failed to send, reason : [chars].","See the reason.","Check the network connectivity and the appliance status."
"ISNS","2","ISNS_CFS_OPERATION_FAILED","iSNS CFS [chars] failed","ISNS CFS operation failed","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"ISNS","2","ISNS_INIT","iSNS initialization of [chars] [chars]","ISNS initialization failed","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IVR","2","AUTOLEARN_ACTION_FAIL","failure happens during constructing virtual dynamic pfcid table","This can happen if failure happens during building, distributing or committing the virtual dynamic pfcid table","Please 1. check the fabric connection or 2. check current virtual user-configured pfcid entries and internally assigned virtual fcid entries for possible conflict"
"IVR","2","AUTOLEARN_FEATURE_NOT_SUPPORT","some switches:[chars] dontsupportautolearn'","This can happen if some switches doesntsupportthevirtualpfcidautolearnfeature'","Please upgrade the unsupported switches"
"IVR","2","CFS_PEER_LOST_WITHIN_SESSION","CFS peer with switch wwn [chars] was lost in the middle of an active CFS session. Abort the CFS session and re-enter the configuration changes","Due to port flaps, link outages, switch restart etc. a CFS peer switch of IVR was lost. The current configuration changes would not be applied to this peer until the peer merges with this switch. The CFS merge may fail if the configuration at the lost peer conflicts with the changes made in this session. Also, IVR auto topology could be out of sync. with this peer. It is recommended that the user abort this CFS session using ivr abort command and then re-enter the configuration changes.","No action is required."
"IVR","2","DEVICE_FCID_REWRITE_FAILURE","Failure while programming FCID rewrite entries for pWWN [chars] on incoming VSAN [dec]. Device may not be able to communicate with its peer devices, failure reason code: [hex]","Failed to program FCID rewrite entries probably because the hardware ran out of FCID rewrite entries. This can happen if there are too many devices in Inter-VSAN zone or too many local VSANs in VSAN topology","Reduce the number of devices involved in IVR in the active IVR zoneset. Also, reduce the number of redundant transit VSANs, if any"
"IVR","2","DEVICE_STATE_INCOMPATIBLE_WITH_NAT_MODE","State for device with port WWN [chars] could not be restored because it was incompatible with the current NAT mode([dec]). This probably happened because NAT mode was modified without completely deactivating the active IVR zoneset","This probably happened because NAT mode was modified without completely deactivating the active IVR zoneset","The switch needs to be rebooted"
"IVR","2","DEVICE_VSAN_REWRITE_FAILURE","Failure while programming VSAN rewrite entries for pWWN [chars] on incoming VSAN [dec]. Device may not be able to communicate with its peer devices","Failed to program VSAN rewrite entries probably because the hardware ran out of VSAN rewrite entries. This can happen if there are too many devices in Inter-VSAN zone or too many local VSANs in VSAN topology","Reduce the number of domains involved in IVR by moving the members of active IVR zoneset to fewer switches. Also, reduce the number of redundant transit VSANs, if any"
"IVR","2","INTEROP_MODE_2_OR_3_BF_FAILED","[chars] VSAN [dec] Virtual Domain [chars]","Build Fabric (BF) failed in VSAN [dec]. The BF was initiated in order to remove an unused virtual domain [dec] from the fcdomain list in that VSAN. The virtual domain still remains in the fcdomain list and hence it would not be available in that VSAN for assignment.","Perform a manual build fabric using fcdomainsinterfaceifyouwouldliketoremovetheunusedvirtualdomain(s)fromthefcdomainlist.'"
"IVR","2","INTEROP_MODE_2_OR_3_RDI_FAILED","VSAN [dec], requested domain [chars], received domain [chars] sWWN [chars]. Return Code [chars]","Request Domain Identifier (RDI) command to allocate virtual domain [dec] failed in VSAN [dec]. Received another domain [chars] instead. IVR-members connected to third-party switch may not participate in IVR communications. It is likely that the domain requested in the RDI command is already in use.","Reassign the domains so that the domain requested via RDI does not overlap with any existing domain in that VSAN."
"IVR","2","IVR_DISABLE_FAILED","Inter-VSAN Routing disable failed for reason: [chars]","Inter-VSAN Routing disable failed for reason: [chars]. Cleanup might not have completed","Deactivate ivr zoneset and disable ivr again. If that fails, then the ivr process would terminate itself in 5 minutes"
"IVR","2","IVZS_ACTIVATION_FAILED_RETRYING","Inter-VSAN zoneset activation failed in VSAN [dec] : [chars]. retrying after [dec] seconds","Inter-VSAN zoneset activation failed in VSAN [dec] : [chars]. This could be an intermittent regular zoneset activation error. The activation will be retried in [dec] seconds.","No action is required."
"IVR","2","NO_LICENSE_SHUTDOWN","Inter-VSAN Routing is shutting down.","License required for continued IVR operation is not available. Hence IVR is shutting down","Install appropriate license for IVR services and then enable IVR again."
"IVR","2","NO_LICENSE_WARNING","Inter-VSAN Routing would shutdown in [dec] seconds.","License required for continued IVR operation is not available. Unless the required license is installed IVR would shutdown in [dec] seconds. IVR configurations would be lost.","Install appropriate license for IVR services to continute to operate uninterrupted within [dec] seconds"
"IVR","2","PERSISTENT_VIRTUAL_FCID_CONFLICT_WITH_AUTOLEARN","Persistent virtual fcid and dynamic pfcid entries","This can happen if conflict happens during persistent virtual domain, or virtual fcid entry configuration.","Please assign a non-conflict persistent virtual domain or fcid entry with current dynamic entries"
"IVR","2","PERSISTENT_VIRTUAL_FCID_UNAVAILABLE","to vsan [dec] because the configured persistent virtual domain/fcid could not be assigned","This can happen if the virtual domain/fcid configured by the user is - a) Already in use (either by IVR or a real switch) b) Not allowed due to interop mode or allowed domain list","Please make sure that the configured virtual domain/fcid is allowed and available for use"
"IVR","2","VIRTUAL_DOMAIN_CONFLICT","In VSAN [dec] virtual domain [dec] from native VSAN [dec] conflicts with native VSAN [dec] for the same virtual domain","Currently advertised virtual domain [dec] in VSAN [dec] is native to VSAN [dec]. This switch has learned of a device that is member of active IVR zone and has the same domain ID, but belongs to a different native VSAN. This device would not be advertised in that VSAN until the domain conflict is resolved.","No action is required."
"IVR","2","VIRTUAL_FCID_UNAVAILABLE","to vsan [dec] because the internally generated FCID conflicts with fcid assigned to WWN [chars]. Please configure fcid for WWN [chars] too","This can happen if the virtual domain/fcid internally configured is already in use by another active device","Please assign a different persistent virtual fcid by CLI command"
"IVR","3","AAM_MODE_CANNOT_CHANGE","AAM mode cannot be changed. Might cause the fabric NAT mode inconsistency","Could be caused by ivr NAT is not enable","No action is required."
"IVR","3","AAM_MODE_DEREGISTERED_FAILED","Abstract ACL Manager (AAM) mode deregister failed. Error code is [chars].","Abstract ACL Manager (AAM) mode deregister failed","No action is required."
"IVR","3","AAM_MODE_REGISTERED_FAILED","Abstract ACL Manager (AAM) register failed. Error code is [chars].","Abstract ACL Manager (AAM) register failed","No action is required."
"IVR","3","ACL_ERROR","ACL API, [chars], failed with error [chars]","IVR invoked ACL API and received the error code. [chars] describes the API and [chars] specifies the error.","No action is required."
"IVR","3","ACL_PERMIT_ENTRY_ERROR","ACL permit entry update on interface [chars] failed for reason: [chars]","ACL could not program permit entries for IVR traffic. [chars] describes the interface named and [chars] describes the system error message from ACL. IVR traffic coming from the interface may be dropped.","If the problem persists, please contact TAC, or your reseller for support."
"IVR","3","ACL_PLOGI_ENTRY_ERROR","PLOGI capture entry update in slot [dec] failed for reason: [chars]","ACL could not program IVR PLOGI could not be programmed. slot[dec] describes the line card slot number and [chars] describes the system error message. PLOGI and its response may be dropped because ivr process cannot capture those frames.","No action is required."
"IVR","3","AFID_CONFLICT","[chars]","AFID configuration is different at different ivr-enabled switches in the same VSAN. Change AFID configuration (auto mode) or vsan topology configuration (user mode) to make it consistent","No action is required."
"IVR","3","CFS_INVALID_PAYLOAD_RECEIVED","Inter-VSAN process received invalid payload from CFS","Inter-VSAN process received invalid payload from CFS.","No action is required."
"IVR","3","CLEAR_FAILED","[chars]","An error occurred while clearing the lock. The reason for the failure : [chars]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IVR","3","COMMIT_FAILED","[chars]","An error occurred while committing configuration. The reason for the failure : [chars]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IVR","3","COMMIT_PARTIALLY_FAILED","[chars]","An error occurred while committing configuration. Configuration could not be committed on some switches. The reason for the failure : [chars]. Configuration can be inconsistent in the fabric.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IVR","3","COMMIT_REJECTED","[chars]","Commit request received from remote switch is rejected. The reason for the failure: [chars]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IVR","3","DDAS_LOCK_TIMER_EXPIRED","IVR database lock is released, as device-alias commit/abort notification is not received in the expected time frame.","When device-alias sends the validation request, IVR database is locked and a timer is started. For any reason, if device-alias commit/abort notification is not received within the expected time frame, the lock timer gets expired and the lock is released. If device-alias commmit notification is received after the lock is released, the changes are not applied and this could cause inconsistency between IVR and device-alias.","No action is required."
"IVR","3","DEVICE_NOT_PREENT_IN_FB_DB_FICON","Device with port WWN [chars] could not be exported to VSANs [chars] because its native switch is not present in the current active fabric binding database of those VSANs.","This happens if ficon is enabled on VSANs [chars] and native switch of device with port WWN [chars] is not present in the current active fabric binding database of those VSANs. This is a requirement for ficon compliance.","No action is required."
"IVR","3","DEVICE_ON_WRONG_NATIVE_AFID_VSAN","Device with port WWN [chars] (FCID:[chars], native VSAN [dec] native AFID [dec]) may not be exported to other VSANs (for Inter-VSAN zoning) because it has come online in VSAN [dec] AFID [dec]","Device has come online on a AFID/VSAN different from the configured native AFID/VSAN","No action is required."
"IVR","3","DEVICE_ON_WRONG_NATIVE_VSAN","Device with port WWN [chars] (FCID:[chars], native VSAN [dec]) may not be exported to other VSANs (for Inter-VSAN zoning) because domain [hex] exists in VSAN [dec]","Device has come online on a VSAN different from the configured native VSAN or the device does not satisfy unique domain criteria.","No action is required."
"IVR","3","DM_ERROR","Domain Manager API, [chars], failed with error [hex]","IVR invoked DM API and received the error code. [chars] describes the API and 0x[hex] specifies the error.","No action is required."
"IVR","3","DOMAIN_DISALLOWED_IN_INTEROP","Device with port WWN [chars] and FCID [chars] may not be able to participate in Inter-VSAN zone since domain [dec] is disallowed in the interop mode for VSAN [dec]","VSAN interop modes place restrictions on what domain ranges are allowed. This domain is out of the range allowed for this interop mode. See the Cisco MDS 9000 Family Configuration Guide for details on the domain range limitations.","Change the domain of the switch to which this IVR zone member is connected to so that it is within the allowed domain list for the interop mode. The domain identifier can be statically assigned using fcdomain interface. You can also configure a range of domains allowed in a VSAN using the fcdomains'allowed-domains'interface.'"
"IVR","3","DOMAIN_UNAVAILABLE","Device with port WWN [chars] and FCID [chars] may not be able to participate in Inter-VSAN zone since domain [dec] is already assigned in VSAN [dec]","Device with port WWN [chars] and FCID [dec] may not be able to participate in Inter-VSAN zone since domain [dec] is already assigned in VSAN [dec].","No action is required."
"IVR","3","FC2_ERROR","FC2 API [chars] failed with error [hex] for [chars]","IVR invoked FC2 API for [chars] socket and received the error code. [chars] describes the API and 0x[hex] specifies the error.","No action is required."
"IVR","3","FCID_NAT_MODE_CANNOT_CHANGE","IVR NAT mode cannot be changed. Might cause the fabric NAT mode inconsistency","Could be caused by active zoneset, pending activation /deactivation or non-empty device list","No action is required."
"IVR","3","FCID_REWRITE_REQUEST_TO_ACL_FAILED","fcid rewrite [chars] request vsan [dec] did [chars] sid [chars] failed:[chars]([hex]).","This happens when either after IVR retried the request few times or ACL experienced error while processing the request.","No action is required."
"IVR","3","INTERNAL_ERROR","Internal error: [chars]","IVR process encountered a general error, one that does not fall in any of the categories. [chars] describes the error and its context.","No action is required."
"IVR","3","INVALID_ZONE_MEMBER_PROP_INTEROP_MODE_2_3","unsupported member/zone properties in interop mode 2 or 3 [chars]","Inter-VSAN member properties incompatible with interop mode vsan","No action is required."
"IVR","3","IVR_NAT_OFF_IS_SAB","Fcid-nat must be enabled before IVR zoneset activation for Sabre platform.","Fcid-nat must be enabled before IVR zoneset activation for Sabre platform.","No action is required."
"IVR","3","IVZ_ACTIVATION_FAILED_VSAN","Inter-VSAN zoneset [chars] activation failed in VSAN [dec]","Inter-VSAN zoneset activation failed failed in VSAN.","No action is required."
"IVR","3","IVZ_ACTIVATION_FAILED","Inter-VSAN zoneset [chars] activation failed","Inter-VSAN zoneset activation failed.","No action is required."
"IVR","3","IVZ_DEACTIVATION_FAILED_VSAN","Inter-VSAN zoneset [chars] deactivation failed in VSAN [dec]","Inter-VSAN zoneset deactivation failed in VSAN.","No action is required."
"IVR","3","IVZ_DEACTIVATION_FAILED","Inter-VSAN zoneset [chars] deactivation failed","Inter-VSAN zoneset deactivation failed.","No action is required."
"IVR","3","LOCK_FAILED","[chars]","An error occurred while acquiring the lock. The reason for the failure : [chars]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IVR","3","MERGE_ACTIVATION_FAILED","[chars]","An error occurred while activating merged configuration. The reason for the failure : [chars]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IVR","3","MERGE_FAILED","reason is [chars]","An error occurred while merging configuration. The reason for the failure : [chars]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IVR","3","MTS_ERROR","MTS message transmission failed with error [dec]","IVR process unsuccessfully tried to send a MTS message. MTS error number is specified in [dec].","No action is required."
"IVR","3","NS_ERROR","FCNS API, [chars], failed with error [hex]","IVR invoked FCNS API and received the error code. [chars] describes the API and 0x[hex] specifies the error.","No action is required."
"IVR","3","PSS_CFG_RESTORE_ERROR","Configuration restoration for [chars] failed with error [hex]","IVR read the saved configuration and encountered an error while rebuilding the runtime configuration. [chars] describes the configuration which the process tried to restore and 0x[hex] is the system err code.","No action is required."
"IVR","3","PSS_ERROR","PSS operation [chars] returned error: [hex]","[chars] specifies the context where the failure occurred and 0x[hex] specifies the error.","No action is required."
"IVR","3","PSS_RTDB_RESTORE_ERROR","Runtime database restoration for [chars] failed with error [hex]","IVR read the saved runtime database and encountered an error while rebuilding the runtime database. [chars] describes the runtime database which the process tried to restore and 0x[hex] is the system error code.","No action is required."
"IVR","3","QOS_IOD_UNDROP_REQUEST_TO_ACL_FAILED","qos iod undrop request vsan [dec] did [chars] failed:[chars].","This happens when either after IVR retried the request few times or ACL experienced error while processing the request.","No action is required."
"IVR","3","RIB_ERROR","RIB API, [chars], failed with error [hex]","IVR invoked RIB API and received the error code. [chars] describes the API and 0x[hex] specifies the error.","No action is required."
"IVR","3","ROUTE_REQUEST_TO_ACL_FAILED","route [chars] request vsan [dec] domain [dec] failed:[chars].","This happens when either after IVR retried the request few times or ACL experienced error while processing the request.","No action is required."
"IVR","3","TOPOLOGY_COMPUTATION_FAILED","Inter-VSAN Topology computation has failed due to: [chars]","Inter-VSAN Topology has failed due to [chars]. Possible reasons are (a) Number of AFID/VSAN combination is more than te maximum supported value of 128, or (b) Number of ivr-enabled switches is more than the maximum supported value of 128","No action is required."
"IVR","3","UNEXPECTED_MTS_MSG","Unexpected MTS message, opcode [dec], is received","IVR process received unexpected MTS event. MTS opcode is specified in [dec].","No action is required."
"IVR","3","UNLOCK_FAILED","[chars]","An error occurred while releasing the lock. The reason for the failure : [chars]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IVR","3","VSAN_SEGMENTED","[chars]","VSAN is segmented. VSAN is removed from the topology graph and hence no Inter-VSAN traffic can flow through this VSAN.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"IVR","3","ZS_POLICY_IS_DENY_NO_ACTIVE_ZS","Default zone behavior policy is deny on VSAN [dec] and there is no active zoneset","Default zone behavior is deny and there is no active zoneset. Inter-VSAN zone members may not be able communicate in this VSAN.","No action is required."
"IVR","3","ZS_POLICY_IS_PERMIT_NO_FORCE","Default zone behavior policy is permit on VSAN [dec] and the force option is off","Default zone behavior is permit and the force option is off. Inter-VSAN zoneset activation on this VSAN has failed.","No action is required."
"IVR","3","ZS_POLICY_IS_PERMIT_ZS_DEACTIVATED","Default zone behavior policy is permit on VSAN [dec] and regular zoneset deactivated","Default zone behavior is permit and regular zoneset is deactivated. Inter-VSAN zone members may not be able to communicate.","No action is required."
"IVR","4","AUTO_TOPOLOGY_UPDATE_DISCARDED","[chars]","Received auto topology update is discarded due to conflicts","No action is required."
"IVR","4","FCID_REWRITE_REQUEST_TO_ACL_FAILED_AND_RETRYING","fcid rewrite [chars] request vsan [dec] did [chars] sid [chars] failed:[chars]([hex]). Retrying the request again.","This happens when either any of the linecards being upgraded or ACL experienced error while processing the request.","No action is required."
"IVR","4","PERSISTENT_VIRTUAL_DOMAIN_MERGE_CONFLICT","[chars]","Merge failed due to conflict in the persistent virtual domain configuration","No action is required."
"IVR","4","IVR_VDC_FORCEFUL_CLEANUP","IVR was removed with VDC delete/reload/suspend, Forceful cleanup was triggered.","IVR was removed from an N7K switch via VDC delete/reload, which triggered a forceful cleanup.","No action is required."
"IVR","4","IVR_REMOVED_PENDING_CFG","IVR was removed while there were still pending IVR configurations. Forceful cleanup was triggered and the pending configurations were not saved.","IVR was removed from an N7K switch via VDC delete/reload, which triggered a forceful cleanup. The pending IVR configurations were not saved.","No action is required."
"IVR","4","PERSISTENT_VIRTUAL_FCID_MERGE_CONFLICT","[chars]","Merge failed due to conflict in the persistent virtual fcid configuration","No action is required."
"IVR","4","QOS_IOD_UNDROP_REQUEST_TO_ACL_FAILED_AND_RETRYING","qos iod undrop request vsan [dec] did [chars] failed:[chars]. Retrying the request again.","This happens when either any of the linecards being upgraded or ACL experienced error while processing the request.","No action is required."
"IVR","4","ROUTE_REQUEST_TO_ACL_FAILED_AND_RETRYING","route [chars] request vsan [dec] domain [dec] failed:[chars]. Retrying the request again.","This happens when either any of the linecards being upgraded or ACL experienced error while processing the request.","No action is required."
"IVR","4","UNKNOWN_NATIVE_VSAN","Unknown native VSAN for the virtual domain [dec] in VSAN [dec] local native VSAN for the same virtual domain is [dec]","Could not determine native VSAN of the currently advertised virtual domain [dec] in VSAN [dec]. This switch has learned of a device that is member of active IVR zone has the same domain ID, and belongs to native VSAN [dec]. This device would not be advertised in that VSAN until the native VSAN information is resolved.","No action is required."
"IVR","5","AAM_MODE_DEREGISTERED","Abstract ACL Manager (AAM) mode has been deregistered","Abstract ACL Manager (AAM) mode has been deregistered","No action is required."
"IVR","5","AAM_MODE_REGISTERED","Abstract ACL Manager (AAM) mode has been registered","Abstract ACL Manager (AAM) mode has been registered","No action is required."
"IVR","5","FCID_NAT_MODE_ACTIVATED","FCID network address translation (NAT) mode has been activated","FCID network address translation (NAT) mode has been activated","No action is required."
"IVR","5","FCID_NAT_MODE_DEACTIVATED","FCID network address translation (NAT) mode has been deactivated","FCID network address translation (NAT) mode has been deactivated","No action is required."
"IVR","5","IVR_ASSERTION_FAILED","Unexpected assertion failure in File [chars] at Line [dec]","An assertion failed in IVR code","No action is required."
"IVR","5","IVZS_ACTIVATION_RETRYING","Inter-VSAN zoneset activation did not go through because of [chars], retrying in VSAN [dec] after [dec] seconds","Inter-VSAN zoneset activation failed because of [chars] in VSAN [dec]. This could be an intermittent regular zoneset activation error. The activation will be retried in [dec] seconds.","No action is required."
"IVR","5","IVZS_WAITING_FOR_LOWEST_SWWN","Waiting for lowest switch WWN Inter-VSAN enabled switch in VSAN [dec]","Only lowest switch WWN Inter-VSAN enabled switch adds the Inter-VSAN zones to the regular active zoneset in a VSAN. This local switch is not the lowest sWWN switch in VSAN [dec]","No action is required."
"IVR","5","IVZ_ACTIVATED_VSAN","Inter-VSAN zoneset [chars] activated in VSAN [dec]","Inter-VSAN zoneset activated in VSAN[dec].","No action is required."
"IVR","5","IVZ_ACTIVATED","Inter-VSAN zoneset [chars] activated","Inter-VSAN zoneset activated[dec].","No action is required."
"IVR","5","IVZ_CLEANUP_DONE_BY_TIMER","Inter-VSAN clean-up is not done after waiting for 5 minutes","Inter-VSAN related configuration might not be cleaned up before the ivr process is terminated","If the problem persists, you may have to reboot your switch to clean up the old IVR configuration"
"IVR","5","IVZ_CLEANUP_DONE","Inter-VSAN clean-up is done","Inter-VSAN related configuration is cleaned up before exiting.","No action is required."
"IVR","5","IVZ_DEACTIVATED_VSAN","Inter-VSAN zoneset [chars] deactivated in VSAN [dec]","Inter-VSAN zoneset deactivated in VSAN[dec].","No action is required."
"IVR","5","IVZ_DEACTIVATED","Inter-VSAN zoneset [chars] deactivated","Inter-VSAN zoneset deactivated[dec].","No action is required."
"IVR","5","IVZ_PARTIALLY_ACTIVATED","Inter-VSAN zoneset [chars] partially activated","Inter-VSAN zoneset activated[dec].","Check if it is successful in all VSANs by doing show IVR zoneset status."
"IVR","5","IVZ_PARTIALLY_DEACTIVATED","Inter-VSAN zoneset [chars] partially deactivated","Inter-VSAN zoneset deactivated[dec].","Check if it is successful in all VSANs by doing show IVR zoneset status."
"IVR","5","LICENSE_CHECKIN_FAILED","Failed to checkin [chars] license: Err=[chars]","Failed to checkin [chars] license","No action is required."
"IVR","5","SERVICE_GROUP_ACTIVATED","Inter-VSAN Service Group has been activated","Inter-VSAN Service Group has been activated.","No action is required."
"IVR","5","SERVICE_GROUP_DEACTIVATED","Inter-VSAN Service Group has been deactivated","Inter-VSAN Service Group has been deactivated.","No action is required."
"IVR","5","VSAN_NO_LONGER_SEGMENTED","[chars]","VSAN is no longer segmented. VSAN is added back to the topology graph and hence Inter-VSAN traffic can now flow through this VSAN.","No action is required."
"IVR","5","VSAN_TOPOLOGY_ACTIVATED","Inter-VSAN Topology has been activated","Inter-VSAN Topology has been activated.","No action is required."
"IVR","6","DRAV_ASYNC_DOMAIN_RELEASE","[chars]","DRAV FSM has unconditionally released a domain due to conflict after a fabric merge. The details are in [chars]","No action is required."
"IVR","6","DRAV_CRITICAL_RETRY_EXCEED","[chars]","DRAV FSM frames are attempted to be resent. The details are in [chars]","No action is required."
"IVR","6","DRAV_DOMAIN_ALLOC","Virtual domain [dec] for Native AFID: [dec] Native VSAN [dec]","A virtual domain indicated by [dec] has been reserved for a device with native AFID [dec] and native VSAN [dec]","No action is required."
"IVR","6","DRAV_DOMAIN_RELEASE","Virtual domain [dec] for Native AFID: [dec] Native VSAN [dec]","A virtual domain indicated by [dec] has been released used by devices with native AFID [dec] and native VSAN [dec]","No action is required."
"IVR","6","DRAV_TOPO_UPDATE","[chars]","DRAV FSM Topology has been updated as indicated by [chars]","No action is required."
"IVR","6","LICENSE_VALID","A valid license for Inter-VSAN Routing has been obtained","A valid license for Inter-VSAN Routing has been obtained","No action is required."
"IVR","7","CFS_REQ_RCVD","[chars]","CFS request is received. The WWN of the switch originated this request and the rr-token of the request are provided in the syslog message.","No action is required."
"IVR","7","CFS_RESP_SENT","[chars]","CFS response is sent. The rr-token of the corresponding request and the status are provided in the syslog message","No action is required."
"L2FMC-SLOT#","0","L2FMC_CLI_INIT_FAILED","CLI library initialization failed!","L2FMC failed to initialize CLI infrastructure's backend library. This is a fatal error.","No action is required."
"L2FMC-SLOT#","0","L2FMC_TIMER_INIT_FAILED","Timer subsystem initialization failed!","L2FMC failed to initialize timer library. This is a fatal error.","No action is required."
"L2FMC-SLOT#","2","L2FMC_MEM_ALLOC","Memory allocation failed. [chars]","Memory allocation failed. This is a critical failure","No action is required."
"L2FMC-SLOT#","2","L2FMC_VLAN_NOT_FOUND","VLAN [dec] not found in L2FMC database!","L2FMC failed to find VLAN [dec] in its database. L2 MAC learning & aging on VLAN [dec] may be affected.","No action is required."
"L2FMC-SLOT#","5","L2FMC_GLBL_AGE_CONFIG_FAIL","Global age value configuration to [dec] seconds failed!","L2FMC failed to configure global default age to [dec] seconds.","No action is required."
"L2FMC-SLOT#","5","L2FMC_VLAN_AGE_CONFIG_FAIL","VLAN Age configuration to [dec] seconds failed!","L2FMC failed to configure age for VLAN [dec] to [dec] seconds.","No action is required."
"L2FMC-SLOT#","6","L2FMC_GLBL_AGE_CONFIGURED","Global age value configured to [dec] seconds.","L2FMC has successfully configured global default age to [dec] seconds.","No action is required."
"L2FMC-SLOT#","6","L2FMC_INITIALIZED","Internal state created [chars]","L2FMC has created its internal state stateless/stateful [chars].","No action is required."
"L2FMC-SLOT#","6","L2FMC_VDC_CREATED","VDC [dec] created","Request to create VDC [dec] in L2FMC was successful.","No action is required."
"L2FMC-SLOT#","6","L2FMC_VDC_REMOVED","VDC [dec] Removed","L2FMC has successfully removed VDC [dec] from its databases.","No action is required."
"L2FMC-SLOT#","6","L2FMC_VDC_VLAN_CREATED","VLAN [dec] created","L2FMC has added VLAN [dec].","No action is required."
"L2FMC-SLOT#","6","L2FMC_VDC_VLAN_REMOVED","VLAN [dec] removed from VDC [dec]","L2FMC has successfully removed VLAN [dec] from VDC [dec].","No action is required."
"L2FMC-SLOT#","6","L2FMC_VLAN_AGE_CONFIGURED","Age configured for VLAN [dec] to [dec] seconds.","L2FMC has successfully configured age for VLAN [dec] to [dec] seconds.","No action is required."
"L2FM","0","L2FM_CLI_INITIALIZATION_FAILED","CLI library initialization failed!","Failed to initialize CLI infrastructure's backend library. This is a fatal error.","No action is required."
"L2FM","0","L2FM_VDC_GWMAC_GET_FAILED","Failed to get gwmac for VDC","Failed to get gwmac for VDC.","No action is required."
"L2FM","0","L2FM_WRITE_TO_PSS_FAILED_IN_PREVIOUS_INCARNATION","PSS Write Failed in pervious incarnation. Stateful restart not possible","PSS Write Failed in pervious incarnation. Stateful restart not possible","No action is required."
"L2FM","1","L2FM_CRDCFG_ERROR","L2fm queried Card config for slot info and it has returned error. The slot may not have been added correctly","No action is required.","L2fm"
"L2FM","1","L2FM_LINE_FULL_CONDITION_STRING","Unable to insert the MAC as hardware lines are full","No action is required.","L2fm"
"L2FM","1","L2FM_LINE_FULL_CONDITION","Unable to insert the MAC as hardware lines are full","No action is required.","L2fm"
"L2FM","1","L2FM_ORIB_SENDS_INCORRECT_IFIDX","Incorrect ifidx received from Orib. Please check mac [chars] vlan [dec]","L2fm has received a mac insert/delete from Orib with incorrect ifidx. Please check otv mac entries","No action is required."
"L2FM","1","L2FM_OWNER_NOT_FOUND","Error : fe owner not found for mac entry [chars] in age notif sent from slot = [dec], fe = [dec]","L2fm has received an age notification from the linecard but does not have the mac owner in its database","No action is required."
"L2FM","1","L2FM_SDB_NOT_FLUSHED","Error : [dec] mac entries have not flushed from l2fm sdb","Due to an internal error l2fm has not written mac entries to its sdb","No action is required."
"L2FM","1","L2FM_SMAC_DUP_FOUND","Duplicate static mac found in secondary vlan. P-VLAN:[dec] S-VLAN:[dec] MAC:[chars]","Duplicate static mac found in secondary vlan. P-VLAN:[dec] S-VLAN:[dec] MAC:[chars]","No action is required."
"L2FM","1","L2FM_WRITE_TO_PSS_FAILED","Failed to write to PSS err [chars]","Failed to write to PSS err [chars]","No action is required."
"L2FM","2","L2FM_AGING_TIME_SET_FAILED","Failed to set age time [dec] for vlan [dec]","Failed to set age time [dec] for vlan [dec].","No action is required."
"L2FM","2","L2FM_CFS_OUT_OF_ORDER","Error: Received Message for STATIC MAC INSERT/DELETE as Out Of Order from vpc peer due to congestion. Please check mac programming for Router macs.Flap interface-vlans if necessary to correct the programming","Messages over peer-link could be received out of order due to congestion","No action is required."
"L2FM","2","L2FM_GLBL_AGING_TIME_SET_FAILED","Failed to set global age time [dec]","Failed to set global age time [dec]","No action is required."
"L2FM","2","L2FM_SMAC_INS_FAILED","Failed to insert static mac for VLAN:[dec] MAC:[chars] IfIndex:[hex] Slot:[dec]","No action is required.","L2fm"
"L2FM","2","L2FM_UPDATE_LOST_HINTS","mac [hex]:[hex]:[hex]:[hex]:[hex]:[hex] updated by slot [dec] fe_index [dec], from [hex] to [hex], with [hex] new hints and loosing %08 old_hints. stack trace: [chars]","An update from MTM looks inconsistent with the previous state","No action is required."
"L2FM","4","L2FM_MAC_MOVE","Mac [chars] in vlan [dec] has moved from [chars] to [chars]","Mac [string] in vlan [dec] has moved from [string] to [string]","No action is required."
"L2FM","5","L2FM_VLAN_MODE_CHANGE_TO_NON_CONV","Vlan [dec] has been internally changed to non conversational mode on SVI CREATE","Change vlan learning mode to non conversational mode on SVI CREATE","No action is required."
"L2FM","5","L2FM_VLAN_MODE_REVERTED_BACK","Vlan [dec] has been internally changed to user configured learning mode on SVI DELETE. Mac entries installed non-optimally due to SVI up will get removed from all FEs once ages out","Change vlan learning mode to user configured value on SVI DELETE","No action is required."
"L2FM","6","L2FM_DYN_MAC_INS_FAILED","Dynamic mac insertion failure!fail_cnt: [dec] Slot:[dec]","Failed to insert dynamic macs fail_cnt:[dec] for Slot:[Slot]","No action is required."
"L2FM","6","L2FM_MTS_SEND_FAILED","Failed to send MTS message errno [hex] opcode [dec]","No action is required.","L2fm"
"L2MCAST-SLOT#","0","L2MCAST_CLI_INIT_FAILED","CLI library initialization failed!","L2MCAST failed to initialize CLI infrastructure's backend library. This is a fatal error.","No action is required."
"L2MCAST-SLOT#","0","L2MCAST_TIMER_INIT_FAILED","Timer subsystem initialization failed!","L2MCAST failed to initialize timer library. This is a fatal error.","No action is required."
"L2MCAST-SLOT#","2","L2MCAST_MAC_FULL_LC","Failed to insert entry in MAC table for FE [dec] swidx [dec] ([hex]) with err ([chars]). To avoid possible multicast traffic loss, disable OMF. Use the configuration CLI: 'no ip igmp snooping optimise-multicast-flood'","Failed to program the MAC table. MAC table line full for this entry","No action is required."
"L2MCAST-SLOT#","2","L2MCAST_VLAN_NOT_FOUND","VLAN [dec] not found in L2MCAST database!","L2MCAST failed to find VLAN [dec] in its database. L2 MAC learning & aging on VLAN [dec] may be affected.","No action is required."
"L2MCAST-SLOT#","2","L2MCAST","Memory allocation failed. [chars]","Memory allocation failed. This is a critical failure","No action is required."
"L2MCAST-SLOT#","3","L2MCAST_HW_INSTALL_FAIL","Hw install failed for vlan [dec] ([dec], [chars], [chars]) entry!","L2MCAST failed to insert bd, g, s entry in hardware. Igmp snooping may not be effective on vlan for that group and source","No action is required."
"L2MCAST-SLOT#","6","L2MCAST_HW_INSTALL_FAIL","Hw install failed for vlan [dec] ([dec], [chars], [chars]) entry!","L2MCAST failed to insert bd, g, s entry in hardware. Igmp snooping may not be effective on vlan for that group and source","No action is required."
"L2MCAST-SLOT#","6","L2MCAST_INITIALIZED","Internal state created [chars]","L2MCAST has created its internal state stateless/stateful [chars].","No action is required."
"L2MCAST-SLOT#","6","L2MCAST_VDC_CREATED","VDC [dec] created","Request to create VDC [dec] in L2MCAST was successful.","No action is required."
"L2MCAST-SLOT#","6","L2MCAST_VDC_REMOVED","VDC [dec] Removed","L2MCAST has successfully removed VDC [dec] from its databases.","No action is required."
"L2MCAST-SLOT#","6","L2MCAST_VDC_VLAN_CREATED","VLAN [dec] created","L2MCAST has added VLAN [dec].","No action is required."
"L2MCAST-SLOT#","6","L2MCAST_VDC_VLAN_REMOVED","VLAN [dec] removed from VDC [dec]","L2MCAST has successfully removed VLAN [dec] from VDC [dec].","No action is required."
"L3VM","5","FP_TPG_CREATE","Fabricpath topology [dec] created","FP-Topology created","No action is required."
"L3VM","5","FP_TPG_DELETE","Fabricpath topology [dec] deleted","FP-Topology deleted","No action is required."
"L3VM","5","FP_TPG_INTF_DOWN","Interface [chars] down in fabricpath topology [dec] [chars]","Interface in a FP-Topology went down","No action is required."
"L3VM","5","FP_TPG_INTF_UP","Interface [chars] up in fabricpath topology [dec]","Interface in a FP-Topology is up","No action is required."
"LACP","3","GENERAL_ERROR","[chars]","General error","No action is required."
"LACP","3","LACP_SUSPEND_HALF_DUPLEX_PORT","Port [chars] is in half duplex mode. suspend port","LACP is not supported in half duplex mode. Suspend port","No action is required."
"LACP","3","LACP_SUSPEND_MINLINK","LACP port [chars] of port-channel [chars] is suspended as min-link requirement not met.","LACP suspend ports due to min-link","No action is required."
"LACP","3","LACP_UPGRADE_READY_FAILED","Upgrade ready failed.","Upgrade ready event failed because atleast one port channel member is in intermediate state.","No action is required."
"LACP","3","PACKET_TRANSMIT_ERR","[chars]: Could not send LACP packet err=[dec]","There was an error in sending LACP packet","No action is required."
"LACP","3","SYN_COLL_DIS_EN","[chars] [[chars]]: SYNC, COLLECT and DISTRIBUTE flags enabled too early by partner","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","No action is required."
"LACP","3","SYSTEM_MAC_ERR","[chars]: Could not get system mac[[chars]]","There was an error in acquiring system mac from VDC Mgr","No action is required."
"LACP","5","LACP_DISABLED","LACP Disabled","LACP Service Disabled","No action is required."
"LACP","5","LACP_DOES_NOT_MEET_MINLINK_REQ","LACP port-channel [chars] is brought down as min-link requirement not met.","LACP port-channel down as min-link requirement not met","No action is required."
"LACP","5","LACP_ENABLED","LACP Enabled","LACP Service Enabled","No action is required."
"LACP","5","LACP_MEETS_MINLINK_REQ","LACP port-channel [chars] meets min-link requirement. Reint port-channel","LACP port-channel meets min-link requirement","No action is required."
"LACP","5","LACP_REMOTE_NOTIFY_SUCCESS","Remote notify event.","Remote notify event was successful.","No action is required."
"LACP","5","LACP_SUSPEND_INDIVIDUAL","LACP port [chars] of port-channel [chars] not receiving any LACP BPDUs suspending (individual) port","LACP suspend individual ports","No action is required."
"LACP","5","LACP_UPGRADE_READY_SUCCESS","Upgrade ready successful.","Upgrade ready event is successful as all port channel members are in steady state.","No action is required."
"LACP","5","PORT_PRIORITY_CHANGED","[chars]: LACP port priority changed from [dec] to [dec]","LACP port priority has been changed","No action is required."
"LACP","5","SYSTEM_PRIORITY_CHANGED","LACP system priority changed from [hex] to [hex]","LACP system priority has been changed","No action is required."
"LC-FCFWD","3","ERROR","[chars]","Lc_fcfwd encountered an error","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"LC-QOS","3","ERROR","[chars]","Lc_qos_mgr encountered an error","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"LC-SPAN","3","ERROR","[chars]","Lc_span_mgr encountered an error","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"LC_CFG-SLOT#","2","LC2_CPU_ERRORS","[chars], Total IC [dec], DC [dec], Tag [dec], MBit [dec], SBit [dec], I30 [dec]","LC CPU Cache errors.","No action is required."
"LC_CFG-SLOT#","2","LC_CFG_ABORT","registration aborted with code [dec]","Process lc_cfg_mgr aborted registration","No action is required."
"LC_CFG-SLOT#","2","LC_CFG_EXITED","exited with code [dec]","Process lc_cfg_mgr exited","No action is required."
"LC_MNT_MGR-SLOT#","2","LC_MNT_MGR_ERROR","[chars]","Lc_mnt_mgr syslog message","No action is required."
"LC_PORT_CHANNEL-SLOT#","0","HW_FAILURE","fatal error in configureing [chars]: [chars]","Fatal hardware error in port-channel configuration","Reset the module"
"LC_PORT_CHANNEL-SLOT#","0","IDX_FULL","D_IDX table full (current [dec], new [dec], total [dec])","Programming error in port-channel configuration","Reset the module"
"LC_PORT_CHANNEL-SLOT#","1","MALLOC_FAILED","cannot allocate memory (size [dec])","No enough memory","No action is required."
"LC_PORT_CHANNEL-SLOT#","3","LC_PORT_CHANNEL_ERROR","[chars]","General error","No action is required."
"LC_PORT_CHANNEL-SLOT#","3","LC_PORT_CHANNEL_IDXMAP_FAILURE","could not lookup port index for interface [chars]","Could not look up port index","No action is required."
"LC_PORT_MGR-SLOT#","2","LC_MTS_ERROR","An MTS error has occurred in ([chars]) with the following conditions: opc=[dec] ssap=[hex] dsap=[hex] syserr=[hex]","This is a software error in message communication between two applications.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"LC_RDL","3","SYSLOG_ALLOC_FAIL",": [chars]","RDL malloc failed : [chars]","No action is required."
"LC_RDL","3","SYSLOG_CONTEXT_ERR",": [chars] [dec]","RDL context error: [chars] [dec]","No action is required."
"LC_RDL","3","SYSLOG_ERR",": [chars]","RDL syslog errors : [chars]","No action is required."
"LC_RDL","3","SYSLOG_EXIT",": [chars]","RDL exiting on errors : [chars]","No action is required."
"LC_RDL","3","SYSLOG_INIT_FAIL",": [chars] [chars]","RDL Init Failed: [chars] [chars]","No action is required."
"LC_RDL","3","SYSLOG_MTS_ERR",": [chars]","RDL MTS errors : [chars]","No action is required."
"LC_RDL","3","SYSLOG_MTS_REG_FAILED",": [dec] [dec]","RDL context error: [dec] [dec]","No action is required."
"LC_RDL","6","SYSLOG_DEBUG_1",": [chars] [hex]","RDL Debug logs: [chars] [dec]","No action is required."
"LC_RDL","6","SYSLOG_DEBUG_2",": [chars] [hex]","RDL Debug logs: [chars] [dec]","No action is required."
"LC_RDL","6","SYSLOG_INFO",": [chars]","RDL Debug logs: [chars]","No action is required."
"LC_RDL","6","SYSLOG_RESP_RCVD",": [chars] [dec]","RDL context error: [chars] [dec]","No action is required."
"LDAP","2","LDAP_PROGRAM_EXIT","LDAP daemon exiting: [chars]","LDAP daemon is exiting.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"LDAP","3","LDAP_ERROR_MESSAGE","[chars]","LDAP Error Message","No action is required."
"LDAP","5","LDAP_MONITOR_STATUS","[chars] [chars]","Notifying Ldap server monitor status change","No action is required."
"LDAP","5","LDAP_SERVER_STATUS","[chars] server [chars] with port [dec] status has changed from [chars] to [chars]. Server was in previous-state for [chars], and total dead time of the server is [chars]","Notifying Ldap server status change","No action is required."
"LDAP","6","LDAP_MESSAGE","[chars]","LDAP Message","No action is required."
"LDP","5","LDP_DISABLED","LDP Disabled","MPLS_LDP Service Disabled","No action is required."
"LDP","5","LDP_ENABLED","LDP Enabled","MPLS_LDP Service nabled","No action is required."
"LED_MGR-SLOT#","3","LED_MGR_EXITED","LED Manager application exited (syserr = [dec], errno = [dec])","LED Manager application exited","No action is required."
"LED_MGR-SLOT#","3","LED_MGR_SELECT_ERR","LED Manager application call to select() returned [dec], (errno = [dec])","LED Manager application received error from select()","No action is required."
"LIBBASE_SVC","2","IT_NEXUS_MAX_INTERFACE_LIMIT_REACHED","[chars] cannot be bound for site [chars], as the interfaces reached the maximum flow limit","IT Load Balancing failed","No action is required."
"LIBBASE_SVC","2","LOG_ERR_BASE_SVC_TOM_ABORTED","SME Cluster [chars] Message Id: [hex] aborted","An SME Cluster Message was aborted by the Cluster process","No action is required."
"LIBBASE_SVC","4","FCR_VER2_NOT_ENABLED","FCR Version2 is not enabled. May affect flows. Please enable fc-redirect version2","FCR Version2 not enabled","No action is required."
"LIBBASE_SVC","5","FLOW_NOT_ALLOWED","Flow [chars] <-","Flow creation failed","No action is required."
"LIBBASE_SVC","5","IT_NEXUS_FAILURE","[chars]. [chars] bind failure. Reason: [chars]: [hex]","IT Nexus bind failed","No action is required."
"LIBBASE_SVC","5","IT_NEXUS_OPTIMUM_INTERFACE_LIMIT_REACHED","Interface [chars] exceeded the optimum flow limit","Iterface Flow Limit","No action is required."
"LIBGD","2","GD_ACCESS_FAILED","Guardian Failed to access reg for [chars]","Guardian Access failed","No action is required."
"LIBGD","2","GD_CATASTROPHIC","Guardian catastrophic failure: [chars]","Guardian catastrophic error","No action is required."
"LIBGD","2","GD_INTR","Guardian Interrupt occurred: [chars]","Interrupt occurred on the Guardian","No action is required."
"LIBGD","2","SHUTDOWN","Guardian software process exiting: [chars]","Guardian shutting down","No action is required."
"LIBGD","3","EN_DATA_FAILED","Guardian enable port failed for inst:[dec] port:[dec]","Guardian Enable port failed for the guardian","No action is required."
"LIBGD","5","STARTING","Guardian process starting","Guardian process is being started","No action is required."
"LIBGD","6","DIS_DATA","Guardian disable port done for inst:[dec] port:[dec]","Disabled port successfully for guardian","No action is required."
"LIBGD","6","EN_PORT","Guardian enable port done for inst:[dec] port:[dec]","Enabled port for the Guardian","No action is required."
"LIBGD","6","HW_INIT","GuardianHW initialization has been done for inst: [dec] port: [dec]","Guardian HW initializtion has been called[dec]","No action is required."
"LIBIFMGR","5","ALL_COUNTERS_CLEARED","All interface counters cleared by user","All interface counters cleared by user.","LOG_STD_SH_TECH_ACTION"
"LIBIFMGR","5","INTF_COUNTERS_CLEARED","Interface [chars]counters cleared by user","Interface counters cleared by user.","LOG_STD_SH_TECH_ACTION"
"LICMGR","0","LOG_LIC_GRACE_EXPIRED","Grace period expired for feature [chars].","Unlicensed feature [chars] has exceeded itsgracetimeperiod.Applicationsusingwillbeshutdownimmediately.'","Please install the license file to continue using the feature."
"LICMGR","1","LOG_LIC_LICENSE_EXPIRED","Evaluation license expired for feature [chars].","The named feature has exceeded itsevaluationtimeperiod.Applicationsusingthelicensewillbeshutdownafteragraceperiod.'","Please install the license file to continue using the feature."
"LICMGR","1","LOG_LIC_LICENSE_EXPIRY_WARNING_ALERT","Evaluation license for feature [chars] will expire in [dec] days.","Feature [chars] has very limited time for expiry. Feature will expire in [dec] days and will be shut down.","Please install the license file to continue using the feature."
"LICMGR","1","LOG_LIC_NO_LIC_ALERT","No license(s) present for feature [chars]. Application(s) running in grace-period and will be shut down in [dec] days.","Feature [chars] has not been licensed. The feature will work for a grace period of [dec] days after which application(s) using the feature will be shut down.","Please install the license file to continue using the feature."
"LICMGR","2","LOG_LICAPP_EXPIRY_WARNING","Application [chars] evaluation license [chars] expiry in [dec] days.","Application [chars1] will exceed itsevaluationtimeperiodin[dec]daysandwillbeshutdownafteragraceperiodunlessapermanentlicensef orfeature[chars2]isinstalled.'","Please install the license file to continue using the feature."
"LICMGR","2","LOG_LICAPP_NO_LIC","Application [chars] running without [chars] license, shut down in [dec] days.","Application [chars1] has not been licensed. The application will work for a grace period of [dec] days after which it will be shut down unless a license file for feature [chars2] is installed.","Please install the license file to continue using the feature."
"LICMGR","2","LOG_LIC_EXIT","License manager exiting: [chars]","License manager exiting.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"LICMGR","2","LOG_LIC_INVALID_SERVER_LINE","License file [chars] contains invalid 'SERVER' line. Contact TAC","Invalid SERVER line in license file.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"LICMGR","2","LOG_LIC_NO_LIC","No license(s) present for feature [chars]. Application(s) shut down in [dec] days.","Feature [chars] has not been licensed. The feature will work for a grace period of [dec] days after which application(s) using the feature will be shut down.","Please install the license file to continue using the feature."
"LICMGR","2","LOG_LIC_NVRAM_DISABLED","Licensing NVRAM is not available. Grace period will be disabled: [chars]","The Supervisor NVRAM block may have a hardware problem and may need to be replaced","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"LICMGR","2","LOG_LIC_VENDOR_DOWN","License file contains invalid 'SERVER' line. Vendor daemon down","Vendor daemon is down","Licensing"
"LICMGR","3","LOG_LIC_FILE_MISSING","License file(s) missing for feature [chars].","One or more license files for feature [chars] are missing and must be reinstalled.","Please install the license file to continue using the feature."
"LICMGR","3","LOG_LIC_INVALID_HOSTID","Invalid license hostid VDH=[chars] for feature [chars].","Feature [chars2] has a license with an invalid license hostid VDH=[chars1]. This can occur if a supervisor card with licensed features for one switch is installed on another switch.","No action is required."
"LICMGR","3","LOG_LIC_MESSAGE_ERROR","could not handle message: [chars] of type [dec] from addr [dec]:[dec].","Could not handle a IPC message [chars] of type [dec1] sent by a component running on node [dec2] with sap [dec3].","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"LICMGR","3","LOG_LIC_SERVER_DOWN","License Server Down [dec]","A connection to the license server was lost.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"LICMGR","3","LOG_LIC_SPROM_LIC","Feature [chars] issued [dec] licenses without a valid license file.","Feature [chars] has been licensed [dec] times without a valid license file. This means one or more license files are missing for feature [chars] and must be reinstalled.","Please install the license file to continue using the feature."
"LICMGR","3","LOG_LIC_TOO_MANY_LIC","Only [dec] licenses are supported for [chars] feature, where as [dec] licenses are installed.","More licenses are installed than allowed.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"LICMGR","4","LOG_LIC_LICENSE_EXPIRY_WARNING","Evaluation license for feature [chars] will expire in [dec] days.","Feature [chars] will exceed itsevaluationtimeperiodin[dec]daysandwillbeshutdown.'","Please install the license file to continue using the feature."
"LICMGR","6","LOG_CHECKPOINT_CREATED","created during license expiry.","When a license expires, auto checkpoint is created to prevent configuration loss.","Rollback can be done to the created checkpoint when a new license is installed."
"LICMGR","6","LOG_LIC_FEATURE_CLEARED","Cleared [dec] license(s) for feature [chars].","Uninstalled [dec] license(s) for feature [chars].","Use the showlicenseusage'commandtoverifythislicensefeatureremoval.'"
"LICMGR","6","LOG_LIC_FEATURE_INSTALLED","Installed [dec] license(s) for feature [chars].","Installed [dec] license(s) for feature [chars].","Use the showlicenseusage'commandtoverifythislicensefeatureinstallation.'"
"LICMGR","6","LOG_LIC_LICENSE_CLEARED_ALL","Cleared all licenses.","Cleared all license files.","No action is required."
"LICMGR","6","LOG_LIC_LICENSE_CLEARED","Cleared license file [chars].","Uninstalled the named license file.","Use the showlicense'commandtoverifythislicenseremoval.'"
"LICMGR","6","LOG_LIC_LICENSE_INSTALLED","Installed license file [chars].","Installed the named license file.","Use the showlicense'commandtoverifythislicenseinstallation.'"
"LIM","2","IF_CRITICAL_FAILURE","(Debug syslog)Critical failure: [chars], [chars]","There was a critical failure in the component.","Please follow instructions on the syslog."
"LIM","2","IF_DOWN_ERROR_DISABLED","Interface [chars] is down (Error disabled. Reason:[chars])","The interface encountered an error while configuring it","Collect more information about failed interface using command showportinternalallinterface[char]'.Inmostcases,youcanrecoverusinga'shutdown'followeda'noshutd own'ontheinterfaceorremovingandre-insertingthefibreopticcable.'"
"LIM","2","IF_DOWN_LINK_FAILURE_CRIT","Interface [chars] is down (Link failure)","The physical link has gone down","Ensure that the cable is connected and the remote end is not shut down"
"LIM","2","SEQ_TIMEOUT","Component [chars] timed out on response to opcode [chars] ([chars])","Some component did not respond to a request in stipulated time.","None"
"LIM","2","SYSLOG_LIM_CRITICAL","Critical failure: [chars]","There was a critical failure in the component.","Please collect system tech-support"
"LIM","3","IF_DOWN_CHANNEL_ERR_DISABLED","Interface [chars] is down (Channel error disabled)","This interface belongs to a PortChannel and the PortChannel is error disabled","Perform shut'and'noshutdown'onthePortChannelinterfacethatitbelongsto'"
"LIM","3","IF_ERROR_VLANS_REMOVED","VLANs [chars] on Interface [chars] are removed from suspended state.","The VLANs on an interface are being removed from the suspended state","No action is required."
"LIM","3","IF_ERROR_VLANS_SUSPENDED","VLANs [chars] on Interface [chars] are being suspended. (Reason: [chars])","The VLANs on an interface are being suspended due to some protocol action","No action is required."
"LIM","3","IF_SFP_ALARM","Interface [chars], [chars]","There was an alarm on the transceiver module","Please do show interface transceiver details to obtain more information"
"LIM","3","IF_SFP_ERROR","Interface [chars], [chars]","There was an error on the transceiver module","Please do show interface transceiver details to obtain more information"
"LIM","3","IF_UNSUPPORTED_TRANSCEIVER","Transceiver on interface [chars] is not supported","The transceiver for the interface specified in the error message is not a Cisco supported module","Replace the module with a compatible transceiver. If the transceiver was purchased from Cisco, please contact Cisco TAC to get the transceiver replaced"
"LIM","3","IF_XCVR_ALARM","Interface [chars], [chars]","There was an alarm on the transceiver module","Please do show interface transceiver details to obtain more information"
"LIM","3","IF_XCVR_ERROR","Interface [chars], [chars]","There was an error on the transceiver module","Please do show interface transceiver details to obtain more information"
"LIM","4","IF_NON_QUALIFIED_TRANSCEIVER","Non-qualified transceiver on interface [chars] was detected","The transceiver for the interface specified has not been qualified on this platform for this software release","Replace the module with a supported transceiver. Contact Cisco TAC to get platform transceiver qualification details"
"LIM","4","IF_SFP_WARNING","Interface [chars], [chars]","There was an warning on the transceiver module","Please do show interface transceiver details to obtain more information"
"LIM","4","IF_XCVR_WARNING","Interface [chars], [chars]","There was an warning on the transceiver module","Please do show interface transceiver details to obtain more information"
"LIM","5","IF_ADMIN_UP","Interface [chars] is admin up [chars]","Interface is admin up","No action is required."
"LIM","5","IF_BANDWIDTH_CHANGE","Interface [chars],bandwidth changed to [chars] Kbit","Bandwidth of the interface (port channel) has changed and this change is updated","No action is required."
"LIM","5","IF_DOWN_ADMIN_DOWN","Interface [chars] is down (Administratively down)","Interface has been configured to be administratively down","Perform noshutdown''"
"LIM","5","IF_DOWN_CFG_CHANGE","Interface [chars] is down(Config change)","FCIP interface temporarily down due to reconfiguration","No action is required."
"LIM","5","IF_DOWN_CHANNEL_ADMIN_DOWN","Interface [chars] is down (Channel admin down)","This interface belongs to a PortChannel and the PortChannel is configured to be administratively down","Perform noshutdown'onthePortChannelinterfacethatitbelongsto'"
"LIM","5","IF_DOWN_CHANNEL_MEMBERSHIP_UPDATE_IN_PROGRESS","Interface [chars] is down (Channel membership update in progress)","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","Retry the configuration again"
"LIM","5","IF_DOWN_DOMAIN_ADDR_ASSIGN_FAILURE_ISOLATION","Interface [chars] is down (Isolation due to domain id assignment failure)","Isolated due to a failure while assigning a domain","No action is required."
"LIM","5","IF_DOWN_DOMAIN_INVALID_RCF_RECEIVED","Interface [chars] is down (Isolation due to invalid fabric reconfiguration)","Invalid RCF received","No action is required."
"LIM","5","IF_DOWN_DOMAIN_MANAGER_DISABLED","Interface [chars] is down (Isolation due to domain manager disabled)","Isolated due to domain manager being disabled","No action is required."
"LIM","5","IF_DOWN_DOMAIN_MAX_RETRANSMISSION_FAILURE","Interface [chars] is down (Isolation due to domain manager other side not responding)","Remote end domain manager not responding","No action is required."
"LIM","5","IF_DOWN_DOMAIN_OTHER_SIDE_EPORT_ISOLATED","Interface [chars] is down (Isolation due to domain other side eport isolated)","Isolating this interface due to the remote end being isolated","No action is required."
"LIM","5","IF_DOWN_DOMAIN_OVERLAP_ISOLATION","Interface [chars] is down (Isolation due to domain overlap)","Isolated due to domain overlap","No action is required."
"LIM","5","IF_DOWN_ELP_FAILURE_ISOLATION","Interface [chars] is down (Isolation due to ELP failure)","ELP failed on the interface","Check the output of showportinternalinfo'inthe'ELPfailurereason'field'"
"LIM","5","IF_DOWN_EPP_FAILURE","Interface [chars] is down (Error Disabled - EPP Failure)","Trunk protocol failed","showportinternalevent-historymsgs'willindicatethetrunkprotocolexchangestodeterminewhyitfailed'"
"LIM","5","IF_DOWN_ESC_FAILURE_ISOLATION","Interface [chars] is down (Isolation due to ESC failure)","ESC failed on the interface","Check the output of showportinternalevent-history'todeterminetheESCprotocolexchangestodeterminehowitfailed'"
"LIM","5","IF_DOWN_ETH_IF_DOWN","Interface [chars] is down(Tunnel port src interface down)","Ethernet link to which the FCIP interface is bound is down","Ensure that the ethernet cable is connected, the interface is administratively enabled"
"LIM","5","IF_DOWN_ETH_LINK_DOWN","Interface [chars] is down(Tunnel port src interface link down)","Ethernet link to which the FCIP interface is bound is down","Ensure that the ethernet cable is connected and the remote end is also active"
"LIM","5","IF_DOWN_FCOT_NOT_PRESENT","Interface [chars] is down (FCOT not present)","The FCOT has been removed","Insert an FCOT"
"LIM","5","IF_DOWN_FCOT_VENDOR_NOT_SUPPORTED","Interface [chars] is down (Error disabled - Fcot vendor not supported)","Fcot inserted is not a supported one","Please contact customer support for a list of authorized transceiver vendors"
"LIM","5","IF_DOWN_HW_FAILURE","Interface [chars] is down (Hardware Failure)","The moduleshardwarehasfailed'","Collect more information about failed module using command showmoduleinternalallmodule''"
"LIM","5","IF_DOWN_INACTIVE","Interface [chars] is down (Inactive)","The port VSAN has been suspended or deleted","Assign a new active port VSAN to the interface"
"LIM","5","IF_DOWN_INCOMPATIBLE_ADMIN_MODE","Interface [chars] is down (Error disabled - Incompatible admin port mode)","The configured mode is not supported on this interface","Perform a showportinternalinfo'todeterminethelistofmodessupportedonthisinterface'"
"LIM","5","IF_DOWN_INCOMPATIBLE_ADMIN_RXBBCREDIT","Interface [chars] is down (Error disabled - Incompatible admin port rxbbcredit)","The configured receive B2B credit size is not supported","Get the allowed receive B2B credit size from showportinternalinfo''"
"LIM","5","IF_DOWN_INCOMPATIBLE_ADMIN_RXBUFSIZE","Interface [chars] is down (Error disabled - Incompatible admin port rxbufsize)","The configured receive buffer size is not supported","Get the allowed receive buffer size from showportinternalinfo''"
"LIM","5","IF_DOWN_INCOMPATIBLE_ADMIN_SPEED","Interface [chars] is down (Error disabled - Incompatible admin port speed)","The configured speed is not supported on this interface","Perform a showportinternalinfo'todeterminetherangeofspeedsupportedonthisinterface'"
"LIM","5","IF_DOWN_INITIALIZING","Interface [chars] is down (Initializing)","The interface is in the process of coming up","If the interface is stuck in this state for a while, check the output of showportinternalevent-history'todeterminewhatitiswaitingfor'"
"LIM","5","IF_DOWN_INTERFACE_REMOVED","Interface [chars] is down (Interface removed)","Interface removed","No action is required."
"LIM","5","IF_DOWN_LINK_FAILURE","Interface [chars] is down (Link failure)","The physical link has gone down","Ensure that the cable is connected and the remote end is not shut down"
"LIM","5","IF_DOWN_LOOPBACK_DIAG_FAILURE","Interface [chars] is down (Diag failure)","Diag failed on the interface","Collect more information about failed interface using command attachmodule'toconnecttomodule'"
"LIM","5","IF_DOWN_LOOPBACK_ISOLATION","Interface [chars] is down (Isolation due to port loopback to same switch)","The interface is looped back to another interface on the same switch","Check the connectivity of this interface and ensure that it is connected to another switch"
"LIM","5","IF_DOWN_MODULE_REMOVED","Interface [chars] is down (module removed)","Interface is down because the module was removed","No action is required."
"LIM","5","IF_DOWN_NONE","Interface [chars] is down ([chars])","Interface is down with a possible reason.","Collect more information about port using command showportinternalinfo/event-history'todeterminewhyitwentdown'"
"LIM","5","IF_DOWN_NON_PARTICIPATING","Interface [chars] is down (Non participating)","The loop port has been put into non participating mode","No action is required."
"LIM","5","IF_DOWN_OFFLINE","Interface [chars] is down (Offline)","The interface has been placed into the offline state","No action is required."
"LIM","5","IF_DOWN_PARENT_ADMIN_DOWN","Interface [chars] is down (Parent interface down)","Parent interface is down","No action is required."
"LIM","5","IF_DOWN_PEER_CLOSE","Interface [chars] is down(TCP conn. closed by peer)","The FCIP peer connected to this interface closed the TCP connection","This command will provide the peer IP address of this FCIP interface: show interface. Check to see why the peer closed the TCP connection"
"LIM","5","IF_DOWN_PEER_RESET","Interface [chars] is down(TCP conn. reset by peer)","TCP connection to the FCIP peer got reset","The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Check to see why the peer reset the TCP connection"
"LIM","5","IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN","Interface [chars] is down (No operational members)","This is a PortChannel interface and all its members are operationally down","Enable at least one of the PortChannelsmembers'"
"LIM","5","IF_DOWN_PORT_VSAN_MISMATCH_ISOLATION","Interface [chars] is down (Isolation due to port vsan mismatch)","Isolated due to a mismatch in the configured port VSAN of the local and remote ends","Configure the port VSAN of the local and remote interfaces to be the same and perform a shutdown'anda'noshutdown''"
"LIM","5","IF_DOWN_RCF_IN_PROGRESS","Interface [chars] is down (RCF in progress)","There is an RCF in progress","No action is required."
"LIM","5","IF_DOWN_SOFTWARE_FAILURE","Interface [chars] is down (Port software failure)","The software servicing the data path on the port has failed","No action is required."
"LIM","5","IF_DOWN_SRC_MOD_NOT_ONLINE","Interface [chars] is down(Tunnel source module not online)","Module that has the tunnel source port of this FCIP interface is not fully online","The module that has the tunnel src port is coming online. Please use show mod to find module status"
"LIM","5","IF_DOWN_SRC_PORT_NOT_BOUND","Interface [chars] is down (Tunnel port src interface unbound)","Tunnel port source interface unbound","No action is required."
"LIM","5","IF_DOWN_SRC_PORT_REMOVED","Interface [chars] is down(Tunnel src port removed)","Tunnel source port of this FCIP interface has been removed","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"
"LIM","5","IF_DOWN_SUSPENDED_BY_MODE","Interface [chars] is down (Suspended due to incompatible mode)","This interface belongs to a PortChannel and operational mode of the interface is different from that of the PortChannel","Change the mode and the trunking mode of the PortChannel from auto'andchecktoensurethattheremoteendoftheinterfacealsobelongstothesamePortChannel'"
"LIM","5","IF_DOWN_SUSPENDED_BY_SPEED","Interface [chars] is down (Suspended due to incompatible speed)","This interface belongs to a PortChannel and operational speedode of the interface is different from that of the PortChannel","Change the speed of the PortChannel from auto'andchecktoensurethattheremoteendoftheinterfacealsobelongstothesamePortChannel'"
"LIM","5","IF_DOWN_SUSPENDED_BY_WWN","Interface [chars] is down (Suspended due to incompatible remote switch WWN)","This interface belongs to a PortChannel and remote switch WWN of the interface is different from that of the PortChannel","Ensure that this interface is connected to the same remote switch as all the other interfaces in the PortChannel"
"LIM","5","IF_DOWN_SUSPENDED","Interface [chars] is down (Suspended)","This interface belongs to a PortChannel and has been suspended due to an error while bringing it up","Perform a shutdown'anda'noshutdown'.Ifthishappensagainobtainoutputof'showportinternalinfo/event-history' ontheinterface'"
"LIM","5","IF_DOWN_TCP_KEEP_ALIVE_EXPIRED","Interface [chars] is down(TCP conn. closed - Keep alive expired)","TCP session to the FCIP peer got closed due to loss of TCP keep alive","This may be due to loss of IP connectivity. The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Please do a trace route to check the connectivity to the peer using command:traceroute ipaddr"
"LIM","5","IF_DOWN_TCP_MAX_RETRANSMIT","Interface [chars] is down(TCP conn. closed - retransmit failure)","Interface is down due to maximum retransmission failure","This may be due to loss of IP connectivity. The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Please do a trace route to check the connectivity to the peer using command:traceroute ipaddr"
"LIM","5","IF_DOWN_TCP_PERSIST_TIMER_EXPIRED","Interface [chars] is down(TCP conn. closed - Persist timer expired)","TCP session to the FCIP peer closed because TCP persist timer expired","This may be due to loss of IP connectivity. The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Please do a trace route to check the connectivity to the peer using command:traceroute ipaddr"
"LIM","5","IF_DOWN_UPGRADE_IN_PROGRESS","Interface [chars] is down (Linecard upgrade in progress)","Upgrade of the linecard software is in progress","No action is required."
"LIM","5","IF_DOWN_VRF_UNUSABLE","Interface [chars] is down (Vrf down)","The vrf for which this interface is a member is removed","No action is required."
"LIM","5","IF_DOWN_VSAN_MISMATCH_ISOLATION","Interface [chars] is down (Isolation due to vsan mismatch)","This is a trunking interface and the VSANs configured do not match with the VSANs configured on the remote end","Check the VSANs configured on the local end with the remote end"
"LIM","5","IF_DOWN_ZONE_MERGE_FAILURE_ISOLATION","Interface [chars] is down (Isolation due to zone merge failure)","Isolated due to a failure during zone merge","No action is required."
"LIM","5","IF_DOWN_ZONE_REMOTE_NO_RESP_ISOLATION","Interface [chars] is down (Isolation due to remote zone server not responding)","Isolated due to remote zone server not responding","No action is required."
"LIM","5","IF_DUPLEX","Interface [chars], operational duplex mode changed to [chars]","Operational duplex mode has changed when link came up","No action is required."
"LIM","5","IF_ERRDIS_RECOVERY","Interface [chars] is being recovered from error disabled state (Last Reason:[chars])","Interface is being recovered from error disabled state","No action is required."
"LIM","5","IF_HARDWARE","Interface [chars], hardware type changed to [chars]","There was a change in the hardware characteristic of an interface, such as a transceiver module plugged in or removed","No action is required."
"LIM","5","IF_L2MP_MODE","Interface [chars], l2mp-mode changed to [chars]","The l2mp-mode on the port has changed","No action is required."
"LIM","5","IF_RX_FLOW_CONTROL","Interface [chars], operational Receive Flow Control state changed to [chars]","Operational receive flow control has changed when link came up","No action is required."
"LIM","5","IF_TRUNK_DOWN","Interface [chars], vlan [chars] down","Interface [chars] is trunking, VLANs [chars] are down","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"
"LIM","5","IF_TRUNK_UP","Interface [chars], vlan [chars] up","Interface [chars] is trunking, VLANs [chars] are up","No action is required."
"LIM","5","IF_TX_FLOW_CONTROL","Interface [chars], operational Transmit Flow Control state changed to [chars]","Operational transmit flow control has changed when link came up","No action is required."
"LIM","5","IF_UP","Interface [chars] is up [chars]","Interface is up in mode specified, if applicable","No action is required."
"LIM","5","SPEED","Interface [chars], operational speed changed to [chars]","Operational speed has changed when link came up","No action is required."
"LIM","5","STORM_CONTROL_ABOVE_THRESHOLD","Traffic in port [chars] exceeds the configured threshold [chars]","Traffic on specified port is beyond the configured storm-control threshold, and the excess traffic is being dropped","Identify source of traffic storm"
"LIM","5","STORM_CONTROL_BELOW_THRESHOLD","Traffic in port [chars] has fallen below the configured threshold [chars]","Traffic on specified port has returned to within configured storm-control threshold","No action is required."
"LIT","6","LIT_DEBUG_MSG","[chars]","Debug log message","No action is required."
"LLDP","1","NO_DCBX_ACKS_RECV_FOR_LAST_10_PDUs","No Acks have been received on Interface [chars] for last [dec] DCBX PDUs","No Acks Received","No action is required."
"LLDP","3","DETECT_MULTIPLE_PEERS","Multiple peers detected on [chars]","Multiple peers detected on an interface","No action is required."
"LLDP","3","INVALID_DCBXP_RECEIVED","Received an invalid DCBXP on [chars]","Received an invalid DCBXP on an interface","No action is required."
"LLDP","3","INVALID_LLDP_RECEIVED","Received an invalid LLDP on [chars]","Received an invalid LLDP on an interface","No action is required."
"LLDP","3","LLDP_INTERNAL_ERROR","LLDP internal error: [chars]","Internal error is encountered","No action is required."
"LDP","5","LDP_DISABLED","LDP Disabled","MPLS_LDP Service Disabled","No action is required."
"LDP","5","LDP_ENABLED","LDP Enabled","MPLS_LDP Service nabled","No action is required."
"LLDP","6","DETECT_REMOTE_CHANGE","Remote change detected on [chars]","Remote change detected on an interface","No action is required."
"LLDP","6","DETECT_REMOTE_DCBXP_CHANGE","Remote DCBXP change detected on [chars]","Remote DCBXP change detected on an interface","No action is required."
"M2FIB-SLOT#","0","CLI_INIT_FAILED","CLI library initialization failed!","M2FIB failed to initialize CLI infrastructure's backend library. This is a fatal error.","No action is required."
"M2FIB-SLOT#","0","TIMER_INIT_FAILED","Timer subsystem initialization failed!","M2FIB failed to initialize timer library. This is a fatal error.","No action is required."
"M2FIB-SLOT#","2","M2FIB_MAC_TBL_PRGMING","Failed to program the mac table on FE [dec] for group: FTAG [dec], ([dec] (BD [dec]), *, [chars]). Error: [chars]. To avoid multicast traffic loss, disable OMF using the CLI: 'no ip igmp snooping optimise-multicast-flood'","Failed to program the mac table. This is a critical failure please check m2fib errored transactions","No action is required."
"M2FIB-SLOT#","2","M2FIB_MEM_ALLOC","Memory allocation failed. [chars]","Memory allocation failed. This is a critical failure","No action is required."
"M2FIB-SLOT#","2","VLAN_NOT_FOUND","M2fib recvd invalid vlan!","M2FIB failed to process the route update as the vlan recvd was invalid","No action is required."
"M2FIB-SLOT#","6","INITIALIZED","Internal state created [chars]","M2FIB has created its internal state stateless/stateful [chars].","No action is required."
"M2FIB-SLOT#","6","VDC_CREATED","VDC [dec] created","Request to create VDC [dec] in M2FIB was successful.","No action is required."
"M2FIB-SLOT#","6","VDC_REMOVED","VDC [dec] Removed","M2FIB has successfully removed VDC [dec] from its databases.","No action is required."
"M2FIB-SLOT#","6","VDC_VLAN_CREATED","VLAN [dec] created in VDC [dec]","M2FIB has added VLAN [dec] in VDC [dec].","No action is required."
"M2FIB-SLOT#","6","VDC_VLAN_REMOVED","VLAN [dec] removed from VDC [dec]","M2FIB has successfully removed VLAN [dec] from VDC [dec].","No action is required."
"M2RIB","0","CLI_INIT_FAILED","CLI library initialization failed!","M2RIB failed to initialize CLI infrastructure's backend library. This is a fatal error.","No action is required."
"M2RIB","2","FLOOD_PROG_ERR1","Prev:[chars], Collect console logs and output of show tech-support m2rib","M2RIB has hit flood prog error. Collect output of show tech-support m2rib for further analysis","No action is required."
"M2RIB","2","FLOOD_PROG_ERR2","Curr:[chars], Collect console logs and output of show tech-support m2rib","M2RIB has hit flood prog error. Collect output of show tech-support m2rib for further analysis","No action is required."
"M2RIB","2","IPC_PROCESSING_ERR","Error in processing IPC message : Opcode = [dec], Error code = [hex]","M2RIB encountered an error in processing an MTS message. The error and message are specified in the error message","No action is required."
"M2RIB","2","M2RIB_INIT","M2RIB initialization of [chars] [chars]","M2RIB initialization failed","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"M2RIB","2","MFDM_API_ERROR","ERROR PROG FLOOD ROUTES: Status:[chars] Msg_Ref_State:[hex] Prev_Count:[dec] Curr_Count:[dec] Prev_Msg:[hex] Curr_Msg:[hex], Collect output of show tech-support m2rib","MFDM returned Failure for flood programming. Collect output of show tech-support m2rib for further analysis","No action is required."
"M2RIB","2","MFDM_TIMEOUT_ERR","M2RIB timed out waiting for MFDM: Transaction: %p, Transaction entry: [chars]","Transaction timer for the message sent from M2RIB to MFDM has expired. Ack not received from MFDM.","No action is required."
"M2RIB","6","INITIALIZED","Internal state created [chars]","M2RIB has created its internal state stateless/stateful [chars].","No action is required."
"M2RIB","6","SERVICE_UP","Initialized [chars]","M2RIB line 2.No action is required.MAC MessagesThis section contains the MAC messages.MAC-SLOT#-2Error Message      MAC-SLOT#-2-MAC_INFO: [chars] Explanation    MAC Informational message","No action is required."
"MCAST","2","SHUTDOWN","Process shutting down: [chars]","Mcast is shutting down","The action depends on the situation. The multicast process can shut down gracefully because of a system restart (in which case no action needs to take place) or because of a failure. The message associated with the syslog should be self explanatory to understand the reason for the shutdown. If the process is able to restart properly, there is no immediate harm for the system stability and the suggested action is to report the syslog event together with an explanation of the operations most recently performed on the system."
"MCAST","4","ERROR","[chars]","Mcast encountered a generic error","No action is required."
"MCAST","5","BAD_MSG","Received bad message: [chars]","Mcast has received a malformed/unrecognized message","No action is required."
"MCAST","5","START","Process has been started","Mcast has been started","No action is required."
"MCECTEST","3","ASSERTION_FAILED","[chars]","MCECTEST has hit an assert condition at file [chars]","No action is required."
"MCECTEST","3","INIT_FAIL","[chars]","MCECTEST Initialization failed. due to [chars]","No action is required."
"MCECTEST","3","INTERNAL_ERR","[chars]","MCECTEST encountered an internal error due to [chars]","No action is required."
"MCECTEST","3","MTS_ERR","[chars]","MCECTEST encountered an MTS error due to [chars]","No action is required."
"MCECTEST","5","MCECTEST_DISABLED","MCECTEST Disabled","MCECTEST Service Disabled","No action is required."
"MCECTEST","5","MCECTEST_ENABLED","MCECTEST Enabled","MCECTEST Service enabled","No action is required."
"MCECTEST","6","INTERNAL_INFO","[chars]","MCECTEST got an internal info [chars]","No action is required."
"MCM","2","MCM_CRITICAL_ERROR","Internal Critical Error","Some critical error","No action is required."
"MCM","2","MCM_REPLICATION_DISABLED","Proxy layer-3 modules are not available for replication. Proxy layer-3 multicast replication is disabled.","Replication is disabledError Message     No action is required.MCM-2-MCM_REQ_RESP_ERROR: Error ([hex]: [chars]) while communicating with component :[chars], opcode: [chars] (for: [chars]) Explanation    Error in request-response handshake","No action is required."
"MCM","2","MCM_ROUTING_DISABLED","Proxy layer-3 modules are not available for routing. Proxy layer-3 forwarding is disabled.","Routing is disabled","No action is required."
"MCM","5","MCM_SDB_UPDATE_FAILED","sdb update failed with ret_val [dec]","SDB updated failed for MCM","No action is required."
"MCM","6","MCM_REPLICATION_ENABLED","Proxy layer-3 modules are UP and available for replication. Proxy layer-3 multicast replication is enabled.","Replication is enabled","No action is required."
"MCM","6","MCM_ROUTING_ENABLED","Proxy layer-3 modules are UP and available for routing. Proxy layer-3 forwarding is enabled.","Routing is enabled","No action is required."
"METROPOLIS_USD","3","METRO_MSG1","[chars]","METRO log messageNo action is required.MFDM MessagesThis section contains the MFDM messages.MFDM-2Error Message    MFDM-2-DI_REUSE: LTL node exists with DI [dec] oiflist_index [dec] type [dec] and same DI returned for oiflist_index [dec] type [dec] Please collect show tech-support forwarding distribution l2/l3 multicast and show tech-support pixm. Explanation    PIXM returned duplicate DI.","No action is required."
"MFDM","2","DOWNLOAD_TIMEOUT","Download of L2/L3 route databases timed out : download_in_progress_slots [hex] for database [chars] [chars] [chars]","Download of L2/L3 route databases timed out. Download triggered by VMM insert request.","No action is required."
"MFDM","2","INTERNAL_ERROR","MFDM-[chars] Internal error : show system internal mfdm errors for more information","MFDM PD hit a internal error. show system internal mfdm errors for futher analysis.","No action is required."
"MFDM","2","REF_OUTOFSYNC","In Decrement ltl_node ref_count: [dec] is less than count: [dec] passed in for DI: [hex], oiflist_index: [dec], type: [dec]. Possible PI/PD refcount out-of-sync. Please collect show tech-support forwarding distribution l2/l3 multicast and show tech-support pixm.","MFDM PI/PD refcount out-of-sync","No action is required."
"MFDM","2","XID_TAMPERED","Correcting xid in resp - rrtoken:[hex], req(xid:[dec], rt_cnt:[dec], msg_len:[dec], flag:[dec]), resp(xid:[dec], rt_cnt:[dec], msg_len:[dec], flag:[dec])","MFDM tampered xid in OTV response payload","No action is required."
"MODULE","2","LCM_PRE_UPGRADE_GENERAL_FAIL","Pre upgrade message fails seq [dec]","Pre upgrade message failed.","No action is required."
"MODULE","2","LCM_UPGRADE_DONE_GENERAL_FAIL","Upgrade done message fails SAP [chars]","Upgrade ready message failed.","Recommended Action No action is required."
"MODULE","2","LCM_UPGRADE_OVER_FAIL","Upgrade over message returned [dec] [hex] for SAP [dec]","Upgrade done message failed.","No action is required."
"MODULE","2","LCM_UPGRADE_READY_FAIL","Upgrade ready message returned [dec] [hex] for SAP [dec]","Upgrade ready message failed.","No action is required."
"MODULE","2","LCM_UPGRADE_READY_GENERAL_FAIL","Upgrade ready message fails SAP [chars]","Upgrade ready message failed.","No action is required."
"MODULE","2","MOD_DIAG_FAIL","Module [dec] (Serial number: [chars]) reported failure [chars] due to [chars] in device [chars] (device error [hex])","The module in slot [decimal digit] reported a failure in the runtime diagnostic. Module manager is going to power cycle the module.","Collect information about the module by issuing the command 'show module internal all module [decimal digit]'."
"MODULE","2","MOD_DNLD_FAIL","Image download failed for module [dec] (Serial number: [chars])","Module [decimal digit] failed to download a new image from the supervisor.","Collect information about the module by issuing the command 'show module internal all module [decimal digit]'."
"MODULE","2","MOD_FAILURE","Re-initializing module [dec] (Serial number: [chars]) failed. Received lc_failed from sap [hex] failure reason [hex]","Module [decimal digit] reported a failure during the initialization phase and will be rebooted.","Collect information about the module by issuing the commands 'show module_internal all module '."
"MODULE","2","MOD_FAILURE","Re-initializing module [dec] (Serial number: [chars]) failed. Received lc_failed from sap [hex] failure reason [hex]","Module [decimal digit] reported a failure during the initialization phase and will be rebooted.","Collect information about the module by issuing the commands showmodule_internalallmodule<modulenumber"
"MODULE","2","MOD_FAIL","Initialization of module [dec] (Serial number: [chars]) failed","Module [decimal digit] reported a failure during the initialization phase and will be powered down.","Collect information about the module by issuing the commands 'show module_internal all module '."
"MODULE","2","MOD_MAJORSWFAIL","Module [dec] (Serial number: [chars]) reported a critical failure in service [chars]","A critical failure in service [string] happened at module [decimal digit] is going to reset the module [decimal digit].","Collect information about the module by issuing the command 'show module internal all module [decimal digit]'."
"MODULE","2","MOD_MINORSWFAIL","Module [dec] (Serial number: [chars]) reported a failure in service [chars]","A non-critical failure in service [string] happened at module [decimal digit] is not going to reset the module [decimal digit].","Collect information about the module by issuing the command 'show module internal all module [decimal digit]'."
"MODULE","2","MOD_NOT_ALIVE","Module [dec] not responding... resetting (Serial number: [chars])","Module [decimal digit] is not replying to the hello message: module manager is then going to reset the module.","No action is required."
"MODULE","2","MOD_REGFAILED","Registration failed for module [dec]","Module [decimal digit] sent the registration message notifying a failure.","Collect module internal information by issuing the command 'show module internal all module [decimal digit]'."
"MODULE","2","MOD_SOMEPORTS_FAILED","Module [dec] (Serial number: [chars]) reported failure on ports [dec]/[dec]-[dec]/[dec] ([chars]) due to [chars] in device [chars] (error [hex])","Module [decimal digit] reported a failure in the runtime diagnostic due to failure in some of the ports.","Collect information about the module by issuing the command 'show module internal all module [decimal digit]'."
"MODULE","2","MOD_UNKNOWN","Module type [[dec]] in slot [dec] is not supported","The software card id of module [decimal digit] is not supported by the supervisor.","Collect information about the module by issuing the commands 'show module internal all module [decimal digit]'"
"MODULE","2","XBAR_DIAG_FAIL","Xbar [dec] (Serial number: [chars]) reported failure [chars] due to [chars] in device [chars] (device error [hex])","The xbar in slot [decimal digit] reported a failure in the runtime diagnostic. Module manager is going to power cycle the module.","Collect information about the module by issuing the command 'show module internal all xbar [decimal digit]'."
"MODULE","2","XBAR_FAILURE","Re-initializing xbar [dec] (Serial number: [chars]) failed. Received lc_failed from sap [hex] failure reason [hex]","Xbar [decimal digit] reported a failure during the initialization phase and will be rebooted.","Collect information about the module by issuing the commands 'show module_internal all xbar '."
"MODULE","2","XBAR_FAILURE","Re-initializing xbar [dec] (Serial number: [chars]) failed. Received lc_failed from sap [hex] failure reason [hex]","Xbar [decimal digit] reported a failure during the initialization phase and will be rebooted.","Collect information about the module by issuing the commands showmodule_internalallxbar<modulenumber"
"MODULE","2","XBAR_FAIL","Initialization of xbar [dec] (Serial number: [chars]) failed","Xbar [decimal digit] reported a failure during the initialization phase and will be powered down.","Collect information about the module by issuing the commands 'show module_internal all xbar '."
"MODULE","2","XBAR_SOMEPORTS_FAILED","Xbar [dec] (Serial number: [chars]) reported failure on ports [dec]/[dec]-[dec]/[dec] ([chars]) due to [chars] in device [chars] (error [hex])","Xbar [decimal digit] reported a failure in the runtime diagnostic due to failure in some of the ports.","Collect information about the module by issuing the command 'show module internal all xbar [decimal digit]'."
"MODULE","2","XBAR_SOMEPORTS_FAILED","Xbar [dec] (Serial number: [chars]) reported failure on ports [dec]/[dec]-[dec]/[dec] ([chars]) due to [chars] in device [chars] (error [hex])","Xbar [decimal digit] reported a failure in the runtime diagnostic due to failure in some of the ports.","Collect information about the module by issuing the command showmoduleinternalallxbar[decimaldigit]'.'"
"MODULE","2","XBAR_UNKNOWN","Xbar type [[dec]] in slot [dec] is not supported","The software card id of xbar [decimal digit] is not supported by the supervisor.","Collect information about the module by issuing the commands 'show module internal all xbar [decimal digit]''"
"MODULE","3","LCM_SEQ_ERROR","Error ([chars]) for slot:[dec] while communicating with component [chars] opcode:[chars] (for:[dec])","LCM encountered an error while executing a sequence for a module.","No action is required."
"MODULE","3","LCM_SYSLOG_ERR","[chars]","LCM encountered an error while processing a message for module.","No action is required. '"
"MODULE","3","MOD_SRG_NOT_COMPATIBLE","Module [dec] (Serial number: [chars]) firmware is not compatible with supervisor, downloading new image","The software version of module [decimal digit] is not supported by the supervisor.","Collect information about the module by issuing the command showmoduleinternalallmodule[decimaldigit]'.'"
"MODULE","4","MOD_WARNING","Module [dec] (Serial number: [chars]) reported warning [chars] due to [chars] in device [chars] (device error [hex])","Module [decimal digit] reported a warning in the runtime diagnostic due to failure in some of the ports.","Collect information about the module by issuing the command showmoduleinternalallmodule[decimaldigit]'.'"
"MODULE","4","XBAR_WARNING","Xbar [dec] (Serial number: [chars]) reported warning [chars] due to [chars] in device [chars] (device error [hex])","Xbar [decimal digit] reported a warning in the runtime diagnostic due to failure in some of the ports.","Collect information about the module by issuing the command showmoduleinternalallxbar[decimaldigit]'.'"
"MODULE","5","ACTIVE_SUP_OK","Supervisor [dec] is active (Serial number: [chars])","Module [decimal digit] is ready to be configured and be able to switch traffic.","No action is required."
"MODULE","5","LCM_MODULE_UPGRADE_END","Upgrade of module [dec] ended","Upgrade of the module has ended.","No action is required."
"MODULE","5","LCM_MODULE_UPGRADE_START","Upgrade of module [dec] started","Upgrade of the module has been started by installer","No action is required."
"MODULE","5","MOD_OK","Module [dec] is online (Serial number: [chars])","Module [decimal digit] is ready to be configured and be able to switch traffic.","No action is required."
"MODULE","5","MOD_REINIT","Re-initializing module [dec] (Serial number: [chars])","Module [decimal digit] reported a failure during the initialization phase and will be rebooted.","Collect information about the module by issuing the commands showmodule_internalallmodule<modulenumber"
"MODULE","5","MOD_RESTART","Module [dec] is restarting after image download","Module [decimal digit] completed image download and is restarting.","No action is required."
"MODULE","5","MOD_STARTUP_CFG_MISMATCH","The startup configuration cannot be applied to a different module type for module [dec] (Serial number: [chars]). [chars] module is replacing [chars].","The startup configuration for module [decimal digit] contains information about a different type of module instead of containing information about the current one.","No action is required."
"MODULE","5","STANDBY_SUP_OK","Supervisor [dec] is standby","Module [decimal digit] is ready to be configured and be able to switch traffic.","No action is required."
"MODULE","5","XBAR_OK","Xbar [dec] is online (Serial number: [chars])","Xbar [decimal digit] is ready to be configured and be able to switch traffic.","No action is required."
"MODULE","5","XBAR_REINIT","Re-initializing xbar [dec] (Serial number: [chars])","Xbar [decimal digit] reported a failure during the initialization phase and will be rebooted.","Collect information about the module by issuing the commands showmodule_internalallxbar<modulenumber"
"MODULE","6","MOD_PURGE_CONFIG","Purging the configuration for module [dec]","Notification is being sent to remove the module configurations.","No action is required."
"MODULE","6","MOD_REG_OK","Registration succeeded for module [dec]","Module [decimal digit] sent a successful registration message.","No action is required."
"MONITOR","3","ETH_SPAN_SPM_TIMER_EXPIRY","SPM request timed out for ssn: [dec]","SPM Request timed out for ERSPAN-DST session","No action is required."
"MONITOR","5","ETH_SPAN_SESSION_CREATED","Session [dec] created","A new span session has been created.","No action is required."
"MONITOR","5","ETH_SPAN_SESSION_DELETED","Session [dec] deleted","Session has been deleted.","No action is required."
"MONITOR","5","ETH_SPAN_SESSION_DOWN","Session [dec] is down. Reason '[chars]'","Session is down, no further traffic will be spanned.","No action is required."
"MONITOR","5","ETH_SPAN_SESSION_ERROR","Session [dec] is having error. Reason '[chars]'","The session is experiencing a problem.","Delete the session and try to reconfigure it"
"MONITOR","5","ETH_SPAN_SESSION_UP","Session [dec] is up.","Session is up now. You can monitor Spanned traffic at the destination ports","No action is required."
"MTM-SLOT#","0","CLI_INIT_FAILED","CLI library initialization failed!","MTM failed to initialize CLI infrastructure's backend library. This is a fatal error.","No action is required."
"MTM-SLOT#","0","FE_TIMER_EXPIRED","FE timer expired for fe [dec]!","Driver has failed to respond to MTM request within MTM_FE_TO_TIMER_INTERVAL.This is a fatal error.","No action is required."
"MTM-SLOT#","0","TIMER_INIT_FAILED","Timer subsystem initialization failed!","MTM failed to initialize timer library. This is a fatal error.","No action is required."
"MTM-SLOT#","1","L2_USD_REQ_FAILED","Failed to send request to the L2 ASIC driver.","Failed to send request to L2 ASIC driver.","No action is required."
"MTM-SLOT#","2","FE_MAC_TABLE_LINE_FULL","Failed to insert static mac as MAC table line is full for FE [dec]!","Static mac insert failed due to line full condition.","No action is required."
"MTM-SLOT#","2","HWIDX_TO_IF_FAILED_SUMMARY","Failed to get interface for hardware index for [dec] entries","Failed to get interface for hardware Index for [dec] entries","No action is required."
"MTM-SLOT#","2","IF_TO_HWIDX_FAILED_SUMMARY","Failed to get hardware index for interface Index for [dec] entries.","Failed to get hardware index for interface Index for [dec] entries.","No action is required."
"MTM-SLOT#","2","MTM_MEM_ALLOC","Memory allocation failed. [chars]","Memory allocation failed. This is a critical failure","No action is required."
"MTM-SLOT#","2","MULTICAST_SOURCE_MAC_LEARNT","Inserted dynamically learnt multicast source mac [chars] in vlan [dec]!. Issue showhardwaremacaddress-table<mod","Multicast mac address: [hex] sent as source mac in a packet and was learnt in the Mac Table. Please execute: clear mac address-table dynamic multicast-entries","No action is required."
"MTM-SLOT#","2","STATIC_MATCH","Failed to program static match registers for [chars].","Failed to program the required registers in L2 ASIC for [chars].","No action is required."
"MTM-SLOT#","2","STP_BPDU_MATCH","Failed to program static match registers for BPDU matching.","Failed to program the required registers in L2 ASIC for BPDU matching. BPDUs will not be received by Spanning tree.","No action is required."
"MTM-SLOT#","2","VLAN_NOT_FOUND","VLAN [dec] not found in MTM database!","MTM failed to find VLAN [dec] in its database. L2 MAC learning & aging on VLAN [dec] may be affected.","No action is required."
"MTM-SLOT#","5","AGEGRP_ALLOC_FAILED","Age group allocation for age [dec] failed.","Age group allocation for age [dec] failed. The total number of allocated age group has reached system limits.","No action is required."
"MTM-SLOT#","5","ALL0_LRN_DISABLE_FAIL","Failed to program static match register to disable learning all 0 MAC.","Failed to program the required registers in L2 ASIC to disable learning all 0 MAC.","No action is required."
"MTM-SLOT#","6","INITIALIZED","Internal state created [chars]","MTM has created its internal state stateless/stateful [chars].","No action is required."
"MTM-SLOT#","6","VDC_CREATED","VDC [dec] created","Request to create VDC [dec] in MTM was successful.","No action is required."
"MTM-SLOT#","6","VDC_REMOVED","VDC [dec] Removed","MTM has successfully removed VDC [dec] from its databases.","No action is required."
"MTM-SLOT#","6","VDC_VLAN_CREATED","VLAN [dec] created in VDC [dec]","MTM has added VLAN [dec] in VDC [dec].","No action is required."
"MTM-SLOT#","6","VDC_VLAN_REMOVED","VLAN [dec] removed from VDC [dec]","MTM has successfully removed VLAN [dec] from VDC [dec].","No action is required."
"NFM","2","COMMIT_FAIL","Commit failed: client [hex], [chars]","The DDB commit failed","No action is required."
"NFM","2","DDB_FAILURE","DDB failure: [chars]","A DDB generated failure","No action is required."
"NFM","2","EXITING","Exit reason: [chars]","The NFM service process has exited due to [char]. The process has probably been restarted automatically.","No action is required."
"NFM","2","INIT_FAIL","NFM Service Init failed: [chars]","NFM Service initialization failed. [chars] explains the reason for the failure.","No action is required."
"NFM","2","MALLOC_ERROR","Function [chars]: Size [dec] bytes","The NFM service could not allocate memory.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"NFM","2","PSS_ERROR","[chars]: PSS ret. val=[dec]","The NFM service encountered error while operating on a persistent storage database.","No action is required."
"NFM","2","VERIFY_FAIL","Verify failed - Client [hex], Reason: [chars], Interface: [chars]","The DDB Verify failed","No action is required."
"NFM","3","DDB_ERROR","DDB error: [chars]","The DDB generated error","No action is required."
"NFM","3","FEATURE_MANAGER_ERROR","[chars]: An error occurred processing a Feature Manager msg - error [chars]","An error occurred while processing a message from FEATURE Manager","No action is required."
"NFM","3","HANDLE_IN_USE","[chars]: name: [chars]","The NFM service encountered a handle that was in use while reading a persistent storage database.","No action is required."
"NFM","3","INVALID_HANDLE","[chars]: handle =[hex]","The NFM service encountered an invalid handle in a persistent storage database.","No action is required."
"NFM","3","MONITOR_NOT_FOUND","Monitor with handle [hex] from source [hex]","An Export Msg from a Linecard contained an invalid Monitor handle","No action is required."
"NFM","3","MTS_ERROR","NFM encountered the following MTS error: [chars]","NFM Service encountered an MTS error. [chars] specifies the context where the error occurred.","No action is required."
"NFM","3","NFM_CONFIG_ERROR","[chars]","L2 Netflow config is applied on Port-channel with F1 Line Cards only - error","No action is required."
"NFM","3","NFM_DDB_ERROR","DDB error: [chars]","The DDB generated error","No action is required."
"NFM","3","PSS_CORRUPTED","[chars] PSS found corrupted","The NFM service has detected corruption in one of its persistent information database. The database would be recreated.","No action is required."
"NFM","3","VLAN_PARSE_ERROR","[chars]: An error occurred processing a VLAN Mgr Parse msg [hex]","An error occurred while processing a message from VLAN Manager","No action is required."
"NFM","4","DDB_WARNING","DDB warning: [chars]","The DDB generated warning","No action is required."
"NFM","4","LICENSE_EXPIRED","The License has expired.","The NFM service requires a License to run and exits when the License expires.","No action is required."
"NFM","4","NFM_DDB_WARNING","DDB warning: [chars]","The DDB generated warning","No action is required."
"NFM","4","PSS_VERSION_MISMATCH","PSS [dec] Code [dec]","There was a version mismatch between the NFM service and one of its persistent storage databases. The persistent information has been translated to the new format.","No action is required."
"NFM","5","FEATURE_DISABLED","NetFlow Disabled.","NetFlow Feature Disabled.","No action is required."
"NFM","5","FEATURE_ENABLED","NetFlow Enabled.","NetFlow Feature Enabled.","No action is required."
"NFM","6","BECAME_ACTIVE","Became ACTIVE from standby mode","The NFM service on the standby supervisor became active and it is ready to serve client requests.","No action is required."
"NFM","6","BECAME_STDBY","Became STANDBY from active mode","The NFM service became standby from active mode.","No action is required."
"NFM","6","DDB_NOTIF","DDB notification: [chars]","The DDB generated notification","No action is required."
"NFM","6","FAILED_TO_SEND_HEARTBEAT","Failed to send heartbeat to system manager: Reason=[chars]","The NFM service was unable to send heartbeat to the system manger","No action is required."
"NFM","6","NFM_DDB_NOTIF","DDB notification: [chars]","The DDB generated notification","No action is required."
"NFM","6","SERVICE_UP","Initialized [chars]","The NFM service is up and ready The service was initialized in [char] mode.","No action is required."
"NFM","6","SRV_EXIT","NFM Service shutting down gracefully","NFM Service is shutting down gracefully. This is an informational message.","No action is required."
"NFM","6","SWITCH_OVER","Switching Over to other Sup.","The NFM service has successfully switched over to the standby supervisor card.","No action is required."
"NFM","7","DEBUG","[chars]","Debug information is being sent to syslog","No action is required."
"NFP-SLOT#","2","NF_ACL_ERR","[chars]([dec]): acl error. [chars]","Acl error","No DDTS."
"NFP-SLOT#","2","NF_DDB_ERR","[chars]([dec]): ddb error. [chars]","Ddb error","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"NFP-SLOT#","2","NF_ERR","[chars]([dec]): nfp error. [chars]","Nfp error occured","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"NFP-SLOT#","2","NF_FIB_ERR","[chars]([dec]): fib error. [chars]","Fib error","No DDTS."
"NFP-SLOT#","2","NF_NDE_ERR","[chars]([dec]): nde error. [chars]","Nde error","No DDTS."
"NFP-SLOT#","2","NF_NFM_ERR","[chars]([dec]): nfm error. [chars]","Nfm error","No DDTS."
"NFP-SLOT#","2","NF_QOS_ERR","[chars]([dec]): qos error. [chars]","Qos error","No DDTS."
"NFP-SLOT#","5","NF_INFO","[chars]","Info","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"NPC-SLOT#","3","LOG_NPC_ERR","Nonrecoverable error: [chars]","Errors which cause program to exit occurred","No action is required."
"NPC-SLOT#","4","LOG_NPC_WARNING","Serious error: [chars]","Serious errors which affect all normal operations occurred","No action is required."
"NPC-SLOT#","5","LOG_NPC_DEBUG","Unexpected error: [chars]","Unexpected errors which affect some normal operations occurred","No action is required."
"NPC-SLOT#","5","LOG_NPC_NVP_FSM","Illegal event received: [chars]","Illegal event received in NPC_NVP FSM","No action is required."
"NPC-SLOT#","5","LOG_NPC_VSAN_FSM","Illegal event received: [chars]","Illegal event received in NPC_VSAN FSM","No action is required."
"NPV","2","CFS_PEER_LOST_WITHIN_SESSION","CFS peer with switch wwn [chars] was lost in the middle of an active CFS session. Abort the CFS session and re-enter the configuration changes","Due to port flaps, link outages, switch restart etc. a CFS peer switch of NPV was lost. The current configuration changes would not be applied to this peer until the peer merges with this switch. The CFS merge may fail if the configuration at the lost peer conflicts with the changes made in this session. It is recommended that the user abort this CFS session using ivr abort command and then re-enter the configuration changes.","No action is required."
"NPV","2","NPV_DISABLE_FAILED","NPV could not disabled : [chars] [chars]","NPM could not disabled due to the reason specified. Please try again.","No action is required."
"NPV","2","NPV_ENABLE_FAILED","NPV could not enabled : [chars] [chars]","NPM could not enabled due to the reason specified. Please try again.","No action is required."
"NPV","2","NPV_EXITED","NPV process exited in file [chars] at Line [chars]:[chars]","NPM process encountered a critical error as specified, and so NPV process cannot continue.","No action is required."
"NPV","3","ACL_UPDATE_FAILED","[chars]","ACL update request initiated by the NPV process has failed","No action is required."
"NPV","3","CFS_INVALID_PAYLOAD_RECEIVED","NPV received invalid payload from CFS","NPV process received invalid payload from CFS.","No action is required."
"NPV","3","CLEAR_FAILED","[chars]","An error occurred while clearing the lock. The reason for the failure : [chars]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"NPV","3","COMMIT_FAILED","[chars]","An error occurred while committing configuration. The reason for the failure : [chars]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"NPV","3","COMMIT_PARTIALLY_FAILED","[chars]","An error occurred while committing configuration. Configuration could not be committed on some switches. The reason for the failure : [chars]. Configuration can be inconsistent in the fabric.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"NPV","3","COMMIT_REJECTED","[chars]","Commit request received from remote switch is rejected. The reason for the failure: [chars]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"NPV","3","FC2_SEND_FAILED","[chars]","NPV process could send an FC2 message.","No action is required."
"NPV","3","F_RJT_SENT","[chars]","NPV process sent an F_RJT frame.","No action is required."
"NPV","3","INTERNAL_ERROR","Internal error: [chars]","NPV process encountered a general error, one that does not fall in any of the categories. [chars] describes the error and its context.","No action is required."
"NPV","3","LCP_PROGRAMMING_FAILED","[chars]","LCP programming request initiated by the NPV process has failed","No action is required."
"NPV","3","LOCK_FAILED","[chars]","An error occurred while acquiring the lock. The reason for the failure : [chars]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"NPV","3","LS_RJT_RCVD","[chars]","NPV process received an LS_RJT frame.","No action is required."
"NPV","3","LS_RJT_SENT","[chars]","NPV process sent an LS_RJT frame.","No action is required."
"NPV","3","MALLOC_FAILED","[chars]","NPV process could not allocate memory","No action is required."
"NPV","3","MERGE_ACTIVATION_FAILED","[chars]","An error occurred while activating merged configuration. The reason for the failure : [chars]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"NPV","3","MERGE_FAILED","[chars]","An error occurred while merging configuration. The reason for the failure : [chars]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"NPV","3","MTS_SEND_FAILED","[chars]","NPV process could not send an MTS message.","No action is required."
"NPV","3","NPIV_DISABLE_FAILED","[chars]","NPIV feature could not be disabled.","No action is required."
"NPV","3","NPV_CFS_IPV4_ENABLE_FAILED","CFS IPv4 distribution enable failed because [chars]","NPV CFS distribution might not work. Try enabling it again on the command line. Make sure cfs distribution is enabled.","No action is required."
"NPV","3","PORT_BRINGUP_FAILED","[chars]","NPV process has failed to bringup the port","No action is required."
"NPV","3","PORT_REINIT_FAILED","[chars]","Port reinit request initiated by the NPV process has failed","No action is required."
"NPV","3","UNLOCK_FAILED","[chars]","An error occurred while releasing the lock. The reason for the failure : [chars]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"NPV","4","NPV_NPIV_NOT_ENABLED_ON_UPSTREAM_SWITCH","[chars]","This syslog is printed when the external interface fails to come up due to NPIV feature not enabled on the upstream switch.","Verify and enable NPIV feature in upstream switch."
"NPV","4","NPV_PORT_VSAN_MISMATCH_ON_UPSTREAM_LINK","[chars]","This syslog is printed when the external interface fails to come up due to upstream port VSAN mis-match with the upstream switch.","Make sure port VSAN is same on both sides of this external link"
"NPV","5","ASSERTION_FAILED","Unexpected assertion failure in File [chars] at Line [dec]","An assertion failed in NPV code","No action is required."
"NPV","5","FLEXATTACH_VPWWN_AUTO_ASSIGNED","A virtual port WWN [chars] has been automatically assigned to interface [chars]","The virtual port WWN will be used as port WWN for devices logging in on this interface.","No action is required."
"NPV","5","FLEXATTACH_VPWWN_MANUALLY_ASSIGNED","A virtual port WWN [chars] has been manually assigned to interface [chars]","The virtual port WWN will be used as port WWN for devices logging in on this interface.","No action is required."
"NPV","5","FLEXATTACH_VPWWN_UNASSIGNED","The virtual port WWN has been unassigned from interface [chars]","The physical port WWN will be used as port WWN for devices logging in on this interface.","No action is required."
"NPV","5","FRAME_DISCARDED","[chars]","NPV process discarded an FC2 frame.","No action is required."
"NPV","5","NPV_LOAD_BALANCE_REINIT","Server ports reinitialized : [chars]","Server ports are reinitialized to balance the loads on the external interfaces.","No action is required."
"NPV","5","UNEXPECTED_EVENT","[chars]","NPV process has received an unexpected event in the current state.","No action is required."
"NPV","6","ABTS_SENT","[chars]","NPV process sent an ABTS frame.","No action is required."
"NPV","6","ELS_CMD_SENT_TO_CORE","[chars]","NPV process sent an ELS frame to the core switch.","No action is required."
"NPV","6","ELS_CMD_SENT_TO_SRV","[chars]","NPV process sent an ELS frame to the server.","No action is required."
"NPV","6","EXT_IF_SELECTED","[chars]","NPV process has selected an external interface to forward either all frames received on a server interface or frames received from a specific port WWN.","No action is required."
"NPV","6","FABRIC_PROXY_LOGO_SENT","[chars]","NPV process sent a LOGO frame to the device as the corresponding external interface went down.","No action is required."
"NPV","6","FDISC_RCVD","[chars]","NPV process received an FDISC frame.","No action is required."
"NPV","6","FDISC_SENT","[chars]","NPV process sent an FDISC frame to the core switch.","No action is required."
"NPV","6","FLOGI_RCVD","[chars]","NPV process received an FLOGI frame.","No action is required."
"NPV","6","INTERNAL_FLOGI_SENT","[chars]","NPV process sent an internal FLOGI frame to the core switch on an external interface.","No action is required."
"NPV","6","LOGO_RCVD","[chars]","NPV process received a LOGO frame.","No action is required."
"NPV","6","LOGO_SENT","[chars]","NPV process sent a LOGO frame.","No action is required."
"NPV","6","LS_ACC_RCVD","[chars]","NPV process received an LS_ACC frame.","No action is required."
"NPV","6","LS_ACC_SENT","[chars]","NPV process sent an LS_ACC frame.","No action is required."
"NPV","6","MTS_NOTIF_RCVD","[chars]","NPV process received an MTS notification.","No action is required."
"NPV","6","MTS_NOTIF_SENT","[chars]","NPV process sent an MTS notification.","No action is required."
"NPV","6","MTS_REQ_RCVD","[chars]","NPV process received an MTS request.","No action is required."
"NPV","6","MTS_REQ_SENT","[chars]","NPV process sent an MTS request.","No action is required."
"NPV","6","MTS_RESP_RCVD","[chars]","NPV process received an MTS response.","No action is required."
"NPV","6","MTS_RESP_SENT","[chars]","NPV process sent an MTS response.","No action is required."
"NPV","6","NPIV_DISABLED","[chars]","NPIV feature has been disabled.","No action is required."
"NPV","6","NPIV_ENABLED","[chars]","NPIV feature has been enabled.","No action is required."
"NPV","6","NPV_ENABLE_DISABLE_IN_PROGRESS","[chars]","NPV feature enable/disable is in progress. This syslog is printed at the beginning of various significant phases.","No action is required."
"NPV","6","NPV_LOAD_BALANCE_TIMER_START","(Re)starting automatic load balancing timer for [dec] seconds","Timer started for upon external interface up or server interface down. When the timer goes off some of the server interfaces may be reinitialized to evenly distribute the server interfaces amongst the eligible external interfaces.","No action is required."
"NPV","6","SERVER_PROXY_LOGO_SENT","[chars]","NPV process sent a LOGO frame to the core switch as the server interface went down.","No action is required."
"NPV","7","CFS_REQ_RCVD","[chars]","CFS request is received. The WWN of the switch originated this request and the rr-token of the request are provided in the syslog message.","No action is required."
"NPV","7","CFS_RESP_SENT","[chars]","CFS response is sent. The rr-token of the corresponding request and the status are provided in the syslog message","No action is required."
"NTP","2","NTP_SYSLOG_CRIT_ERR",": [chars]","NTP syslog Critial Error : [chars].","No action is required."
"NTP","2","NTP_SYSLOG_INIT_FAIL",": [chars] [chars]","NTP Initialization Failed: [chars] [chars].","No action is required."
"NTP","2","NTP_SYSLOG_NO_RESP_FROM_LC","from LC[dec] for [chars]","NTP did not receive response from the linecard for the request sent.","No action is required."
"NTP","3","NTP_SYSLOG_ALLOC_FAIL",": [chars]","NTP syslog allocation failed : [chars].","No action is required."
"NTP","3","NTP_SYSLOG_ERR_EXT",": [chars] [chars]","NTP syslog Error Exit : [chars] [dec].","No action is required."
"NTP","3","NTP_SYSLOG_ERR",": [chars]","NTP syslog Error : [chars].","No action is required."
"NTP","3","NTP_SYSLOG_MTS_ERR",": [chars]","NTP MTS Error : [chars].","No action is required."
"NTP","6","NTP_SYSLOG_CREATED",": [chars]; Slot No: [dec]","NTP syslog created : [chars] [chars].","No action is required."
"NTP","6","NTP_SYSLOG_EXIT",": [chars]","NTP syslog Exit : [chars].","No action is required."
"NTP","6","NTP_SYSLOG_LOGGING",": [chars]","NTP logging : [chars].","No action is required."
"NTP","6","NTP_SYSLOG_WARN",": [chars]","NTP syslog Warning : [chars].","No action is required."
"NVP","6","NVP_INFO","[chars]","NVP daemon informational message","No action is required."
"NVP","6","STARTING","deamon started","The NVP daemon successfully started","No action is required."
"NVP-SLOT#","2","CPP_CATASTROPHIC_ERROR","ERROR: Component ([chars]) caused critical error please reboot SSM","Component caused critical error","Restart the linecard"
"OBFL","3","ERROR","[chars]","Obfl_encountered an error","No action is required."
"OC_USD","2","RF_CRC","[chars]","Octopus received packets with CRC error from fabric","No action is required."
"ONEP","2","GET_BUFFER","Onepsync ISSU client failed to get buffer for message. Error: [dec] ([chars])","The Onepsync ISSU client failed to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","LOG_STD_SH_CMD_ACTION( show logging and show checkpoint client)"
"ONEP","2","INIT","Onepsync ISSU client initialization failed to [chars]. Error: [dec] ([chars])","The Onepsync ISSU client could not be initialized. This initialization failure must be addressed before in-service software upgrade or downgrade can be performed successfully. If you do not address this failure, there will be downtime during software upgrade or downgrade.","LOG_STD_ACTION"
"ONEP","2","NE_PSS_32_ERR","ONEP [chars] configuration mismatch: Network Element([dec]) / PSS([dec])","The Network Element and Persistent Storage for the running-config are out of sync. If no other error has occurred, the Network Element configuration will take precedence.","LOG_STD_SH_CMD_ACTION( Try reconfiguring the item, possibly using the [no] form to restore a default value if a new one doesnttake.The'showrunning-config'commandshouldbeusedtoseeifthiserrorpersists.)'"
"ONEP","2","NE_PSS_STRING_ERR","ONEP [chars] configuration mismatch: Network Element([chars]) / PSS([chars])","The Network Element and Persistent Storage for the running-config are out of sync. If no other error has occurred, the Network Element configuration will take precedence.","LOG_STD_SH_CMD_ACTION( Try reconfiguring the item, possibly using the [no] form to restore a default value if a new one doesnttake.The'showrunning-config'commandshouldbeusedtoseeifthiserrorpersists.)'"
"ONEP","2","SEND_NEGO_FAILED","Onepsync ISSU client failed to send negotiation message. Error: [dec] ([chars])","The Onepsync ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","LOG_STD_SH_CMD_ACTION( show logging and show checkpoint client)"
"ONEP","2","SESSION_NEGO_FAIL_START","Failed to start Onepsync ISSU session negotiation. Error: [dec] ([chars])","The Onepsync ISSU client failed to start session negotition. If a problem occurs with the ISSU session start, the standby device cannot be brought up properly.","LOG_STD_SH_CMD_ACTION( show issu session <client_id"
"ONEP","2","SESSION_REGISTRY","Onepsync ISSU client failed to register session information. Error: [dec] ([chars])","The Onepsync ISSU client failed to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly.","LOG_STD_SH_CMD_ACTION( show issu capability entries <client_id"
"ONEP","3","AUTHEN_ERR","[[chars]]: Authentication/authorization failed. [chars]","The session authentication has failed","LOG_STD_SH_CMD_ACTION( Check userscredentialsarematchedagainsttheAAA/localusersconfiguredontheNetwkElement.)'"
"ONEP","3","BUSY_ERR","[[chars]]: The requested resource is currently busy. [chars].","The usage of the resource has exceeded the configured threshold value","LOG_STD_SH_CMD_ACTION( Check the current resource usage and configured resource threshold. cpu threshold rising <value"
"ONEP","3","DISABLED_ERR","[[chars]]: [chars] is disabled.","The requested service set is in disabled state. All the service requests for that service set will be rejected.","LOG_STD_SH_CMD_ACTION( Make sure the service set is enabled. connectedapps service set <name"
"ONEP","3","DUPLICATE_ERR","[[chars]]: Requested entity [chars] already exists.","The connection request to the network element already exists","LOG_STD_SH_CMD_ACTION( Make sure the uniqueness of the application name. One session per application is allowed on a network element.)"
"ONEP","3","INVALID_SESSION","Onepsync ISSU client does not have a valid registered session.","The Onepsync ISSU client does not have a valid registered session.","LOG_STD_SH_CMD_ACTION( show issu capability entries <client_id"
"ONEP","3","LISP_DISABLED_ERR","[[chars]]: [chars] is disabled.","The requested service set is in disabled state. All the service requests for that service set will be rejected.","LOG_STD_SH_CMD_ACTION( Make sure the service set is enabled. connectedapps service set lisp)"
"ONEP","3","MSG_NOT_OK","Onepsync ISSU client MessageType[dec]'isnotcompatible'","The Onepsync ISSU client received an incompatible message from the peer device. The message cannot be processed.","LOG_STD_SH_CMD_ACTION( show issu message group <client_id"
"ONEP","3","MSG_SIZE","Onepsync ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] ([chars])","The Onepsync ISSU client failed to calculate the MTU for the specified message. The Onepsync ISSU client is not able to send the message to the standby device.","LOG_STD_SH_CMD_ACTION( show issu message group <client_id"
"ONEP","3","SESSION_UNREGISTRY","Onepsync ISSU client failed to unregister session information. Error: [dec] ([chars])","The Onepsync ISSU client failed to unregister session information.","LOG_STD_SH_CMD_ACTION( show issu session <client_id"
"ONEP","3","VERSION_ERR","[[chars]]: ONE-P version incompatible between client and network element. [chars]","The ONE-P client service set version is incompatible with the one installed on the network element","LOG_STD_SH_CMD_ACTION( Make sure the version running on the client side is compatible with the one installed on the network element )"
"ONEP","4","ONEP_DISABLED","ONEP feature is administratively disabled, terminated [[dec]] connected application(s)","Administrator has disabled ONEP feature while application sessions were active. All active sessions have been terminated. To enable ONEP again use 'feature onep' command in configuration mode.","LOG_STD_SH_CMD_ACTION( No action is required if this was deliberate operation. To enable ONEP again use 'feature onep' command in configuration mode.)"
"ONEP","6","HISTORY","[chars]","This syslog message is used to display onePK history messages when the historysyslog'onepcommandisenabled.'","LOG_STD_SH_CMD_ACTION( No action is required. Use nohistorysyslog'attheonepconfigurationprompttoturnoffthisloggingifdesired.)'"
"ORI_FWD","2","CRIT_MSG","[chars]","Debug log message","No action is required."
"ORI_FWD","6","ORF_DEBUG_MSG","[chars]","Debug log message","No action is required."
"ORI_MAC","2","ORI_MAC_CRIT_MSG","[chars]","Debug log message","No action is required."
"ORI_MAC","6","ORI_MAC_DEBUG_MSG","[chars]","Debug log message","No action is required."
"ORI_XBAR_USD","2","CRIT_MSG","[chars]","Critical log message","No action is required."
"ORI_XBAR_USD","2","FR_CRC","[chars]","FR CRC error message","No action is required."
"ORI_XBAR_USD","2","SYNC_ERR","[chars]","Sync loss error","No action is required."
"ORI_XBAR_USD","4","WARNING_MSG","[chars]","Warning log message","No action is required."
"ORI_XBAR_USD","6","DEBUG_MSG","[chars]","Debug log message","No action is required."
"OTM","2","OTM_EEM_FAIL","OTM failed to register with EEM","OTM process failed to register with eem, exiting now","No action is required."
"OTM","3","OTM_ERROR","[chars] [chars]","[chars1][chars2]","No action is required."
"OTM","5","OTM_OBJECT_STATUS","Status of tracking object [dec] changed to [chars]","Status of tracking object [dec] changed to [chars]","No action is required."
"OTM","5","OTM_OBJ_ADD",": Tracking object [dec] configured, status of the object [chars]","Tracking Object [dec] configured, status of the object [chars]","No action is required."
"OTM","6","OTM_EXITED","OTM process exited","OTM process is terminated","No action is required."
"OTM","6","OTM_OBJ_REM",": Tracking object [dec] removed","Tracking Object [dec] removed","No action is required."
"OTM","6","OTM_STARTED","OTM process started","OTM process is up and running","No action is required."
"OTM","6","OTM_TRACK_START","Client started tracking object [dec]","Client has started tracking object [dec]","No action is required."
"OTM","6","OTM_TRACK_STOP","Client stopped tracking object [dec]","Client has stopped tracking object [dec]","No action is required."
"PHY_USD-SLOT#","4","LOG_PHY_ISSU_LINK_ST_CHNG","Port [dec]: link state during ISSU","Port Link status changed while perfoming an In Service System Upgrade. Disabling the port.","No action is required."
"PIXM","2","PIXM_SYSLOG_MESSAGE_TYPE_CRIT","[chars]","PIXM has encountered a critical error","Please collect PIXM tech support using showtechpixm'and'showtechpixmc-all''"
"PIXM","3","PIXM_SYSLOG_MESSAGE_TYPE_ERR","[chars]","PIXM has encountered a error","Please collect PIXM tech support using showtechpixm'and'showtechpixmc-all''"
"PIXM","4","PIXM_SYSLOG_MESSAGE_TYPE_WARNING","[chars]","PIXM has encountered a warning-level error","Please collect PIXM tech support using showtechpixm'and'showtechpixmc-all''"
"PIXM","7","PIXM_SYSLOG_MESSAGE_TYPE_DEBUG","[chars]","This is a debug output from PIXM","Please collect PIXM tech support using showtechpixm'and'showtechpixmc-all''"
"PLATFORM","0","CHASSIS_CLKSWITCH","Hardware clock switched to redundant clock-[dec]","Clock module on chassis deteted a failure and switched to redundant clock module.","Please perform a showplatforminternalinfo'tocollectmoreinformation.'"
"PLATFORM","0","CHASSIS_CLKSWRESET","Switch reset due to clock switch","Chassis clock source has failed and system will be reset. System will automatically start using redundant clock module.","Please refer to the platform document on clock modules."
"PLATFORM","0","CHASSIS_CLKSW_MODULE_RESET","Modules reset due to clock switch","Chassis clock source has switched and all Vegas line cards will be reset. System will automatically continue using redundant clock module.","Please refer to the platform document on clock modules."
"PLATFORM","0","FAIL_REMOVED","Fan module removed. Fan[dec] has been absent for [dec] seconds","Fan module is removed. This could lead to temperature alarms.","Replace the fan module ASAP."
"PLATFORM","0","MOD_TEMPMAJALRM","[chars] reported Major temperature alarm. Sensor=[dec] Temperature=[dec] MajThreshold=[dec]","Module in slot [decimal digit] exceeded major temperature threshold.","Please perform a showenvtemperature'tocollectmoreinformation.'"
"PLATFORM","0","MOD_TEMPSHUTDOWN","[chars] powered down due to major temperature alarm for Sensor [dec].","Module in slot [decimal digit] shutdown due to temperature exceeding major threshold.","Please perform a showenvtemperature'tocollectmoreinformation.'"
"PLATFORM","0","MOD_TEMPWARMALRM","[chars] reported Warm temperature alarm. Sensor=[dec] Temperature=[dec] WarmThreshold=[dec]","Module in slot [decimal digit] exceeded warm temperature threshold.","Please perform a showenvtemperature'tocollectmoreinformation.'"
"PLATFORM","0","PFM_EMERGENCY","[chars]","Platform Emergency","No action is required."
"PLATFORM","0","SUP_SPROM_ERROR","Unable to read SPROM for Sup in slot [dec]","The supervisor in slot [decimal digit] was not able to read its SPROM.","No action is required."
"PLATFORM","0","SUP_WRONGSLOTNUM","Supervisor powered up in WRONG SLOT:[dec] (Serial number [chars])","The supervisor is comming up in wrong slot [decimal digit].","No action is required."
"PLATFORM","0","SYS_LC_DRIVER_LOAD_FAILED","Failed to load linecard module drivers","Failed to load drivers.","Image is possibly corrupt. Try to load a different image."
"PLATFORM","0","SYS_RESET","[chars] System shutdown in [dec] seconds","System shutdown in [decimal digit] seconds.","Please perform a showenvtemperature'tocollectmoreinformation.'"
"PLATFORM","0","SYS_SHUTDOWN_FAN_REMOVAL","System shutdown in [dec] seconds due to fan removal","System shutdown in [decimal digit] seconds due to removal of fan module.","Please perform a showenvfan'tocollectmoreinformation.'"
"PLATFORM","0","SYS_SHUTDOWN_MDS9124_FAN_FAIL","System shutdown in [dec] seconds due to less than 4 fans operating.","System shutdown in [decimal digit] seconds due to less than 4 fans operating.","Please perform a showenvfan'tocollectmoreinformation.'"
"PLATFORM","0","SYS_SHUTDOWN","System shutdown in [dec] seconds due to major temperature alarm","System shutdown in [decimal digit] seconds due to temperature exceeding major threshold.","Please perform a showenvtemperature'tocollectmoreinformation.'"
"PLATFORM","0","SYS_SUP_DRIVER_LOAD_FAILED","Failed to load supervisor module drivers","Failed to load drivers.","Image is possibly corrupt. Try to load a different image"
"PLATFORM","0","XBAR_CARD_CLK_FAIL","Xbar card in slot:[dec] (Serial number [chars]) encountered clock failure","The xbar in slot [decimal digit] encountered clock failure.","No action is required."
"PLATFORM","0","XBAR_CARD_INCOMPAT_CHASSIS","Xbar card in slot:[dec] (Part number [chars]) Incompatible with backplane chassis Part Num:[chars]","The xbar in slot [decimal digit] is incompatible with backplane chassis.","No action is required."
"PLATFORM","0","XBAR_WRONGSLOTNUM","Xbar powered up in WRONG SLOT:[dec] (Serial number [chars])","The xbar in slot [decimal digit] powered up in wrong slot.","No action is required."
"PLATFORM","1","FABRIC_SWITCH_FAN_FAIL","Less than 4 required fans operating.","Fan module has failed leaving less than 4 total fans operating. Fan needs to be replaced. This can lead to overheating and temperature alarms.","Please perform a showplatforminternalinfo'tocollectmoreinformation.'"
"PLATFORM","1","FAN_FAIL","Fan module Failed","Fan module has failed and needs to be replaced. This can lead to overheating and temperature alarms.","Please perform a showplatforminternalinfo'tocollectmoreinformation.'"
"PLATFORM","1","PFM_ALERT","[chars]","Platform Alert","No action is required."
"PLATFORM","1","PS_SINGLE_INPUT","Both power inputs are connected for Power supplies, remove single-input configuration for optimal power usage","Current power supply redundancy mode may not be optimal","Please perform a showenvironmentpower'and'showplatforminternalinfo'tocollectmoreinformation.'"
"PLATFORM","1","XBAR_PWRDENY","Xbar [dec] can not be powered up due to insufficient power (Serial number [chars])","Available power in power supplies is not sufficient to power up the xbar","You can verify available power and current usage using command showenvpower'.Pleaserefertopowersupplydocumentonhowtoincreasepowersupplycapacity.'"
"PLATFORM","2","9134_FAN_FAIL","Fan module [dec] Failed","Fan module has failed and needs to be replaced. This can lead to overheating and temperature alarms.","Please perform a showplatforminternalinfo'tocollectmoreinformation.'"
"PLATFORM","2","9134_FAN_OK","Fan module [dec] ok","Fan module is ok","No action is required."
"PLATFORM","2","CASA_FAN_FAIL","Fan module [dec] Failed","Fan module has failed and needs to be replaced. This can lead to overheating and temperature alarms.","Please perform a showplatforminternalinfo'tocollectmoreinformation.'"
"PLATFORM","2","CASA_FAN_OK","Fan module [dec] ok","Fan module is ok","No action is required."
"PLATFORM","2","CHASSIS_CLKMODFAULTY","Chassis clock module [dec] faulty","Clock module on chassis is faulty or has been removed.","Please perform a showplatforminternalinfo'tocollectmoreinformation.'"
"PLATFORM","2","CHASSIS_CLKMODOK","Chassis clock module [dec] ok","Clock module on chassis is functioning properly.","No action is required."
"PLATFORM","2","CHASSIS_CLKSRC","Current chassis clock source is clock-[dec]","The current chassis clock source is [decimal digit].","No action is required."
"PLATFORM","2","FANLET_FAN_FAIL","Failed Fanlets for Fan [dec] ([chars] fan) : [chars]","The specified fanlets have failed. This can lead to overheating and temperature alarms.","Please perform a showplatforminternalinfo'tocollectmoreinformation.'"
"PLATFORM","2","FANMOD_FAN_FAIL","Fan module [dec] ([chars] fan) Failed/Removed","Fan module has failed and needs to be replaced. This can lead to overheating and temperature alarms.","Please perform a showplatforminternalinfo'tocollectmoreinformation.'"
"PLATFORM","2","FANMOD_FAN_OK","Fan module [dec] ([chars] fan) ok","Fan module is ok","No action is required."
"PLATFORM","2","FAN_OK","Fan module ok","Fan module is ok","No action is required."
"PLATFORM","2","FAN_REMOVED","Fan module [dec] (Serial number [chars]) [chars] removed","Fan module is removed","No action is required."
"PLATFORM","2","INSUFFICIENT_MAC","program management port on all the non-default VDCs","Could not program the mac address for the management port of all the VDCs","No action is required."
"PLATFORM","2","MEMORY_ALERT_RECOVERED","Memory Status Alert : [chars]","Memory alert event received","None"
"PLATFORM","2","MEMORY_ALERT","Memory Status Alert : [chars]. Usage [chars]% of Available Memory","Memory alert event received","None"
"PLATFORM","2","MOD_ALL_PWRDN_NOXBAR","All modules powered down due to non-availability of xbar modules","All modules in switch are powered down because all xbar modules are offline","Please perform a showmodule','showplatforminternalallmodule[decimaldigit]'and'showmoduleinternalallmodule[de cimaldigit]'tocollectmoreinformationifyoususpectmodulehasbeenpowereddownduetoerrors.Atleast onexbarmodulehastobeformodulestofunction'"
"PLATFORM","2","MOD_DETECT","Module [dec] detected (Serial number [chars]) Module-Type [chars] Model [chars]","A new module in slot [decimal digit] is detected.","No action is required."
"PLATFORM","2","MOD_PWRDENY","Module [dec] can not be powered up due to insufficient power (Serial number [chars])","Available power in power supplies is not sufficient to power up the module","You can verify available power and current usage using command showenvpower'.Pleaserefertopowersupplydocumentonhowtoincreasepowersupplycapacity.'"
"PLATFORM","2","MOD_PWRDN","Module [dec] powered down (Serial number [chars])","The module in slot [decimal digit] is powered down.","Please perform a showmodule','showplatforminternalallmodule[decimaldigit]'and'showmoduleinternalallmodule[de cimaldigit]'tocollectmoreinformationifyoususpectmodulehasbeenpowereddownduetoerrors.'"
"PLATFORM","2","MOD_PWRFAIL_EJECTORS_OPEN","All ejectors open, Module [dec] will not be powered up (Serial number [chars])","The module can not be powered up because all the ejectors are open","Please perform a showplatforminternalallmodule[decimaldigit]'and'showmoduleinternalallmodule[decimaldigit]''sh owspromxbar[dec][dec]'toreadmoduleIDPROMcontentstocollectmoreinformation.'"
"PLATFORM","2","MOD_PWRFAIL","Module [dec] failed to power up (Serial number [chars])","The module in slot [decimal digit] failed to power up","Please perform a showplatforminternalallmodule[decimaldigit]'andtocollectmoreinformation.'"
"PLATFORM","2","MOD_PWRIDPROMFAIL","Module [dec] failed to power up due to IDPROM read error","The module can not be powered up due to IDPROM read error","Please perform a showplatforminternalallmodule[decimaldigit]'and'showmoduleinternalallmodule[decimaldigit]''sh owsprommodule[dec][dec]'toreadmoduleIDPROMcontentstocollectmoreinformation.'"
"PLATFORM","2","MOD_PWRIDPROM_SW_CARD_ID_UNKNOWN","Module [dec] failed to power up. (Unknown card. Could not get software-card-id)","The module can not be powered up due to missing SWID in core-plugin for this CARDID","Please perform a showplatforminternalallmodule[decimaldigit]'and'showmoduleinternalallmodule[decimaldigit]''sh owsprommodule[dec][dec]'toreadmoduleIDPROMcontentstocollectmoreinformation.'"
"PLATFORM","2","MOD_PWRUP_XBAR","Modules powered up due to xbar availability","Modules powered up because atleast one xbar module is online","No action needed"
"PLATFORM","2","MOD_PWRUP","Module [dec] powered up (Serial number [chars])","The module in slot [decimal digit] is powered up.","No action is required."
"PLATFORM","2","MOD_REMOVE","Module [dec] removed (Serial number [chars])","The module in slot [decimal digit] has been removed.","No action is required."
"PLATFORM","2","MOD_TEMPMAJOR2WARM","[chars] recovered from minor temperature alarm. Warm alarm pending. Sensor=[dec] Temperature=[dec] MajTheshold=[dec] WarmThreshold=[dec]","Module in slot [decimal digit] warm temperature threshold.","Please perform a showenvtemperature'tocollectmoreinformation.'"
"PLATFORM","2","MOD_TEMPMAJOR_OK","[chars] recovered from major temperature alarm. Sensor=[dec] Temperature=[dec] MajThreshold=[dec]","Module in slot [decimal digit] major temperature threshold.","Please perform a showenvtemperature'tocollectmoreinformation.'"
"PLATFORM","2","MOD_TEMPMINALRM","[chars] reported minor temperature alarm. Sensor=[dec] Temperature=[dec] MinThreshold=[dec]","Module in slot [decimal digit] has exceeded minor temperature threshold.","Please perform a showenvtemperature'tocollectmoreinformation.'"
"PLATFORM","2","MOD_TEMPMINOR2WARM","[chars] recovered from minor temperature alarm. Warm alarm pending. Sensor=[dec] Temperature=[dec] MinTheshold=[dec] WarmThreshold=[dec]","Module in slot [decimal digit] warm temperature threshold.","Please perform a showenvtemperature'tocollectmoreinformation.'"
"PLATFORM","2","MOD_TEMPOK","[chars] recovered from minor temperature alarm. Sensor=[dec] Temperature=[dec] MinThreshold=[dec]","Module in slot [decimal digit] minor temperature threshold.","Please perform a showenvtemperature'tocollectmoreinformation.'"
"PLATFORM","2","MOD_TEMPRECOVER","[chars] recovered from major temperature alarm. Minor temperature alarm pending. Sensor=[dec] Temperature=[dec] MajThreshold=[dec] MinThresh=[dec]","Module in slot [decimal digit] recovered from major temperature threshold. Minor threshold still exceeded.","Please perform a showenvtemperature'tocollectmoreinformation.'"
"PLATFORM","2","MOD_TEMPWARM_OK","[chars] recovered from warm temperature alarm. Sensor=[dec] Temperature=[dec] WarmThreshold=[dec]","Module in slot [decimal digit] warm temperature threshold.","Please perform a showenvtemperature'tocollectmoreinformation.'"
"PLATFORM","2","PFM_CRITICAL","[chars]","Platform Critical","No action is required."
"PLATFORM","2","PFM_FATW_BUS_SWITCH_FAIL","Backplane two wire [chars] bus connection fault detected but failed to perform bus switchover(BUS_A to BUS_B)","Could not access some modules using BUS_A, but can access using BUS_B","Please perform a showplatforminternalerr''"
"PLATFORM","2","PFM_FATW_BUS_SWITCH","Backplane two wire [chars] bus connection or device fault caused bus switchover(BUS_A to BUS_B)","Could not access some modules using BUS_A, but can access using BUS_B","Please perform a showplatforminternalerr''"
"PLATFORM","2","PFM_IMG_CMPT_FAIL","Image version is not supported in this chassis.","This image version is not supported in this chassis.","Sup-platform"
"PLATFORM","2","PFM_LC_BOOT_DEV_ABSENT","No bootflash found in Module [dec]","No bootflash found.","Try to put in a bootflash in the module and try again."
"PLATFORM","2","PFM_LC_BOOT_DEV_FAIL","Bootflash access error in Module [dec]","Bad bootflash/corrupted filesystem.","Try to put in a known good bootflash in the module and try again."
"PLATFORM","2","PFM_LC_MOD_POWERED_DOWN","Module [dec] Powered Down. Module is not supported in this chassis. (Chassis Incompatible card)","Module Powered Down, because Module is not supported in this chassis. (Chassis Incompatible card)","Please perform a showmodule'toseethePowerDownreason.'"
"PLATFORM","2","PFM_LC_NETBOOT_FAIL","Netboot for Module [dec] failed","Netboot failed.","Try to replace the BIOS in the module."
"PLATFORM","2","PFM_LC_REGISTRATION_FAIL","Could not register with Module [dec]","Module registration failed.","Try to replace the module."
"PLATFORM","2","PFM_LC_STATUS","Module [dec] powered up with [dec] status","Status for the module that failed registration.","Try to replace the module."
"PLATFORM","2","PFM_LOW_MEMORY_CONDITION","Module [dec] is running low on memory. %ld percent used","Supervisor is running low on memory","Switchover"
"PLATFORM","2","PFM_MODULE_POWER_OFF_TRIGGER","Power-off [chars] due to [chars] policy trigger","Policy trigger initiated a module poweroff","None"
"PLATFORM","2","PFM_MODULE_POWER_OFF","Manual power-off of [chars] from Command Line Interface","User initiated a module power-off from the CLI","None"
"PLATFORM","2","PFM_MODULE_POWER_ON","Manual power-on of [chars] from Command Line Interface","User initiated a module power-on from the CLI","None"
"PLATFORM","2","PFM_MODULE_RESET","Manual restart of Module [dec] from Command Line Interface","User initiated a module reload from the CLI","None"
"PLATFORM","2","PFM_NETBOOT_DISABLE","Netboot for supervisor module in slot [dec] is disabled due to incompatible platform","Standby supervisor failed to powerup.","Try to replace the standby supervisor."
"PLATFORM","2","PFM_PREP_DEEP_SLEEP","Supervisor module in slot [dec] preparing to enter deep sleep mode","Deep sleep mode initiated by the Connectivity Management Processor (CMP) for this supervisor","No action is required."
"PLATFORM","2","PFM_PWR_MGMT_EPLD_VER_MISMATCH","Module [dec] Pwr Mgmt Epld (Version-[dec]) needs to be upgraded","Using a wrong version of Epld version can result in unexplainable behaviour","Upgrade Power Managment EPLD"
"PLATFORM","2","PFM_STDBY_POWERUP_FAIL","standby supervisor failed to powerup","Standby supervisor failed to powerup.","Try to replace the standby supervisor."
"PLATFORM","2","PFM_SYSTEM_RESET_TRIGGER","System restart due to [chars] policy trigger","Policy/trigger initiated a system reload","None"
"PLATFORM","2","PFM_SYSTEM_RESET","Manual system restart from Command Line Interface","User initiated a system reload from the CLI","None"
"PLATFORM","2","PFM_SYSTEM_SHUTDOWN_TRIGGER","System shutdown due to [chars] policy trigger","Policy/trigger initiated a system shutdown","None"
"PLATFORM","2","PFM_XBAR_RESET","Manual restart of Xbar [dec] from Command Line Interface","User initiated a xbar reload from the CLI","None"
"PLATFORM","2","PLUGIN_ABSENT","Module in slot[dec] (sw_card_id=[dec]) has missing plugin","Plugin not loaded, The LC cannot be poweredup","Load the associated plugin"
"PLATFORM","2","PS_ABSENT","Power supply [dec] is absent/shutdown, ps-redundancy might be affected","Power Supply is absent.","No action is required."
"PLATFORM","2","PS_CAPACITY_CHANGE","Power supply PS[dec] changed its capacity. possibly due to power cable removal/insertion (Serial number [chars])","Detected power supply capacity change.","Please refer to power supply document on increasing decreasing power supply capacity, configuring power supplies, etc. Please perform showenvironmentpower'and'showplatforminternalinfo'tocollectmoreinformation.'"
"PLATFORM","2","PS_CAPACITY_DIFFER","Detected power supplies with differing capacity. It is recommended to have same capacity for both powersupplies otherwise it may cause service disruptions","Detected a power supply that has differing capacity than an the otherpower supply.","Please refer to power supply document on increasing decreasing power supply capacity, configuring power supplies, etc. Please perform showenvironmentpower'and'showplatforminternalinfo'tocollectmoreinformation.'"
"PLATFORM","2","PS_DETECT","Power supply [dec] detected but shutdown (Serial number [chars])","Power Supply is detected but shutdown.","Please perform a showenvironmentpower'and'showplatforminternalinfo'tocollectmoreinformation.'"
"PLATFORM","2","PS_FAIL","Power supply [dec] failed or shut down (Serial number [chars])","Power Supply has failed or has been shutdown","Please perform a showenvironmentpower'and'showplatforminternalinfo'tocollectmoreinformation.Pleaserefertopow ersupplydocumentonincreasingdecreasingpowersupplycapacity,configuringpowersupplies,etc.'"
"PLATFORM","2","PS_FANFAIL","Fan in Power supply [dec] failed","Fan module in the Power Supply has failed","Please perform a showenvironmentpower'and'showplatforminternalinfo'tocollectmoreinformation.'"
"PLATFORM","2","PS_FANOK","Fan in Power supply [dec] ok","Fan module in the Power Supply is ok.","No action is required."
"PLATFORM","2","PS_MISMATCH","Detected power supply [chars]. This reduces the redundant power available to the system and can cause service disruptions (Serial number [chars])","Detected a new power supply that has reduced capacity than an existing power supply.","Please refer to power supply document on increasing decreasing power supply capacity, configuring power supplies, etc. Please perform showenvironmentpower'and'showplatforminternalinfo'tocollectmoreinformation.'"
"PLATFORM","2","PS_OK","Power supply [dec] ok (Serial number [chars])","Power Supply is ok.","No action is required."
"PLATFORM","2","PS_PWR_INPUT_MISSING","Power supply [dec] present but all AC/DC inputs are not connected, power redundancy might be affected","Power Supply is present but not at full capacity.","No action is required."
"PLATFORM","2","PS_RED_MODE_CHG","Power supply redundancy mode changed to [chars]","Power supply redundancy mode changed notification","Please perform a showenvironmentpower'and'showplatforminternalinfo'tocollectmoreinformation.'"
"PLATFORM","2","PS_RED_MODE_RESTORED","Power redundancy operational mode changed to configured mode","Power Supply redundancy mode changes.","No action is required."
"PLATFORM","2","PS_REMOVE_LAST","Unexpected removal of last power supply [dec]. (Serial number [chars])","Unexpected removal the only power supply in the system.","Power supply unit may be faulty. Contact CISCO to replace the unit."
"PLATFORM","2","PS_REMOVE","Power supply [dec] removed (Serial number [chars])","Power Supply is removed.","No action is required."
"PLATFORM","2","PS_UNKNOWN","Detected an unknown power supply [dec] for CISCO Multilayer Switch (Serial number [chars])","Unable to determine power supply type. Default power supply types will be assumed.","Please refer to power supply document on increasing decreasing power supply capacity, configuring power supplies, etc."
"PLATFORM","2","PS_UNSUPPORTED","Detected an unsupported power supply [dec] [chars] for CISCO Multilayer Switch (Serial number [chars])","This power supply is not supported for the CISCO Multilayer Switches.","Please refer to power supply document on increasing decreasing power supply capacity, configuring power supplies, etc."
"PLATFORM","2","SYS_IDPROMBAD_RECOVER_FAIL","Chassis IDPROM [dec] data re-initialization Un-successful. Data is invalid","Chassis IDPROM [decimal digit] re-initialization was unsuccessful. Data is invalid.","Please perform a showsprommodule[decimaldigit]1'toreadmoduleIDPROMcontentsandcollectmoreinformation.'"
"PLATFORM","2","SYS_IDPROMBAD_RECOVER_PASS","Chassis IDPROM [dec] data re-initialized successfully","Chassis IDPROM [decimal digit] invalid data was succesfully re-initialized to valid.","Please perform a showsprommodule[decimaldigit]1'toreadmoduleIDPROMcontentsandverifytheinformation.'"
"PLATFORM","2","SYS_IDPROMBAD","Chassis IDPROM [dec] data invalid","Chassis IDPROM [decimal digit] contains invalid data.","Please perform a showsprommodule[decimaldigit]1'toreadmoduleIDPROMcontentsandcollectmoreinformation.'"
"PLATFORM","2","XBAR_DETECT","Xbar [dec] detected (Serial number [chars])","A new xbar in slot [decimal digit] is detected.","No action is required."
"PLATFORM","2","XBAR_PWRFAIL_EJECTORS_OPEN","All ejectors open, Xbar [dec] will not be powered up (Serial number [chars])","The xbar can not be powered up because all the ejectors are open","Please perform a showplatforminternalallmodule[decimaldigit]'and'showmoduleinternalallmodule[decimaldigit]''sh owspromxbar[dec][dec]'toreadmoduleIDPROMcontentstocollectmoreinformation.''"
"PLATFORM","2","XBAR_REMOVE","Xbar [dec] removed (Serial number [chars])","The xbar in slot [decimal digit] has been removed.","No action is required."
"PLATFORM","3","EJECTOR_STAT_CHANGED","Ejectorsstatusinslot[dec]haschanged,[chars]Ejectoris[chars],[chars]Ejectoris[chars]'","Ejector status has changed","None"
"PLATFORM","3","MOD_BRINGUP_MULTI_LIMIT","Giving up after multiple attempts were made to bring up the Module [dec], (Serial number [chars])","The module can not be powered up even after three attempts","Please perform a showplatforminternalallmodule[decimaldigit]'and'showmoduleinternalallmodule[decimaldigit]''sh owspromxbar[dec][dec]'toreadmoduleIDPROMcontentstocollectmoreinformation.'"
"PLATFORM","3","MOD_PWRFAIL_MULTI","Module [dec] failed to power up multiple times (Serial number [chars])","The module can not be powered up even after three attempts","Please perform a showplatforminternalallmodule[decimaldigit]'and'showmoduleinternalallmodule[decimaldigit]''sh owspromxbar[dec][dec]'toreadmoduleIDPROMcontentstocollectmoreinformation.'"
"PLATFORM","3","PFM_ERROR","[chars]","Platform Error","No action is required."
"PLATFORM","3","SINGLE_EJECTOR_STAT_CHANGED","Ejectorsstatusinslot[dec]haschanged,Ejectoris[chars]'","Ejector status has changed","None"
"PLATFORM","3","XBAR_BRINGUP_MULTI_LIMIT","Giving up after multiple attempts were made to bring up the Xbar [dec], (Serial number [chars])","The module can not be powered up even after three attempts","Please perform a showplatforminternalallmodule[decimaldigit]'and'showmoduleinternalallmodule[decimaldigit]''sh owspromxbar[dec][dec]'toreadmoduleIDPROMcontXBAentstocollectmoreinformation.'"
"PLATFORM","3","XBAR_PWRFAIL_MULTI","Xbar [dec] failed to power up multiple times (Serial number [chars])","The xbar can not be powered up even after three attempts","Please perform a showplatforminternalallmodule[decimaldigit]'and'showmoduleinternalallmodule[decimaldigit]''sh owspromxbar[dec][dec]'toreadmoduleIDPROMcontentstocollectmoreinformation.'"
"PLATFORM","3","XBAR_PWRFAIL","Xbar [dec] failed to power up (Serial number [chars])","The xbar in slot [decimal digit] failed to power up","Please perform a showplatforminternalallmodule[decimaldigit]'andtocollectmoreinformation.'"
"PLATFORM","3","XBAR_PWRIDPROMFAIL","Xbar [dec] failed to power up due to IDPROM read error","The xbar can not be powered up due to IDPROM read error","Please perform a showplatforminternalallmodule[decimaldigit]'and'showmoduleinternalallmodule[decimaldigit]''sh owspromxbar[dec][dec]'toreadmoduleIDPROMcontentstocollectmoreinformation.'"
"PLATFORM","3","XBAR_PWRIDPROM_SW_CARD_ID_UNKNOWN","Xbar [dec] failed to power up. (Unknown card. Could not get software-card-id)","The xbar can not be powered up due to missing SWID in core-plugin for this CARDID","Please perform a showplatforminternalallmodule[decimaldigit]'and'showmoduleinternalallmodule[decimaldigit]''sh owspromxbar[dec][dec]'toreadmoduleIDPROMcontentstocollectmoreinformation.'"
"PLATFORM","4","MOD_TEMPACCESSFAIL","[chars] temperature sensor [dec] access failed","Module in slot [decimal digit] unable to access temperature sensor.","Please perform a showenvtemperature'tocollectmoreinformation.'"
"PLATFORM","4","MOD_TEMPFAIL","[chars] temperature sensor [dec] failed","Module in slot [decimal digit] contains a faulty temperature sensor.","Please perform a showenvtemperature'tocollectmoreinformation.'"
"PLATFORM","4","PFM_FAN_FLTR_STATUS","Fan Filter status: [chars]","Fan Filter status: Present/Absent","Please perform a showplatforminternalinfo.'"
"PLATFORM","4","PFM_PS_RED_MODE_CHG","Power redundancy mode changed to [chars]","Power redundancy mode changed","Please perform a showplatforminternalinfo.'"
"PLATFORM","4","PFM_WARNING","[chars]","Platform Warning","No action is required."
"PLATFORM","5","FAN_DETECT","Fan module [dec] (Serial number [chars]) [chars] detected","Fan module is detected","No action is required."
"PLATFORM","5","FAN_STATUS","Fan module [dec] (Serial number [chars]) [chars] current-status is [chars]","Fan module changed status","No action is required."
"PLATFORM","5","FEX_FAN_DETECT","Fex [dec] Fan Module [dec] detected","Fex Fan module is detected","No action is required."
"PLATFORM","5","FEX_FAN_REMOVE","Fex [dec] Fan Module [dec] removed","Fex Fan module is removed","No action is required."
"PLATFORM","5","FEX_PS_FOUND","Fex [dec] Power Supply [dec] found (Serial number [chars])","Fex power supply is found","No action is required."
"PLATFORM","5","FEX_PS_REMOVE","Fex [dec] Power Supply [dec] removed (Serial number [chars])","Fex power supply is removed","No action is required."
"PLATFORM","5","MOD_STATUS","[chars] current-status is [chars]","Module in slot [decimal digit] changed status.","No action is required."
"PLATFORM","5","PFM_NOTICE","[chars]","Platform Notice","No action is required."
"PLATFORM","5","PS_FOUND","Power supply [dec] found (Serial number [chars])","Power Supply is detected.","No action is required."
"PLATFORM","5","PS_STATUS","PowerSupply [dec] current-status is [chars] [chars]","Module in slot [decimal digit] changed status.","No action is required."
"PLATFORM","5","XBAR_PWRDN","Xbar [dec] powered down (Serial number [chars])","The xbar in slot [decimal digit] is powered down.","Please perform a showmodulexbar','showplatforminternalallmodule[decimaldigit]'and'showmoduleinternalallmodul e[decimaldigit]'tocollectmoreinformationifyoususpectmodulehasbeenpowereddownduetoerrors.'"
"PLATFORM","5","XBAR_PWRUP","Xbar [dec] powered up (Serial number [chars])","The xbar in slot [decimal digit] is powered up.","No action is required."
"PLATFORM","6","PFM_INFO","[chars]","Platform Info","No action is required."
"PLATFORM","7","PFM_CLOCK_UPD_FAIL","Clock update failed due to context-switch delay of [dec] msec","System shutdown in [decimal digit] seconds.","Please perform a showenvtemperature'tocollectmoreinformation.'"
"PLOG_SUP","4","PLOG_SUP_EXIT","Persistent Logger encountered an error [dec].","Persistent Logger encountered an error","No action is required."
"PLOG","4","PLOG_LC_EXIT","Persistent Logger encountered an error [dec]","Persistent Logger encountered an error","No action is required."
"PLSM","3","EDP_ERR","Interface [chars] in Error Disabled Policy(EDP) state Check : show interface status error policy [detail]","Error Disabled Policy State for a interface.","None"
"PLSM","6","SEQ_INFO","EDP State Cleared for interface [chars] vlans [chars]","EDP State cleared for a interface.","None"
"PLTFM_CONFIG","3","PC_ACL_LOU_COMMIT_RESPONSE_FAIL_LOG","LOU threshold commit failed.","LOU threshold response to commit failed.","No action is required."
"PLTFM_CONFIG","3","PC_ACL_LOU_COMMIT_TIMEOUT_LOG","LOU threshold commit timed out.","LOU threshold response to commit timed out.","No action is required."
"PLTFM_CONFIG","3","PC_ACL_LOU_VERIFY_RESPONSE_FAIL_LOG","LOU threshold verification failed, active acls are using more LOUs than requested threshold, aborting operation.","LOU threshold response to verify failed, so sending abort msg to all LC aclqos.","No action is required."
"PLTFM_CONFIG","3","PC_ACL_LOU_VERIFY_TIMEOUT_LOG","LOU threshold verification timed out, aborting operation.","LOU threshold response to verify timed out, so sending abort msg to all LC aclqos.","No action is required."
"PLTFM_CONFIG","4","XL_LICENSE_MIX_NOTIFY","Mixed use of non-XL with XL modules in the same VDC may limit common resources to non-XL capacity.","This is a reminder that mixing non-XL and XL modules in the same VDC may limit XL modules to the capacity of non-XL modules.","No action is required."
"PLUGIN","2","LOAD_REQUEST_FAILED_ON_STANDBY","Load request failed on standby. rc ([hex])","Load request failed on standby","No action is required."
"PLUGIN","2","NOTIFY_MSG_FAILURE","Plugin notify message ([chars]) returned failure (rc [hex])","Plugin notify message returned failure.","No action is required."
"PLUGIN","2","NO_MEMORY","Memory allocation failed (size [dec])","The service failed to allocate memory.","No action is required."
"PLUGIN","2","PLUGIN_EXTRACT_FAILED_ON_STANDBY","Plugin extraction failed on standby. rc ([hex])","Plugin extraction failed on standby","No action is required."
"PLUGIN","2","PLUGIN_LOAD_INTERNAL_ERROR","Plugin has internal error during load operation. Reason: [chars]","Plugin has internal error","No action is required."
"PLUGIN","2","PLUGIN_UNLOAD_INTERNAL_ERROR","Plugin has internal error during unload operation. Reason: [chars]","Plugin has internal error","No action is required."
"PLUGIN","2","SEND_NOTIFY_MSG_FAILED","Failed to send plugin notify message ([chars]). Reason: [chars]","Failed to send plugin notify message","No action is required."
"PLUGIN","2","UNEXPECTED_LOAD_SYNC","Received unexpected plugin load sync. Current plugin request ([dec])","Standby received load sync and current standby does not have an outstanding load request","No action is required."
"PLUGIN","2","UNEXPECTED_UNLOAD_SYNC","Received unexpected plugin unload sync. Current plugin request ([dec])","Standby received unload sync and current standby does not have an outstanding unload request","No action is required."
"PLUGIN","2","UNLOAD_REQUEST_FAILED_ON_STANDBY","Unload request failed on standby. rc ([hex])","Unload request failed on standby","No action is required."
"PLUGIN","2","UPDATE_SYS_INFO_FAILED","Failed to update system information ([chars])","Failed to update system information","No action is required."
"PLUGIN","3","MSG_SEND_FAILURE","failed to send [chars] to sap [dec]/[dec]: [chars]","Failed to send a message","No action is required."
"PMON","2","PGMON_RISING_THRESHOLD","[chars].","Port Group Rising Threshold Crossed","No action is required."
"PMON","2","PMON_CRIT_INFO","Port Monitor Critical Information: [chars].","Port Monitor Critical Information","No action is required."
"PMON","2","PMON_INIT_FAIL","Port Monitor : [chars].","Initialization failed, need to exit.","No action is required."
"PMON","2","PMON_MTS_FAIL","Port Monitor MTS Error: [chars].","Theresmtserror.'","No action is required."
"PMON","2","PMON_PORTGUARD_ACTION","[chars].","Port Guard config Applied","No action is required."
"PMON","3","PMON_ERR_INFO","Port Monitor Error: [chars].","Port Monitor error","No action is required."
"PMON","5","PGMON_FALLING_THRESHOLD","[chars].","Port Group Falling Threshold Crossed","No action is required."
"PMON","6","PMON_LOG_INFO","Port Monitor Log Information: [chars].","Port Monitor Log Information","No action is required."
"POAP","2","POAP_DHCP_DISCOVER_RECVD_NAK","Received DHCP NAK","Received DHCP NAK","No action is required."
"POAP","2","POAP_DHCP_DISCOVER_START","POAP DHCP Discover phase started","POAP DHCP Discover phase started","No action is required."
"POAP","2","POAP_FAILURE","[chars]","POAP failure","No action is required."
"POAP","2","POAP_INFO","[chars]","POAP Info","No action is required."
"POAP","2","POAP_INITED","POAP process initialized","POAP process initialized","No action is required."
"POAP","2","POAP_SCRIPT_DOWNLOADED","Successfully downloaded POAP script file","Successfully downloaded POAP script file","No action is required."
"POAP","2","POAP_SCRIPT_EXEC_SUCCESS","POAP script execution success","POAP script execution success","No action is required."
"POAP","2","POAP_SCRIPT_STARTED_MD5_NOT_VALIDATED","POAP script execution started(MD5 not validated)","POAP script execution started(MD5 not validated)","No action is required."
"POAP","2","POAP_SCRIPT_STARTED_MD5_VALIDATED","POAP script execution started(MD5 validated)","POAP script execution started(MD5 validated)","No action is required."
"POAP","2","POAP_SCRIPT_STARTED_MD5_VALIDATION_FAIL","POAP boot file validation failed","POAP boot file validation failed.","No action is required."
"POAP","5","POAP_DISABLED","POAP Disabled","POAP Service Disabled","No action is required."
"POAP","5","POAP_ENABLED","POAP Enabled","POAP Service nabled","No action is required."
"PONG","5","PONG_DISABLED","Pong Manager disabled","Pong Service Enabled","No action is required."
"PONG","5","PONG_ENABLED","Pong Manager enabled","Pong Service Enabled","No action is required."
"PONG","5","PONG_INJECTED","Pong packet injected","Pong packet injected","No action is required."
"PORT-CHANNEL","1","LC_CFG_FAILURE","configuring module [dec] failed [[chars]]","Module configuration failed","Module will be automatically reset"
"PORT-CHANNEL","1","MALLOC_FAILED","cannot allocate memory (size [dec])","No enough memory","No action is required."
"PORT-CHANNEL","1","MAP_PARAM_FAILURE","mapping parameter failed for [chars] [[chars]]","Parameter mapping failed","Specified service is misbehaving; check its status"
"PORT-CHANNEL","1","MCAST_SEND_FAILURE","failed to send multicast [chars]: [chars]","Failed to send a multicast message to all modules, usually because some module went down","Run show port-channel consistency to check consistency"
"PORT-CHANNEL","2","AUTO_CREATE_DISABLED","[chars] has been deprecated; [chars] [chars]","Auto create port-channel is deprecated and disabled","Convert the auto created channel to presistent by doing port-channel <n"
"PORT-CHANNEL","2","RESET_MODULE","reset module [dec] for not responding or returning error","A module is reset for not responding or returning error","No action is required."
"PORT-CHANNEL","3","COMPAT_CHECK_FAILURE","[chars] is not compatible","Compatibility check failed when adding ports to port-channel","Make sure the compatibility parameters are consistent while adding ports to port-channel, or use force option"
"PORT-CHANNEL","3","GENERAL_ERROR","[chars]","General error","No action is required."
"PORT-CHANNEL","3","LC_CFG_TIMEOUT_ENTRY_PORT_ERR_DISABLE","Failed to send LC config due to timeout, Port [chars] Err disabled","Failed to send a lc_config message","No action is required."
"PORT-CHANNEL","3","LC_CFG_UCAST_FAILED_PORT_ERR_DISABLE","Failed to send LC config unicast msg, Port [chars] Err disabled","Failed to send a lc_config unicast message","No action is required."
"PORT-CHANNEL","3","LC_CFG_UCAST_SEND_FAILURE","Failed to send LC config Unicast msg to slot [dec] node [hex] sap [dec]: [chars]. Resetting LineCard","Failed to send a lc_config unicast message","No action is required."
"PORT-CHANNEL","3","MSG_SEND_FAILURE","failed to send [chars] to sap [dec]: [chars]","Failed to send a message","No action is required."
"PORT-CHANNEL","3","PORT_CHANNEL_NOT_FOUND","[chars] is not found","Cannot find port-channel in its database, which indicates an inconsistency with an external component","No action is required."
"PORT-CHANNEL","3","TIMEOUT","timed out after [dec] seconds [type [chars], state [chars]]","Some operation timed out","Run show port-channel consistency to check all module connectivity and consistency"
"PORT-CHANNEL","4","PORT_CFG_DELETED","[chars] removed from [chars]","Port is removed from a port-channel because different module was inserted or module config purged","You lost some ports from port-channel, check if you want to add ports in the new module to the same port-channel."
"PORT-CHANNEL","4","PORT_INDIVIDUAL","port [chars] is operationally individual","The port is operating as an individual link even though it is locally or remotely configured to be part of a port channel","Check the configuration of the port locally and remotely to ensure that it can operate as part of a port channel"
"PORT-CHANNEL","4","PORT_NOT_FOUND","port [chars] is not part of port-channel","Cannot find the port in port-channel database, which indicates an inconsistency with an external component","No action is required."
"PORT-CHANNEL","4","RACE_WARN","[chars]","Warning of possible race condition","No action is required."
"PORT-CHANNEL","4","UNEXPECTED_RESPONSE","unexpected response [chars] from [chars]","Received an unexpected response and discarded","No action is required."
"PORT-CHANNEL","5","AUTO_CREATE_FAILURE","[chars] [chars]","Auto create process on the port failed","No action is required."
"PORT-CHANNEL","5","CREATED","[chars] created","A port-channel is created","No action is required."
"PORT-CHANNEL","5","DELETED","[chars] deleted","A port-channel is deleted","No action is required."
"PORT-CHANNEL","5","FOP_CHANGED","[chars]: first operational port changed from [chars] to [chars]","The first operational port in a port-channel is changed","No action is required."
"PORT-CHANNEL","5","MAX_CHANNEL_DISALLOWED","Module failed to come online because port channel interface <port-channel number","The port-channel number configured on the switch is larger than 128","Delete the set of port channel interface <port-channel interface"
"PORT-CHANNEL","5","PORT_ADDED","[chars] added to [chars]","Ports are added to a port-channel","No action is required."
"PORT-CHANNEL","5","PORT_DOWN","[chars]: [chars] is down","Port goes down in a port-channel","No action is required."
"PORT-CHANNEL","5","PORT_REMOVED","[chars] removed from [chars]","Ports are removed from a port-channel","No action is required."
"PORT-CHANNEL","5","PORT_UP","[chars]: [chars] is up","Port comes up in a port-channel","No action is required."
"PORT-CHANNEL","6","RESYNC","resyncing [chars] with all modules","Resync modules with sup after an error or switchover","No action is required."
"PORT-CHANNEL","7","GSYNC_DONE","global synchronization is done","Port-channel manager finished global synchronization","No action is required."
"PORT-CHANNEL","7","GSYNC_REQ","requesting global synchronization","Port-channel manager requested a global synchronization from active sup","No action is required."
"PORT-CHANNEL","7","START_ACTIVE","started in active mode","Port-channel manager started in active mode","No action is required."
"PORT-CHANNEL","7","START_DEFAULT","started with default configuration","Port-channel manager started with default configuration","No action is required."
"PORT-CHANNEL","7","START_STANDBY","started in standby mode","Port-channel manager started in standby mode","No action is required."
"PORT-CHANNEL","7","START_STATEFUL","started statefully","Port-channel manager started with running configuration","No action is required."
"PORT-CHANNEL","7","START_STATELESS","started statelessly","Port-channel manager started with startup configuration","No action is required."
"PORT-PROFILE","2","IF_REFRESH_FAILED","Interface Database Refresh failed for [chars]","Interface Database Refresh failed","No action is required."
"PORT-PROFILE","3","ALLOC_FAILED","Failed in File:[chars] Line:[dec] for type [dec] size [dec]","SDM process could not allocate heap memory in File:[chars], at line:[dec], for memory-type:[dec] of Size:[dec]","No action is required."
"PORT-PROFILE","3","ASSERTION_FAILED","Failed in File:[chars] Line:[dec]","PPM Process assertion failed in File:[chars], at line:[dec]","No action is required."
"PORT-PROFILE","3","CREATE_IF_FAILED","Running-config collection Failed for intf range [chars]","Running-config collection failed for :[chars]","No action is required."
"PORT-PROFILE","3","IF_APPLY_FAILED","Config Apply Failed","Config Apply Failed","No action is required."
"PORT-PROFILE","3","INTERFACE_NO_SHUTDOWN_FAILED","Interface no shutdown failed for [chars] after profile re-inherit","Interface could not be unshut after profile re-inherit","No action is required."
"PORT-PROFILE","3","INTERFACE_SHUTDOWN_FAILED","Interface shutdown failed for [chars] after failure to apply commands","Interface could not be shutdown after failure to apply commands","No action is required."
"PORT-PROFILE","3","PROFILE_CREATE_FAILED","Port-profile [chars] creattion failed with error '[chars]'","Port-profile:[chars] creation failed with [:chars]","No action is required."
"PORT-PROFILE","3","PROFILE_DEINHERIT_FAILED","Port-profile [chars] de-inherit failed with error [chars] on [chars]","Port-profile:[chars] de-inherit failed with [:chars] on [:chars]","No action is required."
"PORT-PROFILE","3","PROFILE_DELETE_FAILED","Port-profile [chars] is deletion failed with error '[chars]'","Port-profile:[chars] deletion failed with [:chars]","No action is required."
"PORT-PROFILE","3","PROFILE_DISABLE_FAILED","Port-profile [chars] disable failed with error '[chars]'","Port-profile:[chars] disable failed with [:chars]","No action is required."
"PORT-PROFILE","3","PROFILE_ENABLE_FAILED","Port-profile [chars] enable failed with error '[chars]'","Port-profile:[chars] enable failed with [:chars]","No action is required."
"PORT-PROFILE","3","PROFILE_INHERIT_FAILED","Port-profile [chars] inherit failed with error [chars] on [chars]","Port-profile:[chars] inherit failed with [:chars] on [:chars]","No action is required."
"PORT-PROFILE","6","PROFILE_CREATED","Port-profile [chars] is created successfully","Port-profile:[chars] is created","No action is required."
"PORT-PROFILE","6","PROFILE_DEINHERITED","Port-profile [chars] is de-inherited successfully on [chars]","Port-profile:[chars] is de-inherited on [:chars]","No action is required."
"PORT-PROFILE","6","PROFILE_DELETED","Port-profile [chars] is deleted successfully","Port-profile:[chars] is deleted","No action is required."
"PORT-PROFILE","6","PROFILE_DISABLED","Port-profile [chars] is disabled successfully","Port-profile:[chars] is disabled","No action is required."
"PORT-PROFILE","6","PROFILE_ENABLED","Port-profile [chars] is enabled successfully","Port-profile:[chars] is enabled","No action is required."
"PORT-PROFILE","6","PROFILE_INHERITED","Port-profile [chars] is inherited successfully on [chars]","Port-profile:[chars] is inherited on [:chars]","No action is required."
"PORT-RESOURCES","3","PRM_MSG_SEND_FAILURE","failed to send [chars] to sap [dec]: [chars]","Failed to send a message","No action is required."
"PORT-RESOURCES","5","INVALID_PORT_ACTIV_PKG_LICENSE_FILE_INSTALLED","Invalid on demand port activation license file is installed for module [dec] (number of port licenses = [dec])","Interfaces may not acquire port activation licenes during installation","Install a valid port activation license file"
"PORT-SECURITY","2","ALLOC_FAILED","Memory allocation failed for size:[dec] for [chars]","Memory allocation failed for size [dec] for [chars]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"PORT-SECURITY","2","FEATURE_DISABLED","Feature [chars] disabled due to [chars]","Feature [chars] is unavailable and will be disabled now","Please install the correct license and reenable"
"PORT-SECURITY","3","BINDING_CONFLICT","[chars]","An already logged in device is in conflict with the PSM active binding configurations. [chars] indicates the WWN of the login entity, interface","For port-security, the auto-learn feature can be used with activation to prevent this. This violating device or switch will be logged out"
"PORT-SECURITY","3","BINDING_VIOLATION","[chars]","A login happend that violates PSM binding configurations [chars] indicates the WWN of the login entity","Only entries in the activated database of PSM can login. Change the config and activate it again"
"PORT-SECURITY","3","CFS_NOTIF_ERR","[chars]","An error occurred during the processing of a CFS notification. [chars] indicates the actual cause for the error","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"PORT-SECURITY","3","DB_ERR","[chars]","An error occurred during an PSM database operation. [chars] indicates the reason for the error","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"PORT-SECURITY","3","EFMD_FC2_OPER_FAILED","[chars]","EFMD fc2 operation failed","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"PORT-SECURITY","3","EFMD_INIT_FAILED","[chars]","EFMD init failed","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"PORT-SECURITY","3","EFMD_MERGE_UNKNOWN_FORMAT","[chars]","Received a corrupted EFMD Request Packet","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"PORT-SECURITY","3","INIT_FAIL","[chars]","An error happened during PSM Initialization. [chars] indicates the reason for failure","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"PORT-SECURITY","3","LEARNT_BINDING_CONFLICT","[chars]","An already logged in device that is learnt during activation is in conflict with the PSM active binding configurations. [chars] indicates the WWN of the login entity, interface","Copy the active-db to config-db and reactivate. Not doing so could result in unexpected login rejects later on that interface."
"PORT-SECURITY","3","MTS_ERR","[chars]","An error occurred in processing of an MTS message. [chars] indicates the error that occurred","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"PORT-SECURITY","3","PSS_ERR","[chars]","An error occurred during an PSM PSS operation. [chars] indicates the PSS operation that caused the error","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"PORT-SECURITY","3","PSS_VER_FAIL","PSS file [chars] has version [dec].[dec].[dec], expected version [dec].[dec].[dec]","There was a mismatch in the PSS version. [chars] indicates the PSS service, [dec].[dec].[dec] its current version number and [dec].[dec].[dec] the expected version","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"PORT-SECURITY","4","ACTIVATION_FAIL","[chars]","Activation of bindings failed due to [chars]","Correct the error and reactivate it again"
"PORT-SECURITY","6","INFO","[chars]","An event happend that affects PSM. [chars] indicates the event","No action is required."
"PORT","2","IF_DOWN_ERROR_DISABLED","Interface [chars] is down (Error disabled) [chars] [chars]","The interface encountered an error while configuring it. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Collect more information about failed interface using command showportinternalallinterface[char]'.Inmostcases,youcanrecoverusingfollowingcommands'configter minal','interface[char]','shutdown','noshutdown'ontheinterfaceorremovingandre-insertingthefibreop ticcable'"
"PORT","2","IF_DOWN_LINK_FAILURE_CRIT","Interface [chars] is down (Link failure)","The physical link has gone down","Ensure that the cable is connected and the remote end is not shut down"
"PORT","3","IF_SFP_ALARM","Interface [chars], [chars] [chars] [chars]","There was an alarm on the transceiver module. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Please do show interface transceiver details to obtain more information"
"PORT","3","IF_TRANSCEIVER_READ_ERROR","Transceiver read error for interface [chars] [chars] [chars]","Transceiver eeprom read failed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Remove and insert the SFP back again. If the problem persists check if the transceiver is supported using the command: show interface transceiver. Please contact customer support to resolve the condition"
"PORT","3","IF_UNSUPPORTED_TRANSCEIVER","Transceiver for interface [chars] is not supported","Transceiver is not from an authorized vendor","This command will determine the transceiver being used: show interface transceiver. Please contact customer support for a list of authorized transceiver vendors"
"PORT","4","IF_NON_QUALIFIED_TRANSCEIVER","Non-qualified transceiver on interface [chars] was detected","The transceiver for the interface specified has not been qualified on this platform for this software release","Replace the module with a supported transceiver. Contact Cisco TAC to get platform transceiver qualification details"
"PORT","4","IF_SFP_CLK_RATE_ERROR","SFP clock rate error for interface [chars] [chars] [chars]","SFP clock rate mismatch/failed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Remove the SFP and insert a new one with a different frequency type. If the problem persists check if the transceiver is supported using the command: show interface transceiver. Please contact customer support to resolve the condition"
"PORT","4","IF_SFP_WARNING","Interface [chars], [chars] [chars] [chars]","There was an warning on the transceiver module. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Please do show interface transceiver details to obtain more information"
"PORT","4","IF_TRUSTSEC_VIOLATION","Interface [chars] encountered port security violation [chars] [chars]","The port has detected port security violation. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Check port security configs on interface"
"PORT","5","EC_DISABLED_AS_LICENSE_NOT_PRESENT","Extended credit feature has been disabled as Enterprise Package license could not be checked out","The Enterprise Package license is not available, so the extened credit feature has been disabled even though it was present in startup config","Install the Enterprise Package license and re-enable the extended credit feature"
"PORT","5","IF_BRINGUP_ALLOWED_FCOT_CHECKSUM_ERR","Interface [chars] is allowed to come up even with SFP checksum error [chars] [chars]","SFP checksum on this interface failed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Try to replace the SFP on this interface"
"PORT","5","IF_BRINGUP_FAILED_ALL_ZERO_PEER_WWN_RCVD","Interface [chars], is not allowed to come up (received as all zeros wwn from peer [chars] [chars]","Check peer interface configuration. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","No action is required."
"PORT","5","IF_BRINGUP_NOT_ALLOWED_PORT_CONFIG_FAILURE","Interface [chars] is not allowed to be operational due to port config failure for reason: [chars] ([hex]) [chars] [chars]","Check interface configuration. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Try to change the configuration on the interface with the current available hardware capability"
"PORT","5","IF_DOWN_ADMIN_DOWN","Interface [chars] is down (Administratively down) [chars] [chars]","Interface has been configured to be administratively down. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Perform the following commands to bring up the interface: configterminal','interface[char]','noshutdown''"
"PORT","5","IF_DOWN_BIT_ERR_RT_THRES_EXCEEDED","Interface [chars] is down (Error disabled - bit error rate too high) [chars] [chars]","The port has detected too high bit error rate in frames received from attached device. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Check the attached device; replace it if needed"
"PORT","5","IF_DOWN_BUNDLE_MISCFG","Interface [chars] is down (Isolation due to channel mis-configuration on local or remote switch) [chars] [chars]","One port across a link is part of a PortChannel while the other is not. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","While adding or deleting a member port from a PortChannel, both ports across the link should be added/deleted. No operation should be performed on either ports until they are both added/deleted."
"PORT","5","IF_DOWN_CFG_CHANGE","Interface [chars] is down(Config change) [chars] [chars]","FCIP interface temporarily down due to reconfiguration. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","No action is required."
"PORT","5","IF_DOWN_CHANNEL_ADMIN_DOWN","Interface [chars] is down (Channel admin down) [chars] [chars]","This interface belongs to a PortChannel and the PortChannel is configured to be administratively down. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Perform the following commands on the PortChannel interface to which it belongs to bring the interface up: configterminal','interface[char]','shutdown','noshutdown''"
"PORT","5","IF_DOWN_CHANNEL_MEMBERSHIP_UPDATE_IN_PROGRESS","Interface [chars] is down (Channel membership update in progress) [chars] [chars]","The interface belongs to a PortChannel and a configuration is being attempted on the interface while there is a configuration in progress on the PortChannel. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Retry the configuration again"
"PORT","5","IF_DOWN_DENIED_DUE_TO_PORT_BINDING","Interface [chars] is down(Suspended due to port binding) [chars] [chars]","The F port is suspended due to being denied by port binding. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Please check the port binding database to allow the host port to log in."
"PORT","5","IF_DOWN_DOMAIN_ADDR_ASSIGN_FAILURE_ISOLATION","Interface [chars] is down (Isolation due to domain id assignment failure) [chars] [chars]","Isolated due to a failure while assigning a domain. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","No action is required."
"PORT","5","IF_DOWN_DOMAIN_ID_MISMATCH_ISOLATION","Interface [chars] is isolated (configured fcdomain ID is different from runtime config) [chars] [chars]","The runtime fcdomain ID does not equal the static configured fcdomain ID. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Ensure that the fcdomain ID configuration matches the runtime config."
"PORT","5","IF_DOWN_DOMAIN_INVALID_RCF_RECEIVED","Interface [chars] is down (Isolation due to invalid fabric reconfiguration) [chars] [chars]","Invalid RCF received. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","No action is required."
"PORT","5","IF_DOWN_DOMAIN_MANAGER_DISABLED","Interface [chars] is down (Isolation due to domain manager disabled) [chars] [chars]","Isolated due to domain manager being disabled. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","No action is required."
"PORT","5","IF_DOWN_DOMAIN_MAX_RETRANSMISSION_FAILURE","Interface [chars] is down (Isolation due to domain manager other side not responding) [chars] [chars]","Remote end domain manager not responding. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","No action is required."
"PORT","5","IF_DOWN_DOMAIN_NOT_ALLOWED_ISOLATION","Interface [chars] is isolated (domain not allowed) [chars] [chars]","There arentenoughalloweddomainstomergetheVSANsacrossthelink.[optionallyiftheportbelongstoport-ch annel,theport-channelnumbertowhichtheportbelongswillbedisplayedandifinterfacedescriptioniscon figured,theinterfacedescriptionisdisplayed]'","Ensure that all assigned domain idsareintheconfiguredalloweddomainsonbothsidesofthelink.'"
"PORT","5","IF_DOWN_DOMAIN_OTHER_SIDE_EPORT_ISOLATED","Interface [chars] is down (Isolation due to domain other side eport isolated) [chars] [chars]","Isolating this interface due to the remote end being isolated. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","No action is required."
"PORT","5","IF_DOWN_DOMAIN_OVERLAP_ISOLATION","Interface [chars] is down (Isolation due to domain overlap) [chars] [chars]","Isolated due to domain overlap. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","No action is required."
"PORT","5","IF_DOWN_DPVM_VSAN_NOT_FOUND","Interface [chars] is down (dynamic vsan not present) [chars] [chars]","The specified dynamic vsan is not configured on this switch. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Configure the dynamic vsan."
"PORT","5","IF_DOWN_DPVM_VSAN_SUSPENDED","Interface [chars] is down (dynamic vsan in suspended state) [chars] [chars]","The specified dynamic vsan is in suspended state. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Un-suspend the dynamic vsan."
"PORT","5","IF_DOWN_ELP_FAILURE_ISOLATION_CLASSF_PARAM_ERR","Interface [chars] is down (Isolation due to ELP failure: class F param error) [chars] [chars]","ELP failed on the interface due to class F param error. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Configure the attached switchport correctly and try again"
"PORT","5","IF_DOWN_ELP_FAILURE_ISOLATION_CLASSN_PARAM_ERR","Interface [chars] is down (Isolation due to ELP failure: class N param error) [chars] [chars]","ELP failed on the interface due to class N param error. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Configure the attached switchport correctly and try again"
"PORT","5","IF_DOWN_ELP_FAILURE_ISOLATION_INVALID_PAYLOAD_SIZE","Interface [chars] is down (Isolation due to ELP failure: invalid payload size)","ELP failed on the interface due to invalid payload size","Configure the attached switchport correctly and try again"
"PORT","5","IF_DOWN_ELP_FAILURE_ISOLATION_INVALID_PORT_NAME","Interface [chars] is down (Isolation due to ELP failure: invalid port name) [chars] [chars]","ELP failed on the interface due to invalid port name. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Configure the attached switchport correctly and try again"
"PORT","5","IF_DOWN_ELP_FAILURE_ISOLATION_INVALID_SWITCH_NAME","Interface [chars] is down (Isolation due to ELP failure: invalid switch name) [chars] [chars]","ELP failed on the interface due to invalid switch name. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Configure the attached switchport correctly and try again"
"PORT","5","IF_DOWN_ELP_FAILURE_ISOLATION_INVALID_TX_BBCREDIT","Interface [chars] is down (Isolation due to ELP failure: loopback detected) [chars] [chars]","ELP failed on the interface due to loopback connection detected. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Connect to a port on another switch and try again"
"PORT","5","IF_DOWN_ELP_FAILURE_ISOLATION_LOOPBACK_DETECTED","Interface [chars] is down (Isolation due to ELP failure: invalid transmit B2B credit) [chars] [chars]","ELP failed on the interface due to invalid transmit B2B credit. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Configure the attached switchport correctly and try again"
"PORT","5","IF_DOWN_ELP_FAILURE_ISOLATION_RATOV_EDTOV_MISMATCH","Interface [chars] is down (Isolation due to ELP failure: R_A_TOV or E_D_TOV mismatch) [chars] [chars]","ELP failed on the interface due to R_A_TOV or E_D_TOV mismatch. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Configure R_A_TOV and E_D_TOV values correctly and try again"
"PORT","5","IF_DOWN_ELP_FAILURE_ISOLATION_REVISION_MISMATCH","Interface [chars] is down (Isolation due to ELP failure: revision mismatch) [chars] [chars]","ELP failed on the interface due to revision mismatch. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Configure the attached switchport correctly and try again"
"PORT","5","IF_DOWN_ELP_FAILURE_ISOLATION_UNKNOWN_FLOW_CTL_CODE","Interface [chars] is down (Isolation due to ELP failure: invalid flow control code) [chars] [chars]","ELP failed on the interface due to invalid flow control code. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Configure the attached switchport correctly and try again"
"PORT","5","IF_DOWN_ELP_FAILURE_ISOLATION_UNKNOWN_FLOW_CTL_PARAM","Interface [chars] is down (Isolation due to ELP failure: invalid flow control param) [chars] [chars]","ELP failed on the interface due to invalid flow control param. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Configure the attached switchport correctly and try again"
"PORT","5","IF_DOWN_ELP_FAILURE_ISOLATION","Interface [chars] is down (Isolation due to ELP failure) [chars] [chars]","ELP failed on the interface. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Check the output of showportinternalinfo'inthe'ELPfailurereason'field'"
"PORT","5","IF_DOWN_EPP_FAILURE","Interface [chars] is down (Error Disabled - EPP Failure) [chars] [chars]","Trunk protocol failed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","showportinternalevent-historymsgs'willindicatethetrunkprotocolexchangestodeterminewhyitfailed'"
"PORT","5","IF_DOWN_ESC_FAILURE_ISOLATION","Interface [chars] is down (Isolation due to ESC failure) [chars] [chars]","ESC failed on the interface. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Check the output of showportinternalevent-history'todeterminetheESCprotocolexchangestodeterminehowitfailed'"
"PORT","5","IF_DOWN_ETH_IF_DOWN","Interface [chars] is down(Tunnel port src interface down) [chars] [chars]","Ethernet link to which the FCIP interface is bound is down. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Ensure that the ethernet cable is connected, the interface is administratively enabled"
"PORT","5","IF_DOWN_ETH_LINK_DOWN","Interface [chars] is down(Tunnel port src interface link down) [chars] [chars]","Ethernet link to which the FCIP interface is bound is down. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Ensure that the ethernet cable is connected and the remote end is also active"
"PORT","5","IF_DOWN_FABRIC_BIND_FAILURE","Interface [chars] is down(Isolation due to fabric bind failure) [chars] [chars]","Fabric binding failed on this port. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Please check the fabric binding database to ensure that the remote port is allowed to connect to this port"
"PORT","5","IF_DOWN_FCOT_NOT_PRESENT","Interface [chars] is down (FCOT not present) [chars] [chars]","The FCOT has been removed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Insert an FCOT"
"PORT","5","IF_DOWN_FCOT_REMOVED","Interface [chars] is down (FCOT has been removed) [chars] [chars]","The FCOT has been removed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Insert an FCOT"
"PORT","5","IF_DOWN_FCOT_VENDOR_NOT_SUPPORTED","Interface [chars] is down (Error disabled - FCOT vendor not supported) [chars] [chars]","FCOT inserted is not a supported one. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Please contact customer support for a list of authorized transceiver vendors"
"PORT","5","IF_DOWN_FCSP_AUTHENT_FAILURE","Interface [chars] is down (FC-SP authentication failure) [chars] [chars]","The port failed FC-SP authentication with its peer. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Please check the FC-SP configuration."
"PORT","5","IF_DOWN_FICON_BEING_ENABLED","Interface [chars] is down(FICON being enabled) [chars] [chars]","FICON is being enabled on the port. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Please wait. This might take a while"
"PORT","5","IF_DOWN_FICON_NOT_ENABLED","Interface [chars] is down(Error disabled - FICON not enabled) [chars] [chars]","FICON not enabled on port. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Please enable FICON on port"
"PORT","5","IF_DOWN_FICON_VSAN_DOWN","Interface [chars] is down(FICON vsan down) [chars] [chars]","FICON is being enabled on the port VSAN of this port. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","This is an intermediary state, whereby the port VSAN of the port is being enabled to be a FICON VSAN."
"PORT","5","IF_DOWN_HW_FAILURE","Interface [chars] is down (Hardware Failure) [chars] [chars]","The moduleshardwarehasfailed.[optionallyiftheportbelongstoport-channel,theport-channelnumbertowhi chtheportbelongswillbedisplayedandifinterfacedescriptionisconfigured,theinterfacedescriptionisdis played]'","Collect more information about failed module using command showmoduleinternalallmodule''"
"PORT","5","IF_DOWN_INACTIVE","Interface [chars] is down (Inactive) [chars] [chars]","The port VSAN has been suspended or deleted. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Assign a new active port VSAN to the interface"
"PORT","5","IF_DOWN_INCOMPATIBLE_ADMIN_MODE","Interface [chars] is down (Error disabled - Incompatible admin port mode) [chars] [chars]","The configured mode is not supported on this interface. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Perform a showportinternalinfo'todeterminethelistofmodessupportedonthisinterface'"
"PORT","5","IF_DOWN_INCOMPATIBLE_ADMIN_RXBBCREDIT","Interface [chars] is down (Error disabled - Incompatible admin port rxbbcredit) [chars] [chars]","The configured receive B2B credit size is not supported. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Get the allowed receive B2B credit size from showportinternalinfo''"
"PORT","5","IF_DOWN_INCOMPATIBLE_ADMIN_RXBUFSIZE","Interface [chars] is down (Error disabled - Incompatible admin port rxbufsize) [chars] [chars]","The configured receive buffer size is not supported. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Get the allowed receive buffer size from showportinternalinfo''"
"PORT","5","IF_DOWN_INCOMPATIBLE_ADMIN_SPEED","Interface [chars] is down (Error disabled - Incompatible admin port speed) [chars] [chars]","The configured speed is not supported on this interface. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Perform a showportinternalinfo'todeterminetherangeofspeedsupportedonthisinterface'"
"PORT","5","IF_DOWN_INITIALIZING","Interface [chars] is down (Initializing) [chars] [chars]","The interface is in the process of coming up. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","If the interface is stuck in this state for a while, check the output of showportinternalevent-history'todeterminewhatitiswaitingfor'"
"PORT","5","IF_DOWN_INTERFACE_REMOVED","Interface [chars] is down (Interface removed) [chars] [chars]","Interface removed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","No action is required."
"PORT","5","IF_DOWN_INVALID_ATTACHMENT","Interface [chars] is down(Invalid attachment) [chars] [chars]","The peer port does not have the compatible security attributes. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Please ensure that the peer port has compatible security attributes as the local port."
"PORT","5","IF_DOWN_INVALID_CONFIG","Interface [chars] is down(Error disabled - Possible PortChannel misconfiguration) [chars] [chars]","The local and peer port have a PortChannel membership misconfiguration. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Ensure that both the local and peer ports are either both members of the same PortChannel or are not both part of PortChannel"
"PORT","5","IF_DOWN_INVALID_FABRIC_BINDING","Interface [chars] is down(Invalid fabric binding exchange) [chars] [chars]","Fabric binding failed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Please check fabric binding database"
"PORT","5","IF_DOWN_LINK_FAILURE","Interface [chars] is down (Link failure [chars]) [chars] [chars]","The physical link has gone down. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Ensure that the cable is connected and the remote end is not shut down"
"PORT","5","IF_DOWN_LOCALLY_DISRUPTIVE_RECONFIGURATION","Interface [chars] is down (fcdomain applied a locally disruptive reconfiguration) [chars] [chars]","Fcdomain applied a locally disruptive reconfiguration (local domain became invalid. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","No action is required."
"PORT","5","IF_DOWN_LOOPBACK_DIAG_FAILURE","Interface [chars] is down (Diag failure) [chars] [chars]","Diag failed on the interface. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Collect more information about failed interface using command attachmodule'toconnecttomodule'"
"PORT","5","IF_DOWN_LOOPBACK_ISOLATION","Interface [chars] is down (Isolation due to port loopback to same switch) [chars] [chars]","The interface is looped back to another interface on the same switch. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Check the connectivity of this interface and ensure that it is connected to another switch"
"PORT","5","IF_DOWN_MODULE_REMOVED","Interface [chars] is down (module removed) [chars] [chars]","Interface is down because the module was removed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","No action is required."
"PORT","5","IF_DOWN_NONE","Interface [chars] is down (None) [chars] [chars]","There is no apparent reason the interface is down. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Collect more information about port using command showportinternalallinterface[char]'todeterminewhyitwentdown'"
"PORT","5","IF_DOWN_NON_PARTICIPATING","Interface [chars] is down (Non participating) [chars] [chars]","The loop port has been put into non participating mode. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","No action is required."
"PORT","5","IF_DOWN_NOS_RCVD","Interface [chars] is down (NOS received) [chars] [chars]","The physical link has gone down. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Ensure that the cable is connected and the remote end is not shut down"
"PORT","5","IF_DOWN_NO_TRUNK_OPER_VSANS_ISOLATION","Interface [chars] is down(Isolation due to no common vsans with peer on trunk) [chars] [chars]","The trunk port is isolated as there are no common VSANs to be brought up with the peer port. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Please check that there are common VSANs configured and allowed to come up between the ports."
"PORT","5","IF_DOWN_OFFLINE","Interface [chars] is down (Offline) [chars] [chars]","The interface has been placed into the offline state. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","No action is required."
"PORT","5","IF_DOWN_OHMS_EXTERNAL_LB_TEST","Interface [chars] is down(Loopback test) [chars] [chars]","Loopback tests. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Please wait. This might take a while"
"PORT","5","IF_DOWN_OLS_RCVD","Interface [chars] is down (OLS received) [chars] [chars]","The physical link has gone down. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Ensure that the cable is connected and the remote end is not shut down"
"PORT","5","IF_DOWN_PARENT_ADMIN_DOWN","Interface [chars] is down (Parent interface down) [chars] [chars]","Parent interface is down. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","No action is required."
"PORT","5","IF_DOWN_PEER_CLOSE","Interface [chars] is down(TCP conn. closed by peer) [chars] [chars]","The FCIP peer connected to this interface closed the TCP connection. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","This command will provide the peer IP address of this FCIP interface: show interface. Check to see why the peer closed the TCP connection"
"PORT","5","IF_DOWN_PEER_RESET","Interface [chars] is down(TCP conn. reset by peer) [chars] [chars]","TCP connection to the FCIP peer got reset. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Check to see why the peer reset the TCP connection"
"PORT","5","IF_DOWN_PORT_ACT_LICENSE_NOT_AVAILABLE","Interface [chars] is not allowed to come up (port activation license not available [chars] [chars]","Assign a port activation license to this port or install additional port activation licenses as needed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","No action is required."
"PORT","5","IF_DOWN_PORT_BIND_FAILURE","Interface [chars] is down(Isolation due to port bind failure) [chars] [chars]","Port binding failed on this port. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Please check the port binding database to ensure that the remote port is allowed to connect to this port"
"PORT","5","IF_DOWN_PORT_BLOCKED","Interface [chars] is down(Port blocked due to FICON) [chars] [chars]","The port has been blocked by FICON configuration. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Please unblock the port in FICON configuration."
"PORT","5","IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN","Interface [chars] is down (No operational members) [chars] [chars]","This is a PortChannel interface and all its members are operationally down. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Enable at least one of the PortChannelsmembers'"
"PORT","5","IF_DOWN_PORT_VSAN_MISMATCH_ISOLATION","Interface [chars] is down (Isolation due to port VSAN mismatch) [chars] [chars]","Isolated due to a mismatch in the configured port VSAN of the local and remote ends. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Configure the port VSAN of the local and remote interfaces to be the same and perform a shutdown'anda'noshutdown''"
"PORT","5","IF_DOWN_RCF_IN_PROGRESS","Interface [chars] is down (RCF in progress) [chars] [chars]","There is an RCF in progress. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","No action is required."
"PORT","5","IF_DOWN_SOFTWARE_FAILURE","Interface [chars] is down (Port software failure) [chars] [chars]","The software servicing the data path on the port has failed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","No action is required."
"PORT","5","IF_DOWN_SRC_MOD_NOT_ONLINE","Interface [chars] is down(Tunnel source module not online) [chars] [chars]","Module that has the tunnel source port of this FCIP interface is not fully online. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","The module that has the tunnel src port is coming online. Please use show mod to find module status"
"PORT","5","IF_DOWN_SRC_PORT_NOT_BOUND","Interface [chars] is down (Tunnel port src interface unbound) [chars] [chars]","Tunnel port source interface unbound. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","No action is required."
"PORT","5","IF_DOWN_SRC_PORT_REMOVED","Interface [chars] is down(Tunnel src port removed) [chars] [chars]","Tunnel source port of this FCIP interface has been removed. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","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"
"PORT","5","IF_DOWN_SUSPENDED_BY_MODE","Interface [chars] is down (Suspended due to incompatible mode) [chars] [chars]","This interface belongs to a PortChannel and operational mode of the interface is different from that of the PortChannel. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Change the mode and the trunking mode of the PortChannel from auto'andchecktoensurethattheremoteendoftheinterfacealsobelongstothesamePortChannel'"
"PORT","5","IF_DOWN_SUSPENDED_BY_SPEED","Interface [chars] is down (Suspended due to incompatible speed) [chars] [chars]","This interface belongs to a PortChannel and operational speedode of the interface is different from that of the PortChannel. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Change the speed of the PortChannel from auto'andchecktoensurethattheremoteendoftheinterfacealsobelongstothesamePortChannel'"
"PORT","5","IF_DOWN_SUSPENDED_BY_WWN","Interface [chars] is down (Suspended due to incompatible remote switch WWN) [chars] [chars]","This interface belongs to a PortChannel and remote switch WWN of the interface is different from that of the PortChannel. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Ensure that this interface is connected to the same remote switch as all the other interfaces in the PortChannel"
"PORT","5","IF_DOWN_SUSPENDED","Interface [chars] is down (Suspended) [chars] [chars]","This interface belongs to a PortChannel and has been suspended to to an error while bringing it up. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","In most cases, you can recover using following commands configterminal','interface[char]','shutdown','noshutdown'ontheinterface.Ifthishappensagainobtaino utputof'showportinternalallinterface[char]'ontheinterface'"
"PORT","5","IF_DOWN_TCP_KEEP_ALIVE_EXPIRED","Interface [chars] is down(TCP conn. closed - Keep alive expired) [chars] [chars]","TCP session to the FCIP peer got closed due to loss of TCP keep alive. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","This may be due to loss of IP connectivity. The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Please do a trace route to check the connectivity to the peer using command:traceroute ipaddr"
"PORT","5","IF_DOWN_TCP_MAX_RETRANSMIT","Interface [chars] is down(TCP conn. closed - retransmit failure) [chars] [chars]","Interface is down due to maximum retransmission failure. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","This may be due to loss of IP connectivity. The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Please do a trace route to check the connectivity to the peer using command:traceroute ipaddr"
"PORT","5","IF_DOWN_TCP_PERSIST_TIMER_EXPIRED","Interface [chars] is down(TCP conn. closed - Persist timer expired) [chars] [chars]","TCP session to the FCIP peer closed because TCP persist timer expired. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","This may be due to loss of IP connectivity. The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Please do a trace route to check the connectivity to the peer using command:traceroute ipaddr"
"PORT","5","IF_DOWN_TOO_MANY_INTR","Interface [chars] is down (Error disabled - too many interrupts) [chars] [chars]","The port has received too many interrupts in the hardware. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Check the attached device; replace it if needed"
"PORT","5","IF_DOWN_TOO_MANY_INVALID_FLOGIS","Interface [chars] is down(Suspended due to too many invalid flogis [chars] [chars]","The port is suspended due to receiving a large number of invalid FLOGIs.[optionallyiftheportbelongstoport-channel,theport-channelnumbertowhichtheportbelongs willbedisplayedandifinterfacedescriptionisconfigured,theinterfacedescriptionisdisplayed]'","Please check the HBA and perform a shut, followed by no shut on the port."
"PORT","5","IF_DOWN_UPGRADE_IN_PROGRESS","Interface [chars] is down (Linecard upgrade in progress) [chars] [chars]","Upgrade of the linecard software is in progress. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","No action is required."
"PORT","5","IF_DOWN_VIRTUAL_IVR_DOMAIN_OVERLAP_ISOLATION","Interface [chars] is down (Isolation due to virtual IVR domain overlap) [chars] [chars]","Isolated due to virtual IVR domain overlap. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","No action is required."
"PORT","5","IF_DOWN_VSAN_MISMATCH_ISOLATION","Interface [chars] is down (Isolation due to vsan mismatch) [chars] [chars]","This is a trunking interface and the VSANs configured do not match with the VSANs configured on the remote end. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Check the VSANs configured on the local end with the remote end"
"PORT","5","IF_DOWN_ZONE_MERGE_FAILURE_ISOLATION","Interface [chars] is down (Isolation due to zone merge failure) [chars] [chars]","Isolated due to a failure during zone merge. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","No action is required."
"PORT","5","IF_DOWN_ZONE_REMOTE_NO_RESP_ISOLATION","Interface [chars] is down (Isolation due to remote zone server not responding) [chars] [chars]","Isolated due to remote zone server not responding. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","No action is required."
"PORT","5","IF_PORT_GUARD_DOWN","Interface [chars] is down ([chars]) [chars] [chars]","The interface is down due to port guard configuration. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","Perform a shut followed by no shut to bring up the interface"
"PORT","5","IF_PORT_QUIESCE_FAILED","Interface [chars] port quiesce failed due to failure reason: [chars] ([hex])","There may be few packet drops due to this failure","No action is required."
"PORT","5","IF_PSS_DUPLICATE_KEY","Duplicate key found for Interface [chars]","Duplicate pss key detected","No action is required."
"PORT","5","IF_TRUNK_DOWN","Interface [chars], vsan [chars] is down ([chars]) [chars] [chars]","Interface [chars] is trunking, VSAN [chars] is down with reason in (). [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","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"
"PORT","5","IF_TRUNK_UP","Interface [chars], vsan [chars] is up [chars] [chars]","Interface [chars] is trunking, VSAN [chars] is up. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","No action is required."
"PORT","5","IF_UP","Interface [chars] is up [chars] [chars] [chars]","Interface is up in mode specified, if applicable. [optionally if the port belongs to port-channel, the port-channel number to which the port belongs will be displayed and if interface description is configured, the interface description is displayed]","No action is required."
"PORT","5","MODULE_BRINGUP_NOT_ALLOWED","Not allowing module [dec] to come up for reason: [chars] ([hex])","Module is not allowed to be operational due to the current system state","Use command 'show module <x"
"PORT","5","MODULE_INDEX_RESTORE_ERROR","Error in restoring indices for module [dec]: reason [chars] ([hex])","Restore of module index may fail due to overlap of indices","No action is required."
"PORT","5","MODULE_UNLIMITED_OSM_SEQ_FAILED","Enable/Disable of unlimited oversubscription failed for module [dec]","Interfaces of the module may be in indeterminate state","Reload the module"
"PREFPATH","1","LC_CFG_FAILURE","configuring module [dec] failed [[chars]]","Module configuration failed","No action is required."
"PREFPATH","1","MCAST_SEND_FAILURE","failed to send multicast [chars]: [chars]","Failed to send a multicast message to all modules, usually because some module went down","No action is required."
"PREFPATH","2","INITFAIL","Preferred Path Initialization failed: [chars]","Preferred Path initialization failed. [chars] explains the reason for the failure.","No action is required."
"PREFPATH","2","IPC_PROCESSING_ERR","Error in processing IPC message : Opcode = [dec], Error code = [hex]","Preferred Path component encountered an error in processing an MTS message. The error and message are specified in the error message","No action is required."
"PREFPATH","2","PREFPATH_INIT","Preferred Path initialization of [chars] [chars]","Preferred Path initialization failed","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"PREFPATH","3","ACL_PROG_FAILURE","SLOT [dec]: Failed to [chars] ACL for route - source fcid [chars] mask [chars] dest fcid [chars] mask [chars] selected interface [chars] (ACL return code=[hex], [chars])","The Preferred Path has failed to program or erase Preferred Path related ACL. The error code returned by ACL module is [int.].","No action is required."
"PREFPATH","3","DBERROR","[chars]","Preferred Path encountered a database error. [chars] specifies the context where the failure occurred.","No action is required."
"PREFPATH","3","FAILURE_RESPONSE","[chars] [dec]","Preferred Path failed to get response [chars][int.] specify the context where the failure occurred.","No action is required."
"PREFPATH","3","GENERAL_ERROR","General Error: [chars]","General error","No action is required."
"PREFPATH","3","MTSERROR","[chars]","Preferred Path encountered an MTS error. [chars] specifies the context where the error occurred.","No action is required."
"PREFPATH","3","PREFPATH_ACTIVE_FAILURE","Failed to [chars] route - source fcid [chars] mask [chars] dest fcid [chars] mask [chars] selected interface [chars] (reason: [chars])","The Preferred Path has failed to activate route. The reason is [str.].","No action is required."
"PREFPATH","3","PSSERROR","[chars]","Preferred Path encountered a PSS error. [chars] specifies the context where the failure occurred.","No action is required."
"PREFPATH","3","RIB_ERR","Error in RIB : [chars]","Failed to interact with RIB for static route update, error description in [chars].","No action is required."
"PREFPATH","3","TIMEOUT_ERROR","[chars] [dec]","Preferred Path encountered a timeout [chars][int.] specify the context where the failure occurred.","No action is required."
"PREFPATH","4","UNEXPECTED_RESPONSE","unexpected response [chars] from [chars]","Received an unexpected response and discarded","No action is required."
"PREFPATH","6","ACL_PROG_SUCCESS","SLOT [dec]: Successfully [chars] route - source fcid [chars] mask [chars] dest fcid [chars] mask [chars] selected interface [chars]","The Preferred Path has successfully programmed or erased Preferred Path related ACL.","No action is required."
"PREFPATH","6","SERVICE_UP","Initialized [chars]","Preferred Path Service Up","No action is required."
"PREFPATH","6","STATE_CREATED","Internal state created [chars]","Preferred Path has created its internal state stateless/stateful [chars].","No action is required."
"PRIVATE_VLAN","2","PVLAN_ASSOC_DOWN_FAILED","Failed to bring down the association between [dec] & [dec]","Association bringdown failed","No action is required."
"PRIVATE_VLAN","2","PVLAN_ASSOC_UP_FAILED","Failed to bring up the association between [dec] & [dec]","Association bringup failed","No action is required."
"PRIVATE_VLAN","2","PVLAN_ELTM_MTS_SEND_FAILED","MTS send failed while communicating with ELTM.","ELTM MTS send failed","No action is required."
"PRIVATE_VLAN","2","PVLAN_ELTM_TIMED_OUT","ELTM timed out while configuring hardware.","ELTM timed out","No action is required."
"PRIVATE_VLAN","2","PVLAN_ETHPM_TIMED_OUT","ETHPM timed out while configuring/unconfiguring hardware","ETHPM timed out","No action is required."
"PRIVATE_VLAN","2","PVLAN_HW_ERROR","Error [hex] occurred for ifindex [hex] while programming hardware: [chars]","Hardware Configuration Error","No action is required."
"PRIVATE_VLAN","2","PVLAN_PIXM_MTS_SEND_FAILED","MTS send failed while communicating with PIXM","PIXM MTS send failed","No action is required."
"PRIVATE_VLAN","2","PVLAN_PIXM_TIMED_OUT","PIXM timed out while configuring hardware.","PIXM timed out","No action is required."
"PRIVATE_VLAN","3","PVLAN_ASSOC_SDB_UPDATE_FAILED","Failed to update SDB while [chars] association for vlan [dec]","SDB Update failed","No action is required."
"PRIVATE_VLAN","3","PVLAN_IN_USE","PVLAN [dec] in use by interface [chars], please do 'no switchport access vlan' or 'no switchport private-vlan host-association'","PVLAN in use","No action is required."
"PRIVATE_VLAN","3","PVLAN_VLANMGR_FAILURE","Cannot restore association operational state. Failed to communicate with VLAN manager","Restoring association operational status failed","No action is required."
"PRIVATE_VLAN","5","PVLAN_DISABLED","PVLAN Disabled","PVLAN Service Disabled","No action is required."
"PRIVATE_VLAN","5","PVLAN_DISABLE_FAILED","Disabling of private-vlan failed. Either shutdown these ports or remove them from private-vlan mode: [chars]","Disabling of private-vlan failed","No action is required."
"PRIVATE_VLAN","5","PVLAN_ENABLED","PVLAN Enabled","PVLAN Service Enabled","No action is required."
"PROC_MGR-SLOT#","2","ERR_MSG","[chars]","Process manager error.","No action is required."
"PROC_MGR-SLOT#","2","MESG","[chars]","Process manager information.","Process manager information."
"PROC_MGR-SLOT#","2","PROC_MGR_APP_CRIT_ERROR","ERROR: Critical error determined for app ([chars]) status=[dec] signal=[dec]","Application caused critical error.","Restart the linecard."
"PROC_MGR-SLOT#","2","PROC_MGR_APP_EXITED","ERROR: Application ([chars]) exited with status=[dec] signal=[dec]","Application exited.","Check the application."
"PROC_MGR-SLOT#","2","PROC_MGR_COMP_CATASTROPHIC_ERROR","ERROR: Component ([chars]) caused critical error and linecard will be rebooted","Component caused critical error.","Restart the linecard."
"PROC_MGR-SLOT#","2","PROC_MGR_COMP_CRIT_ERROR","ERROR: Critical error determined for component ([chars]) errno=[dec]","Critical error for component.","Restart the linecard."
"PROC_MGR-SLOT#","2","PROC_MGR_COMP_DEP_FAIL","ERROR: Dependency failure - Component ([chars]) depends on ([chars])","Component dependency failure.","Check whether the component exists."
"PROC_MGR-SLOT#","2","PROC_MGR_COMP_NOT_INSTALLED","ERROR: Component ([chars]) could not be installed errno=[dec]","Component not installed.","Check whether the component exists."
"PROC_MGR-SLOT#","2","PROC_MGR_COMP_TIMEOUT","ERROR: Component ([chars]) did not exit and time out occurred","Component initialization timed out.","Check the component."
"PROC_MGR-SLOT#","2","PROC_MGR_MTS_CORE_CLIENT_FAIL","ERROR: MTS message to core_client FAILED errno=[dec]","Message to core client failed.","Restart the linecard."
"PROC_MGR-SLOT#","2","PROC_MGR_QUIT","Process manager quitting because: [chars]","Process manager quitting.","No action is required."
"PROC_MGR-SLOT#","2","PROC_MGR_RM_KLM_SCRIPT","Removed: KLM/Script [[chars]] in [dec] sec [dec] usec ...","Removed KLM/Script.","No action is required."
"PROC_MGR-SLOT#","2","PROC_MGR_STOP_PROC","Process [[chars]] exited in [dec] sec [dec] usec ...","Process stopped.","No action is required."
"PROC_MGR-SLOT#","2","PROC_MGR_TERM_TIME","* Termination took [dec] sec [dec] usec *","Process manager termination time.","No action is required."
"PROC_MGR-SLOT#","2","PROC_MGR_UT_PEEK_FAIL","ERROR: Unable to peek on utaker queue","Peek at utaker queue failed.","Restart the linecard."
"PROC_MGR-SLOT#","2","PROC_MGR_UT_SEM_ALLOC_FAIL","ERROR:Failed to allocate utaker semaphore: [dec]","Utaker semaphore allocation failed.","Restart the linecard."
"PROC_MGR-SLOT#","2","PROC_MGR_UT_SEM_GET_FAIL","ERROR:[chars] [dec]: Failed to get utaker semaphore: [dec]","Utaker semaphore get failed.","Restart the linecard."
"PROC_MGR-SLOT#","2","PROC_MGR_UT_SEM_GIVE_FAIL","ERROR:[chars] [dec]: Failed to give utaker semaphore: [dec]","Utaker semaphore give failed.","Restart the linecard."
"PROC_MGR-SLOT#","2","PROC_MGR_UT_SEM_TAKE_FAIL","ERROR:[chars] [dec]: Failed to take utaker semaphore: [dec]","Utaker semaphore take failed.","Restart the linecard."
"PROC_MGR-SLOT#","3","PROC_MGR_ERROR_MSG","[chars]","Process manager error message","No action is required."
"PROC_MGR-SLOT#","4","PROC_MGR_APP_NOT_RESP","ERROR: Process ([chars]) is not responding, it will be terminated","Application not sending heartbeat.","Check the application."
"PROC_MGR-SLOT#","6","PROC_MGR_INFO_MSG","[chars]","Process manager info message","No action is required."
"PROFILER","0","EMERGENCY_MSG","[chars]","Profiler Emergency Message","Please file the bug for Profiler Library Component throCDETS'"
"PROFILER","1","ALERT_MSG","[chars]","Profiler Alert Message","Profiler Internal Operation Alert"
"PROFILER","2","CRITICAL_MSG","[chars]","Profiler Critical Message","No action is required."
"PROFILER","3","ERROR_MSG","[chars]","Profiler Error Message","No action is required."
"PROFILER","4","WARN_MSG","[chars]","Profiler Warning Message","No action is required."
"PROFILER","5","NOTIF_MSG","[chars]","Profiler Notification Message","No action is required."
"PROFILER","6","INFO_MSG","[chars]","Profiler Informational Message","No action is required."
"PROFILER","7","DEBUG_MSG","[chars]","Profiler Debug Message","No action is required."
"PSS","0","PSS_NO_MORE_PAGES","[chars]: needs more working pages","Service needs more working page buffers","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"PSS","0","PSS_READ_DATA_FAILURE","[chars]: failed to read data to [chars] block [dec]: [chars]","PSS cannot read data","No action is required."
"PSS","0","PSS_SYNC_DATA_FAILURE","[chars]: failed to sync data to [chars]: [chars]","PSS cannot sync data due to filesystem or disk error","No action is required."
"PSS","0","PSS_SYNC_LOG_FAILURE","[chars]: failed to sync log: [chars]","PSS cannot sync log due to filesystem or disk error","No action is required."
"PSS","0","PSS_UNKNOWN_LOG","[chars]: unknown log type [hex] at offset [dec]","Unknown logging entry found","No action is required."
"PSS","0","PSS_WRITE_DATA_FAILURE","[chars]: failed to write data to [chars] block [dec]: [chars]","PSS cannot write data due to filesystem or disk error","No action is required."
"PSS","0","PSS_WRITE_FAILURE","[chars]: failed to write data: [chars]","PSS cannot write data due to filesystem or disk error","No action is required."
"PSS","0","PSS_WRITE_LOG_FAILURE","[chars]: failed to write log: [chars]","PSS cannot write log due to filesystem or disk error","No action is required."
"PSS","1","PSS_INVALID_MAGIC","[chars]: database [chars] has invalid magic number [hex]","PSS found a corrupted database with invalid magic number","No action is required."
"PSS","1","PSS_META_READ_ERROR","[chars]: cannot read meta page from [chars]: [chars]","PSS cannot read meta page of a database","No action is required."
"PSS","1","PSS_STAT_ERROR","[chars]: cannot stat [chars]: [chars]","PSS cannot do fstat on a database","No action is required."
"PSS","1","PSS_VERSION_MISMATCH","[chars]: found version mismatch in [chars]","PSS found a database whose format it cannot interpret due to version mismatch","The image upgrade was not done properly; write erase should cure it as a last step"
"PSS","2","PSS_INFRACONVERT","[chars]","Error in libinfraconvert during pss conversion","No action is required."
"PSS","2","PSS_INVALID_SIZE","[chars]: database [chars] ([chars]) has invalid size %ld (block size [dec])","PSS found a database with invalid size - probably due to a crash","No action is required."
"PSS","2","PSS_MISSING_FILE","[chars]: database [chars] missing [chars] file","PSS database is incomplete; probably due to a crash","No action is required."
"PSS","2","PSS_RECOVERY_FAILED","[chars]: failed to recover [chars]","PSS recovery failed","No action is required."
"PSS","4","PSS_CLEANUP","[chars]: cleaning up [chars]","PSS removed a leftover or corrupted file","No action is required."
"PSS","4","PSS_RECOVERY_ENDED","[chars]: recovered [chars] successfully","PSS recovery finished","No action is required."
"PSS","4","PSS_RECOVERY_STARTED","[chars]: recovering [chars]: [dec] valid transactional records","PSS started recovery of previous aborted transaction","No action is required."
"PSS","5","PSS_CONVERT_FORMAT","[chars]: converting pss format: [chars]","PSS format is being converted","No action is required."
"PSS","5","PSS_CONVERT_LAYOUT","[chars]: converting pss layout: [chars] (params [dec]/[dec]/[dec] -","PSS layout is being converted","No action is required."
"PSS","5","PSS_SHRINK","[chars]: shrinking pss: [chars]","PSS is being shrunk to remove free space","No action is required."
"PSS","5","SDB_CLOSED_AT_COMMIT","[chars]: sdb [chars] is closed: token [dec] is not committed","Publisher received SDB commit but sdb was already closed","No action is required."
"PTPLC","3","PTPLC_PORT_CFG_FAILED","Configuration failed on port [hex], [chars]: [hex], [chars]","PTP interface configuration error","No action is required."
"PTPLC","3","PTPLC_PTP_INTF_CONFIG_ERROR","Failed to configure PTP/PONG on port [dec]: [hex], [chars]","PTP interface configuration error","No action is required."
"PTP","5","PTP_DISABLED","PTP disabled","PTP Service Enabled","No action is required."
"PTP","5","PTP_DOMAIN_CHANGE","PTP domain changed to [dec]","PTP domain changed","No action is required."
"PTP","5","PTP_ENABLED","PTP enabled","PTP Service Enabled","No action is required."
"PTP","6","PTP_ANNOUNCE_INTERVAL_CHANGE","PTP announce interval for [hex] changed to [dec]","PTP announce interval for [chars] changed","No action is required."
"PTP","6","PTP_ANNOUNCE_TIMEOUT_CHANGE","PTP announce timeout interval for [hex] changed to [dec]","PTP announce timeout interval for [chars] changed","No action is required."
"PTP","6","PTP_DELAY_REQ_INTERVAL_CHANGE","PTP delay-req interval for [hex] changed to [dec]","PTP delay-req interval for [chars] changed","No action is required."
"PTP","6","PTP_PRIORITY1_CHANGE","PTP priority1 changed to [dec]","PTP priority1 changed","No action is required."
"PTP","6","PTP_PRIORITY2_CHANGE","PTP priority2 changed to [dec]","PTP priority2 changed","No action is required."
"PTP","6","PTP_SYNC_INTERVAL_CHANGE","PTP sync interval for [hex] changed to [dec]","PTP sync interval for [chars] changed","No action is required."
"PTP","6","PTP_VLAN_CHANGE","PTP vlan for [hex] changed to [dec]","PTP vlan for [chars] changed","No action is required."
"PULSE","0","EMERGENCY_MSG","[chars]","Pulse Emergency Message","Please file the bug for Pulse Library Component throCDETS'"
"PULSE","1","ALERT_MSG","[chars]","Pulse Alert Message","Pulse Internal Operation Alert"
"PULSE","2","CRITICAL_MSG","[chars]","Pulse Critical Message","No action is required."
"PULSE","3","ERROR_MSG","[chars]","Pulse Error Message","No action is required."
"PULSE","4","WARN_MSG","[chars]","Pulse Warning Message","No action is required."
"PULSE","5","NOTIF_MSG","[chars]","Pulse Notification Message","No action is required."
"PULSE","6","INFO_MSG","[chars]","Pulse Informational Message","No action is required."
"PULSE","7","DEBUG_MSG","[chars]","Pulse Debug MessageNo action is required.QD MessagesThis section contains the QD messages.QD-3Error Message    QD-3-QD_COSMAP_TMO: Cos map update for [chars] timed out Explanation    Cos map update timed out.","No action is required."
"QOS","2","EXITING","Exit reason: [chars]","The QOS Manager process has exited due to [char]. The process has probably been restarted automatically.","No action is required."
"QOS","2","GENERAL_ERROR","[chars]","The QOS Manager has encountered an critical error. The description of error is [str.].","No action is required."
"QOS","2","INITFAIL","QoS Manager Initialization failed: [chars]","QoS Manager initialization failed. [chars] explains the reason for the failure.","No action is required."
"QOS","2","MALLOC_ERROR","Size [dec] bytes","The QOS Manager could not allocate memory.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"QOS","2","PSS_ERROR","[chars]: PSS returned value=[dec]","The QOS Manager encountered error while operating on a persistent storage database.","No action is required."
"QOS","2","STDOUT_ROTATE_FAILURE","Failed to rotate stdout file: [chars]","The QOS Manager has failed to rotate its current stdout file with filename [str.]. The file size could grow beyond its maximum limit.","No action is required."
"QOS","3","ALLOCFAIL","Heap Memory allocation failed: [chars]","QoS Manager is out of dynamic memory. [chars] specifies the context where the failure occurred.","No action is required."
"QOS","3","DBERROR","[chars]","QoS Manager encountered a database error. [chars] specifies the context where the failure occurred.","No action is required."
"QOS","3","E_PORT_ACL_FAILURE","Failed to [chars] QOS ACL for interface [chars] (ACL return code=[hex])","The QOS Manager has failed to program or erase QoS related ACL when an E-Port came up or went down for interface [str.]. The error code returned by ACL module is [int.].","No action is required."
"QOS","3","FAILURE_RESPONSE","[chars] [hex]","QoS Manager failed to get response [chars][hex] specify the context where the failure occurred.","No action is required."
"QOS","3","GENERROR","[chars]","QoS Manager encountered a general error, one that does not fall in any of the above categories. [chars] describes the error and its context.","No action is required."
"QOS","3","LICERR","[chars]","QoS Manager failed to get license.","No action is required."
"QOS","3","MTSERROR","[chars]","QoS Manager encountered an MTS error. [chars] specifies the context where the error occurred.","No action is required."
"QOS","3","PSSERROR","[chars]","QoS Manager encountered a PSS error. [chars] specifies the context where the failure occurred.","No action is required."
"QOS","3","QOS_PSS_CORRUPTED","[chars] PSS found corrupted","The QOS Manager has detected corruption in one of its persistent information database. The database would be recreated.","No action is required."
"QOS","3","TIMEOUT_ERROR","[chars] [hex]","QoS Manager encountered a timeout [chars][hex] specify the context where the failure occurred.","No action is required."
"QOS","3","UNKNOWN_MSG","Received from Node=[dec] SAP=[dec]","The QOS Manager has received an unknown message from [dec]].[dec]. This information is for debugging only.","No action is required."
"QOS","4","LICEXP","[chars]","QoS Manager license is going to expire. [chars] gives the expected time of expiry.","No action is required."
"QOS","4","PSS_VERSION_MISMATCH","PSS [dec] Code [dec]","There was a version mismatch between the QOS Manager and one of its persistent storage databases. The persistent information has been translated to the new format.","No action is required."
"QOS","6","BECAME_ACTIVE","Became ACTIVE from standby mode.","The QOS Manager on the standby supervisor became active and it is ready to serve client requests.","No action is required."
"QOS","6","BECAME_STDBY","Became STANDBY from active mode.","The QOS Manager became standby from active mode.","No action is required."
"QOS","6","DISABLED_UP_MARKING","[chars]","The QoS Manager has disabled marking of time-critical control traffic as high-priority traffic. Priority of such traffic is now not altered by QoS Manager.","No action is required."
"QOS","6","ENABLED_UP_MARKING","[chars]","The QoS Manager has enabled marking of time-critical control traffic as high-priority traffic.","No action is required."
"QOS","6","EXCESSIVE_DELAY","[chars]","Excessive time taken for a processing event. The description of the event is [str.].","No action is required."
"QOS","6","E_PORT_ACL_SUCCESS","Successfully [chars] QOS ACL for interface [chars]","The QOS Manager has successfully programmed or erased QoS related ACL when an E-Port came up or went down for interface [str.].","No action is required."
"QOS","6","FAILED_TO_SEND_HEARTBEAT","Failed to send heartbeat to system manager: Reason=[chars]","The QOS Manager was unable to send heartbeat to the system manager.","No action is required."
"QOS","6","GENERAL_EVENT","[chars]","The QOS Manager has generated an important event. The description of the event is [str.].","No action is required."
"QOS","6","MGRCREATED","QoS Manager created","QoS Manager was created successfully and is up and running. This is an informational message.","No action is required."
"QOS","6","MGREXIT","QoS Manager shutting down gracefully","QoS Manager is shutting down gracefully. This is an informational message.","No action is required."
"QOS","6","PSS_CREATED","[chars] PSS Created","One of the persistent information database of QOS Manager has been recreated.","No action is required."
"QOS","6","PSS_DESTROYED","[chars] PSS Destroyed","One of the persistent information databases of QoS Manager has been intentionally destroyed and would be recreated.","No action is required."
"QOS","6","SERVICE_UP","Initialized [chars]","The QOS Manager is up and ready to accept client requests The service was initialized in [char] mode.","No action is required."
"QOS","6","SWITCHOVER","Switching Over to other Supervisor.","The QOS Manager has successfully switched over to the standby supervisor card.","No action is required."
"QOS","6","UNKNOWNMTS","QoS Manager received an unexpected message","QoS Manager received an unexpected message.","No action is required."
"R2D2_USD","2","R2D2_SYSLOG_CRIT","[chars] :[dec], [chars]","R2D2 instance not ok to use","Collect more information about R2D2 Reloading the module will recover."
"R2D2_USD","6","R2D2_SYSLOG_INFO","[chars]","R2D2 log message","No action is required."
"RADIUS","2","RADIUS_NO_AUTHEN_INFO","ASCII authentication not supported","ASCII authentication not supported.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"RADIUS","2","RADIUS_PROGRAM_EXIT","RADIUS daemon exiting: [chars]","RADIUS daemon is exiting.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"RADIUS","3","RADIUS_ERROR_MESSAGE","[chars]","RADIUS Error Message","No action is required."
"RADIUS","4","RADIUS_WARNING","[chars]","RADIUS Warning","No action is required."
"RADIUS","5","RADIUS_MONITOR_STATUS","[chars] [chars]","Notifying Radius server monitor status change","No action is required."
"RADIUS","5","RADIUS_NOTIFICATION","[chars]","RADIUS Notification","No action is required."
"RADIUS","5","RADIUS_SERVER_STATUS","[chars] server [chars] with auth-port [dec] and acct-port [dec] status has changed from [chars] to [chars]. Server was in previous-state for [chars], and total dead time of the server is [chars]","Notifying Radius server status change","No action is required."
"RADIUS","6","RADIUS_ACCOUNTING_MESSAGE","[chars]","Accounting Message","No action is required."
"RADIUS","6","RADIUS_MESSAGE","[chars]","RADIUS Message","No action is required."
"RDL","2","PSS_VER_FAIL","PSS file [chars] has version [dec].[dec].[dec], expected version [dec].[dec].[dec]","There was a mismatch in the PSS version. [chars] indicates the PSS service, [dec].[dec].[dec] its current version number and [dec].[dec].[dec] the expected version","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"RDL","3","SYSLOG_ALLOC_FAIL",": [chars]","RDL memory allocation failed : [chars].","No action is required."
"RDL","3","SYSLOG_CONTEXT_ERR",": [chars] [dec]","RDL context error: [chars] [dec].","No action is required."
"RDL","3","SYSLOG_ERR",": [chars]","RDL syslog errors : [chars].","No action is required."
"RDL","3","SYSLOG_EXIT",": [chars]","RDL exiting on errors : [chars].","No action is required."
"RDL","3","SYSLOG_INIT_FAIL",": [chars] [chars]","RDL Initialization Failed: [chars] [chars].","No action is required."
"RDL","3","SYSLOG_MTS_ERR",": [chars]","RDL MTS errors : [chars].","No action is required."
"RDL","6","INFORMATION","[chars]","An event happend that affects RDL. [chars] indicates the event","No action is required."
"RDL","6","PSS_ERR","[chars]","An error occurred during an RDL PSS operation. [chars] indicates the PSS operation that caused the error","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"RDL","6","SYSLOG_DEBUG_1",": [chars] [hex]","RDL Debug logs: [chars] [dec].","No action is required."
"RDL","6","SYSLOG_DEBUG_2",": [chars] [hex]","RDL Debug logs: [chars] [dec].","No action is required."
"RDL","6","SYSLOG_INFO",": [chars]","RDL Debug logs: [chars].","No action is required."
"RDL","6","SYSLOG_RESP_RCVD",": [chars] [dec]","RDL context error: [chars] [dec].","No action is required."
"RES_MGR","1","RES_MGR_HA_ERR","HA sync message received for resource [dec] which does not exist","RES_MGR Received HA msg for resource which does not exist Please check standby status and restart standby to recover","No action is required."
"RES_MGR","2","RES_MGR_CONFLICTING_RESOURCE_KEYS","The [chars] resource key [dec] from node [dec] is conflicting with other nodes.","The user should try and release the conflicting resource.","No action is required."
"RES_MGR","2","RES_MGR_CRIT","RES_MGR Critical: [chars]","RES_MGR generic critical condition","No action is required."
"RES_MGR","2","RES_MGR_HA_PSS_ERR","HA sync message received for resource [dec] with wrong pss type [dec]","RES_MGR Received HA msg for resource which does not exist Please check standby status and restart standby to recover","No action is required."
"RES_MGR","3","RES_MGR_RES_ALREADY_EXCEEDED","The VDC [dec] is currently already using more [chars] resources (total: [dec]) than the desired new maximum limit ([dec])","A limit-resource command was issued such that a VDC would be a forbidden state if we obeyed, having already allocated more resources than the new maximum limit","No action is required."
"RES_MGR","3","RES_MGR_RES_MAX_LOWER_THAN_MIN","The maximum limit for [chars] resources is not allowed to be less than the minimum limit","A limit-resource command was issued such that the desired maximum limit was lower than the desired minimum limit","No action is required."
"RES_MGR","3","RES_MGR_RES_TOO_HIGH","Limits for [chars] resources are not allowed to be set as high","A limit-resource command was issued such that a desired limit couldntbesatisfiedbecauseofstaticpolicies'","No action is required."
"RES_MGR","3","RES_MGR_RES_UNAVAIL","Missing [dec] [chars] resources currently available to satisfy the minimum limit requested for vdc [dec]","A limit-resource command was issued such that the desired minimum limit couldntbesatisfiedwiththecurrentlyavailableresources'","No action is required."
"RES_MGR","4","RES_MGR_MAX_ALLOWED_VDCS_HAS_DECREASED","The maximum number of allowed VDCs has decreased from [dec] to [dec] since binary config was saved.","When startup config was saved, more VDCs were allowed in the system.","No action is required."
"RES_MGR","4","RES_MGR_RES_ALREADY_EXCEEDED_BUT_NOT_ENFORCED","The VDC [dec] is currently already using more [chars] resources (total: [dec]) than the desired new maximum limit ([dec]) You may experience some route loss upon switchover, when the new limits will actually take effect.","A limit-resource command was issued such that a VDC may not have enough memory for holding the current amount of routing entries when the new limits will be enforced upon switchover","No action is required."
"RES_MGR","4","RES_MGR_SC_PSS_PCW_NETADMIN","Performing partial config write for resource [chars] in vdc [dec]","A copy running-config startup-config command was issued from a local admin resource limits for the specified resource in the specified vdc had to be saved as a side-effect of it","No action is required."
"RES_MGR","4","RES_MGR_SC_PSS_PCW","Performing partial config write for resource [chars]","A copy running-config startup-config command was issued from another VDC resource limits for the specified resource had to be saved as part of it","No action is required."
"RES_MGR","4","RES_MGR_UNEXPECTED_MSG_LEN","The size of this message was expected to be [dec] ([dec] keys of [dec] size with a [dec] bytes header) and instead was [dec].","A message of unexpected length was received.","No action is required."
"RES_MGR","4","RES_MGR_VLAN_RESERVED_RANGE_UNAVAILABLE","System is running with limited functionality due to restricted reserved vlan range 3968-4047 should be 3968-4096.","User should delete VLANS in range 4048-4093 and use following command: system vlan 3968 reserve","No action is required."
"RES_MGR","5","RES_MGR_DISABLED","RES_MGR Disabled","RES_MGR Service Disabled","No action is required."
"RES_MGR","5","RES_MGR_ENABLED","RES_MGR Enabled","RES_MGR Service Enabled","No action is required."
"RES_MGR","6","RES_MGR_CONDITION_VERIFIED","error [hex] [[chars]] during sysmgrcb_vdc_handshake_done() for vdc [dec]","RES_MGR is spotting some issue when VDC got created","No action is required."
"RIB","0","EMERG","[chars]","Rib caused a system failure","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"RIB","1","ALERT","[chars]","Rib caused failures in other services","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"RIB","1","LCM_FIB_ERR","RIB failed LC insertion","RIB stopped linecard from coming online due to error received from FIB during merge operation","Check RIB error logs to see error received from FIB"
"RIB","2","CRIT","[chars]","Rib encountered a catastrophic error","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"RIB","3","ERR","[chars]","Rib encountered an error","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"RIB","3","FIB_EXIT","fib exited","Fib had exited and may not continue operation","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"RIB","3","MISS_APPS","Missing response from service","Service not responding to rib","Please perform debugriberror',thenrecreatetheoperationscenario,tofindoutmoredetails.'"
"RIB","3","NO_MEM","Out of memory","Rib does not have enough memory to continue proper operation.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"RIB","3","SEND_FIB","Cannot talk to fib","Rib to fib IPC failure","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"RIB","3","SEND_SNMP","Cannot respond to snmp","Rib to snmp IPC failure","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"RIB","3","SEND_STANDBY","Cannot talk to standby rib","Lost a rib-fib transaction log due to IPC failure","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"RIB","4","CPU_HOG","Inactive or busy","Either rib was not scheduled to run, or rib was busy, and rib did not service the message or timer queue for an extended period.","Please perform debugriberror',thenrecreatetheoperationscenario,tofindoutmoredetails.'"
"RIB","4","DUP_FIB","Duplicate response from fib","Rib ignored duplicate response from fib","Please perform debugriberror',thenrecreatetheoperationscenario,tofindoutmoredetails.'"
"RIB","4","LATE_FIB","Late response from fib","Rib ignored late response from fib","Please perform debugriberror',thenrecreatetheoperationscenario,tofindoutmoredetails.'"
"RIB","4","PC_LIMIT","PC number greater than 128 (ignored by RIB)","Rib ignored pc","Please use PC number < 128"
"RIB","4","WARN","[chars]","Rib ignored the unexpected condition","Please perform debugriball',thenrecreatetheoperationscenario,tofindoutmoredetails.'"
"RIB","5","NOTE","[chars]","Rib does not support this operation","Please perform debugriball',thenrecreatetheoperationscenario,tofindoutmoredetails.'"
"RIB","6","INFO","[chars]","Rib event occurred","No action is required."
"RLIR","2","DRLIR_REJECT","DRLIR rejected: [chars]: fcid [chars], reason code [dec]","DRLIR rejected: [chars] fcid [chars] reason code [dec]","No action is required."
"RLIR","2","FC2_FAILED","RLIR FC2 operation failed: [chars]: [chars]","RLIR FC2 operation failed: [chars] [chars]","No action is required."
"RLIR","2","INIT_FAILED","RLIR Init failed: [chars]","RLIR Init failed: [chars]","No action is required."
"RLIR","2","LINK_INCIDENT","Interface [chars] [Port [hex]], Link Status: [chars], Link Status Reason: [chars]","RLIR module detected an unintentional Link Incident","No action is required."
"RLIR","2","MALLOC_FAILED","RLIR Malloc failed: [chars]","RLIR Malloc failed: [chars]","No action is required."
"RLIR","2","MTS_FAILED","RLIR MTS operation failed: [chars]: [chars]","RLIR MTS operation failed: [chars] [chars]","No action is required."
"RLIR","2","PSS_FAILED","RLIR PSS operation failed: [chars]: [chars]","RLIR PSS operation failed: [chars] [chars]","No action is required."
"RLIR","6","SYSLOG_INFO","RLIR Syslog info: [chars]","RLIR Syslog info: [chars]","No action is required."
"RLIR","6","SYSLOG_STATUS","RLIR Syslog status: [chars]: [chars]","RLIR Syslog status: [chars] [chars]","No action is required."
"RM","6","RMGR_INFO","[chars]","RMGR daemon informational message","No action is required."
"RM","6","STARTING","deamon started","The RMGR daemon successfully started","No action is required."
"RM-SLOT#","2","CPP_CATASTROPHIC_ERROR","ERROR: Component ([chars]) caused critical error. Service Module will be reloaded","Component caused critical error","Restart the linecard"
"RM-SLOT#","2","RM_CPP_RELOAD_TMOUT","ERROR: Component ([chars]) timed out for critical error response. Service Module will be reloaded","Component critical error timeout","No action is required."
"RM-SLOT#","2","RM_CRITICAL_ALERT","[chars]","Critical Alert","Restart the linecard"
"RM-SLOT#","2","RM_PROCESS_FAILED","ERROR: [chars] failed","Process failed","No action is required."
"RM-SLOT#","2","RM_PROCESS_TMOUT","ERROR: [chars] did not complete. Reloading Service Module","Component critical error timeout","No action is required."
"RM-SLOT#","2","RM_VICPP_RECREATE_ERROR","All the fast path resources are down VICPP connectivity lost","Component caused critical error","Restart the linecard"
"RM-SLOT#","4","RM_WARNING","[chars]","Warning","No action is required."
"RSCN","2","FC2_FAILED","RSCN FC2 operation failed: [chars]: [chars]","RSCN FC2 operation failed: [chars] [chars]","No action is required."
"RSCN","2","INIT_FAILED","RSCN Init failed: [chars]","RSCN Init failed: [chars]","No action is required."
"RSCN","2","MALLOC_FAILED","RSCN Malloc failed: [chars]","RSCN Malloc failed: [chars]","No action is required."
"RSCN","2","MTS_FAILED","RSCN MTS operation failed: [chars]: [chars]","RSCN MTS operation failed: [chars] [chars]","No action is required."
"RSCN","2","PSS_FAILED","RSCN PSS operation failed: [chars]: [chars]","RSCN PSS operation failed: [chars] [chars]","No action is required."
"RSCN","2","SCR_REJECT","SCR rejected: [chars]: fcid [chars], Reason code-[chars], Reason code expl-[chars]","SCR rejected: [chars] fcid [chars] Reason code [chars] Reason code expl [chars]","No action is required."
"RSCN","4","RSCN_REJECT","RSCN rejected: [chars]: fcid [chars], Reason code-[chars], Reason code expl-[chars]","RSCN rejected: [chars] fcid [chars] Reason code [chars] Reason code expl [chars]","No action is required."
"RSCN","4","SWRSCN_REJECT","SW-RSCN rejected: [chars]: fcid [chars], Reason code-[chars], Reason code expl-[chars]","SW-RSCN rejected: [chars] fcid [chars] Reason code [chars] Reason code expl [chars]","No action is required."
"RSCN","6","SYSLOG_INFO","RSCN Syslog info: [chars]","RSCN Syslog info: [chars]","No action is required."
"RSCN","6","SYSLOG_STATUS","RSCN Syslog status: [chars]: [chars]","RSCN Syslog status: [chars] [chars]","No action is required."
"SABRE_APP-SLOT#","2","SABRE_APP_EXITED","Sabre driver application exited (syserr = [dec], errno = [dec])","Sabre driver application exited","No action is required."
"SAC_USD","2","JTAG_CHECK_FAILED","Xbar Driver JTAG ID check failed for slot:[dec] asic:[dec]","Xbar Driver JTAG ID check failed","No action is required."
"SAC_USD","2","SAC_ACCESS_FAILED","Xbar Driver Failed to access reg for [chars]","Xbar Driver Access failed","No action is required."
"SAC_USD","2","SAC_CATASTROPHIC","Xbar Driver catastrophic failure: [chars]","Xbar Driver catastrophic error","No action is required."
"SAC_USD","2","SAC_INTR_OCCURED","Xbar ASIC interrupt occured: [chars]","Interrupt occured","No action is required."
"SAC_USD","2","SAC_INTR_THRESHLD","Xbar ASIC interrupt threshold reached: [chars]","Interrupt threshold reached","No action is required."
"SAC_USD","2","SAC_INTR","Xbar ASIC interrupt occurred: [chars]","Interrupt occurred on the xbar","No action is required."
"SAC_USD","2","SAC_MALLOC_FAILED","Xbar Driver memory allocation failed","Xbar Driver Access failed","No action is required."
"SAC_USD","2","SHUTDOWN","Xbar Driver software process exiting: [chars]","Xbar Driver shutting down","No action is required."
"SAC_USD","2","SYNC_FAILED","Xbar Driver sync failed: [chars]","Xbar Driver Sync failed for the xbar channel","No action is required."
"SAC_USD","3","EN_DATA_FAILED","Xbar Driver enable data failed for slot:[dec] asic:[dec] channel:[hex]","Xbar Driver Enable Datapath failed for the xbar channel","No action is required."
"SAC_USD","3","FPOE_DB_ECC","Xbar Driver FPOE DB ECC error in [chars]","FPOE DB ECC error","No action is required."
"SAC_USD","5","STARTING","Xbar Driver process starting","Xbar Driver process is being started","No action is required."
"SAC_USD","5","XBAR_FLOW_CTRL_DIS_EN","XBAR Multicast Flow Control [chars]","Sacramento xbar multicast flow control on Stage3 ports","No action is required."
"SAC_USD","6","DIS_DATA","Xbar Driver disable datapath done for slot:[dec] asic:[dec] channel:[hex]","Disabled Datapath successfully for the xbar channel","No action is required."
"SAC_USD","6","EN_DATA","Xbar Driver enable datapath done for slot:[dec] asic:[dec] channel:[hex]","Enabled Datapath successfully for the xbar channel","No action is required."
"SAC_USD","6","SAC_DEBUG_MSG","[chars]","Debug log message","No action is required."
"SAC_USD","6","SPINE_HW_INIT","Xbar Driver HW initialization has been done for Fabric-Slot:[dec] Asic:[dec]","Xbar Driver HW initialization has been called[dec]","No action is required."
"SAC_USD","6","SYNC_DONE","Xbar Driver sync done for slot:[dec] asic:[dec] channel:[hex]","Sync Completed successfully for the xbar channel","No action is required."
"SAL","5","SAL_DISABLED","SAL Disabled","SAL Service Disabled","No action is required."
"SAL","5","SAL_ENABLED","SAL Enabled","SAL Service nabled","No action is required."
"SANTAP-SLOT#","2","AVT_CREATE_FAILED","AVT PWWN: [chars], NWWN: [chars], Vsan: [dec], Host: [chars], Tgt: [chars], TgtVsan: [dec], RC: [chars]","AVT create failed because sanity check failed. Please check reason code for exact failure.","No action is required."
"SANTAP-SLOT#","2","AVT_SCSI_FAILED","AVT PWWN: [chars], Host: [chars], AVT Lun: 0x%Ld AVTVsan: [dec], OPC: [hex] RC: [chars]","SCSI command to AVT is invalid Please check reason code for exact failure.","No action is required."
"SANTAP-SLOT#","2","COMMIT_FAILED","Commit Failed, status: [dec] token = [dec], vtUid = 0x%Lx, lunId = 0x%Lx","ISAPI Commit Failed, number of ITLs exceeded limit for the DPP","No action is required."
"SANTAP-SLOT#","2","CVT_CREATE_FAILED","CVT PWWN: [chars], NWWN: [chars], Vsan: [dec], RC: [chars]","CVT create failed because sanity check failed. Please check reason code for exact failure.","No action is required."
"SANTAP-SLOT#","2","DVT_CREATE_FAILED","DVT PWWN: [chars], FEVsan: [dec], BEVsan: [dec], io_tmo: [dec], app_io_tmo: [dec], RC: [chars]","DVT create failed because sanity check failed. Please check reason code for exact failure.","No action is required."
"SANTAP-SLOT#","2","DVT_DELETE_FAILED","DVT PWWN: [chars], RC: [chars]","DVT delete failed. Please check reason code for exact failure.","No action is required."
"SANTAP-SLOT#","2","DVT_LUN_CREATE_FAILED","DVT: [chars], Host: [chars], DVTLun: 0x%LX, TGTLun: 0x%LX, HIIndex: [dec], Expected HIIndex: [dec], RC: [chars]","DVT LUN create failed because of sanity checks. Please check reason code for exact failure","No action is required."
"SANTAP-SLOT#","2","FIT_EXISTS_ON_DIFFERENT_DPP_ERR","CONFIG Error: Cannot Create FIT on DPP [dec] for DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]. Same Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex] is logged in to another DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex] on a different DPP [dec]","Same HOST cannot log into two DVTs which are on different DPPs","No action is required."
"SANTAP-SLOT#","2","FIT_EXISTS_ON_DIFFERENT_PORT_ERR","CONFIG Error: Cannot Create FIT on Ifindex [hex]. Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex] logged in to DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex] on a different ifindex [hex]","Same HOST cannot log into two DVTs which are on different ports","No action is required."
"SANTAP-SLOT#","2","HOST_PWWN_EXISTS_IN_BE_VSAN","WARNING:: Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex] Exists in BackEnd Vsan [dec], cannot create FIT for DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","FIT cannot be created, as Host exists in the Backend Vsan.","No action is required."
"SANTAP-SLOT#","2","INTERNAL_ERR","[chars]","Santap Internal Error","No action is required."
"SANTAP-SLOT#","2","ISAPI_CRIT_PROCESS_CRASH","[chars]. [chars]. SANTAP VM Size: [dec]kB","ISAPI critical error - process crash.","No action is required."
"SANTAP-SLOT#","2","PSS_DELETE_AVT_REC","AVT PWWN: [chars], NWWN: [chars], Vsan: [dec], Host: [chars], Tgt: [chars], TgtVsan: [dec], RC: [chars]","AVT PSS record is deleted because sanity check failed. Please check reason code for exact failure.","No action is required."
"SANTAP-SLOT#","2","PSS_DELETE_CVT_REC","CVT PWWN: [chars], NWWN: [chars], Vsan: [dec], RC: [chars]","CVT PSS record is deleted because sanity check failed. Please check reason code for exact failure.","No action is required."
"SANTAP-SLOT#","2","PSS_DELETE_DVT_REC","DVT PWWN: [chars], FEvsan: [dec], BEVsan: [dec], io_tmo: [dec], app_io_tmo: [dec], RC: [chars]","DVT PSS record is deleted because sanity check failed. Please check reason code for exact failure.","No action is required."
"SANTAP-SLOT#","2","SANTAP_UNPROVISIONING_NOT_SUPPORTED_DURING_PSS_RECOVERY","Santap can not be unprovisioned during pss recovery. Please wait for Santap to recover and retry.","Santap can not be unprovisioned during pss recovery. Please wait for Santap to recover and retry.","No action is required."
"SANTAP-SLOT#","2","SANTAP_VERSION_NOT_SUPPORTED","Santap feature is not supported in this version of NX-OS. Please refer to NX-OS release notes for more detail.","Santap feature is not supported in this version of NX-OS. Please refer to NX-OS release notes for more detail.","No action is required."
"SANTAP-SLOT#","2","ST_AVT_DELETED","Santap: AVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex] (avt vsan [dec]) deleted","Santap AVT is deleted as part of Unprovisioning or VSAN Delete","No action is required."
"SANTAP-SLOT#","2","ST_AVT_LUN_DELETED","Santap: AVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex] (avt lun 0x%Lx) deleted","Santap avtlun is deleted as part of Unprovisioning or VSAN Delete or CLI","No action is required."
"SANTAP-SLOT#","2","ST_CVT_DELETED","Santap: CVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex] (cvt vsan [dec], name [chars]) deleted","Santap CVT is deleted as part of Unprovisioning or VSAN Delete","No action is required."
"SANTAP-SLOT#","2","ST_DVT_DELETED","Santap: DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex] (FE vsan [dec], BE vsan [dec]) deleted","Santap DVT is deleted as part of Unprovisioning or VSAN Delete","No action is required."
"SANTAP-SLOT#","2","ST_GLOBAL_DUPLICATE_AVT_REC","PSS Error: Deleting duplicate AVT %Lx PSS record","Duplicate AVT Error","No action is required."
"SANTAP-SLOT#","2","ST_GLOBAL_DUPLICATE_CVT_IN_VSAN","PSS Error: VSAN: [dec] aleady has CVT %Lx. Deleting CVT %Lx PSS record","Multiple CVT in VSAN Error","No action is required."
"SANTAP-SLOT#","2","ST_GLOBAL_DUPLICATE_DVT_REC","PSS Error: Deleting duplicate DVT %Lx PSS record","Duplicate DVT Error","No action is required."
"SANTAP-SLOT#","2","ST_GLOBAL_NO_DVT_AVT_ERR","DVT %Lx does not exist for AVT","No DVT for AVT Error","No action is required."
"SANTAP-SLOT#","2","ST_GLOBAL_NO_HIFIT_AVT_ERR","HI %Lx does not exist for AVT %Lx","No HI for AVT Error","No action is required."
"SANTAP-SLOT#","2","ST_GLOBAL_NO_VSAN_DEL_AVT","PSS Error: VSAN: [dec] deleted. Deleting AVT %Lx PSS record","VSAN Deleted Error","No action is required."
"SANTAP-SLOT#","2","ST_GLOBAL_NO_VSAN_DEL_CVT","PSS Error: VSAN: [dec] deleted. Deleting CVT %Lx PSS record","VSAN Deleted Error","No action is required."
"SANTAP-SLOT#","2","ST_GLOBAL_NO_VSAN_DEL_DVT","PSS Error: VSAN: [dec] deleted. Deleting DVT %Lx PSS record","VSAN Deleted Error","No action is required."
"SANTAP-SLOT#","2","ST_HOST_PURGED_FROM_DVT","Santap: Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex] removed from DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex] (FE vsan [dec], BE vsan [dec]).","Santap Host Initiator is removed from DVT","No action is required."
"SANTAP-SLOT#","2","ST_MAX_32BIT_LUNS_PER_HOST_REACHED","MAX_32bit_LUNS_PER_HOST([dec]) limit reached for Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]. Cannot Install Lun 0x%Lx","System limit reached for the number of Luns per Host. More Luns cannot be added at this point.","No action is required."
"SANTAP-SLOT#","2","ST_MAX_DVT_LUNS_PER_LC_REACHED","MAX_DVT_LUNS_PER_LC([dec]) limit reached. Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], Cannot Install Lun 0x%Lx","System limit reached for the number of Luns per LC. More Luns cannot be added at this point.","No action is required."
"SANTAP-SLOT#","2","ST_MAX_HOSTS_PER_DVT_REACHED","MAX_HOST_PER_DVT([dec]) limit reached for DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]. Reject Plogi/Prli from Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","System limit reached for the number of Hosts logging into DVT. More Hosts cannot be configured at this point.","No action is required."
"SANTAP-SLOT#","2","ST_MAX_ITLS_PER_DPP_REACHED","MAX_LUNS_PER_DPP([dec]) limit reached on DPP [dec] for Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]. Cannot Install Lun 0x%Lx","System limit reached for the number of ITLs per DPP. More Luns cannot be added at this point.","No action is required."
"SANTAP-SLOT#","2","ST_MAX_LUNS_PER_DVT_REACHED","MAX_LUNS_PER_DVT([dec]) limit reached for Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]. Cannot Install Lun 0x%Lx","System limit reached for the number of Luns per DVT. More Luns cannot be added at this point.","No action is required."
"SANTAP-SLOT#","2","ST_MAX_LUNS_PER_HOST_REACHED","MAX_LUNS_PER_HOST([dec]) limit reached for Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]. Cannot Install Lun 0x%Lx","System limit reached for the number of Luns per Host. More Luns cannot be added at this point.","No action is required."
"SANTAP-SLOT#","2","ST_REPORT_LUNS_FAILED_ZONE_MISCONFIG","ZONE MISCONFIG: Report Luns Failed for Host: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], Tgt: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], dd-sts [hex], scsi-sts [hex], isapi-sts [hex]","Report Luns Failed for the specified Host, Tgt pair due to missing zone. Please check the zone configuration.","No action is required."
"SANTAP-SLOT#","2","ST_REPORT_LUNS_FAILED","Report Luns Failed for Host: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], Tgt: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], dd-sts [hex], scsi-sts [hex], isapi-sts [hex]","Report Luns Failed for the specified Host, Tgt pair. Please check the configuration.","No action is required."
"SANTAP-SLOT#","2","ST_SES_DELETED","Santap: Ses [dec] deleted","Santap ses is deleted as part of Unprovisioning or VSAN Delete or CLI","No action is required."
"SANTAP-SLOT#","4","INTERNAL_WARNING","[chars]","Santap Internal Warning","No action is required."
"SANTAP-SLOT#","4","ST_16_BIT_LUNS_PRESENT","16 Bit luns installed (current num luns [dec]) for Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]. Cannot Install Lun 0x%Lx !!","Cannot Install 16bit and 32 bit luns for the same Host-Tgt pair","No action is required."
"SANTAP-SLOT#","4","ST_32_BIT_LUNS_PRESENT","32 Bit luns installed (current num luns [dec]) for Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]. Cannot Install Lun 0x%Lx !!","Cannot Install 16bit and 32 bit luns for the same Host-Tgt pair","No action is required."
"SANTAP-SLOT#","4","ST_LUN_BLK_SIZE_GREATER_THAN_FIVE_TWELVE","Lun Block Size 0x%Lx detected is greater than 512 for Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], Lun 0x%Lx. Cannot Install this Lun.","Santap doesnt support Luns with Blk Size greater than 512","No action is required."
"SANTAP-SLOT#","4","ST_LUN_DEVICE_TYPE_NOT_SUPPORTED","Lun Device Type [dec] detected is not supported for Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], Lun 0x%Lx. Cannot Install this Lun.","Santap doesnt support devices other than DASD and ArrCntl","No action is required."
"SANTAP-SLOT#","4","ST_LUN_SIZE_GREATER_THAN_2_POW_48","Lun Size 0x%Lx detected is greater than 2 power 48 for Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], Lun 0x%Lx. Cannot Install this Lun.","Santap doesnt support Luns greater than 2 power 48","No action is required."
"SANTAP-SLOT#","4","ST_MISSING_LUN_IN_TARGET_AVT_LUN_EXISTS","Warning: Lun 0x%Lx deleted on Target but AVT LUN 0x%Lx exists for Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], AVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Please remove relevant avtluns, as Lun no longer exists on Target","No action is required."
"SANTAP-SLOT#","4","ST_MISSING_LUN_IN_TARGET_SES_EXISTS","Warning: Lun 0x%Lx deleted on Target but Session [dec] exists for Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Please remove relevant sessions, as Lun no longer exists on Target","No action is required."
"SANTAP-SLOT#","4","ST_NEAR_MAX_HOSTS_PER_DVT","Warning: Approaching MAX_HOSTS_PER_DVT([dec]) for DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]. Existing num hosts [dec]","Please be wary of the number of hosts logging in.","No action is required."
"SANTAP-SLOT#","4","ST_NEAR_MAX_LUNS_PER_HOST","Warning: Approaching MAX_LUNS_PER_HOST([dec]) limit for Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]. Existing num luns [dec]","Please be wary of the number of luns configured for this host.","No action is required."
"SANTAP-SLOT#","5","SANTAP_INFO","[chars]","SANTAP notification.","No action is required."
"SANTAP-SLOT#","6","FIT_CREATE_ERROR_TARGET_OFFLINE","Target Offline, Cannot Create FIT in vsan [dec] for Host [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex] and DVT [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","FIT Cannot be created as the target is offline","No action is required."
"SANTAP-SLOT#","6","ST_MASK_PACING_COUNTER_RESET","Current outstanding MO [dec] EMI [dec] MAO [dec] reset counter [dec] pacing? [dec] current thresholds MO [dec] EMI [dec] MAO [dec]","User has reset avt lun mask pacing counter","No action is required."
"SANTAP-SLOT#","6","ST_MASK_PACING_DISABLED","Current outstanding MO [dec] EMI [dec] MAO [dec] reset counter [dec] current thresholds MO [dec] EMI [dec] MAO [dec]","User has disabled avt lun mask pacing","No action is required."
"SANTAP-SLOT#","6","ST_MASK_PACING_ENABLED","Current outstanding MO [dec] EMI [dec] MAO [dec] reset counter [dec] current thresholds MO [dec] EMI [dec] MAO [dec]","User has enabled avt lun mask pacing","No action is required."
"SANTAP-SLOT#","6","ST_MASK_PACING_EXCL_MASK_IN_PARAM_MODIFIED","Current outstanding MO [dec] EMI [dec] MAO [dec] reset counter [dec] pacing? [dec] new thresholds MO [dec] EMI [dec] MAO [dec]","User has modified excl mask in threshold","No action is required."
"SANTAP-SLOT#","6","ST_MASK_PACING_MASK_ALL_OUT_PARAM_MODIFIED","Current outstanding MO [dec] EMI [dec] MAO [dec] reset counter [dec] pacing? [dec] new thresholds MO [dec] EMI [dec] MAO [dec]","User has modified mask all out threshold","No action is required."
"SANTAP-SLOT#","6","ST_MASK_PACING_MASK_OUT_PARAM_MODIFIED","Current outstanding MO [dec] EMI [dec] MAO [dec] reset counter [dec] pacing? [dec] new thresholds MO [dec] EMI [dec] MAO [dec]","User has modified mask out threshold","No action is required."
"SANTAP-SLOT#","6","ST_RECOVER_VSAN_DATABASE","Attempting VSAN database resync","Santap force recovery of vsans has been attempted by user. This will attemp to bring back santap vsan database in sync with the switch","No action is required."
"SANTAP-SLOT#","6","ST_RESYNC_VTS_IN_VSAN","ReSync Vsan [dec], changing state from [chars] to [chars]. All the VTs in this vsan will be resynced","Santap force recovery of vsans has been attempted by user. This will attempt to bring back santap vt in sync with ISAPI","No action is required."
"SANTAP-SLOT#","6","ST_SCP_PACING_COUNTER_RESET","Current outstanding scp [dec] reset counter [dec] threshold [dec]","User has reset scp pacing","No action is required."
"SANTAP-SLOT#","6","ST_SCP_PACING_DISABLED","Current outstanding scp [dec] reset counter [dec] threshold [dec]","User has disabled scp pacing","No action is required."
"SANTAP-SLOT#","6","ST_SCP_PACING_ENABLED","Current outstanding scp [dec] reset counter [dec] threshold [dec]","User has enabled scp pacing","No action is required."
"SANTAP-SLOT#","6","ST_SCP_PACING_PARAM_MODIFIED","Current outstanding scp [dec] reset counter [dec] pacing enabled? [dec], new threshold [dec]","User has modified the scp pacing threshold","No action is required."
"SAN_EXT_TUNER","3","SAN_EXT_TUNER_LICENSE_EXPIRED","SAN Extension Licence expired - Disabling SAN Extension Tuner","SAN Extension Licence expired/not present - Disabling SAN Extension Tuner","No action is required."
"SCHEDULER","2","SCH_SYSLOG_MALLOC_ERR","Out of memory: [chars]","Process memory exhausted. Possible memory leak.","Contact TAC"
"SCHEDULER","2","SCH_SYSLOG_MTS_ERR","MTS error: [chars]","MTS operation failure","Contact TAC"
"SCHEDULER","2","SCH_SYSLOG_PSS_SNAPSHOT_ERR","Source URI:[chars] Destination URI:[chars] errcode:[dec]","Error while performing snapshot I/O to PSS","Contact TAC"
"SCHEDULER","2","SCH_SYSLOG_SDWRAP_ERR","Debug infrastructure initialization failed: [chars]","Debug infrastructure failed to initialize","Contact TAC"
"SCHEDULER","3","SCH_ERR","[chars]","Scheduler error","No action is required."
"SCHEDULER","3","SCH_SYSLOG_FILE_ERR","[chars] Error:[chars]","File handling error","No action is required."
"SCHEDULER","3","SCH_SYSLOG_PSS_ERR","Purpose:[chars] URI:[chars] Error:[dec]","Error while performing I/O to PSS","Contact TAC"
"SCHEDULER","3","SCH_SYSLOG_USER_ERR","Description: Failed to execute job for user id [chars] Error:[dec]","Error while attempting to execute job for user. Possibly, the user is removed from the system.","Ensure the user exists. Make sure he is not a remotely authenticated user."
"SCHEDULER","4","SCH_WARN","[chars]","Scheduler warning","No action is required."
"SCHEDULER","6","SCH_MSG","[chars]","Scheduler Message","No action is required."
"SCM","2","SCMLCINSERTFAIL","[chars]","SCSI-TARGET","NONE"
"SCSI-TARGET","2","PROC_OPEN_VHBA_DEVICE_FAIL","Failed to communicate with SCSI-target driver error: [hex]","SCSI-target process failed to communicate with itspeerkerneldriver[hex].NoSCSIdiscoverycanbeperformed.'","Collect more information using command showscsi-targetinternaldriver'.'"
"SCSI-TARGET","2","PROC_SET_SCSI_INDEX_FAIL","Failed to set SCSI index SCSI-target driver error: [hex]","SCSI-target process failed to set SCSI index with itspeerkerneldriver[hex].NoSCSIdiscoverycanbeperformed.'","Collect more information using command showscsi-targetinternaldriver'.'"
"SCSI-TARGET","2","PROC_WWNM_GET_WWN_FAIL","Failed to get local controller pwwn from WWN Manager error: [hex] response: [hex]","SCSI-target process used wwnm_bwt_get_local_controller_wwn() api for the port wwn and it failed due to error [hex], response code [hex]. No SCSI discovery can be performed.","Collect more information using commands showprocesscpu'and'showsysteminternalsysmgrserviceall'.SeeWWNManagersystemerrorcodesforr eason.'"
"SCSI-TARGET","2","PSS_INIT_FAIL","pss initialization failed due to error: [hex]","SCSI-target process pss initialization failure due to error [hex]. No SCSI discovery can be performed.","Collect more information using command showflash'.Seepsssystemerrorcodesforreason.'"
"SCSI-TARGET","3","PROC_VSAN_GET_RATOV_FAIL","Failed to get vsan attribute RATOV from VSAN Manager, error: [hex]","SCSI-target process used the vsan_get_global_value() api for RATOV and it failed due to error [hex].","This is a non-fatal error. The default value for RATOV is used. Collect more information using commands showprocesscpu'and'showsysteminternalsysmgrserviceall'.SeeVsanManagersystemerrorcodesforre ason.'"
"SCSI-TARGET","3","PSS_CREATE_FAIL","pss create runtime database failed due to error: [hex]","SCSI-target process pss create runtime database failure due to error [hex]. No SCSI discovery can be performed.","Collect more information using command showflash'.Seepsssystemerrorcodesforreason.'"
"SCSI-TARGET","3","PSS_DELETE_FAIL","pss delete runtime entry key:[hex] failed due to error: [hex]","SCSI-target process pss delete runtime entry key [hex] failure due to error [hex].","Collect more information using command showflash'.Seepsssystemerrorcodesforreason.'"
"SCSI-TARGET","3","PSS_MAX_KEY_FAIL","pss set runtime max key failed due to error: [hex]","SCSI-target process pss set runtime max key failure due to error [hex]. No SCSI discovery can be performed.","Collect more information using command showflash'.Seepsssystemerrorcodesforreason.'"
"SCSI-TARGET","3","PSS_MAX_VALUE_FAIL","pss set runtime max value failed due to error: [hex]","SCSI-target process pss set runtime max value failure due to error [hex]. No SCSI discovery can be performed.","Collect more information using command showflash'.Seepsssystemerrorcodesforreason.'"
"SCSI-TARGET","3","PSS_OPEN_FAIL","pss open runtime database failed due to error: [hex]","SCSI-target process pss open runtime database failure due to error [hex]. No SCSI discovery can be performed.","Collect more information using command showflash'.Seepsssystemerrorcodesforreason.'"
"SCSI-TARGET","3","PSS_RELOAD_FAIL","pss reload runtime database failed due to error: [hex]","SCSI-target process pss reload runtime database failure due to error [hex].","Collect more information using command showflash'.Seepsssystemerrorcodesforreason.'"
"SCSI-TARGET","3","PSS_SNAPSHOT_DEBUG_FAIL","pss snapshot runtime debug to uri:[chars] failed due to error: [hex]","SCSI-target process pss snapshot of runtime debug to uri [string] failed due to error [hex].","Collect more information using command showflash'.Seepsssystemerrorcodesforreason.'"
"SCSI-TARGET","3","PSS_SNAPSHOT_FAIL","pss snapshot runtime to uri:[chars] failed due to error: [hex]","SCSI-target process pss snapshot of runtime to uri [string] failed due to error [hex].","Collect more information using command showflash'.Seepsssystemerrorcodesforreason.'"
"SCSI-TARGET","3","PSS_STORE_FAIL","pss store runtime entry key:[hex] val:[hex] failed due to error: [hex]","SCSI-target process pss store runtime entry key [hex] value [hex] failure due to error [hex].","Collect more information using command showflash'.Seepsssystemerrorcodesforreason.'"
"SCSI-TARGET","7","SCSI_TARGET_DISCOVERED","SCSI-target discovered VSAN:[dec] FCID:[hex] prlisparm:[hex]","SCSI-target process discovered VSAN [dec] FCID [hex] prli service parameter [hex].","None"
"SDV","2","RANDNUM_FAIL","Random number generation failed","Random number generation failed. Process has to exit due to FIPS compliance","No action is required."
"SDV","3","ACL_CACHE_ERROR","ACL CACHE ERR, Trying to prog with no interface list","A Null interface list was generated for a ACL entry","No action is required."
"SDV","3","ACL_ERROR","ACL API, [chars], failed with error [hex]","SDV invoked ACL API and received the error code. [chars] describes the API and 0x[hex] specifies the error.","No action is required."
"SDV","3","ALLOC_FAILED","Failed for type [dec] size [dec]","SDM process could not allocate heap memory. [dec] is the memory type and [dec] is the size of memory","No action is required."
"SDV","3","ASSERTION_FAILED","[chars]:[dec]","SDM process has hit an assert condition at file [chars] line number [dec]","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SDV","3","AUTO_FAILOVER_ERROR","[chars]","SDV Virtual-device failed to auto-failover due to [chars]","No action is required."
"SDV","3","BCAST_NOT_SUPPORTED","Broadcast attribute will be ignored for SDV devices","Broadcast attribute will be ignored for SDV devices","No action is required."
"SDV","3","ENQUEUE_EVENT_FAIL","Unable to enqueue event into state machine","Unable to enqueue event into state machine","No action is required."
"SDV","3","FCID_REWRITE_REQUEST_TO_ACL_FAILED","fcid rewrite [chars] request vsan [dec] vdev_id [dec] failed:[chars].","This happens when either after SDV retried the request few times or ACL experienced error while processing the request.","No action is required."
"SDV","3","INIT_FAIL","[chars]","SDM process init has failed due to [chars]","No action is required."
"SDV","3","INTERNAL_ERR","[chars]","SDM process encountered an internal error due to [chars]","No action is required."
"SDV","3","LOCK_FAILED","[chars]","An error occurred while acquiring the lock. The reason for the failure : [chars]","No action is required."
"SDV","3","MERGE_ACTIVATION_FAILED","[chars]","Error while activating the merged SDV database due to [chars]","No action is required."
"SDV","3","MERGE_CAP_FAILED","[chars]","SDV fabric merge failed because of incomaptible capabilities [chars]","Compare SDV configuration in both fabrics and resolve the conflicts if any and commit the changes."
"SDV","3","MERGE_FAILED","[chars]","SDV fabric merge failed due to [chars]","Check the error using 'show sdv merge staus vsan <vsan-id"
"SDV","3","MTS_ERR","[chars]","SDM process encountered an MTS error due to [chars]","No action is required."
"SDV","4","FCID_REWRITE_REQUEST_TO_ACL_FAILED_AND_RETRYING","failed:[chars]. Retrying the request again.","This happens when either any of the linecards being upgraded or ACL experienced error while processing the request.","No action is required."
"SDV","6","INTERNAL_ERR_INFO","[chars]","SDM process encountered ignorable error due to [chars]","No action is required."
"SDV","7","SRVCREATED","SDM Process started","SDM process has started","No action is required."
"SECURITYD","2","FIPS_BYPASS_SELF_TEST_STATUS","FIPS Bypass self-test status : [chars]","Status of FIPS self-test [chars]","No action is required."
"SECURITYD","2","FIPS_CRNG_SELF_TEST_STATUS","FIPS CRNG self-test status : [chars]","Status of FIPS self-test [chars]","No action is required."
"SECURITYD","2","FIPS_CRYPTO_SELF_TEST_STATUS","FIPS [chars] Crypto self-test status : [chars]","Status of FIPS [chars] self-test [chars]","No action is required."
"SECURITYD","2","FIPS_IMAGE_INTEGRITY_SELF_TEST_STATUS","FIPS Image Integrity self-test status : [chars]","Status of FIPS [chars] self-test [chars]","No action is required."
"SECURITYD","2","FIPS_POST_ERROR_MSG","[chars]","Fips post Error Message","No action is required."
"SECURITYD","2","FIPS_POST_MAINTENANCE","FIPS Test failed. Moving to maintenance mode","FIPS Test failed. Moving to maintenance mode","No action is required."
"SECURITYD","2","FIPS_POST_TEST_FAILED","FIPS crypto-test failure : [dec]","FIPS crytpo-test failed [chars]","No action is required."
"SECURITYD","2","FIPS_POWERUP_SELF_TESTS_STATUS","FIPS power-up self-test status: [chars]","Status FIPS self-test [chars]","No action is required."
"SECURITYD","2","FIPS_POWERUP_SELF_TEST_STATUS","FIPS [chars] power-up self-test status : [chars]","Status of FIPS [chars] power-up self-test [chars]","No action is required."
"SECURITYD","2","FIPS_SELF_TEST_FAILED","FIPS self-test failure : [chars] : [chars]","FIPS self-test failed [chars] for service [chars]","No action is required."
"SECURITYD","2","PROGRAM_EXIT","security/accounting daemon exiting: [chars]","Security/accounting daemon is exiting.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SECURITYD","3","NVRAMFAILURE","nvram failure","Nvram can not be read/written to. Hence accounting log can not be stored there","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SECURITYD","6","ACCOUNTING_MESSAGE","[chars]","Accounting Message","No action is required."
"SECURITYD","6","CHANGE_PASSWD","changing passwd for [chars]","Changing passwd for [chars]","No action is required."
"SECURITYD","6","DELETE_STALE_USER_ACCOUNT","deleting expired user account:[chars]","Deleting expired user account of [chars]","No action is required."
"SECURITYD","6","FIPS_MODE_SET_FAILED","Error when setting FIPS mode : [chars]","FIPS mode failed [chars]","No action is required."
"SECURITYD","6","FIPS_MODE_SET","FIPS mode is [chars] for service [chars]","FIPS mode is changed [chars] [chars]","No action is required."
"SECURITYD","6","FIPS_POST_INFO_MSG","[chars]","Fips post Information Message","No action is required."
"SENSOR_USD","2","SNSM_SYSLOG_INIT_FAILED","Sensor Mgr Initialization failed. Component [chars]","Sensor Manager syslog message","No action is required."
"SENSOR_USD","2","SNSM_SYSLOG_SHUTDOWN","Sensor Mgr process shutting down: [chars]","Sensor Manager syslog message","No action is required."
"SENSOR_USD","2","SNSM_SYSYLOG_ALLOC_MEMORY","Sensor Mgr Memory allocation failed","Sensor Manager syslog message","No action is required."
"SENSOR_USD","3","MSG_SNSM_SYS_MEM_ALOC_FAILURE","Sensor Mgr Error in allocing mem: [dec], Error code = [dec]","Sensor Manager syslog message","No action is required."
"SENSOR_USD","3","SNSM_API_CALL_FAILURE","Sensor Mgr Error in [chars] call errno=[dec]","Sensor Manager syslog message","No action is required."
"SENSOR_USD","3","SNSM_SYSLOG_BAD_MTS_MSG","Sensor Mgr Received bad MTS message: [dec]","Sensor Manager syslog message","No action is required."
"SENSOR_USD","3","SNSM_SYSLOG_MTS_PROCESS_ERROR","Sensor Mgr Error in processing MTS message: [dec], Error code = [hex]","Sensor Manager syslog message","No action is required."
"SENSOR_USD","3","SNSM_SYS_DEQUE_PENDING_QUE_FAILURE","Sensor Mgr Error in Dequing pend Que: %p, Error code = [hex]","Sensor Manager syslog message","No action is required."
"SENSOR_USD","3","SNSM_SYS_ENQUE_PENDING_QUE_FAILED","Sensor Mgr Error in queuing to pending queue: %p, Error code = [hex]","Sensor Manager syslog message","No action is required."
"SENSOR_USD","3","SNSM_SYS_MTS_RECV_FAILURE","Sensor Mgr Error in receving MTS mesg","Sensor Manager syslog message","No action is required."
"SENSOR_USD","5","SNSM_SYSLOG_STARTING","Sensor Mgr process started","Sensor Manager syslog message","No action is required."
"SESSION-MGR","2","DB_UNLOCK_FAILED","Failed to unlock the database for session:[chars]","Session-Manager failed to unlock the database for session: [chars]","No action is required."
"SESSION-MGR","3","ALLOC_FAILED","Failed in File:[chars] Line:[dec] for type [dec] size [dec]","Session-mgr process could not allocate heap memory in File:[chars], at line:[dec], for memory-type:[dec] of Size:[dec]","No action is required."
"SESSION-MGR","4","ISSU_FAILED","[chars] :[hex]","Session manager failed ISSU because of:[string] and error: [hex]","No action is required."
"SENSOR","0","DC3_SENSOR_MSG","[chars]","SENSOR log emergency message","No action is required."
"SENSOR","3","DC3_SENSOR_MSG1","[chars]","SENSOR log message","No action is required."
"SESSION-MGR","2","DB_UNLOCK_FAILED","Failed to unlock the database for session:[chars]","Session-Manager failed to unlock the database for session: [chars]","No action is required."
"SESSION-MGR","3","ALLOC_FAILED","Failed in File:[chars] Line:[dec] for type [dec] size [dec]","Session-mgr process could not allocate heap memory in File:[chars], at line:[dec], for memory-type:[dec] of Size:[dec]","No action is required."
"SESSION-MGR","4","ISSU_FAILED","[chars] :[hex]","Session manager failed ISSU because of:[string] and error: [hex]","No action is required."
"SFC","3","ERROR","[chars]","SCSI Flow Client encountered an error","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SFM","2","NO_LICENSE_WARNING","SCSI Flow Manager is shutting down as no license is available.","License required for continued SCSI Flow Manager operation is not available.","No action is required."
"SFM","6","LICENSE_VALID","A valid license for SCSI FLow Manager has been obtained","A valid license for SCSI Flow Manager has been obtained","No action is required."
"SIM","2","IF_CRITICAL_FAILURE","(Debug syslog)Critical failure: [chars], [chars]","There was a critical failure in the component.","Please follow instructions on the syslog."
"SIM","2","IF_DOWN_ERROR_DISABLED","Interface [chars] is down (Error disabled. Reason:[chars])","The interface encountered an error while configuring it","Collect more information about failed interface using command showportinternalallinterface[char]'.Inmostcases,youcanrecoverusinga'shutdown'followeda'noshutd own'ontheinterfaceorremovingandre-insertingthefibreopticcable.'"
"SIM","2","IF_DOWN_LINK_FAILURE_CRIT","Interface [chars] is down (Link failure)","The physical link has gone down","Ensure that the cable is connected and the remote end is not shut down"
"SIM","2","SEQ_TIMEOUT","Component [chars] timed out on response to opcode [chars] ([chars])","Some component did not respond to a request in stipulated time.","None"
"SIM","2","SYSLOG_SIM_CRITICAL","Critical failure: [chars]","There was a critical failure in the component.","Please collect system tech-support"
"SIM","3","IF_DOWN_CHANNEL_ERR_DISABLED","Interface [chars] is down (Channel error disabled)","This interface belongs to a PortChannel and the PortChannel is error disabled","Perform shut'and'noshutdown'onthePortChannelinterfacethatitbelongsto'"
"SIM","3","IF_ERROR_VLANS_REMOVED","VLANs [chars] on Interface [chars] are removed from suspended state.","The VLANs on an interface are being removed from the suspended state","No action is required."
"SIM","3","IF_ERROR_VLANS_SUSPENDED","VLANs [chars] on Interface [chars] are being suspended. (Reason: [chars])","The VLANs on an interface are being suspended due to some protocol action","No action is required."
"SIM","3","IF_SFP_ALARM","Interface [chars], [chars]","There was an alarm on the transceiver module","Please do show interface transceiver details to obtain more information"
"SIM","3","IF_SFP_ERROR","Interface [chars], [chars]","There was an error on the transceiver module","Please do show interface transceiver details to obtain more information"
"SIM","3","IF_UNSUPPORTED_TRANSCEIVER","Transceiver on interface [chars] is not supported","The transceiver for the interface specified in the error message is not a Cisco supported module","Replace the module with a compatible transceiver. If the transceiver was purchased from Cisco, please contact Cisco TAC to get the transceiver replaced"
"SIM","3","IF_XCVR_ALARM","Interface [chars], [chars]","There was an alarm on the transceiver module","Please do show interface transceiver details to obtain more information"
"SIM","3","IF_XCVR_ERROR","Interface [chars], [chars]","There was an error on the transceiver module","Please do show interface transceiver details to obtain more information"
"SIM","4","IF_NON_QUALIFIED_TRANSCEIVER","Non-qualified transceiver on interface [chars] was detected","The transceiver for the interface specified has not been qualified on this platform for this software release","Replace the module with a supported transceiver. Contact Cisco TAC to get platform transceiver qualification details"
"SIM","4","IF_SFP_WARNING","Interface [chars], [chars]","There was an warning on the transceiver module","Please do show interface transceiver details to obtain more information"
"SIM","4","IF_XCVR_WARNING","Interface [chars], [chars]","There was an warning on the transceiver module","Please do show interface transceiver details to obtain more information"
"SIM","5","IF_ADMIN_UP","Interface [chars] is admin up [chars]","Interface is admin up","No action is required."
"SIM","5","IF_BANDWIDTH_CHANGE","Interface [chars],bandwidth changed to [chars] Kbit","Bandwidth of the interface (port channel) has changed and this change is updated","No action is required."
"SIM","5","IF_DOWN_ADMIN_DOWN","Interface [chars] is down (Administratively down)","Interface has been configured to be administratively down","Perform noshutdown''"
"SIM","5","IF_DOWN_CFG_CHANGE","Interface [chars] is down(Config change)","FCIP interface temporarily down due to reconfiguration","No action is required."
"SIM","5","IF_DOWN_CHANNEL_ADMIN_DOWN","Interface [chars] is down (Channel admin down)","This interface belongs to a PortChannel and the PortChannel is configured to be administratively down","Perform noshutdown'onthePortChannelinterfacethatitbelongsto'"
"SIM","5","IF_DOWN_CHANNEL_MEMBERSHIP_UPDATE_IN_PROGRESS","Interface [chars] is down (Channel membership update in progress)","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","Retry the configuration again"
"SIM","5","IF_DOWN_DOMAIN_ADDR_ASSIGN_FAILURE_ISOLATION","Interface [chars] is down (Isolation due to domain id assignment failure)","Isolated due to a failure while assigning a domain","No action is required."
"SIM","5","IF_DOWN_DOMAIN_INVALID_RCF_RECEIVED","Interface [chars] is down (Isolation due to invalid fabric reconfiguration)","Invalid RCF received","No action is required."
"SIM","5","IF_DOWN_DOMAIN_MANAGER_DISABLED","Interface [chars] is down (Isolation due to domain manager disabled)","Isolated due to domain manager being disabled","No action is required."
"SIM","5","IF_DOWN_DOMAIN_MAX_RETRANSMISSION_FAILURE","Interface [chars] is down (Isolation due to domain manager other side not responding)","Remote end domain manager not responding","No action is required."
"SIM","5","IF_DOWN_DOMAIN_OTHER_SIDE_EPORT_ISOLATED","Interface [chars] is down (Isolation due to domain other side eport isolated)","Isolating this interface due to the remote end being isolated","No action is required."
"SIM","5","IF_DOWN_DOMAIN_OVERLAP_ISOLATION","Interface [chars] is down (Isolation due to domain overlap)","Isolated due to domain overlap","No action is required."
"SIM","5","IF_DOWN_ELP_FAILURE_ISOLATION","Interface [chars] is down (Isolation due to ELP failure)","ELP failed on the interface","Check the output of showportinternalinfo'inthe'ELPfailurereason'field'"
"SIM","5","IF_DOWN_EPP_FAILURE","Interface [chars] is down (Error Disabled - EPP Failure)","Trunk protocol failed","showportinternalevent-historymsgs'willindicatethetrunkprotocolexchangestodeterminewhyitfailed'"
"SIM","5","IF_DOWN_ESC_FAILURE_ISOLATION","Interface [chars] is down (Isolation due to ESC failure)","ESC failed on the interface","Check the output of showportinternalevent-history'todeterminetheESCprotocolexchangestodeterminehowitfailed'"
"SIM","5","IF_DOWN_ETH_IF_DOWN","Interface [chars] is down(Tunnel port src interface down)","Ethernet link to which the FCIP interface is bound is down","Ensure that the ethernet cable is connected, the interface is administratively enabled"
"SIM","5","IF_DOWN_ETH_LINK_DOWN","Interface [chars] is down(Tunnel port src interface link down)","Ethernet link to which the FCIP interface is bound is down","Ensure that the ethernet cable is connected and the remote end is also active"
"SIM","5","IF_DOWN_FCOT_NOT_PRESENT","Interface [chars] is down (FCOT not present)","The FCOT has been removed","Insert an FCOT"
"SIM","5","IF_DOWN_FCOT_VENDOR_NOT_SUPPORTED","Interface [chars] is down (Error disabled - Fcot vendor not supported)","Fcot inserted is not a supported one","Please contact customer support for a list of authorized transceiver vendors"
"SIM","5","IF_DOWN_HW_FAILURE","Interface [chars] is down (Hardware Failure)","The moduleshardwarehasfailed'","Collect more information about failed module using command showmoduleinternalallmodule''"
"SIM","5","IF_DOWN_INACTIVE","Interface [chars] is down (Inactive)","The port VSAN has been suspended or deleted","Assign a new active port VSAN to the interface"
"SIM","5","IF_DOWN_INCOMPATIBLE_ADMIN_MODE","Interface [chars] is down (Error disabled - Incompatible admin port mode)","The configured mode is not supported on this interface","Perform a showportinternalinfo'todeterminethelistofmodessupportedonthisinterface'"
"SIM","5","IF_DOWN_INCOMPATIBLE_ADMIN_RXBBCREDIT","Interface [chars] is down (Error disabled - Incompatible admin port rxbbcredit)","The configured receive B2B credit size is not supported","Get the allowed receive B2B credit size from showportinternalinfo''"
"SIM","5","IF_DOWN_INCOMPATIBLE_ADMIN_RXBUFSIZE","Interface [chars] is down (Error disabled - Incompatible admin port rxbufsize)","The configured receive buffer size is not supported","Get the allowed receive buffer size from showportinternalinfo''"
"SIM","5","IF_DOWN_INCOMPATIBLE_ADMIN_SPEED","Interface [chars] is down (Error disabled - Incompatible admin port speed)","The configured speed is not supported on this interface","Perform a showportinternalinfo'todeterminetherangeofspeedsupportedonthisinterface'"
"SIM","5","IF_DOWN_INITIALIZING","Interface [chars] is down (Initializing)","The interface is in the process of coming up","If the interface is stuck in this state for a while, check the output of showportinternalevent-history'todeterminewhatitiswaitingfor'"
"SIM","5","IF_DOWN_INTERFACE_REMOVED","Interface [chars] is down (Interface removed)","Interface removed","No action is required."
"SIM","5","IF_DOWN_LINK_FAILURE","Interface [chars] is down (Link failure)","The physical link has gone down","Ensure that the cable is connected and the remote end is not shut down"
"SIM","5","IF_DOWN_LOOPBACK_DIAG_FAILURE","Interface [chars] is down (Diag failure)","Diag failed on the interface","Collect more information about failed interface using command attachmodule'toconnecttomodule'"
"SIM","5","IF_DOWN_LOOPBACK_ISOLATION","Interface [chars] is down (Isolation due to port loopback to same switch)","The interface is looped back to another interface on the same switch","Check the connectivity of this interface and ensure that it is connected to another switch"
"SIM","5","IF_DOWN_MODULE_REMOVED","Interface [chars] is down (module removed)","Interface is down because the module was removed","No action is required."
"SIM","5","IF_DOWN_NONE","Interface [chars] is down ([chars])","Interface is down with a possible reason.","Collect more information about port using command showportinternalinfo/event-history'todeterminewhyitwentdown'"
"SIM","5","IF_DOWN_NON_PARTICIPATING","Interface [chars] is down (Non participating)","The loop port has been put into non participating mode","No action is required."
"SIM","5","IF_DOWN_OFFLINE","Interface [chars] is down (Offline)","The interface has been placed into the offline state","No action is required."
"SIM","5","IF_DOWN_PARENT_ADMIN_DOWN","Interface [chars] is down (Parent interface down)","Parent interface is down","No action is required."
"SIM","5","IF_DOWN_PEER_CLOSE","Interface [chars] is down(TCP conn. closed by peer)","The FCIP peer connected to this interface closed the TCP connection","This command will provide the peer IP address of this FCIP interface: show interface. Check to see why the peer closed the TCP connection"
"SIM","5","IF_DOWN_PEER_RESET","Interface [chars] is down(TCP conn. reset by peer)","TCP connection to the FCIP peer got reset","The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Check to see why the peer reset the TCP connection"
"SIM","5","IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN","Interface [chars] is down (No operational members)","This is a PortChannel interface and all its members are operationally down","Enable at least one of the PortChannelsmembers'"
"SIM","5","IF_DOWN_PORT_VSAN_MISMATCH_ISOLATION","Interface [chars] is down (Isolation due to port vsan mismatch)","Isolated due to a mismatch in the configured port VSAN of the local and remote ends","Configure the port VSAN of the local and remote interfaces to be the same and perform a shutdown'anda'noshutdown''"
"SIM","5","IF_DOWN_RCF_IN_PROGRESS","Interface [chars] is down (RCF in progress)","There is an RCF in progress","No action is required."
"SIM","5","IF_DOWN_SOFTWARE_FAILURE","Interface [chars] is down (Port software failure)","The software servicing the data path on the port has failed","No action is required."
"SIM","5","IF_DOWN_SRC_MOD_NOT_ONLINE","Interface [chars] is down(Tunnel source module not online)","Module that has the tunnel source port of this FCIP interface is not fully online","The module that has the tunnel src port is coming online. Please use show mod to find module status"
"SIM","5","IF_DOWN_SRC_PORT_NOT_BOUND","Interface [chars] is down (Tunnel port src interface unbound)","Tunnel port source interface unbound","No action is required."
"SIM","5","IF_DOWN_SRC_PORT_REMOVED","Interface [chars] is down(Tunnel src port removed)","Tunnel source port of this FCIP interface has been removed","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"
"SIM","5","IF_DOWN_SUSPENDED_BY_MODE","Interface [chars] is down (Suspended due to incompatible mode)","This interface belongs to a PortChannel and operational mode of the interface is different from that of the PortChannel","Change the mode and the trunking mode of the PortChannel from auto'andchecktoensurethattheremoteendoftheinterfacealsobelongstothesamePortChannel'"
"SIM","5","IF_DOWN_SUSPENDED_BY_SPEED","Interface [chars] is down (Suspended due to incompatible speed)","This interface belongs to a PortChannel and operational speedode of the interface is different from that of the PortChannel","Change the speed of the PortChannel from auto'andchecktoensurethattheremoteendoftheinterfacealsobelongstothesamePortChannel'"
"SIM","5","IF_DOWN_SUSPENDED_BY_WWN","Interface [chars] is down (Suspended due to incompatible remote switch WWN)","This interface belongs to a PortChannel and remote switch WWN of the interface is different from that of the PortChannel","Ensure that this interface is connected to the same remote switch as all the other interfaces in the PortChannel"
"SIM","5","IF_DOWN_SUSPENDED","Interface [chars] is down (Suspended)","This interface belongs to a PortChannel and has been suspended due to an error while bringing it up","Perform a shutdown'anda'noshutdown'.Ifthishappensagainobtainoutputof'showportinternalinfo/event-history' ontheinterface'"
"SIM","5","IF_DOWN_TCP_KEEP_ALIVE_EXPIRED","Interface [chars] is down(TCP conn. closed - Keep alive expired)","TCP session to the FCIP peer got closed due to loss of TCP keep alive","This may be due to loss of IP connectivity. The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Please do a trace route to check the connectivity to the peer using command:traceroute ipaddr"
"SIM","5","IF_DOWN_TCP_MAX_RETRANSMIT","Interface [chars] is down(TCP conn. closed - retransmit failure)","Interface is down due to maximum retransmission failure","This may be due to loss of IP connectivity. The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Please do a trace route to check the connectivity to the peer using command:traceroute ipaddr"
"SIM","5","IF_DOWN_TCP_PERSIST_TIMER_EXPIRED","Interface [chars] is down(TCP conn. closed - Persist timer expired)","TCP session to the FCIP peer closed because TCP persist timer expired","This may be due to loss of IP connectivity. The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Please do a trace route to check the connectivity to the peer using command:traceroute ipaddr"
"SIM","5","IF_DOWN_UPGRADE_IN_PROGRESS","Interface [chars] is down (Linecard upgrade in progress)","Upgrade of the linecard software is in progress","No action is required."
"SIM","5","IF_DOWN_VRF_UNUSABLE","Interface [chars] is down (Vrf down)","The vrf for which this interface is a member is removed","No action is required."
"SIM","5","IF_DOWN_VSAN_MISMATCH_ISOLATION","Interface [chars] is down (Isolation due to vsan mismatch)","This is a trunking interface and the VSANs configured do not match with the VSANs configured on the remote end","Check the VSANs configured on the local end with the remote end"
"SIM","5","IF_DOWN_ZONE_MERGE_FAILURE_ISOLATION","Interface [chars] is down (Isolation due to zone merge failure)","Isolated due to a failure during zone merge","No action is required."
"SIM","5","IF_DOWN_ZONE_REMOTE_NO_RESP_ISOLATION","Interface [chars] is down (Isolation due to remote zone server not responding)","Isolated due to remote zone server not responding","No action is required."
"SIM","5","IF_DUPLEX","Interface [chars], operational duplex mode changed to [chars]","Operational duplex mode has changed when link came up","No action is required."
"SIM","5","IF_ERRDIS_RECOVERY","Interface [chars] is being recovered from error disabled state (Last Reason:[chars])","Interface is being recovered from error disabled state","No action is required."
"SIM","5","IF_HARDWARE","Interface [chars], hardware type changed to [chars]","There was a change in the hardware characteristic of an interface, such as a transceiver module plugged in or removed","No action is required."
"SIM","5","IF_L2MP_MODE","Interface [chars], l2mp-mode changed to [chars]","The l2mp-mode on the port has changed","No action is required."
"SIM","5","IF_RX_FLOW_CONTROL","Interface [chars], operational Receive Flow Control state changed to [chars]","Operational receive flow control has changed when link came up","No action is required."
"SIM","5","IF_TRUNK_DOWN","Interface [chars], vlan [chars] down","Interface [chars] is trunking, VLANs [chars] are down","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"
"SIM","5","IF_TRUNK_UP","Interface [chars], vlan [chars] up","Interface [chars] is trunking, VLANs [chars] are up","No action is required."
"SIM","5","IF_TX_FLOW_CONTROL","Interface [chars], operational Transmit Flow Control state changed to [chars]","Operational transmit flow control has changed when link came up","No action is required."
"SIM","5","IF_UP","Interface [chars] is up [chars]","Interface is up in mode specified, if applicable","No action is required."
"SIM","5","SPEED","Interface [chars], operational speed changed to [chars]","Operational speed has changed when link came up","No action is required."
"SIM","5","STORM_CONTROL_ABOVE_THRESHOLD","Traffic in port [chars] exceeds the configured threshold [chars]","Traffic on specified port is beyond the configured storm-control threshold, and the excess traffic is being dropped","Identify source of traffic storm"
"SIM","5","STORM_CONTROL_BELOW_THRESHOLD","Traffic in port [chars] has fallen below the configured threshold [chars]","Traffic on specified port has returned to within configured storm-control threshold","No action is required."
"SKSD","2","SKSD_CRYPT_SERVICE_CRIT","Encryption-Service: [chars]","Encryption Service critical errors.","No action is required."
"SKSD","3","SKSD_CRYPT_SERVICE_ERR","Encryption-Service: [chars]","Encryption Service errors.","No action is required."
"SKSD","3","SKSD_FIPS_MODE_INIT_ERROR","Could not initialize FIPS mode : [chars]","FIPS mode initialization error","No action is required."
"SKSD","3","SKSD_FIPS_MODE_SELFTEST","FIPS POST for [chars] [chars]","FIPS Selftest Result","No action is required."
"SKSD","4","SKSD_CRYPT_SERVICE_WARN","Encryption-Service: [chars]","Encryption Service warnings.","No action is required."
"SKSD","5","SKSD_CRYPT_SERVICE_NOTICE","Encryption Service: [chars]","Encryption Service updates.","No action is required."
"SKSD","5","SKSD_EXIT","Keystore Application Exiting: [chars]","Keystore Program exiting","No action is required."
"SKSD","5","SKSD_FUNC","Keystore Operation: [chars]","Keystore Event upon a receiving a request","No action is required."
"SKSD","5","SKSD_HW_INIT","Hardware Keystore Init done","Hardware Keystore Init completed","No action is required."
"SKSD","5","SKSD_HW_RESET","Hardware Reset :[chars]","Hardware Reset","No action is required."
"SKSD","5","SKSD_HW","Smartcard :[chars]","Smartcard Presence","No action is required."
"SKSD","5","SKSD_INIT","Keystore Application Init: [chars]","Keystore Program Init","No action is required."
"SKSD","5","SKSD_KEY_ADD","Key added","Key added to keystore","No action is required."
"SKSD","5","SKSD_KEY_DELETE","Key deleted","Key deleted from keystore","No action is required."
"SKSD","5","SKSD_MKEY_INSTALL","Installing a Master Key on the smartcard(s)","Installing a new Master Key on the smartcard(s)","No action is required."
"SKSD","5","SKSD_SUP_STATE","Supervisor card new state: [dec]","Supervisor state change","No action is required."
"SKSD","5","SKSD_SW_INIT","Software Keystore Init done","Software Keystore Init completed","No action is required."
"SKSD","6","SKSD_CRYPT_SERVICE_INFO","Encryption Service: [chars]","Encryption Service informational updates.","No action is required."
"SKT_USD","2","SKT_RF_CRC_ERR","[chars]","Skytrain received packet(s) from fabric with CRC error","No action is required."
"SKT_USD","6","SKT_DEBUG_MSG","[chars]","Debug log message","No action is required."
"SKYLINE_APP-SLOT#","2","SKYLINE_APP_EXITED","Skyline driver application exited (syserr = [dec], errno = [dec])","Skyline driver application exited","No action is required."
"SME_CPP","2","IT_NEXUS_MAX_INTERFACE_LIMIT_REACHED","[chars] cannot be bound as the interfaces reached the maximum IT Nexus limit","IT Load Balancing failed","No action is required."
"SME_CPP","2","LOG_ERR_SME_CTRL_LUN_PATH_MISCONFIG","Control LUN [chars] behind Host PWWN [chars] Tgt PWWN [chars] LUN Id [chars] has some lun paths that are not configured.","A single lun with multiple paths has some non configured paths. Please configure all lun paths.","No action is required."
"SME_CPP","2","LOG_ERR_SME_DIFF_LUN_MISCONFIG","Lun [chars] and [chars] behind Host PWWN [chars] Tgt PWWN [chars] LUN Id [chars] configured as one device.","Two different luns configured as one device. Please fix configuration.","No action is required."
"SME_CPP","2","LOG_ERR_SME_LICENSE_EXPIRED","SME License expired - Disabling [chars]","SAN Media Encryption License expired/not present - Disabling SME","No action is required."
"SME_CPP","2","LOG_ERR_SME_TAPE_LUN_PATH_MISCONFIG","Tape Drive [chars] behind Host PWWN [chars] Tgt PWWN [chars] LUN Id [chars] has some lun paths that are not configured.","A single lun with multiple paths has some non configured paths. Please configure all lun paths.","No action is required."
"SME_CPP","2","LOG_ERR_SME_TOM_ABORTED","SME Cluster [chars] Message Id: [hex] aborted","An SME Cluster Message was aborted by the Cluster process","No action is required."
"SME_CPP","2","LOG_WARN_SME_LICENSE_GRACE","No SME License. Feature will be shut down after a grace period of approximately [dec] days","SAN Media Encryption feature on grace period. Please acquire actual license.","No action is required."
"SME_CPP","2","SME_INIT_FAILED","Initialization failed for SME: [chars], Reason: [hex]","Initialization failed for SME","No action is required."
"SME_CPP","3","LOG_ERR_SME_DBSYBC_REJECT","SME Database Synchronization [chars] for a New Cluster (Id 0x%llx) Rejected; Reason - [chars].","A switch can be part of only one SME cluster","No action is required."
"ME_CPP","3","LOG_ERR_SME_DISK_DP_CNODE_NOT_FOUND","crypto disk data preparation for (DG: [chars] CD NAME: [chars]) could not find cnode ([chars] if_index: [hex])","The data preparation failed since crypto node assigned for data prepration is not found","No action is required."
"SME_CPP","3","LOG_ERR_SME_DISK_DP_CNODE_OVERLOAD","crypto disk data preparation for (DG: [chars] CD NAME: [chars]) could not be assgined a crypto node ([chars] if_index: [hex]) due to max limit. current active sessions: [dec]","The data preparation failed since crypto node is already handling maximum number of data preparation sessions","No action is required."
"SME_CPP","3","LOG_ERR_SME_DISK_KMC_NAME_MISMATCH","The KMC DG: [chars] and CD NAME: [chars] corresponding to VID: [chars] PID: [chars] DID: [chars] doesnt match cdisk DG: [chars] and CD NAME: [chars]","The discovered vendor id information not match the cryptodisk","No action is required."
"SME_CPP","3","LOG_ERR_SME_DISK_KMC_VPD_FIXED","The VPD of cdisk DG: [chars] CD NAME: [chars] has been changed to VPD in KMC VID: [chars] PID: [chars] DID: [chars] and old VPD of disk has been removed","The vendor id information has been modified to be consistent with KMC","No action is required."
"SME_CPP","3","LOG_ERR_SME_DISK_KMC_VPD_MISMATCH","The VID:[chars] PID:[chars] DID: [chars] of cdisk DG: [chars] CD NAME: [chars] does not match VPD in KMC VPD: [chars] PID: [chars] DID: [chars]","The discovered vendor id information not match the cryptodisk","No action is required."
"SME_CPP","3","LOG_ERR_SME_DISK_LUN_PATH_AUTH_FAIL1","ITL HPWWN: [chars] TPWWN: [chars] LUN Id: [chars] VPD mismatch disk. Disk VPD VID: [chars] PID: [chars] DID: [chars] ITL VID: [chars] PID: [chars] DID: [chars]","The given path does not belong to the configured disk","No action is required."
"SME_CPP","3","LOG_ERR_SME_DISK_LUN_PATH_AUTH_FAIL2","ITL HPWWN: [chars] TPWWN: [chars] LUN Id: [chars] VID: [chars] PID: [chars] DID: [chars] belongs to a different cdisk DG: [chars] CD NAME: [chars]","The given path does not belong to the configured disk","No action is required."
"SME_CPP","3","LOG_ERR_SME_DISK_LUN_PATH_AUTH_FAIL3","CFG ITL HPWWN: [chars] TPWWN: [chars] LUN Id: [chars] VID: [chars] PID: [chars] DID: [chars] doesnt belong to DG: [chars] CD NAME: [chars] whose VID: [chars] PID: [chars] DID: [chars]","The given path does not belong to the disk","No action is required."
"SME_CPP","3","LOG_ERR_SME_DISK_LUN_PATH_AUTH_FAIL4","CFG ITL HPWWN: [chars] TPWWN: [chars] LUN Id: [chars] of DG: [chars] CD: [chars] has VID: [chars] PID: [chars] DID: [chars] belonging to DG: [chars] CD NAME: [chars]","The given path does not belong to the disk","No action is required."
"SME_CPP","3","LOG_ERR_SME_INTF_MISMATCH_CLUSTER_PARAMS","SME interface [chars] part of cluster [chars] with ID [chars] and security mode [dec], but the DPP has state from a previous instance of a cluster [chars] with ID [chars] and security mode [dec].","DPP has persistent state about a previous cluster membership incarnation, but the interface is part of a different cluster.","No action is required."
"SME_CPP","3","LOG_ERR_SME_INTF_MISMATCH_CRYPTO_NODE_CERTIFICATE2","but the DPP has a different certificate (len [dec] fingerprint [chars]).","DPP has persistent state about a previous cluster membership with a different crypto node identity.","No action is required."
"SME_CPP","3","LOG_ERR_SME_INTF_MISMATCH_CRYPTO_NODE_CERTIFICATE","SME interface [chars] part of cluster [chars] with ID [chars] as a crypto node [chars] with certificate (len [dec] fingerprint [chars]), ..","DPP has persistent state about a previous cluster membership with a different crypto node identity.","No action is required."
"SME_CPP","3","LOG_ERR_SME_INTF_MISMATCH_CRYPTO_NODE_PARAMS","SME interface [chars] part of cluster [chars] with ID [chars] as a crypto node [chars], but the DPP is identified as [chars].","DPP has persistent state about a previous cluster membershipon a different switch or module.","No action is required."
"SME_CPP","3","LOG_ERR_SME_IT_NEX_USED_FOR_DP","IT CL: [chars] H: [chars] T: [chars] VSAN: [dec] has PATH lunid: [chars] for disk (dg: [chars] cd: [chars]) so rediscover not issued","The IT nexus is currently in use by data preparation so rediscover not permitted since it disrupts data preparation. Please stop data preparation first","No action is required."
"SME_CPP","3","LOG_SME_CDISK_DP_FAILED","SME cdisk ([chars]) data preparation failed ([chars]), disk-group ([chars]), cluster (name [chars], id %llx)","SME cdisk data preperation failed","No action is required."
"SME_CPP","3","LOG_SME_DISK_ASL_FAILED","[chars]","SME KMC disk asl token generation failed for the given device discovery info","No action is required."
"SME_CPP","3","LOG_SME_KEY_CREATE_FAILED","Key creation ([chars]) failed with error ([chars]), SME cluster (name [chars], id %llx)","SME key creation failed","No action is required."
"SME_CPP","3","LOG_SME_KMC_DELETE_ALL_KEYS_FAILED","Delete all keys in cluster failed to KMC server failed with error ([chars]), SME cluster (name [chars], id %llx)","SME KMC delete keys failed","No action is required."
"SME_CPP","3","LOG_SME_KMC_DELETE_KEYS_FAILED","Delete keys for [chars] failed to KMC server failed with error ([chars]), SME cluster (name [chars], id %llx)","SME KMC delete keys failed","No action is required."
"SME_CPP","3","LOG_SME_KMC_KEEPALIVE_FAILED","Keepalive to KMC server failed with error ([chars]), SME cluster (name [chars], id %llx)","SME KMC keepalive failed","No action is required."
"SME_CPP","3","LOG_SME_KMC_KEY_ENTITY_LOOKUP_FAILED","Key ([chars]) lookup from KMC server failed with error ([chars]), SME cluster (name [chars], id %llx)","SME KMC key lookup failed","No action is required."
"SME_CPP","3","LOG_SME_KMC_KEY_LOOKUP_FAILED","Key ([chars]) lookup from KMC server failed with error ([chars]), SME cluster (name [chars], id %llx)","SME KMC key lookup failed","No action is required."
"SME_CPP","3","LOG_SME_KMC_KEY_UPDATE_FAILED","Key updates ([chars]) to KMC server failed with error ([chars]), SME cluster (name [chars], id %llx)","SME KMC key updates failed","No action is required."
"SME_CPP","3","LOG_SME_KMC_MODIFY_DISK_STATUS_FAILED","Key ([chars]) update disk status in KMC server failed with error ([chars]), SME cluster (name [chars], id %llx)","SME KMC disk status update failed","No action is required."
"SME_CPP","3","LOG_SME_REPLACE_SMARTCARD_ABORT","Replace smartcard process (type [chars]) aborted [chars] with reason ([chars]) in SME cluster (name [chars], id %llx)","SME KMC connection up","No action is required."
"SME_CPP","3","SME_FIPS_MODE_ERROR","SME FIPS error: [chars]","SME module FIPS mode error","No action is required."
"SME_CPP","3","SME_MAX_CLUSTERS_LIMIT_EXCEEDED","SME maximum clusters limit of [dec] exceeded","The maximum sme clusters limit exceeded","No action is required."
"SME_CPP","5","IT_NEXUS_OPTIMUM_INTERFACE_LIMIT_REACHED","Interface [chars] exceeded the optimum IT Nexus limit","Iterface Flow Limit","No action is required."
"SME_CPP","5","LOG_ERR_SME_INTF_MISMATCH_NOT_PART_OF_ANY_CLUSTER","SME interface [chars] not part of any cluster, but the DPP has state from a previous instance of a cluster [chars] with ID [chars].","DPP has persistent state about a previous cluster membership incarnation, but the interface is not part of any cluster.","No action is required."
"SME_CPP","5","LOG_ERR_SME_INTF_MISMATCH_NOT_PROVISIONED","SME is not provisioned on slot [dec], but the DPP has state from a previous instance as a crypto node [chars] of a cluster [chars] with ID [chars].","DPP has persistent state about a previous cluster membership incarnation, but the switch has not provisioned the interface for SME.","No action is required."
"SME_CPP","5","LOG_SME_CDISK_DP_SUCCESS","SME cdisk ([chars]) data preparation succeeded, disk-group ([chars]), cluster (name [chars], id %llx)","SME cdisk data preperation succeeded","No action is required."
"SME_CPP","5","LOG_SME_CLUSTER_INTF_ADDED","SME interface now part of cluster [chars] with ID [chars] as a crypto node [chars] and certificate (len [dec] fingerprint [chars]).","Interface added to cluster successfully","No action is required."
"SME_CPP","5","LOG_SME_CLUSTER_INTF_REMOVED","SME interface now removed from cluster [chars] with ID [chars] as a crypto node [chars] and certificate (len [dec] fingerprint [chars]).","Interface removed from cluster successfully","No action is required."
"SME_CPP","5","LOG_SME_INTERFACE_DOWN","SME Interface ([chars]) DOWN","SAN Interface was brought down","No action is required."
"SME_CPP","5","LOG_SME_INTERFACE_UP","SME Interface ([chars]) is UP","SAN Interface was brought up","No action is required."
"SME_CPP","5","LOG_SME_IT_NEXUS_FAILURE","[chars]. [chars] bind failure. Reason: [chars]: [hex]","SME IT Nexus bind failed","No action is required."
"SME_CPP","5","LOG_SME_KEY_CREATE_SUCCESS","Key created ([chars]) successfully in SME cluster (name [chars], id %llx)","SME key creation succeeded","No action is required."
"SME_CPP","5","LOG_SME_KMC_CONNECTION_DOWN","Connection to KMC server [chars] is down with reason ([chars]) from local switch in SME cluster (name [chars], id %llx)","SME KMC connection down","No action is required."
"SME_CPP","5","LOG_SME_KMC_CONNECTION_INIT_FAIL","Connection initialization to KMC server [chars] from local switch in SME cluster (name [chars], id %llx) failed with error ([chars])","SME KMC connection initialization failed","No action is required."
"SME_CPP","5","LOG_SME_KMC_CONNECTION_INIT_PASS","Connection initialization to KMC server [chars] from local switch in SME cluster (name [chars], id %llx) succeeded","SME KMC connection initialization succeeded","No action is required."
"SME_CPP","5","LOG_SME_KMC_CONNECTION_UP","Connection to KMC server [chars] is up from local switch in SME cluster (name [chars], id %llx)","SME KMC connection up","No action is required."
"SME_CPP","5","LOG_SME_KMC_DELETE_ALL_KEYS_SUCCESS","Delete all keys in cluster to KMC server succeeded, SME cluster (name [chars], id %llx)","SME KMC delete keys succeeded","No action is required."
"SME_CPP","5","LOG_SME_KMC_DELETE_KEYS_SUCCESS","Delete keys for [chars] to KMC server succeeded, SME cluster (name [chars], id %llx)","SME KMC delete keys succeeded","No action is required."
"SME_CPP","5","LOG_SME_KMC_KEY_ENTITY_LOOKUP_NOKEY","Key ([chars]) lookup from KMC server failed with error ([chars]), SME cluster (name [chars], id %llx)","SME KMC key lookup resulted in no key","No action is required."
"SME_CPP","5","LOG_SME_KMC_KEY_ENTITY_LOOKUP_SUCCESS","Key ([chars]) lookup from KMC server succeeded, SME cluster (name [chars], id %llx)","SME KMC key lookup succeeded","No action is required."
"SME_CPP","5","LOG_SME_KMC_KEY_LOOKUP_SUCCESS","Key ([chars]) lookup from KMC server succeeded, SME cluster (name [chars], id %llx)","SME KMC key lookup succeeded","No action is required."
"SME_CPP","5","LOG_SME_KMC_KEY_UPDATE_SUCCESS","Key updates ([chars]) to KMC server succeeded, SME cluster (name [chars], id %llx)","SME KMC key updates succeeded","No action is required."
"SME_CPP","5","LOG_SME_KMC_MODIFY_DISK_STATUS_SUCCESS","Key ([chars]) update disk status in KMC server succeeded, SME cluster (name [chars], id %llx)","SME KMC disk status update succeeded","No action is required."
"SME_CPP","5","LOG_SME_MASTER_KEY_REKEYED","Master Key rekeyed successfully in SME cluster (name [chars], id %llx)","SME Master Key rekeyed","No action is required."
"SME_CPP","5","LOG_SME_REPLACE_SMARTCARD_COMMIT","Replace smartcard process (type [chars]) committed [chars] in SME cluster (name [chars], id %llx)","SME KMC connection up","No action is required."
"SME_CPP","5","LOG_SME_REPLACE_SMARTCARD_START","Replace smartcard process (type [chars]) initiated [chars] in SME cluster (name [chars], id %llx)","SME KMC connection up","No action is required."
"SME_CPP","5","LOG_SME_TAPE_VOLUME_GROUP_REKEYED","Tape volume group ([chars]) rekeyed successfully in SME cluster (name [chars], id %llx)","SME Master Key rekeyed","No action is required."
"SME_CPP","5","SME_DISABLED","SME Disabled","SME Service Disabled","No action is required."
"SME_CPP","5","SME_DISK_DP_WAIT_KMC","crypto disk data preparation (DG: [chars] CD NAME: [chars]) is waiting KMC validation of VPD","The data preparation is waiting for validation of VPD with KMC","No action is required."
"SME_CPP","5","SME_DISK_DP_WAIT_PATH_ADD","crypto disk data preparation (DG: [chars] CD NAME: [chars]) is waiting paths to be added","The data preparation is waiting for paths to be added to the crypto disk","No action is required."
"SME_CPP","5","SME_DISK_DP_WAIT_PATH_CFG","crypto disk data preparation (DG: [chars] CD NAME: [chars]) is waiting for the path (fabric: [chars] hwwn: 0x%Lx twwn: 0x%Lx vsan: [dec] lun_id: [chars]) to be added","The data preparation is waiting for discovered path to be added","No action is required."
"SME_CPP","5","SME_DISK_DP_WAIT_PATH_DISC","(DG: [chars] CD NAME: [chars]) is waiting for configured path (fabric: [chars] hwwn: 0x%Lx twwn: 0x%Lx vsan: [dec] lun_id: [chars]) to be discovered","The data preparation is waiting for configured path to be discovered","No action is required."
"SME_CPP","5","SME_ENABLED","SME Enabled","SME Service nabled","No action is required."
"SME_CPP-SLOT#","2","LOG_ERR_SME_DEVICE_MISCONFIG","Different configured Devices under same physical LUN - Old Cluster Name:[chars] New Cluster Name:[chars] Old Group Name:[chars] New Group Name:[chars] Old Device Name:[chars] New Device Name:[chars]","Different configured devices under same physical LUN","No action is required."
"SME_CPP-SLOT#","2","LOG_ERR_SME_ITL_MISCONFIG","Different physical LUNs under same Tape Device - Device Name:[chars] Host PWWN:[chars] Tgt PWWN:[chars] LUN Id:[chars] Serial Num:[chars] Serial Num:[chars]","Different physical LUNs under same Tape Device","No action is required."
"SME_CPP-SLOT#","2","LOG_ERR_SME_LUN_MISCONFIG","Different physical LUNs under same ITL - Old Serial Num:[chars] New Serial Num:[chars]","Different physical LUNs under same ITL","No action is required."
"SME_CPP-SLOT#","2","LOG_ERR_SME_TAPE_BYPASS_ENC","Bypassing encryption for partly written tape - Cluster:[chars] Tape Device:[chars] Serial Num:[chars]","This tape is currently not being encrypted","No action is required."
"SME_CPP-SLOT#","2","LOG_ERR_SME_TAPE_CTH_FAIL","Bypassing encryption for current tape on failed CTH verification - Cluster:[chars] Tape Device:[chars] Serial Num:[chars]","This tape is currently not being encrypted because CTH verification has failed in DPP","No action is required."
"SME_CPP-SLOT#","2","LOG_ERR_SME_TAPE_KEY_ERR","Getting tape keys from SUP failed - Cluster:[chars] Tape Device:[chars] Serial Num:[chars]","There was a failure retrieving keys from SUP for this tape","No action is required."
"SME_CPP-SLOT#","3","LOG_ERR_SME_DISC_TIMEOUT","Module:[dec] Host-Target:[chars]","Discovery on this IT Nexus is taking too long, please check status","No action is required."
"SME_CPP-SLOT#","3","LOG_ERR_SME_DISK_CAP_CHANGED","capacity changed for lun VID: [chars] PID: [chars] DID: [chars] previous max_lba: 0x%Lx blk_sz: [dec] discovered max_lba: [hex] blk_sz: [dec] on ITL Host PWWN:[chars] Tgt PWWN:[chars] LUN Id:0x%Lx","The capacity of the disk seems to have changed","No action is required."
"SME_CPP-SLOT#","3","LOG_ERR_SME_DISK_CPP_ITL_MISCONFIG","Disk ITL Host PWWN:[chars] Tgt PWWN:[chars] LUN Id:0x%Lx has been misconfigured under a non disk lun","Disk ITL has been misconfigured under non disk lun","No action is required."
"SME_CPP-SLOT#","3","LOG_ERR_SME_DISK_CPP_IT_MISCONFIG","Tape device has been misconfigured under disk IT nexus [chars] hence skipping discovery of ITLs under this IT nexus","Remove misconfigured disk path under the tape device","No action is required."
"SME_CPP-SLOT#","3","LOG_ERR_SME_DISK_CRYPTO_UPDATE_ITL_AUTH_FAIL","ITL Host PWWN:[chars] Tgt PWWN:[chars] LUN Id:0x%Lx with discovered VID: [chars] PID: [chars] DID: [chars] marked by SUP as failed authentication","SUP detected authentication failure on path","No action is required."
"SME_CPP-SLOT#","3","LOG_ERR_SME_DISK_ENTITY_INVALID","disk entity index invalid from KMC (cluster: [chars] DG: [chars] CD NAME: [chars] VID: [chars] PID: [chars] DID: [chars]","KMC returned an invalid disk entity index","No action is required."
"SME_CPP-SLOT#","3","LOG_ERR_SME_DISK_INVALID_CAPACITY","Disk capacity not supported.IT nexus:[chars] LUN Id:0x%Lx VID: [chars] PID : [chars] max_lba=[hex] max_lba64=0x%Lx","The reported disk capacity is zero","No action is required."
"SME_CPP-SLOT#","3","LOG_ERR_SME_DISK_ITL_CREATE_VPD_MISMATCH","ITL Host PWWN:[chars] Tgt PWWN:[chars] LUN Id:0x%Lx VID: [chars] PID: [chars] DID: [chars] doesnt match cdisk DG: [chars] CD NAME: [chars] VID: [chars] PID: [chars] DID: [chars]","The configured path does not belong to this disk","No action is required."
"SME_CPP-SLOT#","3","LOG_ERR_SME_DISK_ITL_MISCONFIG","ITL Host PWWN:[chars] Tgt PWWN:[chars] LUN Id:0x%Lx part of DG: [chars] CD NAME: [chars] is misconfigured as the ITL VPD VID: [chars] PID: [chars] DID: [chars] belongs to a different cdisk DG: [chars] CD NAME: [chars]","The configured path does not belong to this disk","No action is required."
"SME_CPP-SLOT#","3","LOG_ERR_SME_DISK_KEY_INVALID","(CLUSTER: [chars] DG: [chars] CD NAME: [chars] keytype: [dec] keyguid: [chars] invalid","KMC returned an invalid disk key","No action is required."
"SME_CPP-SLOT#","3","LOG_ERR_SME_DISK_KMC_VERIFY_PENDING","cluster: [chars] DG: [chars] CD NAME: [chars] VID: [chars] PID: [chars] DID: [chars]","Vpd of the discovered path pending verification with KMC","No action is required."
"SME_CPP-SLOT#","3","LOG_ERR_SME_DISK_MISCONFIG","A disk device misconfiguration under disk config - Device Name:[chars] Host PWWN:[chars] Tgt PWWN:[chars] LUN Id:%Lx","A disk device misconfigured under disk config","No action is required."
"SME_CPP-SLOT#","3","LOG_ERR_SME_DISK_PHYENCRYPT_FAILED","CL: [chars] DG: [chars] CD: [chars] VID: [chars] PID: [chars] DID: [chars] ISAPI_PhyCopyEncrypt() failed isapi status: [dec] copy status: [hex] scsi status: [hex] data preparation failed","ISAPI_PhyCopyEncrypt() failed causing data preparation to fail","No action is required."
"SME_CPP-SLOT#","3","LOG_ERR_SME_DISK_VPD_CHANGED","VID, PID and DID changed on ITL Host PWWN:[chars] Tgt PWWN:[chars] LUN Id:0x%Lx previous VID: [chars] PID : [chars] DID: [chars] current VID: [chars] PID: [chars] DID: [chars]","The VPD of the disk seems to have changed","No action is required."
"SME_CPP-SLOT#","3","LOG_ERR_SME_DISK_VPD_MISMATCH","ITL Host PWWN:[chars] Tgt PWWN:[chars] LUN Id:0x%Lx failed authentication DISK VPD(VID id: [chars] PID: [chars] DID: [chars]) ITL(VID: [chars] PID: [chars] DID: [chars])","The configured path does not belong to this disk","No action is required."
"SME_CPP-SLOT#","3","LOG_ERR_SME_DP_TEST_IO_ERR","IT nexus [chars] lun [chars] isapi [hex] scsi [hex] sense/asc/ascq [hex]/[hex]/[hex]","ITL DP TEST IO failure, please check status","No action is required."
"SME_CPP-SLOT#","3","LOG_ERR_SME_ITL_CPP_ERR","Module:[dec] Host-Target [chars] LunID:[chars]","ITL failure seen on CPP, please check status","No action is required."
"SME_CPP-SLOT#","3","LOG_ERR_SME_IT_NEXUS_UNSUPPORTED","IT nexus [chars] has both disks and tapes which is an unsupported configuration","IT nexus has an unsupported mix of tape and disk devices","No action is required."
"SME_CPP-SLOT#","3","LOG_ERR_SME_NON_DISK_MISCONFIG","A non-disk device misconfigured under disk config - Host PWWN:[chars] Tgt PWWN:[chars] LUN Id:%Lx","A non disk device misconfigured under disk config","No action is required."
"SME_CPP-SLOT#","3","LOG_ERR_SME_NON_TAPE_MISCONFIG","A non-tape device misconfigured under tape config - Device Name:[chars] Host PWWN:[chars] Tgt PWWN:[chars] LUN Id:%Ld","A disk misconfigured under tape config","No action is required."
"SME_CPP-SLOT#","4","LOG_WARN_SME_MAX_BLOCK_LEN","Maximum block length [dec] of tape drive is 256K or less - [chars] LunID:[chars] VendorID:[chars] ProdID:[chars] Serial Num:[chars] Cluster:[chars] Tape Device:[chars]","This tape drive may not operate correctly with SME","No action is required."
"SNMPD","1","ALERT","SNMP log alert : [chars]","SNMP log alert message.","No action is required."
"SNMPD","2","CRITICAL","SNMP log critical : [chars]","SNMP log critical message.","No action is required."
"SNMPD","3","ERROR","SNMP log error : [chars]","SNMP log error message.","No action is required."
"SNMPD","4","WARNING","SNMP log warning : [chars]","SNMP log warning message.","No action is required."
"SNMPD","5","NOTIFICATION","SNMP log notification : [chars]","SNMP log notification message.","No action is required."
"SNMPD","6","INFO","SNMP log informational : [chars]","SNMP log info message.","No action is required."
"SNMPD","7","DEBUG","SNMP log debugging : [chars]","SNMP log debug message.","No action is required."
"SPAN","2","MEM_FULL","Memory allocation failed","Memory allocation failed","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SPAN","3","IPC_FAIL","IPC Error","Internal IPC error","No action is required."
"SPAN","3","SYSINFO_TIMEOUT","Span timed out waiting for response from port manager for sys info","Span request for critical system information from port manager timed out. So, span on the new active is exiting and system manager will restart Span.","No action is required."
"SPAN","5","ATL_VSAN_DEFAULT_ALL","Default to all VSANs for SPAN egress session","Generation 2 fabric switches support only one VSAN filter for egress SPAN session. If no or more than one VSANs are specified, SPAN will default to use all VSANs for the egress SPAN session","No action is required."
"SPAN","5","SPAN_CFG_REJECT_SRC_VSAN_FILTER_NOT_SUPPORTED","Source interface [[chars]] in dir [[chars]] removed from session [[dec]].","Interface level VSAN filters is not supported","No action is required."
"SPAN","5","SPAN_CFG_REJECT_VSAN_SRC_PRESENT","Source VSAN [[dec]] removed from session [[dec]].","Source VSANs are removed from the session as mixing of interface and VSANs is not supported.","No action is required."
"SPAN","5","SPAN_PSS_CORRUPTION","Span is starting stateless due to PSS corruption","Due to unrecoverable PSS corruption error, SPAN starts stateless without any configuration","No action is required."
"SPAN","5","STATELESS_RESTART_ON_ACTIVE","Span is restarting as Span on active sup was restarted stateless.","Due to unrecoverable error, Span on active supervisor was restarted stateless. So, the standby Span restarts to get in sync with the stateless Span on active.","No action is required."
"SPAN","5","STATELESS_RESTART","Span is restarting stateless.","Due to unrecoverable error, Span is starting stateless. The currently active sessions will not be preserved. The user will have to reenter all the configuration.","No action is required."
"SPAN","6","SESSION_DOWN","Session [dec] is inactive ([chars])","Session [dec] is inactive now. Traffic for this session is no longer spanned","Check the reason for session inactive using command showspansession'andtakecorrespondingaction.'"
"SPAN","6","SESSION_UP","Session [dec] is active, destination SD port [chars]","Session [dec] is active now. You can monitor Spanned traffic at the destination SD port","No action is required."
"SPAN","6","STATELESS_SWITCHOVER","Span is starting stateless after switchover.","Active sessions are not preserved across switchover. Span is starting stateless and the configuration will be reapplied to get back the active configuration.","No action is required."
"SPI-SLOT#","2","SPI_INFO","[chars]","SPI Informational message","No action is required."
"STATSCLIENT","2","STATSCL_CRIT","[chars]","StatsClient Critical Message","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"STATSCLIENT","3","STATSCL_ERR2","[chars] [dec] [dec]","StatsClient Error","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"STATSCLIENT","3","STATSCL_ERR","[chars] [dec]","StatsClient Error","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"STATSCLIENT","6","STATSCL_INFO","[chars]","StatsClient Flow MessagePlease contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support.STATSINFRA MessagesThis section contains the STATSINFRA messages.STATSINFRA-3Error Message    STATSINFRA-3-STATS_INFRA_CRIT: [chars] Explanation    StatsInfra Critical Message","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"STATSINFRA","3","STATS_INFRA_ERR","[chars]","StatsInfra Error","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"STATSINFRA","3","STATS_INFRA_INFO","[chars]","StatsInfra Flow Message","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"STATSPROFILER","2","IF_CRITICAL_FAILURE","(Debug syslog)Critical failure: [chars], [chars]","There was a critical failure in the component.","Please follow instructions on the syslog."
"STATSPROFILER","2","IF_DOWN_ERROR_DISABLED","Interface [chars] is down (Error disabled. Reason:[chars])","The interface encountered an error while configuring it","Collect more information about failed interface using command showportinternalallinterface[char]'.Inmostcases,youcanrecoverusinga'shutdown'followeda'noshutd own'ontheinterfaceorremovingandre-insertingthefibreopticcable.'"
"STATSPROFILER","2","IF_DOWN_LINK_FAILURE_CRIT","Interface [chars] is down (Link failure)","The physical link has gone down","Ensure that the cable is connected and the remote end is not shut down"
"STATSPROFILER","2","SEQ_TIMEOUT","Component [chars] timed out on response to opcode [chars] ([chars])","Some component did not respond to a request in stipulated time.","None"
"STATSPROFILER","2","SYSLOG_STATSPROFILER_CRITICAL","Critical failure: [chars]","There was a critical failure in the component.","Please collect system tech-support"
"STATSPROFILER","3","IF_DOWN_CHANNEL_ERR_DISABLED","Interface [chars] is down (Channel error disabled)","This interface belongs to a PortChannel and the PortChannel is error disabled","Perform shut'and'noshutdown'onthePortChannelinterfacethatitbelongsto'"
"STATSPROFILER","3","IF_ERROR_VLANS_REMOVED","VLANs [chars] on Interface [chars] are removed from suspended state.","The VLANs on an interface are being removed from the suspended state","No action is required."
"STATSPROFILER","3","IF_ERROR_VLANS_SUSPENDED","VLANs [chars] on Interface [chars] are being suspended. (Reason: [chars])","The VLANs on an interface are being suspended due to some protocol action","No action is required."
"STATSPROFILER","3","IF_SFP_ALARM","Interface [chars], [chars]","There was an alarm on the transceiver module","Please do show interface transceiver details to obtain more information"
"STATSPROFILER","3","IF_SFP_ERROR","Interface [chars], [chars]","There was an error on the transceiver module","Please do show interface transceiver details to obtain more information"
"STATSPROFILER","3","IF_UNSUPPORTED_TRANSCEIVER","Transceiver on interface [chars] is not supported","The transceiver for the interface specified in the error message is not a Cisco supported module","Replace the module with a compatible transceiver. If the transceiver was purchased from Cisco, please contact Cisco TAC to get the transceiver replaced"
"STATSPROFILER","3","IF_XCVR_ALARM","Interface [chars], [chars]","There was an alarm on the transceiver module","Please do show interface transceiver details to obtain more information"
"STATSPROFILER","3","IF_XCVR_ERROR","Interface [chars], [chars]","There was an error on the transceiver module","Please do show interface transceiver details to obtain more information"
"STATSPROFILER","4","IF_NON_QUALIFIED_TRANSCEIVER","Non-qualified transceiver on interface [chars] was detected","The transceiver for the interface specified has not been qualified on this platform for this software release","Replace the module with a supported transceiver. Contact Cisco TAC to get platform transceiver qualification details"
"STATSPROFILER","4","IF_SFP_WARNING","Interface [chars], [chars]","There was an warning on the transceiver module","Please do show interface transceiver details to obtain more information"
"STATSPROFILER","4","IF_XCVR_WARNING","Interface [chars], [chars]","There was an warning on the transceiver module","Please do show interface transceiver details to obtain more information"
"STATSPROFILER","5","IF_ADMIN_UP","Interface [chars] is admin up [chars]","Interface is admin up","No action is required."
"STATSPROFILER","5","IF_BANDWIDTH_CHANGE","Interface [chars],bandwidth changed to [chars] Kbit","Bandwidth of the interface (port channel) has changed and this change is updated","No action is required."
"STATSPROFILER","5","IF_DOWN_ADMIN_DOWN","Interface [chars] is down (Administratively down)","Interface has been configured to be administratively down","Perform noshutdown''"
"STATSPROFILER","5","IF_DOWN_CFG_CHANGE","Interface [chars] is down(Config change)","FCIP interface temporarily down due to reconfiguration","No action is required."
"STATSPROFILER","5","IF_DOWN_CHANNEL_ADMIN_DOWN","Interface [chars] is down (Channel admin down)","This interface belongs to a PortChannel and the PortChannel is configured to be administratively down","Perform noshutdown'onthePortChannelinterfacethatitbelongsto'"
"STATSPROFILER","5","IF_DOWN_CHANNEL_MEMBERSHIP_UPDATE_IN_PROGRESS","Interface [chars] is down (Channel membership update in progress)","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","Retry the configuration again"
"STATSPROFILER","5","IF_DOWN_DOMAIN_ADDR_ASSIGN_FAILURE_ISOLATION","Interface [chars] is down (Isolation due to domain id assignment failure)","Isolated due to a failure while assigning a domain","No action is required."
"STATSPROFILER","5","IF_DOWN_DOMAIN_INVALID_RCF_RECEIVED","Interface [chars] is down (Isolation due to invalid fabric reconfiguration)","Invalid RCF received","No action is required."
"STATSPROFILER","5","IF_DOWN_DOMAIN_MANAGER_DISABLED","Interface [chars] is down (Isolation due to domain manager disabled)","Isolated due to domain manager being disabled","No action is required."
"STATSPROFILER","5","IF_DOWN_DOMAIN_MAX_RETRANSMISSION_FAILURE","Interface [chars] is down (Isolation due to domain manager other side not responding)","Remote end domain manager not responding","No action is required."
"STATSPROFILER","5","IF_DOWN_DOMAIN_OTHER_SIDE_EPORT_ISOLATED","Interface [chars] is down (Isolation due to domain other side eport isolated)","Isolating this interface due to the remote end being isolated","No action is required."
"STATSPROFILER","5","IF_DOWN_DOMAIN_OVERLAP_ISOLATION","Interface [chars] is down (Isolation due to domain overlap)","Isolated due to domain overlap","No action is required."
"STATSPROFILER","5","IF_DOWN_ELP_FAILURE_ISOLATION","Interface [chars] is down (Isolation due to ELP failure)","ELP failed on the interface","Check the output of showportinternalinfo'inthe'ELPfailurereason'field'"
"STATSPROFILER","5","IF_DOWN_EPP_FAILURE","Interface [chars] is down (Error Disabled - EPP Failure)","Trunk protocol failed","showportinternalevent-historymsgs'willindicatethetrunkprotocolexchangestodeterminewhyitfailed'"
"STATSPROFILER","5","IF_DOWN_ESC_FAILURE_ISOLATION","Interface [chars] is down (Isolation due to ESC failure)","ESC failed on the interface","Check the output of showportinternalevent-history'todeterminetheESCprotocolexchangestodeterminehowitfailed'"
"STATSPROFILER","5","IF_DOWN_ETH_IF_DOWN","Interface [chars] is down(Tunnel port src interface down)","Ethernet link to which the FCIP interface is bound is down","Ensure that the ethernet cable is connected, the interface is administratively enabled"
"STATSPROFILER","5","IF_DOWN_ETH_LINK_DOWN","Interface [chars] is down(Tunnel port src interface link down)","Ethernet link to which the FCIP interface is bound is down","Ensure that the ethernet cable is connected and the remote end is also active"
"STATSPROFILER","5","IF_DOWN_FCOT_NOT_PRESENT","Interface [chars] is down (FCOT not present)","The FCOT has been removed","Insert an FCOT"
"STATSPROFILER","5","IF_DOWN_FCOT_VENDOR_NOT_SUPPORTED","Interface [chars] is down (Error disabled - Fcot vendor not supported)","Fcot inserted is not a supported one","Please contact customer support for a list of authorized transceiver vendors"
"STATSPROFILER","5","IF_DOWN_HW_FAILURE","Interface [chars] is down (Hardware Failure)","The moduleshardwarehasfailed'","Collect more information about failed module using command showmoduleinternalallmodule''"
"STATSPROFILER","5","IF_DOWN_INACTIVE","Interface [chars] is down (Inactive)","The port VSAN has been suspended or deleted","Assign a new active port VSAN to the interface"
"STATSPROFILER","5","IF_DOWN_INCOMPATIBLE_ADMIN_MODE","Interface [chars] is down (Error disabled - Incompatible admin port mode)","The configured mode is not supported on this interface","Perform a showportinternalinfo'todeterminethelistofmodessupportedonthisinterface'"
"STATSPROFILER","5","IF_DOWN_INCOMPATIBLE_ADMIN_RXBBCREDIT","Interface [chars] is down (Error disabled - Incompatible admin port rxbbcredit)","The configured receive B2B credit size is not supported","Get the allowed receive B2B credit size from showportinternalinfo''"
"STATSPROFILER","5","IF_DOWN_INCOMPATIBLE_ADMIN_RXBUFSIZE","Interface [chars] is down (Error disabled - Incompatible admin port rxbufsize)","The configured receive buffer size is not supported","Get the allowed receive buffer size from showportinternalinfo''"
"STATSPROFILER","5","IF_DOWN_INCOMPATIBLE_ADMIN_SPEED","Interface [chars] is down (Error disabled - Incompatible admin port speed)","The configured speed is not supported on this interface","Perform a showportinternalinfo'todeterminetherangeofspeedsupportedonthisinterface'"
"STATSPROFILER","5","IF_DOWN_INITIALIZING","Interface [chars] is down (Initializing)","The interface is in the process of coming up","If the interface is stuck in this state for a while, check the output of showportinternalevent-history'todeterminewhatitiswaitingfor'"
"STATSPROFILER","5","IF_DOWN_INTERFACE_REMOVED","Interface [chars] is down (Interface removed)","Interface removed","No action is required."
"STATSPROFILER","5","IF_DOWN_LINK_FAILURE","Interface [chars] is down (Link failure)","The physical link has gone down","Ensure that the cable is connected and the remote end is not shut down"
"STATSPROFILER","5","IF_DOWN_LOOPBACK_DIAG_FAILURE","Interface [chars] is down (Diag failure)","Diag failed on the interface","Collect more information about failed interface using command attachmodule'toconnecttomodule'"
"STATSPROFILER","5","IF_DOWN_LOOPBACK_ISOLATION","Interface [chars] is down (Isolation due to port loopback to same switch)","The interface is looped back to another interface on the same switch","Check the connectivity of this interface and ensure that it is connected to another switch"
"STATSPROFILER","5","IF_DOWN_MODULE_REMOVED","Interface [chars] is down (module removed)","Interface is down because the module was removed","No action is required."
"STATSPROFILER","5","IF_DOWN_NONE","Interface [chars] is down ([chars])","Interface is down with a possible reason.","Collect more information about port using command showportinternalinfo/event-history'todeterminewhyitwentdown'"
"STATSPROFILER","5","IF_DOWN_NON_PARTICIPATING","Interface [chars] is down (Non participating)","The loop port has been put into non participating mode","No action is required."
"STATSPROFILER","5","IF_DOWN_OFFLINE","Interface [chars] is down (Offline)","The interface has been placed into the offline state","No action is required."
"STATSPROFILER","5","IF_DOWN_PARENT_ADMIN_DOWN","Interface [chars] is down (Parent interface down)","Parent interface is down","No action is required."
"STATSPROFILER","5","IF_DOWN_PEER_CLOSE","Interface [chars] is down(TCP conn. closed by peer)","The FCIP peer connected to this interface closed the TCP connection","This command will provide the peer IP address of this FCIP interface: show interface. Check to see why the peer closed the TCP connection"
"STATSPROFILER","5","IF_DOWN_PEER_RESET","Interface [chars] is down(TCP conn. reset by peer)","TCP connection to the FCIP peer got reset","The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Check to see why the peer reset the TCP connection"
"STATSPROFILER","5","IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN","Interface [chars] is down (No operational members)","This is a PortChannel interface and all its members are operationally down","Enable at least one of the PortChannelsmembers'"
"STATSPROFILER","5","IF_DOWN_PORT_VSAN_MISMATCH_ISOLATION","Interface [chars] is down (Isolation due to port vsan mismatch)","Isolated due to a mismatch in the configured port VSAN of the local and remote ends","Configure the port VSAN of the local and remote interfaces to be the same and perform a shutdown'anda'noshutdown''"
"STATSPROFILER","5","IF_DOWN_RCF_IN_PROGRESS","Interface [chars] is down (RCF in progress)","There is an RCF in progress","No action is required."
"STATSPROFILER","5","IF_DOWN_SOFTWARE_FAILURE","Interface [chars] is down (Port software failure)","The software servicing the data path on the port has failed","No action is required."
"STATSPROFILER","5","IF_DOWN_SRC_MOD_NOT_ONLINE","Interface [chars] is down(Tunnel source module not online)","Module that has the tunnel source port of this FCIP interface is not fully online","The module that has the tunnel src port is coming online. Please use show mod to find module status"
"STATSPROFILER","5","IF_DOWN_SRC_PORT_NOT_BOUND","Interface [chars] is down (Tunnel port src interface unbound)","Tunnel port source interface unbound","No action is required."
"STATSPROFILER","5","IF_DOWN_SRC_PORT_REMOVED","Interface [chars] is down(Tunnel src port removed)","Tunnel source port of this FCIP interface has been removed","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"
"STATSPROFILER","5","IF_DOWN_SUSPENDED_BY_MODE","Interface [chars] is down (Suspended due to incompatible mode)","This interface belongs to a PortChannel and operational mode of the interface is different from that of the PortChannel","Change the mode and the trunking mode of the PortChannel from auto'andchecktoensurethattheremoteendoftheinterfacealsobelongstothesamePortChannel'"
"STATSPROFILER","5","IF_DOWN_SUSPENDED_BY_SPEED","Interface [chars] is down (Suspended due to incompatible speed)","This interface belongs to a PortChannel and operational speedode of the interface is different from that of the PortChannel","Change the speed of the PortChannel from auto'andchecktoensurethattheremoteendoftheinterfacealsobelongstothesamePortChannel'"
"STATSPROFILER","5","IF_DOWN_SUSPENDED_BY_WWN","Interface [chars] is down (Suspended due to incompatible remote switch WWN)","This interface belongs to a PortChannel and remote switch WWN of the interface is different from that of the PortChannel","Ensure that this interface is connected to the same remote switch as all the other interfaces in the PortChannel"
"STATSPROFILER","5","IF_DOWN_SUSPENDED","Interface [chars] is down (Suspended)","This interface belongs to a PortChannel and has been suspended due to an error while bringing it up","Perform a shutdown'anda'noshutdown'.Ifthishappensagainobtainoutputof'showportinternalinfo/event-history' ontheinterface'"
"STATSPROFILER","5","IF_DOWN_TCP_KEEP_ALIVE_EXPIRED","Interface [chars] is down(TCP conn. closed - Keep alive expired)","TCP session to the FCIP peer got closed due to loss of TCP keep alive","This may be due to loss of IP connectivity. The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Please do a trace route to check the connectivity to the peer using command:traceroute ipaddr"
"STATSPROFILER","5","IF_DOWN_TCP_MAX_RETRANSMIT","Interface [chars] is down(TCP conn. closed - retransmit failure)","Interface is down due to maximum retransmission failure","This may be due to loss of IP connectivity. The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Please do a trace route to check the connectivity to the peer using command:traceroute ipaddr"
"STATSPROFILER","5","IF_DOWN_TCP_PERSIST_TIMER_EXPIRED","Interface [chars] is down(TCP conn. closed - Persist timer expired)","TCP session to the FCIP peer closed because TCP persist timer expired","This may be due to loss of IP connectivity. The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Please do a trace route to check the connectivity to the peer using command:traceroute ipaddr"
"STATSPROFILER","5","IF_DOWN_UPGRADE_IN_PROGRESS","Interface [chars] is down (Linecard upgrade in progress)","Upgrade of the linecard software is in progress","No action is required."
"STATSPROFILER","5","IF_DOWN_VRF_UNUSABLE","Interface [chars] is down (Vrf down)","The vrf for which this interface is a member is removed","No action is required."
"STATSPROFILER","5","IF_DOWN_VSAN_MISMATCH_ISOLATION","Interface [chars] is down (Isolation due to vsan mismatch)","This is a trunking interface and the VSANs configured do not match with the VSANs configured on the remote end","Check the VSANs configured on the local end with the remote end"
"STATSPROFILER","5","IF_DOWN_ZONE_MERGE_FAILURE_ISOLATION","Interface [chars] is down (Isolation due to zone merge failure)","Isolated due to a failure during zone merge","No action is required."
"STATSPROFILER","5","IF_DOWN_ZONE_REMOTE_NO_RESP_ISOLATION","Interface [chars] is down (Isolation due to remote zone server not responding)","Isolated due to remote zone server not responding","No action is required."
"STATSPROFILER","5","IF_DUPLEX","Interface [chars], operational duplex mode changed to [chars]","Operational duplex mode has changed when link came up","No action is required."
"STATSPROFILER","5","IF_ERRDIS_RECOVERY","Interface [chars] is being recovered from error disabled state (Last Reason:[chars])","Interface is being recovered from error disabled state","No action is required."
"STATSPROFILER","5","IF_HARDWARE","Interface [chars], hardware type changed to [chars]","There was a change in the hardware characteristic of an interface, such as a transceiver module plugged in or removed","No action is required."
"STATSPROFILER","5","IF_L2MP_MODE","Interface [chars], l2mp-mode changed to [chars]","The l2mp-mode on the port has changed","No action is required."
"STATSPROFILER","5","IF_RX_FLOW_CONTROL","Interface [chars], operational Receive Flow Control state changed to [chars]","Operational receive flow control has changed when link came up","No action is required."
"STATSPROFILER","5","IF_TRUNK_DOWN","Interface [chars], vlan [chars] down","Interface [chars] is trunking, VLANs [chars] are down","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"
"STATSPROFILER","5","IF_TRUNK_UP","Interface [chars], vlan [chars] up","Interface [chars] is trunking, VLANs [chars] are up","No action is required."
"STATSPROFILER","5","IF_TX_FLOW_CONTROL","Interface [chars], operational Transmit Flow Control state changed to [chars]","Operational transmit flow control has changed when link came up","No action is required."
"STATSPROFILER","5","IF_UP","Interface [chars] is up [chars]","Interface is up in mode specified, if applicable","No action is required."
"STATSPROFILER","5","SPEED","Interface [chars], operational speed changed to [chars]","Operational speed has changed when link came up","No action is required."
"STATSPROFILER","5","STORM_CONTROL_ABOVE_THRESHOLD","Traffic in port [chars] exceeds the configured threshold [chars]","Traffic on specified port is beyond the configured storm-control threshold, and the excess traffic is being dropped","Identify source of traffic storm"
"STATSPROFILER","5","STORM_CONTROL_BELOW_THRESHOLD","Traffic in port [chars] has fallen below the configured threshold [chars]","Traffic on specified port has returned to within configured storm-control threshold","No action is required."
"STP","2","BLOCK_BPDUGUARD","Received BPDU on port [chars] with BPDU Guard enabled. Disabling port.","A BPDU was received in the interface specified in the error message that has the spanning tree BPDU Guard feature enabled. As a result, the interface was administratively shut down.","Either remove the device sending BPDUs or disable the BPDU Guard feature. The BPDU Guard feature can be locally configured on the interface or globally configured on all ports that have portfast enabled. After the conflict has been resolved, re-enable the interface by entering the <CmdBold"
"STP","2","BLOCK_DETECTED_PVST_PEER","Blocking port [chars] [PVST peer detected].","The listed interface received SSTP BPDU indicating that peer is running PVST and will be held in spanning tree blocking state until the interface stops receiving SSTP BPDUs","Either enable PVST simulation configuration for the interface or make sure the port peer is not PVST switch"
"STP","2","BLOCK_PVID_LOCAL","Blocking [chars] on [chars]. Inconsistent local vlan.","The spanning tree port associate with the listed spanning tree instance and interface will be held in spanning tree blocking state until the Port VLAN ID (PVID) inconsistency is resolved. The listed spanning tree instance is that of the native VLAN id of the listed interface.","Verify that the configuration of the native VLAN id is consistent on the interfaces on each end of the 802.1Q trunk connection. Once corrected, spanning tree will automatically unblock the interfaces as appropriate."
"STP","2","BLOCK_PVID_PEER","Blocking [chars] on [chars]. Inconsistent peer vlan.","The spanning tree port associate with the listed spanning tree instance and interface will be held in spanning tree blocking state until the port VLAN Id (PVID) inconsistency is resolved. The listed spanning tree instance is that of the native VLAN id of interface on the peer switch to which the listed interface is connected.","Verify that the configuration of the native VLAN id is consistent on the interfaces on each end of the 802.1Q trunk connection. Once corrected, spanning tree will automatically unblock the interfaces as appropriate."
"STP","2","BRIDGE_ASSURANCE_BLOCK","Bridge Assurance blocking port [chars] [chars].","BPDUs were not received from a neighboring switch on the interface that has spanning tree Bridge Assurance configured. As a result, the interface was moved to the spanning tree Blocking state","LOG_STD_NO_ACTION"
"STP","2","BRIDGE_ASSURANCE_UNBLOCK","Bridge Assurance unblocking port [chars] [chars].","The interface listed in the message has been restored to normal spanning tree state after receiving BPDUs from the neighboring L2 switch/bridge","LOG_STD_NO_ACTION"
"STP","2","DISPUTE_CLEARED","Dispute resolved for port [chars] on [chars].","The listed interface has stopped receiving Inferior BPDUs with designated role and state as learning and/or forwarding. The Dispute has been resolved and if the port is still designated, it will be taken out of the blocking state as and when appropriate.","LOG_STD_NO_ACTION"
"STP","2","DISPUTE_DETECTED","Dispute detected on port [chars] on [chars].","The spanning tree has detected a Dispute on this interface. The BPDU received from the peer is Inferior with designated role and state as learning and/or forwarding. Since this condition could be caused by an unidirectional link failure, the interface is put into blocking state and marked as disputed in order to prevent possible loops from being created","Issue the <CmdBold"
"STP","2","IPC_PROCESSING_ERR","Error in processing IPC message : Opcode = [dec], Error code = [hex]","STP encountered an error in processing an MTS message. The error and message are specified in the error message","No action is required."
"STP","2","L2GW_BACKBONE_BLOCK","L2 Gateway Backbone port inconsistency blocking port [chars] on [chars].","A BPDU was received on the listed interface which advertises a superior spanning tree root bridge to that currently in use. The interface is put into blocking state and marked as L2 Gateway Backbone port inconsistent in order to prevent a suboptimal spanning tree topology to form.","Issue the <CmdBold"
"STP","2","L2GW_BACKBONE_UNBLOCK","L2 Gateway Backbone port inconsistency cleared unblocking port [chars] on [chars].","The listed interface is no longer receiving BPDUs advertizing a superior root bridge. The L2 Gateway Backbone port inconsistency is cleared for the interface and then it is taken out of the blocking state if appropriate.","LOG_STD_NO_ACTION"
"STP","2","LOOPGUARD_BLOCK","Loop guard blocking port [chars] on [chars].","The spanning tree message age timer has expired because and no BPDUs were received from the designated bridge. Since this condition could be caused by an unidirectional link failure, the interface is put into blocking state and marked as loop guard inconsistent in order to prevent possible loops from being created","Issue the <CmdBold"
"STP","2","LOOPGUARD_CONFIG_CHANGE","Loop guard [chars] on port [chars].","The spanning tree loopguard configuration for the listed interface has been changed. If enabled, the interface will be put into blocking state and marked as loopguard inconsistent when the message age timer expires because no BPDU were received from the designated bridge. This feature is mainly used to detect unidirectional links","Verify that this is the desired configuration for the listed interface. Correct it if this is not the desired configuration otherwise no further action is required."
"STP","2","LOOPGUARD_UNBLOCK","Loop guard unblocking port [chars] on [chars].","The listed interface has received a BPDU and therefore if the inconsistency was due to an unidirectional link failure, now the problem is not there anymore. The loop guard inconsistency is cleared for the interface which is taken out of the blocking state if appropriate.","LOG_STD_NO_ACTION"
"STP","2","PVSTSIM_FAIL","Blocking [chars] port [chars]: Inconsistent [chars] PVST BPDU received on VLAN [dec], claiming root [chars]","When a MST switch is connected to a PVST+ switch, the CIST (MST00) information on the port of the MST switch must be consistently better than all the PVST+ messages if the port is designated or consistently worse than all the PVST+ messages if the port is root. If this constraint is not respected, the port on the MST switch is blocked in order to prevent a potential bridging loop","When STP is converging after a new switch, or switch port is added to the topology, this condition may happen transiently. The port unblocks automatically in such cases. If the port remains blocked, identify the root bridge as reported in the message, and configure a worse or better priority for the VLAN spanning tree consistent with the CIST role on the port of the MST switch. There could be more inconsistencies than the message indicates, and the port will not recover until all such inconsistencies are cleared. If you cannot determine which other VLANs have inconsistencies, disable and reenable the port. This message will appear again and specify another VLAN with inconsistencies to be fixed. Repeat this process until all inconsistencies on all VLANs are cleared."
"STP","2","PVSTSIM_OK","PVST Simulation inconsistency cleared on port [chars].","The listed interface is no longer receiving PVST BPDUs advertising an information inconsistent with the CIST port information. The PVST Simulation Inconsistency is cleared and the interface returns to normal operation","LOG_STD_NO_ACTION"
"STP","2","RANDNUM_FAIL","[chars]","There was a critical error during random number generation. [chars] indicates details of the error","No action is required."
"STP","2","RECV_BAD_TLV","Received SSTP BPDU with bad TLV on [chars] [chars].","The list interface received a SSTP BPDU that was missing the VLAN id tag. The BPDU is discarded.","No action is required."
"STP","2","RECV_PVID_ERR","Received BPDU with inconsistent peer vlan id [dec] on [chars] [chars].","The listed interface received a SSTP BPDU that is tagged with a VLAN id that does not match the VLAN id on which the BPDU was received. This occurs when the native VLAN is not consistently configured on both ends of a 802.1Q trunk.","Verify that the configuration of the native VLAN id is consistent on the interfaces on each end of the 802.1Q trunk connection. Once corrected, spanning tree will automatically unblock the interfaces as appropriate."
"STP","2","ROOTGUARD_BLOCK","Root guard blocking port [chars] on [chars].","A BPDU was received on the listed interface which advertizes a superior spanning tree root bridge to that currently in use. The interface is put into blocking state and marked as root guard inconsistent in order to prevent a suboptimal spanning tree topology to form.","Issue the <CmdBold"
"STP","2","ROOTGUARD_CONFIG_CHANGE","Root guard [chars] on port [chars].","The spanning tree root guard configuration for the listed interface has been changed. If enabled, any BPDU received on ths interface which advertizes a superior spanning tree root bridge to that already in use will cause the interface to be put into blocking state and marked as root guard inconsistent.","Verify that this is the desired configuration for the listed interface. Correct it if this is not the desired configuration otherwise no further action is required."
"STP","2","ROOTGUARD_UNBLOCK","Root guard unblocking port [chars] on [chars].","The listed interface is no longer receiving BPDUs advertizing a superior root bridge. The root guard inconsistency is cleared for the interface and then it is taken out of the blocking state if appropriate.","LOG_STD_NO_ACTION"
"STP","2","SET_PORT_STATE_FAIL","Port state change req to PIXM failed, status = [hex] [[chars]] vdc [dec], tree id [dec], num ports [dec], ports [chars] state [chars], opcode [chars], msg id ([dec]), rr_token [hex]","The port set port state has failed. check port","LOG_STD_NO_ACTION"
"STP","2","SET_PORT_STATE_TIMEOUT","Port state change req to PIXM timedout after [dec] sec. vdc [dec], tree id [dec], num ports [dec], ports [chars] state [chars], opcode [chars], msg id ([dec]), rr_token [hex]","The port set port state has timedout. check port","LOG_STD_NO_ACTION"
"STP","2","STP_INIT","STP initialization of [chars] [chars]","STP initialization failed","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"STP","2","STP_ISSU_LC_RESET","STP resetting LC[dec] to prevent Loops during ISSU caused by a topology change in the network. Peer on [chars] [chars] could not be Disputed","This can happen as a result of a topology change in the network while the Linecard was undergoing ISSU. Since STP cannot change the port state to blocking on the Linecard undergoing ISSU, it will first try to prevent the Loop by causing a Dispute on the peer ports forcing them into blocking state. But if the peer does not support Dispute mechanism, and STP detects a potential Loop, it will reset the Linecard to prevent the Loop","LOG_STD_NO_ACTION"
"STP","2","UNBLOCK_CONSIST_PORT","Unblocking port [chars] on [chars]. Port consistency restored.","The Port VLAN ID and/or Port Type inconsistencies have been resolved and spanning tree will now unblock the listed interface of the listed spanning tree instance as appropriate.","LOG_STD_NO_ACTION"
"STP","2","UNBLOCK_DETECTED_PVST_PEER","Unblocking port [chars] [PVST peer detected].","The listed interface has stopped receiving SSTP BPDUs and so will be restored to normal spanning tree state","LOG_STD_NO_ACTION"
"STP","2","VLAN_PORT_LIMIT_EXCEEDED","The number of vlan-port instances exceeded [[chars] mode] recommended limit of [dec]","The total number of individual VLAN ports, in the spanning tree mode specified in the error message, has exceeded the limit specified in the error message. VLANs can be counted more than once; if VLAN 1 is carried on 10 interfaces, it will count as 10 VLAN ports. Note that bundling is ignored for purposes of this count; if 8 interfaces on the same module are in one bundle, and the port channel is carrying VLAN 1, it will count as 1 VLAN ports.","Reduce the number of trunks and VLANs configured in the switch. Keep the VLAN port count below the recommended limit specified in the configuration documentation. Enter the <CmdBold"
"STP","2","VPC_PEERSWITCH_CONFIG_DISABLED","vPC peer-switch configuration is disabled. Please make sure to change spanning tree bridge priority as per the recommended guidelines.","The vPC peer-switch configuration has been changed. If enabled, please make sure to configure spanning tree bridge priority as per the recommended guidelines. If disabled, please make sure to change spanning tree bridge priority as per the recommended guidelines.","Verify that this is the desired configuration and follow the vPC peer-switch recommended guidelines."
"STP","2","VPC_PEERSWITCH_CONFIG_ENABLED","vPC peer-switch configuration is enabled. Please make sure to configure spanning tree bridge priority as per recommended guidelines to make vPC peer-switch operational.","The vPC peer-switch configuration has been changed. If enabled, please make sure to configure spanning tree bridge priority as per the recommended guidelines. If disabled, please make sure to change spanning tree bridge priority as per the recommended guidelines.","Verify that this is the desired configuration and follow the vPC peer-switch recommended guidelines."
"STP","2","VPC_PEER_LINK_INCONSIST_BLOCK","vPC peer-link detected [chars] blocking [chars] [chars].","VPC Peer-link detected the STP inconsistency mentioned in the message. This will impact the STP topology for vPCs and can cause frame duplications. As a result, the interface was moved to the spanning tree Blocking state","LOG_STD_NO_ACTION"
"STP","2","VPC_PEER_LINK_INCONSIST_ERRDISABLE","vPC Peer-link detected [chars]. Disabling [chars].","VPC Peer-link detected the STP inconsistency mentioned in the message. This will impact the STP topology for vPCs and can cause frame duplications. As a result, the vPC Peer-link was administatively shut down.","Please resolve the inconsistency reported in this message on the vPC Peer link. After the conflict has been resolved, re-enable the interface by entering the <CmdBold"
"STP","2","VPC_PEER_LINK_INCONSIST_UNBLOCK","vPC peer-link inconsistency cleared unblocking [chars] [chars].","VPC Peer-link inconsistency is cleared and the vPC interface listed in the message has been restored to normal spanning tree state.","LOG_STD_NO_ACTION"
"STP","3","BLOCK_PORT_TYPE","Blocking [chars] on [chars]. Inconsistent port type.","The listed interface is being held in spanning tree blocking state until the port type inconsistency is resolved.","Verify that the configuration and operational state of the listed interface and that of the interface to which it is connected have the same mode (access vs trunk). If mode is trunk, verify the same encapsulation (ISL, 802.1Q). Once these parameters are consistent, spanning tree will automatically unblock the interfaces as appropriate."
"STP","3","PORT_SELF_LOOPED","Received BPDU src mac same as that of port. Port self loopback detected. Port [chars] being disabled","The source MAC address contained in a BPDU received on the listed interface matches the MAC address assigned to that interface This indicates the possibility that a port is looped back to itself, possibly due to a diagnostic cable being plugged in. The interface will be administratively shutdown.","Check the interface configuration and any cable plugged into the interface. Once problem resolved, re-enable interface by doing a no shutdown in the interface configuration. Copy the error message as it is printed and also copy the output of a show interface for the interace listed in the error message."
"STP","3","RECV_1Q_NON_TRUNK","Received 802.1Q BPDU on non trunk [chars] [chars].","A SSTP BPDU was received on the listed interface that was not operationally a trunk.","Verify that the configuration and operational state of the listed interface and that of the interface to which it is connected have the same mode (access vs trunk). If mode is trunk, verify the same encapsulation (none, ISL, 802.1Q). Once these parameters are consistent, spanning tree will automatically unblock the interfaces as appropriate."
"STP","4","FORWARDTIME_CONFIG_CHANGE","Forward Delay time change to [dec] seconds for instance [chars] is not recommended as it can cause STP data loops during High Availability Dual-Supervisor Switchover and In-Service Software Upgrade","It is stongly recommended to avoid changing forward delay time value to less than the default value of 15 seconds since it can cause STP data loops during High Availability Dual-Supervisor Switchover and also during In-Service Software Upgrade. Please read the release notes.","Please change the forward delay time to be greater than or equal to the default value of 15 seconds"
"STP","4","HELLOTIME_CONFIG_CHANGE","Hello time change to [dec] seconds for instance [chars] is not recommended as it can trigger STP Topology Changes during High Availability Dual-Supervisor Switchover and In-Service Software Upgrade","It is stongly recommended to avoid changing Hello time value to less than the default value of 2 seconds since it can trigger STP Topology change during High Availability Dual-Supervisor Switchover and also during In-Service Software Upgrade. Please read the release notes.","Please change the hello time to be greater than or equal to the default value of 2 seconds."
"STP","4","MAC_ADDR_FLUSH_REQ_TIMEOUT","MAC Address Flush req to L2FM timedout after [dec] sec. vdc [dec], tree id [dec], num ports [dec], ports [chars], opcode [chars], msg id ([dec]), rr_token [hex]","The MAC Address Flush Request to L2FM has timedout. check port","LOG_STD_NO_ACTION"
"STP","6","FIRST_BPDU_TX","First BPDU transmitted","First BPDU transmitted.","No action is required."
"STP","6","MST_DIGEST","MST digest changed to [chars], pre-std digest changed to [chars]","MST Region configuration has changed","LOG_STD_NO_ACTION"
"STP","6","MST_PORT_BOUNDARY","Port [chars] [chars] as MST Boundary port","MST Boundary port status of the specified port is changed","LOG_STD_NO_ACTION"
"STP","6","MST_PORT_PRE_STANDARD","Port [chars] [chars] as MST Pre-standard port.","MST pre-standard status of the specified port is changed","LOG_STD_NO_ACTION"
"STP","6","PORT_ADDED","Interface [chars], added to [chars] with role [chars], state [chars], cost [dec], priority [dec], link-type [chars]","This spanning tree port has been added","LOG_STD_NO_ACTION"
"STP","6","PORT_COST","Port [chars] instance [chars] cost changed to [dec]","The spanning tree port cost has changed for the specified port","LOG_STD_NO_ACTION"
"STP","6","PORT_DELETED","Interface [chars], removed from [chars]","This spanning tree port has been deleted","LOG_STD_NO_ACTION"
"STP","6","PORT_LINK_TYPE","Port [chars] instance [chars] link changed to [chars]","The spanning tree port link type has changed for the specified port","LOG_STD_NO_ACTION"
"STP","6","PORT_PRIORITY","Port [chars] instance [chars] priority changed to [dec]","The spanning tree port priority has changed for the specified port","LOG_STD_NO_ACTION"
"STP","6","PORT_RANGE_ADDED","Interface [chars] added to [chars] with cost [dec], priority [dec], link-type [chars]","This spanning tree port has been added","LOG_STD_NO_ACTION"
"STP","6","PORT_RANGE_DELETED","Interface [chars] removed from [chars]","This range spanning tree logical ports has been deleted","LOG_STD_NO_ACTION"
"STP","6","PORT_RANGE_ROLE","new_role=[chars] interface=[chars] [chars]","The role of the range of spanning tree logical ports has changed","LOG_STD_NO_ACTION"
"STP","6","PORT_RANGE_STATE","new_state=[chars] interface=[chars] [chars]","The range of Spanning-Tree logical ports have changed state.","LOG_STD_NO_ACTION"
"STP","6","PORT_ROLE","Port [chars] instance [chars] role changed to [chars]","The spanning tree port role has changed for the specified port","LOG_STD_NO_ACTION"
"STP","6","PORT_STATE","Port [chars] instance [chars] moving from [chars] to [chars]","The Spanning-Tree port has changed state.","LOG_STD_NO_ACTION"
"STP","6","PRESTD_NEIGH","This switch has received a pre-standard MST BPDU on port [chars]: Invoking pre-standard MST BPDU transmission on this port.","The switch has received a pre-standard MST BPDU on a port. The switch will automatically adjust its mode of operation on this port and will start sending pre-standard BPDUs.","LOG_STD_NO_ACTION"
"STP","6","ROOT","Root bridge for [chars] changed to [chars]","The spanning tree root bridge has changed","LOG_STD_NO_ACTION"
"STP","6","SERVICE_UP","Initialized [chars]","STP line 2.","No action is required."
"STP","6","STATE_CREATED","Internal state created [chars]","STP has created its internal state stateless/stateful [chars].","No action is required."
"SVC_BATTERY-SLOT#","2","BATTERY_NOT_OPERATIONAL","Battery [dec] temperature [dec] C is outside the operational range (-10C to 65C).","The battery temperature is outside the operational range (-10C to 65C).","Verify fan operation with [show environment fan], and take action to cool down the switch."
"SVC_BATTERY-SLOT#","2","BATTERY_NOT_PRESENT","Battery [dec] is not present.","The line card does not have sufficient number of batteries. Two batteries are needed.","Remove the line card and plug in batteries in the battery slots that are empty."
"SVC_BATTERY-SLOT#","2","CHARGING_DISABLED","Temperature outside permitted range for battery charging (5C-40C).","The temperature of the linecard is not within the range to permit battery charging.","Make sure the temperature of the linecard is between 5C and 40C"
"SVC_BATTERY-SLOT#","2","CHARGING_FAILURE","Charging failure in battery [dec] ([hex]).","The module encountered failures while charging a battery.","Replace the battery."
"SVC_BATTERY-SLOT#","2","CLOCK_INCORRECT","System clock is running behind, battery conditioning will be affected.","The Vegas system clock is running behind the actual time. This will affect the battery conditioning.","Use clock set CLI command to set the correct time"
"SVC_BATTERY-SLOT#","2","COMMUNICATION_FAILURE","Communication failure with battery [dec].","The module encountered failures while communicating with a battery.","Replace the battery."
"SVC_BATTERY-SLOT#","2","CONDITIONING_DISABLED","Temperature outside permitted range for battery conditioning (5C-40C).","The temperature of the linecard is not within the range to permit battery conditioning.","Make sure the temperature of the linecard is between 5C and 40C"
"SVC_BATTERY-SLOT#","2","DISCHARGING_FAILURE","Discharging failure in battery [dec] ([hex]).","The module encountered failures while discharging a battery.","Replace the battery."
"SVC_BATTERY-SLOT#","4","BATTERY_CAPACITY_LOW","Battery capacity is below the required threshold.","The battery is lower than the required threshold.","Make sure the temperature is within the range to allow charging."
"SVC_BATTERY-SLOT#","6","BATTERY_CAPACITY_OK","Battery capacity is above the required threshold.","The battery is above the required threshold.","No action is required."
"SVC_BATTERY-SLOT#","6","CONDITIONING_CANCELLED","Temperature outside permitted range for battery conditioning (5C-40C). Battery [dec] conditioning cancelled.","The temperature of the linecard is not within the range to permit battery conditioning.","Make sure the temperature of the linecard is between 5C and 40C"
"SVC_BATTERY-SLOT#","6","CONDITIONING_COMPLETED","Conditioning of battery [dec] completed successfully.","Conditioning process started for a battery is completed successfully.","No action is required."
"SVC_BATTERY-SLOT#","6","CONDITIONING_RESUMED","Conditioning of battery [dec] resumed.","Conditioning process for a battery is resumed.","No action is required."
"SVC_BATTERY-SLOT#","6","CONDITIONING_STARTED","Conditioning of battery [dec] started.","Conditioning process started for a battery","No action is required."
"SVC","0","NODE_EMERG_MSG","[chars]","Syslog message from a SVC interface node","No action is required."
"SVC","1","NODE_ALERT_MSG","[chars]","Syslog message from a SVC interface node","No action is required."
"SVC","2","NODE_CRIT_MSG","[chars]","Syslog message from a SVC interface node","No action is required."
"SVC","2","SVC_SYSLOG_INIT_FAILED","Initialization failed for SVC: [chars], Reason: [hex]","Initialization failed for SVC","No action is required."
"SVC","2","SVC_SYSLOG_NO_PORT_CHAN","Too many PortChannels allocated by user for interface [chars]","SVC interface needs PortChannels to operate. Too many PortChannels have been allocated by the user for the interface to operate correctly.","Please delete unneeded user configured PortChannels and shutdown the SVC interface. Once complete, please bring the SVC interface back up."
"SVC","2","SVC_SYSLOG_PATH_FAILURE","System health detected SVC packet path failure for [chars].","The CSM has been brought down by the System Health monitor. System Health has detected a failure in the packet path between the SVC interface on the CSM and the backplane. This System Health test is run periodically.","Issue a 'no shutdown' on the SVC interface to bring the node back online. If a subsequent packet path failure occurs, the CSM module should be replaced."
"SVC","2","SVC_SYSLOG_URIFS_FAILURE","[chars] is unreachable for reason: [chars]","SVC interface modflash is not accessable. Modflash is the name of the filesystem local to the SVC interface, and is typically used for coredumps and temporary file transfers.","Please shutdown and bring up the SVC interface in question to regain access to the modflash filesystem."
"SVC","3","NODE_ERR_MSG","[chars]","Syslog message from a SVC interface node","No action is required."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_EC_ER_ACTIVATE_CLUSTER_IP_FAILED ) Activate cluster IP failed [chars]","Unable to activate the cluster IP for the config node. It will not be possible to execute configuration commands.","1. Shutting the interfaces of the node will force this node out of the cluster and cause another node to become the config node, which should restore the ability to execute configuration commands. 2. If the error persists, re-install the code on the node. The node will then have to be removed and re-added back to the cluster. 3. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 2 with the latest level of code. 4. If the error continues, ask IBM Product Support for assistance."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_EC_ER_BATT_FAILURE ) Battery Failed [chars]","The battery module on the Caching Services Module has failed. The nodes on the CSM will have shutdown. Other log entries may accompany this error.","Reload the Caching Services Module. If the error persists, replace the Caching Services Module."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_EC_ER_DISK_FAILURE ) Internal Disk Drive Failed [chars]","The internal disk drive for the node on the Caching Services Module has failed. The node will have shutdown. Other log entries may accompany this error.","Reload the Caching Services Module. If the error persists, replace the Caching Services Module."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_EC_ER_DUMP_RESTORE_FAILED ) Restore of hardened data failed [chars]","Restore of customer data failed. This error will be accompanied by other log entries.","Examine the log for other error entries and follow the actions recommended. If no other entries are found: 1. Re-install the code on the node. The node will have to be removed and re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. If the error continues, ask IBM Product Support for assistance. It may be necessary to replace the Caching Services Module."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_EC_ER_INVALID_BATT_CAPACITY ) Get battery capacity failed [chars]","The process was unable to get the battery capacity. Possibly due to communication failures with the CPP processor in the line card. Node was rebooted due to this error.","If this error is repeated continously, 1. Re-install the code on the line card. The node(s) will then have to be removed and re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. If the error persists, replace the Caching Services Module."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_EC_ER_OPEN_COMMITTED_FILE_FAILED ) Error attempting to open file [chars]","Process was unable to open the committed file. Node was rebooted due to this error.","If this error is repeated continously, 1. Re-install the code on the node. The node will then have to be removed and re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. If the error continues, ask IBM Product Support for assistance."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_EC_ER_SET_BATT_THRESHOLD_FAILED ) Set battery threshold failed [chars]","The process was unable to set the battery threshold. Possibly due to fatal communication failures with the power management module in the line card or the power management module has crashed. Node was rebooted due to this error.","If this error is repeated continously, 1. Re-install the code on the line card. The node(s) will then have to be removed and re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. If the error persists, replace the Caching Services Module."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_IC_EV_NODE_DISENFRANCHISED ) Node missing [chars]","A node is missing from the cluster.","1. If it is not obvious which node in the cluster has failed, check the status of the nodes and find the node with a status of offline. 2. Repair the failing node. 3. When the repair has been completed, this error will automatically be marked as fixed. 4. Check the node status. If all the nodes in the cluster are now online, but the error in the log has not been marked as fixed, manually mark the error as fixed."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_PL_ER_CLUSTER_PATH_FAILURE ) Cluster path failure [chars]","A cluster path has failed. The node is unable communicate with all the other nodes in the cluster.","1. Repair the fibre-channel network fabric. 2. Check the status of the node port. If the status of the port shows as online, mark the error you have just repaired as fixed."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_PL_ER_CPU_QUANTITY ) Processor change detected [chars]","The Caching Services Module is failing.","1. Replace the Caching Services Module. 2. Check node status. If all nodes show a status of online, mark the error you have just repaired fixed."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_PL_ER_DISK_FULL ) Node hard disk full [chars]","The error that is logged in the cluster error log indicates a software problem in the cluster.","1. Ensure that the software is at the latest level on the cluster. 2. Delete files from the /dumps directory. 3. Run a configuration dump and a logged data dump. Save the dump data. 4. Ask IBM Product Support for assistance. 5. Mark the error you have just repaired as fixed."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_PL_ER_FC_ADAP_FAIL ) Logical Fibre Channel port reported failed [chars]","No active/functioning logical FC port was detected by the software.","Reload the node. If the problem persists, replace the Caching Services Module."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_PL_ER_FC_ADAP_QUANTITY ) Logical Fibre Channel port missing [chars]","No active/functioning FC port was detected by the software.","Reload the node. If the problem persists, replace the Caching Services Module."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_PL_ER_FC_PORT_QUANTITY ) Logical Fibre Channel port reported not operational [chars]","No active/functioning logical FC port was detected by the software.","Reload the node. If the problem persists, replace the Caching Services Module."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_PL_ER_NODE_WARMSTART ) Node warmstarted due to software error [chars]","The error that is logged in the cluster error log indicates a software problem in the cluster.","1. Ensure that the software is at the latest level on the cluster. 2. Run a configuration dump and a logged data dump. Save the dump data. 3. Ask IBM Product Support for assistance. 4. Mark the error you have just repaired as fixed."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_PL_ER_POWER_DOMAIN ) Power domain error [chars]","The two nodes in an IO group are on the same Caching Services Module.","Determine what the configuration should be. Remove one of the nodes and add a node to the IO group which is not on the same Caching Services Module."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_VG_ER_MDISK_GROUP_OFFLINE ) A Managed Disk group is offline [chars]","An Mdisk group is offline.","1. Repair the enclosure or disk controller. 2. Start a cluster discovery operation. 3. Check managed disk status. If all managed disks show a status of online, mark the error you have just repaired as fixed."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_VG_ER_MED_ERRS_TOO_HIGH ) Media errors on back-end Managed Disk [chars]","Media errors on backend managed disk.","1. Repair the enclosure or disk controller. 2. Include the managed disk into the cluster. 3. Check managed disk status. If all managed disks show a status of online, mark the error you have just repaired as fixed."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_VL_ER_BASE_EVENT_RESOURCE_RAN_OUT ) Software error [chars]","The error that is logged in the cluster error log indicates a software problem in the cluster.","1. Ensure that the software is at the latest level on the cluster. 2. Run a configuration dump and a logged data dump. Save the dump data. 3. Ask IBM Product Support for assistance. 4. Mark the error you have just repaired as fixed."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_VL_ER_CONTROLLER_CONFIG_INVALID ) Incorrect controller configuration [chars]","Incorrect disk controller configuration.","1. Using service documentation for the disk controller, check that the correct configuration is set up for the disk controller. See also the IBM TotalStorage SAN Volume Controller for Cisco MDS 9000: Configuration Guide. 2. Mark the error you have just repaired as fixed. 3. Start a cluster discovery operation."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_VL_ER_DEVICE_PORT_LOGIN_LOSS ) Number of controller logins reduced [chars]","The number of controller logins has been reduced. One possible cause is that the user intentionally reconfigured the system.","1. Check whether the controller has regained connectivity. If it has not, check the cable connection to the remote-device port. 2. If all logins to a remote-device port have failed and you cannot solve the problem by changing cables, check the condition of the remote-device port and the condition of the remote device. 3. Start a cluster discovery operation. 4. Check the status of the disk controller. If all disk controllers show a good status, mark the error you have just repaired as fixed."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_VL_ER_DEVICE_RESOURCE_RAN_OUT ) Too many controllers were presented to the cluster [chars]","The configuration is not valid. Too many devices have been presented to the cluster or node.","1. Remove unwanted devices from the fibre-channel network fabric. 2. Start a cluster discovery operation to find devices. 3. List all connected managed disks. Check with the customer that the configuration is as expected. Mark the error you have just repaired fixed."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_VL_ER_IO_ERP ) Error Recovery Procedure occurred [chars]","A managed disk error recovery procedure (ERP) has occurred. This error has been reported because a large number of disk error recovery procedures have been performed by the disk controller. The problem is probably caused by a failure of some other component on the SAN.","1. View the error log entry and determine the managed disk that was being accessed when the problem was detected. (Note that the sense data from the disk controller is recorded in the cluster error log and can be accessed there. This data is not available in the switch system log.) 2. Perform the disk controller problem determination and repair procedures for the mdisk determined in step 1. 3. Perform fibre channel switch problem determination and repair procedures for the fibre channel switches containing the node, and connected to the disk controller that is managing the mdisk, and any fibre channel switches in the fibre channel path between those switches. 4. If any problems are found and resolved in steps 2 and 3, mark this error as fixed. 5. If no switch or disk controller failures were found in steps 2 and 3, take an error log dump. Call your hardware support center."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_VL_ER_IO_ERROR ) Managed Disk I/O error [chars]","A managed disk or managed disk controller port has been excluded because of excessive errors or unusual behavior.","1. Repair the enclosure or disk controller. 2. Check the managed disk status. If any managed disks show a status of online, mark the error you have just repaired as fixed. If any managed disks show a status of excluded, included the managed disks and then mark the error as fixed."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_VL_ER_IO_THRESHOLD ) Managed Disk error count threshold exceeded [chars]","A managed disk or managed disk controller port has been excluded because of excessive errors or unusual behavior.","1. Repair the enclosure or disk controller. 2. Check the managed disk status. If any managed disks show a status of online, mark the error you have just repaired as fixed. If any managed disks show a status of excluded, included the managed disks and then mark the error as fixed."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_VL_ER_IO_TIMEOUT_OVERALL ) Timeout due to excessive processing time [chars]","A managed disk has timed out. This error has been reported because a large number of disk timeout conditions have been detected. The problem is probably caused by a failure of some other component on the SAN.","1. Repair problems on all disk controllers and switches on the same SAN as this cluster. 2. If problems are found, mark this error as fixed. 3. If no switch or disk controller failures can be found, take an error log dump and call your hardware support center."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_VL_ER_LOCAL_PORT_EXCLUDED ) Local FC port excluded [chars]","A local fibre-channel port has been excluded.","1. Repair the fibre-channel network fabric. 2. Check the status of the disk controller. If all disk controllers 3. show good status, mark the error you have just repaired fixed. 4. If the error persists and no other cause can be determined, replace the Caching Services Module."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_VL_ER_LOGIN_EXCLUDED ) Login excluded [chars]","Login has been excluded.","1. In the sequence shown, exchange the FRUs for new FRUs: Fibre Channel cable, switch to remote port. 2. Start a cluster discovery operation to recover the login. 3. Check the status of the disk controller. If all disk controllers show a good status, mark the error you have just repaired fixed. 4. If the error persists and no other cause can be determined, replace the Caching Services Module."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_VL_ER_LUN_RESOURCE_RAN_OUT ) Too many LUNs were presented to a node [chars]","The configuration is not valid. Too many devices have been presented to the cluster or node.","1. Remove unwanted devices from the fibre-channel network fabric. 2. Start a cluster discovery operation to find devices. 3. List all connected managed disks. Check with the customer that the configuration is as expected. Mark the error you have just repaired fixed."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_VL_ER_MDISK_ACCESS_INVALID ) Access beyond end of disk, or Managed Disk missing [chars]","The error that is logged in the cluster error log indicates a software problem either in the cluster, or in a disk enclosure or disk controller that is connected to the node.","1. Ensure that the software is at the latest level on the cluster and on the disk controllers. 2. Run a configuration dump and a logged data dump. Save the dump data. 3. Ask IBM Product Support for assistance. 4. Mark the error you have just repaired as fixed."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_VL_ER_MDISK_DEVICE_PORT_EXCLUDED ) Remote Port excluded for a specific Managed Disk and Node [chars]","A remote fibre-channel port has been excluded.","1. View the error log. Note the mdisk ID associated with the error code. 2. Using the mdisk ID, determine the failing disk controller. 3. Refer to the service documentation for the disk enclosure or disk controller and the fibre-channel network fabric to resolve the reported problem. 4. Start a cluster discovery operation to recover the excluded fibre-channel port. 5. Include the managed disk that you noted in step 1. 6. Check the status of the disk controller. If all disk controllers show a good status, mark the error you have just repaired fixed. 7. If all disk controllers do not show a good status, contact the IBM support center to resolve the problem with the disk controller."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_VL_ER_MDISK_EXCLUDED ) Managed Disk excluded due to excessive errors, or all device ports excluded [chars]","A managed disk or managed disk controller port has been excluded because of excessive errors or unusual behavior.","1. Repair the enclosure or disk controller. 2. Check the managed disk status. If any managed disks show a status of online, mark the error you have just repaired as fixed. If all managed disks show a status of excluded, included the managed disks and then mark the error as fixed."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_VL_ER_MDISK_INITIALISE_INVALID ) Invalid blocksize, capacity or LUN identity has changed during Managed Disk initialisation [chars]","Access beyond end of disk. The initialization of the managed disk has failed.","1. Check the status of the managed disk and of the managed-disk group. 2. Include the managed disk into the cluster. 3. Check the managed disk status. If all managed disks show a status of online, mark the error you have just repaired as fixed. 4. If not all managed disks show a status of online, check the status of the disk controller."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_VL_ER_MDISK_RESOURCE_RAN_OUT ) Too many Managed Disks were presented to the cluster [chars]","The configuration is not valid. Too many devices have been presented to the cluster or node.","1. Remove unwanted devices from the fibre-channel network fabric. 2. Start a cluster discovery operation to find devices. 3. List all connected managed disks. Check with the customer that the configuration is as expected. Mark the error you have just repaired fixed."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_VL_ER_QUORUM_DISK_CREATION_FAILURE ) A suitable Managed Disk for use as a Quorum Disk was not found [chars]","No Mdisk is suitable for use as a quorum disk. When a cluster is created three disks are automatically selected as quorum disks. A quorum disk is needed to enable a tie-break when some cluster members are missing. To become a quorum disk: The Mdisk must be accessible by all nodes in the cluster and the Mdisk must have free extents. This error code is produced when at least one quorum disk is not accessible by all nodes in the cluster. A quorum disk might not be available because of a fibre-channel network failure or because of a fibre-channel switch zoning problem.","1. Resolve any known fibre-channel network problems. 2. Ask the customer to confirm that Mdisks have been created and that those mdisks have free extents. 3. List the manage disks. If at least one managed disk shows a mode of managed, mark the error you have just repaired as fixed. 4. If the customer is unable to make the appropriate changes, ask IBM Software Support for assistance."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_EID_VL_ER_QUORUM_DISK_NOT_AVAILABLE ) Quorum Disk not available [chars]","One or more quorum disks were not discovered by the node.","1. Resolve any known fibre-channel network problems. 2. Check managed disk status. If any managed disks are offline or excluded perform the disk controller problem determination and repair procedures for the managed disks. 3. Start a cluster discovery operation. 4. Check managed disk status. If all managed disks show a status of online, mark the error you have just repaired as fixed."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_ERR_CFG_ALL_SSH_KEYS_REMOVED ) Attempt to delete SSH keys (no effect) [chars]","svctaskrmallsshkeys'commandhasbeeninvoked.ThiscommandhasnoeffectinSANVolumeControllerf orCiscoMDS9000,butisretainedforcompatibility.'","None"
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_ERR_CFG_REMOTE_CREATEPARTNERSHIP ) Remote Copy partnership created [chars]","svctaskmkpartnership'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_ERR_CFG_REMOTE_DELETEPARTNERSHIP ) Remote Copy partnership deleted [chars]","svctaskrmpartnership'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_ERR_CFG_REMOTE_MODIFYPARTNERSHIP ) Remote Copy partnership modified [chars]","svctaskchpartnership'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_ERR_CFG_SSH_KEY_ADDED ) Attempt to add SSH key (no effect) [chars]","svctaskaddsshkey'commandhasbeeninvoked.ThiscommandhasnoeffectinSANVolumeControllerfor CiscoMDS9000,butisretainedforcompatibility.'","None"
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_ERR_CFG_SSH_KEY_REMOVED ) Attempt to delete SSH key (no effect) [chars]","svctaskrmsshkey'commandhasbeeninvoked.ThiscommandhasnoeffectinSANVolumeControllerforC iscoMDS9000,butisretainedforcompatibility.'","None"
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_NODERR_CR_START ) Cluster recovery required [chars]","The node has detected that cluster recovery is required and is waiting for for human intervention to continue.","Contact IBM Product support for assistance."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_NODERR_DATA_CORRUPT ) Node data corrupted - node rejected from cluster [chars]","Node data is readable but corrupted. The node has been rejected from the cluster.","1. Re-install the code on the node. The node will have to be removed and re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. If the error continues, ask IBM Product Support for assistance. It may be necessary to replace the Caching Services Module."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_NODERR_DATA_UNREADABLE ) Node data unreadable - node rejected from cluster [chars]","Node data could not be read. The node has been rejected from the the from cluster.","1. Re-install the code on the node. The node will have to be removed and re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. If the error continues, ask IBM Product Support for assistance. It may be necessary to replace the Caching Services Module."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_NODERR_HDW_CONFIG ) Processor not valid [chars]","The node has detected unexpected differences in the processor vital data.","Reload the node. If the problem persists, replace the Caching Services Module."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_NODERR_MEM_SIZE ) Memory size error [chars]","The detected memory size does not match the expected memory size for the cluster.","A memory module on the Cisco MDS 9000 Caching Services Module is probably faulty. Reload the node. If the error persists, replace the Caching Services Module."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_NODERR_MISSING_RES ) Unable to form a cluster due to lack of cluster resources [chars]","The node is unable to locate sufficient other nodes in the cluster and/or the quorum disk controller needed in order to form a cluster.","Check the status of the quorum disk controller and the other nodes in the cluster. If the quorum disk has failed, perform the problem determination procedures for the disk controller. Otherwise perform problem determination on the missing nodes and network."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_NODERR_NO_FABRIC ) The node is unable to see the FC fabric [chars]","No active/functioning logical FC port was detected by the software.","Reload the node. If the problem persists, replace the Caching Services Module."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_NODERR_PWR_DMN_ERR ) Power domain error [chars]","The two nodes in an IO group are on the same Caching Services Module.","Determine if both nodes on the Caching Services Module are in fact in the same IO group. If so, determine what the configuration should be. Remove one of the nodes and add a node to the IO group which is not on the same Caching Services Module. If not, ask IBM Product Support for assistance."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_NODERR_REPEATED_ASSERTS ) Node repeatedly crashing due to a software fault [chars]","The number of software faults has exceeded the maximum allowed for the time period.","1. Delete the node from the cluster. 2. Try to add the node back into the cluster. 3. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster with the latest level of code. 4. If the error continues, ask IBM Product Support for assistance."
"SVC","3","NODE_ERR_MSG","(SVC [dec]/[dec] SS_NODERR_RESET_AND_REJECT ) Node data not found - node rejected from cluster [chars]","Node data was not found. The node has been rejected from the the from cluster.","Examine error logs to determine if another recorded error caused the loss of the node data and, if so, follow the actions for that error. If no other error was recorded, the node may have lost power without saving data or been reset. Attempt to determine the cause of the power loss or reset. If no cause can be determined, then: 1. Re-install the code on the node. The node will have to be removed and re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. If the error continues, ask IBM Product Support for assistance. It may be necessary to replace the Caching Services Module."
"SVC","3","SVC_SYSLOG_IF_INTERNAL_ERROR","Interface [chars] internal error: [chars]","SVC interface internal error","No action is required."
"SVC","3","SVC_SYSLOG_LC_INTERNAL_ERROR","Unable to send MTS to linecard in slot [dec]: [chars]","Linecard MTS failure","No action is required."
"SVC","3","SVC_SYSLOG_NPORT_INTERNAL_ERROR","[chars] N-port for Interface [chars], vsan [dec] internal error: [chars]","N-port internal error","No action is required."
"SVC","4","NODE_WARNING_MSG","[chars]","Syslog message from a SVC interface node","No action is required."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_CA_EV_FIRST_DATA_PINNED ) Customer data pinned [chars]","There is now pinned customer data. This warning is given when data is pinned and there wasntalreadypinneddata.Errorlogentrieswillexistfortheunderlyingcauseofthepinneddata.'","Perform problem determintation on the error log to determine the cause of the pinned data and correct."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_CA_EV_HWS_TO_SYNCHRONOUS ) Cache in write through mode due to pinned data [chars]","The cache must now operate in write through mode because of the amount of pinned data.","Perform problem determintation on the error log to determine the cause of the pinned data and correct."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_EC_ER_BATT_BELOW_CAPACITY ) Battery is below threshold capacity [chars]","Battery capacity is below threshold. The node will remain offline until the battery charge is sufficient to come up.","Wait for the battery to recharge. This may take many hours. If after several hours have passed and the node has not yet come up: 1. Reload the node. 2. If the error persists, re-install the code on the line card. The node(s) will then have to be removed and re-added back to the cluster. 3. If the error persists, replace the Caching Services Module."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_EC_ER_CANNOT_OPEN_IO_PROCESS_Q ) Internal error - IO process queue [chars]","The process was unable to open the needed message queue. Node was rebooted due to this error.","If this error is repeated continously, 1. Re-install the code on the node. The node will then have to be removed and re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. If the error continues, ask IBM Product Support for assistance."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_EC_ER_DEACTIVATE_CLUSTER_IP_FAILED ) Deactivate cluster IP failed [chars]","Unable to deactivate the cluster IP for the config node. The cluster IP should be deactivated by other checks. If that is not the case it may not be possible to execute configuration commands.","If there is a problem executing configuration commands: 1. Shutting the interfaces of the node will force this node out of the cluster and should cause the switch to deactivate the IP address associated with this node which should restore the ability to execute configuration commands. 2. If the error persists, re-install the code on the node. The node will then have to be removed and re-added back to the cluster. 3. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 2 with the latest level of code. 4. If the error continues, ask IBM Product Support for assistance."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_EC_ER_DUMP_METADATA_FAILED ) Node assert dump failed [chars]","A failure occurred writting out a node assert dump. Other log entries may accompany this error.","An initial error will have caused the node assert dump. Examine the log for that error and follow the recommended actions for that error. In addition examine the log for errors related to the internal disk drive. If found, follow the recommended actions. If no entries explain the failure to write the dump: 1. Re-install the code on the node. The node will then have to be removed and re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster with the latest level of code. 3. If the error continues, ask IBM Product Support for assistance. It may be necessary to replace the Caching Services Module."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_EC_ER_EXECVE_FAILED ) Internal error - program launch [chars]","The process was unable to launch the IO program. Node was rebooted due to this error.","If this error is repeated continously, 1. Re-install the code on the node. The node will then have to be removed and re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. If the error continues, ask IBM Product Support for assistance."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_EC_ER_FORK_FAILED ) Internal error - fork failed [chars]","The process was unable to launch the IO program. Node was rebooted due to this error.","If this error is repeated continously, 1. Re-install the code on the node. The node will then have to be removed and re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. If the error continues, ask IBM Product Support for assistance."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_EC_ER_INTERNAL_EXIT_LOGIC_ERR ) Internal error - bad exit code [chars]","Node was warmstarted due to internal logic error.","1. Ensure that the software is at the latest level on the cluster. 2. Ask IBM Product Support for assistance."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_EC_ER_INTERNAL_UNKNOWN_EXEC_MODE ) Internal error - run mode [chars]","Node was rebooted due to internal logic error.","1. Ensure that the software is at the latest level on the cluster. 2. Ask IBM Product Support for assistance."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_EC_ER_IOP_EXITED_DUE_TO_SIGNAL ) Internal error - signal caused exit [chars]","The IO process exited because of a signal which was not caught. Node was warmstarted due to this error.","1. Ensure that the software is at the latest level on the cluster. 2. Ask IBM Product Support for assistance."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_EC_ER_IOP_STOPPED_DUE_TO_SIGNAL ) Internal error - signal caused stop [chars]","The IO process stopped because of a signal received. Node was warmstarted due to this error.","1. Ensure that the software is at the latest level on the cluster. 2. Ask IBM Product Support for assistance."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_EC_ER_IOP_TERMINATED_ABNORMALLY ) Internal error - abnormal exit [chars]","The IO process exited abnormally. Node was warmstarted due to this error.","1. Ensure that the software is at the latest level on the cluster. 2. Ask IBM Product Support for assistance."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_EC_ER_OPEN_MSG_QUEUE_FAILED ) Internal error - message queue [chars]","The process was unable to open the needed message queue. Node was rebooted due to this error.","If this error is repeated continously, 1. Re-install the code on the node. The node will then have to be removed and re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. If the error continues, ask IBM Product Support for assistance."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_EC_ER_PTHREAD_CREATE_FAILED ) Internal error - threads [chars]","The process was unable to create the needed threads. Node was rebooted due to this error.","If this error is repeated continously, 1. Re-install the code on the node. The node will then have to be removed and re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. If the error continues, ask IBM Product Support for assistance."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_EC_ER_UNKNOWN_MESSAGE_TYPE ) Internal error - message type [chars]","Node was rebooted due to internal logic error.","1. Ensure that the software is at the latest level on the cluster. 2. Ask IBM Product Support for assistance."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_EC_ER_WAITPID_FAILED ) Internal error - waitpid failed [chars]","The process was unable to launch the IO program properly. Node was warmstarted due to this error.","If this error is repeated continously, 1. Reload the node. 2. If the error persists, re-install the code on the node. The node will then have to be removed and re-added back to the cluster. 3. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 2 with the latest level of code. 4. If the error continues, ask IBM Product Support for assistance."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_EC_ER_WARMSTART_MEMORY_FAILED ) Internal error - warmstart memory device [chars]","The process was unable to warmstart the memory device. Node was rebooted due to this error.","If this error is repeated continously, 1. Re-install the code on the node. The node will then have to be removed and re-added back to the cluster. 2. Ensure that the software is at the latest level on the cluster. If not, upgrade the cluster and if necessary repeat step 1 with the latest level of code. 3. If the error continues, ask IBM Product Support for assistance."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_FC_ER_MAPPING_STOPPED ) FlashCopy has been stopped [chars]","A Flash Copy mapping task has been stopped because of an error. A stopped flash copy may affect the status of other VDisks in the same I/O group. Preparing the stopped flash copies as soon as possible is advised.","1. Correct higher priority errors. Then, ask the customer to prepare and start the Flash Copy task again. 2. Mark the error you have just repaired as fixed."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_FC_ER_PREPARE_FAILED ) FlashCopy prepare failed due to cache flush failure [chars]","A Flash Copy prepare task has failed because a cache flush has failed.","1. Correct higher priority errors, then retry the prepare tasks. 2. Mark the error you have just repaired as fixed."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_FC_ER_STOP_COMPLETED ) Flash Copy Stopped [chars]","The Flash Copy mapping or consistency group has entered the STOPPED state as a result of a user request to stop.","None"
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_IC_ER_DIRECTORY_LIST_FAILED ) Failed to obtain directory listing from remote node [chars]","An attempt to clean or retrieve files from /dumps directory has failed because of a failure to get listing of the directory from the remote node.","Determine if the remote node is still online. If not, perform problem determination on the remote node. If it is, retry the command. If it still fails contact the IBM Support Center for assistance. Cisco CLI commands may be used to access the node directly as an alternative."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_IC_ER_FEATURISATION_VIOLATION ) Featurisation violation [chars]","The user has allocated more virtualized storage than licensed for or established a Flash Copy mapping or Remote Copy relationship when these have not been licensed.","Look in the featurisation log for log entries of type Error'todeterminethetypeofviolation.Theuserthenshouldtheneitherreducevirtualizedstorage,remove theFlashCopymappingorRemoteCopyrelationship,soastobeincompliancewiththeirlicense;orupdatet helicenseinformationifthatisincorrect;orarrangewiththeirIBMrepresentativetopurchasealicenseforth edesiredfeatures.'"
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_IC_ER_TRANSFER_FILE_FAILED ) Failed to transfer file from remote node [chars]","An attempt to retrieve a file from /dumps directory has failed.","Determine if the remote node is still online. If not, perform problem determination on the remote node. If it is, retry the command. If it still fails contact the IBM Support Center for assistance. Cisco CLI commands may be used to access the node directly as an alternative."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_IC_EV_IOGRP_NONE_OK ) Both nodes in the IO group are not available [chars]","Following node remove by the user, there are no nodes left in the IO group.","None"
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_IC_EV_UPGRADE_NODE_PENDED ) Software upgrade process failed [chars]","A software upgrade has failed. This might be because of a hardware error or it might be because of a failure in the new version of the software. An automatic software downgrade is performed to restore the nodes to their previous software version. This will be indicated in the log by a Softwaredowngradecomplete'entry.Ifthedowngradeoperationfailstodowngradeanode,forexamplebe causeitisoffline,thedownloadoperationwillstopandwaitfortheofflineSANVolumeControllertoberepa iredordeletedfromthecluster.Whilethedowngradeoperationisinprogress,configurationcommandssent totheclusterwillfailwithamessageindicatingthatasoftwareupgradeoperationisstillinprogress.Thedow ngradeoperationmighttakeuptothreehours.'","1. Display the status of the nodes on the cluster. 2. If any node is offline, delete the offline node from the cluster. If the delete fails with a message indicating that a software upgrade is in progress, this means that the downgrade process is still active. Wait for this operation to either complete or stop on the offline node and then retry the delete. If the downgrade operation had stopped, it will now continue. 3. Solve all logged hardware problems 4. Ask the user to retry the software install. 5. If the installation fails again, report the problem to your software support center. 6. Mark the error you have just repaired as fixed."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_IC_EV_UPGRADE_PCK_DELIVERY_FAILED ) Software install package cannot be delivered to all nodes [chars]","An error occured while sending the software package to the nodes.","1. Display the status of the nodes on the cluster. 2. If any node is offline, perform problem determination on the node and bring the node back online. Or, alternatively, delete the offline node from the cluster. 3. Retry the software retry the delete. If the downgrade operation had stopped, it will now continue. 3. Solve upgrade command. 4. If the installation fails again, report the problem to your software support center."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_PL_ER_PLIC_LINK ) Connection to a configured remote cluster has been lost [chars]","This cluster is no longer able to communicate with the remote copy partner cluster.","Perform problem determination on the network and the other cluster."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_RC_ER_LSYNC ) Remote Copy suffered loss of synchronization [chars]","In a remote-copy operation, the relationship has stopped and lost synchronization, for a reason other than a continuous I/O error.","1. Correct higher priority errors, then restart the remote copy. 2. Mark the error you have just repaired as fixed."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_RC_ER_PERS ) Remote Copy suffered persistent error [chars]","A Remote Copy relationship has been stopped because of a continuous I/O error.","1. Correct the higher priority errors, then retry the Remote Copy task. 2. Mark the error you have just repaired as fixed."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_RC_ER_TIMEOUT ) Remote Copy retry timeout [chars]","Remote Copy was unable to find a path to the device in the remote cluster within the timeout period.","Perform problem determination on the network and remote cluster: Ensure that all nodes in both clusters are configured in the inter-cluster SAN or VSAN. Ensure that all virtual disks in the remote cluster are online."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_VG_ER_COPIED_MEDIUM_ERROR ) I/O media error copied [chars]","During a copy or a migrate process a media error was copied to the destination disk.","None"
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_VG_ER_INSUFFICIENT_VIRTUAL_EXTENTS ) Insufficient extents to create Virtual Disk [chars]","There are not enough extents contained within the managed disk group to create the required virtual disk. This error can be logged if a migration is started and then a virtual disk is created which uses the extents that were to be used for the migration.","Add additional managed disks to the managed disk group or reduce the size of virtual disk to be created."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_VG_ER_MIGRATE_STOPPED ) Migration stopped [chars]","The specific migration has been stopped due to errors occurring during migration, these errors have been logged.","Analyze the error log. Perform problem determination and correct any errors which have occurred. Migrate any specific extents which were not migrated due to the errors."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_VG_ER_MIGRATE_SUSPENDED ) Migration suspended [chars]","Migration suspended.","1. Ensure that all error codes of a higher priority have already been fixed. 2. Ask the customer to ensure that all mdisk groups that are the destination of suspended migrate operations have free extents available. 3. Mark this error as fixed. This will cause the migrate operation to be restarted. If the restart fails a new error will be logged."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_VL_ER_IO_MEDIUM_ERROR ) A media error has occurred during I/O to a Managed Disk [chars]","A disk I/O medium error has occurred.","1. Ask the customer to rewrite the bad data to the block LBA reported in the host systems SCSI sense data. Note: If this error has occurred during a migration, the host system will notice the error until the target device is accessed. 2. Check managed disk status. If all managed disks show a status of online, mark the error you have just repaired as fixed."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_VL_ER_IO_THRESHOLD_WARNING ) Managed Disk error count warning threshold met [chars]","IOs to the managed disk have experienced sufficient errors to generate this warning. If the managed disk continues to experience IO errors, the managed disk may be excluded.","Perform problem determination on the affected managed disk."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_VL_ER_LUN_DISCOVERY_FAILED ) Discovery of LUN failed [chars]","The cluster has a connection to the device on the SAN through this node, but the device has not responded to the node in a manner consistent with a functional device LUN.","If there are device LUNs that should have been discovered by the node: 1) Perform a manual discovery. 2) Perform problem determination on the device."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_EID_VL_ER_MDISK_PORT_PREFERENCE_IGNORED ) Preferred port is not being used for Managed Disk access [chars]","The preferred port designated by the back end controller is not being used for Managed Disk access. A port error or excluded port has prevented the use of the preferred port.","Perform problem determination on the controller and network to determine the cause of the port error or exclusion."
"SVC","4","NODE_WARNING_MSG","(SVC [dec]/[dec] SS_NODERR_CR_FAILED ) Cluster recovery failed [chars]","Cluster recovery has failed and a software dump has been created.","Contact IBM Product support for assistance."
"SVC","4","SVC_SYSLOG_IF_INTERNAL_WARN","Interface [chars] internal warning: [chars]","SVC interface internal warning","No action is required."
"SVC","4","SVC_SYSLOG_NPORT_INTERNAL_WARN","[chars] N-port for Interface [chars], vsan [dec] internal warning: [chars]","SVC interface internal warning","No action is required."
"SVC","5","NODE_NOTICE_MSG","[chars]","Syslog message from a SVC interface node","No action is required."
"SVC","5","SVC_SYSLOG_IF_CONFIG_DELETED","Interface [chars] configuration was deleted[chars]","SVC interface configuration was deleted","No action is required."
"SVC","5","SVC_SYSLOG_IF_DOWN","Interface [chars] is down","SVC interface is down","No action is required."
"SVC","5","SVC_SYSLOG_IF_UP","Interface [chars] is up","SVC interface is up","No action is required."
"SVC","6","NODE_INFO_MSG","[chars]","Syslog message from a SVC interface node","No action is required."
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_EID_CA_EV_ALL_DATA_UNPINNED ) All data now unpinned [chars]","All the customer data in the IO group is now unpinned.","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_EID_CA_EV_HWS_TO_ASYNCHRONOUS ) Pinned data reduced; cache can operate normally [chars]","Enough customer data has been unpinned that the cache is no longer required to operate in write through mode because of the pinned data. (Note that the cache may still operate in write through mode for other reasons.)","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_EID_EC_ER_BATT_OK ) Battery recharged [chars]","Battery capacity has been restored to above threshold. The node will now come online.","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_EID_EC_ER_BATT_POWER_DOWN ) Poweroff or power failure detected [chars]","The process has received a poweroff or power failure indication. The node is shutting down.","Restore power. If power was not removed and this occurs: 1. Reload the node. 2. If the error persists, re-install the code on the line card. The node(s) will then have to be removed and re-added back to the cluster. 3. If the error persists, replace the Caching Services Module."
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_EID_EC_ER_PWR_BUTTON ) Power withdrawn [chars]","Node software was notified that AC power was being shut off or the Caching Services Module was being reset.","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_EID_FC_ER_COPY_COMPLETED ) Flash Copy Copied [chars]","The Flash Copy mapping or consistency group has entered the IDLE_COPIED state. The target disk now contains a complete copy and is no longer dependent on the source.","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_EID_FC_ER_PREPARE_COMPLETED ) Flash Copy Prepared [chars]","The Flash Copy mapping or consistency group has entered the PREPARED state. It is now possible to Start or Stop the mapping/group.","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_EID_IC_EV_CLUSTER_RECOVERY_COMPLETE ) Cluster recovery completed [chars]","Cluster recovery has completed successfully.","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_EID_IC_EV_IOGRP_ONE_OK ) One node in the IO group is not available [chars]","Following node remove by the user, there is only one node left in the IO group.","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_EID_IC_EV_SECURE_DELETE_COMPLETE ) Virtual Disk format completed [chars]","The formatting (writing all zeros) to new extents of the Virtual Disk has completed.","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_EID_PL_ER_COLDSTART ) Node software started [chars]","The node software has been started (cold start).","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_EID_RC_ER_COPY_COMP ) Remote Copy complete [chars]","Background copy complete. The standalone relationship or consistency group has transitioned from InconsistentCopying'to'ConsistentSynchronized'.ThiswillonlybeloggedontheclusterofthePrimaryVi trualDisk(s).'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_EID_RC_ER_READY_TO_START ) Remote Copy ready to start [chars]","The remote copy relationship or consistency group, whic had been previously been stopped due to an error, is ready to be restarted. All resources are now online.","Restart the relationship or consistency group."
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_EID_VG_EV_MIGRATE_COMPLETE ) Migration complete [chars]","Migration has completed.","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_EID_VL_ER_CLUSTER_FABRIC_VIEW_CHANGE ) Cluster fabric view has been updated. [chars]","The node is in the process of discoverying devices on the fabric.","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_ADD_MAPPING ) Virtual Disk to Host SCSI mapping created [chars]","svctaskmkvdiskhostmap'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_ADD_WWPN ) Port added to a Host [chars]","svctaskaddhostport'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_CHANGE_CLUSTER_TIME ) Attempt to change cluster time (no effect) [chars]","svctasksetclustertime'commandhasbeeninvoked.ThiscommandhasnoeffectinSANVolumeController forCiscoMDS9000,butisretainedforcompatibility.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_CHANGE_TIMEZONE ) Attempt to change time zone (no effect) [chars]","svctasksettimezone'commandhasbeeninvoked.ThiscommandhasnoeffectinSANVolumeControllerfo rCiscoMDS9000,butisretainedforcompatibility.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_CLUSTER_DISCOVERY ) Manual Managed Disk discovery invoked [chars]","svctaskdetectmdisk'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_CLUSTER_DUMP_CONFIG ) Cluster config dumped to file [chars]","svctaskdumpconfig'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_CLUSTER_MODIFY ) Cluster attributes modified [chars]","svctaskchcluster'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_CLUSTER_SHUTDOWN ) Node or Cluster shutdown [chars]","svctaskstopcluster'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_CREATE_FC_MAPPING ) Flash Copy mapping created [chars]","svctaskmkfcmap'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_CREATE_HOST ) Host created [chars]","svctaskmkhost'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_DELETE_FC_MAPPING ) Flash Copy mapping deleted [chars]","svctaskrmfcmap'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_DELETE_HOST ) Hosts deleted [chars]","svctaskrmhost'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_DELETE_MAPPING ) Virtual Disk to Host SCSI mapping deleted [chars]","svctaskrmvdiskhostmap'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_DELETE_PORT_HOST_LIST ) Ports deleted from a Host [chars]","svctaskrmhostport'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_DELETE_WWPN ) Port deleted from a Host [chars]","svctaskrmhostport'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_DEVICE_SET_NAME ) Controller attributes modified [chars]","svctaskchcontroller'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_ERRORLOG_ANALYSE ) Error log analyzed [chars]","svctaskfinderr'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_ERRORLOG_CLEARLOG ) Error log cleared [chars]","svctaskclearerrlog'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_ERRORLOG_DUMPLOG ) Error log dumped [chars]","svctaskdumperrlog'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_ERRORLOG_FIX ) Error log entry marked fixed [chars]","svctaskcherrstate'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_FC_CONSIST_GRP_SET_NAME ) Flash Copy consistency group name modified [chars]","svctaskchfcconsistgrp-name'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_FC_CREATE_CONSIST_GRP ) Flash Copy consistency group created [chars]","svctaskmkfcconsistgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_FC_DELETE_CONSIST_GRP ) Flash Copy consistency group deleted [chars]","svctaskrmconsistgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_FC_SET_NAME ) Flash Copy mapping name modified [chars]","svctaskchfcmap-name'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_FEATURISATION_CHANGED ) Licensed settings modified [chars]","svctaskchlicense'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_FLASH_PREPARE_CG ) Flash Copy consistency group prepared [chars]","svctaskprestartfcconsistgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_FLASH_START_CG ) Flash Copy consistency group started [chars]","svctaskstartfcconsistgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_FLASH_STOP_CG ) Flash Copy consistency group stopped [chars]","svctaskstopfcconsistgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_HOST_DELETE ) Host deleted [chars]","svctaskrmhost'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_HOST_SET_NAME ) Host attributes modified [chars]","svctaskchhost'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_HWS_SET_NAME ) IO Group name modified [chars]","svctaskchiogrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_IO_TRACE_FINISHED ) IO Tracing stopped [chars]","svctaskstoptrace'orequivalentGUI/CiscoCLIcommandhasbeeninvoked,orthetriggeroccurredforagiv enManagedDisk,automaticallystoppingthetrace.'","Analyse the traces."
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_MDISK_GRP_ADD_MDISK ) Managed Disk added to Managed Disk group [chars]","svctaskaddmdisk'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_MDISK_GRP_CREATE ) Managed Disk Group created [chars]","svctaskmkmdiskgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_MDISK_GRP_DELETE ) Managed Disk Group deleted [chars]","svctaskrmmdiskgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_MDISK_GRP_DELETE_MDISK ) Managed Disk deleted from Managed Disk group [chars]","svctaskrmmdisk'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_MDISK_GRP_SET_NAME ) Managed Disk Group attributes modified [chars]","svctaskchmdiskgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_MDISK_SET_NAME ) Managed Disk attributes modified [chars]","svctaskchmdisk'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_MDISK_UNSLANDER ) Managed Disk online [chars]","The managed disk which was excluded is now online.","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_MIGRATE ) Virtual Disk migration to new Managed Disk group started [chars]","svctaskmigratevdisk'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_MODIFY_FC_MAPPING ) Flash Copy mapping modified [chars]","svctaskchfcmap'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_NODE_ADD ) Node added [chars]","svctaskaddnode'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_NODE_CREATE_CLUSTER ) Cluster created [chars]","clusteradd'orequivalentGUIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_NODE_DELETE ) Node deleted from cluster [chars]","svctaskrmnode'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_NODE_PEND ) Node Pend [chars]","The node has gone into the pending state. It will shortly go into the online or offline state.","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_NODE_REMOVE ) Node leaving cluster (expected) [chars]","The node has gone offline as expected due to shutdown, upgrade or deletion.","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_NODE_SET_NAME ) Node attributes modified [chars]","svctaskchnode'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_NODE_SHUTDOWN ) Node shutdown [chars]","svctaskstopcluster-node'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_NODE_UNPEND ) Node Unpend [chars]","The node has gone online.","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_PLANAR_SN_CHANGE ) Attempt to change the Planar Serial Number (no effect) [chars]","svctaskwritesernum'commandhasbeeninvoked.ThiscommandhasnoeffectinSANVolumeControllerf orCiscoMDS9000,butisretainedforcompatibility.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_PRETRIGGER_FC_MAPPING ) Flash Copy mapping prepared [chars]","svctaskprestartfcmap'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_QUORUM_CREATE ) Quorum disk set [chars]","svctasksetquorum'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_REMOTE_CREATECONSTGRP ) Remote Copy consistency group created [chars]","svctaskmkrcconsistgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_REMOTE_CREATEREL ) Remote Copy relationship created [chars]","svctaskmkrcrelationship'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_REMOTE_DELETECONSTGRP ) Remote Copy consistency group deleted [chars]","svctaskrmconsistgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_REMOTE_DELETEREL ) Remote Copy relationship deleted [chars]","svctaskrmrcrelationship'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_REMOTE_MODIFYCONSTGRP ) Remote Copy consistency group modified [chars]","svctaskchrcconsistgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_REMOTE_MODIFYREL ) Remote Copy relationship modified [chars]","svctaskchrcrelationship'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_REMOTE_START ) Remote Copy relationship started [chars]","svctaskstartrcrelationship'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_REMOTE_START_CG ) Remote Copy consistency group started [chars]","svctaskstartrcconsistgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_REMOTE_STOP ) Remote Copy relationship stopped [chars]","svctaskstoprcrelationship'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_REMOTE_STOP_CG ) Remote Copy consistency group stopped [chars]","svctaskstoprcconsistgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_REMOTE_SWITCH ) Remote Copy relationship switched [chars]","svctaskswitchrcrelationship'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_REMOTE_SWITCH_CG ) Remote Copy consistency group switched [chars]","svctaskswitchrcconsistgrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_SERVICE_APPLY_SOFTWARE ) Software upgrade command accepted [chars]","clusterupgradesvc-system'orequivalentGUIcommandhasbeeninvoked.Thecommandhasbeenaccepte d.Additionallogentrieswilltracktheprogressoftheupgrade.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_STOP_FC_MAPPING ) Flash Copy mapping stopped [chars]","svctaskstopfcmap'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_TRIGGER_FC_MAPPING ) Flash Copy mapping started [chars]","svctaskstartfcmap'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_UPGRADE_BACKED_OFF ) Software downgrade complete [chars]","The software upgrade process failed and all nodes have been restored to the previous level of code.","Perform problem determination on the cause of the upgrade failure and take corrective action before retrying the upgrade."
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_UPGRADE_COMPLETED ) Software upgrade complete [chars]","All nodes have successfully moved to the new code level, which will now be committed.","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_UPGRADE_STARTED ) Software upgrade started [chars]","The software upgrade process has started (the first node is about to be upgraded).","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_VDISK_CREATE ) Virtual Disk created [chars]","svctaskmkvdisk'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_VDISK_DELETE ) Virtual Disk deleted [chars]","svctaskrmvdisk'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_VDISK_EXPAND ) Virtual Disk expanded [chars]","svctaskexpandvdisksize'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_VDISK_EXPAND_SINGLE_EXT ) Virtual Disk expanded by single extent [chars]","svctaskaddvdiskext'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_VDISK_MIGRATE_EXTENT ) Extent migration started [chars]","svctaskmigrateexts'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_VDISK_MIGRATE_EXTENTS ) Extent migration started [chars]","svctaskmigrateexts'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_VDISK_MODIFY_GOVERN ) Virtual Disk throttling rate modified [chars]","svctaskchvdisk-rate'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_VDISK_MOVE_HWS ) Virtual Disk IO Group changed [chars]","svctaskchvdisk-iogrp'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_VDISK_SET_NAME ) Virtual Disk name modified [chars]","svctaskchvdisk-name'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","NODE_INFO_MSG","(SVC [dec]/[dec] SS_ERR_CFG_VDISK_SHRINK ) Virtual Disk shrunk [chars]","svctaskshrinkvdisksize'orequivalentGUI/CiscoCLIcommandhasbeeninvoked.'","None"
"SVC","6","SVC_SYSLOG_CL_CONFIG","Node [chars] has become config node of cluster [chars]","SVC interface has because cluster config node","No action is required."
"SVC","6","SVC_SYSLOG_CL_JOIN","Node [chars] has joined cluster [chars]","SVC interface has joined cluster","No action is required."
"SVC","6","SVC_SYSLOG_CL_UNJOIN","Node [chars] has left cluster [chars]","SVC interface has left cluster","No action is required."
"SVC","6","SVC_SYSLOG_LC_WWN_PURGE","All WWNs for module [dec] have been purged[chars]","SVC linecard has purged all WWNs","No action is required."
"SVC","6","SVC_SYSLOG_VSAN_INACTIVE","Vsan [dec] suspended","Vsan was suspended; can cause warnings","No action is required."
"SVC","7","NODE_DEBUG_MSG","[chars]","Syslog message from a SVC interface node","No action is required."
"SYSMGR","2","ACTIVE_LOWER_MEM_THAN_STANDBY","Active supervisor in slot [dec] is running with less memory than standby supervisor in slot [dec].","Supervisor memory mismatch","No action is required."
"SYSMGR","2","BOOTSCOPE_HANDSHAKE","Service [chars] is in the boot scope, but tried a regular handshake. Discarding request.","A service is trying to take actions that belong to a different class of services.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","CFGERASE_ABORTED","Write erase aborted.","Write erase has failed.","Please verify the other syslog messages printed correct the problem, and try again."
"SYSMGR","2","CFGSNAPSHOT_ABORTED_DIR","Unable to open the configuration directory. Aborting configuration snapshot.","The destination location for the snapshot-config could not be found.","If the problem persists, please use the vshboot command initsystem'toinitializetheconfigurationpartition.'"
"SYSMGR","2","CFGSNAPSHOT_ABORTED_INIT","Unable to initialize the configuration directory (error-id [hex]). Aborting configuration snapshot.","An attempt to copy the startup-config to snapshot-config has failed because the old data could not be removed.","If the problem persists, please use the vshboot command initsystem'toinitializetheconfigurationpartition.'"
"SYSMGR","2","CFGSNAPSHOT_ABORTED","Configuration snapshot aborted.","An attempt to save a snapshot of the startup-config has failed.","Please verify the other syslog messages printed correct the problem, and try again."
"SYSMGR","2","CFGSYNC_FAILURE","Syncing of the configuration to the standby failed.","Syncing of the configuration to the standby failed.","Please verify the other syslog messages printed correct the problem, and try again."
"SYSMGR","2","CFGWRITE_ABORTED_DIR","Unable to open the configuration directory. Aborting configuration copy.","The destination location for the startup-config could not be found.","If the problem persists, please use the vshboot command initsystem'toinitializetheconfigurationpartition.'"
"SYSMGR","2","CFGWRITE_ABORTED_INIT","Unable to initialize the configuration directory (error-id [hex]). Aborting configuration copy.","An attempt to copy the running-config to startup-config has failed because the old data could not be removed.","If the problem persists, please use the vshboot command initsystem'toinitializetheconfigurationpartition.'"
"SYSMGR","2","CFGWRITE_ABORTED_LABEL","Unable to label the new configuration (error-id [hex]). Aborting configuration copy.","An attempt to copy the running-config to startup-config has failed because the new startup-config could not be stamped.","If the problem persists, please use the vshboot command initsystem'toinitializetheconfigurationpartition.'"
"SYSMGR","2","CFGWRITE_ABORTED_LOCK","Unable to lock the configuration (error-id [hex]). Aborting configuration copy.","An attempt to copy the running-config to startup-config has failed because the system could not lock the required configuration items.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","CFGWRITE_ABORTED_LOG","Unable to open a log file for the new configuration: [chars] (error-id [hex]). Aborting configuration copy.","An attempt to copy the running-config to startup-config has failed because a log file could not be created.","If the problem persists, please use the vshboot command initsystem'toinitializetheconfigurationpartition.'"
"SYSMGR","2","CFGWRITE_ABORTED","Configuration copy aborted.","A configuration copy has failed.","Please verify the other syslog messages printed correct the problem, and try again."
"SYSMGR","2","CFGWRITE_TIMEOUT_ABORT","Configuration copy aborted by timeout.","A service failed to store its configuration in the timeout period. The operation has been aborted.","No action is required."
"SYSMGR","2","CFGWRITE_USER_ABORT","Configuration copy aborted by the user.","The user typed CTRL+C while the configuration was being saved, and the operation has been aborted.","No action is required."
"SYSMGR","2","CONVERT_FUNC_FAILED","Conversion function failed for service '[chars]' (error-id [hex]).","This message indicates that the conversion function failed for this service.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","CONVERT_FUNC_NOTFOUND","Conversion function not found for service '[chars]'.","This message indicates that the system could not find appropriate conversion function for this service.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","CONVERT_LIB_NOTFOUND","Conversion library not found for service '[chars]'.","This message indicates that the system could not find conversion library for this service.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","CONVERT_STARTUP_ABORTED","Conversion of startup-config failed.","This message indicates that the conversion of startup configuration was aborted.","If the problem persists, please use the vshboot command initsystem'toinitializetheconfigurationpartition.'"
"SYSMGR","2","CONVERT_ZIPPING_FAILED","Failed to zip the converted startup configuration.","This message indicates that conversion of the startup configuration failed when system was trying to zip the converted configuration.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","CORE_SAVE_FAILED","[chars]: PID [dec] with message [chars].","Recommended Action    No action is required.Error Message      SYSMGR-2-CREATE_DONEFILE_FAILED: Creating /var/run/sysmgr.initdone failed with return value: ([dec]). Explanation    The initialization of the system could not complete.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","DELETE_BINARY_STARTUP_FAILED","Deletion of binary startup config failed during boot (error-id [hex]).","This message indicates that the deletion of the binary startup configuration failed during boot.","If the problem persists, please use the vshboot command initsystem'toinitializetheconfigurationpartition.'"
"SYSMGR","2","FEATURE_SET_NOT_DISABLED_SRVS","vdc [dec]: feature-set 0x%llx: Following services did not cleanup: [chars]","Recommended Action    No action is required.Error Message    SYSMGR-2-FEATURE_SET_SRVTIMEOUT: vdc [dec]: feature-set 0x%llx [chars]: Following services did not respond in time: [chars] Explanation    The services did not handshake with sysmgr in time","No action is required."
"SYSMGR","2","FEATURE_SET_UNGRACEFUL_DISABLE_FAILED_SRVS","vdc [dec]: feature-set 0x%llx: Following services did not exit even after SIGKILL: [chars]","Recommended Action    No action is required.Error Message    SYSMGR-2-FORMAT_FAILURE_SUP_RESET: Failure to format a partition successfully causing sup to reset. Explanation    The partition used to store non-volatile pss files could not be formatted successfully. The supervisor will be reset.","If the problem persists, please contact customer support."
"SYSMGR","2","GSYNC_ABORT","Global sync aborted by signal.","The initial synchronization of the services has been aborted. The synchronization will be attempted again later.","Use the command reloadmodule<mod"
"SYSMGR","2","GSYNC_GET_TIMEOUT","Request for global sync for UUID [hex] not completed in specified time.","Service failed to complete global sync in specified time. The standby will no longer act as a HA standby.","If the problem persists, please contact customer support."
"SYSMGR","2","GSYNC_READY_SRVFAILED","Service '[chars]' on standby supervisor failed to restore its snapshot (error-id [hex]).","The initial synchronization of service [chars] has failed.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","GSYNC_SNAPSHOT_SRVFAILED","Service '[chars]' on active supervisor failed to store its snapshot (error-id [hex]).","The initial synchronization of service [chars] has failed.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","HANDSHAKE_FAILED","Handshake with service '[chars]' in vdc [dec] failed since send failed: [chars] (error-id [hex]).","Handshake with a service failed since system manager could not send handshake response to it.","No action is required."
"SYSMGR","2","HASWITCHOVER_PRE_START","This supervisor is becoming active (pre-start phase).","A cold switchover has started (pre-start phase).","When the other supervisor is back online, use the command showsystemreset-reason'toknowwhatcausedtheswitchover.'"
"SYSMGR","2","HASWITCHOVER_START","Supervisor [dec] is becoming active.","A cold switchover has started.","When the other supervisor is back online, use the command showsystemreset-reason'toknowwhatcausedtheswitchover.'"
"SYSMGR","2","HEARTBEAT_FAILED","Sysmgr heartbeat failed at %lu. [chars]. [chars] ([dec])","System manager had failure while trying to heartbeat with KLM","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","INBAND_START_FAILED","Failure while bringing up inband after ISSU reboot, errno: [dec].","Sysmgr tried to bring up inband after ISSU reboot, but the call returned error.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","INVALID_HANDSHAKE","Invalid secret ([dec]) received from service [chars]. Expected [dec].","A service cantbestarted.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","INVALID_SYSMGRCONF","[chars]: invalid configuration file '[chars]': [chars] (error-id [hex]).","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","INVALID_VERSIONMSG","The remote System Manager ([chars]) declares itself in the same state as this System Manager ([chars]).","The redundancy state negotiation between the two supervisors failed.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","ISSU_FAILED","The ISSU has failed: [chars] (error-id [hex])","The ISSU has failed and the switch need to be rebooted.","No action is required."
"SYSMGR","2","LAST_CORE_BASIC_TRACE","[chars]: PID [dec] with message [chars].","Recommended Action    No action is required.Error Message      SYSMGR-2-MSG_SEND_FAILURE_STANDBY_RESET: Failure in sending message to standby causing standby to reset. Explanation    We will be resetting the standby since mts on the active is unable to send a message to standby.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","MTS_FLUSH_SYNC_QUEUE_FAILURE","flush mts sync queue failed with [chars] (errno [dec])","Calling mts_flush_sync_queue to guarante no outstanding messages. the failure might affect HA","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","NON_VOLATILE_DB_FULL","System non-volatile storage usage is unexpectedly high at [dec]%.","System non-volatile storage space is almost full.","Please run the command clearprocesseslogpid<pid"
"SYSMGR","2","NON_VOLATILE_DB_INODE_FULL","System non-volatile inode storage usage is unexpectedly high at [dec]%.","System non-volatile inode storage space is almost full.","Please run the command clearprocesseslogpid<pid"
"SYSMGR","2","ONBOARD_FAILURE_LOGGING_FULL","Onboard failure logging usage is unexpectedly high at [dec]%.","Onboard failure logging space is almost full.","Please run the command clearloggingonboard'.Ifthismessagecontinuestopersist,pleasecontactTAC.'"
"SYSMGR","2","PARSEERR_DEPENDCYCLE","Dependency cycle found among [chars].","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_DUPLICATEDCONFIG","[chars]: duplicated definition for service config. Previous definition in [chars].","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_DUPLICATEDDEPEND","[chars]: duplicated dependency from [chars] for service [chars]. Previous use in [chars].","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_DUPLICATEDNAME","[chars]: short name [chars] used by service [chars] is also used by service '[chars]' in [chars].","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_DUPLICATEDOPTION","[chars]: duplicated definition for option [chars]-","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_DUPLICATEDSERVICE","[chars]: duplicated definition for service [chars]. Previous definition in [chars].","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_DUPLICATEDVERDB","[chars]: duplicated definition for service version_db. Previous definition in [chars].","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_DUP_UGRPENTRY","[chars]: service [chars] duplicated in the current upgrade group. Previous use in [chars].","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_FT_SET_ID_PARSEERR","[chars]: ft_set_id ([dec]) out of bound for '[chars]'.","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_INCONSISTENTOPT","[chars]: option '[chars]=[chars]' not consistent with '[chars]=[chars]' for service '[chars]'","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_INVALIDCOMPCONDDEPEND","[chars] (in dependency list of compulsory conditional service [chars]): optional conditional service '[chars]' not allowed.","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_INVALIDCONDDEPEND","[chars] (in dependency list of ASAP service [chars]): conditional service '[chars]' not allowed.","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_INVALIDDEPEND","[chars] (in dependency list of service [chars]): service [chars] not defined for scope '[chars]'.","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_INVALIDEXEC","[chars]: invalid executable [chars] for service [chars]: [chars] ([dec]).","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_INVALIDHANDSHAKEDEPEND","[chars] (in handshake dependency list of service [chars]): service '[chars]' is MTS unaware or not defined for scope '[chars]'.","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_INVALIDIDENT","[chars]: [chars] '[chars]' not found for service '[chars]'.","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_INVALIDOPTION","[chars]: option [chars]-","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_INVALIDSTDBYDEPEND","[chars]: service [chars] cannot be dependent on service [chars] due to the standby mode wait for that service.","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_INVALIDVDCDEPEND","[chars] (in dependency list of service [chars]): service [chars] is a [chars] service.","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_INVALID_CLEANUP_ARGUMENTS","[chars]: cleanup_arguments = '[chars]': only conditional services that are scripts can specify cleanup arguments","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_INVALID_COND_SRV_MODE","[chars]: service [chars] not defined for scope 'control' or not mts aware.","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_INVALID_DIR","[chars]: '[chars]' is not a valid [chars]: [chars] ([dec]).","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_INVALID_GLOBAL_SYNC","[chars]: mts unaware service may not request for a global sync.","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_INVALID_HB","[chars]: '[dec]' is not a valid heartbeat timeout.","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_INVALID_MAX_INSTANCE","[chars]: [dec] is not a valid max_instance.","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_INVALID_SHELLTREE","[chars]: invalid shell parser tree [chars] for service [chars]: [chars] ([dec]).","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_INVALID_STANDBY_MODE_GLOBAL_SYNC","[chars]: service with standby mode wait cannot request for a global sync.","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_INVALID_STANDBY_MODE","[chars]: standby_mode should be run.","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_INVALID_STARTUP_MODE_DEPENDENCY","[chars]: Invalid dependency. Service [chars]sstartupmode('[chars]')doesnotmatchdependentservice'[chars]''sstartupmode('[chars]').'","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","No action is required."
"SYSMGR","2","PARSEERR_INVALID_TRANSL","[chars]: invalid translator [chars] for service [chars]: [chars] ([dec]).","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_INVALID_UGRPENTRY","[chars]: service '[chars]' is not defined.","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_MISSINGOPTION","[chars]: option [chars]-","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_MTSUNAWARE_HANDSHAKEDEPEND","[chars]: service [chars] is MTS unaware and cannot have handshake dependencies.","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_NORESTART","[chars]: option [chars]-","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_NOTCONFIG","[chars]: [chars] implemented only for service config.","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_REPARSE_CANNOT_ADD_SRV","Service '[chars]' cannot be added","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_REPARSE_CANNOT_DELETE_SRV","Service '[chars]' cannot be removed","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_REPARSE_CANNOT_MODIFY_PARAM","Cannot modify parameter [chars] for the service '[chars]', old value = [chars], new value = [chars]","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_REPARSE_CANNOT_MODIFY_SRV","Configuration for service '[chars]' cannot be modified, param modified = [chars], old_value = [chars], new_value = [chars]","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_REP_UGRPENTRY","[chars]: service [chars] is used in more than one upgrade group. First use in [chars].","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_TOOMANYDEPENDS_MULTIPLE_INST","[chars]: too many multiple instance dependencies ([dec]) for service '[chars]'.","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_TOOMANYDEPENDS","[chars]: too many dependencies ([dec]) for service '[chars]'.","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_UGRPDUPLICATEDNAME","[chars]: upgrade group name '[chars]' already used in [chars].","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARSEERR_UGRPNAMEREDEFINED","[chars]: the upgrade group is already called '[chars]'.","The system image contains an inconsistent list of services. The initialization of the system cantproceedfurther.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PARTIAL_CFGWRITE_ABORTED","Partial configuration copy aborted.","A partial configuration copy has failed.","Please verify the other syslog messages printed correct the problem, and try again. If problem persists, please run the command copyrunning-configstartup-config'andtryagain.'"
"SYSMGR","2","PLUGIN_BOOTUP_FAILURE","The bootup of the supervisor has failed due to plugin load: [chars] (error-id [hex])","The bootup of the supervisor has failed due to plugin load.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PSS2FILE_CONVERT_FAILED","Conversion of file [chars] failed.","Conversion of internal data format failed.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","PSS2_VOLATILE_DB_FULL","Volatile database usage in kernel is unexpectedly high at [dec]%.","System volatile database in kernel space is almost full.","Please run the command systemsysteminternalpsskernelmemstats'.Ifthismessagecontinuestopersist,pleasecontactTAC.'"
"SYSMGR","2","REDSTATE_GETFAILED","Failed to request redundancy state: [chars] (error-id [hex]).","The local supervisor is unable to get the redundancy state.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","REDSTATE_SETFAILED","Failed to set redundancy state: ret_val ([dec]).","The local supervisor is unable to get the redundancy state.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","REDUNDANCY_CHANNEL_FAILURE","Remote sup will be rebooted since its coming up as active when local sup is still active.","Remote sup is becoming active although local sup is still active. As a result, local sup will cause the remote sup to reset itself.","If the problem persists, please contact customer support."
"SYSMGR","2","REDUNDANCY_HEARTBEAT_FAILURE","Heartbeat between active and standby on the redundancy channel not working for last [dec] minutes.","This supervisor is not receiving heartbeat on the redundancy channel from the other supervisor. This can result in problems during switchover and switchover may even fail.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","RESTART_SYSTEM_LOG","We will be restarting system soon for vdc [dec].","We will be restarting system since we were trying to do a hot switchover before all the state could have been transferred to this supervisor. So we will be doing a cold switchover now.","No action is required."
"SYSMGR","2","RESTORE_RUNTIME_DB_FAILED","Restoring of runtime database for fabric switch upgrade failed during boot (error-id [hex]).","This message indicates that the runtime database could not be restored during boot for the fabric switch upgrade.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","SAVE_RUNTIME_DB_FAILED","Saving of runtime database for fabric switch upgrade failed (error-id [hex]).","This message indicates that the runtime database could not be saved for the fabric switch upgrade.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","SERVICE_CRASHED","Service '[chars]' (PID [dec]) hasntcaughtsignal[dec][chars]'","A service has terminated its execution abnormally. The service might be restarted, depending on the HA policies implemented for the service.","Please use the command showprocess'toverifythattheservicehasbeenrestarted.'"
"SYSMGR","2","SHUTDOWN_FAILURE","Unable to set signal handler for graceful shutdown: [chars] (error-id [hex]).","This is a legacy message that can be ignored from Cisco MDS SAN-OS release 1.3(4a).","No action is required."
"SYSMGR","2","SHUTDOWN_REJECT","The System Manager is busy saving the configuration. Please try again later.","This is a legacy message that can be ignored from Cisco MDS SAN-OS release 1.3(4a).","No action is required."
"SYSMGR","2","SHUTDOWN_SYSTEM_LOG","vdc [dec] will shut down soon.","We are shutting down system the vdc","No action is required."
"SYSMGR","2","SIGKILL_FAILURE","Service '[chars]' failure to respond to SIGKILL causing supervisor to reset. Last heartbeat %.2f secs ago.","We will be resetting the supervisor since service failed to respond to SIGKILL sent to it by System Manager.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","SOCKET_ERROR","Failed to open socket connection, errno: [dec].","Call to open socket connection failed.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","SRV_CLEAR_MEMORY_ALERT","service '[chars]' clear memory alert ([dec]%)","Clean Memory Alert Event received","No action is required."
"SYSMGR","2","SRV_MAJOR_MEMORY_ALERT","service '[chars]' major memory alert ([dec]%)","Major Memory Alert Event received","No action is required."
"SYSMGR","2","SRV_MINOR_MEMORY_ALERT","service '[chars]' minor memory alert ([dec]%)","Minor Memory Alert Event received","No action is required."
"SYSMGR","2","SRV_SPAWN_FAILED","Spawning of service '[chars]' in vdc [dec] failed : [chars] (error-id [hex]).","Failed to spawn a service","No action is required."
"SYSMGR","2","STANDBY_BOOT_FAILED","Standby supervisor failed to boot up.","This message is printed if the standby supervisor doesntcompleteitsbootprocedure(i.e.itdoesn'treachtheloginpromptonthelocalconsole)3to6minutesaf tertheloaderhasbeenloadedbytheBIOS.Thismessageisusuallycausedbybootvariablesnotproperlysetf orthestandbysupervisor.Thismessagecanalsobecausedbyauserintentionallyinterruptingthebootproce dureattheloaderprompt(bymeansofpressingESC).'","Connect to the local console of the standby supervisor. If the supervisor is at the loader prompt, try to use the boot'commandtocontinuethebootprocedure.Otherwise,issuea'reload'commandforthestandbysupervi sorfromavshsessionontheactivesupervisor,specifyingthe'force-dnld'option.Oncethestandbyisonline, fixtheproblembysettingthebootvariablesappropriately.'"
"SYSMGR","2","STARTUP_CONVERSION_FAILED","Startup config conversion failed during boot (error-id [hex]).","This message indicates that the conversion of startup configuration failed during boot.","If the problem persists, please use the vshboot command initsystem'toinitializetheconfigurationpartition.'"
"SYSMGR","2","START_SCRIPT_FAILED","Start script (/isan/etc/rc.sysmgr start) failed with return value: ([dec]).","The initialization of the system could not complete.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","SUBPROC_SPAWN_FAILED","Spawning of sub-process '[chars]' in vdc [dec] failed : [chars] (error-id [hex]).","Failed to spawn a sub-process","No action is required."
"SYSMGR","2","SUP_POWERDOWN","Supervisor in slot [dec] is running with less memory than active supervisor in slot [dec]","Supervisor memory mismatch","No action is required."
"SYSMGR","2","SWITCHOVER_OVER","Switchover completed.","The switchover is completed.","No action is required."
"SYSMGR","2","SWITCHOVER_SRVCRASHED","Service '[chars]' (PID [dec]) crashed during switchover - hasntcaughtsignal[dec].Corewillnotbecollected.'","The switchover failed because a service crashed during switchover.","No action is required."
"SYSMGR","2","SWITCHOVER_SRVFAILED","Service '[chars]' failed in performing its switchover actions (error-id [hex]).","The switchover failed because a service could not transition to the active state.","No action is required."
"SYSMGR","2","SWITCHOVER_SRVTERMINATED","Service '[chars]' (PID [dec]) terminated during switchover with error code [dec] .","The switchover failed because a service terminated during switchover.","No action is required."
"SYSMGR","2","SWITCHOVER_THRESHOLD_EXCEEDED","Switchover threshold exceeded ([dec] switchovers happened within [dec] seconds). Powering down all linecards.","Switchover threshold exceeded","No action is required."
"SYSMGR","2","SWITCHOVER_TIMEOUT","Service '[chars]' (vdc [dec]) did not respond to switchover message in [dec] seconds","The switchover timeout because a service failed to response","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","SYNC_FAILURE_MSG_PAYLOAD","vdc [dec]: [chars]","Dump out the msg to know what causes sync failure","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","SYNC_FAILURE_STANDBY_RESET","Failure in syncing messages to standby for vdc [dec] causing standby to reset.","We will be resetting the standby since mts on the active is unable to sync messages to standby.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","SYSMGR_AUTOCOLLECT_TECH_SUPPORT_LOG","This supervisor will temporarily remain online in order to collect show tech-support. This behavior is configurable via system[no]auto-collecttech-support'.'","Supervisor is automatically collecting logs","No action is required."
"SYSMGR","2","TMP_DIR_FULL","System temporary directory usage is unexpectedly high at [dec]%.","System /tmp space is almost full.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","VDC_CREATE_DELETE_SRVCRASHED","Global vdc-aware service '[chars]' (PID [dec]) crashed during vdc create/delete on standby - hasntcaughtsignal[dec].'","The creation/deletion of vdc on standby failed because a global vdc-aware service crashed on standby.","No action is required."
"SYSMGR","2","VDC_CREATE_DELETE_SRVTERMINATED","Global vdc-aware service [chars] (PID [dec]) terminated during vdc create/delete on standby with error code [dec] .","The creation/deletion of vdc on standby failed because a global vdc-aware service terminated on standby.","No action is required."
"SYSMGR","2","VDC_DELETE_FAILURE","The vdc delete has failed: [chars] (error-id [hex])","The vdc delete has failed","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","2","VDC_NOT_CLEANEDUP_SRVS","vdc [dec]: [chars]","Recommended Action    No action is required.Error Message      SYSMGR-2-VOLATILE_DB_FULL: System volatile database usage is unexpectedly high at [dec]%. Explanation    System volatile database space is almost full.","Please run the command systempssshrink'.Ifthismessagecontinuestopersist,pleasecontactTAC.'"
"SYSMGR","2","WARMSWITCHOVER_START","This supervisor is becoming active.","A cold switchover has started.","When the other supervisor is back online, use the command showsystemreset-reason'toknowwhatcausedtheswitchover.'"
"SYSMGR","2","WDT_KGDB","System watchdog kgdb has been [chars] for slot [dec].","System watchdog kgdb has been [chars]. If the command has been enabled, the system will go into kgdb if there is a watchdog timeout.","No action is required."
"SYSMGR","3","BASIC_TRACE","[chars]: PID [dec] with message [chars].","Recommended Action    No action is required.Error Message      SYSMGR-3-CAPABILITY_REDUN_CHANGE: Redundancy mode changed to [chars] due to configuration change. Explanation    Some configuration changes have occurred causing administrative redundancy mode to change.","No action is required."
"SYSMGR","3","CFGCTRL_ABORT","signal to abort cfgctrl as super changes to the unstable state","When super state changes to unstable, cfgctrl should be terminated","No action is required."
"SYSMGR","3","CFGERASE_FAILED","Configuration erase failed (error-id [hex]).","The requested configuration erase has failed. [dec] is the error-ID representing the failure reason.","No action is required."
"SYSMGR","3","CFGSNAPSHOT_FAILED","Configuration snapshot failed (error-id [hex]).","The requested configuration snapshot has failed. [dec] is the error-id representing the failure reason.","No action is required."
"SYSMGR","3","CFGWRITE_FAILED","Configuration copy failed (error-id [hex]).","The requested configuration copy has failed. [dec] is the error-id representing the failure reason.","No action is required."
"SYSMGR","3","CFGWRITE_REJECT","Discarding request for configuration [chars]: configuration action already in progress.","Another instance of the command copyrunning-configstartup-config'isinprogress.'","Please wait for the other instance to complete."
"SYSMGR","3","CFGWRITE_SRVCRASHED","Service [chars] crashed with signal ([dec]) while configuration was being saved","A required service has crashed while configuration was being saved. The overall configuration copy is considered failed.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","3","CFGWRITE_SRVFAILED","Service '[chars]' failed to store its configuration (error-id [hex]).","A required service has failed to store its own configuration into the startup-config. The overall configuration copy is considered failed.","Use the showprocess'commandtoverifythatthesystemisrunningproperlyandtheservice[chars]isbehavingcorr ectly.Thentryagain.'"
"SYSMGR","3","CFGWRITE_SRVTERMINATED","Service [chars] terminated with error code ([dec]) while configuration was being saved","A required service has terminated while configuration was being saved. The overall configuration copy is considered failed.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","3","CFGWRITE_SRVTIMEOUT","Service [chars] failed to store its configuration in the timeout period","A required service has failed to send a response after receving a request to store its configuration into the startup-config. The overall configuration copy is considered failed.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","3","CFGWRITE_VDCSRVCRASHED","Service [chars] in vdc [dec] crashed with signal ([dec]) while configuration was being saved","A required service has crashed while configuration was being saved. The overall configuration copy is considered failed.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","3","CFGWRITE_VDCSRVFAILED","Service '[chars]' in vdc [dec] failed to store its configuration (error-id [hex]).","A required service has failed to store its own configuration into the startup-config. The overall configuration copy is considered failed.","Use the showprocess'commandtoverifythatthesystemisrunningproperlyandtheservice[chars]isbehavingcorr ectly.Thentryagain.'"
"SYSMGR","3","CFGWRITE_VDCSRVTERMINATED","Service [chars] in vdc [dec] terminated with error code ([dec]) while configuration was being saved","A required service has terminated while configuration was being saved. The overall configuration copy is considered failed.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","3","CFGWRITE_VDCSRVTIMEOUT","Service [chars] in vdc [dec] failed to store its configuration in the timeout period","A required service has failed to send a response after receving a request to store its configuration into the startup-config. The overall configuration copy is considered failed.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","3","COPY_CORES_FAILED","Copying cores failed ([dec]).","Copying cores to the destination failed because of an error specified in the log.","No action is required."
"SYSMGR","3","COREDUMP_TIMEOUT","Failed to store the core in the specified time. Resetting ....","Failed to store the core in the specified time. Resetting ...","No action is required."
"SYSMGR","3","CORE_CLIENT_INIT_FAILED","Core client will not be started due to some internal error.","Core client will not be started due to some internal error.","No action is required."
"SYSMGR","3","CORE_OP_FAILED","Core operation failed: [chars]","Mainly use to display failure on core operation in general","No action is required."
"SYSMGR","3","CORE_SERVER_INIT_FAILED","Core server will not be started due to some internal error.","Core server will not be started due to some internal error.","No action is required."
"SYSMGR","3","DAEMONIZE_FAILED","Unable to daemonize service '[chars]': [chars] ([dec]).","A service could not be spawned.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","3","FAILED_PFM_HANDSHAKE","PFM-handshake from service '[chars]' failed (error-id [hex]).","The Platform Manager handshake has failed. The system cantproceedwiththeinitialization.'","No action is required."
"SYSMGR","3","GSYNC_TIMEOUT_FAILED","Failed to set timeout for global sync for an application ([dec]).","Failed to set timeout for global sync for an application. This can result in global sync to be stuck forever if application never complete global sync.","No action is required."
"SYSMGR","3","HEARTBEAT_FAILURE","Service '[chars]' sent SIGABRT for not setting heartbeat for last [dec] periods. Last heartbeat %.2f secs ago.","A service is not setting proper heartbeats to System Manager So it will kill this service and if this service has restartability set to TRUE, the service will restart.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","3","INVALID_BOOT_HANDSHAKE","Boot-scope-handshake received from service [chars], that is in scope [dec] (not the boot scope).","A service is trying to take actions that belong to a different class of services.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","3","INVALID_GSYNC_GET","Service '[chars]' vdc [dec] requesting gsync without setting proper flag in its conf file.","Service is requesting global sync without setting proper flag in its conf file.","No action is required."
"SYSMGR","3","INVALID_PFM_HANDSHAKE","PFM-handshake received from service [chars], that is in scope [dec] (not the boot scope).","A service is trying to take actions that belong to the Platform Manager service.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","3","INVALID_TRANSITION","Transition from state [chars] to state [chars] is not allowed.","Unexpected transition in the System Manager state machine.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","3","INVALID_UUID","Service [chars] is configured with UUID [hex], but uses UUID [hex].","The identity of a service is inconsistent in the image file","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","3","ISSU_BEGIN_FAILED","ISSU cannot proceed (error-id [hex]).","This message indicates that some service has blocked the ISSU.","No action is required."
"SYSMGR","3","LC_IMAGE_UPGRADE_FAILURE","Linecard image upgrade request failed(error-id [hex]).","Linecard image upgrade request failed","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","3","LC_RESET","Resetting linecard","Linecard is being reset","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","3","LC_SAVE_STATES_FAILURE","Save states request for the linecard failed(error-id [hex]).","Save state request for the linecard failed","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","3","LC_STOP_ASYNC_FAILURE","Stop async notification request failed(error-id [hex]).","Stop async notification request for the linecard failed","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","3","LC_UPG_ERROR","LC ERROR: [chars]","Linecard upgrade error message","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","3","MISSING_OPTIONAL_CAPABILITY","Incomplete support for the current running-config on standby supervisor.","Loose config incompatibilities exist between active and standby sup. Operational redundancy mode is still set to HA.","No action is required."
"SYSMGR","3","MODULE_LOCK_FAILED","Failed to lock the local module to avoid reset (error-id [hex]).","Locking the local module has failed. Reloading the local module can now result in switchover to fail.","No action is required."
"SYSMGR","3","ND_UPGD_RECOVERY_SRVFAILED","Service '[chars]' in vdc [dec] failed in non-disruptive upgrade recovery (error-id [hex]).","The non-disruptive upgrade failed because a service could not recover its state.","No action is required."
"SYSMGR","3","OPERATIONAL_MODE_WARM","Operational redundancy mode set to warm (error-id [hex]).","Operational redundancy mode will be set to warm. [dec] is the error-ID representing the reason.","No action is required."
"SYSMGR","3","PARTIAL_CFGWRITE_FAILED","Partial configuration copy failed (error-id [hex]).","The requested configuration copy has failed. [dec] is the error-ID representing the failure reason.","No action is required."
"SYSMGR","3","PARTIAL_CFGWRITE_VER_MISMATCH","Startup-config version not same as current software version.","Startup-config version not same as current software version.","Please do a copy running startup, and try again."
"SYSMGR","3","RTDBCTRL_BUILD_UPG_TBL_FAILED","Failed to prepare upgrade version table during pre-upgrade","A required sequence in the preupgrade sequence has failed. The version table could not be built correctly","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","3","RTDBCTRL_SRVFAILURE","Service '[chars]' responded with a failure","A service responded with a failure to the request","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","3","RTDBCTRL_SRVTIMEOUT","Service [chars] failed to respond back to System Manager in the specified timeout period","A required service has failed to send a response after receiving a request for the fabric switch upgrade.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","3","RTDBCTRL_SRV_RECV_FAILED","Failed to receive response from Service '[chars]'","A required service has failed to send a response after receiving a request for the fabric switch upgrade.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","3","RTDBCTRL_SRV_SEND_FAILED","Failed to send upgrade request to Service '[chars]'","Failed to send upgrade request to a required service","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","3","SERVICE_TERMINATED","Service [chars] (PID [dec]) has finished with error code [chars] ([dec]).","A service has terminated its execution normally. Depending on the value of [dec2] and the HA policies implemented for the service, the service might be restarted automatically.","No action is required."
"SYSMGR","3","SHUTDOWN_OVER","The System Manager is shutting down now.","This is a legacy message that can be ignored from Cisco MDS SAN-OS release 1.3(4a).","No action is required."
"SYSMGR","3","SHUTDOWN_START","The System Manager has started the shutdown procedure.","This is a legacy message that can be ignored from Cisco MDS SAN-OS release 1.3(4a).","No action is required."
"SYSMGR","3","STANDBY_UNSTABLE_FTSET_OPERATION","Restarting standby since it is not in hot standby state while feature-set operation was in progress in vdc [dec].","Standby unstable during feature-set operation","No action is required."
"SYSMGR","3","STANDBY_VDC_RESTART_FAILURE","vdc [dec] on standby failed to restart. error: [chars] ([hex])","Recommended Action    No action is required.Error Message      SYSMGR-3-SYSMGR_CRASHED: Sysmgr (PID [dec]) [chars] Explanation    Sysmgr has terminated abnormally.","Please use the command showprocess'toverifythatsysmgrhasbeenrestarted.'"
"SYSMGR","3","TFTP_CORES_FAILED","TFTPing cores failed ([chars]).","TFTPing cores to the destination failed because of an error specified in the log.","No action is required."
"SYSMGR","3","UNACCEPTABLE_WAIT","Service [chars], no response from System Manager after [dec] seconds. Terminating.","A spawned service couldnthandshakewiththeSystemManagerandit'sabouttobeterminated.'","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","3","UNLINK_RELINK_CONF_FILES_FAILED","[chars] of conf files failed. plugin_id [dec]","Unlink and/or Relink of configuration files failed.","No action is required."
"SYSMGR","3","URIFS_APPLY_FAILED","Applying URI filesystem database failed (error-id [hex]).","The application of URI filesystem database has failed. [dec] is the error-ID representing the failure reason.","No action is required."
"SYSMGR","4","BASIC_TRACE_WARNING","[chars]: PID [dec] with message [chars].","Recommended Action    No action is required.Error Message      SYSMGR-4-CFGWRITE_PARTIALFORCED: Some services are missing; partial configuration write forced. Explanation    The system is not fully operational, but a configuration copy has been forced. The services that are not running wontsavetheirconfiguration,andthenexttimetheywillrestartwithadefaultconfiguration.'","Use the showprocess'commandtofindoutwhichrequiredservicesarenotrunning.'"
"SYSMGR","4","ON_DEMAND_STOP_UID_KNOWN","On-demand service '[chars]' stopped by uid ([dec]).","The service start type is specified as type on-demand in its configuration file and an external request requested to abort it.","No action is required."
"SYSMGR","4","ON_DEMAND_STOP","On-demand service '[chars]' stopped.","The service start type is specified as type on-demand in its configuration file and an external request requested to abort it.","No action is required."
"SYSMGR","4","PARSEWARN_INVALID_CFGFILE","[chars]: unable to find '[chars]': [chars] ([dec]).","This message is for Cisco TAC debugging. This is not a problem or malfunction.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","4","PARSEWARN_RESTART_CNT_TOO_BIG","Service '[chars]': [chars] restart count of [dec] too big, needs to be set to [dec].","This message is for Cisco TAC debugging. This is not a problem or malfunction.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","4","PARSEWARN_VALUE_TOO_SMALL","[chars]: [chars] is too small, replaced with [dec].","This message is for Cisco TAC debugging. This is not a problem or malfunction.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","4","READCONF_REJECT","Discarding configuration update request: [chars].","This is a legacy message that can be ignored from Cisco MDS SAN-OS release 1.3(4a).","No action is required."
"SYSMGR","4","READCONF_STARTED","Configuration update started (PID [dec]).","This is a legacy message that can be ignored from Cisco MDS SAN-OS release 1.3(4a).","No action is required."
"SYSMGR","4","SRVSCOPE_DELAYED","Waiting for redundancy state; termination delayed for scope [chars].","This message is for Cisco TAC debugging. This is not a problem or malfunction.","No action is required."
"SYSMGR","4","SYSMGR_CORE_TRUNCATED","Core seems to be truncated on generation. [dec] / [dec] KB. PID: [dec]","Core likely truncated","No action is required."
"SYSMGR","4","SYSMGR_PLUGIN_FAILURE","Received failure response [hex] from Plugin Manager","Failure response from plugin mgr","No action is required."
"SYSMGR","4","SYSMGR_VDC_CORE_DELETION","Cores in VDC [dec] will be deleted as part of VDC deletion","VDC cores deleted","No action is required."
"SYSMGR","4","UGRP_ALL_COMPLETED","Upgrade completed for all the groups.","This is a legacy message that can be ignored from Cisco MDS SAN-OS release 1.3(4a).","No action is required."
"SYSMGR","4","VAR_SYSMGR_FULL","System core file storage usage is unexpectedly high at [dec]%. This may cause corruption of core files","System core file storage space is almost full.","Please copy cores off the supervisor and run clearcores'tofreesomespace'"
"SYSMGR","5","CFGERASE_DONE","Configuration erase successful.","The requested configuration erase has completed successfully.","No action is required."
"SYSMGR","5","CFGERASE_STARTED","Configuration erase started (PID [dec]).","The requested configuration erase has started. [dec] is the Process-ID of the process servicing the request.","No action is required."
"SYSMGR","5","CFGINIT_STARTED","Initialization of the startup configuration started (PID [dec]).","The requested initialization of the startup configuration has started. [dec] is the Process-ID of the process servicing the request.","No action is required."
"SYSMGR","5","CFGSNAPSHOT_DONE","Configuration snapshot successful.","The requested configuration snapshot has completed successfully.","No action is required."
"SYSMGR","5","CFGSNAPSHOT_STARTED","Configuration snapshot started (PID [dec]).","The requested configuration snapshot has started. [dec] is the Process-ID of the process servicing the request.","No action is required."
"SYSMGR","5","CFGWRITE_DONE","Configuration copy successful.","The requested configuration copy has completed successfully.","No action is required."
"SYSMGR","5","CFGWRITE_STARTED","Configuration copy started (PID [dec]).","On the active supervisor, this message indicates that the system has started to service a copyrunning-configstartup-config'requestedbytheuser.Onthestandbysupervisor,thismessageindicate sthatthesystemissynchronizingthestartup-configfromtheactivesupervisor.[dec]istheProcess-IDofthe processservicingtherequest.'","No action is required."
"SYSMGR","5","CONVERT_STARTUP_STARTED","Configuration conversion started (PID [dec]).","This message indicates that the system has started conversion of startup configuration. This happens either on system boot or during the course of an upgrade.","No action is required."
"SYSMGR","5","DELETE_BINARY_STARTUP_STARTED","Deletion of binary startup configuration started (PID [dec]).","This message indicates that the system will be deleting the binary startup configuration, due to an error in the conversion of the startup conversion.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","5","FSM_STATE_TRANS","System Manager NESTED state transition from [chars] to [chars].","Recommended Action    No action is required.Error Message      SYSMGR-5-IMPROPER_CLEANUP: Service '[chars]' exited without replying to switchover request. Explanation    A conditional service exited without replying to switchover request. This message is for logging purposes only and does not affect the functionality of the system","No action is required."
"SYSMGR","5","ISSU_ABORT","Notifying services of aborted ISSU (PID [dec]).","This message indicates that the ISSU has been aborted and the services have been asked to rollback any changes.","No action is required."
"SYSMGR","5","ISSU_BEGIN_STARTED","Notifying services of ISSU (PID [dec]).","This message indicates that the system has started notifying services for the ISSU. Services can block the upgrade at this point.","No action is required."
"SYSMGR","5","LC_UPGRADE_REBOOT","Rebooting linecard as a part of upgrade","Linecard is being rebooted as a part of upgrade","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","5","LC_UPGRADE_START","Starting linecard upgrade","Linecard upgrade is starting","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","5","MODULE_ONLINE","System Manager has received notification of local module becoming online.","System Manager has received notification of local module becoming online.","No action is required."
"SYSMGR","5","PARTIAL_CFGWRITE_ASCII_CONFIG","Startup-config version not present.","Startup-config version not present.","Startup-config version is not present. Ascii configuration will be applied."
"SYSMGR","5","PARTIAL_CFGWRITE_DONE","Partial configuration copy successful.","The requested configuration copy has completed successfully.","No action is required."
"SYSMGR","5","PARTIAL_CFGWRITE_STARTED","Partial configuration copy started by UUID [hex] (PID [dec]).","This message is printed only on active supervisor, and indicates that service with mentioned UUID has requested a partial write mem. [dec] is the Process-ID of the process servicing the request.","No action is required."
"SYSMGR","5","RECOVERY_FAILED","Stateful recovery failed, system manager will now start stateless.","Stateful recovery failed, system manager will now restart system and start stateless.","No action is required."
"SYSMGR","5","RUNTIME_DB_RESTORE_STARTED","Runtime database controller started (PID [dec]).","This message indicates that the system has started the restoration of the runtime database. This happens during the non-disruptive fabric switch upgrade.","No action is required."
"SYSMGR","5","RUNTIME_DB_RESTORE_SUCCESS","Runtime database successfully restored.","This message indicates that the runtime database has been successfully restored for the non-disruptive fabric switch upgrade.","No action is required."
"SYSMGR","5","RUNTIME_DB_SAVE_STARTED","Runtime database save has started (PID [dec]).","This message indicates that the system has started the saving of the runtime database. This happens during the non-disruptive fabric switch upgrade.","No action is required."
"SYSMGR","5","SERVICE_DELETED","Service [chars] has been removed from the System Manager database.","This is a legacy message that can be ignored from Cisco MDS SAN-OS release 1.3(4a).","No action is required."
"SYSMGR","5","STATEFUL_STATE","System Manager is in state [chars] after stateful restart.","System Manager has been restarted stateful after an error that resulted in System Manager exiting.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","5","SUBPROC_KILLED","'[chars]' (PID [dec]) hasntcaughtsignal[dec]'[chars]'","This message is for Cisco TAC debugging. This is not a problem or malfunction.","No action is required."
"SYSMGR","5","SUBPROC_TERMINATED","'[chars]' (PID [dec]) has finished with error code [chars] ([dec]).","This message is for Cisco TAC debugging. This is not a problem or malfunction.","No action is required."
"SYSMGR","5","UGRP_COMPLETED","Upgrade completed for group [dec].","This is a legacy message that can be ignored from Cisco MDS SAN-OS release 1.3(4a).","No action is required."
"SYSMGR","6","ALL_SCOPES_STARTED","System services have completely started at this time.","System services have completely started at this time.","No action is required."
"SYSMGR","6","HANDSHAKE_DONE","Handshake with service '[chars]' successfully performed.","This message is for Cisco TAC debugging. This is not a problem or malfunction.","No action is required."
"SYSMGR","6","HANDSHAKE_VERIFYING_DONE","Handshake verification done from service '[chars]'.","Recommended Action    No action is required.Error Message      SYSMGR-6-LC_UPG_DEBUG: LC DEBUG: [chars] Explanation    Linecard upgrade debug message","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"SYSMGR","6","RLIMIT_INFO","rlimit of service '[chars]'([dec]) = %llu","Recommended Action    No action is required.Error Message      SYSMGR-6-SERVICE_STARTED: Service '[chars]' in vdc [dec] started with PID([dec]). Explanation    The System Manager is starting a service. This message is for debugging purposes only.","No action is required."
"SYSMGR","6","SERVICE_SUCCESS_EXIT","Service [chars] (PID [dec]) has successfully exited with exit code [chars] ([dec]).","A service has successfully exited its execution.","No action is required."
"SYSMGR","6","SRVSCOPE_COMPLETED","Completed execution for scope [chars].","This message is for Cisco TAC debugging. This is not a problem or malfunction.","No action is required."
"SYSMGR","6","SRVSCOPE_STARTED","Started execution for scope [chars].","This message is for Cisco TAC debugging. This is not a problem or malfunction.","No action is required."
"SYSMGR","6","SRVSTATE_CHANGED","State for service '[chars]' changed from [chars] to [chars] in vdc [dec].","This message is for Cisco TAC debugging. This is not a problem or malfunction.","No action is required."
"SYSMGR","6","SRV_ENQUEUED_FOR_START","Conditional service '[chars]' started by sap '[dec]' has been enqueued for start.","Recommended Action    No action is required.Error Message      SYSMGR-6-STATE_CHANGED: System Manager state changed from [chars] to [chars] for vdc [dec]. Explanation","No action is required."
"SYSMGR","6","SUBPROC_SUCCESS_EXIT","[chars] (PID [dec]) has successfully exited with exit code [chars] ([dec]).","This message is for Cisco TAC debugging. This is not a problem or malfunction.","No action is required."
"SYSMGR","6","SUPERSTATE_CHANGED","System Manager super state changed from [chars] to [chars] for vdc [dec].","Recommended Action    No action is required.Error Message      SYSMGR-6-UNEXPECTED_GSYNC_RESTART_STANDBY: Sending a message to restart system on standby on vdc [dec]. Explanation    Activity occurred on active supervisor that is incompatible with state of standby. System will be restarted on standby.","No action is required."
"SYSMGR","7","CFGWRITE_UNEXPECTEDRSP","Discarding unexpected response from service '[chars]'.","Recommended Action    No action is required.Error Message      SYSMGR-7-DUPLICATED_PFM_HANDSHAKE: PFM-handshake received from service [chars], but information already available. Explanation    This message is for Cisco TAC debugging. This is not a problem or malfunction.","No action is required."
"SYSMGR","7","LIBCDB_FAILURE","Conversion for service '[chars]' failed in libcdb.","This message indicates that either the system could not find conversion tarball or there is no conversion library needed for this service.","No action is required."
"SYSMGR","7","LIBVDB_FAILURE","Conversion for service '[chars]' failed in libvdb.","This message indicates that the system could not find package information for this service in the version database.","No action is required."
"SYSMGR","7","ND_UPGD_RECOVERY_SRVSUCCEEDED","Service '[chars]' recovered its state during non-disruptive upgrade.","Recommended Action    No action is required.Error Message      SYSMGR-7-NO_STARTUP_CONFIG: No startup-config to convert. Explanation    This message indicates that the system tried to convert startup configuration but it found no configuration to convert.","No action is required."
"SYSMGR","7","SWITCHOVER_SRVSUCCEDED","Service '[chars]' completed its switchover actions.","This message is for Cisco TAC debugging. This is not a problem or malfunction.","No action is required."
"SYSMGR","7","UNEXPECTEDMSG","Opcode [dec] not expected at this time from service '[chars]' ([chars]).","This message is for Cisco TAC debugging. This is not a problem or malfunction.","No action is required."
"SYSMGR","7","UNKNOWNADDR","Opcode [dec] received from unknown source [chars]. Discarding.","This message is for Cisco TAC debugging. This is not a problem or malfunction.","No action is required."
"SYSMGR","7","UNKNOWNMSG","Unknown opcode [dec] received from [chars].","The System Manager has received an unrecognized message with the specified opcode. [chars] is the source of the message. This message is for debugging purposes only.","No action is required."
"SYSMGR","7","UNKNOWNPID","Opcode [dec] received from [chars] with unknown PID [dec]. Discarding.","The System Manager has received a message from an unknown process. [chars] is the source of the message. This message is for debugging purposes only.","No action is required."
"SYSMGR","7","UNKNOWNUUID","Opcode [dec] received from [chars] with unknown UUID [dec]. Discarding.","The System Manager has received an unrecognized message from the specified UUID. [chars] is the source of the message. This message is for debugging purposes only.","No action is required."
"SYSTEMHEALTH","2","OHMS_BATTERY_FAILED","Battery [dec] failed for module [dec]. Reason: [chars].","Battery failed.","No action is required."
"SYSTEMHEALTH","2","OHMS_BOOTFLASH_FAILED_RESET_DAY","Bootflash hard resets for module [dec] has reached threshold limit in 24 hours.","Bootflash hard resets reached threshold limit in 24 hours.","No action is required."
"SYSTEMHEALTH","2","OHMS_BOOTFLASH_FAILED_RESET_LIFE","Bootflash hard resets for module [dec] has reached the maximum threshold limit.","Bootflash hard resets reached maximum threshold limit.","No action is required."
"SYSTEMHEALTH","2","OHMS_BOOTFLASH_FAILED","Bootflash test maximum failures reached for module [dec] Reason: ([chars]).","Bootflash failed.","No action is required."
"SYSTEMHEALTH","2","OHMS_CACHE_DISK_FAILED","Cache disk [dec] failed for module [dec].","Cache disk failed.","No action is required."
"SYSTEMHEALTH","2","OHMS_EMGMT_FAILED","Management port failed for module [dec].","Ethernet management port failed.","No action is required."
"SYSTEMHEALTH","2","OHMS_EOBC_FAILED","EOBC test failed for module [dec].","EOBC test failed for module.","No action is required."
"SYSTEMHEALTH","2","OHMS_FIPS_FAILURE","FIPS compliance error during random number generation.","FIPS compliance error.","No action is required."
"SYSTEMHEALTH","2","OHMS_FREE_DISK_FAILED","Free Disk Space on partition [chars] is below [chars] threshold for module [dec].","System Health Free Disk Space below threshold.","Force a switch over if a standby supervisor is available, or reboot the switch to recover"
"SYSTEMHEALTH","2","OHMS_FREE_DISK_RUNNING","Free Disk Space on partition [chars] have increased and is above [chars] threshold for module [dec].","System Health Free Disk Space above threshold.","No action is required."
"SYSTEMHEALTH","2","OHMS_INBAND_FAILED","Inband test maximum failures reached for module [dec].","Inband failed.","No action is required."
"SYSTEMHEALTH","2","OHMS_MOD_PORT_LB_TEST_FAILED","Module [dec] Port [dec] has failed loop back tests.","Port loop-back test failure.","No action is required."
"SYSTEMHEALTH","2","OHMS_MOD_RELOAD_REQ","Module [dec] reload being requested due to errors found by [chars] test.","System Health Module Reload Request.","No action is required."
"SYSTEMHEALTH","2","OHMS_MOD_SNAKE_TEST_FAILED","Module [dec] has failed snake loopback tests.","Snake test failure.","No action is required."
"SYSTEMHEALTH","2","OHMS_NVRAM_FAILED","Nvram test maximum failures reached for module [dec] for blocks 0x%llx.","Nvram failed.","No action is required."
"SYSTEMHEALTH","2","OHMS_SUP_CF_CRC_FAILED","Compact Flash firmware CRC checksum on module [dec] is corrupted.","Compact flash firmware has been corrupted.","Replace the compact flash on this module."
"SYSTEMHEALTH","2","OHMS_SUP_CF_CRC_INIT_ERRORS","Compact Flash firmware CRC checksum procedure encountered an error during initialization on module [dec], reason:([chars]).","Compact flash CRC checksum initializations failed.","Check the compact flash on the board and any relevant system (mis)configurations."
"SYSTEMHEALTH","2","OHMS_SUP_CF_REFLASH_FAILED","Compact Flash firmware refresh procedure failed, replace the compact flash on module [dec]. Reason [dec]","Compact flash firmware has been corrupted is corrupted.","Replace the compact flash on this module."
"SYSTEMHEALTH","2","OHMS_SWITCHOVER_REQ","Supervisor switch over being requested due to errors found [chars] test.","System Health Switch Over Request.","No action is required."
"SYSTEMHEALTH","2","OHMS_SWITCH_RELOAD_REQ","Switch reload request due to errors found [chars] test.","System Health Switch Reload Request.","No action is required."
"SYSTEMHEALTH","2","OHMS_TCAM_PARITY_FAILED","TCAM test failed for module [dec].","TCAM test failed for module as uncorrectable parity errors were detected.","Please schedule a downtime and replace the module."
"SYSTEMHEALTH","2","OHMS_TCAM_PARITY_OFLOW","Too many TCAM Parity errors detected on module [dec]","More parity errors than that can be corrected were detected on the affected module","Please schedule a downtime and reload the module. If these errors continue to happen even after module reload, please replace the module"
"SYSTEMHEALTH","4","OHMS_BATTERY_ERRORS","Battery test on module [dec] has been suspended due to internal errors.","Battery test internal errors.","No action is required."
"SYSTEMHEALTH","4","OHMS_BOOTFLASH_TEST_ERRORS","Bootflash test cannot proceed due to internal errors on module [dec].","Compact flash test internal errors.","No action is required."
"SYSTEMHEALTH","4","OHMS_CACHE_DISK_ERRORS","Cache disk test on module [dec] dpp [dec] has been suspended due to internal errors.","Cache disk test internal errors.","No action is required."
"SYSTEMHEALTH","4","OHMS_CF_CRC_PASSED","Compact Flash firmware on module [dec] is healthy at this time.","The Compact Flash model has data retention issues and need to be replaced.","Please schedule a downtime and replace the compact flash on this module."
"SYSTEMHEALTH","4","OHMS_CF_REFLASH_PASSED","Compact Flash firmware was successfully refreshed on module [dec].","The Compact Flash model has data retention issues and need to be replaced.","Please schedule a downtime and replace the compact flash on this module."
"SYSTEMHEALTH","4","OHMS_EMGMT_ERRORS","Management port test cannot proceed due to internal errors on module [dec].","Ethernet management port internal errors.","No action is required."
"SYSTEMHEALTH","4","OHMS_EOBC_ERRORS","EOBC test on module [dec] has been suspended due to internal errors.","EOBC test internal errors.","No action is required."
"SYSTEMHEALTH","4","OHMS_EOBC_HALTED","EOBC Test Halted for module [dec]. Module needs EPLD Upgrade","Module does not have the minimum required EPLD version to run EOBC test.","Please upgrade the module with the latest EPLDs.'"
"SYSTEMHEALTH","4","OHMS_EXIT","Online System Health exiting due to internal errors. Reason [dec].","Online System Health exiting due to internal errors.","No action is required."
"SYSTEMHEALTH","4","OHMS_FAIL_ACTION_NOTICE","Failure action not taken, failure action is disabled.","System Health SERDES test failure.","No action is required."
"SYSTEMHEALTH","4","OHMS_FREE_DISK_ERRORS","Too many errors on module [dec] while running the Free Disk Space test for partition [chars].","System Health Free Disk Space test has too many errors while running.","No action is required."
"SYSTEMHEALTH","4","OHMS_FREE_DISK_FAILING","Free Disk Space on partition [chars] is starting to go below threshold for module [dec]","System Health Free Disk Space going below threshold.","Force a switch over if a standby supervisor is available, or reboot the switch to recover"
"SYSTEMHEALTH","4","OHMS_INBAND_FAILING1","Inband test failed [dec] times for module [dec].","Inband Failing.","No action is required."
"SYSTEMHEALTH","4","OHMS_INBAND_TEST_ERRORS","Too many errors while running the inband test.","Inband test has had too many errors while running.","No action is required."
"SYSTEMHEALTH","4","OHMS_LC_DAEMON_EXITED","System Health process running on module [dec] exited due to internal errors. Will attempt to restart.","System Heath line card daemon exited.","No action is required."
"SYSTEMHEALTH","4","OHMS_LC_DAEMON_FAILED","System Health process running on module [dec] failed due to fatal errors.","System Heath line card daemon failed.","No action is required."
"SYSTEMHEALTH","4","OHMS_LC_DAEMON_RESTARTED","System Health process running on module [dec] restarted.","System Heath line card daemon restarted.","No action is required."
"SYSTEMHEALTH","4","OHMS_MOD_SNAKE_PATH_FAILURE","Snake Loopback data path failure on module [dec].","Snake data path only error.","No action is required."
"SYSTEMHEALTH","4","OHMS_MOD_SNAKE_TEST_ERRORS","Snake Loopback test cannot proceed due to internal errors for module [dec].","Snake test internal errors.","No action is required."
"SYSTEMHEALTH","4","OHMS_NVRAM_ERRORS","Too many errors on module [dec] while running the Nvram test.","Nvram test has had too many errors while running.","No action is required."
"SYSTEMHEALTH","4","OHMS_SERDES_FAILED","SERDES loopback test on interface fc[dec]/[dec] failed.","System Health SERDES Test Failure.","No action is required."
"SYSTEMHEALTH","4","OHMS_SUP_BOOTFLASH_ERRORS","Bootflash test has encountered an error on module [dec] Reason:([chars]).","Compact flash test errors on supervisor.","No action is required."
"SYSTEMHEALTH","4","OHMS_SUP_CF_CRC_INTERN_ERRORS","Compact flash firmware CRC checksum procedure cannot proceed due to internal errors on module [dec].","Compact flash firmware CRC checksum procedure ended up in errors.","Try restarting the cf-crc-check using system health clear-errors module <x"
"SYSTEMHEALTH","4","OHMS_SUP_CF_CRC_PROCESS_ERRORS","Compact flash firmware CRC checksum procedure failed on module [dec]. Reason [dec]","Compact flash firmware CRC checksum procedure failed.","Try restarting the cf-crc-check using system health clear-errors module <x"
"SYSTEMHEALTH","4","OHMS_SUP_CF_CRC_TEST_FAILING","Compact flash firmware CRC checksum validation starting to fail on module [dec].","Compact flash firmware CRC checksum might be bad on this module.","Schedule a downtime and replace the compact flash on the affected module. Do not attempt any hitless up/downgrades."
"SYSTEMHEALTH","4","OHMS_SUP_CF_RECALLED","Compact Flash on module [dec] was recalled.","The Compact flash model has data retention issues and need to be replaced.","Please schedule a downtime and replace the compact flash on this module."
"SYSTEMHEALTH","4","OHMS_SUP_CF_REFLASH_INTERN_ERRORS","Compact Flash firmware re-flash procedure cannot proceed due to internal errors on module [dec].","Compact flash firmware re-flash procedure ended up in errors.","Try restarting the test using system health clear-errors module <x"
"SYSTEMHEALTH","4","OHMS_SUP_CF_REFLASH_TEST_FAILING","Compact flash firmware refresh procedure starting to fail on module [dec].","Compact flash might be dead on this module.","Schedule a downtime and replace the compact flash on the affected module. Do not attempt any hitless up/downgrades."
"SYSTEMHEALTH","4","OHMS_SUP_CF_UNRESPONSIVE","Recalled Compact Flash on module [dec] is unresponsive.","The Compact flash model has data retention issues and need to be replaced.","Please schedule a downtime and replace the compact flash on this module."
"SYSTEMHEALTH","4","OHMS_SVC_DAEMON_FAILED","System Health process running on module [dec] SVC node [dec] exited due to errors.","OHMS SVC daemon exited.","No action is required."
"SYSTEMHEALTH","4","OHMS_TCAM_PARITY_ACL_FIB_TIMEOUT","TCAM test timeout waiting for ACL/FIB to update TCAM on module [dec]","System health TCAM test timeout occured while waiting for response from ACL/FIB","If significant packet drops are encountered in the forwarding engine, please schedule a downtime and reload the module"
"SYSTEMHEALTH","4","OHMS_TCAM_PARITY_ACL_FIB_UPDATE_FAILING","Tcam test failed as ACL/FIB failed to update TCAM on module [dec]","ACL/FIB failed to update TCAM after soft parity errors were encountered.","If significant packet drops are encountered in the forwarding engine, please schedule a downtime and reload the module"
"SYSTEMHEALTH","4","OHMS_TCAM_PARITY_ERRORS","TCAM test on module [dec] has been suspended due to internal errors.","TCAM test internal errors.","No action is required."
"SYSTEMHEALTH","5","OHMS_BATTERY_FAILING","Battery [dec] starting to fail on module [dec]. Reason: [chars].","System Health battery failing.","No action is required."
"SYSTEMHEALTH","5","OHMS_BOOTFLASH_FAILING","Bootflash starting to fail on module [dec].","System Health bootflash failing.","No action is required."
"SYSTEMHEALTH","5","OHMS_CDISK_FAILING","Cache disk [dec] starting to fail on module [dec].","System Health cache disk failing.","No action is required."
"SYSTEMHEALTH","5","OHMS_EMGMT_FAILING","Management port on module [dec] starting to show signs of failures.","System Health emgmt failing.","No action is required."
"SYSTEMHEALTH","5","OHMS_EOBC_FAILING","EOBC starting to fail on module [dec].","System Health eobc failing.","No action is required."
"SYSTEMHEALTH","5","OHMS_INBAND_FAILING","Inband starting to fail on module [dec].","System Health inband failing.","No action is required."
"SYSTEMHEALTH","5","OHMS_NVRAM_FAILING","Nvram starting to fail on module [dec].","System Health Nvram failing.","No action is required."
"SYSTEMHEALTH","5","OHMS_SUP_CF_ERRORS_CLEARED","Compact flash failing conditions on module [dec] has been cleared.","Compact flash might be dead on this module.","Schedule a downtime and replace the compact flash on the affected module. Do not attempt any hitless up/downgrades."
"SYSTEMHEALTH","5","OHMS_TCAM_PARITY_CLEARED","Failing conditions for TCAM on module [dec] have been cleared.","System Health TCAM failures cleared.","No action is required."
"SYSTEMHEALTH","5","OHMS_TCAM_PARITY_FAILING","TCAM starting to fail on module [dec].","System Health Tcam failing.","No action is required."
"SYSTEMHEALTH","5","OHMS_TEST_FAILING","[chars] test starting to fail on module [dec].","System Health test failing.","No action is required."
"SYSTEMHEALTH","6","OHMS_ASIC_FAILURE_INFO","Module [dec] Asic [chars] instance [dec] probable cause of failure.","HW failure analysis findings.","No action is required."
"SYSTEMHEALTH","6","OHMS_BATTERY_CLEARED","Failing conditions for battery [dec] on module [dec] have been cleared.","System Health battery failure cleared.","No action is required."
"SYSTEMHEALTH","6","OHMS_BOOTFLASH_CLEARED","Failing conditions for bootflash on module [dec] have been cleared.","System Health bootflash failures cleared.","No action is required."
"SYSTEMHEALTH","6","OHMS_CDISK_CLEARED","Failing conditions for cache disk [dec] on module [dec] have been cleared.","System Health cache disk failure cleared.","No action is required."
"SYSTEMHEALTH","6","OHMS_EMGMT_CLEARED","Failing conditions for management port on module [dec] have been cleared.","System Health emgmt failure cleared.","No action is required."
"SYSTEMHEALTH","6","OHMS_EOBC_CLEARED","Failing conditions for EOBC on module [dec] have been cleared.","System Health eobc failures cleared.","No action is required."
"SYSTEMHEALTH","6","OHMS_FAILURE_CLEARED","Failing conditions for test [chars] have been cleared on module [dec].","System Health failure cleared.","No action is required."
"SYSTEMHEALTH","6","OHMS_INBAND_CLEARED","Failing conditions for inband on module [dec] have been cleared.","System Health inband failures cleared.","No action is required."
"SYSTEMHEALTH","6","OHMS_INBAND_DROP","Inband Dropping frames from module [dec] due to unknown reasons.","System Health Inband non-timeout drop.","No action is required."
"SYSTEMHEALTH","6","OHMS_INBAND_TO_ERR","Inband Dropping frames from module [dec] due to timeout errors.","System Health Inband timeout drop.","No action is required."
"SYSTEMHEALTH","6","OHMS_INBAND_TX_CONGESTION","Inband Unable to transmit due to TX path congestion on module [dec].","System Health Inband TX congestion.","No action is required."
"SYSTEMHEALTH","6","OHMS_NVRAM_CLEARED","Failing conditions for Nvram on module [dec] have been cleared.","System Health Nvram failures cleared.","No action is required."
"SYSTEMHEALTH","6","OHMS_STARTED","Online System Health started.","Online System Health started.","No action is required."
"TACACS","2","TACACS_PROGRAM_EXIT","TACACS+ daemon exiting: [chars]","TACACS+ daemon is exiting.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"TACACS","3","TACACS_ERROR_MESSAGE","[chars]","TACACS+ Error Message","No action is required."
"TACACS","4","TACACS_WARNING","[chars]","TACACS+ warning","No action is required."
"TACACS","5","TACACS_MONITOR_STATUS","[chars] [chars]","Notifying Tacacs+ server monitor status change","No action is required."
"TACACS","5","TACACS_NOTIFICATION","[chars]","TACACS+ notification","No action is required."
"TACACS","5","TACACS_SERVER_STATUS","[chars] server [chars] with auth-port [dec] and acct-port [dec] status has changed from [chars] to [chars]. Server was in previous-state for [chars], and total dead time of the server is [chars]","Notifying Tacacs+ server status change","No action is required."
"TACACS","6","TACACS_ACCOUNTING_MESSAGE","[chars]","Accounting Message","No action is required."
"TACACS","6","TACACS_MESSAGE","[chars]","TACACS+ Message","No action is required."
"TBIRD_CMN_USD","6","TBIRD_CMN_DEBUG_MSG","[chars]","Debug log message","No action is required."
"TBIRD_FWD_USD","6","TBIRD_FWD_DEBUG_MSG","[chars]","Debug log message","No action is required."
"TBIRD_MAC_USD","3","FCMAC_ERR_MSG","[chars]","Error log message","No action is required."
"TBIRD_MAC_USD","6","FCMAC_DEBUG_MSG","[chars]","Debug log message","No action is required."
"TBIRD_QUE_USD","6","TBIRD_QUE_DEBUG_MSG","[chars]","Debug log message","No action is required."
"TBIRD_XBAR_USD","6","TBIRD_XBAR_DEBUG_MSG","[chars]","Debug log message","No action is required."
"TCAP","2","MEM_FULL","Memory allocation failed.","TCAP process has failed to allocate memory.","Please perform a showtcapevent-history'tocollectmoreinformation.'"
"TCAP","2","PROC_DN","Process is shutting down: [chars]","TCAP process is exiting.","Please perform a showtcapevent-history'tocollectmoreinformation.'"
"TCAP","2","PROC_INITFAIL","Process initialization failed due to [chars].","TCAP process has failed initialization.","Please perform a showtcapevent-history'tocollectmoreinformation.'"
"TIM","2","IF_CRITICAL_FAILURE","(Debug syslog)Critical failure: [chars], [chars]","There was a critical failure in the component.","Please follow instructions on the syslog."
"TIM","2","IF_DOWN_ERROR_DISABLED","Interface [chars] is down (Error disabled. Reason:[chars])","The interface encountered an error while configuring it","Collect more information about failed interface using command showportinternalallinterface[char]'.Inmostcases,youcanrecoverusinga'shutdown'followeda'noshutd own'ontheinterfaceorremovingandre-insertingthefibreopticcable.'"
"TIM","2","IF_DOWN_LINK_FAILURE_CRIT","Interface [chars] is down (Link failure)","The physical link has gone down","Ensure that the cable is connected and the remote end is not shut down"
"TIM","2","SEQ_TIMEOUT","Component [chars] timed out on response to opcode [chars] ([chars])","Some component did not respond to a request in stipulated time.","None"
"TIM","2","SYSLOG_TIM_CRITICAL","Critical failure: [chars]","There was a critical failure in the component.","Please collect system tech-support"
"TIM","3","IF_DOWN_CHANNEL_ERR_DISABLED","Interface [chars] is down (Channel error disabled)","This interface belongs to a PortChannel and the PortChannel is error disabled","Perform shut'and'noshutdown'onthePortChannelinterfacethatitbelongsto'"
"TIM","3","IF_ERROR_VLANS_REMOVED","VLANs [chars] on Interface [chars] are removed from suspended state.","The VLANs on an interface are being removed from the suspended state","No action is required."
"TIM","3","IF_ERROR_VLANS_SUSPENDED","VLANs [chars] on Interface [chars] are being suspended. (Reason: [chars])","The VLANs on an interface are being suspended due to some protocol action","No action is required."
"TIM","3","IF_SFP_ALARM","Interface [chars], [chars]","There was an alarm on the transceiver module","Please do show interface transceiver details to obtain more information"
"TIM","3","IF_SFP_ERROR","Interface [chars], [chars]","There was an error on the transceiver module","Please do show interface transceiver details to obtain more information"
"TIM","3","IF_UNSUPPORTED_TRANSCEIVER","Transceiver on interface [chars] is not supported","The transceiver for the interface specified in the error message is not a Cisco supported module","Replace the module with a compatible transceiver. If the transceiver was purchased from Cisco, please contact Cisco TAC to get the transceiver replaced"
"TIM","3","IF_XCVR_ALARM","Interface [chars], [chars]","There was an alarm on the transceiver module","Please do show interface transceiver details to obtain more information"
"TIM","3","IF_XCVR_ERROR","Interface [chars], [chars]","There was an error on the transceiver module","Please do show interface transceiver details to obtain more information"
"TIM","4","IF_NON_QUALIFIED_TRANSCEIVER","Non-qualified transceiver on interface [chars] was detected","The transceiver for the interface specified has not been qualified on this platform for this software release","Replace the module with a supported transceiver. Contact Cisco TAC to get platform transceiver qualification details"
"TIM","4","IF_SFP_WARNING","Interface [chars], [chars]","There was an warning on the transceiver module","Please do show interface transceiver details to obtain more information"
"TIM","4","IF_XCVR_WARNING","Interface [chars], [chars]","There was an warning on the transceiver module","Please do show interface transceiver details to obtain more information"
"TIM","5","IF_ADMIN_UP","Interface [chars] is admin up [chars]","Interface is admin up","No action is required."
"TIM","5","IF_BANDWIDTH_CHANGE","Interface [chars],bandwidth changed to [chars] Kbit","Bandwidth of the interface (port channel) has changed and this change is updated","No action is required."
"TIM","5","IF_DOWN_ADMIN_DOWN","Interface [chars] is down (Administratively down)","Interface has been configured to be administratively down","Perform noshutdown''"
"TIM","5","IF_DOWN_CFG_CHANGE","Interface [chars] is down(Config change)","FCIP interface temporarily down due to reconfiguration","No action is required."
"TIM","5","IF_DOWN_CHANNEL_ADMIN_DOWN","Interface [chars] is down (Channel admin down)","This interface belongs to a PortChannel and the PortChannel is configured to be administratively down","Perform noshutdown'onthePortChannelinterfacethatitbelongsto'"
"TIM","5","IF_DOWN_CHANNEL_MEMBERSHIP_UPDATE_IN_PROGRESS","Interface [chars] is down (Channel membership update in progress)","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","Retry the configuration again"
"TIM","5","IF_DOWN_DOMAIN_ADDR_ASSIGN_FAILURE_ISOLATION","Interface [chars] is down (Isolation due to domain id assignment failure)","Isolated due to a failure while assigning a domain","No action is required."
"TIM","5","IF_DOWN_DOMAIN_INVALID_RCF_RECEIVED","Interface [chars] is down (Isolation due to invalid fabric reconfiguration)","Invalid RCF received","No action is required."
"TIM","5","IF_DOWN_DOMAIN_MANAGER_DISABLED","Interface [chars] is down (Isolation due to domain manager disabled)","Isolated due to domain manager being disabled","No action is required."
"TIM","5","IF_DOWN_DOMAIN_MAX_RETRANSMISSION_FAILURE","Interface [chars] is down (Isolation due to domain manager other side not responding)","Remote end domain manager not responding","No action is required."
"TIM","5","IF_DOWN_DOMAIN_OTHER_SIDE_EPORT_ISOLATED","Interface [chars] is down (Isolation due to domain other side eport isolated)","Isolating this interface due to the remote end being isolated","No action is required."
"TIM","5","IF_DOWN_DOMAIN_OVERLAP_ISOLATION","Interface [chars] is down (Isolation due to domain overlap)","Isolated due to domain overlap","No action is required."
"TIM","5","IF_DOWN_ELP_FAILURE_ISOLATION","Interface [chars] is down (Isolation due to ELP failure)","ELP failed on the interface","Check the output of showportinternalinfo'inthe'ELPfailurereason'field'"
"TIM","5","IF_DOWN_EPP_FAILURE","Interface [chars] is down (Error Disabled - EPP Failure)","Trunk protocol failed","showportinternalevent-historymsgs'willindicatethetrunkprotocolexchangestodeterminewhyitfailed'"
"TIM","5","IF_DOWN_ESC_FAILURE_ISOLATION","Interface [chars] is down (Isolation due to ESC failure)","ESC failed on the interface","Check the output of showportinternalevent-history'todeterminetheESCprotocolexchangestodeterminehowitfailed'"
"TIM","5","IF_DOWN_ETH_IF_DOWN","Interface [chars] is down(Tunnel port src interface down)","Ethernet link to which the FCIP interface is bound is down","Ensure that the ethernet cable is connected, the interface is administratively enabled"
"TIM","5","IF_DOWN_ETH_LINK_DOWN","Interface [chars] is down(Tunnel port src interface link down)","Ethernet link to which the FCIP interface is bound is down","Ensure that the ethernet cable is connected and the remote end is also active"
"TIM","5","IF_DOWN_FCOT_NOT_PRESENT","Interface [chars] is down (FCOT not present)","The FCOT has been removed","Insert an FCOT"
"TIM","5","IF_DOWN_FCOT_VENDOR_NOT_SUPPORTED","Interface [chars] is down (Error disabled - Fcot vendor not supported)","Fcot inserted is not a supported one","Please contact customer support for a list of authorized transceiver vendors"
"TIM","5","IF_DOWN_HW_FAILURE","Interface [chars] is down (Hardware Failure)","The moduleshardwarehasfailed'","Collect more information about failed module using command showmoduleinternalallmodule''"
"TIM","5","IF_DOWN_INACTIVE","Interface [chars] is down (Inactive)","The port VSAN has been suspended or deleted","Assign a new active port VSAN to the interface"
"TIM","5","IF_DOWN_INCOMPATIBLE_ADMIN_MODE","Interface [chars] is down (Error disabled - Incompatible admin port mode)","The configured mode is not supported on this interface","Perform a showportinternalinfo'todeterminethelistofmodessupportedonthisinterface'"
"TIM","5","IF_DOWN_INCOMPATIBLE_ADMIN_RXBBCREDIT","Interface [chars] is down (Error disabled - Incompatible admin port rxbbcredit)","The configured receive B2B credit size is not supported","Get the allowed receive B2B credit size from showportinternalinfo''"
"TIM","5","IF_DOWN_INCOMPATIBLE_ADMIN_RXBUFSIZE","Interface [chars] is down (Error disabled - Incompatible admin port rxbufsize)","The configured receive buffer size is not supported","Get the allowed receive buffer size from showportinternalinfo''"
"TIM","5","IF_DOWN_INCOMPATIBLE_ADMIN_SPEED","Interface [chars] is down (Error disabled - Incompatible admin port speed)","The configured speed is not supported on this interface","Perform a showportinternalinfo'todeterminetherangeofspeedsupportedonthisinterface'"
"TIM","5","IF_DOWN_INITIALIZING","Interface [chars] is down (Initializing)","The interface is in the process of coming up","If the interface is stuck in this state for a while, check the output of showportinternalevent-history'todeterminewhatitiswaitingfor'"
"TIM","5","IF_DOWN_INTERFACE_REMOVED","Interface [chars] is down (Interface removed)","Interface removed","No action is required."
"TIM","5","IF_DOWN_LINK_FAILURE","Interface [chars] is down (Link failure)","The physical link has gone down","Ensure that the cable is connected and the remote end is not shut down"
"TIM","5","IF_DOWN_LOOPBACK_DIAG_FAILURE","Interface [chars] is down (Diag failure)","Diag failed on the interface","Collect more information about failed interface using command attachmodule'toconnecttomodule'"
"TIM","5","IF_DOWN_LOOPBACK_ISOLATION","Interface [chars] is down (Isolation due to port loopback to same switch)","The interface is looped back to another interface on the same switch","Check the connectivity of this interface and ensure that it is connected to another switch"
"TIM","5","IF_DOWN_MODULE_REMOVED","Interface [chars] is down (module removed)","Interface is down because the module was removed","No action is required."
"TIM","5","IF_DOWN_NONE","Interface [chars] is down ([chars])","Interface is down with a possible reason.","Collect more information about port using command showportinternalinfo/event-history'todeterminewhyitwentdown'"
"TIM","5","IF_DOWN_NON_PARTICIPATING","Interface [chars] is down (Non participating)","The loop port has been put into non participating mode","No action is required."
"TIM","5","IF_DOWN_OFFLINE","Interface [chars] is down (Offline)","The interface has been placed into the offline state","No action is required."
"TIM","5","IF_DOWN_PARENT_ADMIN_DOWN","Interface [chars] is down (Parent interface down)","Parent interface is down","No action is required."
"TIM","5","IF_DOWN_PEER_CLOSE","Interface [chars] is down(TCP conn. closed by peer)","The FCIP peer connected to this interface closed the TCP connection","This command will provide the peer IP address of this FCIP interface: show interface. Check to see why the peer closed the TCP connection"
"TIM","5","IF_DOWN_PEER_RESET","Interface [chars] is down(TCP conn. reset by peer)","TCP connection to the FCIP peer got reset","The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Check to see why the peer reset the TCP connection"
"TIM","5","IF_DOWN_PORT_CHANNEL_MEMBERS_DOWN","Interface [chars] is down (No operational members)","This is a PortChannel interface and all its members are operationally down","Enable at least one of the PortChannelsmembers'"
"TIM","5","IF_DOWN_PORT_VSAN_MISMATCH_ISOLATION","Interface [chars] is down (Isolation due to port vsan mismatch)","Isolated due to a mismatch in the configured port VSAN of the local and remote ends","Configure the port VSAN of the local and remote interfaces to be the same and perform a shutdown'anda'noshutdown''"
"TIM","5","IF_DOWN_RCF_IN_PROGRESS","Interface [chars] is down (RCF in progress)","There is an RCF in progress","No action is required."
"TIM","5","IF_DOWN_SOFTWARE_FAILURE","Interface [chars] is down (Port software failure)","The software servicing the data path on the port has failed","No action is required."
"TIM","5","IF_DOWN_SRC_MOD_NOT_ONLINE","Interface [chars] is down(Tunnel source module not online)","Module that has the tunnel source port of this FCIP interface is not fully online","The module that has the tunnel src port is coming online. Please use show mod to find module status"
"TIM","5","IF_DOWN_SRC_PORT_NOT_BOUND","Interface [chars] is down (Tunnel port src interface unbound)","Tunnel port source interface unbound","No action is required."
"TIM","5","IF_DOWN_SRC_PORT_REMOVED","Interface [chars] is down(Tunnel src port removed)","Tunnel source port of this FCIP interface has been removed","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"
"TIM","5","IF_DOWN_SUSPENDED_BY_MODE","Interface [chars] is down (Suspended due to incompatible mode)","This interface belongs to a PortChannel and operational mode of the interface is different from that of the PortChannel","Change the mode and the trunking mode of the PortChannel from auto'andchecktoensurethattheremoteendoftheinterfacealsobelongstothesamePortChannel'"
"TIM","5","IF_DOWN_SUSPENDED_BY_SPEED","Interface [chars] is down (Suspended due to incompatible speed)","This interface belongs to a PortChannel and operational speedode of the interface is different from that of the PortChannel","Change the speed of the PortChannel from auto'andchecktoensurethattheremoteendoftheinterfacealsobelongstothesamePortChannel'"
"TIM","5","IF_DOWN_SUSPENDED_BY_WWN","Interface [chars] is down (Suspended due to incompatible remote switch WWN)","This interface belongs to a PortChannel and remote switch WWN of the interface is different from that of the PortChannel","Ensure that this interface is connected to the same remote switch as all the other interfaces in the PortChannel"
"TIM","5","IF_DOWN_SUSPENDED","Interface [chars] is down (Suspended)","This interface belongs to a PortChannel and has been suspended due to an error while bringing it up","Perform a shutdown'anda'noshutdown'.Ifthishappensagainobtainoutputof'showportinternalinfo/event-history' ontheinterface'"
"TIM","5","IF_DOWN_TCP_KEEP_ALIVE_EXPIRED","Interface [chars] is down(TCP conn. closed - Keep alive expired)","TCP session to the FCIP peer got closed due to loss of TCP keep alive","This may be due to loss of IP connectivity. The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Please do a trace route to check the connectivity to the peer using command:traceroute ipaddr"
"TIM","5","IF_DOWN_TCP_MAX_RETRANSMIT","Interface [chars] is down(TCP conn. closed - retransmit failure)","Interface is down due to maximum retransmission failure","This may be due to loss of IP connectivity. The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Please do a trace route to check the connectivity to the peer using command:traceroute ipaddr"
"TIM","5","IF_DOWN_TCP_PERSIST_TIMER_EXPIRED","Interface [chars] is down(TCP conn. closed - Persist timer expired)","TCP session to the FCIP peer closed because TCP persist timer expired","This may be due to loss of IP connectivity. The following commands will provide the IP address of the peer and the route used connect to this FCIP peer: show interface, show ip route. Please do a trace route to check the connectivity to the peer using command:traceroute ipaddr"
"TIM","5","IF_DOWN_UPGRADE_IN_PROGRESS","Interface [chars] is down (Linecard upgrade in progress)","Upgrade of the linecard software is in progress","No action is required."
"TIM","5","IF_DOWN_VRF_UNUSABLE","Interface [chars] is down (Vrf down)","The vrf for which this interface is a member is removed","No action is required."
"TIM","5","IF_DOWN_VSAN_MISMATCH_ISOLATION","Interface [chars] is down (Isolation due to vsan mismatch)","This is a trunking interface and the VSANs configured do not match with the VSANs configured on the remote end","Check the VSANs configured on the local end with the remote end"
"TIM","5","IF_DOWN_ZONE_MERGE_FAILURE_ISOLATION","Interface [chars] is down (Isolation due to zone merge failure)","Isolated due to a failure during zone merge","No action is required."
"TIM","5","IF_DOWN_ZONE_REMOTE_NO_RESP_ISOLATION","Interface [chars] is down (Isolation due to remote zone server not responding)","Isolated due to remote zone server not responding","No action is required."
"TIM","5","IF_DUPLEX","Interface [chars], operational duplex mode changed to [chars]","Operational duplex mode has changed when link came up","No action is required."
"TIM","5","IF_ERRDIS_RECOVERY","Interface [chars] is being recovered from error disabled state (Last Reason:[chars])","Interface is being recovered from error disabled state","No action is required."
"TIM","5","IF_HARDWARE","Interface [chars], hardware type changed to [chars]","There was a change in the hardware characteristic of an interface, such as a transceiver module plugged in or removed","No action is required."
"TIM","5","IF_L2MP_MODE","Interface [chars], l2mp-mode changed to [chars]","The l2mp-mode on the port has changed","No action is required."
"TIM","5","IF_RX_FLOW_CONTROL","Interface [chars], operational Receive Flow Control state changed to [chars]","Operational receive flow control has changed when link came up","No action is required."
"TIM","5","IF_TRUNK_DOWN","Interface [chars], vlan [chars] down","Interface [chars] is trunking, VLANs [chars] are down","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"
"TIM","5","IF_TRUNK_UP","Interface [chars], vlan [chars] up","Interface [chars] is trunking, VLANs [chars] are up","No action is required."
"TIM","5","IF_TX_FLOW_CONTROL","Interface [chars], operational Transmit Flow Control state changed to [chars]","Operational transmit flow control has changed when link came up","No action is required."
"TIM","5","IF_UP","Interface [chars] is up [chars]","Interface is up in mode specified, if applicable","No action is required."
"TIM","5","SPEED","Interface [chars], operational speed changed to [chars]","Operational speed has changed when link came up","No action is required."
"TIM","5","STORM_CONTROL_ABOVE_THRESHOLD","Traffic in port [chars] exceeds the configured threshold [chars]","Traffic on specified port is beyond the configured storm-control threshold, and the excess traffic is being dropped","Identify source of traffic storm"
"TIM","5","STORM_CONTROL_BELOW_THRESHOLD","Traffic in port [chars] has fallen below the configured threshold [chars]","Traffic on specified port has returned to within configured storm-control threshold","No action is required."
"TLPORT","2","INITFAIL","TL Port Manager Initialization failed: [chars]","TL Port Manager initialization failed. [chars] explains the reason for the failure.","No action is required."
"TLPORT","3","ALLOCFAIL","Heap Memory allocation failed: [chars]","TL Port Manager is out of dynamic memory. [chars] specifies the context where the failure occured.","No action is required."
"TLPORT","3","FC2ERROR","[chars]","TL Port Manager encountered an FC2 error. [chars] specifies the context where the error occured.","No action is required."
"TLPORT","3","GENERROR","[chars]","TL Port Manager encountered a general error, one that does not fall in any of the above categories. [chars] describes the error and its context.","No action is required."
"TLPORT","3","MTSERROR","[chars]","TL Port Manager encountered an MTS error. [chars] specifies the context where the error occured.","No action is required."
"TLPORT","3","PSSERROR","[chars]","TL Port Manager encountered a PSS error. [chars] specifies the context where the failure occured.","No action is required."
"TLPORT","4","TLPM_ALPA_CACHE_FULL","Translation Port ALPA cache is full. Some new entries may not be cached","TL Port cache is currently fully populated with active entries. Hence, there is no available cache space to be assigned any newly created alpa entry on a TL Port. This is an informational message.","No action is required."
"TLPORT","6","MGRCREATED","Translation Port Manager created.","TL Port Manager was created successfully and is up and running. This is an informational message.","No action is required."
"TLPORT","6","MGREXIT","Translation Port Manager shutting down gracefully.","TL Port Manager is shutting down gracefully. This is an informational message.","No action is required."
"TLPORT","6","PORTDOWN","Translation Port [chars] DOWN.","A port configured as TL Port is DOWN and out of operation. [chars] is the interface-id string that identifies the TL Port. This is an informational message.","No action is required."
"TLPORT","6","PORTUP","Translation Port [chars] UP.","A port configured as TL Port is UP and operational. [chars] is the interface-id string that identifies the TL Port. This is an informational message.","No action is required."
"TPC-SLOT#","5","LOG_ERR_TPC_DPP_DEAD","VSAN :[dec] VT pWWN :[chars] DPP died","The DPP associated with the Virtual Target has crashed","No action is required."
"TPC-SLOT#","5","LOG_ERR_TPC_VT_ACT_FAILED","VSAN :[dec] VT pWWN :[chars] VT Activate failed","The activate step for a Virtual Target has failed","No action is required."
"TPC-SLOT#","5","LOG_ERR_TPC_VT_CREATE_FAIL","VSAN :[dec] VT pWWN :[chars] VT and NPort creation FAILED !!!","The Virtual Target and nport creation failed","No action is required."
"TPC-SLOT#","5","LOG_ERR_TPC_VT_DESTROYED","VSAN :[dec] Virtual Target : [chars] Deleted","The Virtual Target in the associated VSAN is being destroyed","No action is required."
"TPC-SLOT#","5","LOG_ERR_TPC_VT_VSAN_DOWN","VSAN :[dec] VT pWWN :[chars] VSAN down","The VSAN where the Virtual Target is configured is down","No action is required."
"TTYD","2","TTYD_ERROR","TTYD Error [chars]","Critical TTY daemon error.","No action is required."
"TTYD","2","TTYD_MTS","TTYD Message queue [dec] [chars]","TTY daemon message error.","No action is required."
"TTYD","2","TTYD_SDWRAP","TTYD Debug Facility error [dec] [chars]","TTY daemon Debug Facility failed.","No action is required."
"TTYD","3","TTYD_MISC_ERROR","Error [chars] with error [chars]([hex])","TTY daemon errors.","No action is required."
"TTYD","6","TTYD_MISC","TTYD [chars]","The tty daemon miscellaneous message.","No action is required."
"TTYD","6","TTYD_PSS","TTYD Store error:[hex] [chars]","Failed to store configuration for TTY service.","No action is required."
"TUNNEL","2","FEATURE_ENABLE_FAILED","failed to enable feature tunnel, reason [chars] ([hex])","Failed to enable feature tunnel, reason [char] ([int])","Check the failure reason and take appropriate action to fix the failure. if unable to fix, please capture 'show tech-support tunnel'"
"TUNNEL","2","TM_F2_ONLY_VDC","Tunnel feature is not supported in F2 only VDC","Tunnel feature is not supported in F2 only VDCError Message     Disable the Tunnel feature by the CLI 'no feature tunnel' TUNNEL-3Error Message      TUNNEL-3-HW_PROGRAMMING_FAILED: for [chars], reason [chars] Explanation    Hardware programming failed for tunnel [num] interface","Try shutdown'and'noshutdown'undertunnelinterfacesubmodeaftersometime.ifstilltunnelinterfacedoesn't comeupcaptureshowtech-supporttunneltoidentifytheissue'"
"TUNNEL","4","TM_DF_PROGRAMMING_FAILED","[chars] DF(dont fragment) programming failed! status [hex]","[chars] DF programming failed! status [int]","Capture 'show tech-support tunnel ' to identify why df flag programing failed"
"TUNNEL","4","TM_DF_PROGRAMMING","Programming [chars] DF(dont fragment) df.sel [dec] df.val [dec]","Programming [chars] DF df.sel [int] df.val [int]","No action is required."
"TUNNEL","4","TM_MTU_PROGRAMMING_FAILED","[chars] mtu [dec] programming failed! status [hex]","[chars] mtu [int] programming failed! status [int]","Capture show 'tech-support tunnel' to identify why MTU programming as failed. tunnel interface will used default mtu value"
"TUNNEL","4","TM_MTU_PROGRAMMING","Programming [chars] mtu [dec]...","Programming [chars] mtu [int]","No action is required."
"TUNNEL","5","IF_CLEAR_COUNTER","Interface [chars] counters is cleared","Interface [char] counters is cleared","No action is required."
"TUNNEL","5","IF_CREATED","Interface [chars] is created","Interface [char] is created","No action is required."
"TUNNEL","5","IF_CREATE_FAILED","Interface [chars] creation failed due to [[hex]] [chars]","Interface [char] is creation failed due to [int] [char]","No action is required."
"TUNNEL","5","IF_DELETED","Interface [chars] is deleted","Interface [char] is deleted","No action is required."
"TUNNEL","5","IF_STATE_UPDATE","Interface [chars] is [chars] reason [chars]","Interface [char] is [char] reason [char]","No action is required."
"TUNNEL","5","PPF_SESSION_FAILED","session id %llx type [chars] for [chars] failed error [hex] [chars]","Session id [int] type [char] for [char] failed error [int] [char]","No action is required."
"TUNNEL","5","TM_DISABLED","Tunnel Disabled","Tunnel Service Disabled","No action is required."
"TUNNEL","5","TM_ENABLED","Tunnel Enabled","Tunnel Service Enabled","No action is required."
"TUNNEL","7","TM_INFO","[chars]","Tunnel Service info","No action is required."
"TUSCANY_APP-SLOT#","2","TUSCANY_APP_EXITED","Tuscany driver application exited (syserr = [dec], errno = [dec])","Tuscany driver application exited","No action is required."
"U2RIB","2","IPC_PROCESSING_ERR","Error in processing IPC message : Opcode = [dec], Error code = [hex]","U2RIB encountered an error in processing an MTS message. The error and message are specified in the error message","No action is required."
"U2RIB","2","U2RIB_INIT","U2RIB initialization of [chars] [chars]","U2RIB initialization failed","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"U2RIB","3","U2RIB_LD_BLNCE_ERROR","Error in config. lb parameters using the DCEFIB Library, error code = [hex], [chars]","Error while communicating with the dcefib library","No action is required."
"U2RIB","5","U2RIB_DISABLED","U2RIB Disabled","U2RIB Service Disabled","No action is required."
"U2RIB","5","U2RIB_ENABLED","U2RIB Enabled","U2RIB Service enabled","No action is required."
"U2RIB","6","STATE_CREATED","Internal state created [chars]","U2RIB has created its internal state stateless/stateful [chars].","No action is required."
"UDLD","3","IDB_ERROR","UDLD error handling [chars] interface: [chars]","A softare error occurred in UDLD processing associated with a specific interface.","LOG_STD_SH_TECH_ACTION"
"UDLD","3","MSG_SEND_FAILURE","failed to send [chars] to sap [dec]: [chars]","Failed to send a message","LOG_STD_SH_TECH_ACTION"
"UDLD","3","UDLD_INTERNAL_ERROR","UDLD internal error: [chars]","A softare sanity check failed in the course of UDLD processing.","LOG_STD_SH_TECH_ACTION"
"UDLD","3","UDLD_INTERNAL_IF_ERROR","UDLD internal error, interface [chars]: [chars]","A softare sanity check failed in the course of UDLD processing.","LOG_STD_SH_TECH_ACTION"
"UDLD","4","UDLD_GWRAP_COUNT","UDLD gwrap count is %lu, please log a 'show tech udld' for detail info.","UDLD gwrap count reached high level, show tech udld is needed to debug it.","LOG_STD_SH_TECH_ACTION"
"UDLD","4","UDLD_NEIGHBOR_MISMATCH","UDLD neighbor mismatch detected, exp: [chars], rec [chars]. Please collect debug info using: http://zed.cisco.com/confluence/display/KGP/UDLD+debug","An interface will be disabled because UDLD protocol detected a nieghbor mismatch condition on the interface indicated. Cause is likely due to bad interface hardware or cable misconfiguration. User should investigate.","LOG_STD_SH_TECH_ACTION"
"UDLD","4","UDLD_PORT_DISABLED","Interface [chars], link error detected: [chars]. Please collect debug info using: http://zed.cisco.com/confluence/display/KGP/UDLD+debug","An interface was disabled because UDLD protocol detected the cause on the interface indicated. Cause is likely due to bad interface hardware or cable misconfiguration. User should investigate.","LOG_STD_SH_TECH_ACTION"
"UDLD","4","UDLD_PORT_RESET","UDLD reset interface [chars]","A port which had been disabled for UDLD has been reset.","LOG_STD_SH_TECH_ACTION"
"UDLD","5","UDLD_AGGRESSIVE","UDLD Aggressive","UDLD Service Aggressive","No action is required."
"UDLD","5","UDLD_DISABLED","UDLD Disabled","UDLD Service Disabled","No action is required."
"UDLD","5","UDLD_ENABLED","UDLD Enabled","UDLD Service Enabled","No action is required."
"UFDM","2","DNLD_TIMEDOUT","Download timer expired: [chars]","UFDM download timer expired. Collect show tech-support forwarding l3 unicast for futher analysis.","No action is required."
"UFDM","2","FIB_ROUTE_UPDATE_ERR","Route update error from slot [dec] FIB","FIB returned route update error. Collect show tech-support forwarding l3 unicast for futher analysis.","No action is required."
"UFDM","2","INTERNAL_ERROR","Internal error: [chars], collect output of show tech-support fowarding l3 unicast... command","UFDM hit a internal error. Collect show tech-support forwarding l3 unicast for futher analysis.","No action is required."
"USBHSD","1","MANUAL_FORMAT","logflash needs to be formatted","Logflash is not accessible; use format logflash: to format it","No action is required."
"USBHSD","2","AUTO_FORMAT","logflash auto-format [chars]","Logflash auto-format event","No action is required."
"USBHSD","2","DISK_BUSY_FAILED","Cannot umount [chars],","The specified disk interface is in use it can not be un mounted, The user may experience file system correuption","Make sure slot0 is not being used either by mounting or by any command and re-insert the disk again"
"USBHSD","2","DISK_FSCK_FAIL","file system check returned error on slot [dec]","Flash fliesyetm may be corrupted, the flash was taken while it was being accessed","Reformat the extarnal flash"
"USBHSD","2","DISK_MOUNT_FAIL","disk mount unsuccessful on [chars]","Unknown flash filesystem or not cleanly un mounted","Use vfat flash only and make sure external slot is not being accessed then re-insert flash"
"USBHSD","2","DISK_RESCAN_FAIL","disk rescan unsuccessful on [chars]","Flash fliesyetm was not cleanly un mounted","Make sure external slot is not being accessed and re-inset the flash"
"USBHSD","2","DISK_UMOUNT_FAIL","disk umount unsuccessful for [chars]","Flash fliesyetm is busy the system could noy un-mount it","Make sure external slot is not being accessed and re-inset the flash"
"USBHSD","2","FORK","fork failed ([chars] process)","The flash daemon failed to fork","No action is required."
"USBHSD","2","INTERNAL_ERROR","Internal Error [dec]","The flash daemon interface returns error","Restart the idehsd deamon"
"USBHSD","2","MOUNT","[chars] online","Flash daemon mounting slot","No action is required."
"USBHSD","2","UMOUNT","[chars] offline","Flash daemon un mounting slot","No action is required."
"USBHSD","2","USB_SWAP","USB insertion or removal detected","USB swap event","No action is required."
"USBHSD","3","DEVICEOPEN_FAILED","device open failed. Component [chars]","The flash daemon device open failed The failure is due to the sub-component [chars]","No action is required."
"USBHSD","5","DISK_SWAP","[chars] [chars]","Compach flash swap event","No action is required."
"USBHSD","6","DISK_BUSY","trying to un mount disk [chars]","Flash daemon trying to umount busy slot","No action is required."
"USBHSD","6","DISK_EVENT","slot [dec] [chars]","Flash daemon found a disk hotswap handler event","No action is required."
"USBHSD","6","IOCTL","ioctl: [chars] returns [dec]","Flash daemon trying to umount busy slot","No action is required."
"USBHSD","6","STARTING","deamon started","The compact flash swap daemon successfully started","No action is required."
"USBHSD","6","USBHSD_INFO","[chars]","Flash daemon informational message","No action is required."
"USBHSD","7","USBHSD_TRACE","[chars]() [chars]:[dec] disk=[dec]","Flash daemon debug message to trace code path","No action is required."
"USDBA","2","USDBA_CRC_ERR","[chars]","USDBA received packet(s) with CRC error","No action is required."
"USDBA","6","USDBA_DEBUG_MSG","[chars]","Debug log message","No action is required."
"VAJRA_USD","6","VAJRA_DEBUG_MSG","[chars]","Debug log message","No action is required."
"VAL_USD","6","VAL_DEBUG_MSG","[chars]","Debug log message","No action is required."
"VDC_MGR","2","VDC_CRITICAL","vdc_mgr has hit a critical error: [chars]","Vdc_mgr has hit a critical error","A critical error has been hit within vdc_mgr. Please check show vdc to determine the state of the vdcs"
"VDC_MGR","2","VDC_LIC_WARN_EXP","WARNING License for vdcs is about to expire! VDCs will be deleted if license is allowed to expire","VDC license is close to expire","Please contact your sales representative to obtain a license"
"VDC_MGR","2","VDC_LIC_WARN","Service using grace period will be shutdown in [dec] day(s)","The license for vdcs is not installed and currently running in the grace period","Vdcs will continue to work within the grace period, but obtaining a license is reccomended"
"VDC_MGR","2","VDC_OFFLINE","vdc [dec] is now offline","The vdc has been shut down. Either it has been deleted or has just completed ungraceful cleanup","If the vdc was deleted, no action is necessary. Otherwise vdc_mgr may attempt to recreate it according to the ha-policy that has been set"
"VDC_MGR","2","VDC_ONLINE","vdc [dec] has come online","Vdc_mgr has finished creating a vdc and it is ready to use","No action is required."
"VDC_MGR","2","VDC_UNALLOCATED","Module [dec] is unsupported by the current vdc and some of its ports have been placed in the unallocated pool.","The module is of a type unsupported by the current vdc. You can see port membership by 'show vdc membership' and check the current vdc's configuration via 'show vdc'","Allocate interfaces to a vdc that supports this module type or change the current vdc to support this module type via the 'limit-resource module-type' command"
"VDC_MGR","2","VDC_UNGRACEFUL","vdc_mgr: Ungraceful cleanup request recieved for vdc [dec], restart count for this vdc is [dec] restarts within the last 5 minutes","Vdc_mgr has begun ungraceful cleanup for a vdc","There has been a failure within the vdc and vdc_mgr has begun the cleanup process. Use show vdc to determine its state"
"VDC_MGR","3","VDC_ERROR","vdc_mgr: [chars]","Vdc_mgr has recieved bad data but will try to continue","Vdc_mgr will attempt to correct the error at hand"
"VDC_MGR","5","VDC_FEATURESET_ALLOW","vdc_mgr: Feature-set [chars] can now be used in this vdc","Allowed feature-set config has changed","No action is required."
"VDC_MGR","5","VDC_FEATURESET_DISALLOW","vdc_mgr: Feature-set [chars] is now disallowed in this vdc","Allowed feature-set config has changed","No action is required."
"VDC_MGR","5","VDC_HOSTNAME_CHANGE","vdc [dec] hostname changed to [chars]","Host name for a vdc has changed.","No action is required."
"VDC_MGR","5","VDC_MEMBERSHIP_ADD","vdc_mgr: Interface [chars] has been added to this vdc","A new interface has been added to this vdc","No action is required."
"VDC_MGR","5","VDC_MEMBERSHIP_DELETE","vdc_mgr: Interface [chars] has been removed from this vdc","A new interface has been removed from this vdc","No action is required."
"VDC_MGR","5","VDC_MODULETYPE","vdc_mgr: Module type changed to [chars]","This vdc has been changed to support only the the type of modules listed","No action is required."
"VDC_MGR","5","VDC_STATE_CHANGE","vdc [dec] state changed to [chars]","A vdc state change has happened. This is most likely due to a configuration change.","No action is required."
"VDC_MGR","5","VDC_SWMODULETYPE","vdc_mgr: System Module type changed to [chars]","This switch has been changed to support only the the type of modules listed","No action is required."
"VEC-SLOT#","3","LOG_DPP_EXCEPTION","DPP Exception DPP [dec]","No action is required.","Vec"
"VEC-SLOT#","3","LOG_GUID_MISMATCH","GUID Mismatch DPP [dec] PWWN [chars] lun [chars] Expected [chars] Read [chars]","The disk GUID verification performed by the DPP failed. Access to the disk is denied.","No action is required."
"VEC-SLOT#","4","LOG_DPP_REBOOTED","DPP [dec] Rebooted","No action is required.","Vec"
"VEC-SLOT#","5","LOG_ERR_VEC_DISK","SCSI STATUS([hex]) [chars] SENSE_KEY([hex]) [chars] ASC([hex]) ASCQ([hex]) [chars]","No action is required.","Vec"
"VEC-SLOT#","5","LOG_ERR_VEC_DPP_MON_FSM","Illegal Event [chars] in State [chars] FSM [chars]","An Event is received for a State in the VEC DPP Monitor FSM which should not have occured","No action is required."
"VEC-SLOT#","5","LOG_ERR_VEC_DPRLI_FSM","Illegal Event [chars] in State [chars] FSM [chars]","An Event is received for a State in the VEC DPRLI FSM which should not have occured","No action is required."
"VEC-SLOT#","5","LOG_ERR_VEC_GID_FSM","Illegal Event [chars] in State [chars] FSM [chars]","An Event is received for a State in the VEC Guid ID FSM which should not have occured","No action is required."
"VEC-SLOT#","5","LOG_ERR_VEC_HOST_LMAP_FSM","Illegal Event [chars] in State [chars] Host VSAN :[dec] Host pWWN :[chars] VEP pWWN :[chars]","An Event is received for a State in the VEC HOST LMAP XP FSM which should not have occured","No action is required."
"VEC-SLOT#","5","LOG_ERR_VEC_HOST_LOGO","Logging out Host [VSAN :[dec] pWWN :[chars]] logged in to VEP [pWWN :[chars]]. Reason : Host not responding","The Host HBA is logged out from the VEP as it is not responding to ADISCs initiated from the VEP","No action is required."
"VEC-SLOT#","5","LOG_ERR_VEC_HOST_XP_FSM","Illegal Event [chars] in State [chars] Host VSAN :[dec] Host pWWN :[chars] VEP pWWN :[chars]","An Event is received for a State in the VEC HOST XP FSM which should not have occured","No action is required."
"VEC-SLOT#","5","LOG_ERR_VEC_HOST","Host VSAN :[dec] Host pWWN :[chars] access denied to VEP pWWN :[chars] due to licensing","The Host HBA is denied access to the VEP due to licensing","No action is required."
"VEC-SLOT#","5","LOG_ERR_VEC_NPORT_FSM","Illegal Event [chars] in State [chars] FSM [chars]","An Event is received for a State in the VEC NPORT FSM which should not have occured","No action is required."
"VEC-SLOT#","5","LOG_ERR_VEC_PID_FSM","Illegal Event [chars] in State [chars] FSM [chars]","An Event is received for a State in the VEC PID FSM which should not have occured","No action is required."
"VEC-SLOT#","5","LOG_ERR_VEC_TARGET_FSM","Illegal Event [chars] in State [chars] FSM [chars]","An Event is received for a State in the VEC TARGET FSM which should not have occured","No action is required."
"VEC-SLOT#","5","LOG_ERR_VEC_TCAM_MON_FSM","Illegal Event [chars] in State [chars] DPP :[dec]","An Event is received for a State in the VEC TCAM MON FSM which should not have occured","No action is required."
"VEC-SLOT#","5","LOG_ERR_VEC_TP_FSM","Illegal Event [chars] in State [chars] Host VSAN :[dec] TP nWWN :[chars] TP pWWN :[chars]","An Event is received for a State in the VEC TP FSM which should not have occured","No action is required."
"VEC-SLOT#","5","LOG_ERR_VEC_VEP_FSM","Illegal Event [chars] in State [chars] Host VSAN :[dec] VEP nWWN :[chars] VEP pWWN :[chars]","An Event is received for a State in the VEC VEP FSM which should not have occured","No action is required."
"VEC-SLOT#","5","LOG_ERR_VEC_VEP_ILC_LIMIT","VEP [VSAN :[dec] pWWN :[chars]] could not be created. Reason : ILC VEP limit [dec] reached","The VEP could not be created as the per ILC limit of VEPs has been reached","No action is required."
"VEC-SLOT#","5","LOG_ERR_VEC_VLUN_FSM","Illegal Event [chars] in State [chars] FSM [chars]","An Event is received for a State in the VEC VLUN FSM which should not have occured","No action is required."
"VEC-SLOT#","5","LOG_ERR_VEC_VO_FSM","Illegal Event [chars] in State [chars] FSM [chars]","An Event is received for a State in the VEC VO FSM which should not have occured","No action is required."
"VEC-SLOT#","5","LOG_ERR_VEC_VSAN_FSM","Illegal Event [chars] in State [chars] VSAN [dec]","An Event is received for a State in the VEC VSAN FSM which should not have occured","No action is required."
"VEC-SLOT#","5","LOG_ERR_VEC_VSAN_XCHG_FSM","Illegal Event [chars] in State [chars] VES IP Addr [chars]","An Event is received for a State in the VEC VSAN XCHG FSM which should not have occured","No action is required."
"VEC-SLOT#","5","LOG_NOTICE_VEC_SLEEP_THRESH","VEC not scheduled for [dec] seconds","The VEC process sleep threshold was exceeded which should not have occured. Recovery will be preformed if appropriate.","No action is required."
"VEC-SLOT#","5","LOG_NOTICE_VEC_WORK_THRESH","VEC did not yeild the cpu for [dec] seconds","The VEC process work threshold was exceeded which should not have occured. Recovery will be preformed if appropriate.","No action is required."
"VEDB_MGR","2","MALLOC_ERROR","Size [dec] bytes","The VEDB library could not allocate memory.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"VEDB_MGR","6","EXITING","Exited due to [chars]","The VEDB library has exited due to [char]. The process has probably been restarted automatically.","No action is required."
"VEDB_MGR","6","SERVICE_UP","Initialized [chars]","The VEDB library is up and ready to accept client requests The service was initialized in [char] mode.","No action is required."
"VES-SLOT#","4","LOG_WARNING_VES_CONFIG_TOO_BIG","Volume [chars] configuration too large to virtualize","The VES maximum volume configuration was exceeded. Volume will be virtualized by the cpp.","No action is required."
"VES-SLOT#","5","LOG_ERR_VES_PATH_FSM","disk guids dont match - received verify_mismatch for pid [dec] from vec [dec]","An VERIFY MISMATCH Event is received for a State in the VES PATH FSM which should not have occured","No action is required."
"VES-SLOT#","5","LOG_ERR_VES_VEP_FSM","Illegal Event [chars] in State [chars] Host VSAN :[dec] VEP pWWN :[chars]","An Event is received for a State in the VES VEP FSM which should not have occured","No action is required."
"VES-SLOT#","5","LOG_ERR_VES_VSAN_FSM","Illegal Event [chars] in State [chars] VSAN [dec]","An Event is received for a State in the VES VSAN FSM which should not have occured","No action is required."
"VES-SLOT#","5","LOG_ERR_VES_VSAN_XCHG_FSM","Illegal Event [chars] in State [chars] VEC IP Addr [chars]","An Event is received for a State in the VES VSAN XCHG FSM which should not have occured","No action is required."
"VES-SLOT#","5","LOG_NOTICE_VES_SLEEP_THRESH","VES not scheduled for [dec] seconds","The VES process sleep threshold was exceeded which should not have occured. Recovery will be preformed if appropriate.","No action is required."
"VES-SLOT#","5","LOG_NOTICE_VES_WORK_THRESH","VES did not yeild the cpu for [dec] seconds","The VES process work threshold was exceeded which should not have occured. Recovery will be preformed if appropriate.","No action is required."
"VFC","3","VFC_MEM_ERROR","Memory consistency problem","Miscellaneous target error","No action is required."
"VFC","3","VFC_TGT_ERROR","Target error:[chars] 0x%llx","Miscellaneous target error","No action is required."
"VFC","6","STARTING","deamon started","The VFC daemon successfully started","No action is required."
"VIPER_CMN_USD","6","VIPCMN_DEBUG_MSG","[chars]","Debug log message","No action is required."
"VIPER_ICB_USD","2","VIP_ICB_TEST","[chars]","Debug log message","No action is required."
"VIPER_ICB_USD","6","VIP_ICB_DEBUG_MSG","[chars]","Debug log message","No action is required."
"VIPER_MAC_USD","6","VIPER_MAC_DEBUG_MSG","[chars]","Debug log message","No action is required."
"VIPER_XBAR_USD","6","VIPER_XBAR_DEBUG_MSG","[chars]","Debug log message","No action is required."
"VIP_FWD","6","VIP_FWD_DEBUG_MSG","[chars]","Debug log message","No action is required."
"VIP_ILK","6","VIP_ILK_DEBUG_MSG","[chars]","Debug log message","No action is required."
"VLAN_MGR","2","CRITICAL_MSG","[chars]","VLAN Manager Critical Message","No action is required."
"VLAN_MGR","3","ERROR_MSG","[chars]","VLAN manager error","No action is required."
"VLAN_MGR","4","WARN_MSG","[chars]","VLAN manager warning","No action is required."
"VLAN_MGR","5","NOTIF_MSG","[chars]","VLAN Manager Notification Message","No action is required."
"VLAN_MGR","5","RESERVED_VLAN_RANGE_CHANGED","New Reserved VLAN Range Configured From VLAN [dec] to VLAN [dec]","VLAN Manager Reserved VLAN Reconfiguration Message","No action is required."
"VLAN_MGR","6","INFO_MSG","[chars]","VLAN manager info","No action is required."
"VLAN_MGR","6","VLAN_CREATED","VLAN [dec], created","VLAN created","No action is required."
"VLAN_MGR","6","VLAN_MGR_STATEFULL_RESTART","VLAN Manager statefull restart","VLAN Manager statefull restart","No action is required."
"VLAN_MGR","6","VLAN_MGR_STATELESS_RESTART","VLAN Manager stateless restart","VLAN Manager stateless restart","No action is required."
"VLAN_MGR","6","VLAN_OPER_STATUS_CHG","VLAN [dec], status changed to [chars]","VLAN operational state change","No action is required."
"VMAN","2","ACTIVATION_STATE","[chars] [chars]'[chars][chars]'","The activation state of the named virtual service has changed as notified by Virt-manager.","In the failed case, check Virt-managerslogsforthecauseofthefailure.Inthesuccessfulcase,thisnotificationcanbeignored.'"
"VMAN","2","ALLOC_VIRT_INST_RCS","Virtual Service[chars]","A memory allocation request failed to allocate a data structure required to activate the virtual service.","Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause."
"VMAN","2","COMMIT_VIRT_INST_RCS","Virtual Service[chars]","The request to commit the resources required by the named virtual service failed.","Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause."
"VMAN","2","CPUSHARES_LIMIT","Virtual Service[chars]","The virtual service machine definition file is requesting more CPU shares than the system has available for virtual services.","Deactivate any other virtual services to free up CPU share resources and activate this virtual service. If that does not address the problem, then enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause."
"VMAN","2","CPUTUNES_INTERNAL_ERROR","Virtual Service[chars]","Virt-manager and its associated infrastructure experienced an internal error.","Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause."
"VMAN","2","CPUTUNES_SHARES_LIMIT","Virtual Service[chars]","The virtual service machine definition file is requesting more CPU shares than the system has available for virtual services.","Deactivate any other virtual services to free up CPU share resources and activate this virtual service. If that does not address the problem, then enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause."
"VMAN","2","CREATE_VIRT_INST_ENTRY","Virtual Service[chars]","The request to create a DB entry for the named virtual service failed.","Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause."
"VMAN","2","DEFER_VIRT_INST_PROC","Virtual Service[chars]","The final activation processing failed to successfully defer.","Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause."
"VMAN","2","DISK_IMAGE_PATH","Virtual Service[chars]","The virtual service machine definition file contains an invalid disk image path for one of the disk devices. This may be a Harddisk, CDROM or USB storage device.","Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause."
"VMAN","2","FIND_VIRT_INST_ENTRY","Failed to find virtual service with id [dec] in the Virt-manager DB","The virtual service with the ID named could not be located in the Virt-manager DB.","Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause."
"VMAN","2","GENERAL_FAILURE","Virtual Service[chars]","The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.","No action is required"
"VMAN","2","HA_SYNC_ERR","[chars] [chars]'[chars]'","The ha-sync persistent storage disk for the virtual service cannot be watched for sync to standby RP.","Collect the Virt-manager logs and scan them for the cause."
"VMAN","2","INCONSISTENT_CPUTUNES_CONFIG","Virtual Service[chars]","The virtual service machine definition file is requesting invalid CPU tunes parameter.","Use a different valid machine definition file for the virtual service. If the problem persists, then enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause."
"VMAN","2","INCONSISTENT_MEM_CONFIG","Virtual Service[chars]","The virtual service machine definition file is inconsistent in the specification of required memory via the <memory","Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause."
"VMAN","2","INSERT_VIRT_INST_ENTRY","Virtual Service[chars]","Inserting the named virtual service into the virtual service DB tracked by Virt-manager failed.","Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause."
"VMAN","2","INSTALL_FAILURE","Virtual Service[chars]","The installation of the virtual service failed.","Enable the Virt-manager trace logs and repeat the installation of the virtual service. Collect the Virt-manager logs and scan them for the cause."
"VMAN","2","INSTALL_MEDIA_RETRY","VMAN, VM install media still unavailable.[chars]","The install media was not detected. Waiting for udev to complete install media(harddisk) detection.","After VMAN exceeds the maximum retry limit, verify if install media (harddisk) is accessible and retry the installation again."
"VMAN","2","INSTALL_STATE","Successfully [chars] [chars]''","The installation state of the named virtual service has changed as notified by Virt-manager.","In the failed case, check Virt-managerslogsforthecauseofthefailure.Inthesuccessfulcase,thisnotificationcanbeignored.'"
"VMAN","2","INVALID_ACT_MSG","Virtual Service[chars]","The virtual service activate message was received, however, the data it contained could not be interpreted","Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause."
"VMAN","2","INVALID_DEACT_MSG","Failed to process virtual service deactivate message","The virtual service deactivate message was received, however, the data it contained could not be interpreted","Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause."
"VMAN","2","INVALID_PACKAGE","Virtual Service[chars]","The package definition file for the named virtual service has failed to be validated and the virtual service will not run","Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. The most likely cause would be that the package file has been corrupted during file transfer. The suggested action would be to redo the file transfer."
"VMAN","2","INVALID_UNPROV_MSG","Failed to process virtual service unprovision message","The virtual service unprovision message was received, however, the data it contained could not be interpreted","Enable the Virt-manager trace logs and repeat the activation followed by deactivation and then unprovision of the virtual service. Collect the Virt-manager logs and scan them for the cause."
"VMAN","2","MACHINE_TYPE_NOT_SUPPORTED","Virtual Service[chars]","The virtual service cannot be activated as the machine type specified is not supported; action Enable the support for the machine type and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause.","Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause."
"VMAN","2","MACH_PARSE_FAILURE","Virtual Service[chars]","The named virtual service has an invalid parameter specified in the .xml file inside the .ova package","Fix the .xml file inside the .ova package to have valid values. Then retry installing and activating it"
"VMAN","2","MEMORY_LIMIT_WARN","Virtual service ([chars])[chars] defines [dec] MB of Memory exceeding the maximum [dec] MB.","The virtual service machine definition file is requesting more memory for the specified profile, than the system has available for virtual services.","Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause."
"VMAN","2","MEMORY_LIMIT","Virtual Service[chars]","The virtual service machine definition file is requesting more memory than the system has available for virtual services.","Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause."
"VMAN","2","MORETHANONE_CPUTUNES_CONFIG","Virtual Service[chars]","The virtual service machine definition file is requesting more than one CPU tunes parameter.","Use a different valid machine definition file for the virtual service. If the problem persists, then enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause."
"VMAN","2","NETWORK_CONFIG_ERROR","Virtual Service[chars]","A network configuration error has been detected for the named virtual service.","No action is required"
"VMAN","2","PROCESS_PKG_DEF","Virtual Service[chars]","The virtual service package for the named virtual service has failed to be validated and the virtual service will not run.","Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause."
"VMAN","2","PROC_INT_LIST","Virtual Service[chars]","The interface list embedded in the activate request for the named virtual service could not be processed.","Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause."
"VMAN","2","REMOVE_VIRT_INST_ENTRY","Virtual Service[chars]","Removing the named virtual service from the virtual service DB tracked by Virt-manager failed.","Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause."
"VMAN","2","SET_VTX_ROMVAR_SPACE","Failed to set ROM monitor variable ENABLE_VTX: No space in table","Failed to set ENABLE_VTX ROM monitor variable due to no space in Monitor Variable Table.","Verify number of entries in Monitor Variable Table."
"VMAN","2","SET_VTX_ROMVAR_STRING","Failed to set ROM monitor variable ENABLE_VTX: Invalid string format: [chars]","Failed to set ENABLE_VTX rom monitor variable due to invalid string format.","Verify format of string from error message."
"VMAN","2","START_FAILED","Virtual Service[chars]","The named virtual service failed to start.","Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause."
"VMAN","2","VCPU_INVALID","Virtual Service[chars]","The virtual service machine definition file is requesting invalid VCPU value.","Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause."
"VMAN","2","VCPU_LIMIT","Virtual Service[chars]","The virtual service machine definition file is requesting more VCPUs than the system has reserved for virtual services.","Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause."
"VMAN","2","VIRT_INST_DISK","Virtual Service[chars]","The virtual service requires Disk Storage in excess of the Free Disk Storage available to virtual services.","Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause."
"VMAN","2","VIRT_INST_INTERFACE","Virtual Service[chars]","The number of configured virtual port group interfaces must match the number of Ethernet Network Interfaces defined in the machine definition file","Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause."
"VMAN","2","VIRT_INST_MEMORY","Virtual Service[chars]","The virtual service requires physical memory in excess of the free memory available to virtual services.","Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause."
"VMAN","2","VIRT_INST_MGMT_INTERFACE","Virtual service [chars] has no management interface defined but it is configured in CLI.","A management interface is configured but none is defined.","Deactivate the virtual service, remove the management interface configuration CLI, and reactivate the virtual-service."
"VMAN","2","VIRT_INST_STATE","Virtual Service[chars]","The named virtual service has failed. It is no longer running either because the guest OS has failed, the guest OS has shut down the machine or the emulator has failed.","An attempt at restarting the virtual service can be made from the IOS configuration by doing a no activate/activate. For debugging collect the Virt-manager logs and scan them for the cause."
"VMAN","3","PSS_ERR","Purpose: [chars], URI: [chars], errcode: [dec]","Persistent Storage Service handling error","Collect the Virt-manager logs and scan them for the cause."
"VMAN","3","PSS_SNAPSHOT_ERR","Source URI: [chars], Destination URI: [chars], errcode: [dec]","Persistent Storage Service snapshot error","Collect the Virt-manager logs and scan them for the cause."
"VMAN","3","SDWRAP_ERR","Description: [chars], errcode: [dec]","Debug infrastructure error","Collect the Virt-manager logs and scan them for the cause."
"VMAN","4","WATCHDOG_TIMER","[chars] [chars]'[chars][chars]'","The watchdog timer configured for the named virtual service has expired.","Check any logs produced by the virtual service to determine the cause."
"VMAN","5","AUX","Virtual Service[chars]","The AUX login to a virtual service may allow the user access to system functions that may not have been tested or may interact with the system in unintended ways. Use with caution.","No action is required"
"VMAN","5","UNSIGNED_PACKAGE","Unsigned software package [chars] loaded for service container [chars].","A software package without a code signing certificate has been loaded.","Take note of the service container and software package. Verify the software package is expected to be unsigned and has the appropriate contents. Uninstall the package if unsure of the package origins."
"VMAN","5","VIRT_INST","LOG FROM VIRTUAL SERVICE [chars]: [chars]","The named virtual service has triggered the log. Please interpret the log in the context of the virtual services.","No action is required"
"VMM","2","VMM_DBG_SEQDELAY_LOG","VDC[dec]: Sending [chars] mts([chars]) request to service [dec] for slot [dec].","VMM sent request for the sap mentioned","No action is required."
"VMM","2","VMM_SERVICE_ERR","VDC[dec]: Service SAP [chars] for slot [chars] returned error [hex] ([chars]) in [chars] sequence","Service returned error in the specified sequence","No action is required."
"VMM","2","VMM_TIMEOUT","VDC[dec]: Service SAP [chars] for slot [chars] timed out in [chars] sequence","Service did not respond in the specified sequence","No action is required."
"VNI","2","ALLOC_MEMORY","Memory allocation failed","The service failed to allocate a block of dynamic memory.","No action is required."
"VNI","3","INIT_FAILED","Initialization failed. Component [chars]","The service failed to start. The failure occurred while initializing the component [chars].","Show processes to check the status of the other processes, debug the specified component."
"VNI","6","INTERFACE_EVENT","VSAN interface [chars] [chars]","The specified VSAN Interface has been successfully [chars].","No action is required."
"VNI","6","STARTING","Virtual Network Interface Manager started","The service has successfully started.","No action is required."
"VNI","6","VSAN_DELETED","VSAN [dec] has been deleted","The specified VSAN has been deleted. The service will delete all the configuration on that VSAN.","No action is required."
"VNTAGC","5","VNTAGC_GENERIC_SYSLOG","[chars]","VNTag Manager Client Generic Syslog","No action is required."
"VNTAG_MGR","2","MCAST_DVIF_ALLOC_FAILURE","DVIF allocation failure during MCAST group creation. TCB RID: [hex]. MCAST LTL: [hex]. Reason: [chars].","MCAST DVIF allocation for MCAST group.","No action is required."
"VNTAG_MGR","2","VLAN_DVIF_ALLOC_FAILURE","DVIF allocation failure for VLANs [chars]. Reason: [chars].","Flood DVIF allocation failure for VLANs.","No action is required."
"VNTAG_MGR","2","VNTAG_MGR_OMF_DVIF_ALLOC_FAIL","OMF DVIF allocation failed (DVIF exhaustion).To enable OMF you need to shut down a VLAN/MCAST group","OMF DVIF reservation failed (dvif exhaustion). To enable OMF a VLAN or MCAST group needs to be disabled to get a free dvif.","No action is required."
"VNTAG_MGR","2","VNTAG_SEQ_ERROR","[chars]","Some step in an event sequence has failed","No action is required."
"VNTAG_MGR","2","VNTAG_SEQ_TIMEOUT","[chars]","Event sequence timeout","No action is required."
"VNTAG_MGR","4","VNTAG_MIXED_FPC_HIFPC_PAYLOAD","[chars]","This not allowed from PIXM itself, but could happen due to some incorrect MBL batching.","No action is required."
"VNTAG_MGR","4","VNTAG_PRUNED_L3_PORT","Port [hex] will not be added to FEX forwarding table as it is a L3 port.","To avoid sending multidestination traffic to L3 ports we do not add them to FEX forwarding table.","No action is required."
"VNTAG_MGR","5","VNTAG_MGR_DISABLED","VNTag Manager Disabled","VNTag Manager Service Disabled","No action is required."
"VNTAG_MGR","5","VNTAG_MGR_ENABLED","VNTag Manager Enabled","VNTag Manager Service Enabled","No action is required."
"VNTAG_MGR","5","VNTAG_MGR_GENERIC_SYSLOG","[chars]","VNTag Manager Generic Syslog","No action is required."
"VPC","2","PEER_KEEP_ALIVE_RECV_FAIL","In domain [dec], VPC peer keep-alive receive has failed","Peer keep-alive receive failed","No action is required."
"VPC","2","PEER_KEEP_ALIVE_SEND_FAIL","In domain [dec], VPC peer keep-alive send has failed","Peer keep-alive send failed","No action is required."
"VPC","2","PEER_VPC_RESP_TIMEDOUT","Failed to receive response from peer for vPC: [dec]","VPC bringup failed","No action is required."
"VPC","2","TRACK_INTFS_DOWN","In domain [dec], vPC tracked interfaces down, suspending all vPCs and keep-alive","VPC tracked object down","No action is required."
"VPC","2","VPC_ADD_L3_BKUP_VLAN_TO_PEER_GW_EXCLUDE_LIST","Exclude L3 backup routing VLAN from vpc peer-gateway config.","Triggered when peer-link is F1 and peer-gateway is configured without exclude-vlan list.","No action is required."
"VPC","2","VPC_CORE_PORT_FPATH_BUP_FAILED","Failed to bring up vPC+ peer link port [chars] in Fabric Path Port Mode - vPC+ Fabric Path switch ID not configured","VPC+ Failed to bringup peer-link - switch-ID not configured","No action is required."
"VPC","2","VPC_ES_FAILED_LID_ALLOC","Failed to negotiate common LID between vPC peers.","Failed to find common lid.","No action is required."
"VPC","2","VPC_ES_FAILED_PEERLINK_DOWN","vPC+ operations failed. Bringing down peer-link.","Triggered in mcecm_em_es_failed. Bring down peer-link.","No action is required."
"VPC","2","VPC_ES_PEER_LINK_OPERATION_FAILED","Peer-link operation failed due to SAP [dec].","Triggered in mcecm_cfg_es_failed when peer-link bringup fails.","No action is required."
"VPC","2","VPC_GRACEFUL_SUSP_ALL_VPC","Operational graceful type-1 check configuration changed, reiniting all vPCs","Graceful configuration change,reinit vPCs","No action is required."
"VPC","2","VPC_ISSU_END","Peer vPC switch ISSU end, unlocking configuration","Peer vPC switch issu end","No action is required."
"VPC","2","VPC_ISSU_START","Peer vPC switch ISSU start, locking configuration","Peer vPC switch issu start","No action is required."
"VPC","2","VPC_LC_FAIL","LC [dec] does not support required hardware for vPC; run showvdcmembershipstatus'forportstatus'","Lc insertion failed","No action is required."
"VPC","2","VPC_NON_DEF_LID","vPC+ negotiated non-default local id. Flapping orphan edge ports recommended.","Triggered in mcecm_em_es_failed. Bring down peer-link.","No action is required."
"VPC","2","VPC_PEER_LINK_FPATH_BUP_FAILED","Failed to bring up vPC+ peer link port [chars] - port [chars] is not configured as a Fabric Path port","VPC+ Failed to bringup Peer-link - not in Fabric Path mode","No action is required."
"VPC","2","VPC_PSS_ERROR","[chars], 0x([hex]) present in VPC DB but not is IM DB","Triggered when vpc DB and IM SDB are inconsistent","No action is required."
"VPC","2","VPC_SUSP_ALL_VPC","Peer-link going down, suspending all vPCs on secondary","Peer link down suspend vPCs","No action is required."
"VPC","2","VPC_SVI_EXCLUDE","vPC [dec] has up vlans [chars] which are excluded from suspension on dual-active","VPC track object deconfigured","No action is required."
"VPC","3","GLOBAL_CONSISTENCY_FAILED","In domain [dec], global configuration is not consistent ([chars])","Global compat-check failed","No action is required."
"VPC","3","INTF_CONSISTENCY_FAILED","In domain [dec], VPC [dec] configuration is not consistent ([chars])","MCEC compat-check failed","No action is required."
"VPC","3","PEER_UNREACHABLE","Remote Switch Unreachable","Peer unreachable","No action is required."
"VPC","3","PEER_VPC_BRINGUP_FAILED","Peer vPC [dec] bringup failed ([chars])","Peer vPC bringup failed","No action is required."
"VPC","3","VPCM_ASSERTION_FAILED","[chars]","VPCM has hit an assert condition at file [chars]","No action is required."
"VPC","3","VPCM_INIT_FAIL","vPC Manager Initialization Failed ([chars])","VPCM Initialization failed. due to [chars]","No action is required."
"VPC","3","VPCM_INTERNAL_ERR","[chars]","VPCM encountered an internal error due to [chars]","No action is required."
"VPC","3","VPCM_MTS_ERR","[chars]","VPCM encountered an MTS error due to [chars]","No action is required."
"VPC","3","VPC_BRINGUP_FAILED","vPC [dec] bringup failed ([chars])","VPC bringup failed","No action is required."
"VPC","3","VPC_PEER_LINK_BRINGUP_FAILED","vPC peer-link bringup failed ([chars])","VPC Peer-link bringup failed","No action is required."
"VPC","3","VPC_PEER_LINK_DOWN","VPC Peer-link is down","VPC Peer link is down","No action is required."
"VPC","4","PEER_VPC_DELETED","Peer vPC [dec] deleted","Peer vPC configuration deleted","No action is required."
"VPC","4","VPC_CONSISTENCY_NEW_VLAN_FAIL","Global Consistency check for vPC failed for new vlans","Global Consistency check for vPC failed for new vlans","No action is required."
"VPC","4","VPC_DELETED","vPC [dec] is deleted","VPC configuration deleted","No action is required."
"VPC","4","VPC_DISABLE_IP_REDIRECTS","peer-gateway enabled. Disabling IP redirects on all interface-vlans of this vPC domain for correct operation of this feature.","Peer-gateway enabled, hence IP redirects on SVIs are disabled","No action is required."
"VPC","4","VPC_LC_UPG_OVER_DELIVERY_FAIL","Failed to deliver LC upgrade to vPC peer","Failed to deliver LC upgrade to peer","No action is required."
"VPC","4","VPC_PEER_LINK_DELETED","vPC Peer-link deleted. This will bringdown all vPC interfaces","VPC Peer-link configuration removed","No action is required."
"VPC","4","VPC_PEER_ROLE_CHANGE","In domain [dec], VPC peer role status has changed to [chars]","VPC Peer role status changed to (Primary/Secondary","No action is required."
"VPC","4","VPC_PER_VLAN_NO_SUPPORT","image that does not support per-vlan type-1 check will not bring down/up any vlan (i.e. nothing will happen) until next compat-check.","Triggered when ISSU/ISSD to an image which does not support per-vlan compat-check","No action is required."
"VPC","4","VPC_PER_VLAN_CONSISTENCY_FAILED","Global consistency check for vPC failed for few vlans","Global Consistency check for vPC failed for few vlans","No action is required."
"VPC","4","VPC_REINITIALIZED","Reinitializing vpcs assuming peer dead","Initializing vpcs assuming peer dead","No action is required."
"VPC","4","VPC_ROLE_CHANGE","In domain [dec], VPC role status has changed to [chars]","VPC role status changed to (Primary/Secondary","No action is required."
"VPC","5","GLOBAL_CONSISTENCY_SUCCESS","In domain [dec], global configuration is consistent","Global compat-check passed","No action is required."
"VPC","5","INTF_CONSISTENCY_SUCCESS","In domain [dec], vPC [dec] configuration is consistent","VPC configuration is consistent","No action is required."
"VPC","5","PEER_KEEP_ALIVE_RECV_INT_LATEST","In domain [dec], VPC peer-keepalive received on interface [chars]","VPC peer-keepalive receive interface changed","No action is required."
"VPC","5","PEER_KEEP_ALIVE_RECV_SUCCESS","In domain [dec], vPC peer keep-alive receive is successful","Peer keep-alive receive successful","No action is required."
"VPC","5","PEER_KEEP_ALIVE_SEND_INT_LATEST","In domain [dec], VPC peer-keepalive sent on interface [chars]","VPC peer-keepalive send interface changed","No action is required."
"VPC","5","PEER_KEEP_ALIVE_SEND_SUCCESS","In domain [dec], vPC peer keep-alive send is successful","Peer keep-alive send successful","No action is required."
"VPC","5","PEER_KEEP_ALIVE_STATUS","In domain [dec], peer keep-alive status changed to [chars]","Peer keep-alive (oob) status is changed to <peer-alive","Peer-not-alive"
"VPC","5","ROLE_PRIORITY_CFGD","In domain [dec], vPC role priority changed to [dec]","Role priority configured","No action is required."
"VPC","5","SYSTEM_MAC_CFGD","In domain [dec], vPC system-mac changed to [chars]","System mac configured","No action is required."
"VPC","5","SYSTEM_PRIO_CFGD","In domain [dec], vPC system priority changed to [dec]","System priority changed","No action is required."
"VPC","5","VPCM_DISABLED","vPC Manager disabled","VPCM Service Disabled","No action is required."
"VPC","5","VPCM_ENABLED","vPC Manager enabled","VPCM Service Enabled","No action is required."
"VPC","5","VPC_DELAY_SVI_BUP_TIMER_EXPIRED","vPC restore, delay interface-vlan bringup timer expired, reiniting interface-vlans","VPC delay interface-vlan restore timer expired","No action is required."
"VPC","5","VPC_DELAY_SVI_BUP_TIMER_START","vPC restore, delay interface-vlan bringup timer started","VPC delay interface-vlan restore timer start","No action is required."
"VPC","5","VPC_DOWN","vPC [dec] is down ([chars])","VPC is down (reason)","No action is required."
"VPC","5","VPC_PEER_LINK_UP","vPC Peer-link is up","VPC Peer-link is up","No action is required."
"VPC","5","VPC_RESTORE_TIMER_EXPIRED","vPC restore timer expired, reiniting vPCs","VPC restore timer expired","No action is required."
"VPC","5","VPC_RESTORE_TIMER_START","vPC restore timer started to reinit vPCs","VPC restore timer start","No action is required."
"VPC","5","VPC_ROLE_PREMPT","In domain [dec], vPC role pre-emption triggered","VPC preemption triggered","No action is required."
"VPC","5","VPC_UP","vPC [dec] is up","MCEC is UP","No action is required."
"VPC","6","PEER_LOCK_FAILED","Locking failed on peer switch - Aborting upgrade!!","Locking failed on peer switch","No action is required."
"VPC","6","PEER_VPC_CFGD_VLANS_CHANGED","Peer vPC [dec] configured vlans changed","Remote MCEC configured vlans Changed","No action is required."
"VPC","6","PEER_VPC_CFGD","peer vPC [dec] is configured","VPC is configured","No action is required."
"VPC","6","PEER_VPC_DOWN","Peer vPC [dec] is down ([chars])","Peer vPC is down","No action is required."
"VPC","6","PEER_VPC_UP","Peer vPC [dec] is up","Peer vPC is up","No action is required."
"VPC","6","STATS_CLEARED","vPC Statistics Cleared","VPC statistics cleared","No action is required."
"VPC","6","TRACK_OBJ_CONFIGURED","In domain [dec], track object configured [dec]","VPC track object configured","No action is required."
"VPC","6","TRACK_OBJ_DELETED","In domain [dec], track object deleted","VPC track object deconfigured","No action is required."
"VPC","6","TYPE1_PARAM_CHANGED","TYPE-1 parameters changed: [chars]","Type-1 Parameters Changed","No action is required."
"VPC","6","VPCM_INTERNAL_INFO","[chars]","VPCM got an internal info [chars]","No action is required."
"VPC","6","VPC_ALLOWED_VLAN_CHANGED","vPC [dec] operational vlans changed","Operational vlans changed on vPC","No action is required."
"VPC","6","VPC_CFGD","vPC [dec] is configured","VPC is configured","No action is required."
"VPC","6","VPC_CONSISTENCY_CHECK_BYPASS","Bypassing consistency check for vPC: [dec]","Bypassing consistency check for vpcs","No action is required."
"VPC","6","VPC_CONSISTENCY_NEW_VLAN_PASS","Global Consistency check for vPC passed for new vlans","Global Consistency check for vPC passed for new vlans","No action is required."
"VPC","6","VPC_DOMAIN_ID_CFGD","vPC domain-id configured to [dec]","VPC domain-id configured","No action is required."
"VPC","6","VPC_ES_EGRESS_DF_STATE_CHANGED","Egress designated forwarder state changed from [chars] to [chars] for vPC [dec].","DF state changed for some vPC.","No action is required."
"VPC","6","VPC_ES_ID_CFGD","Fabricpath switch ID [dec] configured","Fabricpath switch ID configured","No action is required."
"VPC","6","VPC_ES_ID_REMOVED","Fabricpath switch ID [dec] removed","Fabricpath switch ID removed","No action is required."
"VPC","6","VPC_PEER_LINK_CFGD","vPC peer-link is configured","VPC Peer-link is configured","No action is required."
"VPC","6","VPC_PER_VLAN_CONSISTENCY_PASSED","Global Consistency check for vPC passed for all vlans","Global Consistency check for vPC passed for all vlans","No action is required."
"VPM","2","GENERAL_ERROR","[chars]","The VP Manager has encountered an critical error. The description of error is [str.]","No action is required."
"VPM","2","MALLOC_ERROR","Size [dec] bytes","The VP Manager could not allocate memory.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"VPM","2","PSS_ERROR","[chars]","The VP Manager encountered error while operating on a persistent storage database.","No action is required."
"VPM","2","VPMON_CRIT","[chars] [dec]","VPMON daemon critical message","No action is required."
"VPM","2","VPMON_DPP_DOWNLOAD","HB failure, Restarting the DPP [dec]","VPMON daemon redownloading DPP(s)","ISAPI API users need to re-download config data to fast path"
"VPM","2","VPMON_DPP_RELOAD_FORCE","Force reload of DPP(s) [chars]: [chars]","VPMON daemon critical action message","No action is required."
"VPM","3","PSS_SYNC_TO_STNDBY_FAILED","PSS TYPE=[chars] KEY=[chars]","Could not send PSS Sync. notification to Standby Supervisor. PSS Type=[str.] Operation=[.str] Key=[Str.]","No action is required."
"VPM","3","SEND_TO_ILC_FAILED","[chars]","The VP Manager could not send to ILC for DG=[chars], at slot=[dec] processor=[dec] and SAP=[dec].","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"VPM","3","SEND_TO_SNMP_AGENT_FAILED","[chars]","The VP Manager could not send to SNMP Agent for DG=[chars].","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"VPM","3","UNKNOWN_MSG","Recvd. from Node=[dec] SAP=[dec]","The VP Manager has received an unknown message from [dec]].[dec]. This information is for debugging only.","No action is required."
"VPM","3","VPM_PSS_CORRUPTED","[chars] PSS found corrupted","The VP Manager has detected corruption in one of its persistent information database. The database would be recreated.","No action is required."
"VPM","4","PSS_VERSION_MISMATCH","PSS [dec] Code [dec]","There was a version mismatch between the VP Manager and one of its persistent storage databases. The persistent information has been translated to the new format.","No action is required."
"VPM","6","BECAME_ACTIVE","Became ACTIVE from standby mode","The VP Manager on the standby supervisor became active and it is ready to serve client requests.","No action is required."
"VPM","6","BECAME_STDBY","Became STANDBY from active mode","The VP Manager became standby from active mode.","No action is required."
"VPM","6","DG_DEREGISTERED","[chars]","The VP Manager has deregistered DG [chars] at slot=[dec] processor=[dec] and SAP=[dec].","No action is required."
"VPM","6","DG_REGISTERED","[chars]","The VP Manager has registered DG [chars] from slot=[dec] processor=[dec] and SAP=[dec].","No action is required."
"VPM","6","EXITING","Exited due to [chars]","The VP Manager process has exited due to [char]. The process has probably been restarted automatically.","No action is required."
"VPM","6","FAILED_TO_SEND_HEARTBEAT","Failed to send heartbeat to system manager: Reason=[chars]","The VP Manager was unable to send heartbeat to the system manger","No action is required."
"VPM","6","GENERAL_EVENT","[chars]","The VP Manager has generated an important event. The description of the event is [str.]","No action is required."
"VPM","6","PSS_CREATED","[chars] PSS Created","One of the persistent information database of VP Manager has been recreated","No action is required."
"VPM","6","PSS_DESTROYED","[chars] PSS Destroyed","One of the persistent information databases of Vp Manager has been intentionally destroyed and would be recreated.","No action is required."
"VPM","6","SERVICE_UP","Initialized [chars]","The VP Manager is up and ready to accept client requests The service was initialized in [char] mode.","No action is required."
"VPM","6","SWITCHOVER","Switching Over to other Sup.","The VP Manager has successfully switched over to the standby supervisor card.","No action is required."
"VPM","6","VPMON_INFO","[chars]","VPMON daemon informational message","No action is required."
"VPM","6","VPMON_STARTING","deamon started","The VPMON daemon successfully started","No action is required."
"VPM","6","VPM_MDS_LICENSE_GRACE","MDS LICENSE in grace period for feature : [chars]","MDS license is in grace period. Please retrieve a new MDS license","No action is required."
"VPM","6","VPM_MDS_LICENSE_REVOKED","MDS LICENSE REVOKED for feature : [chars]","MDS license is revoked. Please retrieve a new MDS license","No action is required."
"VPM","6","VPM_MDS_TIMED_LICENSE","Timed MDS LICENSE for feature : [chars]","Timed MDS license","No action is required."
"VPM-SLOT#","2","CPP_CATASTROPHIC_ERROR","ERROR: Component ([chars]) caused critical error please reboot SSM","Component caused critical error","Restart the linecard"
"VRRP-CFG","2","ALLOC_MEMORY","Memory allocation failed","The service failed to allocate a block of dynamic memory.","No action is required."
"VRRP-CFG","2","VSH_REGISTER_FAIL","VSH registration failed returning [dec]","VRRPsparsetreeregistrationwithVSHfailed'","No action is required."
"VRRP-CFG","3","INIT_FAILED","Initialization failed. Component [chars]","The service failed to start. The failure occurred while initializing the component [chars].","Show processes to check the status of the other processes, debug the specified component."
"VRRP-CFG","3","VRRP_FEATURE_MANAGER_ERROR","Error in feature manager operation","The feature manager operation did not go through fine","Please check the reason for error using feature manager and rectify the problem"
"VRRP-CFG","5","STARTING","VRRP Manager service started","The service successfully started.","No action is required."
"VRRP-ENG","2","ALLOC_MEMORY","Memory allocation failed","The service failed to allocate a block of dynamic memory.","No action is required."
"VRRP-ENG","2","VR_FAILURE","Error in VR[chars] [dec] interface [chars]. Going to init state","The VR [dec] on the interface [chars] is in init state for an internal error.","Show interface to check the status of the interface, show configuration, status and statistics of the specified virtual router, enable the vrrp debug and shut/ no shut the specified virtual router."
"VRRP-ENG","3","ARP_INIT_ERROR","Failed to init ARP, ret [hex], errno [dec]","VRRP-ARP interaction failed.","No action is required."
"VRRP-ENG","3","BFD_IF_SESSION_REMOVAL_ERROR","Failed to remove interface level VRRP-BFD sessions ([hex] [hex]), Refer logs","Plz refer internal error history for more details.","No action is required."
"VRRP-ENG","3","BFD_SESSION_ADD_ERROR","Failed to add a few VRRP-BFD sessions([hex] [hex]), Refer logs","Plz refer internal error history for more details.","No action is required."
"VRRP-ENG","3","BFD_SESSION_CREATION_ERROR","Failed to create BFD session information([hex] [hex]), Refer logs","Plz refer internal error history for more details.","No action is required."
"VRRP-ENG","3","BFD_SESSION_REMOVAL_ERROR","Failed to remove a few VRRP-BFD sessions([hex] [hex]), Refer logs","Plz refer internal error history for more details.","No action is required."
"VRRP-ENG","3","INIT_FAILED","Initialization failed. Component [chars]","The service failed to start. The failure occurred while initializing the component [chars].","Show processes to check the status of the other processes, debug the specified component."
"VRRP-ENG","3","IP_INIT_ERROR","Failed to init IP, ret [hex], errno [dec]","VRRP-IP interaction failed.","No action is required."
"VRRP-ENG","3","L3VM_INIT_ERROR","Failed to init L3VM, ret [hex], errno [dec]","VRRP-L3VM interaction failed.","No action is required."
"VRRP-ENG","3","URIB_INIT_ERROR","Failed to init URIB, ret [hex], errno [dec]","VRRP-URIB interaction failed.","No action is required."
"VRRP-ENG","4","BAD_ADV","VR[chars] ID [dec] on interface [chars] bad advertisement received: reason [chars]","The virtual router specified has received an invalid advertisement.","Check that all VRRP nodes have the same configuration."
"VRRP-ENG","5","INTERFACE_DOWN","Cannot start the VR[chars] [dec] since the interface [chars] is down","The specified VR is enabled but cantchangestatefrominit.Thespecifiedinterfaceisdownordoesn'thaveaprimaryIPaddressconfigured.'","No action is required."
"VRRP-ENG","5","INTERFACE_STATE_CHANGE","Interface [chars] state changed to [chars]","The interface specified has changed state This could have triggered a VRRP status change.","No action is required."
"VRRP-ENG","5","INVALID_CONFIG","Cannot start the VR[chars] [dec] on the interface [chars]. Invalid IP configuration. Reason: [chars]","The specified VR on interface [chars] is enabled but the IP configuration is not valid because of [chars].","Show interface to check that the IP address of the interface is configured and it is in the same subnet of the virtual router address."
"VRRP-ENG","5","STARTING","VRRP Engine service started","The service successfully started.","No action is required."
"VRRP-ENG","5","VR_STATE_CHANGE","VR[chars] ID [dec] on interface [chars] state changed to [chars], event [chars]","The status of the specified virtual router has changed to [chars].","No action is required."
"VRRP-ENG","6","VSHA_RESULT","VR ID [dec] on interface [chars] state change request result [chars]","The result of the request for status change on the virtual router (with VSHA extension) specified is [chars].","No action is required."
"VSAN","2","PROGRAM_EXIT","process exiting with reason: [chars]","VSAN manager process is exiting with reason [chars].","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"VSAN","3","CFS_OPERATION_FAILED","cfs [chars] operation failed : [chars]","Cfs operation [chars1] has failed. [chars2]","Please check the reason for the failure of the cfs operation and rectify the problem"
"VSAN","3","MEM_ALLOC_FAILED","alloc failed for size:[dec]","Memory allocation of size [dec] failed.","Do 'show process memory' command to see memory usage of processes."
"VSAN","3","MESSAGE_ERROR","could not handle message:[chars] of type [dec] sent by addr [dec]:[dec]","Got an IPC message [chars] of type [dec1] sent by a component running on node [dec2] with sap [dec3].","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"VSAN","6","ACTIVATED","VSAN:[dec] changing from suspended to active","Making VSAN with ID [dec] active from suspended state.","No action is required."
"VSAN","6","CFS_MERGE_NOT_SUPPORTED","merging of fctimer configuration data is not supported","Merging of fctimer configuration data using cfs is not supported","No action is required."
"VSAN","6","CREATED","Created VSAN:[dec] with name:[chars]","Created VSAN with ID [dec] and name [chars].","No action is required."
"VSAN","6","MEMBERSHIP_UPDATE","Updated membership for interface:[chars] with VSAN:[dec]","Updating membership for interface [chars] with VSAN [dec].","No action is required."
"VSAN","6","REMOVED","Removed VSAN:[dec]","Removed VSAN with ID [dec].","No action is required."
"VSAN","6","SUSPENDED","VSAN:[dec] changing from active to suspended","Suspending VSAN with ID [dec] from active state.","No action is required."
"VSAN","6","TRUNKING_MEMBERSHIP_UPDATE","trunking membership updated for interface:[chars] with VSAN bitmap:[chars]","Updated trunking membership for interface [chars1] with allowed VSAN list [chars2].","No action is required."
"VSC-SLOT#","2","CPP_CATASTROPHIC_ERR","ERROR: Component ([chars]) caused critical error","Virtualization software suffers critical error","Perform graceful shutdown and restart the linecard"
"VSC-SLOT#","2","CPP_RELOAD","Component ([chars]) is reloading the linecard","No response to critical error notification from application","Response to critical error notification and perform graceful shutdown"
"VSC-SLOT#","2","REGISTER_NOTIF_REPLY_FAILED","Component ([chars]) fails to register to receive notification reply","System will not receive partner notification reply","Virtualization software will restart the linecard after reply timeout."
"VSC-SLOT#","3","SSM_GET_SW_CARDID","Get SSM software card ID failed","SSM get software card ID failed","There is a serious error and the linecard need to be restarted"
"VSC-SLOT#","5","RX_PS_CRITICAL_NOTIF_REPLY","Component ([chars]) receives critical error notification reply","Partner software will handle critical error","Virtualization software wontrestartthelinecard.Itispartnersoftwareresponsiblitytodoshutdown'"
"VSD-SLOT#","2","CPP_CATASTROPHIC_ERROR","ERROR: Component ([chars]) caused critical error please reboot SSM","Component caused critical error","Restart the linecard"
"VSD-SLOT#","6","VSD_INFO","[chars]","VSD daemon informational message","No action is required."
"VSHA","3","VSHA_INIT_FAILED","Initialization failed. Component [chars]","The service failed to start. The failure is happened initializing the specified component","No action is required."
"VSHA-SLOT#","3","LOG_VSHA_STATE_TIMEOUT","VSHA Shutting Down. Deport Wait Timeout for sg: [chars] (vrid [dec]).","SG was being shutdown. But DG could not be deported within specified time by the linecard","No action is required."
"VSHA-SLOT#","3","LOG_VSHA_STATE","VSHA Shutting Down. Failure to deport dg: [chars] from sg: [chars] (vrid [dec]).","DG was either removed from SG or SG was offlined. But DG could not be deported by the linecard","No action is required."
"VSHA-SLOT#","5","LOG_VSHA_ARBT_DISK_STATE","Arbitration_disk [chars] for Service_Group [chars] (vrid [dec]) in error state","FCDD has reported arbt_disk as deleted/noi longer accessible.","No action is required."
"VSHA-SLOT#","5","LOG_VSHA_DG_STATE","Disk_Group [chars] from Service_Group [chars] (vrid [dec]) in error state","VSHA resource monitor has detected dg is not accessible.","No action is required."
"VSHA-SLOT#","5","LOG_VSHA_SG_STATE","State change for sg [chars] (vrid [dec]). New state is [chars]. State change reason is [chars]","Either a failover or user command caused a sg state change.","No action is required."
"VSHD","2","VSHD_SYSLOG_EOL_ERR","EOL function [chars] from library [chars] exited due to Signal [dec]","Error in CLI EOL function","No action is required."
"VSHD","2","VSHD_SYSLOG_PSS_SNAPSHOT_ERR","Source URI:[chars] Destination URI:[chars] errcode:[dec]","PSS snapshot error","No action is required."
"VSHD","2","VSHD_SYSLOG_SDWRAP_ERR","Description:[chars] errcode:[dec]","Debug infrastructure error","No action is required."
"VSHD","3","VSHD_ROLE_DISTRIBUTE_FAILURE","Role distribution operation ([chars]) failed with error id [hex]","This is probably occurring due to unstable fabric","Please retry operation when fabric is stable"
"VSHD","3","VSHD_SYSLOG_FILE_ERR","Purpose:[chars] Filename:[chars] errcode:[dec]","File handling error","No action is required."
"VSHD","3","VSHD_SYSLOG_MTS_ERR","message [chars]","MTS message handling error","No action is required."
"VSHD","3","VSHD_SYSLOG_PARSE_TREE_ERR","[chars]","Error while updating parse tree in shell","No action is required."
"VSHD","3","VSHD_SYSLOG_PSS_ERR","Purpose:[chars] URI:[chars] errcode:[dec]","PSS handling error","No action is required."
"VSHD","4","VSHD_LICENSE_EXPIRY_WARNING","License [chars] expires on [chars]. Vsan policy will be set to default (deny) for all roles when license expires","Vsan policy would be set default (deny) for all roles when license expires","Please install the license file to continue using the feature."
"VSHD","4","VSHD_ROLE_DATABASE_OUT_OF_SYNC","Role configuration database found to be different between the switches during merge","Role configuration database is recommended to be identical among all switches in the fabric.","Edit the configuration on one of the switches to obtain the desired role configuration database and then commit it"
"VSHD","4","VSHD_ROLE_DATABASE_VERSION_NOT_UNDERSTOOD","This switch does not understand the version of role configuration database received during merge","This is probably occurring due to different versions of system image on switches in the fabric","Please make sure all switches are running the same version of the system image"
"VSHD","5","VSHD_SYSLOG_CONFIG_CHANGE","VDC=[chars], VTY=[chars], user=[chars], CMD='[chars]'","Configuration change notification","No action is required."
"VSHD","5","VSHD_SYSLOG_CONFIG_I","Configured from vty by [chars] on [chars]","CLI Configuration mode was exited","No action is required."
"VSHD","5","VSHD_SYSLOG_ROLE_CREATED","New cli role [chars] created","New cli role created","No action is required."
"VSHD","7","VSHD_SYSLOG_PARSE_TREE_UPDATE","Parse tree [chars]","Parse tree updated in shell","No action is required."
"VTP","0","EMERGENCY_MSG","[chars]","VTP Emergency Message","Capture show tech-support vtp"
"VTP","1","ALERT_MSG","[chars]","VTP Alert Message","Capture show tech-support vtp"
"VTP","2","CRITICAL_MSG","[chars]","VTP Critical Message","No action is required."
"VTP","2","VTP_MODE_OFF_LONG_VLAN_NAME_EXIST","VTP Mode changed to off as long vlan configuration exists","By default, VTP feature comes up in Server mode. long vlans can only operate in VTP transparent/off mode As long Vlan configuration already exist, VTP mode is changed to off.","No action is required."
"VTP","2","VTP_MODE_OFF_PVLAN_EXIST","VTP Mode changed to off as Private VLAN configuration exists","By default, VTP feature comes up in Server mode. Private Vlans can only operate in VTP transparent/off mode As Private Vlan configuration already exist, VTP mode is changed to off.","No action is required."
"VTP","2","VTP_MODE_OFF_RESERVED_VLAN_EXIST","VTP Mode changed to off as reserved vlan configuration exists","By default, VTP feature comes up in Server mode. reserved vlans can only operate in VTP transparent/off mode As Reserved Vlan configuration already exist, VTP mode is changed to off.","No action is required."
"VTP","2","VTP_MODE_TRANSPARENT_VLAN_RES_LIMIT_EXIST","VTP Mode changed to transparent as vlan resource limit configuration exists","By default, VTP feature comes up in Server mode. resource limit configuration can only operate in VTP transparent/off mode As vlan resouce limit configuaration exists, VTP mode is changed to transparent.","No action is required."
"VTP","3","ERROR_MSG","[chars]","VTP Error Message","No action is required."
"VTP","4","BAD_STARTUP_VLAN_CONFIG_FILE","Failed to configure VLAN from startup-config. Fallback to use VLAN configuration file from non-volatile memory","VLAN software failed to use VLAN configuration from startup-config file. It will fallback to use the binary VLAN configuration file in non-volatile memory.","No action is required."
"VTP","4","VLAN_CREATE_FAIL","Failed to create VLANs [chars]: [chars]","The VLANs specified in the error message could not be created. The VLAN manager called an VLAN database routine to create one or more VLANs, but the Vlan Manager failed the VLAN creation requests.","Collect show tech-support"
"VTP","4","VTP_BAD_VLAN_CONFIGURATION_FILE_VERSION","VLAN configuration file contained unknown file version: [dec]","The VLAN configuration file read by the VLAN manager contained an unrecognized file version number. (This may indicate an attempt to regress to an older version of the VLAN manager software.)","LOG_STD_ACTION"
"VTP","4","VTP_BAD_VLAN_CONFIGURATION_FILE","Vlan configuration file contained incorrect verification word: [hex]","The VLAN configuration file read by the VLAN manager did not begin with correct value which would indicate a valid VLAN configuration file. Thus, it has been rejected.","Collect show tech-support"
"VTP","4","VTP_BAD_VLAN_DOMAIN_NAME_LENGTH","VLAN configuration file contained incorrect domain name length: [dec]","The VLAN configuration file read by the VLAN manager did not contain a valid domain name length. Thus, it has been rejected.","Please provision VTP domain name again"
"VTP","4","VTP_BAD_VLAN_PASSWORD_LENGTH","VLAN configuration file contained incorrect VTP password length: [dec]","The VLAN configuration file read by the VLAN manager did not contain a valid VTP password length. Thus, it has been rejected.","Please provision VTP password again"
"VTP","4","VTP_INVALID_DATABASE_DATA","VTP received bad data","Invalid data was received by VTP process","Collect show tech-support"
"VTP","4","VTP_PROTOCOL_ERROR","VTP protocol code internal error: [chars]","VTP protocol code encountered an unexpected error will processing configuration request, packet, or timer expiration.","Collect show tech-support"
"VTP","4","WARN_MSG","[chars]","VTP Warning Message","No action is required."
"VTP","5","NOTIF_MSG","[chars]","VTP Notification Message","No action is required."
"VTP","6","IFS_FAILURE","VLAN manager encountered file operation error: call = [chars] / file = [chars] / code = [dec] ([chars]) / bytes transfered = [dec]","VTP received an unexpected error return from a file system call.","Collect show tech-support"
"VTP","6","INFO_MSG","[chars]","VTP Informational Message","No action is required."
"VTP","6","VTP_DOMAIN_NAME_CHG","VTP domain name changed to [chars].","The VTP domain name was changed through configuration to the name specified in the message. A management domain is the naming scope of a VLAN name. Each VLAN has a name that is unique within the management domain.","No action is required."
"VTP","6","VTP_MODE_CHANGE","VLAN manager changing device mode from [chars] to [chars].","Some switch devices must automatically change VTP device modes upon receipt of a VLAN configuration database containing more than a set number of VLANs, depending on the device. This message indicates that such a spontaneous conversion has occurred, what the previous mode was, and what the current mode is.","No action is required."
"VTP","6","VTP_OLD_CONFIG_FILE_READ","Old version [dec] VLAN configuration file detected and read OK. Version [dec] files will be written in the future.","VLAN software detected an old version of the VLAN configuration file format. It was able to interpret the file with no problems but will create files using the new format in the future.","No action is required."
"VTP","6","VTP_PRUNING_CHANGE","VTP Operational Pruning [chars].","VTP operational pruning changed. This can happen due to admin pruning change, VTP mode changes or VTP config propagation. showvtpstatus'outputcanbelookeduptofindthereasonforthischange.'","Check showvtpstatus'outputtofindthereasonforthischange.Noactionisrequired.'"
"VTP","7","DEBUG_MSG","[chars]","Association Manager Debug Message","No action is required."
"WWN","1","TYPE1_ALERT","[dec] (< [dec] %) Remain","The WWN Manager has run out of WWNs. No new dynamically allocated WWNs are available. However, statically assigned WWNs such as switch WWN, port WWN, etc. are still available.","Please add additional WWNs by programming a new Secondary MAC address and its range."
"WWN","1","TYPES2_5_ALERT","Only [dec] (< [dec] %) Type 2 & 5 WWNs Remain","The WWN Manager has run out of WWNs of NAA Types 2 and 5","Please add additional WWNs by programming a new Secondary MAC address and its range."
"WWN","2","BKPLN_PROM_CANT_READ","Can not read backplane PROM","The WWN Manager has failed to read chassis information. No dynamic WWNs could be allocated.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"WWN","2","EXITING","Exited due to [chars]","The WWN Manager process has exited due to [char]. The process has probably been restarted automatically.","No action is required."
"WWN","2","GENERAL_ERROR","[chars]","The WWN Manager has encountered an critical error. The description of error is [str.].","No action is required."
"WWN","2","MALLOC_ERROR","Size [dec] bytes","The WWN Manager could not allocate memory.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"WWN","2","PSS_BKP_PSS_MISMATCH","Block [dec]: PSS: Not Free; BKPLN PROM: Free","This WWN Manager detected a discrepancy between the information on the chassis and that in its persistent information databases. The persistent information database has been updated with the information on the chassis.","No action is required."
"WWN","2","PSS_ERROR","[chars]","The WWN Manager encountered error while operating on a persistent storage database.","No action is required."
"WWN","2","STDOUT_ROTATE_FAILURE","Failed to rotate stdout file: [chars]","The WWN Manager has failed to rotate its current stdout file with filename [str.]. The filesize could grow beyond its maximum limit.","No action is required."
"WWN","2","TYPE1_CRIT","[dec] (< [dec] %) Remain","The WWN Manager has only [dec] or less than [dec]-percent WWNs remaining.","Please add additional WWNs by programming a new Secondary MAC address and its range."
"WWN","2","TYPES2_5_CRIT","[dec] (< [dec] %) Remain","The WWN Manager has only [dec] or less than [dec]-percent WWNs of NAA Types 2 and 5 remaining.","Please add additional WWNs by programming a new Secondary MAC address and its range."
"WWN","3","PSS_SYNC_TO_STNDBY_FAILED","PSS TYPE=[chars] KEY=[chars]","Could not send PSS Sync. notification to Standby Supervisor. PSS Type=[str.] Operation=[.str] Key=[Str.].","No action is required."
"WWN","3","RELEASE_ERR_UNKNOWN","Unknown WWN [chars] [chars]","WWN Manager received a request to release a WWN [char] that could not have been allocated by this WWN Manager due to [char].","No action is required."
"WWN","3","RELEASE_ERR","Cant Rel. WWN [chars]","WWN Manager received a request to release a WWN that cannot be released.","No action is required."
"WWN","3","STARTUP_COPY_TO_RUNNING_FAILED","[chars]","Could not snapshot Startup-Config PSS to Running-Config. The description of error is [str.].","No action is required."
"WWN","3","TOOMANY_REQ_REL","WWNs [chars] = [dec]","The WWN Manager received a request to allocate [dec] WWN, which is more than the maximum number of WWNs that can be allocated/released in a single request.","No action is required."
"WWN","3","UNKNOWN_MSG","Received from Node=[dec] SAP=[dec] Opcode=[dec]","The WWN Manager has received an unknown message from [dec]].[dec] with opcode [dec]. This information is for debugging only.","No action is required."
"WWN","3","WWN_PSS_CORRUPTED","[chars] PSS found corrupted","The WWN Manager has detected corruption in one of its persistent information database. The database would be recreated.","No action is required."
"WWN","4","PSS_SUP_CNT_MISMATCH","PSS [dec] Bkpln [dec]","The WWN Manager has detected that some other supervisor card was plugged in earlier on this chassis. This WWN Manager is making sure that new WWNs allocate do not conflict with WWNs that could have been allocated by the previous supervisor card.","No action is required."
"WWN","4","PSS_VERSION_MISMATCH","PSS [dec] Code [dec]","There was a version mismatch between the WWN Manager and one of its persistent storage databases. The persistent information has been translated to the new format.","No action is required."
"WWN","4","TYPE1_WARN","[dec] (< [dec] %) Remain","The WWN Manager has only [dec] or less than [dec]-percent WWNs remaining for allocation.","No action is required."
"WWN","4","TYPES2_5_WARN","[dec] (< [dec] %) Remain","The WWN Manager has only [dec] or less than [dec]-percent WWNs of NAA Types 2 and 5 remaining.","Please add additional WWNs by programming a new Secondary MAC address and its range."
"WWN","5","VSAN_WWN_CHANGE","[chars]","VSAN-WWN created or deleted. The description of error is [str.].","No action is required."
"WWN","6","ALLOCATED_BLOCK","Block number [dec]","The WWN Manager has allocated a new block, block number [dec], of 256 WWNs for internal use.","No action is required."
"WWN","6","BECAME_ACTIVE","Became ACTIVE from standby mode","The WWN Manager on the standby supervisor became active and it is ready to serve client requests for WWNs.","No action is required."
"WWN","6","BECAME_STDBY","Became STANDBY from active mode","The WWN Manager became standby from active mode.","No action is required."
"WWN","6","EXCESSIVE_DELAY","[chars]","Excessive time taken for a processing event. The description of the event is [str.].","No action is required."
"WWN","6","FAILED_TO_SEND_HEARTBEAT","Failed to send heartbeat to system manager: Reason=[chars]","The WWN Manager was unable to send heartbeat to the system manager.","No action is required."
"WWN","6","GENERAL_EVENT","[chars]","The WWN Manager has generated an important event. The description of the event is [str.].","No action is required."
"WWN","6","PSS_CREATED","[chars] PSS Created","One of the persistent information database of the WWN Manager has been recreated.","No action is required."
"WWN","6","PSS_DESTROYED","[chars] PSS Destroyed","One of the persistent information databases has been intentionally destroyed and would be recreated.","No action is required."
"WWN","6","RELEASED_BLOCK","Block number [dec]","The WWN Manager has released a block, block number [dec], of 256 WWNs.","No action is required."
"WWN","6","SEC_MAC_UPDATED","MAC=[chars] Range=[dec]","The WWN Manager had updated the Secondary MAC address with MAC address [char] and range [dec]. This update was initiated from a management entity.","No action is required."
"WWN","6","SERVICE_UP","Initialized [chars]","The WWN Manager is up and ready to accept client requests for WWNs. The service was initialized in [char] mode.","No action is required."
"WWN","6","SWITCHOVER","Switching Over to other Supervisor","The WWN Manager has successfully switched over to the standby supervisor card.","No action is required."
"WWN","7","RELEASE_ERR_FREE","Already free WWN [chars]","A client of WWN Manager attempted to release WWN [char] which is already free. This information is for debugging only.","No action is required."
"X2_USD","2","DC3_X2_SYSLOG_INTERNAL_SOFTWARE_ERROR","An internal error in the X2 driver occurred on port [dec]: [chars] [dec]","An unexpected internal X2 driver software error occurred","Contact technical support"
"X2_USD","2","DC3_X2_SYSLOG_INVALID_TRANSCEIVER_TYPE","Module in port [dec] has an invalid transceiver type of [hex]","An unsupported module was plugged into the port","Retry with a supported module"
"X2_USD","2","DC3_X2_SYSLOG_NVRAM_CHKSUM_FAILURE","NVRAM checksum failure for module in port [dec]","Non-volatile memory checksum error in module","Remove and reinsert module and retry opeartion"
"X2_USD","2","DC3_X2_SYSLOG_ONEX_INITIALIZATION_FAILURE","A validated OneX module in port [dec] failed initialization with error [hex]","A OneX module was detected and validated, but failed initialization","Remove and reinsert module and retry opeartion"
"X2_USD","2","DC3_X2_SYSLOG_ONEX_VALIDATION_FAILURE","OneX module in port [dec] failed validation with error [hex]","A counterfeit OneX module detected, or a valid OneX has a corrupt sprom","Replace OneX module"
"X2_USD","5","DC3_X2_SYSLOG_ONEX_INSERTION","OneX inserted into port [dec]","OneX X2 to SFP+ Converter inserted is detected","Ensure OneX insertion an expected action"
"X2_USD","5","DC3_X2_SYSLOG_ONEX_REMOVAL","OneX removed from port [dec]","OneX X2 to SFP+ Converter removal is detected","Ensure OneX removal an expected action"
"X2_USD","5","DC3_X2_SYSLOG_ONEX_SFPPLUS_INSERTION","SFP+ inserted into port [dec]","SFP+ insertion into OneX X2 to SFP+ Converter detected","Ensure SFP+ insertion into OneX an expected action"
"X2_USD","5","DC3_X2_SYSLOG_ONEX_SFPPLUS_REMOVAL","SFP+ removed from port [dec]","SFP+ removal from OneX X2 to SFP+ Converter detected","Ensure SFP+ removal from OneX an expected action"
"XBAR_CLIENT","2","CROSS_LINK_SYNC_LOSS","XBAR-[chars].","Cross links lost sync and hence xbar is brought down.","Please reload the xbar using reloadxbar<xbar-num"
"XBAR_CLIENT","2","MEM_FULL","Memory allocation failed.","XBAR_CLIENT process has failed to allocate memory.","Please perform a showxbar-clientevent-history'tocollectmoreinformation.'"
"XBAR_CLIENT","2","MEM_FULL","memory allocation failed","Process xbar_client failed to allocate memory","Please examine the xbar-client event-history for more information."
"XBAR_CLIENT","2","PROC_DN","Process is shutting down: [chars].","XBAR_CLIENT process is exiting.","Please perform a showxbar-clientevent-history'tocollectmoreinformation.'"
"XBAR_CLIENT","2","PROC_DN","exiting: [chars].","Process xbar_client is exiting","Please examine the xbar-client event-history for more information."
"XBAR_CLIENT","2","PROC_INITFAIL","Process initialization failed due to [chars].","XBAR_CLIENT process has failed initialization.","Please perform a showxbar-clientevent-history'tocollectmoreinformation.'"
"XBAR_CLIENT","2","PROC_INITFAIL","Process initialization failed due to [chars].","XBAR_CLIENT process has failed initialization.","Please perform a showxbar-clientevent-history'tocollectmoreinformation.'"
"XBAR_CLIENT","2","PROC_INITFAIL","initialization failed due to [chars]","Process xbar_client failed initialization","Please examine the xbar-client event-history for more information."
"XBAR_CLIENT","3","IPC_MSGERR","Error in processing IPC message: [dec], Error code = [dec].","XBAR_CLIENT process has encountered an error in processing message.","Please perform a showxbar-clientevent-history'tocollectmoreinformation.'"
"XBAR_CLIENT","3","IPC_MSGERR","failure processing IPC message [dec], error code = [dec]","Process xbar_client failed to process IPC message","Please examine the xbar-client event-history for more information."
"XBAR_CLIENT","3","IPC_MSGUNKN","Received unexpected IPC message: [dec].","XBAR_CLIENT process has received an unknown message.","Please perform a showxbar-clientevent-history'tocollectmoreinformation.'"
"XBAR_CLIENT","3","IPC_MSGUNKN","unknown IPC message received: [dec]","Process xbar_client has received an unknown IPC message.","Please examine the xbar-client event-history for more information."
"XBAR_CLIENT","3","SUP2_XBC_MOD_INIT_FAIL","[chars], errcode - [hex]","The module initialiazation failed","Please perform a showprocessxbar-clientevent-history'tocollectmoreinformation'"
"XBAR_CLIENT-SLOT#","2","VEGAS2_XBC_MEM_FULL","memory allocation failed in routine [chars]","Process xbar_client failed to allocate memory","Please perform a showprocessxbar-clientevent-history'tocollectmoreinformation'"
"XBAR_CLIENT-SLOT#","2","VEGAS2_XBC_PROC_DN","terminating due to signal [dec]","Process xbar_client is exiting","Please perform a showprocessxbar-clientevent-history'tocollectmoreinformation'"
"XBAR_CLIENT-SLOT#","2","VEGAS2_XBC_PROC_INITFAIL","initialization failed: [chars], errno [dec]","Process xbar_client failed initialization","Please perform a showprocessxbar-clientevent-history'tocollectmoreinformation'"
"XBAR_CLIENT-SLOT#","3","VEGAS2_XBC_IPC_MSGUNKN","unknown IPC message received: opcode [dec]","Process xbar_client hass received an unknown IPC message","Please perform a showprocessxbar-clientevent-history'tocollectmoreinformation'"
"XBAR_CLIENT-SLOT#","3","VEGAS2_XBC_MOD_INIT_FAIL","[chars], errcode - [hex]","The module initialiazation failed","Please perform a showprocessxbar-clientevent-history'tocollectmoreinformation'"
"XBAR_DRIVER_USD","2","SCZ_ACCESS_FAILED","Xbar Driver Failed to access reg for [chars]","Xbar Driver Access failed","No action is required."
"XBAR_DRIVER_USD","2","SCZ_CATASTROPHIC","Xbar Driver catastrophic failure: [chars]Error Message    Ex XBAR_DRIVER_USD-2-SCZ_CATASTROPHIC: Xbar Driver catastrophic failure: [chars]","Xbar Driver catastrophic error","No action is required."
"XBAR_DRIVER_USD","2","SCZ_INTR","Xbar Driver Interrupt occurred: [chars]","Interrupt occurred on the xbar","No action is required."
"XBAR_DRIVER_USD","2","SCZ_SW_INIT_ABORTED","Xbar Driver Failed to finish Software Initialization: [chars]","Xbar Driver Software Initialization failed","No action is required."
"XBAR_DRIVER_USD","2","SHUTDOWN","Xbar Driver software process exiting: [chars]","Xbar Driver shutting down","No action is required."
"XBAR_DRIVER_USD","2","SYNC_FAILED","Xbar Driver sync failed: [chars]","Xbar Driver Sync failed for the xbar channel","No action is required."
"XBAR_DRIVER_USD","3","EN_DATA_FAILED","Xbar Driver enable data failed for slot:[dec] asic:[dec] channel: [hex]","Xbar Driver Enable Datapath failed for the xbar channel","No action is required."
"XBAR_DRIVER_USD","5","STARTING","Xbar Driver process starting","Xbar Driver process is being started","No action is required."
"XBAR_DRIVER_USD","6","DIS_DATA","Xbar Driver disable datapath done for slot:[dec] asic:[dec] channel: [hex]","Disabled Datapath successfully for the xbar channel","No action is required."
"XBAR_DRIVER_USD","6","EN_DATA","Xbar Driver enable datapath done for slot:[dec] asic:[dec] channel: [hex]","Enabled Datapath successfully for the xbar channel","No action is required."
"XBAR_DRIVER_USD","6","HW_INIT","Xbar DriverHW initialization has been done for Slot: [dec] Asic: [dec]","Xbar Driver HW initializtion has been called[dec]","No action is required."
"XBAR_DRIVER_USD","6","SYNC_DONE","Xbar Driver sync done for slot:[dec] asic:[dec] channel: [hex]","Sync Completed successfully for the xbar channel","No action is required."
"XBAR","2","ARB_INIT_FAIL","Arbiter Initialization failed return_code [hex] ([chars]).","The supervisor has experienced an arbiter setup failure .","No action is required."
"XBAR","2","INCOMPATIBLE_CONFIG","[chars] [dec] [chars].","This module is not compatible with the current fabric mode. It will be powered down.","No action is required."
"XBAR","2","XBAR_INSUFFICIENT_XBAR_BANDWIDTH","Module in slot [dec] has insufficient xbar-bandwidth.","To track insufficient xbar-bandwidth.","No action is required."
"XBAR","2","XBAR_MIXED_SPINES_POLICY_MATCHED","[chars]","Fabric could not be brought online due to policy match","No action is required."
"XBAR","2","XBAR_SUFFICIENT_XBAR_BANDWIDTH","Module in slot [dec] has sufficient xbar-bandwidth.","To track recovery from insufficient xbar-bandwidth.","No action is required."
"XBAR","2","XBM_EEM_FABRIC_ACTION","Fabric [chars] has been reloaded by xbar-manager because of an eem-policy triggered action [chars] %i","Xbar-manager has removed the fabric because an eem policy has been met This means that the fabric has hit the maximum number of recoverable sync-losses with multiple line-cards within a time-window.","No action is required."
"XBAR","2","XBM_EEM_MODULE_ACTION","Module [chars] has been reloaded by xbar-manager because of an eem-policy triggered action [chars] %i","Xbar-manager has removed the linecard because an eem policy has been met This means that the module has hit the maximum number of recoverable sync-losses with fabric card(s) within a time-window.","No action is required."
"XBAR","3","MEM_FULL","Memory allocation failed. [chars] %i","Recommended Action    No action is required.XBAR-4Error Message    XBAR-4-XBAR_MIXED_SPINES_IN_CHASSIS: [chars] Explanation    There are both FAB-1 and FAB-2 type spines in the Chassis. Please replace the FAB-1 spines with FAB-2 Spines.","No action is required."
"XBAR","5","ARBITER_INIT_FAILURE","Re-initializing Arbiter. [chars] [chars] module %i","The supervisor has experienced an arbiter setup failure .","No action is required."
"XBAR","5","ARB_CLEAR_PORT_FAIL","Arbiter reported failure to de-register port [dec] in group [dec] return_code [hex] ([chars]).","The supervisor has experienced an arbiter setup failure .","No action is required."
"XBAR","5","ARB_INIT_MOD_DIS_INTR_FAIL","Arbiter reported failure to disable interrupt for module [dec] return_code [hex] ([chars]).","The supervisor has experienced an arbiter setup failure .","No action is required."
"XBAR","5","ARB_INIT_MOD_INSERT_CHECK_FAIL","Arbiter reported failure to recognize module [dec] return_code [hex] ([chars]).","The supervisor has experienced an arbiter setup failure .","No action is required."
"XBAR","5","ARB_INIT_MOD_INSERT_FAIL","Arbiter reported failure to init module [dec] return_code [hex] ([chars]).","The supervisor has experienced an arbiter setup failure .","No action is required."
"XBAR","5","ARB_INIT_MOD_INTR_FAIL","Arbiter reported failure to enable interrupt for module [dec] return_code [hex] ([chars]).","The supervisor has experienced an arbiter setup failure .","No action is required."
"XBAR","5","ARB_INIT_MOD_REMOVE_FAIL","Arbiter reported failure to remove module [dec] return_code [hex] ([chars]).","The supervisor has experienced an arbiter setup failure .","No action is required."
"XBAR","5","ARB_INIT_PORT_FAIL","Arbiter reported failure to register port [dec] in group [dec] return_code [hex] ([chars]).","The supervisor has experienced an arbiter setup failure .","No action is required."
"XBAR","5","MOD_CONNECTION_REATTEMPT","Re-attempting XBAR connection with module [dec]","The module has experienced a setup failure on connecting the module to the fabric.","Collect more informations about XBAR component Use command showxbarinternalevent-historymodule<moduleid"
"XBAR","5","SYNC_THRESHOLD_FAILURE","Module resync threshold exceeded [chars] [chars] module %i","This module has exceeded the number of resync attempts in a day. Module will be reloaded","No action is required."
"XBAR","5","XBAR_ENABLE_FPOE_DB_FAILURE","XBAR [chars] enabling FPOE-DB mode failed","The supervisor failed to enable FPOE-DB mode in fabric. The supervisor is going to reboot. In case of dual supervisor, a switchover will occur.","No action is required."
"XBAR","5","XBAR_INIT_FAILURE","XBAR [chars] initialization failed [chars] %i","The supervisor has experienced a fabric initialization failure. The supervisor is going to reboot. In case of dual supervisor, a switchover will occur.","No action is required."
"XBAR","5","XBAR_INIT_FAIL","Xbar [[dec].[dec]] reported failure durinig intialization return_code [hex] ([chars]).","The supervisor has experienced an xbar setup failure .","No action is required."
"XBAR","5","XBAR_MOD_INSERT_SEQ_FAILURE","[chars] for module [dec]","The xbar manager received failure response and is failing the insert sequence","No action is required."
"XBAR","5","XBAR_MOD_LC_INSERT_SEQ_FAILURE","Module in slot [dec] has failed insert sequence","The xbar manager is failing the insert sequence","No action is required."
"XBAR","5","XBAR_PORT_CHECK_SYNC_FAIL","Xbar [[dec].[dec]] reported failure to check sync on port [dec] return_code [hex] ([chars]).","The supervisor has experienced an xbar setup failure .","No action is required."
"XBAR","5","XBAR_PORT_CONTINUE_SYNC_FAIL","Xbar [[dec].[dec]] reported failure to continue sync on port [dec] return_code [hex] ([chars]).","The supervisor has experienced an xbar setup failure .","No action is required."
"XBAR","5","XBAR_PORT_DISABLE_FAIL","Xbar [[dec].[dec]] reported failure to disable port [dec] return_code [hex] ([chars]).","The supervisor has experienced an xbar setup failure .","No action is required."
"XBAR","5","XBAR_PORT_ENABLE_FAIL","Xbar [[dec].[dec]] reported failure to enable port [dec] return_code [hex] ([chars]).","The supervisor has experienced an xbar setup failure .","No action is required."
"XBAR","5","XBAR_PORT_FORCE_POE_DISABLE_FAIL","Xbar [[dec].[dec]] reported failure to disable force poe mode on [dec] return_code [hex] ([chars]).","The supervisor has experienced an xbar setup failure .","No action is required."
"XBAR","5","XBAR_PORT_FORCE_POE_ENABLE_FAIL","Xbar [[dec].[dec]] reported failure to enable force poe mode on [dec] return_code [hex] ([chars]).","The supervisor has experienced an xbar setup failure .","No action is required."
"XBAR","5","XBAR_PORT_LPBACK_DISABLE_FAIL","Xbar [[dec].[dec]] reported failure to disable port loopback on [dec] return_code [hex] ([chars]).","The supervisor has experienced an xbar setup failure .","No action is required."
"XBAR","5","XBAR_PORT_LPBACK_ENABLE_FAIL","Xbar [[dec].[dec]] reported failure to enable port loopback on [dec] return_code [hex] ([chars]).","The supervisor has experienced an xbar setup failure .","No action is required."
"XBAR","5","XBAR_PORT_START_SYNC_FAIL","Xbar [[dec].[dec]] reported failure to start sync on port [dec] return_code [hex] ([chars]).","The supervisor has experienced an xbar setup failure .","No action is required."
"XBAR","5","XBAR_RELEASE_ACCESS_FAIL","Slot [dec] reported failure releasing [chars] xbar access return_code [hex] ([chars])","The supervisor has experienced an xbar access failure .","No action is required."
"XBAR","5","XBAR_SET_ACCESS_FAIL","Slot [dec] reported failure acquiring [chars] xbar access return_code [hex] ([chars])","The supervisor has experienced an xbar access failure .","No action is required."
"XBAR","5","XBAR_STANDBY_SUP_ARB_FAIL","[chars] return_code [hex] ([chars])","The supervisor has experienced an arbiter access failure .","No action is required."
"XBAR","5","XBAR_STATUS_REPORT","Module [dec] reported status for component [dec] code [hex].","An error status has been reported. If error is on supervisor, the supervisor is going to reboot. In case of dual supervisors, a switchover will occur. If error is on module, the module will be power cycled.","No action is required."
"XBAR","5","XBAR_SW_INIT_FAIL","Xbar [[dec].[dec]] reported failure durinig sw intialization return_code [hex] ([chars]).","The supervisor has experienced an xbar setup failure .","No action is required."
"XBAR","5","XBAR_VERSION_CHECK_FAILURE","XBAR [chars] SCZ version check failed [chars] %i","This SUP has an older Santacruz version, and so will not be allowed to power-up, Please upgrade to the latest supervisor version.","No action is required."
"XCVR_USD","6","XCVR_USD_DEBUG_MSG","[chars]","Debug log message","No action is required."
"XCVR_USD","6","XCVR_USD_LOG_MSG","[chars]","Debug log messageNo action is required.XCVR MessagesThis section contains the XCVR messages.XCVR-6Error Message    XCVR-6-XCVR_LIB_DEBUG_MSG: [chars] Explanation    Debug log message","No action is required."
"XCVR","6","XCVR_LIB_DEBUG_MSG","[chars]","Debug log message","No action is required."
"XMLMA","2","HEARTBEAT_FAIL","XML master agent failed to send heart beat: [chars]","XML master agent has failed sending heartbeat.","No action is required."
"XMLMA","2","INITFAIL","XML master agent initialization fails: [chars]","XML master agent has failed initialization.","No action is required."
"XMLMA","2","MTSERROR","XML master agent mts operation failed: [chars]","XML master agent mts operation failed.","No action is required."
"XMLMA","2","PSSFAILURE","XML master agent pss operation failed: [chars]","XML master agent pss operation failed.","No action is required."
"XMLMA","2","XMLMACRIT","XML master agent: [chars]","XML master agent critical log.","No action is required."
"XMLMA","3","XMLMAERR","XML master agent: [chars]","XML master agent error log.","No action is required."
"XMLMA","5","STARTING","XML master agent started [chars]","XML master agent has been started.","No action is required."
"XMLMA","6","XMLMAEXIT","XML master agent exiting...: [chars]","XML master agent is exiting.","No action is required."
"XMLMA","6","XMLMALOG","XML master agent operation log: [chars]","XML master agent operation log.","No action is required."
"XMLSA","2","HEARTBEAT_FAIL","XML sub agent failed sending heart beat: [chars]","XML sub agent failed sending heartbeat.","No action is required."
"XMLSA","2","INITFAIL","XML sub agent initialization fails: [chars]","XML agent has failed initialization.","No action is required."
"XMLSA","2","USER_INACTIVE","XML sub agent timeed out: [chars]","XML sub agent timedout due to inactivity.","No action is required."
"XMLSA","2","VSH_ERR","XML sub agent vsh cmd error...: [chars]","XML sub agent vsh cmd error.","No action is required."
"XMLSA","5","STARTING","XML sub agent started: [chars]","XML sub agent has been started.","No action is required."
"XMLSA","6","XMLSAEXIT","XML sub agent exiting...: [chars]","XML sub agent is exiting.","No action is required."
"XMLSA","6","XMLSALOG","XML sub agent log: [chars]","XML sub agent log.","No action is required."
"ZBM","2","ZBM_HA_FAILURE","Failed to do high availability operation: [chars].","Failed to do high availability operation. [chars] is the reason.","No action is required."
"ZBM","2","ZBM_INIT_FAILED","Initialization failed for ZBM: [chars], reason: [hex].","Initialization failed for ZBM due to [chars], reason: [hex].","No action is required."
"ZBM","2","ZBM_INIT_WARNING","Initialization warning for ZBM: [chars], reason: [hex].","Initialization warning for ZBM due to [chars], reason: [hex].","No action is required."
"ZBM","2","ZBM_LINECARD_STATUS","Status from linecard: [dec], for module: [chars](ID: [dec]), status : [dec], error_id: [hex], catastrophic: [chars], restart count: [dec].","Status from linecard: [dec], for module: [chars](ID: [dec]), status : [dec], error_id: [hex], catastrophic: [chars], restart count: [dec].","No action is required."
"ZBM","2","ZBM_MALLOC_FAILURE","Memory allocation failed for size [dec]","Memory allocation is failed for size [dec] bytes.","Restart the process."
"ZBM","2","ZBM_MTS_FAILURE","Failed to do MTS operation: [chars].","Failed to do MTS operation. [chars] is the reason.","No action is required."
"ZBM","2","ZBM_MTS_REGISTRATION_FAILED","MTS options setting to [hex] failed for opCode: [dec].","MTS options setting to [hex] failed for opCode: [dec].","No action is required."
"ZBM","2","ZBM_PSS_FAILURE","Failed to do PSS operation: [chars], reason: [hex].","Failed to do PSS operation [chars]. [hex] is the reason.","No action is required."
"ZBM","2","ZBM_PSS_VER_FAIL","PSS file [chars] has version [dec].[dec].[dec], expected version [dec].[dec].[dec].","There was a mismatch in the PSS version. [chars] indicates the PSS service, [dec].[dec].[dec] its current version number and [dec].[dec].[dec] the expected version.","No action is required."
"ZBM","2","ZBM_RUNTIME_FAILURE","[chars] [dec], Error: [hex]","ZBM runtime failure is reported as [chars] [dec], reason: [hex].","No action is required."
"ZBM","2","ZBM_TCAM_FAILURE","Failed to do TCAM operation: [chars].","Failed to do TCAM operation. [chars] is the reason.","No action is required."
"ZBM","2","ZBM_TCAM_SEND","[chars]","Sending to tcam [chars]","No action is required."
"ZBM","4","ZBM_WARNING","[chars] [dec]","ZBM warning messages is reported as [chars] [dec].","No action is required."
"ZBM","6","ZBM_DIAG_EVENT_STATUS","[chars] [hex].","ZBM system health management event status is reported as [chars] [hex].","No action is required."
"ZBM","6","ZBM_ECHO_PROGRAMMING_FAILED","[chars].","Programming echo entry failed for [chars].","No action is required."
"ZBM","6","ZBM_E_PORT_EVENT_STATUS","[chars] [chars].","ZBM xEport event status is reported as [chars] [chars].","No action is required."
"ZBM","6","ZBM_FCC_EVENT_STATUS","[chars] [chars].","ZBM FCC event status is reported as [chars] [chars].","No action is required."
"ZBM","6","ZBM_INIT_PROCESS","Zone Block Mgr process started [chars] at [chars]","Zone Block Mgr process started in [chars] (stateless/stateful) mode at time [chars].","No action is required."
"ZBM","6","ZBM_LINECARD_EVENT_STATUS","[chars] [hex].","ZBM linecard event status is reported as [chars] [dec].","No action is required."
"ZBM","6","ZBM_MCAST_EVENT_STATUS","[chars] [chars].","ZBM multicast event status is reported as [chars] [chars].","No action is required."
"ZBM","6","ZBM_NX_PORT_EVENT_STATUS","[chars] [chars].","ZBM Nx Port event status is reported as [chars] [chars].","No action is required."
"ZBM","6","ZBM_PORT_MODE_EVENT_STATUS","[chars] [chars].","ZBM portmode event status is reported as [chars] [chars].","No action is required."
"ZBM","6","ZBM_RUNTIME_STATUS","[chars] [dec]","ZBM runtime status is reported as [chars] [dec].","No action is required."
"ZBM","6","ZBM_STATUS","ZBM Status: [chars].","ZBM status is reported as [chars].","No action is required."
"ZBM","6","ZBM_UPDATE_SSRAM_QOS_EVENT_STATUS","[chars] [chars].","ZBM update SSRAM for QoS event status is reported as [chars] [chars].","No action is required."
"ZONE","2","LZ_EXITING","LUN/Read-only zoning process exited. Reason: [chars]","The LUN/Read-only zoning process has exited due to [char]. The process has probably been restarted automatically.","No action is required."
"ZONE","2","LZ_GENERAL_ERROR","[chars]","The LUN/Read-only zoning process has encountered a critical error. The description of error is [str].","No action is required."
"ZONE","2","LZ_INIT_FAILED","Initialization of LUN/Read-only zoning Process failed at [chars]","Initialization of LUN/Read-only zoning process failed at [char].","No action is required."
"ZONE","2","LZ_MALLOC_ERROR","Size [dec] bytes","The LUN/Read-only zoning process could not allocate memory.","Please contact the Cisco reseller through which you procured the product for support. If you have purchased a Cisco support contract please call Cisco TAC for support."
"ZONE","2","ZS_ALIAS_LIMIT_EXCEEDED","The limit for maximum number of aliases exceeded","The number of aliases configured has exceeded the maximum number of aliases allowed per vsan Due to this, distribution or merge operation may fail.","Make sure the number of aliases is less than the maximum allowed in a vsan."
"ZONE","2","ZS_ATTR_GROUP_LIMIT_EXCEEDED","The limit for maximum number of attribute groups exceeded","The number of attribute groups configured has exceeded the maximum number of attribute groups allowed in a vsan Due to this, distribution or merge operation may fail.","Make sure the number of attribute groups is less than the maximum allowed in a vsan."
"ZONE","2","ZS_BLOCKED_ATTR_PRESENT","Module [dec] failed to come online due to [chars]","Module [dec] failed to come up due to [chars].","Verify if RO/LUN/Broadcast attributes are configured, in any VSAN, disable if configured"
"ZONE","2","ZS_CHANGE_ACA_FAILED","ACA failed : [chars]","Zone Server cannot acquire change authorization : [chars].","Verify the interoperability mode on all the switches OR retry later."
"ZONE","2","ZS_CHANGE_ACQUIRE_AUTH_FAILED","Acquire authorization failed on VSAN [dec]","Zone Server cannot acquire authorization on VSAN [dec].","No action is required."
"ZONE","2","ZS_CHANGE_ACTIVATION_FAILED_RESN_DOM","Activation failed : reason [chars] domain [dec]","Zone Server cannot activate due to reason [chars] on domain [dec].","No action is required."
"ZONE","2","ZS_CHANGE_ACTIVATION_FAILED_RESN","Activation failed : reason [chars]","Zone Server cannot activate due to reason [chars].","No action is required."
"ZONE","2","ZS_CHANGE_ACTIVATION_FAILED","Activation failed","Zone Server cannot activate the zoneset.","No action is required."
"ZONE","2","ZS_CHANGE_APPLY_FAILED","Apply changed failed on VSAN [dec]","Zone Server cannot apply changes on VSAN [dec].","No action is required."
"ZONE","2","ZS_CHANGE_DEACTIVATION_FAILED_RESN_DOM","Deactivation failed : reason [chars] domain [dec]","Zone Server cannot deactivate due to reason [chars] on domain [dec].","No action is required."
"ZONE","2","ZS_CHANGE_DEACTIVATION_FAILED_RESN","Deactivation failed : reason [chars]","Zone Server cannot deactivate due to reason [chars].","No action is required."
"ZONE","2","ZS_CHANGE_DEACTIVATION_FAILED","Deactivation failed","Zone Server cannot deactivate the zoneset.","No action is required."
"ZONE","2","ZS_CHANGE_RELEASE_AUTH_FAILED","Release authorization failed on VSAN [dec]","Zone Server cannot release authorization on VSAN [dec].","No action is required."
"ZONE","2","ZS_CHANGE_RRCA_REJECTED","RRCA received from remote domain [dec] is rejected: [chars]","Received invalid RRCA from domain [dec]. : [chars]","Verify the interoperability mode on the switch."
"ZONE","2","ZS_CHANGE_RUFC_REJECTED","RUFC received from remote domain [dec] is rejected: [chars]","Received invalid RUFC from domain [dec]. : [chars]","Verify the interoperability mode on the switch."
"ZONE","2","ZS_CHANGE_SFC_FAILED","SFC failed : [chars]","Zone Server cannot stage zone configuration : [chars].","Verify the interoperability mode on all the switches."
"ZONE","2","ZS_CHANGE_SFC_REJECTED","SFC received from remote domain [dec] is rejected: [chars]","Received invalid SFC from domain [dec]. : [chars]","Verify the interoperability mode on the switch."
"ZONE","2","ZS_CHANGE_STAGE_ACTIVATE_ZSSET_BY_NAME_FAILED","Stage activate zoneset by name failed on VSAN [dec]","Zone Server cannot stage activate zoneset by name on VSAN [dec].","No action is required."
"ZONE","2","ZS_CHANGE_STAGE_ACTIVATE_ZSSET_ENH_FAILED","Stage activate zone set enhanced failed on VSAN [dec]","Zone Server cannot stage activate zone set enhanced on VSAN [dec].","No action is required."
"ZONE","2","ZS_CHANGE_STAGE_DEACTIVATE_ZSSET_ENH_FAILED","Stage deactivate zoneset enhanced failed on VSAN [dec]","Zone Server cannot stage deactivate zoneset enhanced on VSAN [dec].","No action is required."
"ZONE","2","ZS_CHANGE_STAGE_DISTRIBUTE_DFLT_ZONE_FAILED","Stage distribute default zone failed on VSAN [dec]","Zone Server cannot stage distribute default zone on VSAN [dec].","No action is required."
"ZONE","2","ZS_CHANGE_STAGE_DISTRIBUTE_ZS_DB_FAILED","Stage distribute zoneset database failed on VSAN [dec]","Zone Server cannot stage distribute zoneset database on VSAN [dec].","No action is required."
"ZONE","2","ZS_CHANGE_STAGE_SET_ZONING_MODE_FAILED","Stage set zoning mode failed on VSAN [dec]","Zone Server cannot stage set zoning mode on VSAN [dec].","No action is required."
"ZONE","2","ZS_CHANGE_STAGE_SET_ZONING_POLICIES_FAILED","Stage set zoning policies failed on VSAN [dec]","Zone Server cannot stage set zoning policies on VSAN [dec].","No action is required."
"ZONE","2","ZS_DB_OPERATION_FAILED","Database operation error: [chars]","Database operation is failed : [chars].","No action is required."
"ZONE","2","ZS_EXPORT_IMPORT_FAILED","[chars] operation failed","[chars] (Export/Import) operation failed.","No action is required."
"ZONE","2","ZS_FIPS_COMPLIANCE_FAILURE","FIPS compliance error: consecutively same random numbers","FIPS compliance error: consecutively same random numbers","No action is required."
"ZONE","2","ZS_INIT_FAILED","[chars]","Zone Server initialization failed : [chars].","No action is required."
"ZONE","2","ZS_LICENSE_UNAVAIL","License:[chars] unavailable, removing LUN members, read-only attribute and re-activating active zonesets on all affected VSANs","License:[char] unavailable, removing LUN members, read-only attribute and re-activating active zonesets on all affected VSANs.","No action is required."
"ZONE","2","ZS_LIC_FAILURE","License [chars] operation failed for license [chars]","License [char] operation failed for license [char].","No action is required."
"ZONE","2","ZS_LUN_DISABLING_FAILED","license expiry handling failed for VSAN [dec]","License expiry handling failed for VSAN [dec].","No action is required."
"ZONE","2","ZS_LUN_MEMBER_LIMIT_EXCEEDED","The limit for maximum number of lun members exceeded","The number of lun members configured has exceeded the maximum number of lun members allowed across all vsans Due to this, distribution or merge operation may fail.","Make sure the number of lun members is less than the maximum allowed across all vsans."
"ZONE","2","ZS_MALLOC_FAILURE","Memory allocation failed for size [dec]","Memory allocation is failed for size [dec] bytes.","Restart the process."
"ZONE","2","ZS_MEMBER_LIMIT_EXCEEDED","The limit for maximum number of members exceeded","The number of members configured has exceeded the maximum number of members allowed across all vsans Due to this, distribution or merge operation may fail.","Make sure the number of members is less than the maximum allowed across all vsans."
"ZONE","2","ZS_MERGE_ADJ_NO_RESPONSE","Adjacent switch not responding, isolating interface [chars]","Interface [chars] isolated due to adjacent switch not responding to Zone Server requests.","Flap the interface."
"ZONE","2","ZS_MERGE_FAILED","Zone merge failure, isolating interface [chars] [chars]","Interface [chars] isolated due to zone merge failure. error [chars]","Compare active zoneset with the adjacent switch OR use 'zone merge interface [interface] {import/export} VSAN [VSAN-num]' command."
"ZONE","2","ZS_MERGE_FULL_DATABASE_MISMATCH","Zone merge full database mismatch on interface [chars]","Full zoning databases are inconsistent between two switches connected by interface [chars]. Databases are not merged.","Compare full zoning database with the adjacent switch, correct the difference and flap the link."
"ZONE","2","ZS_MERGE_UNKNOWN_FORMAT","Unknown format, isolating interface [chars]","Interface [chars] isolated due to unknown format in merge request.","Set the interoperability mode to same value on both switches."
"ZONE","2","ZS_MTS_OPER_FAILED","MTS [chars] operation failed : [chars]","Zone Server MTS [chars] operation failed : [chars].","No action is required."
"ZONE","2","ZS_NO_RSCN_ON_SW_CARD","Devices on Module [dec] will not be receiving RSCN as [chars]","Devices on Module [dec] will not be receiving RSCN as [chars].","Enable Zone Based RSCN"
"ZONE","2","ZS_PORT_SWAP_FAILURE","Port swap operation failed","Port swap operation failed.","No action is required."
"ZONE","2","ZS_PSS_VER_MISMATCH","PSS version mismatch URL: [chars] (expected [chars], got [chars])","Configuration version mismatch. PSS URL [chars]. Expected version [chars], stored version [chars].","Upgrade/Downgrade to expected version."
"ZONE","2","ZS_TCAM_BROADCAST_ZONE_DISABLED","Broadcast zoning disabled : Reason: Hard zoning disabled","Broadcast zoning disabled : Reason: Hard zoning disabled due to TCAM programming failure.","No action is required."
"ZONE","2","ZS_TCAM_LUN_ZONING_DISABLED","LUN zoning disabled : Reason: Hard zoning disabled","LUN zoning disabled : Reason: Hard zoning disabled due to TCAM programming failure.","No action is required."
"ZONE","2","ZS_TCAM_PROGRAMMING_FAILED","TCAM operation failed : [chars], Reason: [chars]","TCAM Programming failure has occurred : [chars]. [chars] is the reason for failure.","No action is required."
"ZONE","2","ZS_TCAM_READ_ONLY_ZONE_DISABLED","Read-only zoning disabled : Reason: Hard zoning disabled","Read-only zoning disabled : Reason: Hard zoning disabled due to TCAM programming failure.","No action is required."
"ZONE","2","ZS_TCAM_SWITCHED_TO_SOFT_ZONING_MODE","Switched to soft zoning : Reason: Hard zoning disabled","Switched to soft zoning : Reason: Hard zoning disabled due to TCAM programming failure.","No action is required."
"ZONE","2","ZS_VIRTUAL_DOMAIN_INCONSISTENT","IVR reporting virtual domain different from rib and domain manager in vsan [dec]","IVR reporting virtual domain different from rib and domain manager in vsan [dec].","No action is required."
"ZONE","2","ZS_ZONE_BASED_RSCN_DISABLED","Zone based RSCN Generation has been Disabled. Devices on non ISOLA line cards will not be receiving RSCN","Devices on one or more line cards will not be receiving RSCN as RSCN generation by zone has been disabled on this switch","No action is required."
"ZONE","2","ZS_ZONE_LIMIT_EXCEEDED","The limit for maximum number of zones exceeded","The number of zones configured has exceeded the maximum number of zones allowed across all vsans Due to this, distribution or merge operation may fail.","Make sure the number of zones is less than the maximum allowed across all vsans."
"ZONE","2","ZS_ZONE_SET_LIMIT_EXCEEDED","The limit for maximum number of zonesets exceeded","The number of zonesets configured has exceeded the maximum number of zonesets allowed across all vsans Due to this, distribution or merge operation may fail.","Make sure the number of zonesets is less than the maximum allowed across all vsans."
"ZONE","3","LZ_UNKNOWN_MSG","Recvd. from Node=[dec] SAP=[dec]","The LUN/Read-only zoning process has received an unknown message from [dec]].[dec]. This information is for debugging only.","No action is required."
"ZONE","3","ZS_ACTIVATION_FAILED_DUE_TO_QOS_DISABLED","Activation failed due to qos not enabled","Activation of zoneset failed due to qos not enabled","Make sure qos is enabled and reactivate the zoneset in vsan."
"ZONE","4","LZ_OTHER_CMD_TO_ZONED_OUT_LUN","FCP command [hex] received from SID=[chars] to DID=[chars] for LUN=[chars]","The LUN/Read-only zoning process has received. FCP command [int] from SID [char] to DID [char] for a zoned out LUN [char].","No action is required."
"ZONE","4","ROZ_WRITE_ACCESS_TO_READ_ONLY_LUN","FCP command [hex] received from SID=[chars] to DID=[chars] for LUN=[chars]","The LUN/Read-only zoning process has received FCP command [int] from SID [char] to DID [char] for a read-only LUN [char].","No action is required."
"ZONE","4","ZS_BROADCAST_LUN_WARNING","LUN member(s) and Broadcast attribute are present in zone [chars] in vsan [dec]. Broadcast violations can occur for LUN members.","Broadcast violations can happen in zone [chars] in vsan [dec] since it has LUN zone members.","No action is required."
"ZONE","4","ZS_CHANGE_LC_UPGRADE_IN_PROGRESS","Change protocol request is received from domain [dec] when linecard upgrade is in progress","A change request has been received from domain [dec] when a linecard upgrade is in progress. The change request is rejected.","No action is required."
"ZONE","4","ZS_DB_WARNING","[chars]","Database operation warning: [chars].","No action is required."
"ZONE","4","ZS_DOMAIN_MGR_WARNING","Unable to retrieve domain info from domain mgr error: [chars] in vsan [dec]","Unable to retrieve info of domain from domain manager, error: [chars] in vsan [dec].","No action is required."
"ZONE","4","ZS_FC2_OPER_FAILED","FC2 [chars] operation failed : [chars]","Zone Server FC2 [chars] operation failed : [chars].","No action is required."
"ZONE","4","ZS_IF_PORT_MODE_CONFLICT","Port mode conflict for if [chars]","Port mode conflict for if [chars]","Shutdown/no shutdown the interface"
"ZONE","4","ZS_INVALID_FPORT_WWN_MEMBER","Virtual device fwwn: [chars] is not a valid zone/alias member virtual name: [chars] pwwn: [chars]","Virtual device fwwn: [chars] is not a valid zone/alias member, virtual name: [chars] pwwn: [chars].","No action is required."
"ZONE","4","ZS_LC_UPGRADE_CHANGE_IN_PROGRESS","Linecard upgrade request is received when change protocol is in progress","A request for linecard upgrade has been received when change protocol is in progress. The linecard upgrade will occur after the completion of the change protocol.","No action is required."
"ZONE","4","ZS_LICENSE_EXPIRY_WARNING","Feature [chars] evaluation license [chars] expiry in [dec] days","Feature [chars1] will exceed itsevaluationtimeperiodin[dec]daysandwillbeshutdownunlessapermanentlicense[chars2]isinstalled. '","Please install the license file to continue using the feature."
"ZONE","4","ZS_MEMBER_CONVERSION_FAILED","Zone Member conversion failed for [chars]. Error: [chars]","Zone Member conversion has failed in : [chars] due to error: [chars]","No action is required."
"ZONE","4","ZS_NON_INTEROPERABLE_ZONE_SET","Non interoperable active zoneset present on VSAN [dec] in interoperability mode","Active zoneset has non interoperable members (FCID, FWWN, ..) when interoperability mode is turned on the VSAN [dec].","Turn off interoperability mode OR make sure that active zoneset has only interoperable members (PWWN)."
"ZONE","4","ZS_QOS_LUN_WARNING","LUN member(s) and QoS attribute are present in zone [chars] in vsan [dec]. QoS will not be applicable for LUN members.","QoS will not be applicable to LUN zone members in zone [chars] in vsan [dec].","No action is required."
"ZONE","4","ZS_SDV_VIRT_REAL_CONFLICT_WARNING","Virtual and Real devices are zoned together or zoned with same device. virtual name: [chars] pwwn: [chars]","Virtual and Real devices are zoned together or zoned with same device, virtual name: [chars] pwwn: [chars].","No action is required."
"ZONE","4","ZS_TOO_MANY_ALIAS_IN_CURRENT_INTEROP_MODE","Too many aliases in current interoperability mode","Too many aliases configured in current interoperability mode on the VSAN. Due to this, the next zoneset activation, distribution or merge operation may fail.","Set the interoperability mode to appropriate value OR make sure the number of aliases is less than the maximum allowed in the current interoperability mode."
"ZONE","4","ZS_UNSUPPORTED_MEMBER_IN_CURRENT_INTEROP_MODE","Unsupported member present in active or full zoneset in current interoperability mode","Active or full zoneset has members that are not supported in the current interoperability mode set on the VSAN.","Set the interoperability mode to appropriate value OR make sure that active or full zoneset has only supported members in the current interoperability mode."
"ZONE","5","ZS_EXPORT_IMPORT_COMPLETE","[chars] operation completed","[chars] (Export/Import) operation completed.","No action is required."
"ZONE","5","ZS_POLICY_CHANGE","Default zoning policy changed to [chars]","Default zoning policy changed to (permit/deny).","No action is required."
"ZONE","5","ZS_ZONE_SET_ACTIVATED","Zoneset [chars] activated","Zoneset [chars] activated.","No action is required."
"ZONE","5","ZS_ZONE_SET_DEACTIVATED","Zoneset deactivated","Zoneset deactivated.","No action is required."
"ZONE","6","LZ_BECAME_ACTIVE","LUN/Read-only zoning process became ACTIVE from standby mode","The LUN/Read-only zoning process on the standby supervisor became active.","No action is required."
"ZONE","6","LZ_BECAME_STDBY","LUN/Read-only zoning process became STANDBY from active mode","The LUN/Read-only zoning process became standby from active mode.","No action is required."
"ZONE","6","LZ_FAILED_TO_SEND_HEARTBEAT","LUN/Read-only zoning process failed to send heartbeat to system manager: Reason=[chars]","The LUN/Read-only zoning process was unable to send heartbeat to the system manager.","No action is required."
"ZONE","6","LZ_GENERAL_EVENT","[chars]","The LUN/Read-only zoning process has generated an important event. The description of the event is [str].","No action is required."
"ZONE","6","LZ_INQUIRY_TO_ZONED_OUT_LUN","INQUIRY command received from SID=[chars] to DID=[chars] for LUN=[chars]","The LUN/Read-only zoning process has received INQUIRY FCP command from SID [char] to DID [char] for a zoned out LUN [char].","No action is required."
"ZONE","6","LZ_REPORT_LUNS_CMD_RCVD","REPORT LUNS command received from SID=[chars] to DID=[chars] for LUN=[chars]","The LUN/Read-only zoning process has received REPORT LUNS FCP command from SID [char] to DID [char] for LUN [char].","No action is required."
"ZONE","6","LZ_REQUEST_SENSE_TO_ZONED_OUT_LUN","REQUEST SENSE command received from SID=[chars] to DID=[chars] for LUN=[chars]","The LUN/Read-only zoning process has received. REQUEST SENSE FCP command from SID [char] to DID [char] for a zoned out LUN [char].","No action is required."
"ZONE","6","LZ_SERVICE_UP","LUN/Read-only zoning Process initialized [chars]","The LUN/Read-only zoning process is up. The process was initialized in [char] mode.","No action is required."
"ZONE","6","LZ_SWITCHOVER","LUN/Read-only zoning process switching over to other supervisor.","The LUN/Read-only zoning process has successfully switched over to the standby supervisor card.","No action is required."
"ZONE","6","ZS_CHANGE_ACA_REJECTED","ACA received from remote domain [dec] is rejected","Received invalid ACA from domain [dec]. Either the domain list do not match OR authorization has already been acquired by another switch.","Verify the interoperability mode on the switch."
"ZONE","6","ZS_FC2_OPER_INFO","FC2 [chars] operation failed : [chars]","Zone Server FC2 [chars] operation failed : [chars].","No action is required."
"ZONE","6","ZS_INIT_PROCESS","Zone Server process started [chars] at [chars]","Zone Server process started in [chars] (stateless/stateful) mode at time [chars].","No action is required."
"ZONE","6","ZS_INIT_WARNING","[chars]","Warning during Zone Server Initialization: [chars].","No action is required."
"ZONE","6","ZS_INVALID_MEMBER","Invalid member [dec] [chars]","Invalid member type [dec] [chars] recieved from the API call.",""
"ZONE","6","ZS_UNKNOWN_LIC_FEATURE","[chars]","",""
"ACLMGR","2","NOMAP","Cannot create ACL Manager data structures for VLAN Map [chars].","The ACL manager could not allocate the data structures needed to describe a VLAN map into a form that can be loaded into hardware. This error is most likely caused by lack of free memory. [chars] is the VLAN map name.","Reduce other system activity to ease memory demands."
"ACLMGR","2","NOVLB","Cannot create memory block for VLAN [dec].","The ACL manager could not save per-VLAN information needed for its correct operation. Some per-interface features, such as access groups or VLAN maps, will not be configured correctly. [dec] is the VLAN ID.","Use a less complicated configuration that requires less memory."
"ACLMGR","2","NOVMR","Cannot generate hardware representation of access list [chars]","Available resources are not sufficient to create a hardware representation of the ACL. A lack of available logical operation units or specialized hardware resources can cause this problem. Logical operation units are needed for a TCP flag match or a test other than eq (ne, gt, lt, or range) on TCP, UDP, or SCTP port numbers.","Modify the ACL configuration to use fewer resources, or rename the ACL with a name or number that alphanumerically precedes the other ACL names or numbers."
"ACLMGR","3","ACLTCAMFULL","Acl Tcam Full. Drop packets on Output Acl label [dec] on [chars] [chars].Note This message applies only to the Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The platform-specific ACL TCAM cannot support the number of configured ACLs. [dec] is the label number, and [chars] represents the layer. The first [chars] is for Layer 3, and the second for Layer 2. If only one layer of TCAM is full, only one string is displayed, and the other string is NULL.","Reduce the number of IP or MAC access lists to be applied to interfaces."
"ACLMGR","3","AUGMENTFAIL","Augmenting of access-map [chars] on [chars] label [dec] failed.","The system ran out of CPU DRAM when trying to merge internally required elements with the configured access maps. The first [chars] is the access-map name, the second [chars] is the direction in which the map was applied (input or output), and [dec] is the label number.","Reduce other system activity to ease memory demands."
"ACLMGR","3","IECPORTLABELERROR","ACL labels are out-of-sync on interface [chars], label [dec] is not available on asic [dec].","An internal software error has occurred. [chars] is the interface name. The first [dec] is the label associated with the ACL, and the second [dec] is the ASIC number.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"ACLMGR","3","INSERTFAIL","Insert of access-map [chars] #[dec] into [chars] label [dec] failed.","The system ran out of CPU memory when trying to merge sections of an access map. The first [chars] is the map name, and the second [chars] is the direction in which the map was applied. The first [dec] is the entry number, and the second [dec] is the label number.","Reduce other system activity to ease memory demands. For example, remove any ACLs that have been defined but not used. Use simpler ACLs with fewer access control entries (ACEs). Use fewer VLANs, and remove any unneeded VLANs from the VLAN database."
"ACLMGR","3","INTTABLE","Not in truth table: VLMAP [dec] RACL [dec] Mcb [dec] Feat [dec].","AnAn unrecoverable software error occurred while trying to merge the configured input features. [dec] are internal action codes.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"ACLMGR","3","INVALIDPARAM","Invalid [chars] [int] encountered","The access control list (ACL) manager has encountered an invalid parameter value. [chars] is the parameter name, and [int] is the parameter value.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"ACLMGR","3","MAXRECURSION","Too many ([dec]) levels of recursion while merging ACLs (code [dec]).","The configuration is too complicated for the platform-specific ACL merge code to support. The most likely cause is too many separate access lists in a single VLAN map or policy map. The first [dec] is the number of levels of recursion. The second [dec] is an internal code number of the merge stage that encountered the problem.","Reduce the number of IP or MAC access lists (considered separately) in any one VLAN or policy map to fewer than the number of levels reported by this log message."
"ACLMGR","3","MERGEFAIL","[chars] ACL merge error [dec] ([chars]) on [chars] label [dec].","The ACL manager could not complete the merge of the configured features into a form suitable for loading into the hardware. Packets potentially affected by this feature will be sent to the CPU for processing. The most likely cause is specifying an ACL that is too large or too complex for the system. The first [chars] is the ACL-type error (ip or mac), the first [dec] is the error code, the second [chars] is the message string for the preceding error code, the second [dec] is the label number, and the third [chars] is either input or output.","Specify a smaller and less complicated configuration."
"ACLMGR","3","NOLABEL","Cannot allocate [chars] label for interface [chars].","The ACL manager could not allocate a label for the features on this interface. This means that the hardware cannot be programmed to implement the features, and packets for this interface will be filtered in software. There is a limit of 256 labels per direction. The first [chars] is the direction (input or output), and the second [chars] is the interface name.","Use a simpler configuration. Use the same ACLs on multiple interfaces, if possible."
"ACLMGR","3","OUTTTABLE","Not in truth table: RACL [dec] VLMAP [dec].","An unrecoverable software error occurred while trying to merge the configured output features. [dec] are internal action codes.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"ACLMGR","3","PACLTTABLE","Not in truth table: IPSrcGrd [dec] PACL [dec].Note This message applies only to the Catalyst 3750 and 3560 switches.","An unrecoverable software error occurred while trying to merge the configured port ACL features. The first [dec] is the action specified by IP source guard, and the second [dec] is the action specified by the port ACL.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"ACLMGR","3","QOSTTABLE","Not in truth table: ACL [dec] in map, action [dec].","A software error occurred while trying to merge a quality of service (QoS) policy map. The first [dec] is the ACL number, and the second [dec] is the action corresponding to the specified ACL number.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"ACLMGR","3","RELOADED","Reloading [chars] label [dec] feature.","The ACL manager can now load more of the configured features on this label into the hardware. One or more features had previously been unloaded because of lack of space. [chars] is the direction (input or output), and [dec] is the label number.","No action is required."
"ACLMGR","3","UNKNOWNACTION","Unknown VMR access group action [hex].","An internal software error has occurred. [hex] is an internal action code.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"ACLMGR","3","UNLOADING","Unloading [chars] label [dec] feature.","The ACL manager could not load the complete configuration into the hardware, so some features will be applied in the software. Some or all of the packets in a VLAN are forwarded by the CPU. Multicast packets might be dropped entirely instead of being forwarded. [chars] is the direction (input or output), and [dec] is the label number.","Use a simpler configuration. Use the same ACLs on multiple interfaces, if possible."
"AUTHMGR","0","CONFIG_CORRUPT,MSGDEF_LIMIT_MEDIUM","Checksummed interface configuration corruption detected.","There was an unexpected modification in the interface configuration field.","No action is required."
"AUTHMGR","4","ILLEGAL_TRACE_REQ","Component ID [dec] not registered.","There was an attempt to log a message with an unregistered ID. [dec] is the component ID.","No action is required."
"AUTHMGR","5","MACMOVE","MAC address ([enet]) moved from Interface [chars] to Interface [chars]","The client moved to a new interface but did not log off from the first interface. [enet] is the MAC address of the client, the first [chars] is the earlier interface, and the second [chars] is the newer interface.","No action is required."
"AUTHMGR","5","MACREPLACE","MAC address ([enet]) on Interface [chars] is replaced by MAC ([enet]) AuditSessionID [chars]","A new client has triggered a violation that caused an existing client to be replaced. The first [enet] is the first client, the second [enet] is the new client, the first [chars] is the interface, the second [chars] is the audit session ID.","No action is required."
"AUTHMGR","5","SECURITY_VIOLATION","Security violation on the interface [chars], new MAC address ([enet) is seen. AuditSessionID [chars]","Interface host mode limits the number of hosts that can be attached to an interface. The limit was exceeded and caused a security violation. The interface is error disabled. The first [chars] is the interface, [enet] is the host MAC address, and the second [chars] is the session ID.","Reconfigure the interface to support the number of attached hosts. Enter the shutdown interface configuration command and then the no shutdown interface configuration command to re-enable the interface."
"AUTHMGR","5","VLANASSIGN","VLAN [dec] assigned to Interface [chars] AuditSessionID [chars]","A VLAN is assigned. [dec] is the VLAN ID, the first [chars] is the interface, and the second [chars] is the session ID.","No action is required."
"AUTHMGR","7","FAILOVER","Failing over from [chars] for client ([chars]) on Interface [chars] AuditSessionID [chars]","The authorization manager is failing over from the current authentication method to another method. The first [chars] is the current authentication method, the second [chars] is the client ID, the third [chars] is the interface, and the fourth [chars] is the session ID.","No action is required."
"AUTHMGR","7","STOPPING","Stopping '[chars]' for client [enet] on Interface [chars] AuditSessionID [chars]","The authentication process has been stopped. The first [chars] is the authentication method, [enet] is the Ethernet address of the host, the second [chars] is the interface for the host, and the third [chars] is the session ID.","No action is required."
"AUTHMGR","7","NOMOREMETHODS","Exhausted all authentication methods for client ([chars]) on Interface [chars] AuditSessionID [chars]","All available authentication methods have been tried. The first [chars] is the client identifier, the second [chars]s is the interface for the client, and the third [chars] is the session ID.","No action is required."
"AUTHMGR","7","RESULT","Authentication result [chars] from [chars] for client [chars] on Interface [chars] AuditSessionID [chars]","Authentication results: the first [chars] is the authentication status, the second [chars] is the authentication method, the third [chars] is the client ID, the fourth [chars] is the interface, and the fifth [chars] is the session ID.","No action is required."
"AUTOQOS","3","FEATURE_UNINITIALIZED","Feature not initialized in the platform, [chars].Note This message applies only to Catalyst 3550 switches.","The feature did not initialize and is not enabled on any interface. [chars] is the feature name, which is auto-QoS.","If this feature does not operate, reboot the system by using the reload privileged EXEC command. Verify that this feature is supported on your switch by checking the software configuration guide for this software release."
"BACKUP_INTERFACE","5","PREEMPT","Preempting interface [chars] in backup pair ([chars], [chars]), preemption mode is [chars]","The switch is pre-empting the current forwarding interface in the backup interface pair. The first [chars] is the number of the current forwarding interface. The second and third [chars] are the names of the interfaces in the backup pair, and the fourth [chars] is the pre-emption mode.","No action is required."
"BACKUP_INTERFACE","5","VLB_NON_TRUNK","Warning:  Flexlink VLB is not allowed on non-trunk ports.  Please configure [chars] to be a trunk port.","Flex Link VLAN load-balancing (VLB) detected a nontrunk port. [chars] is the interface name.","Change the interface to trunking mode."
"BSPATCH","1","RELOAD","System will reboot to activate newly patched Boot Loader. Note This message apply only to Catalyst 3750, 3560, and 2970 switches.","The switch automatically reboots after the boot loader is patched.","If this message recurs, copy it exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"BSPATCH","1","PATCHED","Boot Loader patch ([chars]) installed. Note This message apply only to Catalyst 3750, 3560, and 2970 switches.","A boot loader patch installed successfully. [chars] is the SDRAM refresh timer register setting.","If this message recurs, copy it exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"BSPATCH","3","FAILED","Failed to install Boot Loader patch ([chars]). Note This message apply only to Catalyst 3750, 3560, and 2970 switches.","The switch did not apply a boot loader patch. [chars] is the SDRAM refresh timer register setting.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"CFGMGR","1","UNABLE_TO_SEND_RUN_CFG","unable to send running-cfg, bits: [hex], retrying... Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","The system is unsuccessfully trying to distribute the running configuration to the stack member switches. [hex] is the bit representation of the switch number.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"CFGMGR","1","UNABLE_TO_SEND_STARTUP_CFG","unable to send startup-cfg, bits: [hex], retrying... Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","The system is unsuccessfully trying to distribute the startup configuration file to the stack member switches. [hex] is the bit representation of the switch number.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"CFGMGR","3","ERROR_APPLYING_STARTUP_CFG","Error Applying Startup Config to Running Config. Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","The system encountered an error when it was automatically applying the startup configuration to the running configuration.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"CFGMGR","4","MEMBER_WRITING_STARTUP_CFG","only master can do that. Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","A stack member switch attempted to write to the startup configuration file. Only the stack master can write to the startup configuration file.","No action is required."
"CFGMGR","5","UNABLE_TO_USE_PROVISIONED_CFG","Switch [dec] will receive the default configuration.Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","The switch type of the specified switch does not match the provisioned configuration for its switch number. The default configuration is applied to this switch. [dec] is the stack member number.","No action is required."
"CFGMGR","6","APPLYING_RUNNING_CFG","as new master. Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","A new stack master is applying the backed-up running configuration.","No action is required."
"CFGMGR","6","SPURIOUS_MEMBER_ADD","CFG MGR Recvd Spurious New Member Notification: [int].Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","The configuration manager received a notification about adding a stack member switch that already exists in the stack. [int] is the switch number.","If this message recurs, copy it exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"CFGMGR","6","UNABLE_TO_NVGEN_BUSY_RUNNING_CFG","config file busy, retrying... Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","The stack master is temporarily unable to generate the stack running configuration because another process is generating the configuration file.","No action is required. The action will be tried again."
"CFGMGR","6","UNABLE_TO_NVGEN_RUNNING_CFG","config file too large... Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","The stack master cannot generate the stack running configuration because the configuration file is too large.","Remove some configuration commands."
"CMP","4","MEM_CMPIP_ADDR_CONFLICT","Conflict with CMP IP address [IP_address], Reissuing a new CMP IP address to member [dec] Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The cluster commander found a conflict with the assigned CMP IP address of the member. A new unique CMP IP address is assigned to the member. [dec] is the member number.","This is only a warning message. The commander has already assigned the cluster member a new unique address. Clear any open TCP connections on the member by using clear tcp privileged EXEC command."
"CMP","5","ADD","The Device is added to the cluster (Cluster Name: [chars], CMDR IP Address [IP_address]).","The device is added to the cluster. [chars] is the cluster name, and [IP_address] is the Internet address of the command switch.","No action is required."
"CMP","5","MEMBER_CONFIG_UPDATE","Received member configuration from member [dec].","The active or standby command switch received a member configuration. [dec] is the member number of the sender.","No action is required."
"CMP","5","MGMT_VLAN_CHNG","The management vlan has been changed to [dec]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The management VLAN has changed. [dec] is the new management VLAN ID.","No action is required."
"CMP","5","NBR_UPD_SIZE_TOO_BIG","Number of neighbors in neighbor update is [int], maximum number of neighbors allowed in neighbor update is [int].","The number of cluster neighbors in the clustering neighbor update packet exceeds the number of neighbors supported by the clustering module. The first [int] is the new number of neighbors, and the second [int] the maximum number of neighbors.","No action is required."
"CMP","5","REMOVE","The Device is removed from the cluster (Cluster Name: [chars]).","The device was removed from the cluster. [chars] is the cluster name.","No action is required."
"DHCP_SNOOPING","3","DHCP_SNOOPING_INTERNAL_ERROR","DHCP Snooping internal error, [chars].","A software sanity check failed in the DHCP snooping process. [chars] is the error.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"DHCP_SNOOPING","4","AGENT_OPERATION_FAILED","DHCP snooping binding transfer failed. [chars].","The DHCP snooping binding transfer process failed. [chars] is the reason the process failed.","No action is required."
"DHCP_SNOOPING","4","AGENT_OPERATION_FAILED_N","DHCP snooping binding transfer failed ([dec]). [chars].","The DHCP snooping binding transfer process failed. [dec] is the number of times the process failed, and [chars] is the reason the process failed. This message is rate-limited.","No action is required."
"DHCP_SNOOPING","4","DHCP_SNOOPING_ERRDISABLE_WARNING","DHCP Snooping received [dec] DHCP packets on interface [chars].","The switch detected a DHCP packet rate-limit violation on the specified interface and put the interface in the error-disabled state. [dec] is the number of DCHP packets, and [chars] is the interface.","No action is required."
"DHCP_SNOOPING","4","DHCP_SNOOPING_PVLAN_WARNING","DHCP Snooping configuration may not take effect on secondary vlan [dec]. [chars]","If the private VLAN feature is configured, the DHCP snooping configuration on the primary VLAN automatically propagates to all the secondary VLANs. [dec] is the VLAN ID of the secondary VLAN, and [chars] is the warning.","No action is required."
"DHCP_SNOOPING","4","IP_SOURCE_BINDING_NON_EXISTING_VLAN_WARNING","IP source binding is configured on non existing vlan [dec].","An IP source binding was configured on a VLAN that has not been configured yet. [dec] is the VLAN.","No action is required."
"DHCP_SNOOPING","4","IP_SOURCE_BINDING_PVLAN_WARNING","IP source filter may not take effect on secondary vlan [dec] where IP source binding is configured. [chars].","If private VLANs are configured, the IP-source-guard filter on the primary VLAN automatically propagates to all secondary VLANs. [dec] is the secondary VLAN, and [chars] is the warning.","No action is required."
"DHCP_SNOOPING","4","NTP_NOT_RUNNING","NTP is not running; reloaded binding lease expiration times are incorrect.","If the DHCP snooping database agent loads the DHCP snooping bindings and Network Time Protocol (NTP) is not running, the calculated lease duration for the bindings is incorrect.","Configure NTP on the switch to provide an accurate time and date for the system clock. Then disable and re-enable DHCP snooping to clear the DHCP snooping binding database."
"DHCP_SNOOPING","4","QUEUE_FULL","Fail to enqueue DHCP packet into processing queue: [chars], the queue is most likely full and the packet will be dropped.","The CPU is receiving DHCP at a higher rate than the DHCP snooping can process. These DHCP packets are dropped to prevent a denial of service attack. [chars] is the warning.","No action is required."
"DHCP_SNOOPING","4","STANDBY_AGENT_OPERATION_FAILED","DHCP snooping binding transfer failed on the Standby Supervisor. [chars].","The DHCP snooping binding transfer process failed on a standby supervisor engine. [chars] is the standby supervisor engine.","No action is required."
"DHCP_SNOOPING","5","DHCP_SNOOPING_UNTRUSTED_PORT","DHCP_SNOOPING drop message on untrusted port, message type: [chars], MAC sa: [enet]","An untrusted port dropped a DHCP message. A host might be acting as a DHCP server. [chars] is the message type (DHCPOFFER, DHCPACK, DHCPNAK, or DHCPLEASEQUERY), and [enet] is the MAC address of the sending host.","No action is required."
"DHCP_SNOOPING","6","AGENT_OPERATION_SUCCEEDED","DHCP snooping database [chars] succeeded.","The DHCP binding transfer process succeeded. [chars] is the DCHP snooping database.","No action is required."
"DHCP_SNOOPING","6","BINDING_COLLISION","Binding collision. [dec] bindings ignored.","The specified number of bindings were ignored when the switch read the database file. The bindings from the database file have MAC address and VLAN information that a configured DHCP snooping binding already uses.","No action is required."
"DHCP_SNOOPING","6","INTERFACE_NOT_VALID","Interface not valid. [dec] bindings ignored.","The specified number of bindings were ignored when the switch read the database file because the interface in binding database is not available, the interface is a routed port, or the interface is a DHCP snooping-trusted Layer 2 interface. [dec] is the number of bindings that the switch ignores.","No action is required."
"DHCP_SNOOPING","6","LEASE_EXPIRED","Lease Expired. [dec] bindings ignored.","The specified number of bindings were ignored when the switch read the database file because the DHCP lease expired. [dec] is the number of bindings.","No action is required."
"DHCP_SNOOPING","6","PARSE_FAILURE","Parsing failed for [dec] bindings.","The specified number of bindings were ignored when the switch read the database file because the database read operation failed. [dec] is the number of bindings.","No action is required."
"DHCP_SNOOPING","6","VLAN_NOT_SUPPORTED","Vlan not supported. [dec] bindings ignored.","The specified number of bindings were ignored when the switch read the database file because the VLAN is no longer configured on the switch. [dec] is the number of bindings that the switch ignores.","No action required."
"DHCP_SNOOPING_CAT3550","3","MVR_INSTALL","Cannot install [chars] ACLs for DHCP Snooping, probably no TCAM space.Note This message applies only to Catalyst 3550 switches.","When DHCP snooping is enabled, access control lists (ACLs) need to be installed in the TCAM. DHCP snooping fails if there is insufficient space in the TCAM.","Reduce the number of input or output port ACLs (PACLs) and VLAN maps to make space in the TCAM."
"DHCP_SNOOPING_CAT3550","3","UNEXPECTED_EVENT","Process received unknown event (major [hex], minor [hex]).Note This message applies only to Catalyst 3550 switches.","A process received an event it could not handle.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section for more information."
"DOT1Q_TUNNELLING","4","MTU_WARNING","System MTU of [dec] might be insufficient for 802.1Q tunnelling. 802.1Q tunnelling requires system MTU size of [dec] to handle maximum size ethernet frames.Note This message applies only to Catalyst 3550 switches.","The switch MTU setting might not be sufficient for 802.1Q tunneling. The MTU needs to include the 4-byte overhead associated with the additional 802.1Q tag. The first [dec] is the current system MTU setting in bytes, and the second [dec] is the required MTU size in bytes.","Adjust the system MTU for the additional 802.1Q tag by using the system mtu global configuration command, and reload the switch by using the reload privileged EXEC command."
"DOT1X","4","MEM_UNAVAIL","Memory was not available to perform the 802.1X action. AuditSessionID [chars]","The switch does not have enough memory to perform 802.1x authentication. [chars] is the session ID.","Reconfigure the switch to reduce memory usage."
"DOT1X","4","PROC_START_ERR","Dot1x unable to start.","The system did not start the 802.1x process.","Enter the global configuration command dot1x system-auth-control to restart the 802.1x process. If this message recurs, reload the device."
"DOT1X","4","UNKN_ERR","An unknown operational error occurred.","The 802.1x process cannot operate because of an internal system error.","Reload the device."
"DOT1X","5","RESULT_OVERRIDE","Authentication result overridden for client ([chars]) on Interface [chars] AuditSessionID [chars]","The authentication result is overridden. The first [chars] is the client ID, the second [chars] is the interface, and the third [chars] is the session ID.","No action is required."
"DOT1X","5","FAIL","Authentication failed for client ([chars]) on Interface [chars] AuditSessionID [chars]","The authentication was unsuccessful. The first [chars] is the client ID, the second [chars] is the interface, and the third [chars] is the session ID.","No action is required."
"DOT1X","5","INVALID_INPUT","Dot1x Interface parameter is Invalid on interface [chars].","The 802.1x interface parameter is out of the specified range or is invalid. [chars] is the interface.","Refer to the CLI help documentation to determine the valid 802.1x parameters."
"DOT1X","5","SECURITY_VIOLATION","Security violation on interface [chars], New MAC address [enet] is seen.","A host on the specified interface is trying to access the network or to authenticate in a host mode that does not support the number of hosts attached to the interface. This is a security violation, and the port is error disabled.","Ensure that the interface is configured to support the number of attached hosts. Enter the shutdown interface configuration command and then the no shutdown interface configuration command to restart the port."
"DOT1X","5","SUCCESS","Authentication successful for client ([chars]) on Interface [chars] AuditSessionID [chars]","Authentication was successful. The first [chars] is the client ID, the second [chars] is the interface, and the third [chars] is the session ID.","No action is required."
"DOT1X_SWITCH","5","ERR_ADDING_ADDRESS","Unable to add address [enet] on [chars] AuditSessionID [chars]","The client MAC address could not be added to the MAC address table because the hardware memory is full or the address is a secure address on another port. This message might appear if 802.1x is enabled. [enet] is the client MAC address, the first [chars] is the interface, and the second [chars] is the session ID.","If hardware memory is full, remove some of the dynamic MAC addresses. If the client address is on another port, remove it from that port."
"DOT1X_SWITCH","5","ERR_INVALID_PRIMARY_VLAN","Attempt to assign primary VLAN [dec] to 802.1x port [chars] AuditSessionID [chars]Note This message applies to switches running the IP base image.","An attempt was made to assign a primary VLAN to an 802.1x port. This is not allowed. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.","Assign a different VLAN."
"DOT1X_SWITCH","5","ERR_INVALID_SEC_VLAN","Attempt to assign invalid secondary VLAN [dec] to PVLAN host 802.1x port [chars] AuditSessionID [chars] Note This message applies to switches running the IP base image.","An attempt was made to assign a nonsecondary VLAN to a private VLAN host 802.1x port. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.","Change the port mode so that it is no longer a private VLAN host port, or use a valid secondary VLAN."
"DOT1X_SWITCH","5","ERR_PRIMARY_VLAN_NOT_FOUND","Attempt to assign VLAN [dec], whose primary VLAN does not exist or is shutdown, to 802.1x port [chars] AuditSessionID [chars] Note This message applies to switches running the IP base image.","An attempt was made to assign a private VLAN whose primary VLAN does not exist or is shut down. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.","Check that the primary VLAN exists and is not shut down. Check that the private VLAN is associated with a primary VLAN."
"DOT1X_SWITCH","5","ERR_RADIUS_VLAN_NOT_FOUND","Attempt to assign non-existent VLAN [chars] to dot1x port [chars]","RADIUS attempted to assign a VLAN with a particular name or ID to a supplicant on a port, but the name or ID could not be found on the switch. [dec] is the VLAN, and [chars] is the port.","Make sure a VLAN with the specified name or ID exists on the switch."
"DOT1X_SWITCH","5","ERR_SEC_VLAN_INVALID","Attempt to assign secondary VLAN [dec] to non-PVLAN host 802.1x port [chars] AuditSessionID [chars] Note This message applies to switches running the IP base image.","An attempt was made to assign a secondary VLAN to a port that is not a private VLAN host port. This is not allowed. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.","Change the port mode so that it is configured as a private VLAN host port or use a different VLAN that is not configured as a secondary VLAN."
"DOT1X_SWITCH","5","ERR_SPAN_DST_PORT","Attempt to assign VLAN [dec] to 802.1x port [chars], which is configured as a SPAN destination AuditSessionID [chars]","An attempt was made to assign a VLAN to an 802.1x port that is configured as a Switched Port Analyzer (SPAN) destination port. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.","Change the SPAN configuration so that the port is no longer a SPAN destination port, or change the configuration so that no VLAN is assigned."
"DOT1X_SWITCH","5","ERR_VLAN_EQ_MDA_INACTIVE","Multi-Domain Authentication cannot activate because Data and Voice VLANs are the same on port AuditSessionID [chars]","Multi-Domain Authentication (MDA) host mode cannot start when the configured data VLAN on a port is the same as the voice VLAN. [chars] is the port session ID.","Change either the voice VLAN or the access VLAN on the interface so that they are not the same. MDA then starts."
"DOT1X_SWITCH","5","ERR_VLAN_EQ_VVLAN","Data VLAN [dec] on port [chars] cannot be equivalent to the Voice VLAN AuditSessionID [chars]","An attempt was made to assign a data VLAN to an 802.1x port that is the same as the voice VLAN. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.","Change either the voice VLAN or the 802.1x-assigned VLAN on the interface so that they are not the same."
"DOT1X_SWITCH","5","ERR_VLAN_INTERNAL","Attempt to assign internal VLAN [dec] to 802.1x port [chars] AuditSessionID [chars]","An attempt was made to assign an invalid VLAN to an 802.1x port. The VLAN specified is used internally and cannot be assigned to this port. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.Explanation    Assign a different VLAN.Error Message    DOT1X_SWITCH-5-ERR_VLAN_INVALID: Attempt to assign invalid VLAN [dec] to 802.1x port [chars] AuditSessionID [chars] Explanation    An attempt was made to assign an invalid VLAN to an 802.1x port. The VLAN specified is out of range. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.","Change the configuration to use a valid VLAN."
"DOT1X_SWITCH","5","ERR_VLAN_NOT_FOUND","Attempt to assign non-existent or shutdown VLAN [chars] to 802.1x port [chars] AuditSessionID [chars]","An attempt was made to assign a VLAN to an 802.1x port, but the VLAN was not found in the VLAN Trunking Protocol (VTP) database. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.","Make sure the VLAN exists and is not shut down, or use another VLAN."
"DOT1X_SWITCH","5","ERR_VLAN_ON_ROUTED_PORT","Attempt to assign VLAN [dec] to routed 802.1x port [chars] AuditSessionID [chars]","An attempt was made to assign a VLAN to a supplicant on a routed port, which is not allowed. [dec] is the VLAN ID, the first [chars] is the port, and the second [chars] is the session ID.","Either disable the VLAN assignment, or change the port type to a nonrouted port."
"DOT1X_SWITCH","5","ERR_VLAN_PROMISC_PORT","Attempt to assign VLAN [dec] to promiscuous 802.1x port [chars] AuditSessionID [chars]","An attempt was made to assign a VLAN to a promiscuous 802.1x port, which is not allowed. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.","Change the port mode so that it is no longer a promiscuous port, or change the configuration so that no VLAN is assigned."
"DOT1X_SWITCH","5","ERR_VLAN_RESERVED","Attempt to assign reserved VLAN [dec] to 802.1x port [chars] AuditSessionID [chars]","An attempt was made to assign an invalid VLAN to an 802.1x port. The VLAN specified is a reserved VLAN and cannot be assigned to this port. [dec] is the VLAN, the first [chars] is the port, and the seconds [chars] is the session ID.","Assign a different VLAN."
"DOT1X_SWITCH","5","ERR_VLAN_RSPAN","Attempt to assign RSPAN VLAN [dec] to 802.1x port [chars]. 802.1x is incompatible with RSPAN AuditSessionID [chars]","Remote SPAN should not be enabled on a VLAN with 802.1x-enabled. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.","Either disable remote SPAN configuration on the VLAN, or disable 802.1x on all the ports in this VLAN."
"DTP","4","MEM_UNAVAIL","Memory was not available to perform the trunk negotiation action.","The system cannot negotiate trunks because of a lack of memory.","Reduce other system activity to ease memory demands."
"DTP","4","TMRERR","An internal timer error occurred when trunking on interface [chars].","A timer used by the trunking protocol unexpectedly expired. [chars] is the trunked interface.","This problem is corrected internally and has no long-term ramifications. However, if more problems with trunking occur, reload the switch by using the reload privileged EXEC command."
"DTP","4","UNKN_ERR","An unknown operational error occurred.","The system cannot negotiate trunks because an internal operation generated an unexpected error.","Reload the switch by using the reload privileged EXEC command."
"DTP","5","DOMAINMISMATCH","Unable to perform trunk negotiation on port [chars] because of VTP domain mismatch.","The two ports in the trunk negotiation belong to different VTP domains. Trunking can be configured only when the ports belong to the same VTP domain. [chars] is the port number.","Ensure that the ports in the trunk negotiation belong to the same VTP domain."
"DTP","5","ILGLCFG","Illegal config (on, isl--on,dot1q) on [chars].","One end of the trunk link is configured as on with ISL encapsulation and the other end is configured as on with 802.1Q encapsulation. [chars] is the interface.","This configuration is illegal and will not establish a trunk between two switches. You must change the encapsulation type so that both ends of the trunk match."
"DTP","5","NONTRUNKPORTON","Port [chars] has become non-trunk.","The interface changed from a trunk port to an access port. [chars] is the interface that changed.","This message is provided only for information."
"DTP","5","TRUNKPORTCHG","Port [chars] has changed from [chars] trunk to [chars] trunk.","The encapsulation type of the trunk port has changed. The first [chars] is the interface, the second is the original encapsulation type, and the third [chars] is the new encapsulation type.","This message is provided only for information."
"DTP","5","TRUNKPORTON","Port [chars] has become [chars] trunk.","The interface has changed from an access port to a trunk port. The first [chars] is the interface, and the second [chars] is the encapsulation type.","This message is provided only for information."
"DWL","3","LOOP_BACK_DETECTED","Loop-back detected on [chars].","The specified port has a loopback. The cause might be a Token-Ring Type-1 cable connected to the port or a misconfiguration in the network. [chars] is the port.","Correct the problem that is causing the loopback condition. Then enter the shutdown and the no shutdown interface configuration commands."
"EC","4","NOMEM","Not enough memory available for [chars].","Either the LACP or the PAgP EtherChannel could not obtain the memory it needed to initialize the required data structures. [chars] is the data structure name.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"EC","5","BUNDLE","Interface [chars] joined port-channel [chars].","The listed interface joined the specified EtherChannel. The first [chars] is the physical interface, and the second [chars] is the EtherChannel interface.","No action is required."
"EC","5","CANNOT_ALLOCATE_AGGREGATOR","Aggregator limit reached, cannot allocate aggregator for group [dec].Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","A new aggregator cannot be allocated in the group. [dec] is the affected group.","Change the port attributes of the ports in the group so that they match and join the same aggregator."
"EC","5","CANNOT_BUNDLE1","Port-channel [chars] is down, port [chars] will remain stand-alone.","The aggregation port is down. The port remains standalone until the aggregation port is up. The first [chars] is the EtherChannel, and the second [chars] is the port number.","Ensure that the other ports in the bundle have the same configuration."
"EC","5","CANNOT_BUNDLE2","[chars] is not compatible with [chars] and will be suspended ([chars]).","The interface has different interface attributes than the other ports in the EtherChannel. For the interface to join the bundle (EtherChannel), change the interface attributes to match the EtherChannel attributes. The first [chars] is the interface to be bundled, the second [chars] is the physical interface (a switch port or a routed port) that is already in the bundle, and the third [chars] is the reason for the incompatibility.","Change the interface attributes to match the EtherChannel attributes."
"EC","5","CANNOT_BUNDLE_LACP","[chars] is not compatible with aggregators in channel [dec] and cannot attach to them ([chars]).","The port has different port attributes than the port channel or ports within the port channel. [chars] is the incompatible port, [dec] is the channel group number, and the last [chars] is the reason.","For the port to join the bundle, change the port attributes so that they match the port."
"EC","5","COMPATIBLE","[chars] is compatible with port-channel members.","A port was not operational because its attributes were different from those of the port channel or ports within the port channel. The system has detected that the attributes of the port now match the port-channel attributes. [chars] is the affected port.","No action is required."
"EC","5","DONTBNDL","[chars] suspended: incompatible remote port with [chars]","The configuration of the remote port is different from the configuration of other remote ports in the bundle. A port can only join the bundle when the configuration of the local port and the configuration of the remote port are the same as other ports already in the bundle. The first [chars] is the name of the local interface that is being suspended, and the second [chars] is the name of the local interface that is already bundled.","Make sure that the configuration of the remote ports is the same for all ports in the bundle."
"EC","5","ERRPROT","Channel protocol mismatch for interface [chars] in group [dec]: the interface can not be added to the channel group.","The interface cannot be added to the channel group with the specified mode. [chars] is the interface, and [dec] is the channel group.","Change the channel group or the mode for the interface."
"EC","5","ERRPROT2","Command rejected: the interface [chars] is already part of a channel with a different type of protocol enabled.","The interface cannot be selected for the specified protocol because it is already part of a channel with a different protocol. [chars] is the interface.","Remove the interface from the channel group."
"EC","5","ERRPROT3","Command rejected: the interface [chars] is already part of a channel.","The interface cannot be unselected for the specified protocol because it is already part of a channel group. [chars] is the interface.","Remove the interface from the channel group."
"EC","5","L3DONTBNDL1","[chars] suspended: PAgP not enabled on the remote port. Note This message applies only to Catalyst 3750, 3560, and 3550 switches.","PAgP is enabled on the Layer 3 interface but the partner port is not enabled for PAgP. In this mode, the port is placed in a suspended state. [chars] is the Layer 3 interface.","Enable PAgP on the remote side by using the channel-group interface configuration command."
"EC","5","L3DONTBNDL2","[chars] suspended: LACP currently not enabled on the remote port. Note This message applies only to Catalyst 3750, 3560, and 3550 switches.","LACP is enabled on a Layer 3 interface but is not enabled on the partner port. In this mode, the port is put in a suspended state. [chars] is the interface name.","Enable LACP on the remote side."
"EC","5","L3DONTBNDL3","[chars] suspended: LACP not enabled on the remote port. Note This message applies only to Catalyst 3550 switches.","LACP is enabled on a Layer 3 interface but the remote port does not have LACP enabled. In this mode, the local port is put in a suspended state. [chars] is the interface name.","Enable LACP on the remote port."
"EC","5","L3STAYDOWN","[chars] will remain down as its port-channel [chars] is admin-down.Note This message applies only to Catalyst 3550 switches.","On Layer 3 interfaces and aggregation interfaces, the administrative state of the aggregation interface overrides the administrative status of the Layer 3 interface. If the aggregation interface is administratively down, all interfaces in the aggregation interface are forced to be down. [chars] is the Layer 3 interface.","Enter the no shutdown interface configuration command on the aggregation interface."
"EC","5","NOLACP","Invalid EC mode, LACP not enabled.","The EtherChannel mode cannot be set because LACP is not included in the software image.","Install a software image that includes LACP, and set the EC mode to on."
"EC","5","NOPAGP","Invalid EC mode, PAgP not enabled.","PAgP is not included in the Cisco IOS image and the EtherChannel mode cannot be set to desirable or auto.","Obtain an image with PAgP included, or set the mode to on by using the channel-group channel-group-number mode on interface configuration command."
"EC","5","PORTDOWN","Shutting down [chars] as its port-channel is admin-down.","The administrative state of the port is controlled by the administrative state of its aggregate port. If the administrative state of the aggregate port is down, the administrative state of the port is also forced to be down. [chars] is the physical interface.","Enter the no shutdown interface configuration command on the aggregate port to activate the aggregation port."
"EC","5","STAYDOWN","[chars] will remain down as its port-channel [chars] is admin-down.","The administrative state of the aggregation port overrides that of the affected port. If the aggregation port is administratively down, all ports in the aggregation port are forced to be administratively down. The first [chars] is the physical interface, and the second [chars] is the EtherChannel.","Enter the no shutdown interface configuration command on the aggregation port to activate (unshut) the aggregation port."
"EC","5","STAYDOWN","no-shut not allowed on [chars]. Module [dec] not online.","An interface with an EtherChannel configuration cannot be enabled by using the no shutdown interface configuration command because it is a member of an EtherChannel group and that EtherChannel group has been administratively shut down. The interface has an EtherChannel configuration, but no information is available yet about its port channel. [chars] is the interface, and [dec] is the module.","No action is required. Wait until the module is online to find out the port-channel setting of the EtherChannel."
"EC","5","UNBUNDLE","Interface [chars] left the port-channel [chars].","The listed interface left the specified EtherChannel. The first [chars] is the physical interface, which can be a switch port or a routed port, and the second [chars] is the EtherChannel.","No action is required."
"EC","5","UNSUITABLE","[chars] will not join any port-channel, [chars].","One of the interfaces cannot join the EtherChannel because it is configured for PortFast, as a VLAN Membership Policy Server (VMPS), for 802.1x, as a voice VLAN, or as a SPAN destination port. All of these are illegal configurations for EtherChannels. The first [chars] is the interface name, and the second [chars] describes the details of the illegal configuration.","Reconfigure the port, removing the illegal configuration."
"ENVIRONMENT","2","PS_A_HIGHVOLTAGE","[chars] [chars] [chars] [chars] [chars]","The power supply input voltage has exceeded the maximum threshold. This could be caused by the operational environment or faulty components. The first [chars] is the mode, the second [chars] is the severity, the third [chars] is the description, the fourth [chars] is the alarm string, and the fifth [chars] is the error message.","Save the system configuration and power down the system to prevent damage caused by high voltage. If the message recurs, hardware replacement maybe necessary."
"ENVIRONMENT","2","PS_A_LOWVOLTAGE","[chars] [chars] [chars] [chars] [chars]","The power supply input voltage is below the minimum threshold. This could be caused by the operational environment or faulty components. The first [chars] is the mode, the second [chars] is the severity, the third [chars] is the description, the fourth [chars] is the alarm string, and the fifth [chars] is the error message.","Save the system configuration and power down the system to prevent damage caused by low voltage. If the message recurs, hardware replacement maybe necessary."
"ENVIRONMENT","2","PS_B_LOWVOLTAGE","[chars] [chars] [chars] [chars] [chars]","The power supply input voltage is below minimum threshold. This could be caused by the operational environment or faulty components. The first [chars] is the mode, the second [chars] is the severity, the third [chars] is the description, the fourth [chars] is the alarm string, and the fifth [chars] is the error message.","Save the system configuration and power down the system to prevent damage caused by low voltage. If the message recurs, hardware replacement maybe necessary."
"ENVIRONMENT","2","FAN_FAULT","System Fault:FAN FAULT is detected. Note This message applies only to Catalyst 3550 switches.","An internal fan fault was detected.","Check if the fan on the switch failed, or use the show env privileged EXEC command to check if one or more fans on the switch have failed. Replace the switch at your convenience."
"ENVIRONMENT","2","OVER_TEMP","System Fault:OVER TEMPERATURE condition is detected. Note This message applies only to Catalyst 3550 switches.","An overtemperature condition was detected.","Use the show env privileged EXEC command to check if an overtemperature condition exists. If an overtemperature condition does exist, place the switch in an environment that is within 32 to 113? (0 to 45?), and make sure that the fan intake and exhaust areas are clear."
"ENVIRONMENT","3","POWER_ERROR","PSU [chars] model is not supported - Voltage threshold monitor is skipped","There is a power supply problem. [chars] is either A or B.","Check the connected power supply. If the message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section for more information."
"EPM","6","AUTH_ACL","POLICY [chars]| EVENT [chars]","The switch has sent or received a download request for a downloadable ACL (dACL). The first [chars] is the dACL policy. The second [chars] is the event.","No action is required."
"ETHCNTR","2","MOLSENDTIMEOUT","Molecule send timeout, queue [dec], molecule [hex] [hex].Note This message applies only to Catalyst 3550 switches.","An attempt to read or write one or more of the hardware settings failed.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section for more information."
"ETHCNTR","3","FLOWCONTROL_DUPLEX_ERROR","Flowcontrol will not take effect until duplex is set to auto. Note This message applies only to Catalyst 3550 switches.","Flow control cannot be set on the switch in this configuration.","Configure the duplex mode to auto."
"ETHCNTR","3","HALF_DUX_COLLISION_EXCEED_THRESHOLD","Collision at [chars] exceed threshold. Consider as loop-back.","The collisions at a half-duplex port exceeded the threshold, and the port is treated as a loopback. On switches that support Power over Ethernet (PoE), this message might be displayed when a device that can be powered by either a PoE switch port or by AC power is not being powered by an external AC power source and is connected to a port that has been configured with the power inline never interface configuration command. [chars] is the port where the threshold was exceeded.","On switches that support PoE, remove the device or configure the port by entering the power inline auto, shutdown, and no shutdown interface configuration commands. No action is required on non-PoE switches. The port goes into error-disabled mode until the problem is resolved."
"ETHCNTR","3","INTERNAL_ERROR","Internal Error [chars].Note This message applies only to Catalyst 3550 switches.","An internal error occurred when the software was trying to program the hardware. As a result, the switch is in an inconsistent state and might not provide the expected functions. [chars] describes the internal operation that failed.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section for more information."
"ETHCNTR","3","INVALIDMAP","Invalid map [dec] for address [enet].Note This message applies only to Catalyst 3550 switches.","An attempt to bridge a packet in software obtained an invalid result. [dec] is the map number, and [enet] is the Ethernet address.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section for more information."
"ETHCNTR","3","LOOP_BACK_DETECTED",", Loop-back detected on [chars]. The port is forced to linkdown.","A keepalive packet is looped back to the port that sent the keepalive. The loopback condition might be caused by a balun cable being accidentally connected to the port, or there might be a loop in the network. [chars] is the port.","Examine the cables. If a balun cable is connected, and the loopback condition is desired, no action is required. Otherwise, connect the correct cable, and restart the port by entering the no shutdown interface configuration command. We do not recommend using the no keepalive interface command to disable keepalives. The cause of this network loop must be found and corrected. Although disabling keepalives prevents the port from being error-disabled, it does not resolve the cause of the problem and can affect network stability. See CSCea46385 for more information."
"ETHCNTR","3","MOLSENDINT","Molecule send from interrupt handler Note This message applies only to Catalyst 3550 switches.","An interrupt handler is accessing the hardware in an impermissible manner.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section for more information."
"ETHCNTR","3","NETWORK_ERROR","Frame received on queue [dec] contained network error.  Source thread [dec], source interface [chars].Note This message applies only to Catalyst 3550 switches.","The frame that is stored on the switch has an error. The first [dec] is the ingress queue, the second [dec] is the source thread, and [chars] is the ingress interface.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"ETHCNTR","3","NO_HARDWARE_RESOURCES","Not enough hardware resources. Shutting down [chars].Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","There are too many VLANs and routed ports (if the switch supports routed ports) configured. [chars] is the short interface name, such as Gi1/0/1 on a Catalyst 3750 switch, or the VLAN name, such as VLAN0002.","Reduce the total number of VLANs and routed ports to less than 1023. To preserve configuration and connections across reboots, save the configuration."
"ETHCNTR","3","RA_ALLOC_ERROR","RAM Access [chars] [chars] memory allocation failure.Note This message applies only to Catalyst 3550 switches.","A request to read from or write to the RAM access failed its memory allocation. The first [chars] is the RAM access command that failed, and the second [chars] describes whether processor memory allocation or I/O memory allocation failed.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section for more information."
"ETHCNTR","3","RA_REPLY_ERROR","Invalid reply to RAM Access [chars] request ([hex]) from satellite [dec].Note This message applies only to Catalyst 3550 switches.","A request to read from or write to the satellite RAM produced an unexpected reply. [chars] is the request type (read or write), [hex] is the address, and [dec] is the satellite number.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section for more information."
"ETHCNTR","3","SNAP_FORWARDING_UNSUPPORTED","IPv4/IPv6 SNAP forwarding will be disabled because switch [dec] does not support this feature.Note This message applies only to Catalyst 3750 switches.","A switch that is being added to the stack does not support the forwarding of IP Version 4 (IPv4) and IP Version 6 (IPv6) frames with Subnetwork Access Protocol (SNAP) encapsulation. If this occurs, forwarding of IPv4 and IPv6 frames is disabled in the switch stack. [dec] is the stack member number.","Replace the stack member with a switch that supports forwarding of IPv4 and IPv6 frames with SNAP encapsulation."
"ETHCNTR","3","UNEXPECTED_EVENT","Request [hex] encountered event [dec] in state [dec].Note This message applies only to Catalyst 3550 switches.","An unexpected event occurred during a RAM-access request. [hex] is a request identifier. The first [dec] is an event number, and the second [dec] is a state number.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section for more information."
"EXPRESS_SETUP","3","UNABLE_TO_RESET_CONFIG","[chars].","The system cannot reset the configuration. [chars] is a text string that explains why the reset failed. For example, error renaming config file, error removing config file, or error removing private config file.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"EXPRESS_SETUP","6","CONFIG_IS_RESET","[chars].","The configuration is reset. [chars] is a text message that clarifies the reset event, such as The configuration is reset and the system will now reboot.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"EOU","4","UNKN_EVENT_ERR","UNKNOWN Event for  HOST=[inet]| Event=[dec]| AUDITSESSID=[chars]","Unknown message for the EAPoUDP process. [inet] is the host identifier, [dec] is the event identifier, and [chars] is the session ID.","File a DDTS with Cisco."
"EOU","4","VERSION_MISMATCH","HOST=[inet]| Version=[dec]| AUDITSESSID=[chars]","A mismatch in the EAPoUDP versions was detected from the host. [inet] is the host identifier, [dec] is the EAPoUDP version, and [chars] is the session ID.","Check EAPoUDP versions on peers."
"EOU","5","AAA_DOWN","AAA unreachable. METHODLIST=[chars]| HOST=[inet]| POLICY=[chars].| AUDITSESSID=[chars]","The AAA servers defined by the method list cannot be reached by the host and the applied policy. The first [chars] is the method list identifer, [inet] is the host identifier, the second [chars] is the policy, and the third [chars] is the session ID.","Check the possible causes for unreachable AAA servers."
"EOU","5","RESPONSE_FAILS","Received an EAP failure response from AAA for host=[inet]| AUDITSESSID=[chars]","The router received an EAP failure response from authentication, authorization, and accounting (AAA). The host credentials were not validated. [inet] is the host, and [chars] is the session ID.","Check for causes of unsuccessful AAA validation of host credentials."
"EOU","6","AUTHTYPE","IP=[inet]| AuthType=[chars]| AUDITSESSID=[chars]","The authentication type for the host. [inet] is the host IP address, the first [chars] is the authentication type, and the second [chars] is the session ID.","No action is required."
"EOU","6","IDENTITY_MATCH","IP=[inet]| PROFILE=EAPoUDP| POLICYNAME=[chars]| AUDITSESSID=[chars]","The router has found the specifed host under the Extensible Authentication Protocol over User Datagram Protocol (EAPoUDP) identity profile. [inet] is the host IP address, the first [chars] is the enforced policy, and the second [chars] is the session ID.","If you do not want the host to be exempt from authentication, remove its entry from the EAPoUDP identity profile."
"EOU","6","POSTURE","IP=[inet]| HOST=[chars]| Interface=[chars]|AUDITSESSID=[chars]","The posture validation status for the host. [inet] is the host IP address, the first [chars] is the host identfier, the second [chars] is the host interface, and the third [chars] is the session ID.","No action is required."
"EOU","6","SESSION","IP=[inet]| HOST=[chars]| Interface=[chars]| AUDITSESSID=[chars]","An entry for the host was created or deleted on the specified interface. [inet] is the host IP address, the first [chars] is the host identifier, the second [chars] is the interface, and the third [chars] is the session ID.","No action is required."
"FM","1","INIT","Feature Manager subsystem initialization failure.Note This message applies only to Catalyst 3550 switches.","The feature manager subsystem did not initialize because of insufficient memory. Either the hardware has failed, or the wrong Cisco IOS image is installed.","Replace the failing hardware, or obtain the correct Cisco IOS image for this platform."
"FM","2","NOMAP","Cannot create Feature Manager data structures for VLAN Map [chars].Note This message applies only to Catalyst 3550 switches.","The feature manager could not allocate the data structures needed to describe a VLAN map into a form that can be loaded into hardware. This error is probably caused by a lack of free memory. [chars] is the VLAN map name.","Reduce other system activity to ease the memory demands."
"FM","2","NOSB","Cannot create subblock for interface [chars].Note This message applies only to Catalyst 3550 switches.","The feature manager could not save per-interface information needed for its correct operation. Some per-interface features, such as access groups or VLAN maps, will not be correctly configured. [chars] is the interface name.","Use a less complicated configuration that requires less memory."
"FM","2","NOVLB","Cannot create memory block for VLAN [dec].Note This message applies only to Catalyst 3550 switches.","The feature manager could not save per-VLAN information needed for its correct operation. Some per-interface features, such as access groups or VLAN maps, will not be correctly configured. [dec] is the VLAN ID.","Use a less complicated configuration that requires less memory."
"FM","2","NOVMR","Cannot create VMR data structures for access list [chars].Note This message applies only to Catalyst 3550 switches.","The feature manager could not allocate the data structures needed to describe an ACL in a form that can be loaded into hardware. This error is probably caused by a lack of available CPU DRAM. [chars] is the access-list name.","Use a less complicated configuration that requires less memory."
"FM","3","AUGMENTFAIL","Augmenting of access-map [chars] on [chars] label [dec] failed.Note This message applies only to Catalyst 3550 switches.","The system ran out of CPU memory when trying to merge internally required elements with the configured access maps. The first [chars] is the access-map name, the second [chars] is the direction in which the map was applied (input or output), and [dec] is the label number.","Reduce other system activity to ease the memory demands."
"FM","3","CONFLICT","[chars] [chars] conflicts with [chars].Note This message applies only to Catalyst 3550 switches.","Port access lists (PACLs) cannot be applied when input router access lists, VLAN maps, or IP multicast boundaries have been applied, and the reverse. [chars] are the names of the conflicting features.","Remove the conflicting feature or features, and apply the configuration again."
"FM","3","GOTLABEL","Got label for [chars].Note This message applies only to Catalyst 3550 switches.","The feature manager can allocate a hardware label for the interface. The interface needed a label before, but no label was available. [chars] is the label.","No action is required. (This message pairs with the FM-3-NOLABEL message and means that the previous error condition has rectified itself.)"
"FM","3","GOTVLABEL","Got label for VLAN [dec].Note This message applies only to Catalyst 3550 switches.","The feature manager can allocate a hardware label for the VLAN. The VLAN needed a label before, but no label was available. [dec] is the VLAN ID.","No action is required. (This message pairs with the FM-3-NOLABELVL message and means that the previous error condition has rectified itself.)"
"FM","3","ILLEGALCOPY","Illegal copy of [chars] access group [chars] from [chars] label [dec] to [dec].Note This message applies only to Catalyst 3550 switches.","An internal software error occurred. The first [chars] is either ip or mac, the second [chars] is an access list name, the third [chars] is either port or vlan, and the two [dec] values are label numbers.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"FM","3","INITLABEL","Special initialization of label [dec] failed.Note This message applies only to Catalyst 3550 switches.","The access list hardware initialization failed. Prioritization of routing protocol packets above other kinds of packets might not occur on some VLANs or routed ports. [dec] is the label number.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section for more information."
"FM","3","INSERTFAIL","Insert of access-map [chars] [dec] into [chars] label [dec] failed.Note This message applies only to Catalyst 3550 switches.","The system ran out of CPU memory when trying to merge sections of an access map. The first [chars] is the map name, and the second [chars] is the direction in which the map was applied. The first [dec] is the entry number, and the second [dec] is the label number.","Reduce other system activity to ease the memory demands. For example, remove any ACLs that have been defined but are not now used. Use simpler ACLs with fewer access control entries (ACEs). Use fewer VLANs, and remove any unneeded VLANs from the VLAN database."
"FM","3","INTTABLE","Not in truth table: VLMAP [dec] RACL [dec] Rtprot [dec] Redir [dec] Mcb [dec] Feat [dec].Note This message applies only to Catalyst 3550 switches.","An unrecoverable software error occurred while the software was trying to merge the configured input features. The first five [dec] values are internal code numbers for the results of the VLAN map, router ACL, routing protocol selector, IP redirect settings, and the multicast boundary configured on a Layer 3 interface. The sixth [dec] value is the feature that was being examined when the problem was detected.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"FM","3","LABELERROR","Incorrect label to [chars] vlan label attribute copy callback srclabel [dec], dstlabel [dec].Note This message applies only to Catalyst 3550 switches.","The feature manager copy callback attribute was called with an incorrect source or destination label. [chars] is the direction (input or output), the first [dec] is the source label value, and the second [dec] is the destination label value.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"FM","3","MAXRECURSION","Too many ([dec]) levels of recursion while merging [chars] (code [dec]). Note This message applies only to Catalyst 3550 switches.","The configuration is too complicated for the platform-specific ACL merge code to support. The most likely cause is too many separate access lists in a single VLAN map or policy map. The first [dec] is the number of levels of recursion. [chars] describes the merge stage that encountered the problem, such as VLAN map, Global Input, Global Output, or QoS Map. The second [dec] is an internal code number of the merge stage that encountered the problem.","Reduce the number IP or MAC access lists (counted separately) in any one VLAN or policy map to fewer than the number of levels reported by this log message."
"FM","3","MERGEFAIL","[chars] ACL merge error [dec] ([chars]) on [chars] label [dec].Note This message applies only to Catalyst 3550 switches.","The feature manager could not merge the configured features into a form suitable for loading into the hardware. Packets potentially affected by this feature are sent to the CPU for processing. The CPU processing needed to uphold the overflowed ACL severely degrades performance. The first [chars] is the ACL-type error (ip or mac), the first [dec] is the error code, the second [chars] is the message string for the preceding error code, the second [dec] is the label number, and the third [chars] is either input or output.","Reorganize the ACLs so that all entries fit into hardware. Use less complicated and fewer ACLs."
"FM","3","NOLABEL","Cannot allocate [chars] label for interface [chars].Note This message applies only to Catalyst 3550 switches.","The feature manager could not allocate a label for the features on this interface. This means that the hardware cannot be programmed to implement the features, and packets for this interface will be filtered in software. There is a limit of 256 labels per direction. The first [chars] is the direction (input or output), and the second [chars] is the interface name.","Allocate more space to the relevant section of the TCAM by using the sdm prefer global configuration command and reboot the switch, or use a simpler configuration. Use the same ACLs on multiple interfaces, if possible."
"FM","3","NOLABELVL","Cannot allocate [chars] label for VLAN [dec].Note This message applies only to Catalyst 3550 switches.","The feature manager could not allocate a label for the features on this VLAN. This means that the hardware cannot be programmed to implement the features, and packets on this VLAN will be filtered in software. There is a limit of 256 labels per direction. [chars] is the direction (input or output), and [dec] is the VLAN ID.","Allocate more space to the relevant section of the TCAM by using the sdm prefer global configuration command and reboot the switch, or use a simpler configuration. Use the same VLAN map on multiple VLANs, if possible."
"FM","3","NOTEMPTY","Illegal copy of attribute to non empty [chars] vlan label [dec].Note This message applies only to Catalyst 3550 switches.","The feature manager copy callback attribute was called with a destination label already being used by a VLAN or routed port. [chars] is the direction (input or output), and [dec] is the label value.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"FM","3","NOTOBJECT","Invalid object (VLAN [dec], IDB [hex]) used in Feature Manager operation.Note This message applies only to Catalyst 3550 switches.","An internal software error has occurred. An invalid combination of VLAN and interface descriptor block (IDB) values was passed to a software routine. [dec] is the VLAN ID, and [hex] is the IDB value.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"FM","3","NULLCPU","Sending traffic on empty [chars] label [dec] to CPU.Note This message applies only to Catalyst 3550 switches.","An internal software error occurred. [chars] is the direction (input or output), and [dec] is the label number.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section for more information."
"FM","3","OUTTTABLE","Not in truth table: RACL [dec] VLMAP [dec].Note This message applies only to Catalyst 3550 switches.","An unrecoverable software error occurred while trying to merge the configured output features. The two [dec] values are internal code numbers for the results of the router ACL and VLAN map configured on a particular Layer 3 interface.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"FM","3","QOSTTABLE","Not in truth table: ACL [dec] in map, action [dec].Note This message applies only to Catalyst 3550 switches.","A software error occurred while trying to merge a quality of service (QoS) policy map. The first [dec] is the number in the policy map (counting from zero) of the particular ACL where the problem was discovered, and the second [dec] is an internal code number for the result of matching that ACL in the policy map.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"FM","3","RELOADED","Reloading [chars] label [dec] feature in [chars].Note This message applies only to Catalyst 3550 switches.","The feature manager can now load more of the configured features on this label into the hardware. One or more features had been previously unloaded because of a lack of space. The first [chars] is the direction (input or output), [dec] is the label number, and the second [chars] is the TCAM ID.","No action is required."
"FM","3","TOSCOST","Minimize monetary cost TOS bit unsupported in hardware, ignored.Note This message applies only to Catalyst 3550 switches.","This hardware platform does not support filtering based on the type of service (ToS) and precedence. It supports filtering based on Differentiated Services Code Points (DSCPs). The DSCP field does not include the minimize monetary cost bit from the ToS field. The hardware ignores this bit when checking for a match to an ACE, which can lead to unintended filtering actions.","Design filters that do not test for the minimum monetary cost ToS."
"FM","3","UNKNOWNACTION","Unknown VMR access group action [hex].Note This message applies only to Catalyst 3550 switches.","An internal software error has occurred.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section for more information."
"FM","3","UNLOADING","Unloading [chars] label [dec] feature from [chars].Note This message applies only to Catalyst 3550 switches.","The feature manager could not load the complete configuration into the hardware, so some features will be applied in the software. Some or all the packets are forwarded by the CPU. Multicast packets might be dropped instead of being forwarded. The first [chars] is the direction (input or output), [dec] is the label number, and the second [chars] is the TCAM ID.","Allocate more space to the relevant section of the TCAM by using the sdm prefer global configuration command and then reboot the switch, or use a simpler configuration. Use the same ACLs on multiple interfaces, if possible."
"FM","3","WRONGLABEL","Inconsistent records of label for [chars]: FM has [dec], LM has [dec].Note This message applies only to Catalyst 3550 switches.","An internal software error has occurred. [chars] is an interface name. The rest of the message FM has [dec], LM has [dec] means that the feature manager has a record that the interface belongs to the first [dec] and that the label manager has a record that the interface belongs to the second [dec]. Therefore, the software is in an inconsistent state.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"FM","4","EXCESSSECONDARY","More than [dec] secondary IP addresses configured on interface [chars].Note This message applies only to Catalyst 3550 switches.","When secondary IP addresses are configured on an interface and you enable Internet Control Message Protocol (ICMP) redirects for packets received on that interface, the ICMP redirect function on the CPU is not usually notified of packets sent between two different subnets on the same interface. If too many secondary IP addresses are configured on the interface this message is logged, and in addition to being notified about packets that cause the generation of an ICMP redirect, the CPU is also notified about every packet routed between two different subnets that are both on the interface. No ICMP redirects will be sent in error, but the CPU usage might increase because of the additional notifications. [dec] is the limit of secondary IP addresses, and [chars] is the specified interface.","You can use the no ip redirects interface configuration command on the interface named in the message to reduce the CPU load on the system."
"FM","7","TRANSDEF","No augmentation function found for VMR.Note This message applies only to Catalyst 3550 switches.","An internal error occurred. An ACL was not correctly interpreted. The value-mask result (VMR) is incorrect.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section for more information."
"FRNTEND_CTRLR","1","MGR_TXQ_FULL","The front end controller Tx queue reached watermark level Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","There are too many messages in the queue between the front-end controller and the switch software.","Try reloading the switch. If this does not resolve the issue, this might be a hardware problem. Contact the Cisco technical support representative."
"FRNTEND_CTRLR","2","SUB_INACTIVE","The front end controller [dec] is inactive. Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","The front-end controller that controls the LEDs, the PoE features, and the fan-control features is now inactive on the port controlled by the front-end controller. This does not affect the traffic on the port. [dec] is the controller number.","Reset the switch. If the problem is not resolved by resetting the switch, contact your Cisco technical support representative because there might be a problem with the switch."
"GBIC_1000BASET","6","GBIC_1000BASET_DEFAULT_CONFIG","1000BASE-T GBIC module is detected in [chars]. Speed and duplex will be autonegotiated.Note This message applies only to Catalyst 3550 switches.","A 1000BASE-T GBIC module is detected in the slot, and its speed and duplex are automatically negotiated. [chars] is the slot in which the module is installed.","No action is required."
"GBIC_1000BASET","6","GBIC_1000BASET_NO_CONFIG_DUPLEX","Configuration ignored. 1000-BaseT GBIC modules only support autonegotiation on duplex. Note This message applies only to Catalyst 3550 switches.","Autonegotiation was not used. The 1000BASE-T GBIC modules only support autonegotiation on duplex.","No action is required."
"GBIC_1000BASET","6","GBIC_1000BASET_NO_CONFIG_NEGOTIATE","Configuration ignored. 1000BASE-T GBIC modules only support autonegotiation.Note This message applies only to Catalyst 3550 switches.","The disabling of autonegotiation was not used. The 1000BASE-T GBIC modules support autonegotiation.","No action is required."
"GBIC_1000BASET","6","GBIC_1000BASET_NO_CONFIG_SPEED","Configuration ignored. 1000-BaseT GBIC modules only support autonegotiation on speed. Note This message applies only to Catalyst 3550 switches.","Autonegotiation was ignored. The 1000BASE-T GBIC modules only support autonegotiated speed.","No action is required."
"GBIC","4","CHECK_SUM_FAILED","GBIC EEPROM data check sum failed for GBIC interface [chars].Note This message applies only to Catalyst 3550 switches.","The GBIC module was identified as a Cisco GBIC module but the system could not read vendor-data information to verify its accuracy. [chars] is the interface in which the module is installed.","Remove and re-insert the GBIC module. If it continues to fail after re-insertion, it might be defective."
"GBIC","4","NOREAD_VNAME","Unable to read vendor name for GBIC interface [chars].Note This message applies only to Catalyst 3550 switches.","The GBIC module was identified as a Cisco GBIC module but the system could not read the GBIC vendor name. [chars] is the interface in which the module is installed.","Remove and re-insert the GBIC module. If it continues to fail after re-insertion, it might be defective."
"GBIC","4","NOREAD_VSDATA","Unable to read vendor-specific data for GBIC interface [chars].Note This message applies only to Catalyst 3550 switches.","The GBIC module was identified as a Cisco GBIC module but the system could not read the identifying vendor-specific information to verify its authenticity. [chars] is the interface in which the module is installed.","Remove and re-insert the GBIC module. If it continues to fail after re-insertion, it might be defective."
"GBIC","4","NOREAD_VSERNUM","Unable to read serial number for GBIC interface [chars].Note This message applies only to Catalyst 3550 switches.","The GBIC module was identified as a Cisco GBIC module but the system could not read the serial number of the GBIC module. [chars] is the interface in which the module is installed.","Remove and re-insert the GBIC module. If it continues to fail after re-insertion, it might be defective."
"GBIC","4","UNRECOGNIZED_EXTTYPE","GBIC interface [chars] has unrecognized extended type.Note This message applies only to Catalyst 3550 switches.","The GBIC module was identified as a Cisco GBIC module, but the system does not recognize its reported extended type code. [chars] is the interface in which the module is installed.","Check the list of supported GBIC modules for this version of the system software. An upgrade might be required for newer GBIC modules. Even if the module is unrecognized, it might still operate properly, but perhaps with limited functionality."
"GBIC","4","XCVR_INTERR","Internal error occurred in setup for GBIC interface [chars].Note This message applies only to Catalyst 3550 switches.","The system could not allocate resources or had some other problem during the setup for the specified GBIC interface. [chars] is the interface in which the GBIC module is installed.","Reload the switch by using the reload privileged EXEC command. If the problem persists, call your Cisco technical support representative."
"GBIC","6","SERDES_MODULE_UNKNOWN","Unrecognizable GBIC found in [chars] (module mask [hex]).Note This message applies only to Catalyst 3550 switches.","The GBIC module presented data to the system that did not correctly identify the type of the GBIC module. The switch will treat it as a generic GBIC module. [chars] is the name of the interface in which the unknown module is installed, and [hex] is the module type value returned by the module.","If the GBIC module fails to become operational, carefully remove and re-insert it in the slot. If it continues to fail after re-insertion, it might be defective or incompatible with the switch."
"GBIC","6","SERDES_SERIAL_INV_DATA","Unrecognizable GBIC found in [chars] (serial data [hex]).Note This message applies only to Catalyst 3550 switches.","The GBIC module presented data to the system that did not correctly identify the type of the GBIC module. The switch will treat it as a generic GBIC module. [chars] is the name of the interface where the unrecognizable module is found, and [hex] is the data value returned by the module.","If the GBIC module fails to become operational, carefully remove and re-insert it in the slot. If it continues to fail after re-insertion, it might be defective or incompatible with the switch."
"GBIC_SECURITY","4","DUPLICATE_SN","GBIC interface [dec] has the same serial number as another GBIC interface.Note This message applies only to Catalyst 3550 switches.","The GBIC module was identified as a Cisco GBIC module, but its serial number matches that of another interface on the system. [chars] is the interface in which the module is installed.","Cisco GBIC modules are assigned unique serial numbers. Verify that the module was obtained from Cisco or a supported vendor."
"GBIC_SECURITY","4","EEPROM_CRC_ERR","EEPROM checksum error for GBIC in [chars].Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The GBIC in the specified port has invalid EEPROM data. [chars] is the port in which the GBIC is inserted.","Remove the GBIC from the port."
"GBIC_SECURITY","4","EEPROM_READ_ERR","Error in reading GBIC serial ID in [chars]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","An error occurred while the switch was reading the GBIC type from the EEPROM. [chars] is the port in which the GBIC is inserted.","Remove the GBIC from the port."
"GBIC_SECURITY","4","EEPROM_SECURITY_ERR","GBIC in [chars] failed security check.Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The GBIC in the specified port has invalid EEPROM data. [chars] is the port in which the GBIC is inserted.","Remove the GBIC from the port."
"GBIC_SECURITY","4","GBIC_INTERR","Internal error occurred in setup for GBIC interface [chars].","The system could not allocate resources or had some other problem during the setup for the specified SFP module interface. [chars] is the interface in which the SFP module is installed.","Reload the switch by using the reload privileged EXEC command. If the problem persists, find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"GBIC_SECURITY","4","ID_MISMATCH","Identification check failed for GBIC interface [chars].Note This message applies only to Catalyst 3550 switches.","The GBIC module was identified as a Cisco GBIC module but the system could not verify its identity. [chars] is the interface in which the module is installed.","Check the list of supported GBIC modules for this version of the system software. An upgrade might be required for newer modules. Otherwise, verify that the module was obtained from Cisco or a supported vendor."
"GBIC_SECURITY","4","UNRECOGNIZED_VENDOR","GBIC interface [chars] manufactured by an unrecognized vendor.Note This message applies only to Catalyst 3550 switches.","The GBIC module was identified as a Cisco GBIC module but the system could not match its manufacturer with one of the known list of Cisco GBIC vendors. [chars] is the interface in which the module is installed.","Check the list of supported GBIC modules for this version of the system software. An upgrade might be required for newer modules."
"GBIC_SECURITY","4","VN_DATA_CRC_ERROR","GBIC interface [chars] has bad crc.Note This message applies only to Catalyst 3550 switches.","The GBIC module was identified as a Cisco GBIC module, but it does not have a valid CRC in the EEPROM data. [chars] is the interface in which the module is installed.","Check the list of supported GBIC modules for this version of the system software. An upgrade might be required for newer modules. Even if unrecognized, the module might still operate properly, perhaps with limited functionality."
"GBIC_SECURITY","6","SFP_INSERTED","Transceiver SFP [chars] module inserted in [chars]","The online insertion and removal (OIR) facility detected a newly inserted transceiver module for the interface specified in the message. The first [chars] is the module, and the second [chars] is the interface.","No action is required."
"GBIC_SECURITY","6","SFP_REMOVED","Transceiver SFP [chars] module removed from [chars]","The OIR facility detected the removal of a transceiver module from the interface specified in the message. The first [chars] is the module, and the second [chars] is the interface.","No action is required."
"GBIC_SECURITY_CRYPT","4","ID_MISMATCH","Identification check failed for GBIC interface [chars].","The SFP module was identified as a Cisco SFP module, but the system could not verify its identity. [chars] is the port.","Ensure that the Cisco IOS software running on the switch supports the SFP module. You might need to upgrade your software. Otherwise, verify that the SFP module was obtained from Cisco or from a supported vendor."
"GBIC_SECURITY_CRYPT","4","UNRECOGNIZED_VENDOR","GBIC interface [chars] manufactured by an unrecognized vendor.","The SFP module was identified as a Cisco SFP module, but the switch could not match its manufacturer with one on the known list of Cisco SFP module vendors. [chars] is the port.","Ensure that the Cisco IOS software running on the switch supports the SFP module. You might need to upgrade your software."
"GBIC_SECURITY_CRYPT","4","VN_DATA_CRC_ERROR","GBIC interface [chars] has bad crc.","The SFP module was identified as a Cisco SFP module, but it does not have a valid cyclic redundancy check (CRC) in the EEPROM data. [chars] is the port.","Ensure that the Cisco IOS software running on the switch supports the SFP module. You might need to upgrade your software. Even if the switch does not recognize the SFP module, it might still operate properly but have limited functionality."
"GBIC_SECURITY_UNIQUE","3","DUPLICATE_GBIC","GBIC interface [dec]/[dec] is a duplicate of GBIC interface [dec]/[dec].Note This message applies only to Catalyst 3750, 3560, and 2970 switches.","The SFP module was identified as a Cisco GBIC or SFP module, but its vendor ID and serial number match that of another interface on the system. The first [dec]/[dec] is the interface of the duplicate GBIC or SPF module, and the second [dec]/[dec] is the interface of the existing module.","Cisco GBIC or SFP modules are assigned unique serial numbers. Verify that the module was obtained from Cisco or from a supported vendor."
"GBIC_SECURITY_UNIQUE","4","DUPLICATE_SN","GBIC interface [dec]/[dec] has the same serial number as another GBIC interface.Note This message applies only to Catalyst 3750, 3560, and 2970 switches.","The SFP module was identified as a Cisco SFP module, but its serial number matches that of another interface on the system. [dec]/[dec] is the interface in which the duplicate module is installed.","Cisco SFP modules are assigned unique serial numbers. Verify that the module was obtained from Cisco or from a supported vendor."
"GIGASTACK","1","NO_LOOP_DETECT","The link neighbor of link [dec] of GigaStack GBIC in [chars] did not respond to the loop detection request. If loop topology is deployed, make sure all switches in the stack are running the latest software.Note This message applies only to Catalyst 3550 switches.","No acknowledgement for the loop-detection request is received from one of the links on a GigaStack GBIC module. Either the neighboring switch does not support the GigaStack GBIC loop-breaking algorithm, or the link between the two GigaStack GBIC modules is broken. Under this condition, a GigaStack loop topology is not automatically detected, and the connectivity between switches in the stack can be lost. [dec] is the link number, and [chars] is the slot number.","If a loop topology is used with the GigaStack GBIC module, ensure that the latest software is running on all switches in the stack. Check the GigaStack GBIC modules involved to ensure that they are functioning."
"GIGASTACK","3","INIT_FAILURE","GigaStack GBIC in [chars] initialization failed.Note This message applies only to Catalyst 3550 switches.","The GigaStack GBIC module failed power-on self-test (POST). [chars] is the interface name.","Remove the GigaStack GBIC module, and re-insert it into the GBIC module slot."
"GIGASTACK","6","LOOP_BROKEN","Link loss is detected in the GigaStack loop. Link 2 of the GigaStack GBIC in [chars] is re-enabled.Note This message applies only to Catalyst 3550 switches.","The loop formed by GigaStack GBIC modules is broken because of a link loss. Link 2 of the master loop breaker is re-enabled to replace the broken link. [chars] is the interface name.","No action is required."
"GIGASTACK","6","LOOP_DETECTED","GigaStack GBIC in [chars] is selected as Master Loop Breaker. Link 2 of the GigaStack GBIC is disabled to break the loop.Note This message applies only to Catalyst 3550 switches.","A loop is detected in the stack, and this GigaStack GBIC module is selected as the master loop breaker. Link 2 of this GigaStack GBIC module is disabled to break the loop. [chars] is the interface name.","No action is required."
"HARDWARE","1","PSU_THERMAL_CRITICAL","PSU [chars] temperature has reached critical threshold","The switch PSU temperature sensor value has reached the critical level, and the switch cannot function normally. The external temperature is very high. [chars] is the power supply.","Immediately reduce the room temperature."
"HARDWARE","1","TCAM_ERROR","[traceback] Found error in [chars] TCAM Space and not able to recover the errorNote This message is not applicable on Catalyst 2960-S switches.","The switch cannot fix a ternary content addressable memory (TCAM) integrity error. [chars] is the memory location with the error: Unassigned TCAM Space, HFTM TCAM Space (the ASIC forwarding TCAM manager space), or HQATM TCAM Space (the TCAM ASIC quality of service [QoS] and access control list [ACL] TCAM manager space).","Restart the switch."
"HARDWARE","2","FAN_ERROR","Fan [chars] Failure","The switch fan is not working. [chars] is the fan name.","This occurs when the hardware fails. The fan might recover automatically. If the fan on the switch continues to fail, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about the online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"HARDWARE","2","PSU_THERMAL_WARNING","PSU [chars] temperature has reached warning threshold","The switch power supply unit (PSU) temperature sensor value has reached the warning level. The external temperature is high. [chars] is the power supply.","Reduce the temperature in the room. (The switch functions normally until the temperature reaches the critical level.)"
"HARDWARE","2","THERMAL_WARNING","Temperature has reached warning threshold.Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The switch temperature sensor value has reached the warning level. The external temperature is high.","Reduce the room temperature. (The switch functions normally until the temperature reaches the critical level.)"
"HARDWARE","3","MCU_I2C_BAD_DEV","I2C bad device address: [hex] (alchemy[dec])","MCU I2C read or write failed at a particular I2C device address. [hex] is the message number, and [dec] is the alchemy number].","Ensure the environment temperature is not too high or too low."
"HARDWARE","3","ASICNUM_ERROR","[traceback] Port-ASIC number [dec] is invalid","The port ASIC number is invalid. [dec] is the port ASIC number.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still need assistance, open a case with the TAC, or provide your Cisco technical support representative with your information."
"HARDWARE","3","INDEX_ERROR","Index value [dec] is invalid.Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The index into the hardware table is out-of-range. [dec] is the index value.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"HARDWARE","3","INTRNUM_ERROR","Port-ASIC Interrupt number [dec] is invalid.Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The interrupt ID used in a port ASIC is invalid. [dec] is the interrupt number.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"HARDWARE","3","PORTNUM_ERROR","[traceback] port number [dec] is invalid","The port number is out of range. [dec] is the port number.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still need assistance, open a case with the TAC, or provide your Cisco technical support representative with your information."
"HARDWARE","3","STATS_ERROR","Statistics ID [dec] is invalid.Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The statistics ID used is out of range. The statistics supported by the port ASIC are identified by an ID. [dec] is the statistics ID.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"HARDWARE","5","PSU_THERMAL_NORMAL","PSU [chars] Temperature is within the acceptable limit","The switch PSU temperature sensor value is within normal limits. [chars] is the power supply.","No action is required."
"HLFM","3","MACFREE_ERROR","MAC address [enet], vlan [dec] is still referenced; cannot free. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","An attempt was made to free a MAC address before releasing all references to it. [enet] is the MAC address, and [dec] is the VLAN ID.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"HLFM","3","MAP_ERROR","IP address [IP_address] not in mac tables, mac-address [enet], vlan [dec].Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The IP address and MAC address tables are out of sync. [IP_address] is the IP address, [enet] is the MAC address, and [dec] is the VLAN ID.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"HLFM","3","MOD_SD","Failed to modify Station Descriptor with index [dec], vlan [dec], di [dec], error [dec], mad [dec], ref-count [dec]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The forwarding manager attempted to modify a station descriptor that is no longer in use or is invalid. The first [dec] is the station index, the second [dec] is the VLAN ID, the third [dec] is the destination index, the fourth [dec] is the error code, the fifth [dec] is the MAC address descriptor, and the sixth [dec] is the ref-count for this MAC address descriptor.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"HLFM","3","SEND_FAIL","Failed to send RPC message, req [dec], [chars]. Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","There is a local resource error or that too many outgoing messages are queued for the message class. [dec] is the RPC request number, and [chars] is an optional comment.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"HPSECURE","6","ADDR_REMOVED","Address [enet]:[dec] on port [chars] cannot be added on switch [dec] and has been removed.Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","At least one switch in the stack could not add the MAC address because a resource failed, and the MAC address has been deleted from all the switches in the stack. [enet] is the MAC address, the first [dec] is the VLAN to which the MAC address is assigned, [chars] is the interface, and the second [dec] is the stack member number.","No action is required."
"HULC_LICENSE","1","LICENSE_REGISTER_FAILED","[chars] - rc = [dec]Note This message applies only to Catalyst 2960-S switches.","The licensing initialization failed. [chars] explains what part of the license registration failed, and [dec] is the type of license initialization error.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still need assistance, open a case with the TAC, or provide your Cisco technical support representative with your information."
"IDBMAN","3","AGGPORTMISMATCH","[chars]: [chars]([dec] / [dec]) does not match internal slot/port state [chars]([dec] / [dec]). Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","There is an internal error that caused an invalid aggregate port to be used by the software. The first [chars] is the name of the function where the error occurred. The second and third [chars] are the port-channel names, and the ([dec] / [dec]) are the slot and port numbers (slot/port).","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"IDBMAN","3","DELETEDAGGPORT","[chars]([dec] / [dec]) Group [dec] has been deleted, but is being reused. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","There is an internal error that caused an interface that has been deleted to be reused for a new aggregate port. [chars] is the port-channel name, and the ([dec] / [dec]) are the slot and port numbers (slot/port). The last [dec] is the channel-group number.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"IDBMAN","3","INVALIDAGGPORTBANDWIDTH","[chars]([dec] / [dec]) has an invalid bandwidth value of [dec]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","There is an internal error that caused an invalid bandwidth to be used for an aggregate port. [chars] is the port-channel name. The ([dec] / [dec]) are the slot and port numbers (slot/port). The last [dec] is the bandwidth.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"IDBMAN","3","INVALIDPORT","[chars]: trying to use invalid port number [dec] ( Max [dec] ). Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","There is an internal error that caused an invalid port number to be used by the software. [chars] is the interface name. The first [dec] is the port number that is invalid, and the second [dec] is the maximum allowed value for a port number.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"IDBMAN","3","INVALIDVLAN","[chars]: trying to use invalid Vlan [dec].Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","There is an internal error that caused an invalid VLAN to be used by the software. [chars] is the interface name, and [dec] is the VLAN ID that is invalid.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"IDBMAN","3","NOTANAGGPORT","[chars]( [dec] / [dec] ) is not an aggregate port. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","There is an internal error that caused an interface that is not an aggregate port to be used for aggregate port operations. [chars] is the interface name, and ([dec] / [dec]) are the slot and port number (slot/port).","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"IDBMAN","3","PORTNOTINAGGPORT","[chars]([dec] / [dec]) is not present in Aggport [chars [([dec] / [dec]). Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","An internal error has been detected. A port that was supposed to be in an aggregate port was found not to be. The first [chars] is the interface name, and the second [chars] is the port-channel name. The ([dec] / [dec]) are the slot and port numbers (slot/port).","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"IDBMAN","3","VLANNOTSET","[chars]: Vlan [dec] not set since it already has Vlan [dec].Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","An interface VLAN was not set to the requested value because of an internal error. [chars] is the interface name. The first [dec] is the recently configured VLAN ID, and the second [dec] is the currently assigned VLAN ID.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"IDBMAN","4","ACTIVEPORTSINAGGPORT","[chars]( [dec] / [dec] ) has [dec] active ports, but is being removed. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","An internal error removed an aggregate port that has active ports. [chars] is the port-channel name, and the ([dec] / [dec]) are the slot and port number (slot/port). The last [dec] is the number of currently active ports.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"IFMGR","3","IFINDEX_PERSIST_ENTRY_CORRUPT","[chars] seems to be corrupted. Trying to read [dec] size","The ifIndex table is corrupted. [chars] is the path to the IfIndex file, and [dec] is the number of bytes that was being read from the ifIndex table when the corruption was detected.","Delete the ifindex table."
"IFMGR","3","INVALID_PERSISTENT_DATA","Invalid persistent data","The interface manager attempts to write invalid persistent data.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still need assistance, open a case with the TAC, or provide your Cisco technical support representative with your information."
"IGMP_QUERIER","4","NO_IP_ADDR_CFG","The IGMP querier cannot send out General Query messages in VLAN [dec] because there is no IP address configured on the system. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","An IP address for the IGMP querier was not configured at either the global or per-VLAN level. [dec] is the VLAN ID.","Configure a source IP address for the IGMP querier."
"IGMP_QUERIER","4","PIM_ENABLED","The IGMP querier is operationally disabled in VLAN [dec] because PIM has been enabled on the SVI. Note This message applies only to Catalyst 3750 and 3560 switches.","Protocol-Independent Multicast (PIM) was detected on the switch virtual interface (SVI). Do not enable the IGMP querier when PIM is enabled on the SVI. [dec] is the VLAN ID.","Ensure that PIM is disabled on the SVI."
"IGMP_QUERIER","4","SNOOPING_DISABLED","The IGMP querier is operationally disabled in VLAN [dec] because IGMP snooping has been disabled in this VLAN. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","IGMP snooping is disabled on this VLAN. Do not enable the IGMP querier when IGMP snooping is disabled. [dec] is the VLAN IDs.","Confirm that IGMP snooping is enabled both globally and on the VLAN."
"IGMP_QUERIER","6","PIM_DISABLED","The IGMP querier is now operationally enabled in VLAN [dec] because PIM is no longer enabled on the SVI. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","PIM is disabled on the SVI, and the IGMP querier function is now enabled. [dec] is the VLAN ID.","No action is required."
"IGMP_QUERIER","6","SNOOPING_ENABLED","The IGMP querier is now operationally enabled in VLAN [dec] because IGMP snooping is no longer disabled. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","IGMP snooping was enabled. As a result, the IGMP querier function is now enabled. [dec] is the VLAN ID.","No action is required."
"ILET","1","AUTHENTICATION_FAIL","This Switch may not have been manufactured by Cisco or with Cisco's authorization.  This product may contain software that was copied in violation of Cisco's license terms.  If your use of this product is the cause of a support issue, Cisco may deny operation of the product, support under your warranty or under a Cisco technical support program such as Smartnet.  Please contact Cisco's Technical Assistance Center for more information.","A license authentication failure occurred for the switch.","Contact your Cisco sales representative for assistance."
"ILET","1","DEVICE_AUTHENTICATION_FAIL","The [chars] inserted in this switch may not have been manufactured by Cisco or with Cisco's authorization. If your use of this product is the cause of a support issue, Cisco may deny operation of the product, support under your warranty or under a Cisco technical support program such as Smartnet.  Please contact Cisco's Technical Assistance Center for more information.","A license authentication failure occurred for a component that was inserted in the switch. [chars] is the component.","Contact your Cisco sales representative for assistance."
"ILPOWER","3","CONTROLLER_ERR","Controller error, Controller number [dec]: [chars]. Note This message applies only to Catalyst 3750, 3560, and 3550 switches.","An error reported or caused by the PoE controller is detected. [dec] is the controller instance, which is 0 to 5 on a 24-port PoE switch and 0 to 11 on a 48-port PoE switch. [chars] describes the error.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"ILPOWER","3","CONTROLLER_ERR","Controller error, Controller number [chars]: accessing failedNote This message applies only to Catalyst 3550-24PWR switches.","An error reported or caused by the PoE controller was detected. [chars] is the controller number.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section for more information."
"ILPOWER","3","CONTROLLER_ERR","Controller error, Controller number [chars]:Reset failedNote This message applies only to Catalyst 3550-24PWR switches.","An error reported or caused by the PoE controller was detected. [chars] is the controller number.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section for more information."
"ILPOWER","3","CONTROLLER_IF_ERR","Controller interface error, [chars]: [chars]. Note This message applies only to Catalyst 3750, 3560, and 3550 switches.","An interface error is detected between the PoE controller and the system. The first [chars] is the interface. The second [chars] describes the error.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"ILPOWER","3","CONTROLLER_IF_ERR","Controller interface error, S2W bus:Initialization failed.Note This message applies only to Catalyst 3550-24PWR switches.","An interface error was detected between the PoE controller and the system.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section for more information."
"ILPOWER","3","CONTROLLER_PORT_ERR","Controller port error, Interface Fa0/7:Power given, but link is not up.Note This message applies only to the Catalyst 3750 and 3560 switches.","The inline-power-controller reported an error on an interface.","Enter the shutdown and no shutdown interface configuration commands on the affected interfaces. Upgrade to Cisco IOS Release12.1(14)EA1 or later, which provides an electrostatic discharge (ESD) recovery mechanism."
"ILPOWER","3","CONTROLLER_POST_ERR","Inline Power Feature is disabled on this switch because Power On Self Test (POST) failed on this switch. Please consult TECH support for further assistance Note This message applies only to Catalyst 3750, 3560, and 3550 switches.","An error reported or caused by the Power over Ethernet (PoE) controller is detected during power-on self-test (POST).","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"ILPOWER","3","ILPOWER_INTERNAL_IF_ERROR","Inline Power internal error, interface [chars]: [chars]. Note This message applies only to Catalyst 3750 and 3560 switches.","A software check failed during PoE processing. The first [chars] is the interface. The second [chars] describes the error.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"ILPOWER","3","ILPOWER_INTERNAL_IF_ERROR","Inline Power internal error. Interface cannot obtain asic-cnfg information.Note This message applies only to Catalyst 3550-24PWR switches.","The PoE feature code failed for unknown reasons. A software error has probably occurred.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section for more information."
"ILPOWER","4","LOG_OVERDRAWN","Interface [chars] is overdrawing power. it is consuming [dec] milliwatts where as maximum configured power is ([dec]) milliwatts. Note This message applies only to Catalyst 3750, 3560, and 3550 switches.","The powered device is drawing more power than the maximum powered configured on the interface. [chars] is the interface, and [dec] is the maximum configured power.","Ensure that the correct power is budgeted for this interface based on the powered-device electrical specifications or ratings. Otherwise, you might risk overloading the switch. We recommend that you change the cutoff power value if needed."
"ILPOWER","5","CLR_OVERDRAWN","Interface [chars] is NOT overdrawing power. it is consuming [dec] milliwatts where as maximum configured value is ([dec]) milliwatts. Note This message applies only to Catalyst 3550 switches.","The device connected to the Power over Ethernet (PoE) interface is consuming more power than the maximum power allocation. [chars] is the interface. The first [dec] is the power being consumed, and the second [dec] is the maximum allocated power value.","No action is required."
"ILPOWER","5","CONTROLLER_OVERDRAWN","Interface [chars] is NOT overdrawing power. it is consuming [dec] milliwatts where as maximum configured value is ([dec]) milliwatts. Note This message applies only to Catalyst 3750, 3560, and 3550 switches.","The device connected to the Power over Ethernet (PoE) interface is consuming more power than the maximum power allocation. [chars] is the interface. The first [dec] is the power being consumed, and the second [dec] is the maximum allocated power value.","No action is required."
"ILPOWER","5","DC_DISCONNECT","Interface [chars]: DC disconnect.Note This message applies only to Catalyst 3550-24PWR switches.","The DC power has been disconnected.","No action is required."
"ILPOWER","5","IEEE-DISCONNECT","Interface [chars]: PD removed.Note This message applies only to Catalyst 3750 and 3560 switches.","The powered device is no longer connected to the switch or that the connected powered device is being powered by an external AC power source. The switch is no longer providing power to the port. [chars] is the interface.","No action is required."
"ILPOWER","5","ILPOWER_POWER_CDP_SHUT","Interface [chars]: inline power shut Note This message applies only to Catalyst 3750, 3560, and 3550 switches.","Inline power is shut down because CDP consumption power on this Power over Ethernet (PoE) port is greater than the allocation power, the hardware interface limit, the user-configured maximum power, or the available power on this switch. [chars] is the interface.","No action is required."
"ILPOWER","5","ILPOWER_POWER_DENY","Interface [chars]: inline power denied.Note This message applies only to Catalyst 3750 and 3560 switches.","There is not enough power remaining in the switch to supply to the PoE port. [chars] is the interface.","Connect the powered device to an external AC power source."
"ILPOWER","5","ILPOWER_POWER_DENY","Interface [chars]:inline power deniedNote This message applies only to Catalyst 3550-24PWR switches.","The PoE request was denied because the switch does not have enough power left to support the request. [chars] is the interface number.","No action is required."
"ILPOWER","5","INVALID_IEEE_CLASS","Interface [chars]: has detected invalid IEEE class: [dec] device. Power denied Note This message applies only to Catalyst 3750 and 3560 switches.","The power device has an invalid class so that the switch is not supplying power to the device. [chars] is the interface name. [dec] is the class number of the device.","No action is required."
"ILPOWER","5","LINKDOWN_DISCONNECT","Interface [chars]: Link down disconnect. Note This message applies only to Catalyst 3750 and 3560 switches.","The powered device is no longer connected to the switch or that the connected powered device is being powered by an external AC power source. The switch is no longer providing power on the interface. [chars] is the interface.","No action is required."
"ILPOWER","5","POWER_GRANTED","Interface [chars]: Power granted.Note This message applies only to Catalyst 3750 and 3560 switches.","There is enough power available in the switch and that the switch is providing power to the interface. [chars] is the interface.","No action is required."
"ILPOWER","7","DETECT","Interface [chars]: Power Device detected:[chars].Note This message applies only to Catalyst 3750 and 3560 switches.","The switch has detected the attached powered device. The first [chars] is the interface. The second [chars] is the Cisco pre-standard powered device or the IEEE-compliant powered device.","No action is required."
"IMAGEMGR","6","AUTO_ADVISE_SW_INITIATED","Auto-advise-software process initiated for systems [bits: [hex]]. Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","Systems with incompatible software have been detected in the switch stack. Auto-advise software informs you when not all switches in the stack are running the same software version. The stack master then attempts to upgrade all switches running different versions to the version that the master is running. The stack finds out whether or not software is available to be copied to the incompatible systems and if so, advises you how to copy it. Otherwise, the system informs you that the software on the switch stack needs to be updated. [bits [hex]] is the bit representation of the switch number.","No action is required."
"IMAGEMGR","6","AUTO_ADVISE_SW","[chars]. Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","A line of output from the auto-advise-software process is being displayed. [chars] is a text message reporting status of the upgrade process.","No action is required."
"IMAGEMGR","6","AUTO_COPY_SW_INITIATED","Auto-copy-software process initiated for systems [bits: [hex]]. Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","Systems with incompatible software have been detected in the switch stack. The stack now finds out whether or not software is available to be copied to the incompatible systems and whether or not it is appropriate to automatically copy the software. [bits [hex]] is the bit representation of the switch number.","No action is required."
"IMAGEMGR","6","AUTO_COPY_SW","[chars]. Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","A line of output from the auto-copy-software process is being displayed. [chars] is a text message reporting status of the upgrade process.","No action is required."
"IMAGEMGR","6","AUTO_DOWNLOAD_SW_INITIATED","Auto-download-software process initiated for systems [bits: [hex]]. Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","Systems with incompatible software have been detected in the switch stack. The stack now attempts to download software from a previously configured location and to install it to make the systems compatible. [bits [hex]] is the bit representation of the switch number.","No action is required."
"IMAGEMGR","6","AUTO_DOWNLOAD_SW","[chars]. Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","A line of output from the auto-download-software process is being displayed. [chars] is a text message reporting the status of the upgrade process.","No action is required."
"IP","3","SBINIT","Error initializing [chars] subblock data structure. [chars]","The subblock data structure was not initialized. [chars] is the structure identifier.","No action is required."
"IP_DEVICE_TRACKING_HA","4","ENTRY_OUT_OF_SYNC","Host mac-address [enet] ip-address [IP_address] interface [chars]","The IP device tracking table has detected an inconsistency between active and standby for this host. [enet] is the host MAC address, [IP_address] is the host IP address, and [chars] is the interface.","No action is required."
"KEYMAN","4","KEYSTR_CRYPTO_TYPE","Type [dec] encryption unknown.  Interpreting keystring as literal","The format type is not recognized by the system. The unrecognized format type is either a keystring format type value of 0 (unencrypted keystring) or 7 (hidden keystring). [dec] is the public key type.","Use the correct format for the value type or remove the space following the value type."
"KEYMAN","4","KEYSTR_BAD_CRYPTO","Bad encrypted keystring for key id [dec].","The system could not decrypt an encrypted keystring. The keystring may have been corrupted during system configuration. [dec] is the key ID.","Reenter the keystring command and reconfigure the keystring."
"L2TM","3","ACCESS_ERR","TCAM access failed while [chars].Note This message applies only to Catalyst 3550 switches.","The software did not read from or write to the TCAM. [chars] describes the part of the TCAM and the operation that failed.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section for more information."
"L2TM","7","INTERNAL_ERR","Internal error:[chars].Note This message applies only to Catalyst 3550 switches.","An internal error occurred. [chars] describes the internal operation that failed.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section for more information."
"L3TCAM","3","SIZE_CONFLICT","[chars] requires enabling extended routing.Note This message applies only to Catalyst 3550 switches.","The size of the Layer 3 unicast TCAM entry is not sufficient to implement a feature. [chars] is the feature name (either Web Cache Communication Protocol [WCCP] or multiple VPN routing/forwarding [multi-VRF]) that requires the 144-bit TCAM size.","Modify the Switch Database Management (SDM) template to enable the switch to support the 144-bit Layer 3 TCAM. Use the sdm prefer extended-match, sdm prefer access extended-match, or sdm prefer routing extended-match global configuration command, and then reload the switch by using the reload privileged EXEC command."
"L3TCAM","3","TOO_MANY_VRF","Exceed the maximum number of VRF allowed.Note This message applies only to Catalyst 3550 switches.","The number of virtual private networks (VPNs) exceeds the number allowed by the VPN routing/forwarding table on this hardware platform.","Reconfigure your switch to limit the number of VRFs. Do not define (name) more than seven VRFs with the ip vrf vrf-name global configuration command."
"L3TCAM","4","WCCP_ENABLE","Both VRF and WCCP are enabled, please remove either WCCP or VRF configuration.Note This message applies only to Catalyst 3550 switches.","The switch does not support enabling of both VRF and WCCP.","Reconfigure your switch to use either VRF or WCCP."
"MAB","5","FAIL","Authentication failed for client ([chars]) on Interface [chars] AuditSessionID [chars]","Authentication was unsuccessful. The first [chars] is the client, the second [chars] is the interface, and the third [chars] is the session ID.","No action is required."
"MAB","5","SUCCESS","Authentication successful for client ([chars]) on Interface [chars] AuditSessionID [chars]","Authentication was successful. The first [chars] is the client, the second [chars] is the interface, and the third [chars] is the session ID.","No action is required."
"MAC_LIMIT","4","DROP","Vlan [dec] with Configured limit = [dec] has currently [dec] Entries. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The number of MAC address table entries for a VLAN is less than or equal to the maximum number allowed. The first [dec] is the VLAN ID, the second [dec] is the maximum number of MAC address entries, and the third [dec] is the number of entries in the MAC address table.","Your system administrator configures an action."
"MAC_LIMIT","4","ENFORCE","Enforcing limit on Vlan [dec] with Configured limit = [dec]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The number of MAC address entries for the VLAN exceeds the maximum number allowed. The configured action is to limit the number of entries to the maximum allowed. The first [dec] is the VLAN ID, and the second [dec] is the maximum number of MAC address entries.","Your system administrator configures an action."
"MAC_LIMIT","4","EXCEED","Vlan [dec] with Configured limit = [dec] has currently [dec] Entries. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The number of MAC address entries for a VLAN exceeds the maximum number allowed. The first [dec] is the VLAN ID, the second [dec] is the maximum number of MAC address entries, and the third [dec] is the number of entries in the MAC address table.","Your system administrator configures an action."
"MAC_MOVE","4","NOTIF","Host [enet] in vlan [dec] is flapping between port [chars] and port [chars]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The host is moving between the specified ports. [enet] is the Ethernet address of the host, [dec] is the VLAN ID, the first [chars] is the first port, and the second [chars] is the second port.","Check your network for loops."
"NETWORK_PORT_SATELLITE","3","PHY_LOCKUP","Repeated phy lockup seen on [chars]. Interface will be shut down. Note This message applies only to Catalyst 3550 switches.","PHY lockup was detected too many times in a row. The interface is shut down to avoid continuous link flapping.","To re-enable the interface, use the shutdown interface configuration command, followed by the no shutdown interface configuration command."
"NETWORK_PORT_SATELLITE","6","MAC_LOCKUP","Transmit lock up is detected in [chars]. This port is administratively down.Note This message applies only to Catalyst 3550 switches.","When the PHY is powered on and off, the MAC cycles from 1000 to 100 Mb/s, and the port might lock up and stop sending packets. The PHY refers to the physical layer device on the switch, which sends and receives optical signals and provides framing and line integrity. [chars] is the interface name.","Shut down the port by using the shutdown interface configuration command, and bring it back up by using the no shutdown interface configuration command."
"PAGP_DUAL_ACTIVE","3","OBJECT_CREATE_FAILED","Unable to create [chars]","The switch cannot create the specified managed object. [chars] is the object name.","No action is required."
"PAGP_DUAL_ACTIVE","3","RECOVERY_TRIGGER","PAgP running on [chars] informing virtual switches of dual-active: new active id [enet], old id [enet]","PAgP received a new active ID on the specified interface, which means that all virtual switches are in a dual-active scenario. The interface is informing virtual switches of this, which causes one switch to go into recovery mode. [chars] is the interface, the first [enet] is the new active ID, and the second [enet] is the ID that it replaces.","No action is required."
"PAGP_DUAL_ACTIVE","3","REGISTRY_ADD_ERR","Failure in adding to [chars] registry","The switch could not add a function to the registry. [chars] is the registry name.","No action is required."
"PBR","2","NO_RMAP","Cannot create PBR data structures for route-map [chars] Note This message applies only to Catalyst 3550 switches.","The PBR manager could not allocate the data structures needed to describe a route map being used for policy routing. This was probably caused by lack of available memory. [chars] is a value that is applied by using the route-map interface configuration command.","Use a less-complicated configuration that requires less memory."
"PBR","3","NO_LABEL","Cannot allocate label for route-map [chars] Note This message applies only to Catalyst 3550 switches.","The PBR manager could not allocate a label for this route map. This means that the hardware cannot be programmed to implement policy routing. There is a limit of 247 labels for policy routing. [chars] is a value that is applied by using applied the route-map interface configuration command.","Use a less complicated configuration that allows label sharing. If possible, use the same route maps on multiple interfaces."
"PBR","3","MERGE_FAIL","[chars] ACL merge error [dec] on route-map [chars] Note This message applies only to Catalyst 3550 switches.","The PBR manager could not complete the merge of the configured route map into a form suitable for loading into the hardware. The most likely cause is specifying an access control list (ACL) that is too large or too complex for the system to handle. The first [chars] is the module or feature name, and the second [chars] is a value that is applied by using the route-map interface configuration command. [dec] is an internal error code.","Specify a smaller and less-complicated configuration."
"PBR","3","UNSUPPORTED_RMAP","Route-map [chars] not supported for Policy-Based Routing Note This message applies only to Catalyst 3550 switches.","The route map attached to an interface for policy routing contains an action that is not supported on this platform. This is a hardware limitation. [chars] is a value that is applied by using the route-map interface configuration command.","Reconfigure the route map. Use only permit entries and set ip next-hop action in the route map."
"PBR","4","CPU_SUPPORTED_ACTION","Set action in sequence [dec] of route-map [chars] supported by forwarding to CPU. Note This message applies only to Catalyst 3550 switches.","The route map attached to an interface for policy routing contains an action that is not supported in hardware because it contains set interface, set ip default next-hop, set default interface or set ip df actions. The packets must be forwarded by the CPU. [dec] and [chars] are values that are applied by using the route-map interface configuration command.","Reconfigure the route map. If possible, use only set ip next-hop in the route map."
"PBR","3","INSTALL_FAIL","Policy route-map [chars] not installed in hardware Note This message applies only to Catalyst 3550 switches.","The PBR manager could not install the complete route map in the hardware, so this will have to be applied in software. The packets must be forwarded by the CPU. [chars] is a value that is applied by using the route-map interface configuration command.","Reconfigure the route map to use a simpler configuration. If possible, use the same route map on multiple interfaces."
"PBR","4","RETRY_INSTALL","Route-map [chars] installed in hardware upon retry Note This message applies only to Catalyst 3550 switches.","The PBR manager was able to fit the complete configuration into the hardware. One or more route maps had previously not been loaded because of lack of space. [chars] is a value that is applied by using the route-map interface configuration command.","No action is required."
"PHY","4","BADTRANSCEIVER","An inappropriate transceiver has been inserted in interface [chars]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","A transceiver that should not be used is in the specified interface.","Remove the transceiver. If the transceiver is a Cisco device, contact your Cisco technical support representative."
"PHY","4","CHECK_SUM_FAILED","SFP EEPROM data check sum failed for SFP interface [chars].Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The SFP module was identified as a Cisco SFP module, but the system cannot read the vendor data information to verify whether it is correct. [chars] is the interface in which the SFP module is installed.","Remove and then reinsert the SFP module. If it fails again with the same error message, the SFP module might be defective."
"PHY","4","EXCESSIVE_ERRORS","Excessive FCS, data, or idle word errors found on interface [chars].Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The system detected excessive frame check sequence (FCS), data word, or idle word errors on the specified interface. [chars] is the interface.","Enter the show interface privileged EXEC command on the specified interface, and check for cyclic redundancy check (CRC) and other input errors. If errors are excessive, enter the shutdown interface configuration command and then the no shutdown interface configuration command to reset the interface."
"PHY","4","MODULE_DUP","SFPs in [chars] and in [chars] have duplicate vendor-id and serial numbers.","The SFP module was identified as a Cisco SFP module, but its vendor ID and serial number match that of another SFP module in the system. The first [chars] is the interface in which the SFP module is installed, the second [chars] is the interface where the duplicate SFP module is installed.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PHY","4","SFP_NOT_SUPPORTED","The SFP in [chars] is not supported Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","This SFP module is not supported on this switch. [chars] is the interface.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PHY","4","UNSUPPORTED_SFP_CARRIER","Unsupported SFP carrier module found in [chars]","The SFP carrier module was identified as an unsupported, non-Cisco SFP carrier module. [chars] is the unsupported module.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PHY","4","UNSUPPORTED_TRANSCEIVER","Unsupported transceiver found in [chars]Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The SFP module was identified as an unsupported, non-Cisco SFP module. [chars] is the unsupported module.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section on page 1-5."
"PIMSN","6","IGMPSN_GLOBAL","PIM Snooping global runtime mode [chars] due to IGMP Snooping [chars]. Note This message applies only to Catalyst 3750 and 3560 switches.","When IGMP snooping is disabled, PIM snooping is disabled. When IGMP snooping is re-enabled, PIM snooping is re-enabled. The first [chars] is the PIM snooping mode, and the second [chars] is the IGMP snooping mode.","No action is required."
"PIMSN","6","IGMPSN_VLAN","PIM Snooping runtime mode on vlan [dec] [chars] due to IGMP Snooping [chars]. Note This message applies only to Catalyst 3750 and 3560 switches.","When IGMP snooping is disabled, PIM snooping is disabled. When IGMP snooping is re-enabled, PIM snooping is re-enabled. [dec] is the VLAN ID, the first [chars] is the PIM snooping mode, and the second [chars] is the IGMP snooping mode.","No action is required."
"PLATFORM","1","CRASHED","[chars]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The system is trying to display the error message that appeared when the switch failed in a previous instance. [chars] is the description of the error message.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM","3","PHYFWDOWNLOAD_FAILED","Phy Firmware download failed for [chars] Hotswap the Frulink module or use cli to reboot the Frulink.","The firmware download to the PHY device has failed. [chars] is the interface name.","No action is required."
"PLATFORM","3","NO_HARDWARE_RESOURCES","Not enough hardware resources. Shutting down [chars].Note This message applies only to Catalyst 3750 and 3560 switches.","There are too many VLANs and routed ports. [chars] is the short interface name, such as Gi1/0/1, or the VLAN name, such as VLAN0002.","Reduce the total number of VLANs and routed ports to less than 1023. To preserve configurations and connections across reboots, save the configuration."
"PLATFORM","3","PW_REC_HRPC_BAD_LENGTH","Received incompatible length (=[dec]) in set-password-recovery HRPC message from box [dec]. Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","The system received an incompatible length parameter in the set-password-recovery HRPC message. This can be caused by a stack operating with incompatible software versions on different stack members. The first [dec] is the length and the second [dec] is the switch.","Make sure that all stack members are running compatible software images. If the problem persists, find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM","3","PW_REC_HRPC_NOT_ON_MASTER","Set-password-recovery HRPC msg from box [dec] received on master.Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","The stack master received a set-password-recovery HRPC message. These messages should be received only on stack member switches. [dec] is the switch.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM","3","PW_REC_HRPC_ONLY_ON_MASTER","Get-password-recovery HRPC msg from box [dec] received on member.Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","A stack member switch received a get-password-recovery HRPC message. These messages should only be received by the stack master. [dec] is the switch.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM","6","FLEXSTACK_INSERTED","FlexStack module inserted [chars]Note This message applies only to Catalyst 2960-S switches.","The switch has detected a FlexStack module. [chars] is the slot.","No action is required."
"PLATFORM","6","FLEXSTACK_REMOVED","FlexStack module removed [chars]Note This message applies only to Catalyst 2960-S switches.","The switch has detected that a FlexStack module has been removed. [chars] is the slot.","No action is required."
"PLATFORM_ENV","1","PWR_LOPWR","Switch is operating in low power mode, switch is not fully operational. Current power source is [chars]","The switch does not have enough power to power up the ports. [chars] is the interface name.","Connect a Type2 capable power source to both the uplink PD ports."
"PLATFORM_ENV","1","PWR_NONOPTIMAL","Switch is fully operational but in non-optimal mode. Current power source is [chars]","The switch could change into low power mode on loss of the Type1 power supply. [chars] is the interface name.","Make sure both the uplink ports are connected to a Type2 capable power source."
"PLATFORM_ENV","6","PWR_OPTIMAL","Switch is fully operational. Current power source is [chars]","The switch is fully operational in optimal mode. [chars] is the interface name.","No action is required."
"PLATFORM_ENV","6","RPS_PRESENCE","Redundant Power Supply(RPS) [chars]","The Redundant Power Supply (RPS) changed state. [chars] is what was added or removed.","No action is required."
"PLATFORM_FBM","4","RECOVERED","Fallback bridging recovered from resource crunch. Note This message applies only to Catalyst 3750 and 3560 switches.","Fallback bridging has recovered from an earlier lack of resources.","No action is required."
"PLATFORM_FBM","4","RESOURCE_CRUNCH","Fallback bridging on bridge-group [dec] is experiencing a resource crunch. One or more bridge-groups may not be functional. It will recover automatically when system recovers from resource crunch. Delete the bridge-group to immediately recover. Note This message applies only to Catalyst 3750 and 3560 switches.","Fallback bridging could not be properly configured. The most likely cause is a TCAM-full condition on at least one stack member. [dec] is the bridge-group.","The switch automatically recovers, but this could take some time. For an immediate recovery, use the shutdown interface configuration command to disable the port and stop the traffic flow to the switch. Use the clear mac-address-table dynamic privileged EXEC command to remove all MAC addresses from the TCAM. Use the no shutdown interface configuration command to re-enable the port."
"PLATFORM_SM10G","3","HARDWARE","FRULink 10G Service Module (C3KX-SM-10G) features are not supported on this revision of switch hardware. Please upgrade the switch hardware to use the module's features.","The current switch hardware version does not support the features of the module.","Upgrade the switch hardware to support the features of the module."
"PLATFORM_SM10G","3","NO_RESPONSE","The FRULink 10G Service Module (C3KX-SM-10G) is not responding.","The device is not responding. This could be due to hardware or software failure or a module reload.","Reboot or replace the module."
"PLATFORM_SM10G","3","AUTHENTICATION,","The FRULink 10G Service Module (C3KX-SM-10G) may not have been entirely manufactured by Cisco. Module is in pass-through mode.","Apart of the module's hardware could not be verified as official Cisco hardware. Extended services and features are disabled and the module will only operate in pass-thru mode.","Contact your Cisco technical support representative and replace the module."
"PLATFORM_SM10G","3","SW_VERSION_MISMATCH","The FRULink 10G Service Module (C3KX-SM-10G) in switch <switch-number> has a software version that is incompatible with the IOS software version. Please update the software. Module is in pass-thru mode.","The IOS and FRULink 10G service module software are incompatible.","Upgrade the software."
"PLATFORM_SM10G","3","FPGA_UPDATE_INITIATED","The FRULink 10G Service Module (C3KX-SM-10G) firmware is being updated due to a version mismatch. Please wait a few minutes for the update to complete.","The firmware is corrupted and needs to be restored.","Wait for the update to complete."
"PLATFORM_SM10G","3","FPGA_RELOADED","The FRULink 10G Service Module (C3KX-SM-10G) firmware has been updated and the module will be reloaded","The firmware is corrupted and has been restored","Upgrade the firmware."
"PLATFORM_SM10G","3","FPGA_RELOAD_FAILED","The FRULink 10G Service Module (C3KX-SM-10G) firmware could not be updated.","The firmware image is corrupted and could not be restored","Contact your Cisco technical support representative and replace the module."
"PLATFORM_SM10G","3","CORRUPT_SW_IMAGE","The FRULink 10G Service Module (C3KX-SM-10G) software version is corrupted. Please update the software. Module is in pass-thru mode.","The FRULink 10G Service Module software is invalid.","Update the software."
"PLATFORM_SM10G","6","LINK_UP","The FRULink 10G Service Module (C3KX-SM-10G) communication has been established.","Communication is established with the FRULink 10G service module.","No actions is required."
"PLATFORM_SM10G","6","LICENSE","FRULink 10G Service Module (C3KX-SM-10G) features are not supported with this license level. Module is in pass-thru mode.","The services and features of the module require an IPBASE or IPSERVICES license level. If the necessary license is not installed and activated, then the module operates only in the pass-through mode.","Install and activate an IPBASE or IPSERVICES license."
"PLATFORM_HCEF","3","ADJ","[chars]Note This message applies only to the Catalyst 3750 and 3560 switches.","An unsupported feature was configured on a switch running Cisco IOS Release 12.2(25)SE. [chars] is the error message.","Determine if a generic routing encapsulation (GRE) tunnel or the ip cef accounting global configuration command are configured. Only Distance Vector Multicast Routing Protocol (DVMRP) tunnels are supported. If the GRE tunnel is configured, remove the tunnel, or upgrade the switch software to a Cisco IOS release when the GRE feature is needed. If the ip cef accounting command is configured, remove it by using the no ip cef accounting global configuration command."
"PLATFORM_HPLM","3","ERROR","Failed Alloc for action record label move from [dec] to [dec].Note This message applies only to Catalyst 3750 and 3560 switches.","An internal resource allocation error occurred during the label compaction process. The first [dec] is the previous label, and the second [dec] is the new label.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM_HPLM","6","LABEL_COMPLETE","VRF Label compaction complete.Note This message applies only to Catalyst 3750 and 3560 switches.","The VRF label compaction process has successfully completed.","No action is required."
"PLATFORM_HPLM","6","LABEL_FAILED","VRF Label compaction failed.Note This message applies only to Catalyst 3750 and 3560 switches.","The VRF label compaction process has failed.","No action is required."
"PLATFORM_HPLM","6","LABEL_START","VRF Label compaction started.Note This message applies only to Catalyst 3750 and 3560 switches.","The VRF label compaction process has started.","No action is required."
"PLATFORM_IPC","3","COMMON","[chars]. Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","The IPC has failed. [chars] describes the error message.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM_IPC","3","MASTER","[chars]. Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","The IPC has failed on the stack master. [chars] describes the error message.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM_IPC","3","MAX_LENGTH_EXCEEDED","[chars]. Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","An internal IPC application error occurred when an IPC message was sent that exceeded the maximum length. [chars] describes the error message.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM_IPC","3","MEMBER","[chars]. Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","The IPC has failed on a stack member switch. [chars] describes the error message.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM_IPC","3","STACK_EVENT","[chars]. Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","The IPC has failed in the stack. [chars] describes the error message.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM_IPv6_UCAST","6","PREFIX","One or more, more specific prefixes could not be programmed into TCAM and are being covered by a less specific prefixNote This message applies only to Catalyst 3750, 3560, 2975, and 2960 switches.","A more specific prefix could not be programmed into TCAM and is covered by a less specific prefix. This could be a temporary condition. The output of the show platform ipv6 unicast retry route privileged EXEC command lists the failed prefixes.","No action is required."
"PLATFORM_PBR","2","NO_RMAP","Cannot create PBR data structures for route-map [chars]. Note This message applies only to Catalyst 3750 and 3560 switches.","The PBR manager could not allocate the internal data structures for this route-map. A likely cause is lack of available memory. [chars] is the route-map.","Simplify the configuration so that it requires less memory."
"PLATFORM_PBR","3","INSTALL_FAIL","Policy route-map [chars] not installed in hardware.Note This message applies only to Catalyst 3750 and 3560 switches.","The PBR manager could not install the complete route-map in hardware, so the packets are forwarded to the CPU for processing. [chars] is the route-map.","Simplify route-map configurations. For example, use the same route-map on multiple interfaces."
"PLATFORM_PBR","3","NO_LABEL","Cannot allocate label for route-map [chars].Note This message applies only to Catalyst 3750 and 3560 switches.","The PBR manager could not allocate a label for this route-map. As a result, the hardware cannot be programmed to implement policy routing. There is a limit of 247 labels for policy routing. [chars] is the route-map.","Simplify the configuration with label sharing. Use the same route-maps on multiple interfaces, if possible."
"PLATFORM_PBR","3","UNSUPPORTED_RMAP","Route-map [chars] not supported for Policy-Based Routing. Note This message applies only to Catalyst 3750 and 3560 switches.","The route-map attached to an interface for policy routing contains an action that is not supported on this platform. This is a hardware limitation. [chars] is the route-map.","Use the route-map map-tag permit global configuration command and the set ip next-hop ip-address route-map configuration command to reconfigure the route map to use only these supported actions."
"PLATFORM_PBR","4","CPU_SUPPORTED_ACTION","Set action in sequence [dec] of route-map [chars] supported by forwarding to CPU. Note This message applies only to Catalyst 3750 and 3560 switches.","The route-map attached to an interface for policy-based routing contains an action that is not supported in hardware, so the packets are forwarded to the CPU for processing. The route-map actions that invoke this forwarding are set interface, set ip default next-hop, set default interface, or set ip df. [dec] is the action number, and [chars] is the route-map.","Use the set ip next-hop ip-address route-map configuration command to reconfigure the route map action to route the packet to the specified next hop."
"PLATFORM_PBR","4","RETRY_INSTALL","Route-map [chars] installed in hardware upon retry. Note This message applies only to Catalyst 3750 and 3560 switches.","The PBR manager was able to fit the complete configuration into the hardware. One or more route-maps previously did not load because of lack of resources. [chars] is the route-map.","No action is required."
"PLATFORM_PBR","4","SDM_MISMATCH","[chars] requires sdm template routing. Note This message applies only to Catalyst 3750 and 3560 switches.","The routing template is not enabled. [chars] is the text string PBR.","Modify the SDM template to enable the routing template. Use the sdm prefer routing configuration command, and then reload the switch by using the reload privileged EXEC command."
"PLATFORM_PM","3","IFCOUNTERROR","Unit number [dec] of interface [chars] is more than max allowed value of [dec].","There are too many interfaces configured for the interface type. [dec] is the interface count, [chars] is the interface, and [dec] is the maximum number of interfaces.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM_PM","3","INTVLANINUSE","internal vlan-id [dec] allocated for interface [chars] is still in use.","An internal VLAN ID allocated for an interface is still in use. [dec] is the VLAN ID, and [chars] is the interface.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM_PM","3","NOINTVLAN","internal vlan of interface [chars] is not active for vlan-id [dec].","The internal vlan_data is not active for the given VLAN ID. [chars] is the interface, and [dec] is the VLAN ID.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM_RPC","0","RESOURCE_CRASH","[chars]. Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","The system cannot allocate memory for RPC. [chars] describes the error message.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM_RPC","3","BAD_CLASS","Bad Class in RPC message: [int]. Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","There is a missing entry in the class table for a message class. [int] is the number of the missing message class.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM_RPC","3","MSG_THROTTLED","RPC Msg Dropped by throttle mechanism: type [int], class [int], max_msg [int], total throttled [int]. Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","There are too many outgoing messages queued for a message class. An RSP message was dropped. The first [int] is the message type, the second [int] is the message class, the third [int] is the maximum number of messages that can be queued before throttling occurs, and the last [int] is the total number of messages that have been throttled.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM_RPC","3","PERSISTENT_UNABLE_TO_SEND","System is consistently unable to send RPC message: [chars], paks_outstanding: [int]. Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","The system is experiencing a persistent low-level transport failure in sending RPC messages. [chars] is a description of the error returned by the low-level packet-sending driver that triggered the error (usually one of these: fifo full, fifo empty, out of buf, out of mem, null pointer, misc failure), and [int] is the number of packets outstanding (packets from the RPC code to the driver that have not yet been sent).","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM_RPC","3","RESP_FAIL","Unexpected response or failure, class [dec], req [dec], switch [dec], error [dec], [chars]. Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","The platform received an unexpected response. The first [dec] is RPC request class, the second [dec] is the RPC request number, the third [dec] is the destination switch number, the fourth [dec] is the returned error number, and [chars] is an optional comment.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM_RPC","3","SEND_FAIL","Failed to send RPC message in class [dec], req [dec], [chars]. Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","There is a local resource error or that too many outgoing messages are queued for the message class. The first [dec] is RPC request class, the second [dec] is the RPC request number, and [chars] is an optional comment.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM_RPC","3","UNABLE_TO_SEND","System is unable to send RPC message: [chars], paks_outstanding: [int]. Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","The system had a low-level transport failure when trying to send an RPC message. [chars] is a description of the error returned by the low-level packet sending driver that triggered the error (usually one of these: fifo full, fifo empty, out of buf, out of mem, null pointer, misc failure), and [int] is the number of packets outstanding (packets from the RPC code to the driver that have not yet been sent).","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM_SPAN","3","PACKET_DROP","Decreases egress SPAN rate.Note This message applies only to Catalyst 3750 and 3560 switches.","SPAN rates are falling because SPAN (egress or both egress and ingress) is enabled with multicast routing or fallback bridging.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM_UCAST","3","ADJ","[chars].Note This message applies only to Catalyst 3750 and 3560 switches.","The adjacency module for unicast routing encountered an error. [chars] describes the error.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM_UCAST","3","ARP","[chars].Note This message applies only to Catalyst 3750 and 3560 switches.","The ARP module for unicast routing encountered an error. [chars] describes the error.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM_UCAST","3","CEF","[chars].Note This message applies only to Catalyst 3750 and 3560 switches.","The Cisco Express Forwarding (CEF) module for unicast routing encountered an error. [chars] describes the error.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM_UCAST","3","DYNAMIC","[chars].Note This message applies only to Catalyst 3750 and 3560 switches.","The dynamic address tracking mechanism for unicast routing encountered an error. [chars] describes the error.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM_UCAST","3","ERROR","[chars].Note This message applies only to Catalyst 3750 and 3560 switches.","An internal unicast routing error occurred. [chars] describes the error.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM_UCAST","3","HSRP","[chars].Note This message applies only to Catalyst 3750 and 3560 switches.","The Hot Standby Router Protocol (HSRP) module for unicast routing encountered an error. [chars] describes the error.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM_UCAST","3","INTERFACE","[chars]. Note This message applies only to Catalyst 3750 and 3560 switches.","A unicast routing interface error occurred. [chars] describes the error.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM_UCAST","3","RPC","[chars].Note This message applies only to Catalyst 3750 and 3560 switches.","The RPC module for unicast routing encountered an error. [chars] describes the error.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM_UCAST","6","PREFIX","One or more, more specific prefixes could not be programmed into TCAM and are being covered by a less specific prefixNote This message applies only to Catalyst 3750 and 3560 switches.","A more specific prefix could not be programmed into TCAM (due to insufficient memory) and is covered by a less specific prefix. This could be a temporary condition. The output of the show platform ip unicast failed route privileged EXEC command lists the failed prefixes. This may cause software forwarding.","Check the TCAM utilization and compare the values to the SDM template in use. You may need to change the SDM template to one that is more suitable for the current device."
"PLATFORM_VLAN","3","LOCK_FAIL","Failed to lock vlan-id [dec], associated mapped vlan id value [dec].","The VLAN lock operation failed. This can occur if the VLAN is already active in the system or if the VLAN ID is not active. The first [dec] is the VLAN ID, and the second [dec] is the mapped-vlan-id (MVID).","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM_VLAN","3","MVID_ERROR","Mapped Vlan ID value [dec] associated with vlan-id [dec] is invalid.","An active VLAN is not correctly associated with a MVID. The first [dec] is the VLAN ID, and the second [dec] is the MVID.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM_VLAN","3","UNLOCK_FAIL","Failed to unlock vlan-id [dec], associated mapped vlan id value [dec].","The switch did not unlock a VLAN ID. The most likely cause is that the VLAN is already unlocked. The first [dec] is the VLAN ID, and the second [dec] is the MVID.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PLATFORM-WCCP","3","NO_LABEL","Cannot allocate WCCP LabelNote This message applies only to Catalyst 3750 and 3560 switches.","The WCCP label could not be allocated. This means that the hardware cannot be programmed to implement WCCP redirection.","Reduce the number of interfaces configured for WCCP redirection or policy based routing."
"PLATFORM_WCCP","4","SDM_MISMATCH","WCCP requires sdm template routingNote This message applies only to Catalyst 3750 and 3560 switches.","The SDM routing template is not specified on the switch.","Specify the SDM routing template to be used. Enter the sdm prefer routing global configuration command, and then enter the reload privileged EXEC command to reload the switch."
"PM","2","LOW_SP_MEM","Switch process available memory is less than [dec] bytes. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The available memory for the switch processor is low. This can occur when too many Layer 2 VLANs are configured. [dec] is the available memory.","Remove VLANs from the system to reduce memory usage."
"PM","2","NOMEM","Not enough memory available for [chars].","The port manager subsystem could not obtain the memory it needed to initialize the specified operation. [chars] is the port manager operation.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PM","2","VLAN_ADD","Failed to add VLAN [dec] - [chars].","The software did not add the VLAN to the VLAN Trunking Protocol (VTP) database. [dec] is the VLAN ID, and [chars] specifies the reason the software did not add the VLAN.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PM","3","INTERNALERROR","Port Manager Internal Software Error ([chars]: [chars]: [dec]: [chars]).","An internal software error occurred in the port manager. The parameters identify the problem for technical support. The first [chars] is the error message, and the second [chars] is the filename. [dec] is the line number, and the last [chars] is the function name.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PM","4","BAD_APP_ID","an invalid application id ([dec]) was detected.","The port manager detected an invalid request. [dec] is the application ID.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PM","4","BAD_APP_REQ","an invalid [chars] request by the '[chars]' application was detected.","The port manager detected an invalid request. The first [chars] is the invalid request, and the second [chars] is the application making the request.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PM","4","BAD_CARD_COOKIE","an invalid card cookie was detected.","The port manager detected an invalid request.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PM","4","BAD_CARD_SLOT","an invalid card slot ([dec]) was detected.","The port manager detected an invalid request. [dec] is the slot number.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PM","4","BAD_COOKIE","[chars] was detected.","The port manager detected an invalid request. [chars] is the invalid request.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PM","4","BAD_HA_ENTRY_EVENT","Invalid Host access entry event ([dec]) is received.","An invalid host access entry event was received. The host access table entry event should be an add, delete, or update event. [dec] is the event that is received.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PM","4","BAD_PORT_COOKIE","an invalid port cookie was detected.","The port manager detected an invalid request.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PM","4","BAD_PORT_NUMBER","an invalid port number ([dec]) was detected.","The port manager detected an invalid request. [dec] is the port number.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PM","4","BAD_VLAN_COOKIE","an invalid vlan cookie was detected.","The port manager detected an invalid request.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PM","4","BAD_VLAN_ID","an invalid vlan id ([dec]) was detected.","The port manager detected an invalid request. [dec] is the VLAN ID.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PM","4","ERR_DISABLE","[chars] error detected on [chars], putting [chars] in err-disable state.","The port manager detected a misconfiguration or misbehavior and error-disabled the interface. A recovery is attempted after the configured retry time (the default is 5 minutes). On PoE switches, this message might appear when a device that can be powered by either a PoE switch port or by AC power is not being powered by an external AC power source and is connected to a port that has been configured with the power inline never interface configuration command. [chars] is the port where the threshold was exceeded. The first [chars] is the error, and both the second and third [chars] are the affected interface.","On non-PoE switches, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Enter the show tech-support user EXEC command to gather data that might help identify the nature of the error. Use the Bug Toolkit to look for similar reported problems. On PoE switches, remove the device or configure the port by entering the power inline auto, shutdown, and no shutdown interface configuration commands. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PM","4","ERR_DISABLE_VP","[chars] error detected on [chars], vlan [dec].  Putting in err-disable state.","The virtual port (the port-VLAN pair) is error-disabled when it detects a misconfiguration or misbehavior. If configured, a recovery will be attempted after the configured retry time (default time is 5 minutes). The first [chars] is the error, and the second [chars] is the port.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PM","4","ERR_RECOVER","Attempting to recover from [chars] err-disable state on [chars].","The port manager is trying to restart an error-disabled interface. The first [chars] is the error, and the second [chars] is the interface.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PM","4","ERR_RECOVER_VP","Attempting to recover from [chars] err-disable state on [chars], vlan [dec].","The port manager is trying to restart an error-disabled virtual port. The first [chars] is the error, the second [chars] is the virtual port, and [dec] is the VLAN ID.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PM","4","EXT_VLAN_INUSE","VLAN [dec] currently in use by [chars].","The port manager did not allocate the VLAN for external use because the VLAN is being used by another feature. [dec] is the VLAN that is being used, and [chars] is the feature that is using it.","Reconfigure the feature (for example, the routed port) to use another internal VLAN or to request another available VLAN."
"PM","4","EXT_VLAN_NOTAVAIL","VLAN [dec] not available in Port Manager.","The port manager did not allocate the requested VLAN. The VLAN is probably being used as an internal VLAN by other features. [dec] is the requested VLAN.","Configure a different VLAN on the device."
"PM","4","INACTIVE","putting [chars] in inactive state because [chars].","The port is inactive because the port manager could not create a virtual port for the switch port and VLAN. The reason for this condition is specified in the error message. The first [chars] is the interface name, and the second [chars] is the reason.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PM","4","INT_FAILUP","[chars] failed to come up. No internal VLAN available.","The port manager did not allocate an internal VLAN. The interface cannot be enabled. [chars] is the interface name.","Remove the extended-range VLAN by using the no vlan vlan-id global configuration command to free up resources."
"PM","4","INT_VLAN_NOTAVAIL","Failed to allocate internal VLAN in Port Manager.","The port manager did not find any available internal VLAN.","Delete some extended-range VLANs created by users, or remove some features (such as routed ports) that require internal VLAN allocation. To delete extended-range VLANs, use the no vlan vlan-id global configuration command. To delete a routed port, use the no switchport interface configuration command."
"PM","4","INVALID_HOST_ACCESS_ENTRY","Invalid Host access entry type ([dec]) is received.","An invalid host access entry type was received. The host access entry should be a configured or a dynamic type. [dec] is the entry type that is received.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PM","4","LIMITS","The number of vlan-port instances on [chars] exceeded the recommended limit of [dec].","The total number of individual VLAN ports on the module or the switch has exceeded the recommended limit. VLANs can be counted more than once. If VLAN 1 is carried on ten interfaces, it counts as ten VLAN ports. On some platforms, bundling is also ignored for purposes of this count. If eight interfaces on the same module are in one bundle, and the port channel is carrying VLAN 1, it counts as eight VLAN ports. [chars] is the module name (for example, switch or the module number), and [dec] is the recommended limit.","Reduce the number of trunks and VLANs configured in the module or switch as recommended in [dec]. Enter the show interfaces trunk privileged EXEC command to see the total number of trunks and VLANs."
"PM","4","NO_SUBBLOCK","No PM subblock found for [chars].","The port manager did not find the subblock for this interface. [chars] is the interface name.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PM","4","PORT_BOUNCED","Port [chars] was bounced by [chars]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","During a change-over when the port was in the link-down state, the port manager restarted the port. A port can be restarted only when the port data structures are not consistent in the active and standby supervisors. Active ports in the link-down state return to the link-up state when the port is restarted. The first [chars] is the port number, and the second [chars] is the re-activation event.","No action is required."
"PM","4","PVLAN_TYPE_CFG_ERR","Failed to set VLAN [dec] to a [chars] VLAN.Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The platform did not set a private VLAN type. [dec] is the VLAN ID.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PM","4","TOO_MANY_APP","application '[chars]' exceeded registration limit.","The port manager detected an invalid request. [chars] is the application.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PM","4","UNKNOWN_HOST_ACCESS","Invalid Host access value ([dec]) is received.","The host access table is being accessed with an invalid host access value. [dec] is the value that is received.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PM","4","VMPS_CFG","Dynamic access VLAN [dec] same as voice vlan on [chars]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The access VLAN ID on the VMPS server is the same as the voice VLAN ID on the interface. [dec] is the access VLAN ID, and [chars] is the physical interface.","Assign the access VLAN on the VMPS server to a VLAN ID that is different from the voice VLAN ID."
"PM","6","EXT_VLAN_ADDITION","Extended VLAN is not allowed to be configured in VTP CLIENT mode.","The switch did not add a VLAN in VTP client mode.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"PORT_SECURITY","2","PSECURE_VIOLATION","Security violation occurred caused by MAC [enet] on port [chars].","An unauthorized device attempted to connect on a secure port. [enet] is the MAC address of the unauthorized device, and [chars] is the secure port.","Identify the device that attempted to connect on the secure port. Notify your network system administrator of this condition."
"PORT_SECURITY","2","PSECURE_VIOLATION_VLAN","Security violation on port [chars] due to MAC address [enet] on VLAN [dec]","An unauthorized device attempted to connect on a secure trunk port. [chars] is the secure port, [enet] is the MAC address of the unauthorized device, and [dec] is the VLAN ID.","Identify the device that attempted to connect through the secure trunk port. Notify your network system administrator of this condition."
"PORT_SECURITY","6","ADDR_REMOVED","Address [dec]:[enet] exists on port [chars]. It has been removed from port [chars].","A routed port is reconfigured as a switch port. The address in the previous switch configuration conflicts with the running configuration and has been deleted. [dec]:[enet] is the MAC address of the port, and [chars] is the reconfigured port.","No action is required."
"PORT_SECURITY","6","ADDRESSES_REMOVED","Maximum system secure address count reached. Some secure addresses configured on port [chars] removed.Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","Some configured and sticky MAC addresses on the specified port were removed from the configuration. The number of secure addresses that the system supports was exceeded. This condition occurs only during hot swapping or port-mode changes (for example, when the port is converted from a Layer 3 to a Layer 2 port). [chars] is the port.","No action is required."
"PORT_SECURITY","6","VLAN_FULL","Vlan [dec] on port [chars] has reached its limit. Address [enet] has been removed.","The voice VLAN is the same as the access VLAN. Because the maximum number of MAC addresses allowed on the access VLAN has been reached, the specified Ethernet address has been deleted. [dec] is the VLAN ID, [chars] is the port assigned to the voice VLAN and the access VLAN, and [enet] is the Ethernet address.","No action is required."
"PORT_SECURITY","6","VLAN_REMOVED","VLAN [dec] is no longer allowed on port [chars]. Its port security configuration has been removed.","A configured VLAN has been excluded either due to a port-mode change or an allowed VLAN list change and is removed from the configuration. [int] is the VLAN ID, and [chars] is the switch port assigned to the VLAN.","No action is required."
"POWERNET_ISSU","4","SM_EW_DOMAIN_MISMATCH","Energywise domain of EtherSwitch is [chars], recommended to have [chars].Note This message applies only to Cisco EtherSwitch service modules.","The EnergyWise domain of the service module does not match that of the switch. The first [chars] is the EnergyWise domain of the service module. The second [chars] is the EnergyWise domain of the router.","Configure the EnergyWise domain of the service module to match that of the switch. If the message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still need assistance, open a case with the TAC, or provide your Cisco technical support representative with your information."
"QATM","2","ASDATA_READ","Cannot read TCAM associated data.Note This message applies only to Catalyst 3550 switches.","Associated data could not be read from the TCAM. This error might mean a hardware failure.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section for more information."
"QATM","2","ASDATA_WRITE","Cannot write TCAM associated data.Note This message applies only to Catalyst 3550 switches.","Associated data could not be written to the TCAM. This error might mean a hardware failure.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section for more information."
"QATM","2","TCAM_READ","Cannot read TCAM.Note This message applies only to Catalyst 3550 switches.","The TCAM could not be read from. This error might mean a hardware failure.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section for more information."
"QATM","2","TCAM_WRITE","Cannot write the TCAM.Note This message applies only to Catalyst 3550 switches.","The TCAM could not be written to. This error might mean a hardware failure.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section for more information."
"QATM","4","TCAM_LOW","TCAM resource running low for table [chars], resource type [chars], on TCAM number [dec].Note This message applies only to Catalyst 3550 switches.","The TCAM resource is running low and might cause system instability. The first [chars] is the TCAM table, the second [chars] is the resource type, and [dec] is the TCAM number.","Avoid further configurations that might deplete the indicated TCAM resource type that is running low. Use the show tcam user EXEC command to display information about the input security access control list (ACL), the output security ACL, the QoS, or other regions of the TCAM, as shown in the message TCAM table. If possible, change to a different TCAM allocation by using the sdm prefer global configuration command to configure the template used in the SDM resource allocation."
"QM","4","ACTION_NOT_SUPPORTED","Action is not supported in policy map [chars].Note This message applies only to Catalyst 3550 switches.","An action other than the set, trust, and police policy-map class configuration commands was configured in a policy map. This is a hardware limitation. [chars] is the name of the policy map.","Configure only the supported actions of set, trust, and police when in policy-map class configuration mode."
"QM","4","CLASS_NOT_SUPPORTED","Classification is not supported in class map [chars].Note This message applies only to Catalyst 3550 switches.","An unsupported match class-map configuration command was configured in a policy map and attached to an egress interface or that more than one match command was configured. This is a hardware limitation. [chars] is the class-map name.","Reconfigure the class map or the policy map. Use only the match ip dscp dscp-list class-map configuration command in a policy map that is attached to an egress interface. Only one match per class map is supported."
"QM","4","HARDWARE_NOT_SUPPORTED","Hardware limitation has been reached for policy map [chars].Note This message applies only to Catalyst 3550 switches.","The policy-map configuration has exceeded the limitation of the hardware. You either configured more QoS ACL entries than the number specified in the Switch Database Management (sdm) template, or you configured more policers in a policy map (by using the police or police aggregate policy-map class configuration command) than supported. [chars] is the policy-map name.","Reconfigure the class map or the policy map, and reduce the number of QoS ACLs."
"QM","4","MATCH_NOT_SUPPORTED","Match type is not supported in class map [chars].Note This message applies only to Catalyst 3550 switches.","Only the access-group acl-index-or-name, ip dscp dscp-list, and ip precedence ip-precedence-list match types are supported with the match class-map configuration command. [chars] is the name of the class map.","Reconfigure the class map using only the match access-group, match ip dscp, and match ip precedence class-map configuration commands within the class map."
"QM","4","NOT_SUPPORTED","Action [chars] is not supported for a policy map attached to output side.Note This message applies only to Catalyst 3550 switches.","A set or trust policy-map class configuration command was configured in a policy map and attached to an egress interface. A warning message is logged, and the actions do not take affect. This is a hardware limitation. [chars] is either the set or trust action.","Do not configure a set or trust policy-map class configuration command in a policy map and attach it to an egress interface. These policy-map actions are supported only on ingress interfaces."
"QM","4","POLICER_NOT_SUPPORTED","Number of policers has exceeded hardware limitation for policy map [chars].Note This message applies only to Catalyst 3550 switches.","The policy-map configuration has exceeded the limitation of the hardware. You configured more policers in a policy map (by using the police or police aggregate policy-map class configuration command) than supported. [chars] is the policy-map name.","Reconfigure the class map or the policy map, and reduce the number of policers."
"QM","4","POLICING_RATE_NOT_SUPPORTED","Policer configuration has exceeded hardware limitation for policy map [chars].Note This message applies only to Catalyst 3550 switches.","The policy-map configuration has exceeded the limitation of the hardware. You configured a larger policing rate or burst size in a policy map (by using the police or police aggregate policy-map class configuration command) than supported. [chars] is the policy-map name.","Reconfigure the class map or the policy map, and reduce the policing rate or burst size."
"QM","4","UNEXPECTED_INTERNAL_QOS_CONDITION","Unexpected internal QoS condition.Note This message applies only to Catalyst 3550 switches.","An unexpected internal quality of service (QoS) condition has occurred. QoS debug can be enabled to obtain more information in case the condition recurs.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section for more information."
"QOSMGR","3","FEATURE_NOT_FOUND","Cannot find feature for [chars]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","An internal software error has occurred. [chars] is the description of the feature that the software cannot find.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"QOSMGR","3","FILTERTYPE_INVALID","Internal Error Invalid Policy filtertype [dec]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","An internal software error has occurred. [dec] is the invalid filter type identification.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"QOSMGR","3","MERGE_RES_COUNT","Internal Error Invalid count. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","An internal software error has occurred.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"QOSMGR","3","NO_POLICER_QOSLABEL","Creating port Class Label Failed. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","An internal software error has occurred.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"QOSMGR","3","NO_VMR_QOSLABEL","qm_generate_vmrs have no qos label. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","An internal software error has occurred.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"QOSMGR","3","NULL_POLICER","Internal Error Invalid Policer. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","An internal software error has occurred.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"QOSMGR","3","POLICER_RES_COUNT","Internal Error Invalid Policer count. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","An internal software error has occurred.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"QOSMGR","3","POLICYMAP_NOT_FOUND","Cannot find policymap for [chars]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","An internal software error has occurred. [chars] is the policy-map name.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"QOSMGR","3","QUEUE_PTR_ERROR","queue pointers out of order [hex] [hex] [hex] [hex]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","An internal software error has occurred. [hex] [hex] [hex] [hex] are the software-computed queue pointer values. The parameters provide error details for technical support.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"QOSMGR","3","RESERVE_COUNT_ERROR","Reserved Count Exceeding total [dec]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","An internal software error has occurred in the allocated reserved buffers. [dec] is the reserved count computed by the software.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"QOSMGR","3","RESOURCE_INTERNAL","Internal Error in resource allocation. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","An internal software error has occurred.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"QOSMGR","3","VMRSEQ_INVALID","Internal Error Invalid VMR sequence. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","An internal software error has occurred.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"QOSMGR","4","ACTION_NOT_SUPPORTED","Action is not supported in policymap [chars]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","An action other than the set, trust, and police policy-map class configuration commands was configured in a policy map. This is a hardware limitation. [chars] is the policy-map name.","Configure only the supported actions of set, trust, and police when in policy-map class configuration mode."
"QOSMGR","4","CLASS_NOT_SUPPORTED","Classification is not supported in classmap [chars]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","An unsupported match class-map configuration command was configured in a policy map and attached to an egress interface, or more than one match class-map command was configured. This is a hardware limitation. [chars] is the class-map name.","Reconfigure the class map or the policy map. Use only the match ip dscp dscp-list class-map configuration command in a policy map that is attached to an egress interface. Only one match per class map is supported."
"QOSMGR","4","COMMAND_FAILURE","Execution of [chars] command failed. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The command to configure a QoS setting failed. This is possibly due to lack of hardware resources. [chars] is the description of the command.","Look for any other messages that indicate resource failure. If other messages indicate that the hardware resources are exceeded, retry the command with a smaller configuration. Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"QOSMGR","4","HARDWARE_NOT_SUPPORTED","Hardware limitation has reached for policymap [chars]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The policy-map configuration has exceeded the limitation of the hardware. You configured more QoS ACL entries than the number specified in the SDM template. [chars] is the policy-map name.","Reconfigure the class map or the policy map, and reduce the number of QoS ACLs."
"QOSMGR","4","MATCH_NOT_SUPPORTED","Match type is not supported in classmap [chars]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","An unsupported match type was entered. Only the access-group acl-index-or-name, ip dscp dscp-list, and ip precedence ip-precedence-list match types are supported with the match class-map configuration command. [chars] is the class-map name.","Reconfigure the class map using only the match access-group, match ip dscp, and match ip precedence class-map configuration commands within the class map."
"QOSMGR","4","NOT_SUPPORTED","Action '[chars]' is not supported for a policymap attached to output side. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","A set or trust policy-map class configuration command was configured in a policy map and attached to an egress interface. A warning message is logged, and the actions do not take effect. This is a hardware limitation. [chars] is either the set or trust action.","Do not configure a set or trust policy-map class configuration command in a policy map and attach it to an egress interface. These policy-map actions are supported only on ingress interfaces."
"QOSMGR","4","POLICER_PLATFORM_NOT_SUPPORTED","Policer configuration has exceeded hardware limitation for policymap [chars]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The policy-map configuration has exceeded the hardware limitation. An attempt to configure more policers in all policy maps (by using the police or police aggregate policy-map class configuration command) than supported by the hardware, which is not allowed, caused this condition. [chars] is the policy-map name.","Reconfigure the class maps or the policy maps, or delete the policy map from some interfaces."
"QOSMGR","4","POLICER_POLICY_NOT_SUPPORTED","Number of policers has exceeded per policy hardware limitation for policymap [chars]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The policy-map configuration has exceeded the hardware limitation. An attempt to configure more policers in a policy map (by using the police or police aggregate policy-map class configuration command) than supported by the hardware, which is not allowed, caused this condition. [chars] is the policy-map name.","Reconfigure the class map or the policy map, and reduce the number of policers."
"RMON","5","FALLINGTRAP","Falling trap is generated because the value of [chars] has fallen below the falling-threshold value [dec].","A falling trap has been generated. The value of the specified MIB object is below the falling threshold value. [chars] is the MIB object, and [dec] is the threshold value.","Take appropriate action on the specified MIB object."
"RMON","5","RISINGTRAP","Rising trap is generated because the value of [chars] exceeded the rising-threshold value [dec].","A rising trap has been generated. The value of the specified MIB object is above the rising threshold value. [chars] is the MIB object, and [dec] is the threshold value.","Take appropriate action on the specified object."
"SCHED","3","UNEXPECTEDEVENT","[traceback] [process information] Process received unknown event (maj [hex], min [hex])","A process did not handle an event. The first [hex] is the major event number, and the second [hex] is the minor event number, both of which allow you to identify the event that occurred.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information."
"SDM","6","MISMATCH_ADVISE","[chars].Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","A stack member cannot support the SDM template that the stack master is using. Switches in the SDM mismatch state are not functional stack members. This error follows the STACKMGR-6-SWITCH_ADDED_SDM error message if it reports SDM_MISMATCH. [chars] displays mismatch information and recommended corrective actions.","Downgrade the SDM template of the stack master to make it compatible with the stack member switches. For example, if the stack master uses the aggregator routing template, the message recommends downgrading the stack master to the desktop routing template by using the sdm prefer vlan desktop global configuration command."
"SESA","3","MASTER_AUTENTICATION_FAIL","Failed to [chars] SESA MA auth at remote end (src[dec]) (dest [dec]) Err [dec])","The master switch cannot be remotely authenticated. Check Federal Information Processing Standards Publication (FIPS) authorization key on master switch and the remote switch and reboot. [chars] is the action value, the first [dec] is the source switch, the second [dec] is the destination switch, and the third [dec] is the error value.","If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information."
"SESA","2","MEMORY_ALLOC_FAIL","Failed to allocate memory (location [chars])(src [dec])(dest [dec])(Err [dec])","The switch failed to allocate memory. You have to fix the problem immediately. [chars] is the request type, the first [dec] is the source switch, the second [dec] is the destination switch, and the third [dec] is the error value.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"SESA","2","MASTER_THREAD_FAIL","Failed to start master thread processes (location [chars]) on switch [dec](rebooting...)(Err [dec])","The master rekey processess are not starting and the switch will reboot automatically. [chars] is the request type, the first [dec] is the switch box bit, and the second [dec] is the error value.","If the message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SESA","2","REKEY_FAIL","Failed to rekey (location [chars]) (switch: [dec])(Err [dec]),(rebooting...)","The master rekey is failing and the switch will reboot automatically. [chars] is the type of request, the first [dec] is the switch box bit, and the second [dec] is the error value.","If the message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SESA","3","MISMATCH","The [chars] is not compatible with SESA (location [chars]) (rebooting...)","The SESA mixed mode requires the system to support matching features and version. The first [chars] is the version and feature, and the second [chars] is the request type.","Use the right image version and license."
"SESA","3","INTERNAL_ERROR","There was an internal error (reason [chars]) (location [chars]) (rebooting...)","There was a SESA internal error. The first [chars] is the error value, and the second [chars] is the request type.","Check the error log and reboot if necessary. If the message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SESA","3","REMOTE_AUTHENTICATION_FAIL","Failing AT Match check on (box [dec])(sn [chars])(op-1=[hex])(op-N= [hex])","Remote authentication failed. [dec] is the switch number, [chars] is the switch box bit, the first [hex] is the first index value, and the second [hex] is the last index value.","Check the authorization key or error log and reboot if necessary. If the message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SESA","3","INTERNAL_HRPC_ERROR","hrpc bloc error [chars](Error [dec])(idx [dec])(tobits= [hex])","HRPC is not allowing SESA to complete. [chars] is the request type, the first [dec] is the error value, the second [dec] is the switch box bit, and [hex] is the destination switch box bit.","Check error log for sequence, check stack cables, and reboot. If the message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SESA","3","AKS_DECRYPT_FAIL","Failed to decrypt AKS (location [chars])(reason [chars])(src [dec])(dest [dec])(Err [dec])","The remote switch failed to decrypt. The first [chars] is the request type, the second [chars] is the reason for failure, the first [dec] is the source switch, the second [dec] is the destination switch, the third [dec] is the error value.","Check the authorozation key on the master switch and the remote switch and reboot. If the message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SESA_ESP","3","BLOCK_FAILURE","Failure to [chars] ecrypted block (reason [chars]) (class [dec])(pd_sz [dec])(dlen [dec]) Too many indicate a critical situation","There is an error in the request. The message normally appears after a master failover. The first [chars] is the action, the second [chars] is the failure reason, the first [dec] is the class value, the second [dec] is the padding size, the third [dec] is the data length.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SESA_ESP","3","REPLAY_ERROR","Possible replay on switch (Switch [dec]->Switch([dec]),(seq= [hex])(curr= [hex])(class [dec])","The switches are replaying and this could be an intrusion. The first [dec] is the source switch box bit, the second [dec] is the destination switch box bit, the third [dec] is the class value, the first [hex] is the message sequence, and the second [hex] is the error value.","Check the log and reboot the switch. You can also change the authorization keys on all stack members to prevent an attack. If the message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SESA","6","THREAD_START","Starting [chars] thread on switch [dec]","SESA rekeying threads are spinning off after starting successfully. [chars] is the name of the thread, [dec] is the switch box bit.","No action is required."
"SPAN","3","MEM_UNAVAIL","Memory was not available to perform the SPAN operation.","The system could not perform a SPAN operation because of a lack of memory.","Reduce other system activity to ease the memory demands."
"SPAN","3","UNKN_ERR","An internal error occurred during a SPAN operation.","SPAN detected an error in its internal operation.","The error might be transient. Try the SPAN operation again. If a second attempt also fails, reload the switch by using the reload privileged EXEC command to complete the operation."
"SPAN","3","UNKN_ERR_PORT","An internal error occurred when configuring SPAN on port [chars].","SPAN detected an error in its internal operation. [chars] is the interface.","The error might be transient. Try the SPAN operation again. If the second attempt also fails, reload the switch by using the reload privileged EXEC command to complete the operation."
"SPANTREE","2","BLOCK_BPDUGUARD","Received BPDU on port [chars] with BPDU Guard enabled. Disabling port.","A bridge protocol data unit (BPDU) was received on an interface that has the spanning tree BPDU guard feature enabled. The interface was administratively shut down. [chars] is the interface name.","Either remove the device sending BPDUs, or disable the BPDU guard feature. The BPDU guard feature can be locally configured on the interface or globally configured on all ports that have Port Fast enabled. To disable BPDU guard on an interface, use the no spanning-tree bpduguard enable interface configuration command. To disable BPDU guard globally, use the no spanning-tree portfast bpduguard default global configuration command. After you have removed the device or disabled BPDU guard, re-enable the interface by entering the no shutdown interface configuration command."
"SPANTREE","2","BLOCK_BPDUGUARD_VP","Received BPDU on port [chars], vlan [dec] with BPDU Guard enabled. Disabling vlan.","A BPDU was received on the interface and the VLAN. The spanning tree BPDU guard feature is enabled and configured to shut down the VLAN. The VLAN is error disabled. [chars] is the interface, and [dec] is the VLAN.","Either remove the device sending BPDUs, or disable the BPDU guard feature. You can configure the BPDU guard feature locally on the interface or globally on all Port Fast enabled ports. Enter the clear errdisable privileged EXEC command to re-enable the interface and VLAN."
"SPANTREE","2","BLOCK_PVID_LOCAL","Blocking [chars] on [chars]. Inconsistent local vlan.","The spanning-tree port associated with the listed spanning-tree instance and interface will be held in the spanning-tree blocking state until the port VLAN ID (PVID) inconsistency is resolved. The listed spanning-tree instance is that of the native VLAN ID of the listed interface. The first [chars] is the interface, and the second [chars] is the spanning-tree instance.","Verify that the configuration of the native VLAN ID is consistent on the interfaces on each end of the 802.1Q trunk connection. When corrected, spanning tree automatically unblocks the interfaces, as required."
"SPANTREE","2","BLOCK_PVID_PEER","Blocking [chars] on [chars]. Inconsistent peer vlan.","The spanning-tree port associated with the listed spanning-tree instance and interface will be held in the spanning-tree blocking state until the port VLAN ID (PVID) inconsistency is resolved. The listed spanning-tree instance is that of the native VLAN ID of the interface on the peer switch to which the listed interface is connected. The first [chars] is the interface, and the second [chars] is the spanning-tree instance.","Verify that the configuration of the native VLAN ID is consistent on the interfaces on each end of the 802.1Q trunk connection. When interface inconsistencies are corrected, spanning tree automatically unblocks the interfaces."
"SPANTREE","2","CHNL_MISCFG","Detected loop due to etherchannel misconfiguration of [chars] [chars].Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","A misconfiguration of a channel group has been detected. For example, the ports on one side of the EtherChannel either are not configured to be in the channel or did not bundle into the channel, and the other side has successfully bundled the ports into the EtherChannel. The first [chars] is the port, and the second [chars] is the VLAN.","Use the show interfaces status err-disabled privileged EXEC command to identify the local ports, and use the show etherchannel summary privileged EXEC command on the remote device to check the EtherChannel configuration. After the configuration is correct, enter the shutdown and then no shutdown interface configuration commands on the associated port-channel interfaces."
"SPANTREE","2","LOOPGUARD_BLOCK","Loop guard blocking port [chars] on [chars].","The spanning-tree message age timer has expired because no BPDUs were received from the designated bridge. Because this condition could be caused by a unidirectional-link failure, the interface is put into the blocking state and marked as loopguard-inconsistent to prevent possible loops from being created. The first [chars] is the port name, and the second [chars] is the spanning-tree mode displayed in the show spanning-tree privileged EXEC command.","Enter the show spanning-tree inconsistentports privileged EXEC command to review the list of interfaces with loopguard inconsistencies. Find out why devices connected to the listed ports are not sending BPDUs. One reason might be that they are not running the STP. If so, you should disable loop guard on the inconsistent interfaces by using the spanning-tree guard none interface configuration command or by starting the STP on the remote side of the links."
"SPANTREE","2","LOOPGUARD_CONFIG_CHANGE","Loop guard [chars] on port [chars] on [chars].","The spanning-tree loopguard configuration for the listed interface has been changed. If enabled, the interface is placed into the blocking state. It is marked as loopguard-inconsistent when the message-age timer expires because no BPDUs were received from the designated bridge. This feature is mainly used to detect unidirectional links. The first [chars] is the loopguard state (enable or disable), the second [chars] is the interface name, and the third [chars] is the spanning-tree instance.","Verify that this is the desired configuration for the listed interface. Correct it if this is not the desired configuration."
"SPANTREE","2","LOOPGUARD_UNBLOCK","Loop guard unblocking port [chars] on [chars].","The listed interface has received a BPDU. If the inconsistency was caused by a unidirectional link failure, the problem no longer exists. The loopguard-inconsistency is cleared for the interface, which is taken out of the blocking state, if appropriate. The first [chars] is the port name, and the second [chars] is the spanning-tree mode displayed in the show spanning-tree privileged EXEC command.","No action is required."
"SPANTREE","2","PVSTSIM_FAIL","Blocking [chars] port [chars]: Inconsistent [chars] PVST BPDU received on VLAN [dec], claiming root [dec]:[enet]","The specified port on the multiple spanning-tree (MST) switch is blocked. When a designated port on an MST switch is connected to a PVST+ switch, the CIST (MST00) information on the port of the MST switch must be consistently superior (lower bridge ID, lower path cost, and so forth) to the information in all the PVST+ messages. If the port is the root, the CIST (MST00) information on the MST switch must be consistently inferior to all the PVST+ messages. If this constraint is violated, the port on the MST switch is blocked to prevent a potential bridging loop. The first [chars] is the MST switch, the second [chars] is the port, and the third [chars] is the PVST+ switch. The first [dec] is the VLAN ID, the second [dec] is the MST switch, and [enet] is the MST-switch MAC address.","When STP converges after a new switch or switch port is added to the topology, this condition might happen briefly. In such cases, the port unblocks automatically. If the port remains blocked, identify the root bridge as reported in the message, and configure the appropriate priority for the VLAN spanning tree, consistent with the CIST role on the port of the MST switch."
"SPANTREE","2","PVSTSIM_OK","PVST Simulation inconsistency cleared on port [chars].","The specified interface is no longer receiving PVST BPDUs advertising information that is inconsistent with the CIST port information. The PVST simulation inconsistency is cleared, and the interface returns to normal operation. [chars] is the port.","No action is required."
"SPANTREE","2","RECV_1Q_NON_1QTRUNK","Received 802.1Q BPDU on non 802.1Q trunk [chars] [chars].","The interface that received a Shared Spanning Tree Protocol (SSTP) BPDU was in trunk mode but was not using 802.1Q encapsulation. The first [chars] is the interface, and the second [chars] is the VLAN.","Verify that the configuration and operational state of the listed interface and that of the interface to which it is connected are in the same mode (access or trunk). If the mode is trunk, verify that both interfaces have the same encapsulation (ISL or 802.1Q). If the encapsulation types are different, use the switchport trunk encapsulation interface configuration command to make them consistent. When the encapsulation is consistent, spanning tree automatically unblocks the interface."
"SPANTREE","2","RECV_BAD_TLV","Received SSTP BPDU with bad TLV on [chars] [chars].","The listed interface received an SSTP BPDU without the VLAN ID tag. The BPDU is discarded. The first [chars] is the interface, and the second [chars] is the VLAN that received the SSTP BPDU.","If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SPANTREE","2","RECV_PVID_ERR","Received BPDU with inconsistent peer vlan id [dec] on [chars] [chars].","The listed interface received an SSTP BPDU that is tagged with a VLAN ID that does not match the VLAN ID that received the BPDU. This occurs when the native VLAN is not consistently configured on both ends of an 802.1Q trunk. [dec] is the VLAN ID, the first [chars] is the port, and the second [chars] is the VLAN.","Verify that the configurations of the native VLAN ID is consistent on the interfaces on each end of the 802.1Q trunk connection. When the configurations are consistent, spanning tree automatically unblocks the interfaces."
"SPANTREE","2","ROOTGUARD_BLOCK","Root guard blocking port [chars] on [chars].","The listed interface received a BPDU that advertises a superior spanning-tree root bridge (lower bridge ID, lower path cost, and so forth) than that in use. The interface is put into blocking state and marked as root-guard inconsistent to prevent a suboptimal spanning-tree topology from forming. The first [chars] is the port name, and the second [chars] is the spanning-tree mode displayed in the output of the show spanning-tree privileged EXEC command.","Enter the show spanning-tree inconsistentports privileged EXEC command to review the list of interfaces with root-guard inconsistencies. Find out why devices connected to the listed ports are sending BPDUs with a superior root bridge, and take action to prevent more occurrences. When the inaccurate BPDUs have been stopped, the interfaces automatically recover and resume normal operation. Make sure that it is appropriate to have root guard enabled on the interface."
"SPANTREE","2","ROOTGUARD_CONFIG_CHANGE","Root guard [chars] on port [chars] on [chars].","The spanning-tree root guard configuration for the listed interface has changed. If enabled, any BPDU received on this interface that advertises a superior spanning-tree root bridge (lower bridge ID, lower path cost, and so forth) to that already in use causes the interface to be put into the blocking state and marked as root-guard inconsistent. The first [chars] is the root-guard state (enable or disable), the second [chars] is the interface, and the third [chars] is the spanning-tree instance.","Verify that this is the desired configuration for the listed interface. Correct it if it is not the desired configuration."
"SPANTREE","2","ROOTGUARD_UNBLOCK","Root guard unblocking port [chars] on [chars].","The listed interface is no longer receiving BPDUs advertising a superior root bridge (lower bridge ID, lower path cost, and so forth). The root-guard inconsistency is cleared for the interface, and the blocking state is removed from the interface. The first [chars] is the port name, and the second [chars] is the spanning-tree mode displayed in show spanning-tree privileged EXEC command.","No action is required."
"SPANTREE","2","UNBLOCK_CONSIST_PORT","Unblocking [chars] on [chars]. Port consistency restored.","The port VLAN ID or port type inconsistencies have been resolved, and spanning tree will unblock the listed interface of the listed spanning-tree instance. The first [chars] is the interface, and the second [chars] is the spanning-tree instance.","No action is required."
"SPANTREE","3","BAD_PORTNUM_SIZE","Rejected an attempt to set the port number field size to [dec] bits (valid range is [dec] to [dec] bits).","An error occurred in the platform-specific code that caused it to request more or less bits than are possible. The spanning-tree port identifier is a 16-bit field, which is divided evenly between the port priority and port number, with each subfield being 8 bits. This allows the port number field to represent port numbers between 1 and 255. However, on systems with more than 255 ports, the size of port number portion of the port ID must be increased to support the number of ports. This is performed by the spanning-tree subsystem at system initialization because the maximum number of ports on a particular platform will not change. This error occurs because of an error in the platform-specific code, which causes it to request more or less bits than are possible. The first [dec] is the number of bits for the port number, and the second and third [dec] describe the valid range.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SPANTREE","3","PORT_SELF_LOOPED","[chars] disabled.- received BPDU src mac ([enet]) same as that of interface.","The listed interface received a BPDU with a source MAC address that matches the one assigned to the listed interface. This means that a port might be looped back to itself, possibly because of an installed diagnostic cable. The interface will be administratively shut down. [chars] is the interface that received the BPDU, and [enet] is the source MAC address.","Verify the interface configuration, and test any cable connected to the interface. When the problem is resolved, re-enable the interface by entering the no shutdown interface configuration command."
"SPANTREE","3","PRESTD_NEIGH","pre-standard MST interaction not configured ([chars]).","The switch has received a prestandard MST BPDU on an interface that is not configured to send prestandard MST BPDUs. The switch automatically adjusts its configuration on the interface and starts sending prestandard BPDUs. However, the switch does not automatically detect all prestandard neighbors, and we recommend that you configure the interface to send prestandard MST BPDUs by using the spanning-tree mst pre-standard interface configuration command. This warning message only appears once. [chars] is the interface.","Use the spanning-tree mst pre-standard interface configuration command on all the interfaces to which other switches running Cisco's prestandard MST version are connected. We recommend that you migrate all the switches in the network to the MST standard version."
"SPANTREE","4","PORT_NOT_FORWARDING","[chars] [chars] [chars] [chars].","A port-not-forwarding alarm is set or cleared. The first [chars] is the mode, and the second [chars] is the severity. The third [chars] is the interface name, and the fourth [chars] is the alarm string.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SPANTREE","5","EXTENDED_SYSID","Extended SysId [chars] for type [chars].","The extended system ID feature is either enabled or disabled for the given type of spanning tree. If enabled, the spanning-tree instance identifier is stored in the lower portion of the bridge ID priority field and limits the allowed values for the bridge priority from 0 to 61440, in increments of 4096. If disabled, the bridge ID priority field consists only of the configured priority, but some spanning-tree features might not be available on a given platform (for example, support for 4096 VLANs). On some platforms, this feature might be mandatory. The first [chars] is the extended system ID state (enable or disable), and the second [chars] is the spanning-tree instance.","No action is required."
"SPANTREE","5","ROOTCHANGE","Root Changed for [chars] [dec]: New Root Port is [chars]. New Root Mac Address is [enet].","The root switch changed for a spanning-tree instance. The first [chars] and [dec] is the interface ID for the previous root port, the second [chars] is the interface ID for the new root port, and [enet] is the Ethernet address of the new root port.","No action is required."
"SPANTREE","5","TOPOTRAP","Topology Change Trap for [chars] [dec].","A trap was generated because of a topology change in the network. [chars] and [dec] is the interface ID.","No action is required."
"SPANTREE","6","PORTADD_ALL_VLANS","[chars] added to all Vlans","The interface has been added to all VLANs. [chars] is the added interface.","No action is required."
"SPANTREE","6","PORTDEL_ALL_VLANS","[chars] deleted from all Vlans","The interface has been deleted from all VLANs. [chars] is the deleted interface.","No action is required."
"SPANTREE","6","PORT_STATE","Port [chars] instance [dec] moving from [chars] to [chars].","The port state changed. The first [chars] is the interface name. [dec] is the spanning-tree instance ID. The second [chars] is the old state (such as listening, learning, or forwarding, and so forth), and the third [chars] is the new state.","No action is required."
"SPANTREE","7","BLOCK_PORT_TYPE","Blocking [chars] on [chars]. Inconsistent port type.","The listed interface is in the spanning-tree blocking state until the port-type inconsistency is resolved. The first [chars] is the interface, and the second [chars] is the spanning-tree instance.","Verify that the configuration and operational states of the listed interface and those of the interface to which it is connected are in the same mode (access or trunk). If the mode is trunk, verify that both interfaces have the same encapsulation (ISL or 802.1Q). When these parameters are consistent, spanning tree automatically unblocks the interface."
"SPANTREE","7","PORTDEL_SUCCESS","[chars] deleted from Vlan [dec].","The interface has been deleted from VLAN. [chars] is the interface, and [dec] is the VLAN ID.","No action is required."
"SPANTREE","7","RECV_1Q_NON_TRUNK","Received 802.1Q BPDU on non trunk [chars] [chars].","The listed interface received an STP BPDU that is not an operational trunking interface. The first [chars] is the port name, and the second [chars] is the VLAN name.","Verify that the configuration and operational state of the listed interface and that of the interface to which it is connected are in the same mode (access or trunk). If the mode is trunk, verify that both interfaces have the same encapsulation (none, ISL, or 802.1Q). When these parameters are consistent, spanning tree automatically unblocks the interface."
"SPANTREE_FAST","7","PORT_FWD_UPLINK","[chars] [chars] moved to Forwarding (UplinkFast).","The listed interface has been selected as the new path to the root switch for the listed spanning-tree instance. The first [chars] is the spanning-tree instance, and the second [chars] is the interface.","No action is required."
"SPANTREE_VLAN_SW","2","MAX_INSTANCE","Platform limit of [dec] STP instances exceeded. No instance created for [chars] (port [chars]).","The number of currently active VLAN spanning-tree instances has reached a platform-specific limit. No additional VLAN instances are created until the existing number of instances drops below the platform limit. [dec] is the spanning-tree instance limit, the first [chars] is the smallest VLAN ID of those VLANs that cannot have spanning-tree instances created, and the second [chars] is the port number.","Reduce the number of currently active spanning-tree instances by either disabling some of the currently active spanning-tree instances or deleting the VLANs associated with them. You must manually enable the spanning trees that could not be created because of limited instances."
"STACKMGR","3","HDM_GET_DEVICE_RECORD_FAIL","Device Manager could not get device record.Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","This switch could not get the device record for some or all other switches in the stack.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"STACKMGR","3","MSG_FAIL","Failed to retrieve stack message from port-asic [dec] in direction [dec].Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","The stack manager module did not retrieve stack messages. The first [dec] is the ASIC ID, and the second [dec] is the direction.","No action is required."
"STACKMGR","3","NORECORD","Switch removed event for switch [dec] with no switch record.Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","The stack manager received a switch-removed event for which there is no switch record. [dec] is the switch number.","No action is required."
"STACKMGR","4","MASTER_ELECTED","Switch [dec] has been elected as MASTER of the stack. Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","The specified switch has been elected stack master. [dec] is the switch number of the elected stack master.","No action is required."
"STACKMGR","4","STACK_LINK_CHANGE","Stack Port [chars] Switch [dec] has changed to state [chars]. Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","The specified stack port status has changed state to up or down. The first [chars] is the stack port (1 or 2), [dec] is the switch number, and the second [chars] is the new state (up or down).","No action is required."
"STACKMGR","4","SWITCH_ADDED","Switch [dec] has been ADDED to the stack. Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","The specified stack member switch has been added to the stack. [dec] is the switch number.","No action is required."
"STACKMGR","4","SWITCH_ADDED_SDM","Switch [dec] has been ADDED to the stack (SDM_MISMATCH). Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","The specified switch has been added to the stack. [dec] is the switch number. SDM_MISMATCH means that the added switch cannot support the SDM template that the stack master is using. Subsequent SDM-6-MISMATCH_ADVISE messages explain the mismatch and recommend corrective actions.","No action is required unless SDM_MISMATCH is displayed. For SDM_MISMATCH corrective actions, see SDM-6-MISMATCH_ADVISE."
"STACKMGR","4","SWITCH_ADDED_VM","Switch [dec] has been ADDED to the stack (VERSION_MISMATCH). Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","A switch that has been added to the stack has a different software version. [dec] is the switch number.","No action is required."
"STACKMGR","4","SWITCH_REMOVED","Switch [dec] has been REMOVED from the stack. Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","The specified switch has been removed from the stack. [dec] is the switch number.","No action is required."
"STACKMGR","5","MASTER_READY","Master Switch [dec] is READY.Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","The stack master is ready for use. [dec] is the stack master switch number.","No action is required."
"STACKMGR","5","SWITCH_READY","Switch [dec] is READY. Note This message applies only to Catalyst 3750, 2975, and 2960-S switches.","The switch is ready. [dec] is the switch number.","No action is required."
"STORM_CONTROL","3","FILTERED","A [chars] storm detected on [chars]. A packet filter action has been applied on the interface.Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The amount of traffic detected on the interface has exceeded the configured threshold values. The system is filtering the excess traffic. The first [chars] is the traffic type, and the second [chars] is the interface.","Determine and fix the root cause of the excessive traffic on the interface."
"STORM_CONTROL","3","SHUTDOWN","A packet storm was detected on [chars]. The interface has been disabled.Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The amount of traffic detected on the interface has exceeded the configured threshold values. Because the interface is configured to shut down if a packet storm event is detected, it has been placed in an error-disabled state. [chars] is the affected interface.","You can enable error-disabled recovery by using the errdisable recovery global configuration command to automatically re-enable the interface. You should determine and fix the root cause of the excessive traffic on the interface."
"SUPERVISOR","3","FATAL","[chars]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","An internal error occurred in the supervisor ASIC. [chars] is the detailed error message.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SUPQ","3","THROTTLE_CPU_QUEUE","Invalid application ID [dec] used for throttling. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","An application has passed an invalid application ID for throttle check. [dec] is the internal application identifier.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SUPQ","4","CPUHB_RECV_STARVE","[chars]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The system has detected that messages directed to the CPU are delayed. [chars] is the detailed error message.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SUPQ","4","CPUHB_SLOW_TRANSMIT","[chars]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The system is warning you about a slowdown of the sending interface. [chars] is the detailed error message.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SUPQ","4","CPUHB_TX_FAIL","[chars]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The system is warning you about the sending interface discarding the heartbeat message. [chars] is the detailed error message.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SUPQ","4","PORT_QUEUE_STUCK","Port queue Stuck for asic [dec] port [dec] queue [dec]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The system has detected that an interface queue is not being cleared in a reasonable time. The first [dec] is the ASIC, the second [dec] is the interface, and the third [dec] is the queue number.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SUPQ","4","RECV_QUEUE_STUCK","Receive queue Stuck for asic [dec] queue [dec]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The system has detected that the receiving queue is not being cleared in a reasonable time. The first [dec] is the ASIC, and the second [dec] is the queue number.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SW_DAI","4","ACL_DENY","[dec] Invalid ARPs ([chars]) on [chars], vlan [dec].([[enet]/[chars]/[enet]/[chars]/[time-of-day]]).Note This message applies only to Catalyst 3750 and 3560 switches.","The switch has received ARP packets considered invalid by ARP inspection. The packets are erroneous, and their presence shows that administratively denied packets were seen in the network. This log message appears when packets have been denied by ACLs either explicitly or implicitly (with static ACL configuration). These packets show attempted man-in-the-middle attacks in the network. The first [dec] is the number of invalid ARP packets. The first [chars] is either Req (request) or Res (response), and the second [chars] is the short name of the ingress interface. The second [dec] is the ingress VLAN ID. [enet]/[chars]/[enet]/[chars]/[time-of-day] is the MAC address of the sender, the IP address of the sender, the MAC address of the target, the IP address of the target, and the time of day.","No action is required."
"SW_DAI","4","DHCP_SNOOPING_DENY","[dec] Invalid ARPs ([chars]) on [chars], vlan [dec].([[enet]/[chars]/[enet]/[chars]/[time-of-day]]). Note This message applies only to Catalyst 3750 and 3560 switches.","The switch has received ARP packets considered invalid by ARP inspection. The packets are erroneous, and their presence might show attempted man-in-the-middle attacks in the network. This log message appears when the IP and MAC address binding of the sender for the received VLAN is not present in the DHCP snooping database. The first [dec] is the number of invalid ARP packets. The first [chars] is either Req (request) or Res (response), and the second [chars] is the short name of the ingress interface. The second [dec] is the ingress VLAN ID. [enet]/[chars]/[enet]/[chars]/[time-of-day] is the MAC address of the sender, the IP address of the sender, the MAC address of the target, the IP address of the target, and the time of day.","No action is required."
"SW_DAI","6","DHCP_SNOOPING_PERMIT","[dec] ARPs ([chars]) on [chars], vlan [dec].([[enet]/[chars]/[enet]/[chars]/[time-of-day]]).Note This message applies only to Catalyst 3750 and 3560 switches.","The switch has received ARP packets that have been permitted because the IP and MAC address of the sender match the DHCP snooping database for the received VLAN. The first [dec] is the number of valid ARP packets. The first [chars] is either Req (request) or Res (response), and the second [chars] is the short name of the ingress interface. The second [dec] is the ingress VLAN ID. [enet]/[chars]/[enet]/[chars]/[time-of-day] is the MAC address of the sender, the IP address of the sender, the MAC address of the target, the IP address of the target, and the time of day.","No action is required."
"SW_DAI","4","INVALID_ARP","[dec] Invalid ARPs ([chars]) on [chars], vlan [dec].([[enet]/[chars]/[enet]/[chars]/[time-of-day]]).Note This message applies only to Catalyst 3750 and 3560 switches.","The switch has received ARP packets considered invalid by ARP inspection. The packets do not pass one or more validation checks of the source or destination MAC address or the IP address. The first [dec] is the number of invalid ARP packets. The first [chars] is either Req (request), Res (response), or Invalid Opcode. The second [chars] is the short name of the ingress interface. The second [dec] is the ingress VLAN ID. [enet]/[chars]/[enet]/[chars]/[time-of-day] is the MAC address of the sender, the IP address of the sender, the MAC address of the target, the IP address of the target, and the time of day.","No action is required."
"SW_DAI","4","PACKET_BURST_RATE_EXCEEDED","[dec] packets received in [dec] seconds on [chars].Note This message applies only to Catalyst 3750 and 3560 switches.","The switch has received the given number of ARP packets in the specified burst interval. The interface is in the error-disabled state when the switch receives packets at a higher rate than the configured packet rate every second over the configured burst interval. The message is logged just before the interface is put into the error-disabled state and if the configured burst interval is more than a second. The first [dec] is the number of packets, the second [dec] is the number of seconds, and [chars] is the affected interface.","No action is required."
"SW_DAI","4","PACKET_RATE_EXCEEDED","[dec] packets received in [dec] milliseconds on [chars]. Note This message applies only to Catalyst 3750 and 3560 switches.","The switch has received the given number of ARP packets for the specified duration on the interface. This message is logged just before the port is put into the error-disabled state because of the exceeded packet rate and when the burst interval is set to 1 second. The first [dec] is the number of packets, the second [dec] is the number of milliseconds, and [chars] is the affected interface.","No action is required."
"SW_DAI","4","SPECIAL_LOG_ENTRY","[dec] Invalid ARP packets [[time-of-day]]. Note This message applies only to Catalyst 3750 and 3560 switches.","The switch has received ARP packets considered invalid by ARP inspection. The packets are erroneous, and their presence might show attempted man-in-the-middle attacks in the network. This message differs from other SW_DAI messages in that this message captures all messages when the rate of incoming packets exceeds the dynamic ARP inspection logging rate. [dec] is the number of invalid ARP packets, and [time-of-day] is the time of day.","No action is required."
"SW_DAI","6","ACL_PERMIT","[dec] ARPs ([chars]) on [chars], vlan [dec].([[enet]/[chars]/[enet]/[chars]/[time-of-day]]).Note This message applies only to Catalyst 3750 and 3560 switches.","The switch has received ARP packets that are permitted as a result of an ACL match. The first [dec] is the number of valid ARP packets. The first [chars] is either Req (request) or Res (response), and the second [chars] is the short name of the ingress interface. The second [dec] is the ingress VLAN ID. [enet]/[chars]/[enet]/[chars]/[time-of-day] is the MAC address of the sender, the IP address of the sender, the MAC address of the target, the IP address of the target, and the time of day.","No action is required."
"SW_DAI","6","DHCP_SNOOPING_PERMIT","[dec] ARPs ([chars]) on [chars], vlan [dec].([[enet]/[chars]/[enet]/[chars]/[time-of-day]]).Note This message applies only to Catalyst 3750 and 3560 switches.","The switch has received ARP packets that have been permitted because the IP and MAC address of the sender match the DHCP snooping database for the received VLAN. The first [dec] is the number of valid ARP packets. The first [chars] is either Req (request) or Res (response), and the second [chars] is the short name of the ingress interface. The second [dec] is the ingress VLAN ID. [enet]/[chars]/[enet]/[chars]/[time-of-day] is the MAC address of the sender, the IP address of the sender, the MAC address of the target, the IP address of the target, and the time of day.","No action is required."
"SW_MACAUTH","4","UNAUTH_MAC","Unauthenticated MAC [enet] on port [chars]","The switch has received an unauthenticated MAC address on the specified port. [enet] is the unauthenticated MAC address, and [chars] is the port.","No action is required."
"SW_MACAUTH","5","CLEAR_TABLE","MAC Authentication Table Cleared","The MAC authentication table was cleared.","No action is required."
"SW_MACAUTH","5","MACAUTH_ENADSA","MAC Authentication [chars]","MAC authentication is enabled or disabled. [chars] is the MAC authentication status, either enabled or disabled.","No action is required."
"SW_MACAUTH","5","MAC_AUTHENTICATED","MAC [enet] was authenticated","The switch has received a command to authenticate a MAC address. [enet] is the MAC address.","No action is required."
"SW_MATM","4","MACFLAP_NOTIF","Host [enet] in [chars] [dec] is flapping between port [chars] and port [chars] Note This message applies only to Catalyst 3750 and 3560 switches.","The switch found the traffic from the specified host flapping between the specified ports. [enet] is the host MAC address, [chars] [dec] is the switch ID, the first and second [chars] are the ports between which the host traffic is flapping.","Check the network switches for misconfigurations that might cause a data-forwarding loop."
"SW_VLAN","3","MALLOC_FAIL","Failed to allocate [dec] bytes","Memory allocation failed. [dec] is the number of bytes.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SW_VLAN","3","VLAN_DAT_CACHE_SEQUENCE","Out of sequence vlan.dat sync message. Expected: [dec]; received: [dec].","The vlan.dat file is synchronized to the STANDBY through one or more checkpoint messages from ACTIVE. The sequence number for each set of checkpoint messages starts with 1. These messages are cached at the STANDBY until the end-of-set indicator is received. The STANDBY received a checkpoint message with a sequence number that does not match the expected sequence number. The first [dec] is the expected checkpoint message sequence number, and the second [dec] is the received checkpoint message sequence number.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SW_VLAN","3","VLAN_PM_NOTIFICATION_FAILURE","VLAN Manager synchronization failure with Port Manager over [chars].","The VLAN manager dropped a notification from the port manager because of a lack of ready pool space. [chars] is the type of port manager notification.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SW_VLAN","3","VTP_PROTOCOL_ERROR","VTP protocol code internal error [chars].","The VTP code encountered an unexpected error while processing a configuration request, a packet, or a timer expiration. [chars] is the internal error.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SW_VLAN","4","BAD_PM_VLAN_COOKIE_RETURNED","VLAN manager unexpectedly received a bad PM VLAN cookie from the Port Manager, VLAN indicated [dec].","The VLAN manager received an upcall and a VLAN cookie from the port manager that translated to a bad VLAN ID. [dec] is the VLAN ID.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SW_VLAN","4","BAD_STARTUP_VLAN_CONFIG_FILE","Failed to configure VLAN from startup-config. Fallback to use VLAN configuration file from non-volatile memory.","The VLAN software did not use the VLAN configuration from the startup-configuration file. It will use the binary VLAN configuration file in NVRAM.","No action is required."
"SW_VLAN","4","BAD_VLAN_CONFIGURATION_FILE","VLAN configuration file contained incorrect verification word [hex].","The VLAN configuration file read by the VLAN manager did not begin with the correct value. The VLAN configuration file is invalid, and it has been rejected. [hex] is the incorrect verification value.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SW_VLAN","4","BAD_VLAN_CONFIGURATION_FILE_VERSION","VLAN configuration file contained unknown file version [dec].","The VLAN configuration file read by the VLAN manager contained an unrecognized file version number, which might mean an attempt to regress to an older version of the VLAN manager software. [dec] is the file version number.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SW_VLAN","4","BAD_VLAN_TIMER_ACTIVE_VALUE","Encountered incorrect VLAN timer active value [chars].","Because of a software error, a VLAN timer was detected as active when it should have been inactive or as inactive when it should have been active. [chars] is the VLAN timer active value.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SW_VLAN","4","EXT_VLAN_CREATE_FAIL","Failed to create VLANs [chars]: [chars]. Note This message applies only to Catalyst 3550 switches.","The software did not create VLANs. The first [chars] is the Layer 2 VLAN list, and the second [chars] describes the reason for the failure.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section for more information."
"SW_VLAN","4","EXT_VLAN_INTERNAL_ERROR","Extended VLAN manager received an internal error [dec] from [chars] [chars].","An unexpected error code was received by the VLAN manager from the extended-range VLAN configuration software. [dec] is the error code. The first [chars] is the function, and the second [chars] describes the error code.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SW_VLAN","4","EXT_VLAN_INVALID_DATABASE_DATA","Extended VLAN manager received bad data of type [chars] value [dec] from function [chars].","The extended-range VLAN manager received invalid data from an extended-range VLAN configuration database routine. The first [chars] is the data type, [dec] is the number received, and the second [chars] is the function name.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SW_VLAN","4","IFS_FAILURE","VLAN manager encountered file operation error call = [chars] / file = [chars] / code = [dec] ([chars]) / bytes transferred = [dec].","The VLAN manager received an unexpected error return from a Cisco IOS file system (IFS) call while reading the VLAN database. The first [chars] is the function call name, the second [chars] is the file name, the first [dec] is the error code, the third [chars] is the textual interpretation of the error code, and the second [dec] is the number of bytes transferred.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SW_VLAN","4","NO_PM_COOKIE_RETURNED","VLAN manager unexpectedly received a null [chars] type cookie from the Port Manager, data reference [chars].","The VLAN manager queried the port manager for a reference cookie but received a NULL pointer instead. The first [chars] is the type of port manager cookie, and the second [chars] is the interface or VLAN that is the source of the problem.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SW_VLAN","4","STARTUP_EXT_VLAN_CONFIG_FILE_FAILED","Failed to configure extended range VLAN from startup-config. Error [chars].","The VLAN software did not use an extended-range VLAN configuration from the startup configuration file. All extended-range VLAN configurations are lost after the system boots up. [chars] is a description of the error code.","No action is required."
"SW_VLAN","4","VLAN_CREATE_FAIL","Failed to create VLANs [chars]: [chars]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The specified VLANs could not be created. The port manager might not have completed the VLAN creation requests because the VLANs already exist as internal VLANs. The first [chars] is the VLAN ID, and the second [chars] describes the error.","Check the internal VLAN usage by using show vlan internal usage privileged EXEC command, reconfigure the feature that is using the internal VLANs, and create the VLANs again. If this message appears again, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Enter the show tech-support user EXEC command to gather data that might help identify the nature of the error. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SW_VLAN","4","VTP_INTERNAL_ERROR","VLAN manager received an internal error [dec] from vtp function [chars] [chars].","The VLAN manager received an unexpected error code from the VTP configuration software. [dec] is the error code, the first [chars] is the VTP function, and the second [chars] is the error-code description.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SW_VLAN","4","VTP_INVALID_DATABASE_DATA","VLAN manager received bad data of type [chars] value [dec] from vtp database function [chars].","The VLAN manager received invalid data from a VTP configuration database routine. The first [chars] is the data type, [dec] is the inappropriate value that was received, and the second [chars] is the VTP database function.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SW_VLAN","4","VTP_INVALID_EVENT_DATA","VLAN manager received bad data of type [chars] value [dec] while being called to handle a [chars] event.","The VLAN manager received invalid data from the VTP configuration software. The first [chars] is the data type, [dec] is the value of that data, and the second [chars] is the VTP event.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SW_VLAN","4","VTP_SEM_BUSY","VTP semaphore is unavailable for function [chars]. Semaphore locked by [chars].","The VTP database is not available. You should access the VTP database later. The first [chars] is the function name that you want to configure, and the second [chars] is the function name that is using the VTP database.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"SW_VLAN","6","VTP_DOMAIN_NAME_CHG","VTP domain name changed to [chars].","The VLAN Trunking Protocol (VTP) domain name was changed through the configuration to the name specified in the message. [chars] is the changed domain name.","No action is required."
"SW_VLAN","6","OLD_CONFIG_FILE_READ","Old version [dec] VLAN configuration file detected and read OK. Version [dec] files will be written in the future.","The VLAN software detected an old version of the VLAN configuration file format. It interpreted the file, but it will use the new format in the future. The first [dec] is the old version number, and the second [dec] is the new version number.","No action is required."
"SW_VLAN","6","VLAN_DAT_CACHE_EXISTS","Unexpected vlan.dat cache exists. Removing the cache and continuing the sync with new set.","This message does not affect switch functionality.","No action is required."
"SW_VLAN","6","VTP_DOMAIN_NAME_CHG","VTP domain name changed to [chars].","The VTP domain name was changed through the configuration to the name specified in the message. [chars] is the changed domain name.","No action is required."
"SW_VLAN","6","VTP_MODE_CHANGE","VLAN manager changing device mode from [chars] to [chars].","An automatic VTP-mode device-change occurred upon receipt of a VLAN configuration database message containing more than a set number of VLANs. The first [chars] is the previous mode, and the second [chars] is the current mode.","No action is required."
"SWITCH_QOS_TB","5","TRUST_DEVICE_DETECTED","[chars] detected on port [chars], port's configured trust state is now operational. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","A trusted boundary detected a device matching the trusted device setting for the port and has modified the port trust state. The first [chars] is the trusted device, and the second [chars] is the port.","No action is required."
"SWITCH_QOS_TB","5","TRUST_DEVICE_LOST","[chars] no longer detected on port [chars], operational port trust state is now untrusted. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","A trusted boundary lost contact with a trusted device and has set the port trust state to untrusted. The first [chars] is the trusted device, and the second [chars] is the port.","No action is required."
"TCAMMGR","3","GROW_ERROR","cam region [dec] can not grow. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The specified CAM region is configured as a static region with a fixed number of entries, and a caller requested to add more CAM entries. [dec] is the CAM region.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"TCAMMGR","3","HANDLE_ERROR","cam handle [hex] is invalid. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The CAM handle used by the caller is not valid. [hex] is the handle value.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"TCAMMGR","3","INDEX_ERROR","cam value/mask index [dec] is invalid. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The CAM index used by the caller is not valid. [dec] is the index value.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"TCAMMGR","3","MOVE_ERROR","cam entry move from index [int] to index [int] failed. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","Moving a CAM entry from one index to another failed. [int] is the index value.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"TCAMMGR","3","REGION_ERROR","cam region [dec] is invalid. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The CAM region is not valid. [dec] is the region.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"TCAMMGR","3","REGMASK_ERROR","invalid cam region [dec] mask [dec] pair. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","A caller attempted to install an entry with an invalid mask for the region. Only a predetermined set of masks is allowed in a region. The first [dec] is the region, and the second [dec] is the mask.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"UDLD","0","STOPPED","UDLD process stopped:[chars].","The UDLD process stopped because it cannot read the unique system identifier that is being used by UDLD. The system identifier is used to identify the device that is sending the UDLD packets. [chars] is the UDLD process name.","Reload the switch by using the reload privileged EXEC command. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Enter the show tech-support user EXEC command to gather data that might help identify the nature of the error. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"UDLD","3","UDLD_IDB_ERROR","UDLD error handling [chars] interface [chars].","A software error occurred in UDLD processing associated with a specific interface. The first [chars] is the event, and the second [chars] is the interface.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"UDLD","3","UDLD_INTERNAL_ERROR","UDLD internal error [chars].","A software check failed during UDLD processing. [chars] is a description of the internal error.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"UDLD","3","UDLD_INTERNAL_IF_ERROR","UDLD internal error, interface [chars] [chars].","A software check failed during UDLD processing. The first [chars] is the interface, and the second [chars] is a description of the error.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"UDLD","4","UDLD_PORT_DISABLED","UDLD disabled interface [chars], [chars] detected.","The UDLD Protocol disabled an interface because it detected connections between neighbors that were functioning only in one direction, which might potentially cause spanning-tree loops or interfere with connectivity. The cause is likely to be hardware related, either due to a bad port, a bad cable, or a misconfigured cable. The first [chars] is the interface, and the second [chars] is the error detected.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"UDLD","6","UDLD_PORT_RESET","UDLD reset interface [chars].","The UDLD Protocol detected a unidirectional connection between neighbors. Reset the port that was disabled by UDLD by using the udld reset privileged EXEC command or through a hardware action such as a link-state change. [chars] is the interface.","Find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"UFAST_MCAST_SW","3","PROC_START_ERROR","No process available for transmitting UplinkFast packets. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","UplinkFast packets will not be sent because the process could not be created.","UplinkFast does not work unless you reload the switch software. If this problem persists even after reload, find out more about the error by using the show tech-support privileged EXEC command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"UFAST_MCAST_SW","4","MEM_NOT_AVAILABLE","No memory is available for transmitting UplinkFast packets on Vlan [dec]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","UplinkFast packets will not be sent on a VLAN due to memory limitations. [dec] is the VLAN ID.","Reduce other system activity to ease memory demands."
"VLMAPLOG","6","ARP","vlan [dec] (port [chars]) denied arp ip [inet] -> [inet], [dec] packet[chars]","A packet from the virtual LAN (VLAN) that matches the VLAN access-map (VLMAP) log criteria was detected. The first [dec] is the VLAN number, the first [chars] is the port name, the first [inet] is the source IP address, the second [inet] is the destination IP address, the second [dec] denotes the number of packets, and the second [chars] represents the letter 's' to indicate more than one packet.","No action is required."
"VLMAPLOG","6","ICMP","vlan [dec] (port [chars]) denied icmp [inet] -> [inet] ([dec]/[dec]), [dec] packet[chars]","A packet from the VLAN that matches the VLMAP log criteria was detected. The first [dec] is the VLAN number, the first [chars] is the port name, the first [inet] is the source IP address, the second [inet] is the destination IP address, the second [dec] is the Internet Control Message Protocol (ICMP) message type, the third [dec] is the ICMP message code, the fourth [dec] denotes the number of packets, and the second [chars] represents the letter 's' to indicate more than one packet.","No action is required."
"VLMAPLOG","6","IGMP","vlan [dec] (port [chars]) denied igmp [inet] -> [inet] ([dec]), [dec] packet[chars]","A packet from the VLAN that matches the VLMAP log criteria was detected. The first [dec] is the VLAN number, the first [chars] is the port name, the first [inet] is the source IP address, the second [inet] is the destination IP address, the second [dec] is the Internet Group Management Protocol (IGMP) message type, the third [dec] denotes the number of packets, and the second [chars] represents the letter 's' to indicate more than one packet.","No action is required."
"VLMAPLOG","6","IP","vlan [dec] (port [chars]) denied ip protocol=[dec]  [inet] -> [inet], [dec] packet[chars]","A packet from the VLAN that matches the VLMAP log criteria was detected. The first [dec] is the VLAN number, the first [chars] is the port name, the second [dec] is the protocol number, the first [inet] is the source IP address, the second [inet] is the destination IP address, the third [dec] denotes the number of packets, and the second [chars] represents the letter 's' to indicate more than one packet.","No action is required."
"VLMAPLOG","6","L4","vlan [dec] (port [chars]) denied [chars] [inet]([dec]) -> [inet]([dec]), [dec] packet[chars]","A packet from the VLAN that matches the VLMAP log criteria was detected. The first [dec] is the VLAN number, the first [chars] is the port name, the second [chars] is the protocol, the first [inet] is the source IP address, the second [dec] is the source port, the second [inet] is the destination IP address, the third [dec] is the destination port, the fourth [dec] denotes the number of packets, and the third [chars] represents the letter 's' to indicate more than one packet.","No action is required."
"VQPCLIENT","2","CHUNKFAIL","Could not allocate memory for VQP.","An error occurred when the system tried to allocate memory for the VQP client.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"VQPCLIENT","2","DENY","Host [enet] denied on interface [chars]. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The VMPS has denied access for the given host MAC address to an interface. [enet] is the host MAC address, and [chars] is the interface name.","No action is normally required. If you think that the host should have been allowed access, verify the configuration on the VMPS."
"VQPCLIENT","2","TOOMANY","Interface [chars] shutdown by active host limit. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The system has shut down the specified interface because too many hosts have requested access to that interface. [chars] is the interface name.","To enable the interface, remove the excess hosts, and enter the no shutdown interface configuration command."
"VQPCLIENT","3","IFNAME","Invalid interface ([chars]) in response. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The VMPS has specified an unknown VLAN name. [chars] is the VLAN name.","Verify the VMPS configuration."
"VQPCLIENT","3","VLANNAME","Invalid VLAN [chars] in response. Note This message applies only to Catalyst 3750, 3560, 2975, 2970, and 2960 switches.","The VMPS has specified an unknown VLAN name. [chars] is the VLAN name.","Ensure that the VLAN exists on the switch. Verify the VMPS configuration by entering the show vmps privileged EXEC command."
"WCCP","5","CACHEFOUND","Web Cache [IP_address] acquired. Note This message applies only to Catalyst 3750 and 3560 switches.","The switch has acquired the specified web cache. [IP_address] is the web cache IP address.","No action is required."
"WCCP","1","CACHELOST","Web Cache [IP_address] lost. Note This message applies only to Catalyst 3750 and 3560 switches.","The switch has lost contact with the specified web cache. [IP_address] is the web cache IP address.","Verify the operation of the web cache by entering the show ip wccp web-cache privileged EXEC command."
"WRLSCNTR","3","INIT_ERR","Initialization failed. [chars]Note This message applies only to Catalyst 3750 switches.","Part of initialization required for the normal operation of the wireless LAN controller failed.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section."
"WRLSCNTR","3","CONFIG_ERR","No available channel-group to configure internal interfaces [chars] and [chars].Note This message applies only to Catalyst 3750 switches.","The interfaces connected to the wireless LAN controller must be configured as part of a channel group. The switch tried to apply the configuration, but it failed because all channel-group numbers have been assigned. You cannot correctly configure interfaces connected to the wireless LAN controller without removing a channel group.","Modify the EtherChannel configuration to remove a channel group, and use that channel-group number to configure interfaces connected to the wireless LAN controller."
"WRLSCNTR","3","VERSION_ERR","Switch and wireless controller are using incompatible versions.Note This message applies only to Catalyst 3750 switches.","The switch software is not fully compatible with the software on the wireless LAN controller. Some functionality might not be available.","Update the software on the switch or on the wireless LAN controller so that the software versions are compatible."
"C4K_ACL","4","OUTOFMEMORY","Out of Memory while allocating [char]","The software failed to allocate memory for the given object while processing ACLs. The configuration might have exceeded its maximum limit. If so, the feature using this ACL will not work.","If it is mandatory that the feature work normally, remove other unwanted features that require ACLs and retry the operation. If the problem persists, contact your technical support representative."
"C4K_ACLSNOOPMAN","4","ACLALLOCFAILURE","Acl Allocation for [char] failed.","A new IOS ACL was created but there is no memory for the analogous platform ACL. ACL-based snooping will not function properly on the interface.","Alter or remove the configuration on the switch to reduce memory use."
"C4K_ACLSNOOPMAN","4","ACLFEATUREALLOCFAILURE","AclFeature Allocation for Acl Id: [dec] failed.","Memory for the platform ACL-related data structures is exhausted. ACL-based snooping will not function properly on the interface.","Alter or remove the configuration on the switch to reduce memory use."
"C4K_ARPSNOOPINGMAN","4","OUTOFRESOURCES","Resources for constructing ACLs are not available.","Software resources are not available to setup hardware to redirect ARP packets to software. Features dependent on capturing ARP packets such as Dynamic ARP Inspection or LAN Port IP will not work if this log message appears.","Unconfigure other TCAM related features to reduce switch memory requirements and reconfigure the ACL."
"C4K_BAD_ID_HW","2","AUTHENTICATIONFAILUREFANTRAY","The Fan tray failed to authenticate and may not be a genuine Cisco product","The fan tray failed authentication for one of two reasons. The fan tray is either counterfeit or the authentication process on the fan tray is broken. The fan tray will continue to operate, but it may be counterfeit.","Return the fan tray to Cisco TAC for further analysis."
"C4K_BAD_ID_HW","2","AUTHENTICATIONFAILUREMODULE","Module [dec] failed to authenticate and may not be a genuine Cisco product","A switching module or supervisor engine failed authentication for one of two reasons. The switching module or supervisor engine is either counterfeit or the authentication process on the switching module or supervisor engine is broken. If a supervisor engine fails authentication, it will continue to operate, but it may be counterfeit. If a switching module fails authentication, it will be disabled.","Return the switching module or supervisor engine to Cisco TAC for further analysis."
"C4K_BUFFERMANAGER","3","OUTOFVBUFS","Have run out of vbufs (internal buffers)","The switch ran out of the internal memory buffers that are used for various tasks. This error is unusual because the internal buffers are used for only a short time, released, and then available for reuse. Typically, this condition is transitory.","If the message persists, reboot the switch."
"C4K_CHASSIS","2","ALLCHASSISSEEPROMSINVALID","Contents of all chassis' serial eeproms are invalid","The contents of all of the chassis's serial EEPROMs are invalid. In non-redundant chassis, there is one serial EEPROM, and it is bad. If this is a redundant chassis, there are two serial EEPROMs, and they are both bad.","Try removing and reinserting the supervisor engine. If that doesn't work, try power cycling the switch. If the serial EEPROM is still invalid, this chassis should be returned."
"C4K_CHASSIS","2","INLINEPOWEROFF","Inline power to the switch has been turned off","Software detected that the pass-through current is disabled. This condition will cause all phones drawing PoE from the switch to be powered off.","If you want PoE, verify that the in-line power switch on the power supply is turned on."
"C4K_CHASSIS","2","INSUFFICIENTFANSDETECTED","Too few working fans in fan tray, the chassis will overheat. If not resolved, in [dec] minutes [dec] seconds all line cards will be placed into Reset-Mode","Two or more fans in the system fan tray are malfunctioning, or the fan tray has been removed. Although this is a minor alarm, system components could overheat and shut down.","Replace the system fan tray or broken fans."
"C4K_CHASSIS","2","INSUFFICIENTFANSDETECTEDPOWERDOWN","Too few working fans in fan tray, the chassis will overheat. If not resolved, in [dec] minutes [dec] seconds the chassis will power down","Two or more required fans in the fan tray are malfunctioning, or the fan tray has been removed. Software will reset the modules to reduce heat generation, and power down the switch to prevent overheating damage to components.","Replace the broken fans as soon as possible."
"C4K_CHASSIS","2","INSUFFICIENTFANSSHUTDOWN","Resetting linecards due to fan tray failure","Two or more fans in the fan tray have failed, or the fan tray has been removed. Linecards have been reset to reduce heat generation.","Replace the system fan tray as soon as possible."
"C4K_CHASSIS","2","INSUFFICIENTFANTRAYSDETECTED","Too few working fan trays exist and the chassis will overheat. In [dec] min [dec] sec, if this situation is not resolved by installing [dec] fan trays in a [char] airflow direction, all linecards will be placed in Reset-Mode.","The minimum number of fantrays required for correct airflow are not installed.","Install the minimum number of fantrays. Consult your hardware documentation for further information."
"C4K_CHASSIS","2","INSUFFICIENTPOWERDETECTED","Insufficient power available for the current chassis configuration","The current chassis configuration exceeds power availability. If this condition persists, software will reset the modules.","If the power availability problem persists and impacts performance, replace the power supply with a larger capacity power supply."
"C4K_CHASSIS","2","INSUFFICIENTFANTRAYSDETECTEDPOWERDOWN","Too few working fan trays exist and the chassis will overheat. In [dec] min [dec] sec, if this situation is not resolved by installing [dec] fan trays in a [char] airflow direction, the chassis will power down.","The minimum number of fantrays required for correct airflow are not installed.","Install the minimum number of fantrays. Consult your hardware documentation for further information."
"C4K_CHASSIS","2","INSUFFICIENTPOWERSHUTDOWN","Holding module in slot [dec] in reset, due to insufficient power","The switch was using more power than is available for the allowed time interval. Software reset the modules to reduce power consumption.Explanation    If the power availability problem persists and impacts performance, replace the power supply with a power supply with a larger capacity.Error Message    C4K_CHASSIS-2-MUXBUFFERMISMATCHED: Mux Buffer in slot  [dec] of mismatched type [dec].Explanation    The Mux Buffer in this slot is not of the same type as the mux buffers in the other slots. This may impact traffic.","Please contact Cisco TAC to confirm that it is okay to continue using this mux buffer."
"C4K_CHASSIS","2","MUXBUFFERNOTPRESENT","Mux buffer [dec] is not present","The mux buffer card is either not connected to the backplane properly or is not present. This will render the impacted slot useless. The switching module present in this slot cannot be identified, its SEEPROM cannot be read and it will be as good as non-existent.","Reseat the mux buffers as described the hardware documentation. If the problem persists, return the backplane to get it fixed immediately."
"C4K_CHASSIS","2","MUXBUFFERSEEPROMINVALID","Invalid data in mux buffer [dec]'s serial eeprom","The mux buffer's serial EEPROM could not be read or has not been programmed. This may impact traffic.","Contact Cisco TAC to confirm that it is okay to continue using this mux buffer."
"C4K_CHASSIS","2","MUXBUFFERTYPENOTSUPPORTED","Mux Buffer in slot  [dec] of unsupported type [dec].","The Mux Buffer in this slot is not supported by this software. This may impact traffic.","Contact Cisco TAC to confirm that it is okay to continue using this mux buffer."
"C4K_CHASSIS","2","OVERHEATINGSHUTDOWN","Resetting linecards due to critical temperature","The switch is now warmer than its maximum allowable operating temperature. Software will reset modules to reduce heat generation.Explanation    Verify that the switch is in the proper operating environment and that the fans are functioning properly.Error Message    C4K_CHASSIS-2-POWERSUPPLYSHUTDOWN: Unsupported or unknown power supply type detected in slot [dec]. Shutting down power supplyExplanation    An unsupported or unknown power supply has been detected. Power supply will be shut down.","Replace with a power supply supported by this chassis."
"C4K_CHASSIS","2","SLOTOVERHEATINGSHUTDOWN","Resetting linecard in slot [dec] due to critical temperature","Critical temperature for a module has been exceeded. The module has been reset to reduce heat generation.","Remove and reinsert the module after some cooling period. If the problem persists, the module has failed and needs to be replaced."
"C4K_CHASSIS","2","SUPERVISORSEEPROMINVALID","Contents of supervisor's serial eeprom are invalid","The contents of the supervisor engine's serial EEPROM are invalid. For example, a bad checksum or the supervisor engine type doesn't match with the other hardware information. This could happen if the read failed because the supervisor engine isn't seated correctly in the slot.IOS considers this supervisor engine faulty and will not bring up the chassis' interfaces.","Try removing and reinserting the supervisor engine. If that doesn't work, try power cycling the switch. If the switch still fails to come online, this supervisor engine should be returned."
"C4K_CHASSIS","2","SYSTEMSHUTDOWNONPOWERFAILURE","All installed power supplies have experienced a power failure. Shutting system down as a precautionary measure.","All installed power supplies have experienced a power failure and the system will be shut down by IOS.","Power cycle the switch. If the problem reoccurs, replace the power supplies."
"C4K_CHASSIS","3","AFANTRAYSEEPROMINVALID","Invalid fan tray [dec] seeprom data","The fan tray's serial EEPROM could not be read or has not been programmed.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_CHASSIS","3","AFANTRAYSEEPROMREADFAILED","Failed to read fan tray [dec]'s seeprom.","Reading the system fan tray serial EEPROM failed.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_CHASSIS","3","ALLMODULETEMPERATURESENSORSFAILED","All temperature sensors on module [dec] have failed","All temperature sensors on the module have failed. If an over-temperature condition develops, the module will be unable to detect and report it.","If this message appears only once, this could be a transient error and no action is required. If this message appears repeatedly, have the module repaired."
"C4K_CHASSIS","3","ASUPERVISORFANTRAYWITHBADIDPROM","The idprom of the currently installed fan tray [dec] does not contain valid data.","The fantray is operating properly, but could not be identified. For some supervisor-chassis-fantray combinations the power consumption allocated to the fantray may be higher than what the fantray is actually consuming.","Replace the fan tray."
"C4K_CHASSIS","3","BACKPLANESEEPROMREADFAILED","Failed to read backplane's serial eeprom, read [dec], expected size [dec]","Reading the backplane's serial eeprom failed.","Power cycle the switch. If that does not work, return the chassis."
"C4K_CHASSIS","3","BADMACRANGEINSPROM","Module [dec]'s serial eeprom contains [dec] mac addresses, but needs [dec]","The contents of the module's serial EEPROM is incorrect, and the range is smaller than the number of front-panel ports for the module. The module's serial EEPROM contains a range of MAC addresses for this module, and the range should contain the same number of MAC addresses as the number of front-panel ports because each MAC address corresponds to a front-panel port.","Contact your technical support representative; you will likely have to return the module to Cisco to reprogram the serial EEPROM."
"C4K_CHASSIS","3","CHASSISTYPEMISMATCHINSPROM","Supervisor's FPGA register chassis type is [char], but chassis' serial eeprom chassis type is [char]","The chassis type in the supervisor engine's FPGA register doesn't match the type in the chassis' serial EEPROM.","Check the chassis serial EEPROM information, using the show idprom chassis command. This should never happen in a production chassis. If it does, the chassis needs to be returned."
"C4K_CHASSIS","3","CLOCKMODULESEEPROMINVALID","Invalid Clock Module seeprom data","A failure occurred while reading the clock module serial EEPROM. This message should occur only in a prototype switch used in an early field trial.","Contact your technical support representative. You may need to return some switch components for repair or replacement."
"C4K_CHASSIS","3","CLOCKMODULESEEPROMREADFAILED","Failed to read clock module's seeprom","Reading the clock module serial eeprom failed.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_CHASSIS","3","CLOCKMODULESEEPROMWRITEFAILED","Failed to write clock module's seeprom","Writing the clock module serial eeprom failed.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_CHASSIS","3","DAUGHTERCARDSEEPROMREADFAILED","Failed to read the serial eeprom on module [dec], daughter card [dec]","The serial EEPROM for a daughter card on the specified module is unreadable. Because reading this EEPROM is the only way to determine the type of card, the card remains offline, as if it was not installed on the module.","Remove the module, and then remove and reseat the daughter card in the module. If this message reappears after you reinsert the module into the switch, the serial EEPROM might be bad. Contact your technical support representative; you will likely have to return the module to Cisco to reprogram or replace the serial EEPROM."
"C4K_CHASSIS","3","FANTRAYREADFAILED","Failed to read system fan tray status register from hardware","Failed to read system fan tray status register from hardware.","If this message appears only once, this could be a transient error and no action is required. If this message appears repeatedly (once every 10 minutes), replace the system fan tray."
"C4K_CHASSIS","3","FANTRAYSEEPROMINVALID","Invalid fan tray seeprom data","A failure occurred while reading the system fan tray serial EEPROM. This message should occur only in a prototype switch used in an early field trial.","Reseat the fan tray to see if the message is due to a faulty connection. If it persists, contact your technical support representative. You may need to return some switch components for repair or replacement."
"C4K_CHASSIS","3","FANTRAYSEEPROMREADFAILED","Failed to read fan tray's seeprom","Reading the system fan tray serial eeprom failed.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_CHASSIS","3","FIRSTCHASSISSEEPROMINVALID","Contents of chassis's first serial eeprom are invalid","The contents of the chassis's first serial EEPROM are invalid. This message only appears in a redundant chassis, which means there is a second serial EEPROM.","Try power cycling the switch. If the serial EEPROM is still invalid, this chassis should be returned."
"C4K_CHASSIS","3","INSUFFICIENTPOWER","Insufficient power to bring up module in slot [dec]","The module type was identified, but the switch does not have sufficient power to bring the module up. The switch holds the module in reset mode to consume less power.","Either remove the module or upgrade the power supply to expand the power capacity of the chassis."
"C4K_CHASSIS","3","INSUFFICIENTPOWERSUPPLIESDETECTED","Insufficient power supplies present for specified configuration","The system software detected that the current chassis configuration has fewer power supplies than required for the existing configuration.","Add a power supply to meet the needs of the current chassis configuration."
"C4K_CHASSIS","3","INVALIDMGMTETHERNETADDR","Chassis SPROM not set or invalid MAC address range","The out of band management port uses a MAC address from the system's MAC address range. The contents of the system's SPROM are bad, so the out of band management port does not have a MAC address.","Contact your technical support representative. You may need to return some switch components for repair or replacement."
"C4K_CHASSIS","3","LINECARDMUXBUFFERTOSUPALIGNMENTWRONG","Linecard [dec] MuxBuffers aligned towards supervisor in slot [dec] instead of [dec]","The mux buffers that work with the switching module in the mentioned slot are configured to work with the standby supervisor engine. The switching module is completely unusable in this condition.","Try removing and reinserting the affected switching module. If that doesn't work, try resetting the switch. If the problem persists, contact your technical support representative."
"C4K_CHASSIS","3","LINECARDNOTSUPPORTEDINCHASSIS","Module [char] is not supported in this chassis.","The module identified in the message is not supported in the chassis. For example, modules requiring 24 Gbps of backplane capacity are not supported in chassis providing only 6 Gbps on the backplane.","Refer to the release notes and module documentation to find which chassis supports this module."
"C4K_CHASSIS","3","LINECARDNOTSUPPORTEDINVIRTUALSWITCH","Module [char] in slot [dec] is not supported in Virtual Switch mode.","The module identified in the message is not supported in Virtual Switch mode.","Remove this module from the Virtual Switching System. Refer to Cisco documentation for information on Virtual Switching System module support."
"C4K_CHASSIS","3","LINECARDNOTVALIDINSLOT","Linecard [char] is not supported in slot [dec], try slots [char].","The supervisor engine identified the type, but the switching module cannot be supported in this slot due to the insufficient number of backplane ports in this slot.","Remove the module from the slot and place it in the alternative slot listed in the message."
"C4K_CHASSIS","3","LINECARDNOTVALIDINSLOT","Module [char] is not supported in slot [dec], try slots [char].","The module type has been identified but it cannot be supported in this slot due to insufficient backplane ports in this slot.","Remove the module from this slot, and insert it into one of the alternative slots listed in the log message."
"C4K_CHASSIS","3","LINECARDSEEPROMREADFAILED","Failed to read module [dec]'s serial eeprom, try reinserting module","The switch cannot read the serial EEPROM of the specified module, and the module will not boot because the EEPROM failed to identify the module type. The read might fail if the module is not seated correctly in the slot.","Remove and reinsert the module. If this message reappears, reboot the switch. If the problem persists, contact your technical support representative. You will likely have to return the module to Cisco to reprogram or replace the serial EEPROM."
"C4K_CHASSIS","3","LINECARDSEEPROMWRITEFAILED","Failed to write module [dec]'s serial eeprom","A write operation to the serial EEPROM failed. The write might fail if the module is not seated correctly in the slot.","Remove and reinsert the module. If this message reappears, reboot the switch. If the problem persists, contact your technical support representative. You will likely have to return the module to Cisco to reprogram or replace the serial EEPROM."
"C4K_CHASSIS","3","MEDIATYPECHANGESYNC","The previous media-type change on [char] did not complete on the standby. Please retry in 10 seconds.","When you run the media-type command once, wait for 10 seconds to allow the state on the active and the standby supervisor to synchronize before you run the same command again.","Wait for about 10 seconds and try the command again."
"C4K_CHASSIS","3","MIXINVOLTAGEDETECTED","Power supplies in the chassis are receiving different voltage inputs All the inputs to a chassis must be at the same voltage. Mixed voltage inputs are not supported.Recommended Action    Change the power supplied to the switch so that all inputs to the chassis are of the same type.Error Message    C4K_CHASSIS-3-MIXINPOWERDETECTED:Power supplies in the chassis are of different types (AC/DC) or wattage","The software detected different kinds of power supplies in the chassis. In a Catalyst 4006 chassis, the power values default to the wattage of the weakest power supply. If you mix power supplies in a Catalyst 4500 series chassis, the switch will use the power supply in power supply bay 1 (PS1) and ignore the power supply in power supply bay 2 (PS2). We do not recommend mixing power supplies of different wattages.","Verify that both power supplies are the same kind and wattage. Replace a power supply if necessary."
"C4K_CHASSIS","3","MIXINVOLTAGEDETECTED","Power supplies in the chassis are receiving different voltage inputs","All the inputs to a chassis must be at the same voltage. Mixed voltage inputs are not supported.","Replace one of the power supplies so that the power supplies used are of the same model."
"C4K_CHASSIS","3","MODULEBRINGUPTIMEDOUT","Module [dec] software bring up did not complete within allocated time","The module bring up could not be completed within pre-allocated time. The module status will be shown as faulty.","Try using the hw-mod module <module number> reset command and check if the problem occurs again. If it does, contact Cisco technical support to get further assistance."
"C4K_CHASSIS","3","MODULENOTSUPPORTHALF","Module [dec] does not support 10 Mb or 100Mb Half duplex operation. Please have your card upgraded if you need half duplex operation.","Some preproduction switching modules have interfaces that do not work in half-duplex mode. This module is probably a prototype.","Contact your technical support representative; you will likely have to return the module to Cisco."
"C4K_CHASSIS","3","MODULERECOVERY","Module %u automatically resetting to recover.","The module has detected an error during operation and it will reset automatically to clear the fault.","Replace the module if it fails to return to normal operation after it is reset. If errors recur, contact Cisco TAC. Otherwise, no action is required."
"C4K_CHASSIS","3","MUXBUFFERINITFAILURE","Mux Buffer Init Failure: Slot([dec])","Mux Buffer Initialization failed because of an I2C bus error. This may impact traffic.","If traffic is impacted, pull out the linecard and reseat it. If traffic flow is not restored, issue the redundancy reload shelf CLI command to restart both supervisors in the chassis. If the redundancy command fails, contact Cisco TAC."
"C4K_CHASSIS","3","MUXBUFFERLOOPBACKFAILED","Failed to put [char] supervisor's module [dec] muxbuffers in loopback","This error can be seen when serial to wire write operation to put line card muxbuffers in loopback fails. This may indicate problems with line card muxbuffers in 45xx chassis.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_CHASSIS","3","MUXBUFFERREADLOOPBACKFAILED","Failed to read whether [char] supervisor's module [dec] muxbuffers are in loopback","This error can be seen when serial to wire write operation to put line card muxbuffers in loopback fails. This may indicate problems with line card muxbuffers in 45xx chassis.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_CHASSIS","3","MUXBUFFERREADSUPERVISORSELECTIONFAILED","Failed to read linecard [dec] muxbuffer supervisor selection register","The active supervisor tried to read alignment information for the switching module slot's mux buffer from the chassis mux buffer module, but was unable to do so. This information is needed to make sure that switching module slot's mux buffer is aligned towards the active supervisor engine.","If this message appears only once for a switching module, this could be a transient error and no action is required. If this message appears repeatedly (once every 5 minutes) on one or more switching modules please contact your technical support representative to replace the supervisor engine and chassis."
"C4K_CHASSIS","3","MUXBUFFERSEEPROMREADFAILED","Failed to read mux buffer [dec]'s serial eeprom","Reading the mux buffer serial eeprom failed.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_CHASSIS","3","MUXMAYMISALIGN","Linecard mux buffers may mis-align to incorrect supervisor due to mux buffer reset with other supervisor desires to be active","While putting switching module mux-buffers in reset and taking them out of reset, other supervisor engine is trying to become active using hardware hot-standby logic. This may cause incorrect alignment of switching module slot's mux buffer towards the non-active supervisor engine causing complete datapath failure.","If this happens, please contact Cisco Technical Support representative to report the failure and reset the other supervisor using the redundancy reload peer command to fix this condition."
"C4K_CHASSIS","3","NETFLOWCARDSEEPROMREADFAILED","Netflow Services Card seeprom read failed","Reading the Netflow Services Card serial eeprom failed.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_CHASSIS","3","OLDWSX4124","WS-X4124-FX-MT revision [dec].[dec], which is < 1.6, is not supported","WS-X4124-FX-MT modules with revisions < 1.6 are not supported.","This module needs to be replaced with a WS-X4124-FX-MT module that has a newer hardware revision number."
"C4K_CHASSIS","3","ONLYLXSFPSALLOWED","Port [char] has a non-LX SFP, which is not supported","The WS-X4448-GB-LX module supports only LX SFPs. It marks any other type of Small Form-Factor Pluggable (SFP) as faulty.","Replace the SFP with an LX SFP that Cisco supports."
"C4K_CHASSIS","3","OUTOFMEMORY","Ran out of memory - cannot allocate internal buffers","The switch ran out of memory in the temporary buffers.","If this message reappears, reboot the switch."
"C4K_CHASSIS","3","POWERSUPPLYCOMMUNICATIONFAILED","Failed to communicate with power supply in slot [dec].","A Read/Write command issued to the power supply failed.","Reinsert the power supply. If the error recurs, hotswap it with a new power supply."
"C4K_CHASSIS","3","POWERSUPPLYSEEPROMINVALID","Invalid data in power supply [dec]'s serial eeprom","The power supply serial EEPROM could not be read or has not been programmed.","This message may appear twice. Enter the show idprom power-supply {number} and the show power commands. If the power-supply idprom information and status display successfully, disregard the message. Otherwise, remove and re-insert the power supply. If the problem persists, hotswap it with a new power supply."
"C4K_CHASSIS","3","POWERSUPPLYSEEPROMREADFAILED","Failed to read power supply [dec]'s serial eeprom","Reading the power supply serial EEPROM failed.","This message may appear twice. Enter the show idprom power-supply {number} and the show power commands. If the power-supply idprom information and status display successfully, disregard the message. Otherwise, remove and re-insert the power supply. If the problem persists, hotswap it with a new power supply."
"C4K_CHASSIS","3","POWERSUPPLYSTATUSREADFAILED","Failed to read power supply [dec]'s status register","Reading the power supply status register failed.","Re-insert the power supply. If that doesn't work, hotswap it with a new power supply."
"C4K_CHASSIS","3","SEEPROMREADFAILEDAFTERWRITE","Error reading back module [dec]s serial EEPROM data after write","After writing a module's serial EEPROM in response to a CLI request, the switch tried to read it back in, to ensure that the correct values were written out. What the switch read back in differs from what the switch wrote out. The read or write might fail if the module is not seated correctly in the slot.","Remove and reinsert the module. If that does not work, reboot the switch. If the problem persists, contact your technical support representative. You will likely have to return the module to Cisco to reprogram or replace the serial EEPROM."
"C4K_CHASSIS","3","STUBPHYMISMATCH","Stub type mismatch: stub [dec]/[dec] is type [dec], should be type [dec]","The stubs have non-matching physical types for the specified module.","Verify that the physical types for every stub on the module match."
"C4K_CHASSIS","3","SUPERVISORFANTRAYBADIDPROM","The idprom of the currently installed fan tray does not contain valid data.","The fantray is operating properly, but could not be identified. For some supervisor engine, chassis, and fan tray combinations the power consumption allocated to the fan tray may be higher than the fan tray is actually consuming.","Replace the fan tray."
"C4K_CHASSIS","3","SUPERVISORFANTRAYPARTIALFAILURE","A fan tray, among the currently installed fantrays, is not functioning.","There are enough fantrays in the system, but some have failed.","Replace the fan tray."
"C4K_CHASSIS","6","SUPERVISORFANTRAYPARTIALFAILUREOK","All fantrays are in good working condition, system has recovered from a partial fantray failure.","There are enough fan trays in the system and all are operational. Some failed fan trays were removed or replaced.","No action is required."
"C4K_CHASSIS","3","SUPERVISORIDENTIFICATIONFAILED","Failed to identify the Supervisor in Slot [dec]'s","SW can not recognize this supervisor. This supervisor is either unsupported or faulty.","Try removing and reinserting the module. If that doesn't work, try resetting the switch. If the read still fails, this module needs to be returned."
"C4K_CHASSIS","3","SUPERVISORTYPEMISMATCHINSPROM","Supervisor's FPGA register type is [dec], but supervisor's serial eeprom type is [dec]","The type in the supervisor engine's FPGA register doesn't match the type in the supervisor engine's serial EEPROM. This might happen if the IDPROM is misprogrammed or the supervisor engine's FPGA register somehow returns an incorrect value. Both are extremely unlikely.","Check the FruMinorType field in the supervisor engine's serial EEPROM, using the show idprom supervisor command. The output should be the same as the number printed in this log message for the FPGA register type. This should never happen with a production supervisor engine. If it does, replace the supervisor engine."
"C4K_CHASSIS","3","TRANSCEIVERINTEGRITYCHECKBYPASSED","Transceiver integrity check on port [char] failed","Non-Cisco-qualified transceivers are permitted but may give unpredictable results.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_CHASSIS","3","TRANSCEIVERCRCINTEGRITYCHECKFAILED","transceiver integrity check on port [char] failed: bad crc","The checksum of the transceiver SEEPROM is not valid, indicating a bad or non-Cisco transceiver. Only Cisco-qualified transceivers are supported. Other transceivers will cause the associated port to show as faulty.","Replace the transceiver with a transceiver that Cisco supports."
"C4K_CHASSIS","3","TRANSCEIVERINTEGRITYCHECKFAILED","transceiver integrity check on port [char] failed: bad key","Only Cisco-qualified transceivers are supported. Other transceivers will cause the associated port to show as faulty.","Replace the transceiver with an transceiver that Cisco supports."
"C4K_CHASSIS","3","TRANSCEIVERSERIALINTEGRITYCHECKFAILED","transceivers on ports [char] and [char] have duplicate serial numbers","Only Cisco-qualified transceivers are supported. Other transceivers place the associated port in the faulty status.All transceivers must have a unique serial number. If this message appears you likely have a cloned transceiver SEEPROM.","Replace the transceiver with a transceiver that Cisco supports."
"C4K_CHASSIS","3","UNKNOWNLINECARD","Unknown module (Field Replaceable Unit minor type [dec]) in slot [dec]","The module's serial EEPROM was readable, and your software image does not recognize this module. A software upgrade is necessary.","Upgrade the software to a version that is compatible with the module."
"C4K_CHASSIS","4","CANTWRITESUPERVISORSPROM","Writing the supervisor's SPROM is not supported","Rewriting the supervisor engine's serial programmable read-only memory (SPROM) is not allowed, because if it is done incorrectly, it could make the system unusable.","This is an informational message only; no action is required."
"C4K_CHASSIS","4","INLINEPOWERRESTORED","Resuming normal phone operation since inline power has been restored","PoE to the switch was restored, and normal phone operation will resume.","This is an informational message only; no action is required."
"C4K_CHASSIS","4","LINECARDIDENTIFICATIONFAILEDONSTANDBY","GalChassisVp: Linecard in Slot [dec] failed to boot on STANDBY Supervisor","Inserted linecard failed to boot on STANDBY supervisor.Explanation    No action is required.Error Message    C4K_CHASSIS-4-OVERHEATINGOVER: Resuming normal operation after return to acceptable temperatures.Explanation    The unit's modules were reset to reduce heat generation, because the unit reached a critical temperature. The switch is now cool enough to return to normal operation.","This is an informational message only; no action is required."
"C4K_CHASSIS","4","OTHERSUPERVISORACTIVEDEBOUNCE","Other supervisor is still holding hardware lock","This condition is detected when redundancy register indicates that other supervisor is holding lock when it is not due to hardware signal latency. Unless there is a real hardware failure, the system recovers from this state. If there is a persistent hardware failure this message will be seen four times.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_CHASSIS","4","POWERSUPPLYFAILURE","The power supply in slot [dec] has experienced a power failure.","One of the installed power supplies has experienced a power failure.","Power cycle the power supply. If the problem reoccurs, replace the power supply."
"C4K_CHASSIS","4","POWERSUPPLYNOTSUPPORTED","Power supply in slot [dec] is not supported on this  platform.Recommended Action    An unsupported power supply has been detected. This power supply was not designed for this platform and should be replaced.Recommended Action    Replace power supply with a supported supply type.Error Message    C4K_CHASSIS-4-SLOTOVERHEATINGOVER: Resuming normal operation in slot [dec] after return to acceptable temperatures.","The module has been reset to reduce heat generation since it exceeded critical temperature. It has returned to acceptable temperature and normal operation is resuming.","This is an informational message only; no action is required."
"C4K_CHASSIS","4","SOMEMODULETEMPERATURESENSORSFAILED","Some temperature sensors on module [dec] have failed","Some temperature sensors on the module have failed. This may restrict the module's ability to detect over-temperature conditions. If further sensors fail, the module will be unable to detect over-temperature conditions.","If this message appears only once, this could be a transient error and no action is required. If this message appears repeatedly (such as, once every hour), return the module for repair."
"C4K_CHASSIS","4","SPURIOUSFANTRAYREMOVALDETECTED","Spurious fantray removal detected","Spurious fantray removals were detected.","If this message appears only once, this could be a transient error and no action is required. If this message occurs repeatedly(such as, once every hour), have the fantray repaired."
"C4K_CHASSIS","4","SUFFICIENTFANSRESTORED","Resuming normal operation after restoration of adequate fan cooling","The modules were reset to reduce heat generation because there were not enough working fans. Adequate fan cooling is now restored, and the switch will resume normal operation.","This is an informational message only; no action is required."
"C4K_CHASSIS","4","SUFFICIENTMODULEPOWERRESTORED","Module in slot [dec] resuming normal operation after restoration of adequate power","The module was reset to conserve power because the system had inadequate power available. The switch now has adequate power and is resuming normal operation.","This is an informational message only; no action is required."
"C4K_CHASSIS","4","SUFFICIENTPOWERRESTORED","Resuming normal operation after restoration of adequate power","The switch reset the modules to conserve power, but it now has adequate power and will resume normal operation.","This is an informational message only; no action is required."
"C4K_CHASSIS","4","TDRTESTINPROGRESS","TDR test is in progress on interface [char]","The TDR test is already in progress on this interface.","Try the command again after the test is completed."
"C4K_CHASSIS","4","TESTNOTSUPPORTEDONPORT","[char] is not supported on this interface","The online diagnostic test requested cannot be run on the specified port.","This is an informational message only; no action is required."
"C4K_CHASSIS","4","TESTNOTSUPPORTEDONPORT","[char] is not supported on this port","The online diagnostic test requested cannot be run on the specified port.","This is an informational message only; no action is required."
"C4K_CHASSIS","4","TESTNOTSUPPORTEDONPORTCONNECTOR","[char] is not supported on port connector type: [char]","This online diagnostic test cannot be run on the specified port with the current connector type. If the connector type changes to copper, it may be possible to run the test.","This is an informational message only; no action is required."
"C4K_CHASSIS","4","UNSUPPORTEDTRANSCEIVER","Unsupported transceiver found in [char]","The transceiver was identified as an unsupported non-Cisco transceiver.","If this transceiver was purchased from Cisco, contact Cisco TAC to get the transceiver replaced."
"C4K_CHASSIS","5","POEFIXED","Poe fixed on slot [dec] (count=[dec])","Under very rare conditions, due to an anomaly in hardware state that includes transients in input power supply, PoE on a slot is restarted by software.","If the message shows up rarely and coincides with external events such as input power supplies being changed, this message can be safely ignored. If the message shows up continuously, contact your Cisco technical support representative."
"C4K_CHASSIS","5","POEHEALTHCHECKFAILED","Poe Health Check failed on slot [dec] (count = [dec])","The PoE health check has failed on a module. The PoE service provided by the module may be unavailable.","If the message shows up rarely and coincides with external events such as input power supplies being changed, this message can be safely ignored. If the message shows up continuously, contact your Cisco representative for a replacement of the PoE switching module."
"C4K_CHASSIS","5","POERESTARTED","Poe restarted on slot [dec] (count=[dec])","Software detected a glitch on the power input to the chassis power supplies and had to restart PoE on one or more slots.","Verify that the power provided to the switch conforms to Cisco's recommendations. If the power input to the chassis is good and the message is showing up continuously, contact your Cisco technical support representative."
"C4K_CHASSIS","5","PORTSPOERESTARTED","Poe restarted for interfaces on slot [dec] (count=[dec])","Software detected a glitch on the power input to the chassis power supplies and had to restart PoE on the specified slot.","Verify that the power provided to the switch conforms to Cisco's recommendations. If the power input to the chassis is good and the message is showing up continuously, contact your Cisco technical support representative."
"C4K_EVC","4","MAXEFPLIMITREACHED","EvcSwitch: Service Instance cannot be created as  maximum limit  has already been reached.","The system limit on the maximum number of service instances has been reached. This includes all the user configured service instances and internal service instances.","If possible, delete other Service Instances or VLANs that are no longer in use."
"C4K_EVC","4","OUTOFEFPRESOURCES","EvcSwitch: There is not sufficient memory to allocate a new  Service Instance.","The software failed to allocate memory for a Service Instance. The specified service instance will not function but will appear in the configuration file. Other features and service instances are unaffected.","If possible, free up the available memory by removing features that are no longer in use."
"C4K_COMMONHWACLMAN","4","ALLACLINHW","All configured ACLs now fully loaded in hardware TCAM - hardware switching / QoS restored","All ACL-based features are now successfully loaded. Packets that were previously processed in software due to the prior loading failure will now be processed in hardware.Note If the features were policy maps, then QoS will be reenabled on all applicable interfaces.","This is an informational message only; no action is required."
"C4K_COMMONHWACLMAN","4","HWPROGSUCCESS","[char] [char] - now fully loaded in hardware","An ACL-based feature has now been successfully loaded after earlier failing to be fully programmed into hardware. Packets using this feature that were being processed in software due to the prior loading failure will now be processed in hardware. If the feature is a policy map, then QoS will be reenabled on the specific interface.","This is an informational message only; no action is required. This log messages indicates a resumption of normal hardware-based ACL and QoS processing for the specified ACL-based feature"
"C4K_COMMONHWACLMAN","4","CFMPORTMACFEATUREFAILED","Failed to create CFM PortMac AclFeature for address   [mac-addr]  on port  [char]","The platform driver code failed to create a necessary data structure for enabling the CFM feature in the hardware. CFM will not operate correctly on the specified interface.","Remove other ACL or QoS-related configuration to free up resources, then disable and reenable CFM on the interface."
"C4K_COMMONHWACLMAN","4","OUTOFLABELS","No more free labels available for path ([object-info])","A new label could not be assigned for an ACL that the user is trying to program. There are too many labels being used. As a result, software will apply security ACLs, and will not apply QoS features. It's possible too many distinct features using ACLs have been configured, or too many per-port per-VLAN features using ACLs have been configured. The hardware will forward the packets to the CPU for ACL processing.","Detaching and reattaching ACLs or policies may help in some cases."
"C4K_COMMONHWACLMAN","4","OUTOFPATHS","Could not allocate path for ( [object-info])","There are too many ports or VLANs using ACLs. The ACLs might not work correctly.","Remove unnecessary ACLs from some interfaces."
"C4K_COMMONHWACLMAN","4","PERMITALL","Out of resources for Qos, permit all for [object-info]","The switch is running out of hardware CAM resources. All packets are permitted, and QoS is applied.","Remove unnecessary ACLs from some interfaces."
"C4K_COMMONHWACLMAN","4","PORTBASEDACLSDISABLED","Output Port Acl  [char]100  has been disabled on port  [char]","The output port ACL is disabled on the interface because there are not enough hardware resources or there are ACEs that require CPU processing of packets.The port ACL is disabled and displays a warning message because the software cannot handle the output port ACLs.","This is an informational message only; no action is required."
"C4K_COMMONHWACLMAN","4","PUNTTOSOFTWARE","Out of resources, punt packets to sw for [object-info]","The hardware content-addressable memory (CAM) resources have been depleted. The hardware forwards the packets to the software for ACL processing.","Remove unnecessary ACLs from some interfaces."
"C4K_COMMONSTUBMAN","4","DIAGSFAILED","[char] failed diagnostics","An ASIC in slot [char] failed diagnostics.","Contact your technical support representative."
"C4K_COMMONSTUBMAN","4","FAILEDTOSENDLOOPBACKTRIES","[char] port [dec] failed to send packet in [dec] tries","An ASIC in slot [char] was unable to send a loopback packet on port [dec] and this is the [dec]th time it tried to send and failed. This suggests that the switch is out of memory. The software will attempt to send a loopback packet only three times.","Contact your technical support representative."
"C4K_COMMONSTUBMAN","4","UNEXPECTEDLOOPBACK","[char] sent out a loopback packet on port [dec], but it came back on port [dec]","The ASIC diagnostics for slot [char] sent a loopback packet out port [dec] and it came back on another port [dec]. This is unexpected because the loopback is done within the hardware.","Contact your technical support representative."
"C4K_COMMONSTUBMAN","7","LOSTPACKET","[char] port [dec] lost a packet","A loopback packet was lost during online diagnostics of an ASIC in slot [char].","This is an informational message only; no action is required."
"DHCP_SNOOPING","3","DHCP_SNOOPING_INTERNAL_ERROR","DHCP Snooping internal error [char]","A software sanity check failed in the DHCP snooping process. This message may also show up if the system is running out of memory or resources.","Reduce resource consumption by disabling features, ports, or packets destined to software. If the condition persists, call Cisco technical support."
"DHCP_SNOOPING","4","AGENT_OPERATION_FAILED","DHCP snooping binding transfer failed. Unable to access URL.","The DHCP snooping binding transfer failed. The reason for failure can include any of the following:?he URL is not available to use.?ot enough memory is available for creating an agent.?he number of agents reached the maximum supported limit.?he switch is unable to create an agent.?he switch is unable to access the URL.?he switch is unable to start the agent.?he Abort timer expired.?he number of entries exceeded the maximum supported limit.?n error occurred when reading the remote database.?n error occurred while writing to the remote database.?HCP snooping expected more data during the read.?he string type is invalid.?he version string type is invalid.?HCP snooping is expecting a new line in the database.?TYPE' was not found in the remote database.?VERSION' was not found in the remote database.?BEGIN' was not found in the remote database.?END' was not found in the remote database.?he type string was not found in the remote database.?he version string was not found in the remote database.?he checksum failed upon entry into the remote database.","Based on the reason for the error (listed above), take the appropriate action."
"DHCP_SNOOPING","4","AGENT_OPERATION_FAILED_N","DHCP snooping binding transfer failed ([dec]). [chars]","This message is logged once every 30 minutes and displays the [dec] number of failures that occurred for a given reason [chars] during the past 30 minutes.This message is a rate-limited version of the DHCP_SNOOPING-4-AGENT_OPERATION_FAILED message.","Based on the reason for the error [chars], look at the explanation for the DHCP_SNOOPING-4-AGENT_OPERATION_FAILED message, and take the appropriate action."
"DHCP_SNOOPING","4","DHCP_SNOOPING_DATABASE_FLASH_WARNING","Saving DHCP snooping bindings to [char] can fill up your device causing the writes of bindings to device","Saving DHCP snooping bindings to a flash file system such as bootflash or slot0 could cause the flash to fill up. Possible consequences include a long delay to regain a console connection, write failures for database configurations, regular squeeze requirements, and reduced life of flash due to regular squeeze operations.","Save the DHCP snooping bindings to an alternate destination. Possible locations for the database agent include a TFTP or FTP server. See the command line help for a complete list of options."
"DHCP_SNOOPING","4","DHCP_SNOOPING_ERRDISABLE_WARNING","DHCP Snooping received [dec] DHCP packets on interface [char]","DHCP snooping detected a DHCP packet rate-limit violation on the specified interface. The interface will be placed in the errdisable state.","This is an informational message only; no action is required."
"DHCP_SNOOPING","4","DHCP_SNOOPING_PVLAN_WARNING","DHCP Snooping configuration may not take effect on secondary vlan [dec]. [char]","DHCP snooping configuration on the primary VLAN automatically propagates to all secondary VLANs if private VLANs are enabled.","This is an informational message only; no action is required."
"DHCP_SNOOPING","4","DHCP_SNOOPING_RATE_LIMIT_EXCEEDED","The interface [char] is receiving more than the threshold set","This message indicates that DHCP packets are coming into the CPU at a much higher rate than the specified threshold.","This is an informational message only; no action is required."
"DHCP_SNOOPING","4","INVALID_RELEASE_OR_DECLINE_PKT","The interface [char] has received a DHCP Release/Decline packet with no existing binding entry for it","This message indicates that a DHCP Release/Decline packet was received with no corresponding binding entry.","This is an informational message only; no action is required."
"DHCP_SNOOPING","4","IP_SOURCE_BINDING_NON_EXISTING_VLAN_WARNING","IP source binding is configured on non existing vlan [dec].","IP source binding was configured on a VLAN that has not yet been configured.","This is an informational message only; no action is required. It may persist unless you define the VLAN in question and then reapply the IP source binding. If you see this message regarding a VLAN that is correctly configured, contact your technical support representative."
"DHCP_SNOOPING","4","IP_SOURCE_BINDING_PVLAN_WARNING","IP source filter may not take effect on secondary vlan [dec] where IP source binding is configured. [char]","The IP source filter on the primary VLAN automatically propagates to all secondary VLANs if private VLANs are enabled.","Reconfigure the IP source binding to a known functioning VLAN."
"DHCP_SNOOPING","4","NTP_NOT_RUNNING","NTP is not running; reloaded binding lease expiration times are incorrect.","If the DHCP snooping bindings are loaded by the DHCP snooping database agent and NTP is not running, then the calculated lease duration for the bindings will be incorrect.","Configure NTP on the switch to provide an accurate time and date for the system clock. Then disable and re-enable DHCP snooping to clear the bindings database."
"DHCP_SNOOPING","4","OPTION82_INSERTION_FAIL","The interface [char] is not able to insert opt82 into the packet because of insufficient space in the packet","This message indicates that certain data was not inserted into a DHCP packet due t o insufficient space in the packet.","This is an informational message only; no action is required."
"DHCP_SNOOPING","4","QUEUE_FULL","Fail to enqueue DHCP packet into processing queue: [char]","DHCP packets are coming into the CPU at a much higher rate than the DHCP snooping process can handle them. These unhandled DHCP packets will be dropped to prevent a denial of service attack.","This is an informational message only; no action is required."
"DHCP_SNOOPING","4","SSO_SYNC_ACK_ERROR","Error is encountered in processing acknowledgement for DHCP snooping binding sync [char]. ack message txn id:[hex]","There was an error in handling the DHCP synchronization acknowledgement. In most of these cases, the ACK message is ignored.","This is an informational message only; no action is required."
"DHCP_SNOOPING","4","STANDBY_AGENT_OPERATION_FAILED","DHCP snooping binding transfer failed on the Standby Supervisor. [char]","If the DHCP snooping database supporting SSO is configured as a local device, both supervisor engines will update their database whenever there is an update regarding bindings. This error message is an indication that a snooping database update on the standby supervisor engine failed in the manner mentioned. The most likely cause for these problems is if the snooping database is configured as a slot0 device, but functioning compact flash memory is only present on the active supervisor engine's slot0 while the standby supervisor engine's slot0 is empty or faulty. Possible variations in output include:'URL not available for use.''Not enough memory available for creating agent.''Number of agents reached maximum supported limit.''Unable to create agent.''Unable to access URL.''Unable to start agent.''Abort timer expiry.''Number of entries exceeded max supported limit.''Unable to transfer bindings. Memory allocation failure.''Error reading the remote database.''Error writing to remote database.''Expected more data on read.''Type string invalid.''Version string invalid.''New line expected in database.''\'TYPE\' not found in remote database.''\'VERSION\' not found in remote database.''\'BEGIN \' not found in remote database.''\'END\' not found in remote database.''Type string not found in remote database.''Version string not found in remote database.''Checksum failed on an entry in remote database.''No failure recorded.'","The switch will continue to function if no action is taken, but the redundancy features will be compromised until both active and standby supervisor engines have working flash memory available. Replace or insert flash memory into the supervisor engine that lacks it if needed."
"DHCP_SNOOPING","5","DHCP_SNOOPING_FAKE_INTERFACE","[char] drop message with mismatched source interface the binding is not updated message type: [char] MAC sa: [mac-addr]","The DHCP snooping feature has detected a host trying to carry out a denial of service attack on another host in the network. The packet will be dropped.","This is an informational message only; no action is required."
"DHCP_SNOOPING","5","DHCP_SNOOPING_MATCH_MAC_FAIL","[char] drop message because the chaddr doesn't match source mac message type: [char] chaddr: [mac-addr] MAC sa: [mac-addr]","The DHCP snooping feature attempted MAC address validation and the check failed. There may be a malicious host trying to carry out a denial of service attack on the DHCP server. The packet will be dropped.","This is an informational message only; no action is required."
"DHCP_SNOOPING","5","DHCP_SNOOPING_NONZERO_GIADDR","[char] drop message with non-zero giaddr or option82 value on untrusted port message type: [char] MAC sa: [mac-addr]","The DHCP snooping feature discovered a DHCP packet with option values not allowed on the untrusted port, indicating some host may be trying to act as a DHCP relay or server. The packet will be dropped.","This is an informational message only; no action is required."
"DHCP_SNOOPING","5","DHCP_SNOOPING_UNTRUSTED_PORT","[char] drop message on untrusted port message type: [char] MAC sa: [mac-addr]","The DHCP snooping feature discovered certain types of DHCP messages not allowed on the untrusted interface, indicating some host may be trying to act as a DHCP server. The packet will be dropped.","This is an informational message only; no action is required."
"DHCP_SNOOPING","6","AGENT_OPERATION_SUCCEEDED","DHCP snooping database [char] succeeded.","DHCP snooping has successfully read or written to the database.","This is an informational message only; no action is required."
"DHCP_SNOOPING","6","BINDING_COLLISION","Binding collision. [dec] bindings ignored","One or more bindings from the database file has a MAC address and VLAN combination for which the switch already holds DHCP snooping bindings.","This is an informational message only; no action is required."
"DHCP_SNOOPING","6","INTERFACE_NOT_VALID","Interface not valid. [dec] bindings ignored.","The interface that is listed in the database file's binding is not available, that the interface is a router port, or that the interface is a DHCP snooping-trusted Layer 2 interface.","This is an informational message only; no action is required."
"DHCP_SNOOPING","6","LEASE_EXPIRED","Lease Expired. [dec] bindings ignored.","The DHCP lease expired for the given number of bindings from the database file.","This is an informational message only; no action is required."
"DHCP_SNOOPING","6","PARSE_FAILURE","Parsing failed for [dec] bindings.","The database read operation failed for the stated number of bindings.","This is an informational message only; no action is required."
"DHCP_SNOOPING","6","VLAN_NOT_SUPPORTED","Vlan not supported. [dec] bindings ignored.","The VLAN is not supported by DHCP snooping.","This is an informational message only; no action is required."
"DOT1X","4","MEM_UNAVAIL","Memory was not available to perform the 802.1X action","Due to a lack of memory 802.1X cannot perform authentication, so it will not be enabled.","Reduce other system activity to ease memory demands. Install more memory, if necessary."
"DOT1X","4","PROC_START_ERR","DOT1X unable to start","For unknown reasons 802.1X cannot start.","Restart 802.1X by entering the dot1x system-auth-control command in case the condition is transient. If the restart fails, reload the device."
"DOT1X","4","UNKN_ERR","An unknown operational error occurred","Due to an unexpected internal error 802.1X cannot operate.","Reload the device."
"DOT1X","5","FAIL","Authentication failed for client ([char]) on Interface [char]","Authentication was unsuccessful.","This is an informational message only; no action is required."
"DOT1X","5","SUCCESS","Authentication successful for client ([char]) on Interface [char]","Authentication was successful.","This is an informational message only; no action is required."
"DTP","4","MEM_UNAVAIL","Memory not available to perform the trunk negotiation action","The system is unable to negotiate trunks because of a lack of memory.","Reduce other system activity to ease memory demands. If necessary, upgrade to a larger memory configuration."
"DTP","4","TMRERR","An internal timer error occurred when trunking on interface [char]","Occasionally a timer used by the trunking protocol expires unexpectedly. This problem is corrected internally.","This problem has no long-term ramifications. However, if further trunking problems persist, you should reload the device."
"DTP","4","UNKN_ERR","An unknown operational error occurred","The system is unable to negotiate trunks because an internal operation generated an error that the protocol (DTP, in this case) did not expect to handle.","Reload the device."
"DTP","5","DOMAINMISMATCH","Unable to perform trunk negotiation on port [char] because of VTP domain mismatch.","The two ports involved in trunk negotiation belong to different VTP domains. Trunking is possible only when the ports involved belong to the same VTP domain.","Reconfigure the switch to ensure that the two ports that are involved in trunk negotiation belong to the same VTP domain."
"DTP","5","ILGLCFG","Illegal config (on, isl--on,dot1q) on <mod/port>","The two ports on the link are set to the ON mode, but one is set to 802.1Q encapsulation, while the other is set to ISL encapsulation. When both ports on a link are set to the ON mode, their encapsulation types must match.","Configure both ports on the link to have the same encapsulation type."
"DTP","5","NONTRUNKPORTON","Port [dec]/[chars] has become non-trunk","The interface [dec] / [chars] is nontrunked. [dec] / [chars] is the module number/interface range.","This is an informational message only; no action is required."
"DTP","5","TRUNKPORTCHG","Port [dec]/[chars] has changed from [chars] trunk to [chars] trunk","The encapsulation type of the trunk changed. [dec] is the module number, the first [chars] is the interface number, the second [chars] is the original encapsulation type, and the third [chars] is the new encapsulation type.","This is an informational message only; no action is required."
"DTP","5","TRUNKPORTON","Port [dec]/[chars] has become trunk","Interface [dec] / [chars] is trunked. [dec] / [chars] is the module number/interface range.","This is an informational message only; no action is required."
"C4K_EBM","3","CANTALLOCATEEBMPORT","No EbmPort memory to allocate EbmPort for PimPort [char]","There is insufficient memory for information that is associated with the specified port.","Install additional memory."
"C4K_EBM","3","CANTALLOCATEHOSTCHECKPOINTMESSAGE","Cannot allocate memory for host checkpoint message. Layer2 host redundancy on standby will be out-of-sync with active.","There is insufficient memory to allocate space for this internal data structure.","You may need to install additional memory in both supervisor engines."
"C4K_EBM","3","CANTALLOCATEIENODE","No interposition table memory to add entry for addr %ea","There is insufficient memory for this internal data structure.","Install additional memory."
"C4K_EBM","3","CANTALLOCATEIGMPGROUPENTRY","No igmp group memory to add new group entry for addr [mac-addr]","This error occurs if you have created a large number of IGMP groups and there is insufficient memory to support additional Internet Group Management Protocol (IGMP) group entries.","Either install additional memory, or reduce the number of IGMP groups."
"C4K_EBM","3","CANTALLOCATEPORTHOSTENTRY","No port host table memory to add entry for addr [mac-addr] / [mac-addr]","There is insufficient memory for this internal data structure.","Install additional memory."
"C4K_EBM","3","CANTALLOCATEVLANGROUPENTRY","No vlan group table memory to add entry for addr %ea","There is insufficient memory to support additional Layer 2 group entries corresponding to IP multicast groups.","Install additional memory. If memory is unavailable, turn off Cisco Group Management Protocol (CGMP)/Internet Group Management Protocol (IGMP)."
"C4K_EBM","3","CANTALLOCATEVLANHOSTENTRY","No vlan host table memory to add entry for addr %ea","There is insufficient memory to support additional host addresses.","Install additional memory."
"C4K_EBM","4","HOSTFLAPPING","Host [mac-addr] in vlan [dec] is flapping between port [char] and port [char]","The specified host is detected as a source address on multiple ports. Typically, a host is supposed to be learned on only one port. A spanning tree loop is the most common cause of this condition. All traffic from the specified host is temporarily dropped. After 15 seconds, forwarding is reenabled. If the problem persists, the traffic from the problem host continues to be dropped indefinitely. As of Cisco IOS release 12.2(52)SG, this message is enabled by the mac address-table notification mac-move comand. By default, the message is disabled. If enabled, this message will be displayed whenever a host moves. To reflect the change, the text of this syslog message changes to C4K_EBM-4-HOSTFLAPPING:Host %ea in vlan %d is moving from port %s to port %s.","Make sure that spanning tree is enabled to prevent spanning tree loops. If you have spanning tree disabled, make sure that you have no spanning tree loops in your network."
"C4K_EBM","4","MAXHOSTCHKPTMESSAGEQSIZEEXCEEDED","Backlog of checkpoint message waiting to be synced to standby has exceeded pre-defined limits. The host table may become out-of-sync with active.","The active supervisor engine is overloaded and unable to synchronize host messages to the standby supervisor engine or the standby supervisor engine is not in the proper state.","Examine syslog messages from the active supervisor engine and standby supervisor engine to determine if any errors have been reported."
"C4K_EBM","4","MAXHOSTAGECHKPTMESSAGEQSIZEEXCEEDED","Backlog of host age checkpoint message waiting to be sent to active has exceeded pre-defined limits.  The host table may become out-of-sync with active.","The active is overloaded and unable to delete age host messages it received from standby or the standby is not in the proper state.","Examine syslog messages from active and standby to determine if any errors have been reported. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_EBM","4","ZEROETHERADDR","Filtering Ethernet MAC address of value zero from agent host table interface (port: [char])","The switch received a packet with the MAC address 00:00:00:00:00:00. This MAC address is not valid and was probably generated by some non-IEEE 802.1D-compliant hardware or software in the network.The host sort algorithm does not sort hosts with MAC addresses that have all zeros (00:00:00:00:00:00), because a MAC address that has all zeros can not be listed in the learned host table. A request to show learned hosts, either by the show cam dynamic command or by an SNMP request, does not list a MAC address that has all zeros.","Track the source of the invalid MAC address because it might cause other problems."
"EC","4","SSOINCOMPAT","Routed port channels cannot be  created while the switch is configured in the SSO redundancy mode","Routed port channels are not supported while the switch is configured in the SSO redundancy mode.","Switch to RPR mode or use an SVI in a VLAN where a layer 2 port channel is the only member."
"EC","4","NOMEM","Not enough memory available for [char]","The Port Aggregation Protocol or EtherChannel cannot obtain the memory it needs.","This is an informational message only; no action is required."
"EC","5","BUNDLE","Interface [char] joined port-channel [char]","The interface has joined the bundle.","This is an informational message only; no action is required."
"EC","5","CANNOT_ALLOCATE_AGGREGATOR","Aggregator limit reached","A new aggregator cannot be allocated in the group.","Change the port attributes of the ports in the group so that they match and join the same aggregator."
"EC","5","CANNOT_BUNDLE1","Port-channel [char] is down","The administrative state of the aggregation port channel is down. The port remains in a standalone state until the state of the aggregation port is up.","Ensure that all of the ports in the bundle have the same configuration."
"EC","5","CANNOT_BUNDLE2","[char] is not compatible with [char] and will be suspended ([char])","The port has different port attributes from those of the port channel (or the ports within the port channel).","Adjust the port attributes to match those of the port channel."
"EC","5","CANNOT_BUNDLE_LACP","[char] is not compatible with aggregators in channel [dec] and cannot attach to them ([char])","This port has different port attributes than other ports within the port channel.","Match the port attributes to that of the port channel."
"EC","5","CANNOT_BUNDLE_QOS","Removed [char] from port channel because a QoS policy cannot be supported across multiple DFC cards.","The port that is specified in the error message cannot join a port channel because the QoS policy that is attached to the port channel cannot support multiple DFC cards.","Place the port in another port channel, or remove the QoS policy from the port channel."
"EC","5","CANNOT_BUNDLE_QOS1","Removed [char] from port channel  as QoS attributes of port and port-channel are different.","The Port specified in the error message cannot join port channel, because the QoS attributes of this port are not consistent with the QoS attributes of the port-channel.","Match the QoS attributes of the specified port to the QoS attributes of other member ports in the port channel. Use the show queueing interface command to display the QoS attributes of a port."
"EC","5","COMPATIBLE","[char] is compatible with port-channel members","The specified interface is not operational because its attributes are different from the attributes of the port channel or the attributes of the interfaces within the port channel. The switch detects that the attributes of the specified port now match the port-channel attributes.","This is an informational message only; no action is required."
"EC","5","DONTBNDL","[char] suspended: incompatible remote port  with [char]","The configuration of the remote port is different from the configuration of the other ports in the bundle. A port can join the bundle only when the global configuration of the port and the configuration of the remote port are the same as the other ports in the bundle.","Ensure that the configuration of the remote ports is the same for all ports in the bundle."
"EC","5","ERRPROT","Channel protocol mismatch for interface [char] in group [dec]: the interface can not be added to the channel group","The interface cannot be added to the channel group with the specified mode.","Change the channel group or the mode for the interface."
"EC","5","ERRPROT2","Command rejected: the interface [char] is already part of a channel with a different type of protocol enabled","The interface cannot be selected for the specified protocol because it is already part of a channel with a different type of protocol enabled.","Remove the interface from the channel group."
"EC","5","ERRPROT3","Command rejected: the interface [char] is already part of a channel","The interface cannot be unselected for the specified protocol because it is already part of a channel.","Remove the interface from the channel group."
"EC","5","L3DONTBNDL1","[char] suspended: PAgP not enabled on the remote port.","PAgP is enabled on the Layer 3 interface, but the remote port does not have PAgP enabled. In this mode, the port is put in a suspended state.","Enable PAgP on the remote side."
"EC","5","L3DONTBNDL2","[char] suspended: LACP currently not enabled on the remote port.","LACP is enabled on a Layer 3 interface, but the remote port does not have LACP enabled. In this mode, the port is put in a suspended state.","Enable LACP on the remote side."
"EC","5","MINLINKS_MET","Port-channel [char] is up as its  bundled ports ([dec]) meets min-links","The administrative configuration of minimum links is equal or less than the number of bundled ports. Therefore this port channel has been brought up.","This is an informational message only; no action is required."
"EC","5","MINLINKS_NOTMET","Port-channel [char] is down  bundled ports ([dec]) doesn't meet min-links","The administrative configuration of minimum links is greater than the number of bundled ports. Therefore this port channel has been brought down.","Reduce the min-links configuration for this group or add more ports to this port-channel to create a bundle."
"EC","5","NOLACP","Invalid EC mode","LACP is not included in the image. You cannot set EC mode to active or passive.","Upgrade to an image with LACP, or set the mode to On."
"EC","5","NOPAGP","Invalid EC mode","PAgP is not included in the image, so the EtherChannel mode cannot be set to desirable/auto.","Obtain an image that includes PAgP, or set the mode to ON."
"EC","5","PORTDOWN","Shutting down [char] as its port-channel is admin-down","The administrative state of the aggregate port is down, which forces the administrative state of the port to also be down. The administrative state of the port is controlled by the administrative state of its aggregate port.","Enter the no shutdown command on the aggregate port to activate the aggregation port."
"EC","5","STAYDOWN","[char] will remain down as its port-channel [char] is admin-down","An interface with EtherChannel configuration cannot be administratively up if its port channel is administratively down. Although this interface has an EtherChannel configuration, it has no information about the port channel. The no shutdown command is not supported.","Wait for the module to come online."
"EC","5","UNBUNDLE","Interface [char] left the port-channel [char]","The interface fell off the bundle.","This is an informational message only; no action is required."
"EC","5","UNSUITABLE","[char] will not join any port-channel","The configurations for PortFast, VMPS, and Dest-SPAN are incompatible with EtherChannel.","Unconfigure the three features so that the port can form a bundle."
"C4K_ETH","4","MACFATALRXERR","[char] MAC was reset due to a fatal Rx error","There was an Rx error with the specified port, and the port's MAC was reset.","If this continues to happen, please contact Cisco Technical Support representative to possibly replace the supervisor."
"C4K_ETHEDC","3","INVALIDVENDOR","[char]: Invalid Edc Vendor Type: [dec]","An invalid EDC has been detected in the module.","Try resetting the module. If the message recurs, return the module for repair."
"C4K_ETHHOLE","3","NONSFPPLUSINONEXCONVERTERHOLE","Non-SFP+ inserted in port [char], which is for 10G SFP+ OneX Converter","A non-SFP+ transceiver was inserted into a OneX X2-SFP+ converter. Currently, the OneX converter can only support the SFP+ 10G transceiver, not a traditional 1G SFP transceiver.","Remove the faulty SFP-form transceiver immediately and insert a valid Cisco SFP+ 10G transceiver instead; if an SFP transceiver must be used, please use the: 'hw-module module <n> port-group <m> select gigabitethernet' command to convert the X2 port into a TwinGig port, then remove the OneX converter and insert a TwinGig Module converter instead."
"C4K_ETHHOLE","3","SFPONONEXCONVERTERBADSEEPROM","Port [char]: SFP+ on OneX Converter's seeprom is bad, try reinserting: vendor: [char], p/n: [char], s/n: [char]","An SFP Converter was detected, and the read of its serial EEPROM succeeded, but the SFP module appears invalid (perhaps due to a bad checksum). This could happen because an SFP is inserted where an SFP+ is expected. The message tells the vendor, part number and serial number read from the Converter's serial EEPROM.","Remove SFP and insert a supported 10G SFP+ module."
"C4K_ETHHOLE","3","UNSUPPORTEDEDCTYPEDETECTED","Port([char]) detected something unsupported inserted in X2 hole The OneX Converter on port [char] detected an unsupported EDC type","Informational message only. An unsupported pluggable has been detected in OneX converter","No action is required."
"C4K_ETHHOLE","3","UNSUPPORTEDTHINGINSERTEDINX2HOLE","Port([char]) detected something unsupported inserted in X2 hole","Informational message only. An unsupported pluggable has been detected in X2 hole.","No action is required."
"C4K_ETHHOLE","7","ONEXCONVERTERINSERTED","Port [char]: OneX converter inserted: vendor: [char], p/n: [char], s/n: [char] [char]","A OneX Converter was detected and its serial EEPROM read. The message shows the vendor, part number, and serial number from the OneX Converter's serial EEPROM.","No action is required."
"C4K_ETHHOLE","7","ONEXCONVERTERREMOVED","Port [char] OneX converter removed","A OneX Converter was removed from the specified X2 port.","This is an informational message only. No action is required."
"C4K_ETHHOLE","7","SFPONONEXCONVERTERINSERTED","Port [char]: SFP+ on OneX Converter inserted: vendor: [char], p/n: [char], s/n: [char]","An SFP+ was detected in a OneX Converter and the SFP+ serial EEPROM read. The message shows the vendor, part number, and serial number from SFP+ EEPROM.","This is an information message only. No action is required."
"C4K_ETHHOLE","7","SFPPLUSONONEXCONVERTERREMOVED","Port [char]: SFP+ on OneX Converter removed","An SFP+ was removed from a OneX Converter on the specified X2 port.","This is an informational message only. No action is required."
"C4K_ETHHOLE","7","X2INSERTED","Port [char]: X2 inserted: vendor: [char], p/n: [char], s/n: [char] [char], the hole [char] monitoring","Informational message only. A transceiver with a serial eeprom has been detected in the port referred to in the message, and its serial eeprom has been successfully read. The message tells the vendor, part number, and serial number, as read from the transceiver's serial eeprom.","This is a debug message only. No action is required."
"C4K_ETHHOLE","7","X2REMOVED","Port [char] X2 pluggable removed","A transceiver has been removed.","No action is required."
"C4K_ETHPHY","4","LINKMONITOR","[char]: Link Monitor detects Link state marginal, but go ahead to link up","Link Monitor on this port is detecting Link quality might be marginal.","If this problem is seen repeatedly, please double check the cable and its length to meet those cabling requirements. Also, please consider cable mitigation technique to improve the quality of the link. If port is in this state, you might see possible packet loss."
"C4K_ETHPOE","3","CONTROLLERSBRINGUPFAILED","PoE did not properly initialize for module [dec].","Power over Ethernet did not initialize properly.","Reset the module. If the problem persists, contact Cisco TAC."
"C4K_ETHPOE","4","STALLDETECTED","Module %u POE controller has detected a stall","A problem has been detected with one or more Power Over Ethernet controllers on the module.","Current POE settings should remain stable but no changes to POE can be made. The module should be reset at the next maintenance window to restore full POE functionality."
"C4K_ETHPOE","4","SUPPLYFAULT","Module %u POE controller has been shutdown because of excessive power usage.","Power over Ethernet to the module has shut down because it drew too much power.","Remove some devices. Verify that the power consumption is not over limit. Reset the module."
"C4K_ETHPORTMAN","3","INLINEPOWEROVERDRAWN","Inline powered device connected on port [char] exceeded its [char] threshold.","This message might be caused by a faulty powered device drawing more power than is allocated.","Verify that the powered device on the port is functioning properly and only drawing the configured power using the show power module command."
"C4K_ETHPORTMAN","3","TENGIGSEEPROMREADFAILED","Failed to read seeprom on port [char]. Reinsert X2 module or configure GigabitEthernet port group if TwinGigConverter is installed.","A pluggable has been detected in the TenGig port referred to in the message, but the read of its serial eeprom failed. Sometimes, the read fails because the X2 is not seated correctly. Seeprom read can also fail if the interface is in 10G mode and TwinGigConverter is inserted in the hole.","If TwinGigConverter is inserted, remove the TwinGigConverter or reconfigure the port using the command hw-module module <m> port-group <p> select gigabitethernet. If an X2 is inserted, try removing and re-inserting. If this message still appears, try the X2 in another port. If the X2 fails in another port, call TAC for further troubleshooting. If the X2 succeeds in other ports, the original port may be bad. Call TAC for further troubleshooting."
"C4K_FLASH","4","COMPACTFLASHNOTFOUND","Cannot find compact flash","You may see this message if the compact flash is not inserted properly or if it is removed while the switch is trying to access the flash.","Reinsert the compact flash and retry the operation."
"C4K_FLASH","4","COMPACTFLASHNOTREADY","Compact flash is not ready","You may see this message if the compact flash is not inserted properly or if it is removed while the switch is trying to access the flash.","Reinsert the compact flash and retry the operation."
"C4K_FLOW","4","OUTOFMEMORY","Out of memory  [char].","The software failed to allocate memory.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_GBM","3","CANTALLOCATEBRIDGEDOMAINHOSTENTRY","No bridge-domain host table memory to add entry for addr [mac-addr]","There is insufficient memory left to support additional host addresses. Previously learnt host addresses are unaffected.","If possible, free up the available memory by unconfiguring features that are no longer in use."
"C4K_GBM","4","HOSTFLAPPING","Host [mac-addr] in bridge-domain [dec] is flapping between port [char] and port [char]","The specified host is being seen as a source address on multiple ports. Normally, a host is only supposed to be learned on one port. The most common cause of this condition is spanning tree loops.","Please make arrangements such that the same MAC address does not appear in multiple service instances in a short time interval."
"C4K_GBM","4","OUTOFBRIDGEDOMAINRESOURCES","GbmSwitch: There is not sufficient memory to create the  required BridgeDomain.","The software failed to allocate memory for the required Bridge Domain. The specified bridge domain will not fuction but will appear in the configuration file. Other features and bridge domains are unaffected.","If possible, free up available memory by removing features that are no longer in use."
"C4K_GBM","4","OUTOFPSEUDOPORTRESOURCES","GbmSwitch: There is not sufficient memory to allocate","The software failed to allocate memory for a Service Instance (PseudoPort). The specified service instance will not function but will appear in the configuration file. Other features and service instances are unaffected.","If possible, free up available memory by unconfiguring features that are no longer in use."
"C4K_GBM","7","DYNLIMITREACHED","With the addition of  [mac-addr]  on  [char]   the limit for dynamic MACs has been reached. No more non-secured dynamic MACs can be learnt.","If the number of MACs in the MAC table is greater than or equal to 128K , then no more non secured dynamic MACs could be learnt.","This is a debug message only. No action is required."
"C4K_GBM","7","MACTABLEFULL","With the addition of  [mac-addr]  on  [char]   the MAC Table has been exhausted.","The size of the MAC Table is 256K. If this limit is reached, no more dynamic MAC entries can be added.","This is a debug message only. No action is required."
"C4K_GENERICSISF","4","OUTOFMEMORY","Memory for constructing ACLs is not available.","Memory for the platform ACL-related data structures is exhausted. First Hop Security will not function properly on the interface.","Free up memory on the switch by removing ACLs that are no longer needed, or upgrade the system RAM."
"C4K_GLMMAN","3","IMAGEUPGRADEERROR","Module  [dec] FPGA image  [char]","Linecard FPGA image upgrade failed.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_GLMMAN","3","NONSFPPLUSINONEXCONVERTERHOLE","Non-SFP+ inserted in port [char], which is for 10G SFP+ OneX Converter","A non-SFP+ transceiver is inserted into a OneX X2-SFP+ converter. Currently, a OneX converter can only support an SFP+ 10G transceiver, not a traditional 1G SFP transceiver.","Remove the faulty SFP-form transceiver immediately and insert a valid Cisco SFP+ 10G transceiver instead."
"C4K_GLMMAN","3","ONEXCONVERTERBADSEEPROM","Port [char]: OneX Converter's seeprom is bad, try reinserting: vendor: [char], p/n: [char], s/n: [char]","A OneX converter was detected, and the read of its serial EEPROM succeeded, but the contents are invalid (perhaps due to a bad checksum). This event can occur because the OneX converter is not seated correctly. The message shows the vendor, part number, and serial number read from the converter's serial EEPROM.","Try removing and reinserting the OneX converter. If this message still appears after that action, try inserting the converter in another port to verify that the converter is bad, not the port. If the converter fails in another port, return the converter. If the converter succeeds in other ports, it implies that the original port is bad, not the converter, and that the module needs to be returned. As a further test of the original port, try other OneX converters. If these other OneX converters also fail in that port, it is very likely that the port is bad."
"C4K_GLMMAN","3","SFPONONEXCONVERTERBADSEEPROM","Port [char]: Sfp on OneX Converter's seeprom is bad, try reinserting: vendor: [char], p/n: [char], s/n: [char]","An SFP converter was detected, and the read of its serial EEPROM succeeded, but the SFP module used was invalid for the application. This event can occur because an SFP was used where an SFP+ was expected. The message shows the vendor, part number, and serial number read from the converter's serial EEPROM.","Try removing the 1-G SFP and inserting a valid 10-G SFP+ module."
"C4K_GLMMAN","3","TWINGIGCONVERTERBADSEEPROM","Port [char]: TwinGig Converter's seeprom is bad, try reinserting: vendor: [char], p/n: [char], s/n: [char]","A TwinGig Converter has been detected, and the read of its serial EEPROM succeeded, but the contents are invalid (possibly a bad checksum). This could happen because the TwinGig Converter is not seated correctly. The message tells the vendor, part number and serial number read from the Converter's serial EEPROM.","Try removing and reinserting the TwinGig Converter. If this message still appears after that, try the Converter in another port, to verify that the Converter is bad, and not the port. If the Converter fails in another port, return the Converter. If the Converter succeeds in other ports, it implies that the original port is bad, not the Converter, and the module needs to be returned. As a further test of the original port, other TwinGig Converters could be tried. If these other TwinGig Converters also fail in that port, it is very likely that the port is bad."
"C4K_GLMMAN","3","TWINGIGCONVERTERCRCINTEGRITYCHECKFAILED","Port [char]: TwinGig Converter integrity check failed: bad crc","Only Cisco-qualified TwinGig Converters are supported. Others show as unsupported and cause the associated port to placed in faulty status. The CRC of the TwinGig Converter's SEEPROM is invalid.","Verify that the TwinGig Converter is from a Cisco-qualified source. If it is, try reinserting it. If the message still appears after that, try it in another port, to verify the Converter is bad, and not the port. If it still produces error messages, replace the TwinGig Converter."
"C4K_GLMMAN","3","TWINGIGCONVERTERIDENTFAILED","Port [char]: Failed to identify TwinGig Converter","Something is inserted in the specified port, which has been configured to accept a TwinGig Converter, an adaptor which converts an X2 port into 2 SFP ports, but it has failed the identification process.","If the object inserted in the port isn't a TwinGig Converter, remove it. If it is a TwinGig Converter, try removing and reinserting it. If the message still appears after that, try it in another port, to verify the Converter is bad, and not the port. If the Converter fails in another port, return it."
"C4K_GLMMAN","3","TWINGIGCONVERTERINTEGRITYCHECKFAILED","Port [char]: TwinGig Converter integrity check failed: bad key","Only Cisco-qualified TwinGig Converters are supported. Others show as unsupported and cause the associated ports to be placed in faulty status.","Replace the TwinGig Converter with a Cisco-qualified one."
"C4K_GLMMAN","3","TWINGIGCONVERTERS2WERROR","Port [char]: S2w error while reading status of TwinGig Converter","Internal communication error when reading TwinGig Converter status data.","Remove and reinsert the TwinGig Converter. If that doesn't solve the problem, try using the hw-module module port-group command to change to ten gigabit mode and back to gigabit mode, to reset things."
"C4K_GLMMAN","3","TWINGIGCONVERTERSEEPROMREADFAILED","Port [char]: Failed to read serial eeprom of TwinGig Converter, try reinserting","A TwinGig Converter has been detected in the X2 port referred to in the message, but the read of its serial eeprom failed. Sometimes the read fails because the TwinGig Converter is not seated correctly.","Try removing and reinserting the TwinGig Converter. If this message still appears after that, try the Converter in another port, to verify that the Converter is bad, and not the port. If the Converter fails in another port, return the Converter. If the Converter succeeds in other ports, it implies that the original port is bad, not the Converter, and the module needs to be returned. As a further test of the original port, other TwinGig Converters could be tried. If these other TwinGig Converters also fail in that port, it is very likely that the port is bad."
"C4K_GLMMAN","3","TWINGIGINX2HOLE","TwinGigConverter inserted in port [char], which is configured for X2","A TwinGig converter was inserted into an port which was configured for an X2 module.","Remove the TwinGig module or reconfigure the port for gigabit Ethernet, using the hw-module module <m> port-group <p> select gigabitethernet command."
"C4K_GLMMAN","3","X2INTWINGIGCONVERTERHOLE","X2 inserted in port [char], which is configured for a TwinGigConverter","An X2 transceiver has been inserted into an port which has been configured to accept a TwinGig Converter, an adaptor which converts an X2 port into 2 SFP ports. The X2 is a ten gigabit transceiver, and SFPs are gigabit transceivers.","Remove the X2, or reconfigure the port to ten gigabit, using the hw-module module <m> port-group select tengigabitethernet command."
"C4K_GLMMAN","3","X2PLUGGABLEBADSEEPROM","Port [char]: X2Pluggable's seeprom is bad, try reinserting: vendor: [char], p/n: [char], s/n: [char]","An X2 pluggable has been detected, and the read of its serial EEPROM succeeded, but the contents are invalid (perhaps bad checksum). This event could possibly happen because the X2 module is not seated correctly. The message tells the vendor, part number and serial number read from the module's serial EEPROM.","Try removing and reinserting the X2 module. If this message still appears after that, try the module in another port, to verify that the module is bad, and not the port. If the module fails in another port, return the module. If the module succeeds in other ports, it implies that the original port is bad, not the converter, and the module needs to be returned. As a further test of the original port, other X2 modules could be tried. If these other X2 modules also fail in that port, it is very likely that the port is bad."
"C4K_GLMMAN","3","X2PLUGGABLESEEPROMREADFAILED","Failed to read seeprom on port [char]. Reinsert X2 module or configure GigabitEthernet port group if TwinGigConverter is installed.","A pluggable has been detected in the TenGig port referred to in the message, but the read of its serial eeprom failed. It could be that the X2 is not seated correctly. A SEEPROM read can also fail if the interface is in 10G mode and a TwinGig Converter is inserted.","If a TwinGig Converter is inserted, remove the TwinGig Converter or reconfigure the port using the hw-module module <m> port-group <p> select gigabitethernet command. If an X2 is inserted, try removing and re-inserting the X2. If this message still appears, try the X2 in another port. If the X2 fails in another port, call TAC for further troubleshooting. If the X2 succeeds in other ports, the original port may be bad."
"C4K_GLMMAN","4","TWINGIGCONVERTERUNSUPPORTED","Port [char]: TwinGig Converter is unsupported","The TwinGig Converter was identified as not a Cisco-qualified Converter.","If this TwinGig Converter was purchased from Cisco, contact Cisco TAC to get it replaced."
"C4K_GLMMAN","6","IMAGEUPGRADE","Module  [dec] FPGA image  [char]","Linecard FPGA image upgraded.","This is an informational message only. No action is required."
"C4K_GLMMAN","7","ONEXCONVERTERINSERTED","Port [char]: OneX Converter inserted: vendor: [char], p/n: [char], s/n: [char]","A OneX converter was detected and its serial EEPROM read. The message shows the vendor, part number, and serial number from the OneX converter's serial EEPROM.","This is an informational message only; no action is required."
"C4K_GLMMAN","7","ONEXCONVERTERREMOVED","Port [char]: OneX Converter removed","A OneX converter was removed from the specified X2 port.","This is an informational message only; no action is required."
"C4K_GLMMAN","7","SFPONONEXCONVERTERINSERTED","Port [char]: Sfp on OneX Converter inserted: vendor: [char], p/n: [char], s/n: [char]","An SFP in a OneX converter was detected and its serial EEPROM read. The message shows the vendor, part number, and serial number from the SFP+ EEPROM.","This is an informational message only; no action is required."
"C4K_GLMMAN","7","SFPPLUSONONEXCONVERTERREMOVED","Port [char]: Sfp+ on OneX Converter removed","An SFP+ in a OneX converter was removed from the specified X2 port.","This is an informational message only; no action is required."
"C4K_GLMMAN","7","TWINGIGCONVERTERINSERTED","Port [char]: TwinGig Converter inserted: vendor: [char], p/n: [char], s/n: [char]","A TwinGig Converter has been detected and its serial EEPROM read. The message shows the vendor, part number, and serial number from the TwinGig Converter's serial EEPROM.","This is an informational message only; no action is required."
"C4K_GLMMAN","7","TWINGIGCONVERTERREMOVED","Port [char]: TwinGig Converter removed","A TwinGig Converter has been removed from the specified X2 port.","This is an informational message only; no action is required."
"C4K_HAL","3","TCAMEVMISMATCH","[char] EntryValid mismatch between sub-entries  [dec] ( [object-info] ) and  [dec] ( [object-info] ) when reading in mode  [char] in tcam with base addr  [dec]","The Forwarding TCAM's monitoring system detected a TCAM contents mismatch and repaired it.","This is an informational message only; no action is required. If this message appears repeatedly, contact Cisco technical assistance for more information."
"C4K_HAL","3","TCAMFNHMISMATCH","[char] ForceNoHit mismatch between sub-entries  [dec] ( [object-info] ) and  [dec] ( [object-info] ) when reading in mode  [char] in tcam with base addr  [dec]","The Forwarding TCAM's monitoring system detected a TCAM contents mismatch and repaired it.","This is an informational message only, no action is required. If this message appears repeatedly, contact Cisco technical assistance for more information."
"C4K_HW","3","S2WERROR","[char] [char] [dec] Error: [object-info] Device Addr: [dec] Mem Addr: [object-info] Value: [dec]","An unexpected error occurred when the switch accessed the hardware device specified in the message.","Contact your technical support representative."
"C4K_HW","3","X2IDENTIFICATIONFAILURE","Error while trying to identify serdes type for [char] ( [dec]  ) X2 module","There was an error when trying to identify the X2 module type.","Contact your technical support representative. You will probably need to replace the supervisor engine."
"C4K_HW","3","X2LOOPBACKFAILURE","Failed to put [char] Xaui([dec]) [char] loopback","Software was unable to put the X2 in or out of loopback because it was unable to determine the X2 type.","This is an informational message only; no action is required."
"C4K_HW","3","X2OUIREGREADFAILURE","Error while reading Supervisor X2 OUI register Device Addr: [dec]","There was an unexpected error when accessing a hardware device with the given device address.","Contact your technical support representative. You will probably need to replace the supervisor engine."
"C4K_HWACLMAN","4","ACLHWLABELERR","Path [obj] label allocation failure: [string] - packets will be handled in software, QoS is disabled.","A label pair could not be allocated for the specified path. This can happen because the label supply is exhausted, or because the profile supply is exhausted, or because the path requires the application of mutually-incompatible features. Packets that traverse this path will be processed in software.Note If the path includes QoS, it will be disabled on the interface.","Simplify the configuration to reduce the number of labels and profiles required, or remove the conflicting features."
"C4K_HWACLMAN","4","ACLHWPROGERR","[input/output]  [char] - hardware TCAM limit,  [char]","Some ACL-based features cannot be fully programmed into the hardware. Packets that use these features complete processing in the software. If the feature is a policy map, then QoS is completely disabled (on the specific interface).This message lists the impacted feature; further messages list the specific failure that occurred.","This is an informational message only; no action is required."
"C4K_HWACLMAN","4","ACLHWPROGERRREASON","[input/output]  [object-info] [char] -  [char]","This message provides a specific failure that prevented ACL-based features from being fully programmed into the hardware.","This is an informational message only; no action is required."
"C4K_HWACLMAN","4","CAMAUDIT","ACL/QOS CAM Health Check: [input/output]  [char] Index:  [dec] [char] (Cumulative Error Count:  [dec] )","The background system health monitor detected a potential problem.","If this is a software error, the system has already corrected itself automatically and no action is required. If this is a hardware error, power cycle the system."
"C4K_HWACLMAN","4","CAMBLOCKMASKALLOCFAILED","CAM state memory allocation failure in region [dec]","The software could not allocate memory to maintain a software copy of the Hardware Classification TCAM Masks that is used for ACL / QoS functionality.","Copy the message exactly and contact the Cisco Technical Assistance Center."
"C4K_HWACLMAN","4","CLASSIFCAMPARITYERROR","Parity error detected in  [input/output]  Classification CAM   [char] Cell  [object-info] and corrected.","The system detected and fixed a parity error in the Classification TCAM. If this error is seen repeatedly, there is a strong likelihood of a fault in the TCAM ASIC.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_HWACLMAN","4","CLASSIFCAMREPLYPARITYERROR","Parity error detected in lookup response from  [input/output]  Classification CAM, Response Contents:  [char]","The system detected a transient error in the Classification TCAM operation. If this error is seen repeatedly, there may be a fault in the switching engine ASICs. The software will attempt to fix the parity error by rewriting the TCAM entries to the hardware.","If this condition persists, contact Cisco Technical Assistance."
"C4K_HWACLMAN","4","CLASSIFCAMREQPARITYERROR","Parity error detected in lookup request to  [input/output]  Classification CAM,   Data  [char] Address  [char]","The system detected a transient error in the Classification TCAM operation. If this error is seen repeatedly, there is a strong likelihood of a fault in switching engine ASICs.","If this condition persists, contact Cisco Technical Assistance."
"C4K_HWACLMAN","4","CONFLICTACLFEATURE","Conflict Acl feature detected:  [object-info] and  [object-info]  cannot be operational on  [object-info] at the same time.  [object-info] is not operational.","The features indicated in the message share the same classification hardware resource, therefore cannot be enabled at the same time. Only one of the 2 features can be operational at any given time.","Depending on the desired behavior, remove/unconfigure one of the two conflicting features indicated in the message."
"C4K_HWACLMAN","4","FAILEDTOSWITCHVLANTAGS","Failed to switch vlan tags, old tag:  [object-info] new tag:  [object-info] . Software paths:  [dec] Hardware paths:  [dec]","Software failed to switch VLAN tags. This could be a transient error. The ACL being programmed will not become active. (The software and hardware path counts are provided for use by engineers in troubleshooting.)","Detach and reattach ACLs / QoS policies."
"C4K_HWACLMAN","4","FALSEPARITYERROR","[char] Tcam FALSE Perr - Hw index: [object-info] Hw/Sw entry:  [char]","A false parity error in a TCAM entry was detected. Contents of the software copy and hardware copy are the same for the flagged parity error TCAM entry.","This is an informational message only; no action is required."
"C4K_HWACLMAN","4","IGMPSNOOPINGNOTCAMBLOCK","IGMP snooping enabled: no usable TCAM block.","Enabling IGMP snooping features requires adding an input block to all TCAM profiles. If we are not able to find a TCAM block for this purpose, this message is emitted.","Unconfigure IGMP snooping feature, simplify the switch configuration to free up an input classification TCAM block, and reconfigure IGMP snooping."
"C4K_HWACLMAN","4","LABELMTEALLOCATIONFAILURE","Path  [object-info] label MTE allocation failure:   [object-info] - packets will be handled in software.","HW MTE could not be allocated for the path. The packet sent on the path is sent to CPU for processing. When the packet incoming rate is high, CPU load would be high due to ACL processing in software.","Reduce the number of path targets that ACL features are applied to. Path targets are port, vlan or port-vlan. ACL featues are any features that uses ACL TCAM."
"C4K_HWACLMAN","4","MACACLSBYPASSEDFORMPLSPKTS","Note:  [char] MAC ACLs are not applied to MPLS  traffic  when 'qos mpls preserve exp' is configured.","MAC ACLs are not applied for MPLS traffic in the Input and/or output direction when 'qos mpls preserve exp' is configured to retain EXP bits in the top-most label of MPLS packets.","Apply 'no qos mpls preserve exp' to apply MAC ACLs to MPLS traffic. EXP bits in the top-most label of MPLS packets are reset to 0."
"C4K_HWACLMAN","4","MACACLSENABLEDFORMPLSPKTS","Note:  [char] MAC ACLs are applied to MPLS traffic.","NOT AVAILABLE YET.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_HWACLMAN","4","MEDIANETMSPNOTCAMBLOCK","Medianet MSP: no usable TCAM block.","Medianet MSP static entries are loaded into Role Based TCAM block. If there is no TCAM block, log this message.","No TCAM resource available for Medianet MSP. MSP device and flow identification will not work."
"C4K_HWACLMAN","4","MLDSNOOPINGNOTCAMBLOCK","MLD snooping enabled: no usable TCAM block.","Enabling MLD snooping features requires adding an input block to all TCAM profiles. If we are not able to find a TCAM block for this purpose, this message is emitted.","Unconfigure MLD snooping feature, simplify the switch configuration to free up an input classification TCAM block, and reconfigure MLD snooping."
"C4K_HWACLMAN","4","MPLSEXPPRESERVENOTCAMBLOCK","MPLS EXP preservation not enabled: no usable TCAM block.","Enabling the MPLS EXP bit preservation features requires adding an output QoS block to all TCAM profiles. If we are not able to find a TCAM block for this purpose, this message is emitted.","Unconfigure the MPLS EXP preservation feature, simplify the switch configuration to free up an output classification TCAM block, and reconfigure the MPLS EXP preservation feature."
"C4K_HWACLMAN","4","PARITYERROR","[char] Tcam Perr - Hw index:  [object-info] Hw entry:  [char] Sw entry:  [char]","A parity error in a TCAM entry was detected. Contents of the log register are printed out. Software will automatically perform error recovery on the defective TCAM entry.","This is an informational message only; no action is required."
"C4K_HWACLMAN","4","PKTSAMPNOQOSREWRITENOTCAMBLOCK","Netflow-lite not enabled, no usable QoS TCAM block.","Enabling the Netflow-lite feature requires adding an output QoS block to all TCAM profiles. If we are not able to find a TCAM block for this purpose, this message is emitted.","Unconfigure the Netflow-lite feature, simplify the switch configuration to free up an output classification TCAM block, and reconfigure the Netflow-lite preservation feature."
"C4K_HWACLMAN","4","QOSFEATUREOUTOFSWRESOURCES","Out of memory.   [char] is inactive  on port  [char]","The software could not allocate memory to write the QoS related configuration to the QoS TCAM hardware. The given QoS policy configuration will not work on the given port until this is corrected.","This condition might occur under extreme ACL and/or QoS configurations. Some workarounds to attempt are:"
"C4K_HWACLMAN","4","WARNINGSTRING","[char]","See the console message for details.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_HWFLOWMAN","3","FLOWENTRYPARITYERROR","Flow entry at location  [dec] is corrupted due to  [char] parity at segment [dec]","Entry with parity is detected.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_HWFLOWMAN","4","HWFLOWLIMITREACHED","Hardware flow limit reached on label [object-info]","User configured flow limit is reached on given target.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_HWFLOWMAN","4","HWFLOWTABLEFULL","Hardware flow table is full","Hardware supports 128 * 1024 flow entries. Hardware flow table is full.","Disable the flow features on some interfaces or if flexible netflow feature is enabled, use less granular masks to alleviate the problem."
"C4K_HWFLOWMAN","4","HWIPV6ADDRESSTABLEFULL","IPv6AddressTable is full. New IPv6 flows with additional unique  IPv6 address may not be captured","Hardware supports capability to track 16 * 1024 uniqueue IPv6 addresses. Once the address table is full user will not be able to track additioinal unique IPv6 flow records.","When Flexible Netflow is enabled, exclude either source or destination IPv6 address as part of flow information to alleviate the problem."
"C4K_HWFLOWMAN","4","OUTOFFLOWTABLEMEMORY","Out of memory, unable to store flow record","System is out of memory.","Evaluate the system memory usage and perform corrective actions."
"C4K_HWFLOWMAN","5","FLOWUNACCOUNTEDPACKETS","Flow stats for [dec] packets are not accounted due to hardware hash collisions or full hardware flow table","Netflow stats are maintained in a 16 way associated hash with 8192 entries. When new entry can't be allocated either due to hash collisions or when hash table is full this error message is displayed. This is generally a rare event. Use the command show platform hardware flow table utilization to see the netflow hardware table utilization. This message periodically informs users about the total received for which flow-stats were not collected.","No action is required."
"C4K_HWL2MAN","3","STMPARITYERROR","Parity error in Spanning Tree Memory.","There is a parity error in the spanning tree memory, which can indicate a transient hardware problem or a more permanent problem.","If you see this message too often, reboot the switch. If repeated reboots are needed, contact technical support."
"C4K_HWL2MAN","4","PORTVLANMAPHASHADDITIONFAIL","Failed to add entry with  Port:  [char]  Vlan Id:  [dec]  Dir:  [char] into PortVlanMap Hash Table.","We could not store PortVlanMap information. PortVlanMap on the indicated port and VLAN will be ignored.","Remove some VLAN map configurations and reconfigure. If the problem persists, contact Cisco TAC."
"C4K_HWL2MAN","4","RSPANADJALLOCFAIL","Rspan Adjacency Allocation Failed","Allocation of a hardware adjacency for an RSPAN destination session failed. The session will not work as intended.","Remove the configuration of other adjacencies to free memory resources, and try again."
"C4K_HWL2MAN","4","RXSPANACLFEATURERESOURCEFAIL","RxSpan Acl Feature Resource Failure for session  [dec]","Allocation of ACL TCAM resources to support a local SPAN session failed. Untagged packets mirrored by the session will be sent out the VLAN id 0 destination port.","Free memory by removing the configuration of other ACL-based features that are no longer needed."
"C4K_HWL2MAN","6","MACLEARNFAIL","Encountered  [dec] hardware MAC address table  programming failures within  [dec] seconds.","New MAC entries that were learned in software cannot be programmed into the hardware. This happens when a hardware Layer 2 address table bucket is full. This situation does not affect MAC learning in software or programming other new MAC entries whose buckets are not full. The switch will program these entries into hardware as soon as the corresponding buckets are freed. This is an inherent system limitation. This message is most likely to occur when a hardware MAC address table is highly utilized.","This is an informational message only; no action is required. You may decide to free resources by changing the hardware aging time with the mac address-table aging-time n command"
"C4K_HWMAN","4","OCV6ICMPFILTERERR","Hardware limitation, output Ipv6 Acl based on Icmp type and  Icmp code won't work properly for certain Ipv6 Flow Label","This is a hardware limitation, for output Ipv6 Acl to filter properly on Icmp type and Icmp code, source V6 address field can not be used in the Acl at the same time.","This is an informative message; no further actions are necessary."
"C4K_HWNETFLOWMAN","3","NETFLOWSTOPPED","Too many netflow parity errors encountered. It is very likely that this is bad Netflow hardware. Stopping all netflow related activities.","The supervisor engine received too many parity errors from the NetFlow Services Card. The supervisor engine stops all NetFlow-related activities after issuing this message.","Contact your technical support representative."
"C4K_HWNETFLOWMAN","4","ERRORADDRS","Netflow Fatal Error Info: Interrupt Status ( [dec] ),  FDT1 Err Addr ( [dec] ),  FDT2 Err Addr ( [dec] ),  FLD Err Addr ( [dec] )","A fatal NetFlow error occurred. The message contains critical information that can help you determine if the NetFlow hardware is functioning properly or is bad.","Contact your technical support representative."
"C4K_HWNETFLOWMAN","4","FATALERRORINTERRUPTSEEN","Netflow Fatal Error interrupt seen","The NetFlow Services Card sent a fatal interrupt call to the supervisor engine, which can crash the service card, the supervisor engine, and the entire switch. This condition is extremely rare.","Contact your technical support representative."
"C4K_HWNETFLOWMAN","4","FLOWSLOSTERR","Netflow stats lost either due to hardware hash collisions  or full hardware flow table.  [char] [dec] packets.","Netflow stats are maintained in a 16 way associated hash with 8192 entries. When new entry can't be allocated either due to hash collisions or when hash table is full this error message is displayed. This is generally a rare event. Use the command show platform hardware netflow statistics utilization to see the netflow hardware table utilization. This message periodically informs users about the total received for which flow-stats were not collected. Depending on the message, sometime an accurate count of total lost flows is not available. This can happen if the HW counter that tracks the lost stats has itself overflowed.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_HWNETFLOWMAN","4","HARDWAREUNRESPONSIVE","Netflow Hardware too slow in responding to software requests","Software tried to access NetFlow hardware but there was no response. Typically this would indicate that the NetFlow related hardware may have gone bad.","Contact your technical support representative."
"C4K_HWNETFLOWMAN","4","NOFREEFLOWPOLICERS","[dec] flow based policers are in use. All available flow  policers are in use. Can't allocate more number of flow policers","The maximum number of flow policers that can be allocated by the system is 512. This message is displayed when the user tries to exceed that limit.","Free existing flow policers before trying to define new ones."
"C4K_HWNETFLOWMAN","4","NONFATALPARITYERRORINTERRUPTSEEN","Netflow Non Fatal Parity Error interrupt seen ( [dec] times)","The supervisor engine received a nonfatal parity error from the NetFlow Services Card. The system should be able to recover from this condition. If this condition reoccurs often, the NetFlow Services Card is probably bad.","This is an informational message only; no action is required."
"C4K_HWNETFLOWMAN","4","SWAGEDENTRYHWINVALIDATIONFAILED","Invalidation failed for Hw flow (index:  [object-info] ) associated with sw active-aged flow","Software tried to access NetFlow hardware, but there was no response. Typically this would indicate that the NetFlow related hardware may have gone bad.","Contact your technical support representative."
"C4K_HWPORTMAN","3","DFETRAININGHANDSHAKETIMEOUT","DFE timeout: [char]","As a link comes up, both ends of the link go through a handshake to train respective receivers. If either end times out, it indicates h/w failure. The failure may be transient (due to some noise) or persistent.","Not expected to happen. If it does occur, indicates hardware failure. To recover, pullout and re-insert the linecard. If that does not help, try rebooting the switch. If it still fails, need to contact Cisco TAC or Escalation and report the failure along with the message printed."
"C4K_HWPORTMAN","3","MISCONFIGUREDPORTSET","Portset mis-configured: [char]","A portset was configured to an illegal mode (not supported for that portset), or a speed setting on a superport is inconsistent with superport group mode.","Capture output for the show module and show platform mapping port commands, and contact technical support immediately."
"C4K_HWPORTMAN","3","PHYPORTALLOCATION","Phyport allocation failed!!","Insufficient phyports are available for allocation to the superport from the phyport pool for the slot. This can occur due to fragmentation of the phyport ID space. The switching module in this slot will be unusable until the switch is rebooted.","Enter the show tech-support command and the show platform software phy command to gather data that may help identify the nature of the error. Reboot the switch. Enter the show platform mapping port command and the show platform software phy command. If the problem persists, contact your technical support representative. Provide them with the output you have collected."
"C4K_HWPORTMAN","3","SUPERPORTPORTSETTOOMANYERRORINTERRUPT","[char]","An error was detected for a superport group. Contents of the log regster are printed out. This is probably a transient hardware issue affecting a single packet in transit through the switch.","This is an informative message. No further actions are necessary."
"C4K_HWPORTMAN","3","TXQUEALLOCFAILED","LocalPhyport  [dec]  [char]","A problem was encountered in allocation of transmit queue space to the queues of the port. If this happened in response to a policy configuration, the new policy does not take effect. If it happened with the insertion of a switching module, the module cannot be used to transmit traffic.","Capture output from the show tech-support command, the show platform mapping port command, the show platform software phy command and the show platform software qm command to gather data that may help identify the nature of the error. Reboot the switch. Repeat capturing output from these commands. If the problem persists, contact your technical support representative. Provide them with the output you have collected."
"C4K_HWPORTMAN","3","TXQUEDRAINFAILURE","Failed to drain phyport transmit queues on pool  [dec]","Transmit queues of ports on a switching module pool did not drain and queue space was not released. The pool may not map exactly to a slot. If this happened in response to a policy configuration, the new policy does not take effect. If it happened with the insertion of a switching module, the module cannot be used to transmit traffic.","Enter the show tech-support command and the show platform software qm command to gather data that may help identify the nature of the error. If the problem persists, contact your technical support representative."
"C4K_HWPORTMAN","4","BLOCKEDTXQUEUE","Blocked transmit queue HwTxQId[dec] on [char], count=[dec]","This rate-limited message indicates that a transmit queue and traffic on a port is blocked. You may see the blocked transmit queue message if the supervisor engine is not able to send packets to the switching module because it received a busy bit from the switching module. A hardware failure or a speed/duplex mismatch can cause this problem.","Configure both sides of the link to autonegotiate for speed and duplex. Check if pause is in effect, resulting in the queue being blocked, Issue the shut/no shut command to recover the port. If the problem persists, move the connected device to another port and see if the problem happens there. If neither of these solves the problem, issue the hw-module reset command in order to reboot the switch and reset the line card."
"C4K_HWPORTMAN","4","CHECKFORDUPLEXMISMATCHANDPAUSE","[char] Tx-Queue could be blocked due to duplex mismatch or receiving excessive pause frames","The TxQueue on this port could be blocked due to a duplex mismatch or from receiving too many pause frames.","Use the show interface <name> count all command to verify the excessive collisions and pause frame counters. Duplex mismatch problems can be fixed by configuring both ends of a link in auto-negotiate mode. It can also be fixed by turning off auto-negotiation on both ends of the link and ensuring that the duplex configuration on both ends is the same. Excessive pause frames are not expected under normal conditions. If they occur, investigate on the other end of the link to address the problem. After fixing the problem, the port's TxQueue status can be checked by using the show platform hardware interface <name> tx command. The results will indicate whether one or more TxQueue's on this port are still stuck or working properly. If this message is seen when the duplex settings are correct, contact your technical support representative."
"C4K_HWPORTMAN","4","GIGAPORTRESETBYRXCONFIGWORD","[char] has been reset by the received autonegotiation word.","The port stayed connected during switchover, but the device on the other end of the link lost synchronization and restarted autonegotiation.","This is an informational message only; no action is required."
"C4K_HWPORTMAN","4","PORTSETPLLLOCK","SuperportGroup %u PLL has not locked! status [hex]. Proceeding further ...","Insufficient phyports are available for allocation to the superport from the phyport pool for the slot. If it happened with the insertion of a switching module, the module cannot be used to receive and transmit traffic.","Reinsert the linecard or reboot the switch. If the problem persists, contact your technical support representative. Enter the show tech-support command to gather data that may help identify the nature of the error."
"C4K_HWPORTMAN","4","SUPERPORTPORTSETERRORINTERRUPT","[char]","An error was detected for a superport group. Contents of the log regster are printed out. This is probably a transient hardware issue affecting a single packet in transit through the switch.","This is an informatve message; no further actions are necessary."
"C4K_HWPORTMAN","4","SUPERPORTPORTSETTXUNDERRUNINTERRUPT","[char]","A txUnderRun error was detected for a superport group. Contents of the log regster are printed out. This is probably a transient hardware issue affecting a single packet in transit through the switch.","This is an informatve message; no further actions are necessary."
"C4K_HWPORTMAN","4","SUPERPORTRESETBYRXCONFIGWORD","[char] has been reset by the received autonegotiation word.Recommended Action    The port stayed connected during switchover, but the device on the other end of the link lost synchronization and restarted autonegotiation.Recommended Action    Investigate at the link partner side, the problem is probably on that end. If the problem persists, contact your technical support representative.HWPORTMAN-7Error Message    C4K_HWPORTMAN-7-DROPPORTSHUTDOWNSTATUS: DropPort based traffic Suppression  [char] %llu","Indicates traffic suppression due to drop port threshold being exceeded in the VFE. Traffic is suppressed to help relieve drop port queue congestion. It may mean that the drop Q size was not set correctly.","This is an informational message only; no action is required."
"C4K_HWPORTMAN","7","FLOWCONTROLPACKET","Received invalid flow control packet from [char] da [mac-addr] sa [mac-addr] ethertype [hex] opcode [hex]","The switch forwarded a malformed flow control packet to the software. Hardware forwards flow control packets to software if one or both of the ethertype and flow control or opcode are incorrect. The expected ethertype for flow control packets is 0x8808. The expected opcode for flow control packets is 1 (xoff). If devices connected to the switch are capable and configured to generate flow control, verify that the devices generate well-formed flow control packets with valid opcode and ethertype fields.","This is a debug message. No action is required."
"IDBMAN","3","AGGPORTMISMATCH:[char]","[char]([dec] / [dec]) does match internal slot/port state [char]([dec] / [dec])","Due to an internal error the software is using an invalid aggregate port.","This is an informational message only; no action is required."
"IDBMAN","3","DELETEDAGGPORT","[char]([dec] / [dec]) Group [dec] has been deleted","Software is reusing a deleted interface for a new aggregate port.","This is an informational message only; no action is required."
"IDBMAN","3","IIF_ID_REGISTRATION_FAILED","IIF_ID registration failed for Port [char] due to memory allocation failure. The port has been shutdown.","The IIF-ID registration failed because the system is low on available memory. This results in a failure to apply polices such as QoS and Security ACLs on this port.","Reduce other system activities to ease memory demands. If feasible, add more system memory."
"IDBMAN","3","INVALIDAGGPORTBANDWIDTH","[char]([dec] / [dec]) has an invalid bandwidth value of [dec]","Software is using an invalid bandwidth for an aggregate port.","This is an informational message only; no action is required."
"IDBMAN","3","INVALIDPORT:[char]","trying to use invalid port number [dec] (Max [dec])","Software is using an invalid port number.","This is an informational message only; no action is required."
"IDBMAN","3","INVALIDVLAN:[char]","trying to use invalid Vlan [dec]","Software is using an invalid VLAN.","This is an informational message only; no action is required."
"IDBMAN","3","NOTANAGGPORT","[char]([dec] / [dec]) is not an aggregate port","Software is using an interface that is not an aggregate port for aggregate port operations.","This is an informational message only; no action is required."
"IDBMAN","3","PORTNOTINAGGPORT","[char]([dec] / [dec]) is not present in Aggport [char]([dec] / [dec])","Software recognizes that the invalid port belongs to an aggregate port.","This is an informational message only; no action is required."
"IDBMAN","3","VLANINUSE:[char]","Vlan [dec] is in use by [char]","Each Layer 3 interface has a VLAN that is associated with it. This message appears when some other Layer 3 interface is using the VLAN associated with the interface.","This is an informational message only; no action is required."
"IDBMAN","3","VLANNOTSET:[char]","Vlan [dec] not set since it already has Vlan [dec]","Due to a software error, an interface's VLAN was set to a nonrequested value.","This is an informational message only; no action is required."
"IDBMAN","4","ACTIVEPORTSINAGGPORT","[char]([dec] / [dec]) has [dec] active ports","Software has mistakenly removed an aggregate port with active ports.","This is an informational message only; no action is required."
"IDBMAN","4","REMOVED_NONDEFAULT_CONFIG","Removed non default configuration for interfaces in slot [dec]","In SSO mode, the non-default configuration for any removed switching module is not synchronized to the standby supervisor engine during the bulk synchronization, and it is removed from the configuration to avoid a configuration mismatch between active and standby supervisor engines.","This is an informational message only; no action is required."
"IDBMAN","6","VLANMAPPED","Vlan [dec] is mapped to [char]","The given VLAN was mapped to the specified interface.","This is an informational message only; no action is required."
"C4K_IOSACLMAN","4","ACLTYPEMISMATCH","Acl RkiosSharedIos[char] was earlier attached as [char] Acl. Please unconfigure all its uses before using it as a [char] Acl","This message displays if you attach a named ACL as one type, delete the ACL, and configure an ACL of a different type with the same name. For example, you configure a named IP ACL using the name DefaultAcl, attach it to a router port, and then delete the ACL DefaultAcl by entering no ip access-list extended DefaultAcl. You could configure a MAC ACL using the same name. This message is displayed when you try to configure any ACEs in the MAC ACL.","Remove all configurations where the ACL is used as an IP ACL before configuring a MAC ACL with the same name."
"C4K_IOSACLMAN","4","EPMOUTOFMEMORY","Memory for constructing ACLs is not available.Recommended Action    System memory is not available to set up new dynamic host policies. New host policies will not work if this log message is seen.Recommended Action    Free up memory on the switch by removing any ACLs that are no longer needed. Alternately, upgrade the system RAM if possible.Error Message    C4K_IOSACLMAN-4-IPV6FLAGSNOTSUPPORTED: IPv6 flag matching is not supported.","Matching on IPv6 flags is not supported. IPv6 flags will be ignored, as though they had not been configured.","Reconfigure ACLS to use supported match criteria."
"C4K_IOSACLMAN","4","VLANMAPOUTOFMEMORY","Could not add an entry to Vlan Map [char]. Out of memory","The system has insufficient memory to allocate a new entry for this VLAN map.","Remove all configurations where the ACL is used as an IP ACL before configuring a MAC ACL with the same name."
"C4K_IOSDIAGMAN","4","CANNOTRUNTESTMODULENOTREADY","Cannot run the diag test as module is under reset","The requested online diagnostic test cannot be run because the required hardware module is in the reset cycle.","Wait for the module to come back online and resend the test request."
"C4K_IOSDIAGMAN","4","CANNOTRUNTESTNOTPORTFAILEDBOOTUP","Cannot run the diag test as port failed bootup tests","The online diagnostic test requested cannot be run on this port because the port failed bootup tests.","Investigate why the bootup tests have failed on the port. The module or the port may be damaged."
"C4K_IOSDIAGMAN","4","TESTNOTSUPPORTEDONMODULE","[char] is not supported on this module","The online diagnostic test requested is not supported on this module.","If the diagnostic test is required, consider upgrading to hardware that supports the test."
"C4K_IOSDHCPSNOOPMAN","4","CANNOTADDNEWIPLIST","Cannot add new IP list for dhcp security on [char] and vlan [dec]","The switch attempted to add a new IP address to the list of permitted IP addresses but failed. The new addresses are not permitted.","This is an informational message only; no action is required."
"C4K_IOSDHCPSNOOPMAN","4","CANNOTENABLESECURITY","Cannot enable dhcp security on [char] and vlan [dec]","The switch failed to enable IP source guard on the interface and indicated VLAN. This error probably occurred because there might be too many interface-VLAN pairs that have the feature enabled.","This is an informational message only; no action is required."
"IP_PORT_SECURITY","4","DENY_INVALID_PACKET","Detected and dropped illegal traffic  on port [char] and vlan [dec] the non-cumulative packet dropped count is [dec].","IP Port Security only permits traffic with the correct source IP to MAC binding on the port or VLAN. There may be a malicious host trying to carry out a denial of service attack using another host's source address. The illegal traffic is dropped by the IP Port Security feature.","Identify the source of the illegal traffic and stop it."
"IP_SOURCE_GUARD","4","DENY_INVALID_PACKET","Detected and dropped illegal traffic  on port [char] and vlan [dec] the non-cumulative packet dropped count is [dec].","IP Source Guard only permits traffic with the correct source IP to MAC binding on the port or VLAN. There may be a malicious host trying to carry out a denial of service attack using another host's source address. The illegal traffic is dropped by the IP Source Guard feature.","Identify the source of the illegal traffic and stop it."
"C4K_IOSFNFMAN","4","FNFMONITORLIMIT","Configuration of  [dec] flow monitors is allowed","System allows upto 2048 flow monitors to be configured at a given point of time.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_IOSIGMPSNOOPMAN","3","NOSPACELEFT","No igmp group memory to add new group entry","There is insufficient memory to support additional IGMP group entries, which are added automatically when you run CGMP or IGMP.","Install additional memory, or reduce the number of IGMP groups."
"C4K_IOSINTF","3","SUBINTERFACEVLANALLOCFAIL","Failed to allocate internal VLAN for interface [char].  The interface will remain down. Please delete and re-create the  subinterface after freeing another subinterface.","When a subinterface is created, it must allocate an internal VLAN to operate. If there are no internal VLANs available when an interface is enabled, the interface remains down and this message is logged.","Free up an internal VLAN by deconfiguring a different subinterface. Then, delete and re-configure the subinterface flagged in this message."
"C4K_IOSINTF","3","VNETTRUNKVLANALLOCFAIL","Failed to allocate internal VLAN for interface [char].  The interface will remain down. Please unconfigure this vnet trunk","When a vnet trunk is created, it must allocate an internal VLAN to operate. If there are no internal VLANs available when an interface is enabled, the interface remains down and this message is logged.","Free up an internal VLAN by deconfiguring a different subinterface. Then, delete and re-configure the subinterface flagged in this message."
"C4K_IOSINTF","4","DYNAMICPOLICYMEMOVERFLOW","Dynamic policy memory exhausted - [char] policy for host %i on port [char]  not applied.","The memory allocated for dynamic host policies (dynamic ACLs and URL redirection) has been completely used. The policy for the host and interface specified is not fully applied by the platform. Traffic from the host on that interface may hit the default PACL instead.","Reduce either the number of hosts on the system with dynamic host policies or the size of the dynamic policies being applied."
"C4K_IOSINTF","4","FIBNULLHWIDB","Missing hwidb for fibhwidb [char] (ifindex [dec])","An internal software error occurred.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_IOSINTF","4","INTVLANALLOCFAIL","Failed to allocate internal VLAN for interface [char]. The interface will remain down.","When a routed port or port channel interface is enabled, it must map to an internal VLAN in order to operate. If there are no internal VLANs available when an interface is enabled, the interface remains down and this message is logged.","An internal VLAN can be freed by disabling some other routed port or port channel interface or by deleting a user-configured VLAN in the 1006 to 4094 range. Once a VLAN is made available, the interface will come up if it is disabled and reenabled."
"C4K_IOSINTF","4","REFLEXIVEACLNOTSUPPORTED","Reflexive Acls are not supported. Ignoring the [char] entry.","The reflexive ACLs are not supported. ACEs with the evaluate and reflect keywords are ignored.","Do not configure ACEs with the evaluate or reflect keywords."
"C4K_IOSINTF","5","FA1DISABLED","Management interface disabled","The management port has been disabled because it is not supported on the peer supervisor.","This is an informational message only; no action is required."
"C4K_IOSINTF","5","FA1ENABLED","Management interface enabled","The management port has been re-enabled as it is now supported on the peer supervisor or because the peer supervisor has now been reloaded or removed.","This is an informational message only; no action is required."
"C4K_IOSINTF","5","INCORRECTSRCMAC","Source mac ([mac-addr]) in the packet matches the source mac of the router/VRRP/HSRP mac on interface [char]","The client that is authenticating has a reserved source MAC address. This can occur when a client MAC address is misconfigured, or when the system is under attack.","Block the MAC address and investigate the source device."
"C4K_IOSINTF","5","LMPHWSESSIONSTATE","Lmp HW session [char] on slot [dec] port [dec].","LMP hardware keepalive timed out.","This is an informational message only; no action is required."
"C4K_IOSINTF","5","NOPRIMARYVLANASSOCIATION","Packet received on interface [char] in vlan [dec]  without primary vlan association. [mac-addr] will not be secured.","The switch received a packet on a secondary VLAN which does not have a primary VLAN association. The switch will not secure a MAC address in this situation.","Associate this secondary VLAN with a valid primary VLAN."
"C4K_IOSINTF","5","NOTXVLAN","Router Port [char] has no internal vlan assigned to transmit packet","The specified Layer 3 interface does not have an assigned internal VLAN because duplicate IP network assignments exist on different Layer 3 interfaces.","Remove the duplicate IP network that is configured on the interface. Assign the correct IP network, and enter the no shutdown command on this interface."
"C4K_IOSINTF","5","OUTPACLDISABLEDUETORACL","Output PACL [char] is disabled on port [char]","Output RACL and output PACL is mutually exclusive. If the port is enabled in some SVI that has output RACL configured, then the output PACL on the port is disabled.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_IOSINTF","5","OUTPACLDISABLEDUETOVACL","Output PACL [char] is disabled on port [char]","If the port is configured for a VLAN that has output RACL, then the output PACL on the port is disabled. Output RACL and output PACL are mutually exclusive, it is not possible to configure both simultaneously.","This is an informational message only; no action is required."
"C4K_IOSINTF","5","RJ45ACTIVE","Slot= [dec] Port= [dec]:  RJ45 connector has become active","A dual media port changed from using the SFP connector to using the RJ-45 connector.","This is an informational message only; no action is required."
"C4K_IOSINTF","5","RJ45INACTIVE","Slot= [dec] Port= [dec]: RJ45 connector has become inactive","A dual media port changed from using the RJ-45 connector to the SFP connector.","This is an informational message only; no action is required."
"C4K_IOSINTF","5","STALEPHYPORT","Dropping packets to be transmitted out on port [char]  ( Linecard in Slot [dec] may have been removed )","During hot-swapping operations a previously queued packet may be transmitted after a switching module is removed. This indicates such packets are being dropped.","If this message appears without any hot swapping, contact your technical support representative."
"C4K_IOSINTF","5","TRANSCEIVERINSERTED","Slot=[dec] Port=[dec]: Transceiver has been inserted","An approved vendor transceiver has been inserted.","This is an informational message only; no action is required."
"C4K_IOSINTF","5","TRANSCEIVERREMOVED","Slot=[dec] Port=[dec]: Transceiver has been removed","An approved vendor transceiver has been removed.","This is an informational message only; no action is required."
"C4K_IOSINTF","5","TXL3PKTONPHYPORT","Transmitting L3 packet on a physical port [char] that is part of [char] ([dec] packets). Make sure the physical port in the L3 port channel does not have an ip addresses configured on it.","Layer 3 protocols operate at the logical, not the physical, port level. Layer 3 protocol packets were sent on a physical port that is part of a bundle. This condition occurs if there is a misconfiguration; a physical port that is part of a Layer 3 port channel might have been assigned an IP address.","Verify that the physical interface in the Layer 3 port channel does not have an IP address that is assigned to it."
"C4K_IOSINTF","5","TXPKTDROPONETHERCHANNEL","Dropping transmit packet out of interface [char]","A packet that should be transmitted out of a port channel was dropped during transitions in the port channel membership. This condition occurs when a packet is transmitted out of the aggregate port by higher layer protocols, but the software cannot find the specific state information or when physical ports transition into or out of the port channel membership.","If the problem persists, contact your technical support representative."
"C4K_IOSIPROUTEMAN","3","ADJMANNOMOREADJS:AdjMan","hardware adjacency resources exhausted, performance may be degraded.","The hardware adjacency resources have been exhausted. The supervisor engine will forward packets to this adjacency in the software. This action will likely represent a significant performance degradation.","Reduce the number of adjacencies that are loaded into the routing table, and then clear the IP routing table."
"C4K_IOSIPROUTEMAN","3","FIBCANTALLOCATEFIBADJ","IOS IP Route Manager:No memory available to allocate FIB Adjacency for [object-info]","The switch does not have sufficient memory to allocate space for this adjacency; the supervisor engine will forward it in the software instead.","Reconfigure the network so that there are fewer hosts that are directly adjacent to the Catalyst 4500 series switch, and then clear and reload all of the routes (or reboot) so that the adjacent hosts that were being sent to the software get reloaded."
"C4K_IOSIPROUTEMAN","3","FIBCANTALLOCATEFIBENTRY","IOS IP Route Manager:No memory available to allocate FIB Entry for [ip-addr]","The switch has insufficient memory to allocate space for the route that is associated with this network.","Contact your technical support representative because memory leaks might exist."
"C4K_IOSIPROUTEMAN","3","PBRDOESNOTSUPPORTQOS","Route-map ' [char]100  ' on interface ' [char]  ' specifies Quality of Service rewriting which is not supported via Policy-Based Routing on this platform.  Please use the Quality of Service feature instead.  This action on the specified route map will be ignored.","The switch does not support QoS services that are implemented using PBR route maps. The PBR route map that is specified will be loaded, but references to QoS services will be ignored.","Use the QoS policy maps and class maps to configure this feature."
"C4K_IOSIPROUTEMAN","3","VRFMANNOMOREVRFS","VrfMan: VPN routing forwarding resources exhausted.","The VPN routing forwarding resources have been exhausted.","Reduce the total number of VPNs in the switch."
"C4K_IOSIPROUTEMAN","3","WCCPINVALIDMASKASSIGNMENTTABLE","Invalid mask assignment table received for WCCP service group  [char]","The number of distinct masks in the new mask assignment table is more the maximum number supported for a service group on the switch. The new table is discarded. Since a valid mask assignment table is not available anymore, the service group cannot redirect traffic. All the traffic that was expected to be redirected is now routed normally.","Make sure that the cache engine is correctly configured to send a valid mask assignment table to the switch."
"C4K_IOSIPROUTEMAN","4","WCCPMAXACTIVESERVICEGROUPCOUNTEXCEEDED","WCCP service group  [char]  is not  supported as maximum active service groups count,  [dec] has been reached.","Once maximum active service groups count is reached, new service groups will not be supported.","To enable this service group, unconfigure an active service group, unconfigure and reconfigure this service group."
"C4K_IOSIPROUTEMAN","4","WCCPSERVICEGROUPDISABLEDONCEINTERFACE","WCCP output redirection for a service  group is not supported on its CE facing interface. Hence service group  [char]  output redirection  is disabled on  [char]","WCCP egress redirection for a service group is not supported on its CE facing interface.","To enable output redirection, remove CE from this interface, and unconfigure and reconfigure the service group output redirection on the interface."
"C4K_IOSIPROUTEMAN","4","WCCPUNCHANGEDMASKASSIGNMENTTABLE","Mask assignment table update received but the table has not changed for WCCP service group [char]","The service group has received a new mask assignment table identical to the current table. This could be due to a misconfiguration on the content engine side. The table change indication will be ignored and the service group continues to use the current table for redirection.","Check the configuration on the content engine side to make sure that this unnecessary update does not get sent. If the configuration looks correct and the content engine is not sending the same table repeatedly but you still see this message, contact your technical support representative."
"C4K_IOSL2MAN","3","VLANCREATIONERROR","Unable to create new vlan [dec]","The switch does not have sufficient memory to allocate new VLANs, so the new VLAN allocation failed.","Contact your technical support representative because memory leaks might exist."
"C4K_IOSL3MAN","3","ACLFEATURECREATIONERROR","Unable to create acl feature entries for  interface [char]","The switch has run out of memory it uses for allocation of ACL feature entries, so new ACL feature entry allocation has failed.","Alter or remove configuration on the switch to reduce the number of ACLs and overall memory in use."
"C4K_IOSMODPORTMAN","2","CRITICALTEMP","Chassis temperature is at or over critical threshold - current temp: [dec]C, critical threshold: [dec]C","Chassis temperature is above a critical threshold. If some action is not taken immediately to cool down the chassis then the system will be shut down to prevent damage to hardware.","Make sure the switch environment is in the appropriate temperature range, and that the fan tray is working properly. You may need to disable some modules or features temporarily until the cause of the temperature problem is found."
"C4K_IOSMODPORTMAN","2","MODULECRITICALTEMP","Module [dec] Sensor [char] temperature is at or over critical threshold - current temp: [dec]C, critical threshold: [dec]C","Module temperature is above critical threshold. If some action is not taken immediately to cool down the module then the module will be shut down to prevent damage to hardware.","Try removing and reinserting the module. If the problem persists, replace the module."
"C4K_IOSMODPORTMAN","2","MODULESHUTDOWNTEMP","Module [dec] Sensor [char] temperature is at or over shutdown threshold - current temp: [dec]C, shutdown threshold: [dec]C","The module temperature is above the shutdown threshold. If some action is not taken immediately to cool down the module then the module will be shut down to prevent damage to hardware.","Try removing and reinserting the module. If the problem persists, replace the card."
"C4K_IOSMODPORTMAN","2","MODULETEMPUNDERSHUTDOWN","Module [dec] Sensor [char] temperature is now under shutdown threshold but still very high - current temp: [dec]C, shutdown threshold: [dec]C","A module temperature has dropped to below shutdown threshold.","The module may still be above the critical threshold. Carefully inspect it to see what is wrong."
"C4K_IOSMODPORTMAN","2","SHUTDOWNTEMP","Chassis temperature is at or over shutdown threshold - current temp: [dec]C, shutdown threshold: [dec]C","Chassis temperature is above the shutdown threshold. If some action is not taken immediately to cool down the chassis then the system will be shut down to prevent damage to hardware.","Make sure the switch environment is in the appropriate temperature range, and that the fan tray is working properly. You may need to disable some modules or features temporarily until the cause of the temperature problem is found."
"C4K_IOSMODPORTMAN","2","TEMPUNDERSHUTDOWN","Chassis temperature is now under shutdown threshold but still very high - current temp: [dec]C, shutdown threshold: [dec]C","The chassis temperature has dropped to below the shutdown threshold.","The chassis may still be above the critical threshold. Carefully inspect it to see what is wrong."
"C4K_IOSMODPORTMAN","3","SPANCONFIGOUTOFMEMORY","RkiosSpanMan: Out of memory. Unable to process information for RkiosSpanMan: ID. [dec]","The system ran out of memory.","Contact your technical support representative."
"C4K_IOSMODPORTMAN","3","SSOMODULEREADYTIMEOUT","Internal event: timed out after [dec] iterations waiting for the slot [dec] to become ready.","There is an internal logic error. The state of this switching module's ports will not be synchronized to the standby supervisor engine.","This is an informational message only; no action is required."
"C4K_IOSMODPORTMAN","3","UNKNOWNPOWERSUPPLY","Unsupported Power Supply has been inserted in slot [dec]","An unsupported or unknown power supply was inserted.","Replace the power supply with a supported power supply."
"C4K_IOSMODPORTMAN","4","AFANTRAYBAD","Fan tray [dec] has failed.","Afan tray has failed.","Replace or repair the fan tray as soon as possible."
"C4K_IOSMODPORTMAN","4","AFANTRAYGOOD","Fan tray [dec] is okay","A failed fan tray has been fixed.","No action required."
"C4K_IOSMODPORTMAN","4","AFANTRAYPARTIALFAILURE","A fan or thermistor/s in system fan tray [dec] have failed","A fan or thermistor/s in the system fan tray have failed.","Fix or repair the fan tray. The system is not presently impacted."
"C4K_IOSMODPORTMAN","4","AFANTRAYREMOVED","Fan tray [dec] has been removed","The fan tray has been removed.","Informational only."
"C4K_IOSMODPORTMAN","4","CLOCKMODULEFAULTY","Clock module switched to  [dec]  reason [char] for more info use the cmd:'show environment status clock'","The clock module is faulty and may have to be replaced.","Contact your technical support representative to confirm that replacing the clock module is necessary."
"C4K_IOSMODPORTMAN","4","FANTRAYBAD","Fan tray has failed","The fan tray failed.","Replace the fan tray as soon as possible."
"C4K_IOSMODPORTMAN","4","FANTRAYGOOD","Fan tray is okay","The fan tray passed all tests and is operating normally.","This is an informational message only; no action is required."
"C4K_IOSMODPORTMAN","4","FANTRAYPARTIALFAILURE","A fan or thermistor/s in system fan tray have failed","This is a warning message indicating that one or more fans or thermal sensors in the system fan tray have failed.","Schedule a time to replace the fan tray soon. System performance should not be immediately affected."
"C4K_IOSMODPORTMAN","4","FANTRAYREMOVED","Fan tray has been removed","The fan tray was removed.","This is an informational message only; no action is required."
"C4K_IOSMODPORTMAN","4","INLINEPOWEROVERMAX","Inline power exceeds max threshold:Module status changed to 'Pwr Max'","The measured PoE usage is higher than the module's physical limit. This situation can be caused by misconfiguration or by one or more unauthorized appliances drawing more PoE than allocated. In installations with a 1400 W DC power supply, this warning can be a false positive. Refer to bug id CSCef49715.","Make sure that the right amount of PoE is allocated to each device. If the PoE allocation is correct, remove powered devices one at a time and see if the power usage decreases as expected. (You can use the show power detail command to see the PoE allocated to the module and the PoE used.) If the power usage decreases sharply when a device is disconnected, chances are that this device is using more PoE than allocated. Avoiding using this device should solve your problem. If after disconnecting all the devices on the module, the PoE usage is still high, and the system does not use 1400 W DC power, contact your technical support representative."
"C4K_IOSMODPORTMAN","4","INLINEPOWEROVERWARNING","Module [dec] inline power exceeds threshold: status changed to 'Pwr Over'","The measured PoE usage is higher than the module's physical limit. This situation can be caused by misconfiguration or by one or more unauthorized appliances drawing more PoE than allocated. In installations with a 1400 W DC power supply, this warning can be a false positive. Refer to bug id CSCef49715.","Make sure that the right amount of PoE is allocated to each device. If the PoE allocation is correct, remove powered devices one at a time and see if the power usage decreases as expected. (You can use the show power detail command to see the PoE allocated to the module and the PoE used.) If the power usage decreases sharply when a device is disconnected, chances are that this device is using more PoE than allocated. Avoiding using this device should solve your problem. If after disconnecting all the devices on the module, the PoE usage is still high, and the system does not use 1400 W DC power, contact your technical support representative."
"C4K_IOSMODPORTMAN","4","INLINEPOWERSUPPLYBAD","Inline power from power supply [dec] has failed or been turned off","A PoE source from a power supply failed or was turned off. The hardware cannot make a distinction between the two cases.","Verify that the incoming power is good, and if it is replace the power supply as soon as possible."
"C4K_IOSMODPORTMAN","4","MODULETEMPHIGH","Module [dec] Sensor [char] temperature is at  or over threshold - CurrentTemp: [dec]C, Threshold: [dec]C","The module temperature is above its threshold. If the temperature goes above critical threshold, another message will be logged and the system will shut down to prevent damage to hardware.","Inspect the module and find out why it is heating up."
"C4K_IOSMODPORTMAN","4","MODULETEMPUNDERCRITICAL","Module [dec] Sensor [char] temperature is now under critical threshold but still very high - current temp: [dec]C, critical threshold: [dec]C","This message is sent when a module temperature returns to below critical threshold.","This is an informational message only; no action is required. The module temperature may still suggest a problem with the module."
"C4K_IOSMODPORTMAN","4","NFLABSENT","Netflow Services Card absent or idprom invalid on [char] supervisor.","The recommended configuration for using the NetFlow Services Card is to have it installed on both the standby and active supervisor engines. Otherwise, during switchover, the system might lose its NetFlow capabilities.","Verify that the NetFlow Services Card is installed on both supervisor engines."
"C4K_IOSMODPORTMAN","4","NFLIDPROMINVALID","Netflow Services Card has invalid idprom on [char] supervisor","The IDPROM on the NetFlow Services Card on the supervisor engine indicated in the message is invalid.","Contact your technical support representative."
"C4K_IOSMODPORTMAN","4","NFLMISMATCH","Netflow Services Cards have mismatched [char]. ([dec] on [char] and [dec] on [char]).","The IDPROM attributes of the NetFlow Services Cards installed on the active and the standby supervisor engines do not match.","Verify that the NetFlow Services Card is correctly installed on both supervisor engines."
"C4K_IOSMODPORTMAN","4","PEMBAD","Power Entry Module has failed","The external power supply source providing PoE power is bad.","Check the external power supply and replace it, if necessary. This message is most likely to occur in a system using a 1400 W DC power supply and an external power shelf providing DC current to the DC power supply."
"C4K_IOSMODPORTMAN","4","POWERSUPPLYBAD","Power Supply [dec] has failed or been turned off","A power supply failed or was turned off. The hardware cannot make a distinction between the two cases.","Replace the power supply as soon as possible."
"C4K_IOSMODPORTMAN","4","POWERSUPPLYFANBAD","Fan of power supply [dec] has failed","A power supply fan failed.","Replace the power supply as soon as possible."
"C4K_IOSMODPORTMAN","4","POWERSUPPLYINPUTOFF","Input [dec] on Power Supply [dec] has been turned off or has failed.","A power supply input is not delivering power, which could be due to switching it off, power failure, or some failure in the power supply. This message is only displayed for power supplies that have multiple inputs.","Verify that the input power is functioning and that the on/off switch is set to on. If the input is good and the switch is already on, the status LED on the power supply should be green. If it is red or off, the power supply itself may have been damaged and may need to be replaced."
"C4K_IOSMODPORTMAN","4","POWERSUPPLYOUTPUTDECREASED","Power supply [dec] output has decreased","The power supply output decreased. This could be due to switching it off, power failure, or some failure in the power supply.","This is an informational message only; no action is required."
"C4K_IOSMODPORTMAN","4","POWERSUPPLYREMOVED","Power supply [dec] has been removed","The power supply was removed.","This is an informational message only; no action is required."
"C4K_IOSMODPORTMAN","4","SSOMODULEOLDVERSION","Received stale acknowledgement for the linecard in slot [dec]: expected [dec], received [dec].","This is most probably the result of a linecard being rapidly removed and reinserted.","This is an informational message only; no action is required."
"C4K_IOSMODPORTMAN","4","TEMPHIGH","Chassis temperature is at or over threshold - CurrentTemp: [dec]C, Threshold: [dec]C","The chassis temperature is above the threshold. If the temperature goes above a critical threshold, another message is logged and the system shuts down to prevent damage to the hardware.","Inspect the chassis and environment to determine the cause of the rise in temperature. Cool the system."
"C4K_IOSMODPORTMAN","4","TEMPUNDERCRITICAL","Chassis temperature is now under critical threshold but still very high - current temp:  [object-info] C, critical threshold: [object-info] C","The chassis temperature is now below the critical threshold. The chassis is still operating above the normal temperature.","Inspect the chassis to determine the cause of the temperature problem. Cool the system."
"C4K_IOSMODPORTMAN","6","AFANTRAYINSERTED","Fan tray [dec] has been inserted.","A fan tray was inserted.","Informational only. No action is required."
"C4K_IOSMODPORTMAN","6","AFANTRAYINSERTEDDETAILED","Fan tray [dec] ([char] S/N: [char] Hw: [dec].[dec]) has been inserted.","A fan tray was inserted.","Informational only. No action is required."
"C4K_IOSMODPORTMAN","6","BEACONALREADYOFF","Beacon is already off.","Informational only.","Informational only. No action is required."
"C4K_IOSMODPORTMAN","6","BEACONALREADYON","Beacon is already on.","Informational only.","Informational only. No action is required."
"C4K_IOSMODPORTMAN","6","BEACONTURNEDOFF","Beacon has been turned off.","Informational only.","Informational only. No action is required."
"C4K_IOSMODPORTMAN","6","BEACONTURNEDON","Beacon has been turned on.","Informational only.","Informational only. No action is required."
"C4K_IOSMODPORTMAN","6","BEACONTURNOFFFAILED","Beacon turn off activity failed.","Informational only.","Informational only. No action is required."
"C4K_IOSMODPORTMAN","6","BEACONTURNONFAILED","Beacon turn on activity failed.","Informational only.","Informational only. No action is required."
"C4K_IOSMODPORTMAN","6","CLOCKSWITCHOVER","Chassis Clock Module switched to Clock: [dec]","This indicates that the clock module switched over to another clock.","This is an informational message only; no action is required."
"C4K_IOSMODPORTMAN","6","FANTRAYINSERTED","Fan tray has been inserted","The fan tray was inserted.","This is an informational message only; no action is required."
"C4K_IOSMODPORTMAN","6","FANTRAYINSERTEDDETAILED","Fan tray ([char] S/N: [char] Hw: [dec].[dec]) has been inserted","The fan tray was inserted.","This is an informational message only; no action is required."
"C4K_IOSMODPORTMAN","6","INLINEPOWEROK","Inline power within limits:Module status changed to 'Ok'","The measured PoE is now below the configured value and the physical limit for the module.","This is an informational message only; no action is required."
"C4K_IOSMODPORTMAN","6","INLINEPOWERSUPPLYGOOD","Inline power from power supply [dec] is Ok","The PoE power supply just inserted in [dec] is functioning normally.","This is an informational message only; no action is required."
"C4K_IOSMODPORTMAN","6","MODULEINSERTED","Module [dec] is inserted","A module was inserted into slot [dec].","This is an informational message only; no action is required."
"C4K_IOSMODPORTMAN","6","MODULEOFFLINE","Module [dec] is offline","The specified module is offline.","This is an informational message only; no action is required."
"C4K_IOSMODPORTMAN","6","MODULEONLINE","Module [dec] ([char] S/N:[char] Hw:[dec].[dec]) is online","The specified module is online.","This is an informational message only; no action is required."
"C4K_IOSMODPORTMAN","6","MODULEREMOVED","Module [dec] is removed","A module was removed from slot [dec].","This is an informational message only; no action is required."
"C4K_IOSMODPORTMAN","6","MODULETEMPOK","Module [dec] Sensor [char] temperature is now ok - CurrentTemp: [dec]C, Threshold: [dec]C","This message is sent when module temperature returns back to normal.","This is an informational message only; no action is required."
"C4K_IOSMODPORTMAN","6","PACKETMEMORYERRORPOWERCYCLE","Supervisor power cycled due to packet memory errors","This supervisor engine was power cycled to get rid of SRAM errors detected in the packet memory. It is expected that the transient SRAM errors in packet memory are cleared by a power cycle of a supervisor engine.","Contact your technical support representative."
"C4K_IOSMODPORTMAN","6","PACKETMEMORYERRORSOFTRESET","Supervisor soft reset due to packet memory errors","This supervisor engine was reset because it encountered SRAM errors in the packet memory. It was soft reset either because it does not have self power cycle capability or the switch is operating in SSO mode.","Contact your technical support representative."
"C4K_IOSMODPORTMAN","6","PEMGOOD","Power Entry Module has been restored to working condition","The external power supply source providing PoE is working correctly.","This is an informational message only; no action is required."
"C4K_IOSMODPORTMAN","6","POWERSUPPLYFANGOOD","Fan of power supply [dec] is okay","A failed power supply was fixed.","This is an informational message only; no action is required."
"C4K_IOSMODPORTMAN","6","POWERSUPPLYGOOD","Power supply [dec] is okay","A failed power supply was fixed.","This is an informational message only; no action is required."
"C4K_IOSMODPORTMAN","6","POWERSUPPLYINPUTON","Input [dec] on Power Supply [dec] has been turned on.","A power supply input has been turned on. This message is only displayed for power supplies with multiple inputs.","This is an informational message only; no action is required."
"C4K_IOSMODPORTMAN","6","POWERSUPPLYINSERTED","Power supply [dec] has been inserted","The specified power supply was inserted.","This is an informational message only; no action is required."
"C4K_IOSMODPORTMAN","6","POWERSUPPLYINSERTEDDETAILED","Power supply [dec] ([char] S/N: [char] Hw: [dec].[dec]) has been inserted","A power supply was inserted.","This is an informational message only; no action is required."
"C4K_IOSMODPORTMAN","6","POWERSUPPLYOUTPUTINCREASED","Power supply [dec] output has increased","The indicated power supply output increased.","This is an informational message only; no action is required."
"C4K_IOSMODPORTMAN","6","TEMPOK","Chassis temperature is now ok - CurrentTemp: [dec]C, Threshold: [dec]C","The chassis temperature is now normal.","This is an informational message only; no action is required."
"C4K_IOSQOSMAN","4","FAILTOCONSTRUCTQOSACTION","Software failed to process the QoS actions specified in   the policy map  [char] when attaching it to the target.","The software was unable to process the actions specified in the service policy. This could be because the maximum number of supported QoS targets was reached. The QoS policy will still be applied but no QoS action will be taken until resources are freed on from other QoS targets.","Check if the service policy on other targets can be detached in order to free up some resources."
"C4K_IOSREDUNDANCYMAN","3","CHECKPOINTMESSAGESENDFAILURE","RkiosCheckpointMan:Message send failure (client:[char])","There was an internal error when allocating resources for the checkpoint facility.Error Message    C4K_IOSREDUNDANCYMAN-3-CHECKPOINTREGISTERSESSIONFAILED: RkiosCheckpointMan: Error registering session (client:[char])Explanation    internal error initializing checkpoint facility","This is an informational message only; no action is required."
"C4K_IOSREDUNDANCYMAN","3","CHECKPOINTSTARTNEGOTIATIONFAILED","RkiosCheckpointMan: Error starting session (client:[char])","Internal error initializing checkpoint facility.","This is an informational message only; no action is required."
"C4K_IOSREDUNDANCYMAN","3","CHECKPOINTUNREGISTERSESSIONFAILED","RkiosCheckpointMan: Error unregistering session (client:[char])","Internal error on checkpoint facility.","This is an informational message only; no action is required."
"C4K_IOSREDUNDANCYMAN","3","NEWCHECKPOINTCLIENTFAILED:RkiosCheckpointMan","Error adding new client (client:[char], error:[dec])","There was an internal error when allocating resources for the checkpoint facility.","This is an informational message only; no action is required."
"C4K_IOSREDUNDANCYMAN","3","NEWCLIENTREGISTRATIONFAILED","RkiosRedundancyMan:Error adding new client (client:[char], error:[dec])","There was an internal error when allocating resources for the redundancy facility.","This is an informational message only; no action is required."
"C4K_IOSSYS","2","EVENTSCHEDULINGFAILED","Event scheduling failed due to malloc failure","Software missed scheduling of an event because it ran out of free memory.","Restart the switch as soon as possible, and contact Cisco technical support if the message appears again."
"C4K_IOSSYS","3","BLANKSTARTUPCONFIG","Blank or invalid startup-config","An empty or invalid startup-config file was found in the NVRAM. The switch is booting up with default settings.","Configure the switch and save the configuration to NVRAM as the startup file for the next reboot. If the problem persists, contact your technical support representative."
"C4K_IOSSYS","3","SAVEPOSTRESULTFAILED","Failed to save POST results to [char]. [char].","The system cannot save the POST results to bootflash because the bootflash memory might be full.","Check if the bootflash memory is full. If the bootflash memory is full, delete the old POST results by entering the delete \force post* and the squeeze bootflash: commands."
"C4K_IOSSYS","4","BLANKPRIVATECONFIG","Blank or invalid private-config","An invalid private-config is found in the NVRAM, or the private-config was missing.","If this message comes up after a software upgrade, try saving the configuration again and reboot the switch. If the message goes away in the next boot, then it can be ignored. If this message displays each time that the switch is rebooted, contact your technical support representative."
"C4K_IOSSYS","4","CONSOLESPEEDCHANGEFAILED","Console speed cannot be changed from IOS","Console speed cannot be changed by altering the config register value in IOS.","The new config register value will be applied except for console speed. To change console speed, update config register in ROMMON."
"C4K_IOSSYS","4","USEBACKUPSTARTUPCONFIG","Invalid primary startup-configRecommended Action    Blank or invalid starup-config is found in the NVRAM. The device is booting up with default settings.","Configure the device and save the configuration in the NVRAM as the startup-config for the next reboot. If this message persists even after saving startup-config in the NVRAM prior to rebooting, please contact your Cisco Technical Support representative.IOSSYS-7Error Message    C4K_IOSSYS-7-INVALIDVALUE: [char] Type [dec] not handled returning a default of 0Explanation    This message is used by developers only and should not occur during customer operation.","Contact your technical support representative."
"C4K_IOSSYS","7","SETENVERR","Failed to set environment variable: [char].","The system cannot write the specified environment variable because the bootflash memory or NVRAM has insufficient memory.","Clear the unnecessary environment variables by entering the clear platform environment variable unsupported command, and then reboot your switch."
"C4K_IOSSYSMAN","0","FATALERRORCRASH","Forced crash due to: [char]","The system is unusable due to software or hardware failures.","Analyze the memory dump, if any, and determine the cause of the failure, or contact your technical support representative."
"C4K_IOSSYSMAN","3","ENVVARNAMETOOLONG","Name of environment variable","The environment variable name is too long.","Enter the unset command to shorten the name."
"C4K_IOSSYSMAN","3","OUTOFPACKETHEADERS","Cannot allocate buffer for a packet header","The system cannot allocate a buffer for the packet header.","Contact your technical support representative, and provide the configuration information for the switch."
"C4K_IOSSYSMAN","4","ENVVARTOOLONG","Value of env. variable [char] is too long","The software writes certain configuration values to the NVRAM. The variable name is too long (greater than 4096 bytes) for the available storage space.","Boot the system into ROMMON mode. At the ROMMON prompt, enter the unset command to change the environment variable name to a shorter name."
"C4K_IOSSYSMAN","4","NOSPACEFORENVVAR","Env. variable [char] cannot be set: no space","The software writes certain configuration values to the NVRAM. The switch has insufficient memory to write an environment variable.","Boot the system into ROMMON mode. At the ROMMON prompt, enter the unset command to remove the unused environment variables to reclaim the space."
"C4K_IPROUTEMAN","3","CANTALLOCATEIPETHERADDRENTRY","IP Route Manager:No memory to add Router Port MAC Address, numInUse: [dec]","Each router port in the system can listen to secondary MAC addresses as the 'router's MAC address,' which is a process that is useful for protocols like Hot Standby Routing Protocol (HSRP). The system does not have sufficient memory to hold a secondary MAC address.","Boot the switch into ROMMON mode. At the ROMMON prompt, enter the unset command to remove the unused environment variables to reclaim the space."
"C4K_IPROUTEMAN","3","FIBADJMANDUPLICATEADJ","FIB Entry:Tried to create a duplicate adj for key [object-info]","A request was made to add a duplicate adjacency to the Forwarding Information Base (FIB) adjacency database.","This is an informational message only; no action is required."
"C4K_IPROUTEMAN","3","FIBADJMANINUSEDELETION","FIB Adjacency Manager:Attempted to delete FIB Adjacency Id [dec] which is in use","A request was made to delete an adjacency from the Forwarding Information Base (FIB) database while that adjacency was still referenced by a routing table entry.","This is an informational message only; no action is required."
"C4K_IPROUTEMAN","3","FIBADJMANNONEXISTENTDELETION","FIB Adjacency Manager:Attempted to delete FIB Adjacency Id [dec] which does not exist","A request was made to delete an adjacency from a platform Forwarding Information Base (FIB) that does not exist.","This is an informational message only; no action is required."
"C4K_IPROUTEMAN","3","FIBDUPLICATEENTRY:FIB","Attempt to create a duplicate FIB Entry for [ip-addr]","A request to add a duplicate routing table entry to the Forwarding Information Base (FIB) database was detected.","This is an informational message only; no action is required."
"C4K_IPROUTEMAN","3","FIBENTRYNOSUCHADJTODELETE","FIB Entry:Couldn't delete adj [ip-addr] from FIB Entry [ip-addr], no such adj.","A request was made to delete an adjacency from a routing table entry in the platform Forwarding Information Base (FIB), and the adjacency was not found.","This is an informational message only; no action is required."
"C4K_IPROUTEMAN","3","FIBENTRYTOOMANYADJ:FIBEntry","FIB Entry: Too many adjacencies on FIB Entry for [ip-addr], tried to add adj  [ip-addr]","A request was made to add another adjacency to a routing table entry in the platform Forwarding Information Base (FIB) when that entry was already at the maximum allowed value.","This is an informational message only; no action is required."
"C4K_IPROUTEMAN","3","FIBLOADBALANCEMANDUPLICATE","FIB: Attempt to create duplicate Lo ad-balance entry for  [object-info]","A request to add a duplicate load-balance entry was detected.","This is an informational message only; no action is required."
"C4K_IPROUTEMAN","3","FIBLOADBALANCEMANNONEXISTENT","FIB: Attempt to delete non-existent Load-balance entry with  [object-info]","A request was made to delete a non-existent load-balance entry.","This is an informational message only; no action is required."
"C4K_IPROUTEMAN","3","FIBNONEXISTENTDELETION:FIB","Attempted to delete FIB Entry Id [dec] which does not exist","A request was made to delete a nonexistent routing table entry from the platform Forwarding Information Base (FIB).","This is an informational message only; no action is required."
"C4K_IPROUTEMAN","3","NOMOREK2FIBADJS:K2FibUnicast","no more K2FibAdjs available, using punt adj instead for [ip-addr] route.","The hardware resources for adjacencies have been exhausted; switching will take place in the software instead. The switch performance might be degraded.","This is an informational message only; no action is required."
"C4K_IPROUTEMAN","3","VRFMANDUPLICATEVRF","Tried to create a duplicate VRF for key  [object-info]","A request was made to add a duplicate VRF.","This is an informational message only; no action is required."
"C4K_IPROUTEMAN","3","VRFMANNONEXISTENTDELETION","Attempted to delete VRF with key  [object-info] which does not exist","A request was made to delete a VRF that does not exist.Error Message    This is an informational message only; no action is required.Error Message    C4K_IPROUTEMAN-3-WCCPMALLOCFAILURE: WCCP service group  [char]   could not be setup  for redirection due to memory allocation failure.Explanation    The service group cannot be set up for redirection in hardware because of failure to allocate memory. The traffic that is expected to be redirected by this service group will be routed normally. This condition might occur under extreme ACL, QoS, PBR, VRF, or other L2/L3 feature configurations.","Try removing the unused or unneeded configuration on the switch before attempting to configure the service group again. Note that even though the service group configuration shows up in the CLI, it has failed to be set up in hardware. Therefore, the service group should be unconfigured before configuring it again. If the above does not help, contact Cisco Technical Assistance for further troubleshooting and resolution of the problem."
"C4K_IPROUTEMAN","4","CANTALLOCATEFIBENTRY","FIB: No memory available to allocate FIB Entry","The switch has insufficient memory to allocate space for the route that is associated with this network.","Install additional memory."
"C4K_IPROUTEMAN","4","CANTALLOCATEMFIBENTRY","FIB: No memory available to allocate MFIB Entry","The switch has insufficient memory to allocate space for the route that is associated with this network.","Install additional memory."
"C4K_IPROUTEMAN","4","CANTALLOCATEMFIBRPSLOT","No RP slots available","There are no rendez-vous point (RP) slots available for allocation, only 7 protocol independant multicast rendez-vous points may be configured at a time and they are already configured.","This is an informational message only; no action is required.If the new RP is necessary, one of the others already configured will need to be unconfigured first."
"C4K_IPROUTEMAN","4","MFIBMAXINTERFACESIZE","MFIB: Reached maximum number of MFIB interfaces available","There are no more MFIB interfaces available. The switch has allocated the maximum number of MFIB interfaces available in software.","Alter the configuration to eliminate unneeded MFIB interfaces."
"C4K_IPROUTEMAN","4","PORTWCCPSERVICEGROUPNOTENABLED","WCCP service group  [char]  is not enabled on the  interface as maximum service groups enabled count,  [dec] has been reached.","Once maximum service groups are enabled on the interface, new service groups will not be enabled.","To enable this service group, unconfigure a service that is enabled on the interface, and unconfigure and reconfigure this service group."
"C4K_IPROUTEMAN","4","PORTWCCPSERVICEGROUPNOTENABLEDONCEINTERFACE","WCCP output redirection for a service  group is not supported on its CE facing interface. Hence service group  [char]  output redirection  is not enabled on  [char]","WCCP egress redirection for a service group is not supported on its CE facing interface.","To enable output redirection, remove CE from this interface, and unconfigure and reconfigure the service group output redirection on the interface."
"C4K_IPROUTEMAN","4","VRFMANCANTALLOCATEVRF","No memory available to allocate VRF for key  [object-info]","The switch has insufficient memory to allocate space for VRF.","Install additional memory."
"C4K_K5IPSLA","3","STTOOMANYPARITYERRORS","[char]","An excessive number of errors in the Medianet Packet Generator Module of the Snowtrooper FPGA were detected in a short time. Software will automatically reboot the supervisor. This could be a permanent hardware problem.","If the problem persists after the software reboots the supervisor, contact Cisco TAC."
"C4K_K5IPSLA","4","MPGINTERRUPT","[char]","An error in the Medianet Packet Generator was detected. Contents of the log register are printed out. This could be a parity error in a table that software is capable of correcting or a fatal error.","If this message is a fatal error, contact Cisco TAC. Otherwise, no further actions are necessary."
"C4K_K5NETFLOWLITE","3","FRFATALPARITYERROR","[char]","An fatal error in the Netflow-lite Module of Forerunner FPGA were detected in a short time. Software will automatically reboot the supervisor. This could be a permanent hardware problem.","If the problem persists after the software reboots the supervisor, contact Cisco TAC support."
"C4K_K5NETFLOWLITE","3","FRTOOMANYPARITYERRORS","[char]","An excessive number of errors in the Netflow-lite Module of Forerunner Fpga were detected in a short time. Software will automatically reboot the supervisor. This could be a permanent hardware problem.","If the problem persists after the software reboots the supervisor, contact Cisco TAC support."
"C4K_K5NETFLOWLITE","3","OUTOFINITMEMORY","Out of Memory while initializing packet sampling Acl/Qos   resource for  [char]","The software failed to allocate memory for the given object during initializing packeting sampling related Acl/Qos feature.","This is a serious problem, please contact your Cisco Technical Support representative with your configuration. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_K5NETFLOWLITE","3","TATTOOMANYPARITYERRORS","[char]","An excessive number of errors in the Netflow-lite Module of Tatooine Fpga were detected in a short time. Software will automatically reboot the supervisor. This could be a permanent hardware problem.","If the problem persists after the software reboots the supervisor, contact Cisco TAC support."
"C4K_K5NETFLOWLITE","4","OUTOFMEMORY","Out of Memory while allocating Acl/Qos resource for  [char]","The software failed to allocate memory for the given object during creating packeting sampling related Acl/Qos feature, because the configuration exceeded its maximum limit. At this point the packet sampling feature using this ACL will not work. If it is required that the feature work normally, remove other unwanted features that require ACLs and retry the operation. If there are no features using ACLs that can be removed, contact your Cisco Technical Support representative with your configuration","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_L2MAN","6","INVALIDSOURCEADDRESSPACKET","Packet received with invalid source MAC address ( [mac-addr]  ) on port [char]   in vlan  [dec]","A packet was received with an all zero or a multicast source address. The packet is treated as invalid and no learning is done. Excessive flow of such packets can waste CPU cycles. This message is rate-limited and is displayed only for the first such packet received on any interface or VLAN. Subsequent messages will display cumulative count of all such packets received in given interval on all interfaces.","Check the switch configuration file to find the source of these packets on the specified port and take corrective action to fix them at the source end. You can also enable port security on that interface to shutdown the port if the incoming rate of packets with invalid source mac address is too high by issuing the switchport port-security limit rate invalid-source-mac <rate> command."
"C4K_L3HWFORWARDING","2","FWDCAMFULL","L3 routing table is full. Switching to software forwarding.","The hardware routing table is full; forwarding takes place in the software instead. The switch performance might be degraded.","Reduce the size of the routing table. Enter the ip cef command to return to hardware forwarding."
"C4K_L3HWFORWARDING","3","FLCMANCONSISTENCYCHECKFAILED160BITENTRY","consistency check failed for FLC tcam at index [dec] should be [object-info] actual is [object-info] repair status is [char]","The Forwarding TCAM's monitoring system detected a TCAM contents mismatch and repaired it.","This is an informational message only; no action is required. If this error persists, please contact TAC for more information."
"C4K_L3HWFORWARDING","3","FLCMANCONSISTENCYCHECKFAILED320BITENTRY","consistency check failed for FLC tcam at index [dec] should be [object-info] actual is [objectinfo] repair status is [char]","The Forwarding TCAM 's monitoring system detected a TCAM contents m ism atch and repaired it.","This is an informational message only; no action is required. If this error persists, please contact TAC for m ore inform ation."
"C4K_L3HWFORWARDING","3","FLCMANCONSISTENCYCHECKFAILED80BITENTRY","consistency check failed for FLC tcam at index [dec] should be [object-info] actual is [object-info] (note that 'actual' data m ay only be valid for entries where EntryValid is true) repair status is [char]","The Forwarding TCAM 's monitoring system detected a TCAM contents m ism atch and repaired it.","This is an informational message only; no action is required. If this error persists, please contact TAC for more information."
"C4K_L3HWFORWARDING","3","FLCMANRANOUTOFSHUFFLESTATE","Hardware L3 TCAM manager: ran out of shuffle state","Internal hardware manager data structures are corrupted. This may indicate a very serious problem.","Contact Cisco technical assistance if this message is ever seen."
"C4K_L3HWFORWARDING","3","FTECONSISTENCYCHECKFAILED","FwdTableEntry Consistency Check Failed: index  [dec]","There was a consistency check failure. If this error occurs frequently, it could indicate faulty hardware.","If the problem persists, contact your technical support representative."
"C4K_L3HWFORWARDING","3","FWDCAMCONSISTENCYCHECKFAILED","FwdCam Consistency Check Failed: index  [dec]","There is a FwdCam consistency check failure. If this error occurs frequently, it could indicate faulty hardware.","C4K_L3HWFORWARDING-4-FLTCAMFALSEPARITYERROR:"
"C4K_L3HWFORWARDING","3","FWDMEMPARITYERROR","Parity error in Forwarding Memory","There is a parity error in forwarding memory. This error message could indicate a transient hardware problem or a more permanent problem.","If you see this message multiple times, reboot the switch."
"C4K_L3HWFORWARDING","3","FWDSELMANHARDWAREMISMATCH","Hardware FwdSelMan: WARNING: mismatch between hardware and  software shadow state in the FwdSel Table.   [char]","There is a discrepancy between the hardware and software FwdSel tables, this may result in misforwarded packets.","Contact CiscoTAC."
"C4K_L3HWFORWARDING","3","MASKTABLECONSISTENCYCHECKFAILED","MaskTable Consistency Check Failed: block  [dec]","There was a mask table consistency check failure. If this error occurs frequently, it could indicate faulty hardware.","This is an informational message only; no action is required."
"C4K_L3HWFORWARDING","3","MASKTABLEREGIONCONSISTENCYCHECKFAILED","MaskTable Consistency Check Failed: region  [object-info]","There is a consistency check failure in the mask table. The error is located in the region that is specified by [object-info].","This is an informational message only; no action is required."
"C4K_L3HWFORWARDING","3","NOMOREK2FIBADJS","No hardware adjacency resource available for route [ip-addr]","The hardware adjacency table has insufficient memory to allocate the adjacency set for this route. Forwarding will take place in the software instead.","This is an informational message only; no action is required."
"C4K_L3HWFORWARDING","3","PBRBLOCKFAILEDTOADDFLATACE:K2FibPbrBlock","failed to add FlatAce  [object-info] to block  [dec]","The policy-routing data structures are corrupted. This memory corruption will probably crash the switch soon.","Contact your technical support representative."
"C4K_L3HWFORWARDING","3","PBRBLOCKFAILEDTODELETEFLATACE:K2FibPbrBlock","failed to remove FlatAce  [object-info] from block  [dec]","The policy-routing data structures are corrupted. This memory corruption will probably crash the switch soon.","Contact your technical support representative."
"C4K_L3HWFORWARDING","3","PBRFLATTENINGFAILED","Software resource exhaustion trying to load route-map  for interface  [char]  ( [dec]  ), elapsed time is  [object-info] us","The switch has insufficient memory to process the access list for a route map.","This is an informational message only; no action is required."
"C4K_L3HWFORWARDING","3","PBRNOPBRCAMLEFT","K2FibPbr: attempted addition of  [dec] blocks to PBR cam region failed, only managed to get  [dec] for FRM  [char]","There is insufficient memory to program a new route map.","Remove unused portions of the configuration to free the needed memory."
"C4K_L3HWFORWARDING","3","PBRPUNTINGPORT","Policy routing exceeded maximum TCAM usage, all IP unicast  traffic on interface  [char]  will be switched in software.","The hardware policy-based routing forwarding engine has insufficient resources to handle the route map for the specified interface. All unicast IP traffic for that interface will be switched in the software instead.","This is an informational message only; no action is required."
"C4K_L3HWFORWARDING","3","RPFVLANMAXEXCEEDED","Maximum number of RPF vlans exceeded in hardware for route  [ip-addr]","This software release supports a maximum of 4 RPF vlans for hardware-based unicast RPF. Packets arriving on additional VLANs may be dropped incorrectly.","In order to ensure correct forwarding of packets, reconfigure the switch so that no more than four VLANs are required."
"C4K_L3HWFORWARDING","3","WCCPMALLOCFAILURE","WCCP service group  [char]   could not be setup  for redirection due to memory allocation failure.","The service group cannot be setup for redirection in hardware because of failure to allocate memory. The traffic that is expected to be redirected by this service group will be routed normally. This condition might occur under extreme ACL, QoS, PBR, VRF, or other L2/L3 feature configurations.","Try removing the unused or unneeded configuration on the switch before attempting to configure the service group again. Note that even though the service group configuration shows up in the CLI, it has failed to be set up in hardware. Therefore, the service group should be unconfigured before configuring it again. If the above does not help, contact Cisco Technical Assistance for further troubleshooting and resolution of the problem."
"C4K_L3HWFORWARDING","4","FLCMANVFEFLINTERRUPTVALID","FL Interrupt with non-zero valid bit [char]","A parity error in the Very-Fast Forwarding Engine's Forwarding Lookup M odule was detected. Contents of the log register are printed out. This situation could be a transient hardware issue affecting a single packet in transit through the switch or a parity error in a table entry that software is capable of correcting.","This is an informational message only; no action is required."
"C4K_L3HWFORWARDING","4","FLOWCACHEOUTOFSPACEFORFLOWCACHEENTRY","K2FibFlowCache: insufficient space to store flow of type  [object-info] with label  [packet-info]","The software cannot load a flow cache entry into the hardware due to insufficient memory.","This is an informational message only; no action is required."
"C4K_L3HWFORWARDING","4","FLTCAMFALSEPARITYERROR","[char] Hw index: [object-info] Hw/Sw entry: [char]","The Forwarding TCAM 's m onitoring system found a parity error in TCAM contents. This error was identified as a false positive and there is no data corruption.","This is an informational message only; no action is required. If this message appears repeatedly, please contact Cisco technical assistance for more information."
"C4K_L3HWFORWARDING","4","FLTCAMPARITYERROR","[char] Hw index: [object-info] Hw entry: [char] Sw entry: [char]","The forwarding TCAM's monitoring system detected a parity error in TCAM contents and repaired it.","This is an informational message only; no action is required. If this message appears repeatedly, please contact Cisco technical assistance for more information."
"C4K_L3HWFORWARDING","4","FWDCAMOUTOFSPACEFORVRFROUTINGTABLE","Insufficient TCAM resources to load VRF  [char]  routing table. Switching to software forwarding for this VRF.","The software could not load the VRF routing table into the TCAM because there were not enough hardware resources available for the operation. Traffic on this VRF will now be routed in software at reduced forwarding performance.","Reduce the Layer 3 forwarding hardware resource use, by reducing the number of routes loaded or by reducing the number of VLANs contained within the VRF. When the hardware requirements are reduced sufficiently, Cisco IOS software automatically reloads the VRF's routes into hardware. When this happens, the C4K_L3HWFORWARDING-6-SUCCEEDEDTOLOADVRFROUTINGTABLETOFWDCAM message appears."
"C4K_L3HWFORWARDING","4","FWDCAMOUTOFSPACEFORWCCPREDIRECTION","WCCP Service Group [char] failed to setup one or more routed ports/SVI for redirection due to lack of TCAM entries.","One or more VLANs corresponding to L3 routed ports or SVI could not be set up for redirection because there is insufficient room for more TCAM entries. Ingress IPv4 traffic on these VLANs will be routed normally. When the hardware requirements have been reduced sufficiently, the switch will automatically enable redirection for those VLANs.","Reduce the layer 3 forwarding hardware resource utilization, either by reducing the number of routes loaded or by reducing the number of VLANs contained within this WCCP service group. If the redirection is not enabled even after freeing up memory from these actions, contact Cisco technical assistance."
"C4K_L3HWFORWARDING","4","PROFILEIDMAPTABLEPARITYERROR","Parity error detected and corrected at profileIdMapTable index:  [dec]MapTableIndex","The ProfileIdMapTable monitoring system has detected a parity error in profileIdMapTable and repaired it.","This is an informational message only, no action is required. If this message appears repeatedly, please contact Cisco technical assistance for more information."
"C4K_L3HWFORWARDING","4","TCAMFULL","FLC Tcam full, packets will be forwarded in software at  reduced rate.  Failure due to:  [char]","Hardware forwarding resources are exhausted. Packets will be forwarded in software instead, and this will affect performance.","Reconfigure the switch to use fewer routes and re-enable hardware forwarding with the ip cef distributed command."
"C4K_L3HWFORWARDING","4","UNICASTMANNOMOREADJGROUP","No hardware adjacency resource available for route [ip-addr]","There is insufficient space in the hardware adjacency table to allocate the adjacency set for this route. It will be forwarded in software instead.","No action is necessary to ensure correct forwarding, however performance may be degraded. To restore forwarding performance, reconfigure the switch so that fewer adjacencies are required."
"C4K_L3HWFORWARDING","6","NOLONGERPBRPUNTINGPORT","Sufficient Policy Routing TCAM space has been found to handle PBR for interface  [char]  in hardware, no longer punting to software.","The hardware policy-based routing forwarding engine now has sufficient resources to handle the route map for the specified interface and can now do hardware forwarding of unicast IP traffic.","This is an informational message only; no action is required."
"C4K_L3HWFORWARDING","6","SUCCEEDEDTOLOADVRFROUTINGTABLETOFWDCAM","Successfully loaded VRF  [char]  routing table to TCAM.  Switching to hardware forwarding for this VRF.","A VRF that was previously being routed by software is now fully reloaded and hardware forwarding has resumed. Refer to the C4K_L3HWFORWARDING-4-FWDCAMOUTOFSPACEFORVRFROUTINGTABLE message for more information.","This is an informational message only; no action is required."
"C4K_LINECARD","2","MODULEERROR","Module [dec] inconsistency detected ([char]).","An inconsistency was detected in the specified module. The linecard will automatically be reset.Monitor the status of card. If the card does not recover after the autoreset, contact Cisco TAC.Error Message    C4K_LINECARD-2-SOFTERROR: Module [dec] memory inconsistency detected ([char])Explanation    An inconsistency was detected in the memory referred to in this message. The card will automatically be reset.","Monitor the status of card. If the card does not recover after the auto reset, contact Cisco for support."
"C4K_LINECARD","2","UNCORRECTABLESOFTERROR","Module [dec] memory inconsistency detected","An inconsistency was detected in the memory referred to in this message. The card will automatically be reset.","Monitor the status of card. If the card does not recover after the auto reset, contact Cisco for support."
"C4K_LINECARD","3","CONFIGPROMBYPASSED","Config prom on module [dec] has been bypassed","The config PROM on the module has been bypassed. Normally, this means that development-scope ROMMON variables are set. A non-default config PROM is being used instead. The module may perform poorly.","Enter the clear platform environment variable unsupported command to reset the variables back to their defaults."
"C4K_LINECARD","3","CONFIGPROMDATAINVALID","Invalid configuration on module [dec]'s config prom.","The config PROM of the module referred to in the message holds invalid configuration data. The module cannot come up in this case, as the module must have a valid configuration to function.","The module referred to in the log message should be returned to Cisco."
"C4K_LINECARD","3","CONFIGPROMREADFAILED","Failed to read module [dec]'s config prom, try reinserting module","Reading the config PROM of the module failed. This module cannot come up in this case, as the config PROM provides the configuration of the module. Sometimes the read fails because the module isn't inserted correctly in the slot. The read may also fail if the software is lacking resources required to read the PROM.","Try removing and reinserting the module. If that doesn't work, try resetting the switch. If the read still fails, this module needs to be returned."
"C4K_LINECARD","3","CONNECTORTYPECHANGE","Please make sure to RELOAD the switch after all port-groups for the Module %u have been set to the correct mode.","This message gives a reminder to reboot the switch after changing port-groups from Ten Gigabit to Gigabit.","Always reboot the switch after changing the module port-groups."
"C4K_LINECARD","3","INTERRUPTTIMEOUTRUNTIME","Module [dec] interrupt([dec]) completion timed out which may affect port functionality. Please reset the module to recover full functionality.","The software took too long to handle an interrupt from the module hardware. This may affect applying port configuration changes to the hardware.","Reset the linecard. If it does not recover, contact Cisco support."
"C4K_LINECARD","3","LINECARDECCERROR","Module [dec] detected memory ECC failure, resetting the board.","Software detected an ECC memory error and is resetting the module automatically.","If this issue persists, record the error message and contact Cisco technical support."
"C4K_LINECARD","3","LINECARDNOTSUPPORTED","Card in slot([dec]) is not supported with this [char].","The module identified in the message is not supported in the chassis/supervisor. For example, linecards requiring 48Gbps of backplane capacity are not supported in chassis providing only 24Gbps on the backplane/ with supervisor providing only 24Gbps on the backplane.","Refer to Cisco documentation to find which chassis or supervisor supports this module."
"C4K_LINECARD","3","LINECARDSEUEVENT","Module [dec], Gi [dec] to Gi [dec] port group detected SEU event, [char]","Software detected a Single-Event Upset memory error, and will recover the hardware automatically.","If this issue persists, record the error message and contact Cisco technical support."
"C4K_LINECARD","3","MODULEFAILURE","Module %u failure detected ([char]).","A failure in one or more of the module components has been detected and the module is in a degraded operating state. The module may continue to carry traffic but it will not respond to any interface configuration or operational changes.","Monitor the status of the module. If the module does not return to normal operating state within five minutes, reset the module. If the module is carrying traffic normally, the reset may be delayed until when convenient. If the module fails repeatedly, contact Cisco TAC."
"C4K_LINECARD","3","NOTSUPPORTEDINPORTGROUP","[char] isn't a supported type for module [dec], port-group [dec]","The customer has tried to configure a port-group to a type of interface which isn't supported.","Configure a supported interface type for this module and port-group. The show hw-module module port-group command shows which interfaces are in this module and port-group"
"C4K_LINECARD","4","ETHPHYSEUEVENT","[char] detected a soft error event -- [char]","A soft error event is detected and recovery process starts automatically.","Recovery process starts automatically and can take 2-3 minutes to finish. If this issue repeats on the same port, please record the error message and contact Cisco customer support."
"C4K_LINECARD","4","GENERALLOG","[char]","Not Available.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_LINECARD","4","MODULEFAILURECLEARED","Module %u failure cleared.","The module had experienced a temporary run-time failure that has corrected itself.","Monitor the status of the module. No further action is required."
"C4K_LINECARDMGMTPROTOCOL","3","FAILEDTOSEND","EsmpDriver [char] - Failed to send ESMP requests due to [char].","This message indicates a failure in ESMP request generation for the reason given. This is probably due to high CPU utilization caused by a number of factors, and under these circumstances switching module communication protocol packets can not be transmitted.","If you see this message frequently, analyze the traffic going to the CPU and contact your technical support representative to debug the problem."
"C4K_LINECARDMGMTPROTOCOL","4","INITIALTIMEOUTWARNING","[char] - management request timed out.","There are communication problems with the module ASIC that fans out a single gigabit port to front-panel ports. A few messages are within tolerance levels.","This is an informational message only; no action is required. If this message is seen frequently, refer to: http://www.cisco.com/en/US/products/hw/switches/ps663/"
"C4K_LINECARDMGMTPROTOCOL","4","ONGOINGTIMEOUTWARNING","[char] - consecutive management requests timed out.","There are persistent communication problems with the module ASIC that fans out a single gigabit port to front-panel ports.","Reinsert the module."
"LOGGING_REDIRECT_ISSU","2","GET_BUFFER","Logging Redirect ISSU client failed to get buffer for message.  Error: [dec] ([char])","The Logging Redirect ISSU client failed to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","Copy the error message exactly as it appears on the console or in the system log. Issue the show logging and show checkpoint client commands to gather data that may help identify the nature of the error. Research and attempt to resolve the error using the Output Interpreter at https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl . If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl , or contact your Cisco technical support representative."
"LOGGING_REDIRECT_ISSU","2","INIT","Logging Redirect ISSU client initialization failed to [char]. Error: [dec] ([char])","The Logging Redirect ISSU client could not be initialized. This initialization failure must be addressed before in-service software upgrade or downgrade can be performed successfully. If you do not address this failure, there will be downtime during software upgrade or downgrade.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter at https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl . If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl , or contact your Cisco technical support representative."
"LOGGING_REDIRECT_ISSU","2","SEND_NEGO_FAILED","Logging Redirect ISSU client failed to send negotiation message.  Error: [dec] ([char])","The Logging Redirect ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","Copy the error message exactly as it appears on the console or in the system log. Issue the show logging and show checkpoint client commands to gather data that may help identify the nature of the error. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl . If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl , or contact your Cisco technical support representative."
"LOGGING_REDIRECT_ISSU","2","SESSION_NEGO","Logging Redirect ISSU client encountered unexpected client nego_done.  Error: [dec] ([char])","An ISSU-compliant client transitions through a series of internal states. The Logging Redirect ISSU client encountered a 'client negotiation done' state that was unexpected. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","Copy the error message exactly as it appears on the console or in the system log. Issue the show issu session <client_id> and show issu negotiated capability <session_id> command to gather data that may help identify the nature of the error. Research and attempt to resolve the error using the Output Interpreter at https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl . If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl , or contact your Cisco technical support representative."
"LOGGING_REDIRECT_ISSU","2","SESSION_REGISTRY","Logging Redirect ISSU client failed to register session information.  Error: [dec] ([char])","The Logging Redirect ISSU client failed to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly.","Copy the error message exactly as it appears on the console or in the system log. Issue the show issu capability entries <client_id> and show issu session <client_id> and show issu negotiated capability <session_id> commands to gather data that may help identify the nature of the error. Research and attempt to resolve the error using the Output Interpreter at https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl . If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl , or contact your Cisco technical support representative."
"LOGGING_REDIRECT_ISSU","3","INVALID_SESSION","Logging Redirect ISSU client does not have a valid registered session.","The Logging Redirect ISSU client does not have a valid registered session.","Copy the error message exactly as it appears on the console or in the system log. Issue the show issu capability entries <client_id>, show issu session <client_id>, and show issu negotiated capability <session_id> commands to gather data that may help identify the nature of the error. Research and attempt to resolve the error using the Output Interpreter at https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl . If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl , or contact your Cisco technical support representative."
"LOGGING_REDIRECT_ISSU","3","MSG_NOT_OK","Logging Redirect ISSU client Message Type [dec] is not compatible","The Logging Redirect ISSU client received an incompatible message from the peer device. The message cannot be processed.","Copy the error message exactly as it appears on the console or in the system log. Issue the show issu message group <client_id>, show issu session <client_id> and show issu negotiated version <session_id> commands to gather data that may help identify the nature of the error. Research and attempt to resolve the error using the Output Interpreter at https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl . If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl , or contact your Cisco technical support representative."
"LOGGING_REDIRECT_ISSU","3","MSG_SIZE","Logging Redirect ISSU client failed to get the MTU for Message Type [dec] . Error: [dec] ([char])","The Logging Redirect ISSU client failed to calculate the MTU for the specified message. The Logging Redirect ISSU client is not able to send the message to the standby device.","Copy the error message exactly as it appears on the console or in the system log. Issue the show issu message group <client_id>, show issu session <client_id> and show issu negotiated version <session_id> commands to gather data that may help identify the nature of the error. Research and attempt to resolve the error using the Output Interpreter at https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl . If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl , or contact your Cisco technical support representative."
"LOGGING_REDIRECT_ISSU","3","SESSION_UNREGISTRY","Logging Redirect ISSU client failed to unregister session information.  Error: [dec] ([char])","The Logging Redirect ISSU client failed to unregister session information.","Copy the error message exactly as it appears on the console or in the system log. Issue the show issu session <client_id> and show issu negotiated capability <session_id> commands to gather data that may help identify the nature of the error. Research and attempt to resolve the error using the Output Interpreter at https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl . If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl , or contact your Cisco technical support representative."
"LOGGING_REDIRECT_ISSU","3","TRANSFORM_FAIL","Logging Redirect ISSU client [char] transform failed for Message Type [dec] . Error: [dec] ([char])","The Logging Redirect ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In both cases, the Logging Redirect state between the active device and the standby device is not identical.","Copy the error message exactly as it appears on the console or in the system log. Issue the show issu session <client_id> and show issu negotiated version <session_id> commands to gather data that may help identify the nature of the error. Research and attempt to resolve the error using the Output Interpreter at https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl . If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl , or contact your Cisco technical support representative."
"C4K_NPUINTERNALPKTPROCESSING","2","OUTOFEFPS","System EFPs exhausted. Port  [char]  is not added to Vlan  [dec]  . To enable this vlan on the port, please  free system resources by deleting some efps.","System out of efps. Efps for vlan operation cannot be allocated","Recommended Action: Delete some efps to release system resources and retry vlan creation"
"C4K_PKTPROCESSING","3","CPUEVENTSASICVALIDATION","Pkt rcvd: CPU Subport  [dec] TxQId  [dec] eventdata  [dec] FRD  [dec] ,  [dec] FCH  [dec]","Dump data required to verify pkts sent to CPU have the right FCH format & queue as specified in cpuEventFwdTable for the winner event.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_PKTPROCESSING","3","EXCEPTIONEVENTPACKET","Packet Rx on Exception Event : EventCode  [object-info] rxPort  [char]   rxVlan  [dec]  [l2-header]","An unexpected CPU event happened for the packet forwarded to the CPU. The packet was dropped and there should be no other impact.","This is an informational message only; no action is required."
"C4K_PKTPROCESSING","3","INVALIDVLAN","Packet received on invalid Vlan from hardware. PortId [dec] [l2-header]   Vlan [dec] TagType [object-info]","The hardware sent a packet to the CPU, but the receiving VLAN was incorrect. There is probably a hardware problem.","Contact your technical support representative."
"C4K_PKTPROCESSING","3","OUTOFPACKETINFOTODRIVER","\'Ran out of memory to send packet information to the driver that enqueues packets to hardware\'","Transmit packets are probably stuck in a queue, and some of the packets have been sent to multiple destinations. This event wastes memory, so new packet information cannot be allocated.","Contact your technical support representative."
"C4K_PKTPROCESSING","3","OUTOFPACKETSTODRIVER","\'Ran out of memory to send packets to the driver that enqueues packets to hardware\'","Transmit packets are probably stuck in a queue, so new packets cannot be queued.","This is an informational message only; no action is required."
"C4K_PKTPROCESSING","3","REPLICATEDINVALIDVLAN","Replicated packet received on Vlan 0, CRC32 is valid. PortId [dec] [l2-header] Vlan [dec] TagType [object-info] count [object-info]","A replicated packet was received on VLAN 0. The CRC32 packet is correct. If the count is high, there may be a hardware problem.","Contact your technical support representative."
"C4K_PKTPROCESSING","3","UNEXPECTEDOUTPUTACLHIT","Packet hit output ACL but sent to CPU as a result of hardware input Acl processing [l2-header] Port char] Vlan [dec]","An inconsistent hardware state might exist. A packet was sent to the CPU due to input ACL processing by the hardware. The packet unexpectedly encountered output ACL processing.","Contact your technical support representative."
"C4K_PKTPROCESSING","3","UNRECOGNIZEDEVENT","Packet received for an unimplemented event. CPU Subport [dec] TxQId [dec] PDD {[dec], [dec]}","The hardware sent a packet to the CPU, but the software did not recognize the event that triggered the packet to be sent.","This is an informational message only; no action is required."
"C4K_PKTPROCESSING","4","ADJSAMEIFACTIONFORREPLICA","Attempt to transmit replicated packet on the interface it came in on.","A replicated packet encountered a forwarding action (for example, an ACLredirect) that attempted to transmit the packet to an Adjacency pointing to the interface the packet originally came in on. Because this is an error, the packet was sent to the CPU for software processing.","If this happens with WCCP output redirection configured, ensure that redirection exclusion (ip wccp redirect exclude in) is configured on the interface connected to the WCCP content engine."
"C4K_PKTPROCESSING","4","ERRORPACKET","[char]","This message indicates that the software is unable to process a packet so the packet has been forwarded to the CPU instead. Because this event is unexpected, the packet is then dropped. This error indicates that the packet cannot be handled by the TCAM hardware, so the most likely cause is a hardware failure in the supervisor engine.","This is an informational message only; no action is required."
"C4K_PKTPROCESSING","4","INVALIDACLACTION","Unable to determine the ACL action to take because we ran out of memory. Address: src  [mac-addr]  dst  [mac-addr]","There is insufficient memory to create a list of actions to perform on the packet. As a result, the packet was dropped.","This is an informational message only; no action is required."
"C4K_PKTPROCESSING","4","INVALIDACLACTIONFORSPANPORT","Unable to determine the ACL action to take because we ran out of memory. Address:  src  [mac-addr]  dst  [mac-addr]","There is insufficient memory to create a list of actions to perform on the packet. As a result, the packet was dropped.","This is an informational message only; no action is required."
"C4K_PKTPROCESSING","4","UNKNOWNBRIDGEORROUTE","Unable to determine whether to route or bridge software-processed packet with source  mac  [mac-addr]  , destination mac  [mac-addr]  , source IP  [ip-addr]  , destination IP  [ip-addr]","When a replicated packet is sent to the software by an output ACL, the hardware does not indicate whether the packet needs to be bridged or routed.When resources are exhausted or when the ACLs that are programmed in the hardware cannot handle processing directly (such as ACLs matching TCP flags), the supervisor engine sends the packets to the software for processing. If the software cannot determine whether to bridge or route, the packet might be dropped. This drop indicates that the packet was directed to a Hot Standby Routing Protocol (HSRP) router group MAC address.","This is an informational message only; no action is required. If this message is seen repeatedly, contact Cisco technical support."
"C4K_PKTPROCESSING","4","UNKNOWNBRIDGEORROUTEREPLICATED","Unable to determine whether to route or bridge replicated software-processed packet with source  mac  [mac-addr]  , destination mac  [mac-addr]  , source IP  [ip-addr]  , destination IP  [ip-addr]","When a replicated packet is sent to the software by an output ACL, the hardware does not indicate whether the packet needs to be bridged or routed.When resources are exhausted or when the ACLs that are programmed in the hardware cannot handle processing directly (such as ACLs matching TCP flags), the supervisor engine sends the packets to the software for processing. If the software cannot determine whether to bridge or route, the packet might be dropped. This drop indicates that the packet was directed to a Hot Standby Routing Protocol (HSRP) router group MAC address.","This is an informational message only; no action is required."
"C4K_PKTPROCESSING","4","UNKNOWNSOURCELOCATIONFORBRIDGE","Unable to determine source host location of replicated software-processed packet with source address  [mac-addr]  and destination address  [mac-addr]","When a replicated packet is sent by an output ACL to the software for processing, the hardware does not indicate the ingress port or VLAN ID.When resources are exhausted or when the ACLs that are programmed in the hardware cannot handle processing directly (such as ACLs matching TCP flags), the supervisor engine sends the packets to software for processing. Without the ingress port identifier, the supervisor engine might forward the packet back out the port on which it was received, possibly creating network loops or other problems. If the switch is unable to recognize the ingress port from other information, the packet is dropped.","This is an informational message only; no action is required."
"C4K_PKTPROCESSING","5","NOTAPPLYINGACL","Not applying [input/output] Acl for packet [packet-info]","The software is unable to determine the correct ACL entry that is indicated by the hardware. The hardware-provided index of the ACL content-addressable memory (CAM) indicates that the software needs to take the actions for the entry at that index. If the packet was queued in the hardware before the software could process it, the index is out of date.","This is an informational message only; no action is required."
"C4K_PKTPROCESSING","7","ADJLOOKUPFAILED","Draining the backed up packets in CPU queue when we cleaned up FIB adjacencies. Last drained packet's source address  [ip-addr]  and destination address  [ip-addr]","This event can occur when the software processes the routed packets and the router port is shut down. The software can automatically repair adjacencies, but there was at least one packet in the queue that was lost.","This is an informational message only; no action is required."
"C4K_PKTPROCESSING","7","NOTVALIDTXINFOFORREPLICAPACKET","Not Valid TxInfo for Replicated Packet : EventCode  [object-info] txPortId  [dec]  txVlanId  [dec]  [l2-header]","A packet in the replicating pipeline does not have a valid associated VLAN or port. The packet was dropped, as some header information appears to be corrupted. This will not affect any feature or system performance.","This is an informational message only; no action is required."
"C4K_PKTPROCESSING","7","OUTOFPACKETFORNEWPACKET","[char]","Packets are probably queued in process queues waiting to be processed. New packets cannot be allocated by the Packet manager for its client until the queue is cleared.","This is an informational message only; no action is required."
"C4K_PKTSAMP","4","MAXDATASRCLIMITREACHED","PktSampMan: Monitor Instance cannot be created as  maximum  limit  has already been reached.","The system limit on the maximum number of Monitor instances has been reached.","If possible, delete other Monitor Instances that are no longer in use."
"C4K_PKTSAMP","4","MAXEXPORTERLIMITREACHED","PktSampMan: Exporter Instance cannot be created as  maximum   limit has already been reached.","The system limit on the maximum number of Exporter instances has been reached.","If possible, delete other Exporter Instances that are no longer in use."
"C4K_PKTSAMP","4","MAXSAMPLERLIMITREACHED","PktSampMan: Sampler Instance cannot be created as  maximum  limit  has already been reached.","The system limit on the maximum number of Sampler instances has been reached.","If possible, delete other Sampler Instances that are no longer in use."
"C4K_PKTSAMP","4","OUTOFDATASRCRESOURCES","PktSampMan: There is not sufficient memory to allocate a new   Data Source(monitor) instance.","The software failed to allocate memory for a Monitor Instance. The specified monitor instance will not function but will appear in the configuration file. Other features and Monitor instances are unaffected.","If possible, free up the available memory by removing features that are no longer in use and reapply the monitor configuration."
"C4K_PKTSAMP","4","OUTOFEXPORTERRESOURCES","PktSampMan: There is not sufficient memory to allocate a new   exporter instance.","The software failed to allocate memory for a Exporter Instance. The specified exporter instance will not function but will appear in the configuration file. Other features and exporter instances are unaffected. However monitor instances using the exporter will not function properly.","If possible, free up the available memory by removing features that are no longer in use and reapply the exporter configuration."
"C4K_PKTSAMP","4","OUTOFSAMPLERRESOURCES","PktSampMan: There is not sufficient memory to allocate a new   sampler instance.","The software failed to allocate memory for a Sampler Instance. The specified sampler instance will not function but will appear in the configuration file. Other features and sampler instances are unaffected. However monitor instances using the sampler will not function properly.","If possible, free up the available memory by removing features that are no longer in use and reapply the sampler configuration."
"C4K_PLATFORMPACKETMAN","3","OUTOFPACKETHEADERS","Cannot allocate memory for a packet header.","The system cannot allocate a packet header buffer.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"PM","1","INCONSISTENT_PORT_STATE","Inconsistent HW/SW port state for [char]. Please shut/no shut the interface","The hardware and software port state has become inconsistent.","Enter the shutdown command followed by the no shutdown command on the interface specified in the message."
"PM","2","LOW_SP_MEM","Switch process available memory is less than [dec] bytes","The switch has insufficient memory for processing. Too many Layer 2 VLANs might have been configured in the system.","Remove Layer 2 VLANs or other features from the system to reduce memory usage."
"PM","2","NOMEM","Not enough memory available for [char]","The Port Manager subsystem cannot obtain sufficient memory for the specified PM operation. [char] is the PM operation ID.Error Message    PM-2-VLAN_ADD:Failed to add VLAN [dec] - [char].Explanation    The VLAN was not added to VTP, because of the reason stated in the text string.","This is an informational message only; no action is required."
"PM","3","ERR_INCOMP_PORT","[dec]/[dec] is set to inactive because [dec]/[dec] is a [char] port","The private host port cannot be configured with the trunk, private, promiscuous, and SPAN destination port on the same coil.","Try to configure the incompatible ports on different coils."
"PM","3","INTERNALERROR","Port Manager Internal Software Error ([char]:[char]:[dec]:[char])","The access VLAN on the VMPS server is set to the same VLAN as a voice VLAN on the port. The access VLAN assignment on the VMPS server should be different from the voice VLAN.","Reset the VLAN assignments to remove the conflict."
"PM","4","BAD_APP_ID","an invalid application id [dec] was detected","The Port Manager detected a request with an invalid application ID, where [dec] is the application ID.","Reset the VLAN assignments to remove the conflict."
"PM","4","BAD_APP_REQ","an invalid [char] request by the `[char]' application was detected","The Port Manager detected an invalid request. The first [char] is the invalid request, and the second [char] is the application making the request.","Reset the VLAN assignments to remove the conflict."
"PM","4","BAD_CARD_COOKIE","an invalid card cookie was detected","The Port Manager detected an invalid request.","Reset the VLAN assignments to remove the conflict."
"PM","4","BAD_CARD_SLOT","an invalid card slot [dec] was detected","The Port Manager detected an invalid request on slot number [dec].","Reset the VLAN assignments to remove the conflict."
"PM","4","BAD_COOKIE","[char] was detected","The Port Manager detected an invalid request.","Reset the VLAN assignments to remove the conflict."
"PM","4","BAD_HA_ENTRY_EVENT","Invalid Host access entry event ([dec]) is received","The entry event is not an add, delete, or update event (the only supported types).","Enter the show tech-support privileged EXEC command to gather data that might provide information about the error. If you cannot determine the cause of the error from the error message or from the show tech-support command display, copy the error message exactly as it appears on the console or in the system log, contact your technical support representative, and provide the representative with the gathered information."
"PM","4","BAD_PORT_COOKIE","an invalid port cookie was detected","The Port Manager detected an invalid request.","Enter the show tech-support privileged EXEC command to gather data that might provide information about the error. If you cannot determine the cause of the error from the error message or from the show tech-support command display, copy the error message exactly as it appears on the console or in the system log, contact your technical support representative, and provide the representative with the gathered information."
"PM","4","BAD_PORT_NUMBER","an invalid port number [dec] was detected","The Port Manager detected an invalid request on interface number [dec].","Enter the show tech-support privileged EXEC command to gather data that might provide information about the error. If you cannot determine the cause of the error from the error message or from the show tech-support command display, copy the error message exactly as it appears on the console or in the system log, contact your technical support representative, and provide the representative with the gathered information."
"PM","4","BAD_VLAN_COOKIE","an invalid vlan cookie was detected","The Port Manager detected an invalid request.","Try a different VLAN on the device."
"PM","4","BAD_VLAN_ID","an invalid vlan id [dec] was detected","The Port Manager detected an invalid request. The invalid VLAN ID is [dec].","Try a different VLAN on the device."
"PM","4","ERR_DISABLE_VP","[char] error detected on [char]","The Port Manager will put the virtual port in the errdisable state when it detects a misconfiguration or misbehavior. After the configured retry time (5 minutes by default), the system will attempt to recover the interface.","This is an informational message only; no action is required."
"PM","4","ERR_DISABLE","[char] error detected on [char]","The Port Manager will put the interface in the errdisable state when it detects a misconfiguration or misbehavior. After the configured retry time (5 minutes by default), the system will attempt to recover the interface.","This is an informational message only; no action is required."
"PM","4","ERR_RECOVER","Attempting to recover from [char] err-disable state on [char]","The system is attempting to bring the interface back from the errdisable state.","This is an informational message only; no action is required."
"PM","4","ERR_RECOVER_VP","Attempting to recover from [char] err-disable state on [char]","The system is attempting to bring the interface back from the errdisable state.","This is an informational message only; no action is required."
"PM","4","EXT_VLAN_INUSE","VLAN [dec] currently in use by [char]","The Port Manager failed to allocate the VLAN for external use because the VLAN is currently occupied by another feature.","Reconfigure the feature to use another internal VLAN, or request another available VLAN."
"PM","4","EXT_VLAN_NOTAVAIL","VLAN [dec] not available in Port Manager","The Port Manager failed to allocate the requested VLAN. The VLAN might be used as an internal VLAN by other features.","Reconfigure the feature to use another internal VLAN, or request another available VLAN."
"PM","4","INACTIVE","putting [char] in inactive state because [char]","The Port Manager was blocked from creating a virtual port for the switch port and VLAN, causing the port to be inactive. The reason for this condition is specified in the error message.","Try a different VLAN on the device."
"PM","4","INT_FAILUP","[char] failed to come up. No internal VLAN available","The Port Manager failed to allocate the internal VLAN, and the interface cannot start.","Remove extended-range VLANs to free resources."
"PM","4","INT_VLAN_NOTAVAIL","Failed to allocate internal VLAN in Port Manager","The Port Manager failed to find any available internal VLAN.","Delete some extended-range VLANs that are created by users, or remove some features that require internal VLAN allocation, such as a routed port."
"PM","4","INVALID_HOST_ACCESS_ENTRY","Invalid Host access entry type ([dec]) is received","The host access entry should be either configured or dynamic.","Reconfigure the host access entry using the correct type."
"PM","4","LIMITS","Virtual port count for [char] exceeded the recommended limit of [dec]","There is a limit of 1200 virtual ports per module and a maximum of 4500 per switch. This limit was exceeded.","Reduce the number of trunks and VLANs in the module (or switch) that is specified in the error message. Make sure that the overture port and VLAN port count is below the recommended limit."
"PM","4","MPLS_MTU_EC_CFG","MPLS MTU size [dec] is not supported by one or more ports in channel [char].","The MPLS MTU size configured on the ethernet channel is larger than the maximum MTU size that can be supported by one or more ports in this channel. As a result, large packets can be dropped.","Reduce the MPLS MTU size, or remove these ports from the channel before increasing the MPLS MTU size."
"PM","4","MPLS_MTU_PORT_CFG","MPLS MTU size [dec] is not supported by port [char].","The MPLS MTU size configured on the port is larger than the maximum MTU size that can be supported by this port. As a result, large packets can be dropped.","Reduce the MPLS MTU size."
"PM","4","NO_SUBBLOCK","No PM subblock found for [char]","A Port Manager (PM) subblock was not found for this interface.","Enter the show tech-support privileged EXEC command to gather data that might provide information about the error. If you cannot determine the cause of the error from the error message or from the show tech-support command display, copy the error message exactly as it appears on the console or in the system log, contact your technical support representative, and provide the representative with the gathered information."
"PM","4","PORT_BOUNCED","Port [char] was bounced by [char].","The Port Manager needed to perform a reactivation of a port in the link-down state during a switchover. A port is only reactivated when the port data structures lack consistency between the active and standby supervisor engines. The reactivation event returned the active ports in the link-down state to the link-up state.","This is an informational message only; no action is required."
"PM","4","PORT_CONSISTENT","Port [char] consistency has been restored","The port manager on the standby supervisor engine discovered that the port state became consistent again.","This is an informational message only; no action is required."
"PM","4","PORT_INCONSISTENT","Port [char] is inconsistent: IDB state  [char] (set %TE ago)","The port manager on the standby supervisor engine discovered that the port state was inconsistent for more that one second. Inconsistent ports are reactivated on switchover (you will see the PORT_BOUNCED message).","This is an informational message only; no action is required."
"PM","4","PVLAN_TYPE_CFG_ERR","Failed to set VLAN [dec] to a [char] VLAN","The platform failed to set the private VLAN type.","Enter the show tech-support privileged EXEC command to gather data that might provide information about the error. If you cannot determine the cause of the error from the error message or from the show tech-support command display, copy the error message exactly as it appears on the console or in the system log, contact your technical support representative, and provide the representative with the gathered information."
"PM","4","TOO_MANY_APP","application `[char]' exceeded registration limit","The Port Manager detected an invalid request. [char] in the application.","Reconfigure the host access entry using the correct type."
"PM","4","UNKNOWN_HOST_ACCESS","Invalid Host access value ([dec]) is received","A n invalid host access value was sent to the host access table.","Reconfigure the host access entry using the correct type."
"PM","4","VMPS_CFG","Dynamic access VLAN [dec] same as voice vlan on [char].","The access VLAN on the VMPS server is set to the same VLAN as the voice VLAN on the port.","Change the assignments so that the access VLAN assignment on the VMPS server is different from the voice VLAN."
"PM","6","EXT_VLAN_ADDITION","Extended VLAN is not allowed to be configured in VTP CLIENT mode.","The user attempted to configure an extended VLAN while in VTP client mode. This is not allowed, and the configuration failed but did not otherwise impact the switch operation.","This is an informational message only; no action is required. If the new extended VLAN is still desired, get out of VTP client mode and repeat the configuration."
"C4K_PORTFANOUTASIC4X1000MAN","4","DIAGSFAILED","[char] failed diagnostics","The module ASIC that is identified by [char] failed diagnostics.","Contact your technical support representative."
"C4K_PORTFANOUTASIC4X1000MAN","4","FAILEDTOSENDLOOPBACKTRIES","[char] port [dec] failed to send packet in [dec] tries","The module ASIC [char] was unable to send a loopback packet on a module ASIC port for the [dec]th time. The switch has insufficient memory and will attempt to send a loopback packet only up to three times.","Contact your technical support representative."
"C4K_PORTFANOUTASIC4X1000MAN","4","UNEXPECTEDLOOPBACK","[char] sent out a loopback packet on port [dec], but it came back on port [dec]","The module ASIC diagnostics for [char] sent a loopback packet out port [dec], and it came back on another port [dec]. This condition is rare because the loopback is internal to the hardware.","Contact your technical support representative."
"C4K_PORTFANOUTASIC8X1000HW","3","UNKNOWNDEVICEID","[char] - Linecard Management Protocol info register has unknown device id [hex]","Each module ASIC has an information register on it that contains the device ID field (DID) of the ASIC. When the module ASIC driver read this register, it discovered that the DID type was invalid.The [char] field of the DID might contain <asic-code>(x) where x is the gigabit port of the switching engine to which the module ASIC is attached. The hex field of the DID contains the device ID. The expected value is 0x0450.","Contact your technical support representative."
"C4K_PORTFANOUTASIC8X1000MAN","4","DIAGSFAILED","[char] failed diagnostics","The module ASIC identified by [char] failed diagnostics.","Contact your technical support representative."
"C4K_PORTFANOUTASIC8X1000MAN","4","FAILEDTOSENDLOOPBACKTRIES","[char] port [dec] failed to send packet in [dec] tries","The module ASIC [char] is unable to send a loopback packet on the module ASIC interface [dec] and this is the decth time that it has tried to send and failed. The switch attempts to send a loopback packet only up to three times. The switch is out of memory.","Contact your technical support representative."
"C4K_PORTFANOUTASIC8X1000MAN","4","UNEXPECTEDLOOPBACK","[char] sent out a loopback packet on port [dec], but it came back on port [dec]","The module ASIC diagnostics for [char] sent a loopback packet out interface [dec] and it came back on another interface [dec]. This condition is unexpected because the loopback is internal to the hardware.","Contact your technical support representative."
"C4K_PORTFANOUTASIC8X1000MAN","7","LOSTPACKET","[char] port [dec] lost one or more packets, [dec] transmitted [dec] received","A loopback packet was lost during online diagnostics of the module ASIC [char].","This is an informational message only; no action is required."
"C4K_PORTFANOUTASIC8X100MAN","4","DIAGSFAILED","[char] failed diagnostics","The module ASIC that is identified by [char] failed diagnostics.","Contact your technical support representative."
"C4K_PORTFANOUTASIC8X100MAN","4","FAILEDTOSENDLOOPBACKTRIES","[char] port [dec] failed to send packet in [dec] tries","The module ASIC [char] was unable to send a loopback packet on the module ASIC port [dec] for the decth time. The switch has insufficient memory; it will attempt to send a loopback packet up to three times.","Contact your technical support representative."
"C4K_PORTFANOUTASIC8X100MAN","4","UNEXPECTEDLOOPBACK","[char] sent out a loopback packet on port [dec], but it came back on port [dec]","The module ASIC diagnostics for [char] sent the loopback packet out port [dec] and it came back on another interface [dec]. This condition is rare because the loopback is internal to the hardware.","Contact your technical support representative."
"C4K_PORTFANOUTASIC8X100MAN","7","LOSTPACKET","[char] port [dec] lost a packet","A loopback packet was lost during online diagnostics of this port.","This is an informational message only; no action is required."
"C4K_PORTGRANDPRIXASIC8X1000HW","3","REGREADERROR","HalGrandprix ( [char] ) : Register Read - PhyAddr( [hex] )  BlockNum( [dec] ) RegAddr( [hex] )  -  Result( [hex] )","NOT AVAILABLE YET.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"PPPOE_IA","3","GLOBAL_ERROR","PPPoE IA internal error [char]","A software sanity check failed in the PPPoE IA process as described in the output. This message usually occurs when the PPPoE IA feature receives a packet with an invalid source interface or source VLAN. PPPoE IA drops the packet, but is otherwise unaffected.","Enter the show running-config, show pppoe intermediate-agent info, and debug pppoe intermediate-agent commands to obtain more data about the error. If necessary, contact Cisco technical support to help solve the problem."
"PPPOE_IA","3","INTERFACE_ERROR","PPPoE IA internal error Interface [char] : [char]","A software sanity check failed on an interface in the PPPoE IA process. This message is displayed if PPPoE IA received a packet that is should not recieve according to the configuration. PPPoE IA drops the packet, but is otherwise unaffected.","Enter the show running-config, show pppoe intermediate-agent info, and debug pppoe intermediate-agent commands to obtain more data about the error. If necessary, contact Cisco technical support to help solve the problem."
"PPPOE_IA","4","ERRDISABLE_WARNING","PPPoE IA received [dec] PPPoE packets on interface [char]","PPPoE IA detected a PPPoE packet-rate limit violation on the specified interface. The interface will be error disabled.","This is an informational message only; no action is required."
"PPPOE_IA","4","QUEUE_FULL","Fail to enqueue PPPoE packet into processing queue: [char] the  queue is probably full and packet will be dropped.","PPPoE packets are being received at a much higher rate than PPPoE IA process can handle them. These unhandled PPPoE packets will be dropped to prevent a possible denial of service attack.","This is an informational message only; no action is required."
"PPPOE_IA","4","RATE_LIMIT_EXCEEDED","The interface [char] is receiving more than the threshold set","PPPoE packets are being received at a much higher rate than the specified threshold.","This is an informational message only; no action is required."
"PPPOE_IA","5","UNTRUSTED_PORT","[char] drop message on untrusted port message type: [char]  MAC sa: [mac-addr]","PPPoE IA detected types of PPPoE messages that are not allowed on the untrusted interface. A host may be trying to act as a PPPoE server.Explanation    This is an informational message only; no action is required.QOS MessagesThis section contains the quality of service (QOS) message.Error Message    C4K_QOS-4-OUTOFPOLICERRESOURCES:Out of memory to allocate a policerExplanation    The software failed to allocate memory for a policer while processing the QoS configuration, possibly because the policer configuration exceeded its maximum supported limit.","Remove policers from other unwanted policies, and retry the operation. Resend the command when other Telnet sessions are not sending debugging commands."
"C4K_QOS","4","OUTOFQUEUERESOURCES","Out of memory to allocate a queue","The software failed to allocate memory for a queue when processing the QoS configuration. This could be because the queue configuration exceeded its maximum supported limit.","If possible, remove other unwanted policies and retry the operation."
"C4K_QOS_IOS","5","INSUFFICIENT_BW_REMAINING","Policy-map: [char]; with insufficient bandwidth for  [dec] queues not having explicit bandwidth configuration.","Each active queue must be allocated at least 32 kbps bandwidth. However, there is not enough bandwidth remaining to allocate new queues corresponding to class of traffic. For example, a class of traffic that has only shape rate.","While accounting for the interface speed, modify configured bandwidth in the policy map such that in addition to the sum of configured bandwidth across all queuing classes, there is at least 32 kbps bandwidth for every queuing class that does not have bandwidth configured. Then try to re-attach the policy map."
"C4K_QOS_IOS","5","INVALID_BANDWIDTH_PERCENT","Policy map: [char]; with bandwidth percent or bandwidth remaining  percent action results in unsupported absolute bandwidth  value.","The policy map was incorrectly configured. One or more of the bandwidth percent or bandwidth remaining percent values results in an absolute bandwidth value lower than the 32kbps minimum supported.","Considering the current interface speed, modify the configured bandwidth percent or bandwidth remaining percent values such that the resulting absolute bandwidth value is equal to or greater than the platform supported minimum bandwidth value and then try to re-attach the policy map."
"C4K_QOS_IOS","5","INVALID_CLASSMAP_FILTERS_IN_MEMBER_PORT_POLICY","Policy-map: [char]; on the member port of the  port-channel has invalid classification filters.","Class map filters in a policy map on the member port of a port-channel can have either marking field(cos/dscp/precedence) based filters only or other filters types based only. Further, if marking based filters are used, all filters in the policy map must be either cos based or dscp/precedence based.","Modify the configured class map filters of the policy map to be either marking field(cos/dscp/precedence) based only or other filter types based only. If marking field based filters are configured, then configure all filters in the policy map using either cos based filters or dscp/precedence based filters. Then try to re-attach the policy map."
"C4K_QOS_IOS","5","INVALID_CUMULATIVE_BANDWIDTH","Policy-map: [char]; with sum of configured bandwidth  exceeding interface speed.","A policy map was incorrectly configured. The sum of configured class bandwidth can not exceed current interface speed.","Modify policy-map such that cumulative bandwidth across queuing classes does not exceed current interface speed, and then try to re-attach the policy map."
"C4K_QOS_IOS","5","INVALID_DEFAULT_CLASS_WITH_PRIORITY","Policy map: [char]; with strict priority queuing not supported  for default class of traffic.","A policy-map with strict priority queuing action in class-default was configured, but this action is not supported in default class.","Remove the priority queuing action from the default class and try to re-attach the policy map."
"C4K_QOS_IOS","5","INVALID_QUEUELIMIT","Policy-map: [char]; with non-multiple of 8 queue-limit value","The queue-limit value in a policy map must be multiple of 8. An invalid value was configured.","Modify queue-limit values in the policy-map to be multiple of 8, and then try to re-attach the policy map."
"C4K_QOS_IOS","5","INVALID_REMAINING_BW_PERCENT","Policy-map: [char]; with bandwidth remaining percent is  supported only with priority queuing.","The policy map was incorrectly configured. The remaining percentage of bandwidth is supported only when combined with priority queuing action in a policy map.","Modify the policy map to specify bandwidth using either bandwidth or bandwidth percent command instead and then try to re-attach the policy map."
"C4K_QOS_IOS","5","INVALID_SHAPE_PERCENT","Policy map: [char]; with shape percent results in lower than  supported absolute shape value.","The policy map was incorrectly configured. One or more of the configured shape percent values results in an absolute shape value lower than the 32kbps minimum supported on the platform.","Modify the configured shape percent values such that the resulting absolute shape value, considering the interface current speed, is equal to or greater than the 32kbps minimum shape value and then try to re-attach the policy map."
"C4K_QOS_IOS","5","INVALID_SHAPE_RATE","Policy map: [char]; shape value is higher than interface speed.","The policy map was incorrectly configured. One or more of the configured shape values are higher than the current interface speed.","Modify the configured shape values to not exceed the current interface speed and then try to re-attach the policy map."
"C4K_QOS_IOS","5","MORE_QUEUEING_CLASSES","Policy-map: [char]; can have only 7 non-default queuing classes.","The policy map was incorrectly configured. There can be up to 8 queuing classes in a policy map including the default class, which always has default queue. There can be up to 7 non-default queuing classes.","Modify the policy map to contain only 7 non-default queuing classes, and then try to re-attach the policy-map."
"C4K_QOS_IOS","5","MORE_THAN_ONE_PRIORITY_QUEUE","Policy-map: [char]; with more than one priority queue.","The policy map was incorrectly configured. A policy-map can have only one priority queuing action.","Modify the policy-map such that it contains at most one priority queuing class and then try to re-attach the policy map."
"C4K_QOS_IOS","5","QUEUING_NOT_ALLOWED","Policy map: [char]; with queuing action can not be attached  to a [char].","The policy map was incorrectly configured. A policy map with queuing actions can not be attached to a VLAN target as the transmit queues are supported on the port level only but not on a VLAN or port-channel level.","Remove the queuing actions from the policy map and try to re-attach the service policy."
"C4K_HWQOSMAN","4","NOFREEDROPTHRESHOLDTABLEENTRY","No free entries are available in the drop threshold table in  hardware for port  [char] transmit queue  [dec]","The specified threshold values for transmit queue on the specified port cannot be applied as there are no free entries left in hardware.","Reduce the number of unique thresholds configured on transmit queues to the system defined limits."
"C4K_HWQOSMAN","4","OUTOFMEMORYORPOLICERRESOURCES","Out of memory or policer resources","Software failed to allocate memory for a policer while processing the QoS configuration. This could be because either the policer configuration exceeded its maximum supported limit or current IOS memory utilization is high.","Remove policers from unwanted policies and retry the operation."
"C4K_HWQOSMAN","4","OUTOFPOLICERTYPE","Out of memory or fragmented hw utilization or out of policier resources of type  [char]","Software failed to allocate single or dual rate policer either due to reaching the hardware limitation or the current usage of hardware policer resources prevents the allocation of dual rate policers. IOS memory utilization is also one of the causes of this failure.","Remove policers from unwanted policies and retry the operation."
"C4K_HWQOSMAN","4","POLICERLARGEBURSTVALUE","Policer burst value of  [dec] bytes for a policer  rate of  [dec] bps is not supported. Rounding the  burst to value of  [dec] bytes","The user specified burst value for a given policing rate is too high to be supported in hardware. The burst value will be rounded to the maximum supportable value for a given policer rate. The policer will continue to work at the burst value specified in the log message instead of the configured user rate.","As the configured burst value can't be supported, lower the burst value specified in the IOS policer configuration. If this action is not performed there will be a discrepancy between the configured policer rate and the applied policer rate."
"C4K_IOSQOSMAN","4","FAILTOCONSTRUCTQOSACTION","Software failed to process the QoS actions specified in  the policy map  [char] when attaching it to the target.","The software was unable to process the actions specified in the service policy. This could be because the maximum number of supported QoS targets was reached. The QoS policy will still be applied but no QoS action will be taken until resources are freed on from other QoS targets.","Check if the service policy on other targets can be detached in order to free up some resources."
"C4K_IOSQOSMAN","4","OUTOFMEMORY","Out of Memory while attaching service policy  [char] in the  [input/output]  direction to target  [char]","The software was unable to allocate memory while preparing to attach a service policy to the specified target. This could be because maximum the number of allowed configurations was already reached. The QoS policy will not be applied in the specified direction.","No action is required. If the limits have not been exceeded, contact your Cisco Technical Support representative with your configuration."
"C4K_RADIANMAN","3","BRINGUPFAILED","Radian [dec] bringup failed","Radian stub ASIC bringup failed. The ports under this ASIC might not be functioning.","If this issue persists, please record the error message and contact Cisco technical support."
"C4K_REDUNDANCY","1","VTP_CONFIG_DISLOCATE","VTP config file must be in default location for the system  to work in SSO mode","The system failed to reach SSO mode because the VTP configuration file is not i n the default location. In a catalyst 4500 switch, the default VTP configuration file is cat4000_flash:vlan.dat.","Reset the standby supervisor and remove the VTP filename configuration by using the no vtp file command."
"C4K_REDUNDANCY","2","C4K_ISSU_INFRA_INIT","C4k ISSU client [dec] initialization failed to [char].  Error: [dec] ([char])","A cat4k platform ISSU client could not be initialized. This initialization failure must be addressed before in-service software upgrade or downgrade can be performed successfully. If you do not address this failure, there will be downtime during software upgrade or downgrade.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_REDUNDANCY","2","HANDSHAKE_TIMEOUT_ACTIVE","The handshake messaging between active and standby has not yet started.","The initial handshake message exchange between active and standby supervisor engines has not yet started. Traffic on the active supervisor engine is not affected, but supervisor engine redundancy will not work.","Schedule a downtime ASAP and reset the active supervisor engine."
"C4K_REDUNDANCY","2","HANDSHAKE_TIMEOUT_STANDBY","The handshake messaging between standby and active has not yet started.","The initial handshake message exchange between standby and active supervisor engines has not yet started. If the active supervisor engine has not completed its initialization, this message may be seen temporarily on the standby supervisor engine. This condition will correct itself once the active supervisor engine initialization is complete. If problems persist after the active supervisor engine is initialized then redundancy will not work.","Schedule a downtime ASAP and reset the active supervisor engine."
"C4K_REDUNDANCY","2","INCOMPATIBLE_SUPERVISORS","[char]","For proper operation of redundancy, the supervisor engines must be of the same model. In this condition redundancy operations are not available and the standby supervisor engine is disabled because the supervisor engines present are of different models.","Configure the hardware so that the active and standby supervisor engines are of the same model."
"C4K_REDUNDANCY","2","IOS_VERSION_CHECK_FAIL","[char]","The active and standby supervisor engine software is different. In this condition, redundancy operations are not guaranteed.","Configure the active and standby supervisor engines to use the same version of software."
"C4K_REDUNDANCY","2","IOS_VERSION_INCOMPATIBLE","[char]","The system detected an incompatible redundancy condition. The active supervisor engine is running Cisco IOS Release 12.2 or later releases and the standby supervisor engine is running Cisco IOS Release 12.1. The system will reset the standby supervisor engine.","Configure the switch so that the active and standby supervisor engines are running the same release of Cisco IOS software."
"C4K_REDUNDANCY","2","ISSU_INIT","Galios Redundancy ISSU client initialization failed to [char].  Error: [dec] ([char])","The Galios Redundancy ISSU client could not be initialized. This initialization failure must be addressed before in-service software upgrade or downgrade can be performed successfully. If you do not address this failure, there will be downtime during software upgrade or downgrade.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_REDUNDANCY","2","NON_SYMMETRICAL_REDUNDANT_SYSTEM","[char]","The active and standby supervisor engine hardware is different. In this condition, redundancy operations are not guaranteed.","Configure the hardware so that the active and standby supervisor engines are identical."
"C4K_REDUNDANCY","2","POSTFAIL","POST failure on [char] supervisor detected. [char]","The active supervisor engine failed POST. The current standby supervisor engine resets the current active supervisor engine to standby and attempts to become the active supervisor engine. If the standby supervisor engine failed POST, then it will suspend at bootup and stay there. During this time if the active supervisor engine fails, then the standby supervisor engine will also reboot because it is not a fully functional standby supervisor engine at this point.","Run offline diagnostics on the failed supervisor engine to isolate the problem."
"C4K_REDUNDANCY","2","POSTFAIL_RESET","POST failure on ACTIVE supervisor detected. [char]","The active supervisor engine failed POST but detected the standby supervisor engine at bootup. The active supervisor engine will reset itself so that the standby supervisor engine can take over as the new active supervisor engine.","Run offline diagnostics on the failed supervisor engine to isolate the failure. Immediate action is not needed for the switch to operate, but redundancy will not be available until there is a second functional supervisor engine."
"C4K_REDUNDANCY","2","POSTFAIL_RESET","POST failure on ACTIVE supervisor detected. [char]","The active supervisor engine failed POST but detected the standby supervisor engine at bootup. It is attempting to reset itself so that the standby supervisor engine can take over as the new active supervisor engine.","You may need to replace the supervisor engine that failed POST. Contact your technical support representative."
"C4K_REDUNDANCY","2","SEND_NEGO_FAILED","Redundancy ISSU client failed to send negotiation message.  Error: [dec] ([char])","The redundancy ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","Using the show issu compatibility matrix command, verify that both the active and standby supervisor engines have software supporting ISSU. Reset the standby supervisor engine using the redundancy reload peer command. If problems persist, contact a Cisco technical support representative."
"C4K_REDUNDANCY","2","SESSION_REGISTRY","Redundancy ISSU client failed to register session information. Error: [dec] ([char])","The Redundancy ISSU client failed to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly.","Using the show issu compatibility matrix command, verify that both the active and standby supervisor engines have software supporting ISSU. Reset the standby supervisor engine using the redundancy reload peer command. If problems persist, contact a Cisco technical support representative."
"C4K_REDUNDANCY","2","VS_REBOOT_ON_RPR_FALLBACK","Supervisor in virtual-switch configuration cannot operate in redundancy mode RPR","The redundancy infrastructure detected a situation whereby it is not possible to continue operation in Stateful Switchover (SSO) mode, and the system must fall back to Route Processor Redundancy (RPR) mode. However, RPR is not a viable operational mode in a virtual-switch environment. As a result, the supervisor engine is reset.","The redundancy mode falls back to RPR when some kind of mismatch is detected between the two virtual-switch supervisors. Examples are: hardware mismatch, license mismatch, incompatible IOS-XE versions and incompatible software configuration. Determine the cause of the mismatch, then boot the virtual-switch chassis one at a time to address the cause of the mismatch."
"C4K_REDUNDANCY","3","CAP_INVALID_SIZE","Galios Redundancy ISSU client capability list is empty.","The Redundancy ISSU client capability exchange list is too large.","Copy the error message exactly as it appears on the console or in the system log. Issue the show issu capability entries <Client_ID> command to gather data that may help identify the nature of the error, and contact Technical support."
"C4K_REDUNDANCY","3","CAP_NOT_COMPATIBLE","Galios Redundancy ISSU client capability exchange result  incompatible.","The Redundancy ISSU client capability exchange have negotiated as incompatible with the peer.","Copy the error message exactly as it appears on the console or in the system log. Issue the show issu negotiated capability <Session_ID> command to gather data that may help identify the nature of the error, and contact Technical support."
"C4K_REDUNDANCY","3","COMMUNICATION","Communication with the peer Supervisor  has been [char]","The status of the peer supervisor engine communication path changed.","This is an informational message only; no action is required."
"C4K_REDUNDANCY","3","MSG_NOT_COMPATIBLE_WITH_PEER","'MessageType [dec]' is not supported by Galios Redundancy ISSU client  at peer","The Redundancy ISSU client at the peer supervisor is not compatible for this message type. The Redundancy client will be marked as incompatible with the peer.","Copy the error message exactly as it appears on the console or in the system log. Issue the show issu message group <client_id>, show issu session <client_id>, and show issu negotiated version <session_id> commands to gather data that may help identify the nature of the error, and contact Technical support."
"C4K_REDUNDANCY","3","MSG_NOT_OK","Galios Redundancy ISSU client 'Message Type [dec]' is not compatible","The Galios Redundancy ISSU client received an incompatible message from the peer device. The message cannot be processed.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_REDUNDANCY","3","MSG_SIZE","Redundancy ISSU client failed to get the MTU for Message  Type [dec]. Error: [dec] ([char])","The Redundancy ISSU client failed to calculate the MTU for the specified message. The Redundancy ISSU client is not able to send the message to the standby device.","Using the show issu compatibility matrix command, verify that both the active and standby supervisor engines have software supporting ISSU. Reset the standby supervisor engine using the redundancy reload peer command. If problems persist, contact a Cisco technical support representative."
"C4K_REDUNDANCY","3","NOT_READY_FOR_SWITCHOVER","The active Supervisor failed but standby supervisor cannot initiate  Switchover activity. Resetting standby Supervisor.","The standby supervisor engine is currently in an intermediate state and cannot take over for the primary supervisor engine.","This is an informational message only; no action is required."
"C4K_REDUNDANCY","3","PEER_RELOAD","The peer Supervisor is being reset because [char]","The supervisor engine was reset for the reason specified by [char]. See the reported error message for the specific reason. This allows recovery from an indeterminate standby state.","This is an informational message only; no action is required."
"C4K_REDUNDANCY","3","SESSION_UNREGISTRY","Redundancy ISSU client failed to unregister session  information. Error: [dec] ([char])","The redundancy ISSU client failed to unregister session information. This message should only appear while the standby supervisor engine is reloading or if it has been physically removed from the switch. If this message appears while the standby supervisor engine is in normal operation, there may be a software problem but it will probably not affect redundancy functionality.","Check for existing ISSU sessions using the show issu session command, there should not be any open sessions during a reload of the standby supervisor engine. Contact a Cisco technical support representative if additional errors are seen after the standby supervisor engine restarts and initializes."
"C4K_REDUNDANCY","3","SIMPLEX_MODE","The peer Supervisor has been lost","The peer supervisor engine is absent, and the switch shifted to nonredundant mode.","This is an informational message only; no action is required."
"C4K_REDUNDANCY","3","TRANSFORM_FAIL","Redundancy ISSU client [char] transform failed for  'Message Type [dec]'. Error: [dec] ([char])","The Redundancy ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In both cases, the Redundancy state between the active device and the standby device is not identical.","Using the show issu compatibility matrix command, verify that both the active and standby supervisor engines have software supporting ISSU. Reset the standby supervisor engine using the redundancy reload peer command. If problems persist, contact a Cisco technical support representative."
"C4K_REDUNDANCY","4","CONFIGSYNCFAIL","Persistent-config Sync to Standby supervisor failed.","The active supervisor engine failed to receive a confirmation message from the standby supervisor engine. There is a potential problem with the standby supervisor engine.","Contact your technical support representative."
"C4K_REDUNDANCY","4","KEEPALIVE_WARNING","Keepalive messages from peer Supervisor are  missing for [dec] seconds","Keepalive messages have not been sent from the peer supervisor engine. If the situation persists and the keepalive messages do not resume, the peer supervisor engine will eventually be reset. This message is logged for every third missed keepalive message.","This is an informational message only; no action is required."
"C4K_REDUNDANCY","5","CALENDAR","The calendar has been successfully synchronized to the standby   supervisor for the first time","The calendar was successfully synchronized to the standby supervisor engine for the first time.","This is an informational message only; no action is required."
"C4K_REDUNDANCY","5","CALENDAR_RATELIMIT","The calendar has been successfully synchronized to the standby supervisor [dec] times since last calendar syslog","The calendar was successfully synchronized to the standby supervisor engine the specified number of times.","This is an informational message only; no action is required."
"C4K_REDUNDANCY","5","CONFIGSYNC","The [char] has been successfully synchronized to the standby supervisor","The configuration was successfully synchronized to the standby supervisor engine. [char] can be either a private configuration or a startup configuration.","This is an informational message only; no action is required."
"C4K_REDUNDANCY","5","CONFIGSYNC_RATELIMIT","The [char] has been successfully synchronized to the standby supervisor","The configuration was successfully synchronized to the standby supervisor engine. This is a rate-limited message. These messages are logged at 1-minute intervals, rather than continuously as with many other messages.","This is an informational message only; no action is required."
"C4K_REDUNDANCY","6","ACTIVESUPNOTFOUND","Active supervisor not found.","This message is displayed on the redundant supervisor engine when it fails to communicate with the active supervisor engine.","This is an informational message only; no action is required."
"C4K_REDUNDANCY","6","ATTEMPTINGTOBECOMEACTIVE","Attempting to become active supervisor.","This message is displayed on the standby supervisor engine when it fails to communicate with the active supervisor engine and attempts to take over as the active supervisor engine.","This is an informational message only; no action is required."
"C4K_REDUNDANCY","6","DUPLEX_MODE","The peer Supervisor has been detected","A peer supervisor engine was detected, and the switch shifted to duplex mode.","This is an informational message only; no action is required."
"C4K_REDUNDANCY","6","INIT","Initializing as [char] supervisor","A supervisor engine that you are connected to is currently initializing as either the active or standby supervisor engine.","This is an informational message only; no action is required."
"C4K_REDUNDANCY","6","MODE","[char] supervisor initializing for [char] mode","The supervisor engine that you are not directly connected to is currently initializing as either the active or standby supervisor engine in RPR mode.","This is an informational message only; no action is required."
"C4K_REDUNDANCY","6","SWITCHOVER","Switchover activity detected","The standby supervisor engine detected switchover activity.","This is an informational message only; no action is required."
"C4K_HWRETMAN","3","PARITYERROR","[char] parity error, seen [dec]","The hardware reported a parity error. This could indicate a transient hardware problem, or a more permanent problem.","If you see this message too often, reboot the switch."
"C4K_RKACLMAN","4","IPV6FLAGSNOTSUPPORTED","IPv6 flag matching is not supported.","Ipv6 Flags are not supported and ignored.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_RKIOSVS","2","VSLMODULEOIRD","Unable to reconcile vsl port config info sent from standby","This may occur when modules are removed or OIRed from the standby switch when the standby switch is down.","Verify the VSL configurations from the running-config. Missing or stale VSL configuration must be fixed or configured manually and saved."
"C4K_RKIOSVS","3","EMPTYREMOTEVSLPORTCHANNELSYNCED","Remote vsl port channel is not set","This error condition is logged on the active supervisor when the remote VSL port channel received in a sync message is 0.","The VSL port channel cannot be 0. Reconfigure the VSL port channel to a value other than zero."
"C4K_RKIOSVS","3","UNSUPPORTEDREMOTEVSLPORTCHANNELSYNCED","Conflict in remote vsl port channel, same as local port channel( Po[dec])","This error condition is logged on the active supervisor when a remote VSL port channel received in a sync message is identical to the configured local VSL port channel.","VSLport channels on both the member switches cannot be the same. Reconfigure the VSL port channels on the member switches with unique values."
"C4K_RKIOSVS","7","CONFIGUREPORTCHANNEL","RkiosVs: [char] Port-channel[dec] [char]","Occurs when a port channel is configured or unconfigured after receiving VSL config from the remote member.","Informational debug message only. No action is required."
"C4K_RKIOSVS","7","CONFIGUREVSLINTERFACE","RkiosVs: [char] [char] [char] Port-channel[dec]","Logged when a remote VSL interface is added or deleted from a port channel after receiving VSL config from a remote member.","Informational debug message only. No action is required."
"C4K_S2W","4","READCALENDARERR","Calendar read operation Failed: [object-info]","The calendar read operation failed.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_S2W","4","STARTCALENDAROSCILLATORERR","Failed to start the calendar","The calendar operation failed to start.","This is an informational message only; no action is required."
"C4K_S2W","4","WRITECALENDARERR","Calendar write operation failed [object-info]","The system was unable to write to the calendar.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_SPD","3","SDRAMDATAINVALID","Invalid Sdram Spd Data on DIMM module  [dec] . Total  Sdram on the supervisor is  [dec] MB.","There is a SDRAM SPD data checksum error, the data is invalid.","Use the show platform spd sdram command for more details. If a DIMM module is bad, it needs to be returned to Cisco for replacement."
"C4K_SPD","3","SDRAMREADERROR","DIMM module  [dec] Spd Read Error:  [char] . Total Sdr am on the supervisor is  [dec] MB.","The system encountered a problem when reading SDRAM SPD data.","Use the show platform spd sdram command for more details. If a DIMM module is bad, it needs to be returned to Cisco for replacement."
"SFF8472","2","NOMEM","Not enough memory available for [char]","The SFF8472 subsystem could not obtain the memory that it needed.","Contact your technical support representative."
"SFF8472","3","INTERNAL_ERROR","[char]","The SFF8472 subsystem encountered an internal software error. The error message contains text that can be used to help identify the cause of the problem.","Contact your technical support representative."
"SFF8472","3","READ_ERROR","[char]","There was an error reading digital optical monitoring information from the transceiver at the specified interface.","Try removing and reinserting the transceiver. If it still does not work, replace the transceiver."
"SFF8472","3","UNEXPECTEDEVENT","Process received unknown event (maj [hex] min [hex]).","A process received an event it did not know how to handle. A process can register to be notified when various events occur in the router.","Contact your technical support representative."
"SFF8472","5","THRESHOLD_VIOLATION","[char]: [char]; Operating value: [char], Threshold value: [char].","The specified port is not connected, or it is connected to a damaged fiber optic cable.","If the message relates to an enabled but unconnected DOM transceiver, shut the port to stop the alarm messages. If the alarm persists, or relates to an enabled and connected transceiver, contact your Cisco technical support representative."
"SFF8472_FLOAT","3","INTERNAL_ERROR","[char]","The SFF8472 floating-point subsystem encountered an internal software error. The error message contains text that can be used to help identify the cause of the problem.","Contact your technical support representative."
"C4K_SISFMAN","4","OUTOFRESOURCES","Resources for constructing ACLs are not available.Recommended Action    Sofware resources are not available to setup hardware to drop IPv6 Router Advertisements or Redirect packets.","Try unconfiguring other TCAM related features to reduce switch memory requirements and reconfigure your feature.SPANTREE MessagesThis section contains the Spanning Tree Protocol (SPANTREE) messages.SPANTREE-2Error Message    SPANTREE-2-BLOCK_BPDUGUARD:Received BPDU on port [char] with BPDU Guard enabled. Disabling port.Explanation    A BPDU was received in the specified interface that has the spanning tree BPDU guard feature enabled. As a result, the interface was administratively shut down.","Remove the device sending BPDUs, or disable the BPDU guard feature. BPDU guard can be locally configured on the interface or globally configured on all ports that have PortFast enabled. After you resolve the conflict, reenable the interface by entering the no shutdown command in interface configuration mode."
"SPANTREE","2","BLOCK_BPDUGUARD_VP","Received BPDU on port [char]","A BPDU was received on the interface and VLAN specified in the error message. The spanning tree BPDU Guard feature was enabled and configured to shutdown the VLAN. As a result, the VLAN was placed in the error-disabled state.","Either remove the device sending BPDUs or disable the BPDU Guard feature. The BPDU Guard feature can be locally configured on the interface or globally configured on all ports that have portfast enabled. After the conflict has been resolved, reenable the interface/VLAN by entering the clear errdisable command."
"SPANTREE","2","BLOCK_PVID_LOCAL","Blocking [char] on [char]. Inconsistent local vlan.","The spanning tree port that is associated with the listed spanning tree instance [char] and interface [char] is held in spanning tree blocking state until the port VLAN ID (PVID) inconsistency is resolved. The listed spanning tree instance is that of the native VLAN ID of the listed interface.","Verify that the configuration of the native VLAN ID is consistent on the interfaces at each end of the 802.1Q trunk connection. When the configuration is consistent, spanning tree automatically unblocks the interfaces."
"SPANTREE","2","BLOCK_PVID_PEER","Blocking [char] on [char]. Inconsistent peer vlan.","The spanning tree port (with spanning-tree port ID [char]) that is associated with the listed instance and interface is held in blocking state until the port VLAN ID (PVID) inconsistency is resolved. The listed spanning tree instance is that of the native VLAN ID of the interface on the peer switch to which the listed interface is connected.","Verify that the configuration of the native VLAN ID is consistent on the interfaces on each end of the 802.1Q trunk connection. When corrected, spanning tree automatically unblocks the interfaces."
"SPANTREE","2","CHNL_MISCFG","Detected loop due to etherchannel misconfiguration of [chars] [chars]","A misconfigured channel group (with channel group ID [chars]) was detected. For example, the ports of one side of the EtherChannel either are not configured to be in the channel or failed to bundle, while ports on the other side of the EtherChannel are successfully bundled.","Locate the misconfigured local ports by entering the show interfaces status err-disabled command. Check the EtherChannel configuration on the remote device by entering the show etherchannel summary command on the remote device. After the configuration is corrected, enter the shutdown command followed by the no shutdown command to restart the associated port-channel interface."
"SPANTREE","2","LOOPGUARD_BLOCK","Loop guard blocking port [char] on [char].","The spanning tree message age timer expired, because no BPDUs were received from the designated bridge. Because this condition could be caused by an unidirectional link failure, the interface is put into blocking state and marked as loop guard inconsistent in order to prevent possible loops from being created.","Use the show spanning-tree inconsistentports command to review the list of interfaces with loop guard inconsistencies. Determine why devices that are connected to the listed ports are not sending BPDUs. One reason could be that they do not run the Spanning Tree Protocol; in this case, you should disable loop guard in the inconsistent interfaces or start the Spanning Tree Protocol on the other side of the links, depending on the context. Another reason could be a failure in the cable. If the link has a failure that makes it unidirectional (you can transmit, but you cannot receive), you should replace the old cable with a new cable."
"SPANTREE","2","LOOPGUARD_CONFIG_CHANGE","Loop guard [char] on port [char].","There was a change in the spanning tree loop guard configuration for the listed interface. When enabled, the interface will be put into blocking state and marked as loop guard inconsistent when the message age timer expires because no BPDUs were received from the designated bridge. This feature is used to detect unidirectional links.","Verify that this is the desired configuration for the listed interface. Correct it if this is not the desired configuration; otherwise, no further action is required."
"SPANTREE","2","LOOPGUARD_UNBLOCK","Loop guard unblocking port [char] on [char].","The listed interface received a BPDU, and if the inconsistency was due to an unidirectional link failure, the problem does not exist anymore. The loop guard inconsistency is cleared for the interface, which is taken out of the blocking state.","This is an informational message only; no action is required."
"SPANTREE","2","PVSTSIM_FAIL","Blocking [char] port [char]: Inconsitent [char] PVST BPDU received on VLAN [dec]","When a PVST+ switch is connected to an MST switch, the CIST (MSTOO) becomes the root for all PVST+ spanning trees. Looping occurs if any PVST+ spanning tree has a root with a better preference than IST. To prevent looping, the port, which is on the MST switch that receives the superior message from the PVST+ side, is blocked by root guard.When STP is converging after a new switch or a switch port is added to the topology, this condition occurs transiently. The port unblocks automatically in such cases.","If the port remains blocked, identify the root bridge as reported in the message, and configure a worse priority for the VLAN spanning tree. There could be better PVST roots than the message indicates, and the port will not recover until all such roots are cleared. If you are unsure whether the roots are cleared, disable and enable the port again."
"SPANTREE","2","PVSTSIM_OK","PVST Simulation inconsistency cleared on port [char].","The listed interface is no longer receiving PVST BPDUs advertising information inconsistent with the CIST port information. The PVST simulation inconsistency is cleared and the interface returns to normal operation.","This is an informational message only; no action is required."
"SPANTREE","2","RECV_1Q_NON_1QTRUNK","Received 802.1Q BPDU on non 802.1Q trunk [char] [char].","A Shared Spanning Tree Protocol (SSTP) bridge protocol data unit (BPDU) was received on the listed interface. The interface was in trunk mode but was not using 802.1Q encapsulation. The interface ID is [char].","Verify that the configuration and operational state of the listed interface and the interface to which it is connected are in the same mode (access or trunk). If the mode is trunk, verify that both interfaces have the same encapsulation (ISL or 802.1Q). Once these parameters are consistent, spanning tree automatically unblocks the interface."
"SPANTREE","2","RECV_BAD_TLV","Received SSTP BPDU with bad TLV on [char][char].","The listed interface received an SSTP BPDU that was missing the VLAN ID tag. The BPDU is discarded. [char] is the interface ID.","If the error message reappears, copy the message exactly as it appears on the console or in the system log, contact your technical support representative, and provide the representative with the gathered information."
"SPANTREE","2","RECV_PVID_ERR","Received BPDU with inconsistent peer vlan id [dec] on [char] [char]","The listed interface received an SSTP BPDU that is tagged with a VLAN ID that does not match the VLAN ID on which the BPDU was received. This condition occurs when the native VLAN is not consistently configured on both ends of an 802.1Q trunk. [dec] is the VLAN ID. The interface ID is [char].","Verify that the configuration of the native VLAN ID is consistent on the interfaces on each end of the 802.1Q trunk connection. Once the configuration is consistent, spanning tree automatically unblocks the interfaces."
"SPANTREE","2","ROOTGUARD_BLOCK","Root guard blocking port [char] on [char].","A BPDU was received on the listed interface that advertised a spanning tree root bridge that was superior to the one already in use. The interface is put into a blocking state and marked as root guard inconsistent to prevent a suboptimal spanning tree topology from forming.","Enter the show spanning-tree inconsistentports command to review the list of interfaces with root guard inconsistencies. Determine why devices that are connected to the listed ports are sending BPDUs with a superior root bridge, and then take action to prevent further occurrences. Once the invalid BPDUs have been stopped, the interfaces automatically recover and resume normal operation. By looking at the configuration, ensure that it is appropriate to enable root guard on the interface."
"SPANTREE","2","ROOTGUARD_CONFIG_CHANGE","Root guard [char] on port [char].","There was a change in the spanning tree root guard configuration for the listed interface. If root guard is enabled, any BPDU that is received on the interface that advertises a superior spanning tree root bridge to the one that is already in use will cause the interface to be put into blocking state and marked as root guard inconsistent.","Verify that this is the correct configuration for the listed interface. If this is not the correct configuration, change the configuration to one that is appropriate for the interface."
"SPANTREE","2","ROOTGUARD_UNBLOCK","Root guard unblocking port [char] on [char].","The listed interface is no longer receiving BPDUs that are advertising a superior root bridge. The root guard inconsistency is cleared for the interface and then is taken out of the blocking state if appropriate.","This is an informational message only; no action is required."
"SPANTREE","2","UNBLOCK_CONSIST_PORT","Unblocking [char] on [char]. Port consistency restored.","The port VLAN ID and/or port type inconsistencies have been resolved. The Spanning Tree Protocol will unblock the listed interface of the spanning tree instance. The interface ID is [char].","This is an informational message only; no action is required."
"SPANTREE","3","BAD_PORTNUM_SIZE","Rejected an attempt to set the port number field size to [dec] bits (valid range is [dec] to [dec] bits).","The spanning tree port identifier is a 16-bit field that is, by default, divided evenly between the port priority and the port number. Each subfield is 8 bits wide, allowing the port number field to represent port numbers between 1 and 255. On systems with more than 255 ports, the STP subsystem must increase the size of the port number portion of the port ID to support the greater number of ports. This condition occurs at system initialization because the maximum number of ports on a particular platform will not change. This error occurs because of an error in the platform-specific code that caused it to request more (or fewer) bits than were possible.","Contact your technical support representative."
"SPANTREE","3","ERR_NO_UNIDIR_EDGE","[char]: Portfast disabled.","Because UCP is for edge ports only, portfast must be configured. This message is typically seen when spanning-tree portfast is enabled on a port, then authentication control-direction is set to inbound (unidirectional), and then portfast is disabled.","Re-enable portfast on the edge port. This will re-enable uni-directional authentication control."
"SPANTREE","3","PORT_SELF_LOOPED","[char] disabled.- received BPDU src mac ([mac-addr])  same as that of interface","A BPDU with a source MAC address that matches the address assigned to the listed interface was received. A port looped back on itself, possibly due to a diagnostic cable that was plugged into the interface. The interface is administratively shut down. [char] is the interface ID.","Check the interface configuration and any cable that is plugged into the interface. Once the problem is resolved, reenable the interface by entering the no shutdown command on the interface."
"SPANTREE","3","PRESTD_NEIGH","pre-standard MST interaction not configured ([char]). Please","The switch has received a pre-standard MST BPDU transmission on a port that is not configured for it. The switch will automatically adjust its mode of operation on this port and will start sending pre-standard BPDUs. However, this auto-detection of pre-standard neighbors is not 100% accurate, and it is recommended to explicitly configure the port for pre-standard MST BPDU transmission. This warning message is displayed only once.","Use the spanning-tree mst pre-standard configuration command on all ports that are connected to switches running Cisco's pre-standard version of MST. Migrate all switches in the network to the IEEE standard MST version when it is possible."
"SPANTREE","4","PORT_NOT_FORWARDING","[char] [char] [char] [char]","The specified interface is not in the forwarding state and forwarding packets.","Contact your technical support representative."
"SPANTREE","5","EXTENDED_SYSID","Extended SysId [char] for type [char]","The extended system ID feature was either enabled or disabled for the given type of spanning tree. If the feature was enabled, the spanning tree instance identifier is stored in the lower portion of the bridge ID priority field; this will cause the allowed values for the bridge priority to be limited to the range of 0 to 61,440, in increments of 4096. If the feature was disabled, the bridge ID priority field consists entirely of the configured priority, but some spanning tree features might not be available on a given platform (for example, 4096 VLAN support).","This is an informational message only; no action is required."
"SPANTREE","5","ROOTCHANGE","Root Changed for [char] [dec]:  New Root Port is [char]. New Root Mac Address is [mac-addr]","The root changed for an instance of spanning tree.","This is an informational message only; no action is required."
"SPANTREE","5","TOPOTRAP","Topology Change Trap for [char] [dec]","A trap was generated to indicate the change in topology.","This is an informational message only; no action is required."
"SPANTREE","6","PORTADD_ALL_VLANS","[char] added to all Vlans","The interface has been added to all VLANs.","This is an informational message only; no action is required."
"SPANTREE","6","PORTDEL_ALL_VLANS","[char] deleted from all Vlans","The interface has been deleted from all VLANs.","This is an informational message only; no action is required."
"SPANTREE","6","PORT_STATE","Port [char] instance [dec] moving from [char] to [char]","The spanning tree port changed to another state.","This is an informational message only; no action is required."
"SPANTREE","7","BLOCK_PORT_TYPE","Blocking [char] on [char]. Inconsistent port type.","The listed interface is being held in spanning tree blocking state until the port type inconsistency is resolved. The port ID is [char].","Verify that the configuration and operational state of the listed interface and that of the interface to which it is connected are in the same mode (access or trunk). If the mode is trunk, verify that both interfaces have the same encapsulation type (ISL or 802.1Q). When these parameters are consistent, spanning tree automatically unblocks the interface."
"SPANTREE","7","PORTDEL_SUCCESS","[char] deleted from Vlan [dec]","The interface was deleted from the specified VLAN.","This is an informational message only; no action is required."
"SPANTREE","7","RECV_1Q_NON_TRUNK","Received 802.1Q BPDU on non trunk [char] [char].","An SSTP BPDU was received on the listed interface, which is not an operational trunking interface. The interface ID is [char].","Verify that the configuration and operational state of the listed interface and that of the interface to which it is connected are in the same mode (access or trunk). If the mode is trunk, verify that both interfaces have the same encapsulation type (none, ISL, or 802.1Q). Once these parameters are consistent, spanning tree automatically unblocks the interface."
"SPANTREE_FAST","7","PORT_FWD_UPLINK","[char] [char] moved to Forwarding (UplinkFast).","The listed interface was selected as the new root port for the listed spanning tree instance.","This is an informational message only; no action is required."
"SPANTREE_VLAN_SW","2","MAX_INSTANCE","Platform limit of [dec] STP instances exceeded. No instance created for [char] (port [char]).","The number of currently active VLAN spanning tree instances reached a platform-specific limit. No additional VLAN instances will be created until the number of instances drops below that limit.","Reduce the number of currently active spanning tree instances by either disabling some of the instances or deleting the VLANs that are associated with them. You need to manually enable those spanning trees that cannot be created due to limited instances."
"STORM_CONTROL","3","FILTERED","A [char] storm detected on [char]. A packet filter action has been applied on the interface.","The amount of traffic detected on the interface exceeded the configured threshold values. The system filters excess traffic when a packet is received. The system is not forwarding packet traffic.","Determine and fix the root cause of the excessive traffic on the interface."
"STORM_CONTROL","3","SHUTDOWN","A packet storm was detected on [char]. The interface has been disabled.","The amount of traffic detected on the interface exceeded the configured threshold values. Because the interface was configured to be shut down if a packet storm event is detected, it was placed in an errdisable state.","If automatic recovery is preferred, the errdisable recovery mechanism can be used. Determine and fix the root cause of the excessive traffic on the interface."
"C4K_STORE","2","OUTOFCHUNKS","Out of chunks of memory","The system has insufficient memory.","Reboot the switch. If this message reoccurs, add additional memory."
"C4K_SUPERVISOR","0","SUPNOTSUPPORTEDINCHASSIS","The WS-X4013+TS supervisor is not supported in chassis type [char]","The WS-X4013+TS is supported only in the Catalyst 4503 chassis. Either the WS-X4013+TS supervisor engine is in a chassis with more than 3 slots, which is a misconfiguration and not supported, or the chassis' serial EEPROM is programmed incorrectly and contains the wrong chassis type.","If this chassis has more than 3 module slots, the WS-X4013+TS is not supported in it. If the chassis has 3 slots, and you see this message, collect the output of the show idprom chassis command and call Cisco TAC. This chassis needs to be returned to Cisco."
"C4K_SUPERVISOR","2","FPGASOFTERROR","[char]","An inconsistency was detected in the memory referred to in this message","A reload of the system may be required. It is recommended that a reload be scheduled at the next available maintenance period."
"C4K_SUPERVISOR","2","MUXBUFFERNOTPRESENT","Mux buffer (WS-X4K-MUX) [dec] is not present","The WS-X4K-MUX mux buffer for slot [dec] is either not connected to the backplane properly or is not present. If the switching module present in this slot cannot be identified, its SEEPROM cannot be read and it will be unusable.","Reseat the mux buffers in the backplane. If the message persists, contact your technical support representative."
"C4K_SUPERVISOR","2","SOFTERROR","memory inconsistency detected","An inconsistency was detected in the memory referred to in this message.","A reload of the system may be required. It is recommended that a reload be scheduled at the next available maintenance period."
"C4K_SUPERVISOR","2","SOFTERRORRELOADNEEDED","memory inconsistency detected: a reload of this supervisor is required to apply the new configuration","An inconsistency was detected in the specified memory.","Schedule a reload at the next maintenance period."
"C4K_SUPERVISOR","3","BACKPLANESEEPROMREADFAILED","Failed to read backplane's serial eeprom, read [dec], expected size [dec]","A failure occurred when reading the backplane serial EEPROM.","Power cycle the switch. If the problem persists, contact your technical support representative. You will probably need to return the backplane for repair."
"C4K_SUPERVISOR","3","CLOCKMODULESEEPROMREADFAILED","Failed to read clock module's seeprom","A failure occurred while reading the clock module serial EEPROM. This message should occur only in a prototype switch used in an early field trial.","Check the chassis serial EEPROM information. Contact your technical support representative. You may need to return some switch components for repair or replacement."
"C4K_SUPERVISOR","3","CSRAMINITERROR","[char]","Initial CSRAM reset sequence failure. This could indicate a transient or a more permanent problem.","Reboot the system to check if the problem goes away. After multiple retries if it does not go away, save the console logs and contact the Cisco Technical Assistance Center."
"C4K_SUPERVISOR","3","CSSPLINITERROR","[char]","Initial K5 CSSPL interface reset sequence failure. This could indicate a transient or a more permanent problem.","Reboot the system to check if the problem goes away. After multiple retries if it does not go away, save the console logs and contact the Cisco Technical Assistance Center."
"C4K_SUPERVISOR","3","DDRDLLOCKERROR","[char]","DDR-DL associated with DDR/QDR interfaces synchronization failure. This could indicate a transient or a more permanent problem.","Reboot the system to check if the problem goes away. After multiple retries if it does not go away, save the console logs and contact the Cisco Technical Assistance Center."
"C4K_SUPERVISOR","3","FANTRAYREADFAILED","Failed to read system fan tray status register from hardware","The fan tray presence was detected, but the system failed to read the fan tray status register contents.","If this message appears only once, this could be a transient error and no action is required. If this message appears repeatedly (once every 10 minutes), replace the system fan tray."
"C4K_SUPERVISOR","3","FANTRAYSEEPROMREADFAILED","Failed to read fan tray's seeprom","A failure occurred while reading the system fan tray serial EEPROM. This message should occur only in a prototype switch used in an early field trial.","Check the chassis serial EEPROM information. Contact your technical support representative. You may need to return some switch components for repair or replacement."
"C4K_SUPERVISOR","3","INITERROR","[char]","An error occurred during ASIC initialization on the Supervisor Engine. This could indicate a transient or a more permanent problem.","Reboot the system to check if the problem goes away. After multiple retries if it does not go away, save the console logs and contact the Cisco Technical Assistance Center."
"C4K_SUPERVISOR","3","LINKDFEMUXTRAININGSTATUSFAILURE","Internal Link Error in Mux Buffer: Slot([dec]) Link([dec]) Dir([dec])","An internal link between the mux buffer and its peer (either the supervisor or the linecard) has not come up because of an I2c bus error. This may impact traffic.","If traffic is impacted, pull out the linecard and reseat it. If traffic flow is not restored, issue the redundancy reload shelf CLI command to restart both supervisors in the chassis. If the redundancy command fails, contact Cisco TAC."
"C4K_SUPERVISOR","3","LINKDFETIMEDOUT","Module [dec] bpid([dec]) [char] dfe training from the [char]  timed out","NOT AVAILABLE YET.","Link DFE training did not complete before the end of bulk sync. This may affect traffic on the links that failed to complete DFE training."
"C4K_SUPERVISOR","3","LINKDFEWATCHDOGTIMEOUT","Module [dec] dfe training between [char] and Standby Sup  is not complete within expected time.","NOT AVAILABLE YET.","Link DFE training did not complete before the end of bulk sync. This may affect traffic on the links that failed to complete DFE training."
"C4K_SUPERVISOR","3","MUXBUFFERSEEPROMREADFAILED","Failed to read mux buffer [dec]'s serial eeprom","A failure occurred while reading the mux buffer serial EEPROM.","Power cycle the switch. If the serial EEPROM is still invalid, contact your technical support representative. You may need to return some switch components for repair or replacement."
"C4K_SUPERVISOR","3","NETFLOWCARDSEEPROMREADFAILED","Netflow Services Card seeprom read failed","A reading of the serial EEPROM on the NetFlow Services Card failed.","For more information, enter the sprom read nffc command at the ROMMON prompt."
"C4K_SUPERVISOR","3","NETFLOWCARDSEEPROMINVALID","Invalid Netflow Services Card seeprom data","The serial EEPROM on the NetFlow Services Card cannot be read or was not programmed.","For more information, enter the sprom read nffc command at the ROMMON prompt."
"C4K_SUPERVISOR","3","NETFLOWCARDSEEPROMUNKNOWNTYPE","Unknown Netflow Services Card revision: Read fru major/minor ([hex],[hex]) but expected ([hex],[hex]).","The serial EEPROM on the NetFlow Services Card has a revision that is not compatible with this release of software. The card will be ignored.","For more information, enter the sprom read nffc command at the ROMMON prompt."
"C4K_SUPERVISOR","3","PEERSUPERVISORRESETNEEDED","Resetting the peer supervisor","The peer supervisor will be reset to restore functionality. This should happen when upgrading the firmware on the other supervisor.","This reset is expected after a firmware upgrade of the peer supervisor. If the reset occurs without a firmware upgrade, contact Cisco support."
"C4K_SUPERVISOR","3","POWERSUPPLYSEEPROMREADFAILED","Failed to read power supply [dec]'s serial eeprom","A failure occurred while reading the power supply serial EEPROM.","Reinsert the power supply. If that does not work, replace the old power supply with a new power supply."
"C4K_SUPERVISOR","3","POWERSUPPLYSTATUSREADFAILED","Failed to read power supply [dec]'s status register","Reading the power supply status register failed.","Try reinserting the power supply. If the problem persists, hot swap it with a new power supply."
"C4K_SUPERVISOR","3","RETIMERDISABLEFAILED","Failed to disable the retimer of the active supervisor's uplink.","The retimer on the active supervisor engine cannot be initialized. In a redundant system, you might see packets that are transmitted out the active supervisor engine's nonactive uplink.","Disconnect the second uplink on the active supervisor engine."
"C4K_SUPERVISOR","3","RETIMERINITFAILED","Failed to initialize the retimer of the active supervisor's uplink.","The retimer on the active supervisor engine cannot be initialized. In a redundant system, you might see packets that are transmitted out the active supervisor engine's nonactive uplink.","Disconnect the second uplink on the active supervisor engine."
"C4K_SUPERVISOR","3","RKNOVAIFECSSPLINIT","Error on going to [char] Mode, Requires Reboot","An internal ASIC Init I/F failure has occurred. To continue switch operation while ignoring this message may result in packet drops and other errors.","Reboot the Supervisor. If this message persists, contact Cisco Technical Support."
"C4K_SUPERVISOR","3","RKNOVAIFECSSPLINIT","Error on executing Csspl Init data file, Requires Reboot","An internal ASIC Init I/F failure has occurred. To continue switch operation while ignoring this message may result in packet drops and other errors.","Reboot the Supervisor. If this message persists, contact Cisco Technical Support."
"C4K_SUPERVISOR","3","SEEPROMREADFAILED","Failed to read supervisor's serial eeprom, try reinserting supervisor","A reading of the supervisor engine's serial EEPROM failed. The read might fail if the module is not seated correctly in the slot.","Remove and reinsert the module. If that does not work, power cycle the switch. If the read still fails, contact your technical support representative. You may need to return some switch components for repair or replacement."
"C4K_SUPERVISOR","3","STATSMEMORYINCONSISTENCY","Statistics memory inconsistency detected","Statistics collection has been stopped. An inconsistency has been detected in the memory used to collect interface statistics.","Reloaded the sytem at the next maintenance period."
"C4K_SUPERVISOR","3","SUPOCTALPHYMDIOREADERR","Failed to perform read operation on Octal Serdes at address [dec] for the register at address [dec]","Unable to read the Octal Serdes on the supervisor engine.","If this continues to happen, contact your technical support representative to replace the supervisor engine."
"C4K_SUPERVISOR","4","EOBCPORTLOSTCOMMUNICATION","Resetting standby supervisor due to lost TX Communication.","EOBC MAC has stopped transmitting, therefore RESET the peer supervisor, to re-sync the HA state.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C4K_SUPERVISOR","4","INLINEVOLTAGEOUTOFRANGE","Output voltage of the on-board inline power convertor on this  board is  [char] and is outside the expected  range of  [char]","This message should only occur in systems using a Supervisor Engine II-Plus TS. The output voltage of the on-board inline power converter is outside its expected valid range. This condition can occur because of failed PoE components, one or more powered devices drawing more power than expected, or because of problems with the 12 V output of the system power supply.","Use the show power detail and show power inline module 1 commands to verify that the devices drawing PoE are using the expected amount of power, and disconnect them if they are drawing more than desired. If the power supply LEDs are not green, verify at the source that the system power input is correct. If the problem persists, contact your technical support representative. You will probably need to replace the supervisor engine."
"C4K_SUPERVISOR","4","OTHERSUPERVISORACTIVEDEBOUNCE","Other supervisor is still holding hardware lock","This condition is detected when the redundancy register incorrectly indicates that the other supervisor engine is holding a lock. This error is probably caused by hardware signal latency. Unless there is a real hardware failure, the switch automatically recovers from this state. If there is a persistent hardware failure, this message appears four times.","This is an informational message only; no action is required."
"C4K_SUPERVISOR","4","UNSUPPORTEDMODULE","Card in Slot([dec]) Failed to Boot","The module is either unsupported or faulty","If this module was purchased from Cisco, please contact Cisco TAC."
"C4K_SUPERVISOR","7","SEEPROMWRITEFAILED","Failed to write supervisor's serial eeprom","The software was unable to write to the supervisor engine serial EEPROM.","Remove and reinsert the module. If this message reappears, reboot the switch. If the switch is still unable to write to the EEPROM, contact your technical support representative."
"SWITCH_QOS_TB","5","TRUST_DEVICE_DETECTED","[char] detected on port [char]","Software detected that a device matching the trusted device boundary setting for the interface and changed the trust state for the interface to trusted.","This is an informational message only; no action is required."
"SWITCH_QOS_TB","5","TRUST_DEVICE_LOST","[char] no longer detected on port [char], port set to untrusted","The system lost contact with a trusted device and changed the trust state for the interface to untrusted.","This is an informational message only; no action is required."
"SW_DAI","4","ACL_DENY","[dec]Invalid ARPs (Req) on [chars], vlan [dec].","The switch received ARP packets that are considered invalid by ARP inspection. The packets are invalid, and their presence indicates that administratively denied packets are in the network. This log message generates when packets have been denied by ACLs either explicitly or implicitly (with static ACL configuration). The presence of these packets indicates a possible 'man-in-the-middle' attacks in the network.","To stop these messages from generating, find the source host of these packets and stop the host from sending them."
"SW_DAI","4","DHCP_SNOOPING_DENY","[dec] Invalid ARPs (Req) on [chars], vlan [chars].","The switch received ARP packets that are considered invalid by ARP inspection. The packets are invalid, and their presence may be an indication of 'man-in-the-middle' attacks that are attempted in the network. This message is logged when the IP address and MAC address binding for the sender on the received VLAN is not listed in the DHCP snooping database.","To stop these messages from generating, find the source host of these packets and stop the host from sending them."
"SW_DAI","4","INVALID_ARP","[dec] Invalid ARPs (Req) on [chars], vlan [chars].","The switch received ARP packets that are considered invalid by ARP inspection. The packets are invalid and do not pass one or more of the source MAC address, destination MAC address, or IP address validation checks. A packet was denied because the source MAC address, destination MAC address, or IP validation failed.","To stop these messages from generating, find the source host of these packets and stop the host from sending them."
"SW_DAI","4","PACKET_BURST_RATE_EXCEEDED","[dec] packets received in [dec] seconds on [char].","The switch received [dec] number of ARP packets in the specified burst interval. The interface was in the err disabled state and the switch received the packets at a rate higher than the configured packet rate for every second over the configured burst interval. The message is logged just before the interface entered the err disabled state and if the configured burst interval is more than one second.","This is an informational message only; no action is required."
"SW_DAI","4","PACKET_RATE_EXCEEDED","[dec] packets received in [dec] milliseconds on [char].","The switch received [dec] number of ARP packets in the specified duration on the given interface above the exceeded packet rate. This message is logged just before the interface entered the err disabled state and when the burst interval is set to one second.","This is an informational message only; no action is required."
"SW_DAI","4","SPECIAL_LOG_ENTRY","[dec] Invalid ARP packets [%CC]","The switch received [dec] number of ARP packets that the ARP inspection considers invalid. The packets are invalid, and their presence may be an indication of 'man-in-the-middle' attacks attempted on the network. This message displays when the rate of incoming packets exceed the DAI logging rate.","This is an informational message only; no action is required."
"SW_DAI","6","ACL_PERMIT","[dec] ARPs (Req) on [chars], vlan [chars].","The switch received ARP packets that have been permitted because of an ACL match.","This is an informational message only; no action is required."
"SW_DAI","6","ARP_PROBE_PERMIT","[dec] ARPs ([char]) on [char]","This message is logged when an ARP packet with a sender IP address of 0.0.0.0 has been permitted. These packets are used as ARP probes by various network devices. These messages are not logged by default, but only when arp-probe logging is enabled.","This is an informational message only; no action is required."
"SW_DAI","6","DHCP_SNOOPING_PERMIT","[dec] ARPs (Req) on [chars], vlan [chars]","The switch received ARP packets that have been permitted because the IP and MAC address for the sender match against the DHCP snooping database for the received VLAN.","This is an informational message only; no action is required."
"SW_VLAN","3","IIF_ID_ALLOC_FAILED","IIF_ID alloc failed for vlan [dec] due to memory allocation failure. Some features will not work.","TIIF-ID allocation failed because the system is low on memory. This can result in a failure to apply polices such as QoS and Security ACLs on this VLAN.","Reduce other system activities to ease memory demands. If feasible, add system memory."
"SW_VLAN","3","IIF_ID_REGISTRATION_FAILED","IIF_ID registration failed for vlan [dec] due to memory allocation failure. Some features will not work. VlAN has been shutdown.","IIF-ID registration failed because the system is low on memory. This can result in a failure to apply polices such as QoS and Security ACLs on this VLAN. If the VLAN exists, it is shutdown. If the VLAN doesn't exist, then it will be shutdown when it is created.","Reduce other system activities to ease memory demands. If feasible, add system memory."
"SW_VLAN","3","MALLOC_FAIL","Failed to allocate [dec] bytes","Memory allocation failed.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"SW_VLAN","3","VLAN_DAT_CACHE_SEQUENCE","Out of sequence vlan.dat sync message. Expected: [dec]; received: [dec].","The vlan.dat file is synchronized to the standby supervisor engine via one or more checkpoint messages from the active supervisor engine. The sequence number for each such set of checkpoint messages starts with 1. These messages are cached until the end-of-set indication is received. Here, the standby supervisor engine received a checkpoint message with a sequence number that does not match the expected sequence number.","Reset the standby supervisor engine using the redundancy reload peer command. If problems persist, contact a Cisco technical support representative."
"SW_VLAN","3","VLAN_DAT_CACHE_SIZE_EXCEED","Data exceeds allocated size. Offset: [dec]; data_size: [dec]; aloocated: [dec]","The vlan.dat file is synchronized to the standby supervisor engine via one or more checkpoint messages from the active supervisor engine. The sequence number for each such set of checkpoint messages starts with 1. These messages are cached until the end-of-set indication is received. Here, the standby supervisor engine received a checkpoint message with a size that does not fit the size of the cache specified in the checkpoint message with sequence number 1.","Reset the standby supervisor engine using the redundancy reload peer command. If problems persist, contact a Cisco technical support representative."
"SW_VLAN","3","VLAN_PM_NOTIFICATION_FAILURE","VLAN Manager synchronization failure with Port Manager over [char]","Due to a lack of ready pool space, the VLAN Manager dropped a notification from the Port Manager.","This is an informational message only; no action is required."
"SW_VLAN","3","VTP_PROTOCOL_ERROR","VTP protocol code internal error: [char]","The VTP protocol code encountered an unexpected error while processing a configuration request, packet, or timer expiration.","This is an informational message only; no action is required."
"SW_VLAN","4","BAD_PM_VLAN_COOKIE_RETURNED","VLAN manager unexpectedly received a bad PM VLAN cookie from the Port Manager","The VLAN Manager received an upcall from the Port Manager containing a VLAN cookie that translated to a bad VLAN number.","This is an informational message only; no action is required."
"SW_VLAN","4","BAD_STARTUP_VLAN_CONFIG_FILE","Failed to configure VLAN from startup-config. Fallback to use VLAN configuration file from non-volatile memory","The VLAN software failed to use the VLAN configuration from a startup-config file. The software will use the binary VLAN configuration file in nonvolatile memory.","This is an informational message only; no action is required."
"SW_VLAN","4","BAD_VLAN_CONFIGURATION_FILE","VLAN configuration file contained incorrect verification word: [hex]","The VLAN configuration file begins with an unrecognized value and might not be a valid VLAN configuration file. The file was rejected.","This is an informational message only; no action is required."
"SW_VLAN","4","BAD_VLAN_CONFIGURATION_FILE_VERSION","VLAN configuration file contained unknown file version: [dec]","When the VLAN Manager read the VLAN configuration file it contained an unrecognized file version number. This could indicate an attempt to regress to an older version of the VLAN Manager software.","This is an informational message only; no action is required."
"SW_VLAN","4","BAD_VLAN_DOMAIN_NAME_LENGTH","VLAN configuration file contained incorrect domain name length: %u","The VLAN configuration file read by the VLAN manager contained an invalid doman name length and the domain name was rejected.","Correct the VTP domain name and try again."
"SW_VLAN","4","BAD_VLAN_PASSWORD_LENGTH","VLAN configuration file contained incorrect VTP password length: %u","The VLAN configuration file read by the VLAN manager contained an invalid VTP password length and the password was rejected.","Correct the VTP password and try again."
"SW_VLAN","4","BAD_VLAN_TIMER_ACTIVE_VALUE","Encountered incorrect VLAN timer active value: [char]","Due to a software error, a VLAN timer was detected as being active when it should have been inactive or inactive when it should have been detected as being active.","This is an informational message only; no action is required."
"SW_VLAN","4","EXT_VLAN_INTERNAL_ERROR","Extended VLAN manager received an internal error [dec] from [char]: [char]","The VLAN Manager received an unexpected error code from the extended VLAN configuration software.","This is an informational message only; no action is required."
"SW_VLAN","4","EXT_VLAN_INVALID_DATABASE_DATA","Extended VLAN manager received bad data of type [char]: value [dec] from function [char]","The extended VLAN Manager received invalid data from an extended VLAN configuration database routine.","This is an informational message only; no action is required."
"SW_VLAN","4","IFS_FAILURE","VLAN manager encountered file operation error: call = [char] / file = [char]  / code = [dec] ([char]) / bytes transferred = [dec]","The VLAN Manager received an unexpected error return from a Cisco IOS file system call.","This is an informational message only; no action is required."
"SW_VLAN","4","NO_PM_COOKIE_RETURNED","VLAN manager unexpectedly received a null [char] type cookie from the Port Manager","The VLAN Manager queried the Port Manager for a reference cookie but received a NULL pointer instead.","This is an informational message only; no action is required."
"SW_VLAN","4","STARTUP_EXT_VLAN_CONFIG_FILE_FAILED","Failed to configure extended range VLAN from startup-config. Error [char]","The VLAN software failed to use extended VLAN configuration in the startup-config file. Configuration information for all extended-range VLANs will be lost when the system boots.","This is an informational message only; no action is required."
"SW_VLAN","4","VLANMGR_INVALID_DATABASE_DATA","VLAN MANAGER received bad data of type [char]: value [dec] from function [char]","Invalid data was received by the VLAN MANAGER from a VLAN configuration database routine as described.","Call Cisco technical support immediately."
"SW_VLAN","4","VLAN_CREATE_FAIL","Failed to create VLANs [char]: [char]","The VLANs specified in the error message could not be created. The VLAN manager called a VLAN database routine to create one or more VLANs, but the Port Manager could not complete the VLAN creation requests. A possible cause of this error is that the VLANs already exist in the Port Manager as internal VLANs.","Contact your technical support representative."
"SW_VLAN","4","VTP_DB_SIZE_CHECK_FAILED","The [char] VTP database of length [dec] cannot be supported by the system","The VTP database size is more than what the system can support.","Reduce the database size by decreasing the configuration parameters, for example, reduce the size of VLAN names."
"SW_VLAN","4","VTP_FLOOD_ERROR","Primary server request failed Primary server can only change once \ every [dec] seconds.","A VTP takeover packet was received within the takeover rate limit.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"SW_VLAN","4","VTP_INTERNAL_ERROR","VLAN manager received an internal error [dec] from vtp function [char]: [char]","The VLAN Manager received an unexpected error code from the VTP configuration software.","This is an informational message only; no action is required."
"SW_VLAN","4","VTP_INVALID_DATABASE_DATA","VLAN manager received bad data of type [char]: value [dec] from vtp database function [char]","The VLAN Manager received invalid data from a VTP configuration database routine.","This is an informational message only; no action is required."
"SW_VLAN","4","VTP_INVALID_EVENT_DATA","VLAN manager received bad data of type [char]: value [dec] while being called to handle a [char] event","The VLAN Manager received invalid data from the VTP configuration software.","This is an informational message only; no action is required."
"SW_VLAN","4","VTP_PRIMARY_SERVER_CHG","[mac-addr] has become the primary server for the [char] VTP feature","The primary server status has changed and the indicated device has become the primary server for the indicated VTP feature.","This is an informational message only; no action is required."
"SW_VLAN","4","VTP_SEM_BUSY","VTP semaphore is unavailable for function [char]. Semaphore locked by [char]","The VTP database is currently locked by another task and is not available. Retry the operation later.","Retry the operation later.If the problem persists, contact your technical support representative."
"SW_VLAN","4","VTP_USER_NOTIFICATION","VTP protocol user notification: [char]","The VTP protocol code encountered an unusual diagnostic condition.","This is an informational message only; no action is required."
"SW_VLAN","6","OLD_CONFIG_FILE_READ","Old version [dec] VLAN configuration file detected and read OK. Version [dec] files will be written in the future.","The VLAN software detected an old version of the VLAN configuration file format. The VLAN software was able to interpret the file with no problems, but it will create files using the new format in the future.","This is an informational message only; no action is required."
"SW_VLAN","6","VLAN_DAT_CACHE_EXISTS","Unexpected vlan.dat cache exists. Removing the cache and continuing the sync with new set.","An existing VLAN cache file was found while synchronizing supervisor engines. This message is informational only, the switch will continue to work properly even after encountering this situation.","If this message appears frequently, contact your technical support representative."
"SW_VLAN","6","VTP_DOMAIN_NAME_CHG","VTP domain name changed to [char].","The VTP domain name was changed through configuration to the name specified in the message. A management domain is the naming scope of a VLAN name. Each VLAN has a name that is unique within the management domain.","This is an informational message only; no action is required."
"SW_VLAN","6","VTP_MODE_CHANGE","VLAN manager changing device mode from [char] to [char].","Some switch devices must automatically change VTP device modes upon receipt of a VLAN configuration database containing more than a set number of VLANs, depending on the device. Such a spontaneous conversion occurred, what the previous mode was, and what the current mode is.","This is an informational message only; no action is required."
"C4K_SWITCHINGENGINEMAN","2","PACKETMEMORYERROR3","Persistent Errors in Packet Memory [dec]","There is a high rate of persistent errors in packet memory. This condition might indicate a persistent hardware problem.","If this message persists, use the show platform commands to show results, contact your technical support representative, and provide the representative with the gathered information."
"C4K_SWITCHINGENGINEMAN","2","PPELEAKDETECTED","Hardware buffer leak detected. System will be reset!","A packet buffer leak was detected, and the system will reset. This may be due to a transient hardware problem with the packet buffer related memories. This message may also erroneously appear if using jumbo packets or if sharing is configured and transmit queues have backed up.","This is an informational message only; no action is required. To supress the automatic reset action use the diagnostic monitor action conservative command."
"C4K_SWITCHINGENGINEMAN","3","BADASICINTERPOSER","[char] Possibly bad interposer","A high number of locations in packet memory are reporting errors. The IPP ASIC interposer may have gone bad.","Reboot the supervisor. If the problem persists, contact Cisco TAC."
"C4K_SWITCHINGENGINEMAN","3","BADDELIMITER","Recived CPU packet with bad delimiter","The software expected a delimiter pattern of successive packets but received some other pattern. This condition might be due to a loss of synchronization between the hardware and the software.","This is an informational message only; no action is required."
"C4K_SWITCHINGENGINEMAN","3","BADLENGTH","Recived CPU packet with bad length","The switch received a CPU packet that was either too long or too short.","This is an informational message only; no action is required."
"C4K_SWITCHINGENGINEMAN","3","BFDPARITYERROR","Parity error detected in BFD hardware offload: [hex].","The BFD hardware offload logic has detected a parity error in its internal memory. The hardware fault is usually transient but until it is correct, all offloaded BFD sessions will fail.","Reset the supervisor to reinitialize the BFD sessions. If the error recurs, contact Cisco TAC."
"C4K_SWITCHINGENGINEMAN","3","CIMPKTBUFPARITYERROR","Parity error in Cim Packet Buffer at offset  [dec]","There is a parity error in queue memory. This condition might indicate a transient hardware problem or a more permanent problem. After 128 packet memory and queue memory errors, the switch reboots.","If you see this message often, reboot the switch."
"C4K_SWITCHINGENGINEMAN","3","DHMPARITYERROR","\'Parity error in DBL Hash Memory, addr=[hex], total errors=%u\'","There is a parity error in the DM module. This could indicate a transient hardware problem, or a more permanent problem.","If you see this message too often, reboot the switch."
"C4K_SWITCHINGENGINEMAN","3","ERRORINTERRUPT","Error condition detected by hardware. Interrupt Status [hex]","The hardware detected an error condition and raised an interrupt to the software. The interrupt status value indicates the type of error.","This is an informational message only; no action is required."
"C4K_SWITCHINGENGINEMAN","3","FATALERRORINTERRUPTSEEN","[char]","A fatal interrupt in the ASIC switching complex was encountered. Information useful for troubleshooting the cause of this issue will be logged in the contents of this message.","The switch will reboot without user intervention. If the problem persists, contact your technical support representative."
"C4K_SWITCHINGENGINEMAN","3","FREELISTMEMORYPARITYERROR","Parity error in freelist memory, flm addr=[hex], reg bits=[hex], total errors=%u","An error in freelist memory was detected. If this message persists, it may indicate a transient hardware problem, or a more permanent problem leading to memory corruption. After 128 such transmit count errors, the switch will reload.","If the switch is reloading too often due to this condition, you may need to check for environmental conditions such as RFI or other interference. It may also be necessary to replace the supervisor engine."
"C4K_SWITCHINGENGINEMAN","3","IPPCIMTOOMANYERRORS","[char]","The system received too many parity interrupts in a short time. This could indicate a transient hardware problem, or a more permanent problem.","Reboot the switch."
"C4K_SWITCHINGENGINEMAN","3","IPPHPMTOOMANYPARITYERRORS","[char]","An excessive number of errors in the Integrated Packet Processor's CPU Interface Module were detected in a short time. Software will automatically reboot the supervisor engine. This could be a permanent hardware problem.","If the problem persists after the software reboots the supervisor, contact Cisco TAC."
"C4K_SWITCHINGENGINEMAN","3","IPPLLCINTERRUPT","[char]","An error in the Integrated Packet Processor's Link List Control Module was detected. Contents of the log register are printed out. This is considered to be a fatal error. Software will automatically reboot the supervisor.","Contact Cisco TAC support."
"C4K_SWITCHINGENGINEMAN","3","IPPLLCTOOMANYPARITYERRORS","[char]","An excessive number of errors in the Integrated Packet Processor's Link List Control Module were detected in a short time. Software will automatically reboot the supervisor. This could be a permanent hardware problem.","If the problem persists after the software reboots the supervisor, contact Cisco TAC support."
"C4K_SWITCHINGENGINEMAN","3","IPPPFMTOOMANYPARITYERRORS","[char]","An excessive number of errors in the Integrated Packet Processor's PLD FIFO Module were detected in a short time. Software will automatically reboot the supervisor engine. This could be a permanent hardware problem.","If the problem persists after the software reboots the supervisor engine, contact Cisco TAC."
"C4K_SWITCHINGENGINEMAN","3","IPPPRMTOOMANYPARITYERRORS","[char]","An excessive number of errors in the Integrated Packet Processor's Packet Rewrite Module were detected in a short time. Software will automatically reboot the supervisor engine. This could be a permanent hardware problem.","If the problem persists after the software reboots the supervisor engine, contact Cisco TAC."
"C4K_SWITCHINGENGINEMAN","3","IPPPSMTOOMANYPARITYERRORS","[char]","An excessive number of errors in the Integrated Packet Processor's Port Statistics Module were detected in a short time. Software will automatically reboot the supervisor engine. This could be a permanent hardware problem.","If the problem persists after the software reboots the supervisor engine, contact Cisco TAC."
"C4K_SWITCHINGENGINEMAN","3","IPPTMMTOOMANYPARITYERRORS","[char]","An excessive number of errors in the Integrated Packet Processor's Transmit Management Module were detected in a short time. Software will automatically reboot the supervisor engine. This could be a permanent hardware problem.","If the problem persists after the software reboots the supervisor engine, contact Cisco TAC."
"C4K_SWITCHINGENGINEMAN","3","IPPTOOMANYPACKETMEMORYPARITYERRORS","[char]","An excessive number of parity errors in packet memory were detected in a short time. Software will automatically reboot the supervisor engine. This could be a permanent hardware problem.","If the problem persists after the software reboots the supervisor engine, contact Cisco TAC."
"C4K_SWITCHINGENGINEMAN","3","JUMBOPACKET","Recieved a Jumbo CPU packet","The switch received a packet that is larger than 2032 bytes. This large packet is called a jumbo packet.","This is an informational message only; no action is required."
"C4K_SWITCHINGENGINEMAN","3","NOMEMORYFORRXRING","Not enough memory to initialize CPU packets","The system ran out of memory while trying to initialize the CPU packet driver.","This is an informational message only; no action is required."
"C4K_SWITCHINGENGINEMAN","3","PACKETENGINERESTARTED","An error happened in the Packet Engine logic","The packet engine logic became unstable for unknown reasons.","Reboot the switch."
"C4K_SWITCHINGENGINEMAN","3","PACKETMEMORYERROR2","Multiple Errors in Packet Memory [dec]","Multiple errors in packet memory were detected. If this message persists, it might indicate a hardware problem.","If this message persists, use the show platform commands to show results, contact your technical support representative, and provide the representative with the gathered information."
"C4K_SWITCHINGENGINEMAN","3","PACKETMEMORYPARITYERROR","Parity error in Packet Memory at address  [dec] , total errors= [dec]","There is a parity error in packet memory. This condition might indicate a transient hardware problem or a more permanent problem. After 128 packet memory and queue memory errors, the switch reloads automatically.","If this message reoccurs, reboot the switch. If the message appears every time the switch boots, run the show diagnostics online command and send the results to your technical support representative."
"C4K_SWITCHINGENGINEMAN","3","PACKETMEMORYTESTFAILURE","Packet Memory buffer test failed!!!  Insufficient packet  buffers are available to continue booting.","The packet memory diagnostic bootup test detected too many failures for switch operation to continue.","Refer to the Release Note attachment in the DDTS for CSCdz57255."
"C4K_SWITCHINGENGINEMAN","3","PACKETMEMORYTESTPARTIALFAILURE","Packet Memory buffer test detected errors with  [dec] % of the packet buffers.  Switch operation will continue, with  potentially reduced performance. Use 'show diagnostic result  module all detail' command to see test results.","The packet memory diagnostic bootup test detected failures, but there are still a sufficient number of working buffers to enable switch operation.","Use the show diagnostic result module all detail command to see the test results. Refer to the Release Note attachment in the DDTS for CSCdz57255."
"C4K_SWITCHINGENGINEMAN","3","PPECELLDUPDETECTED","Free cell duplicate(s) detected [hex]. System will be reset!","The system detected free cell duplication, and will be reset.","This is an informational message only; no action is required."
"C4K_SWITCHINGENGINEMAN","3","PPECELLDUPREBOOT","Repeated cell duplicates. Detections [dec]. System will be reset!","The free list is being monitored and several free cell duplications were detected. This may be due to a transient hardware problem with the packet buffer related memories. The system will reset.","This is an informational message only; no action is required."
"C4K_SWITCHINGENGINEMAN","3","QUEUEMEMORYPARITYERROR","Parity error in Queue Memory, addr=[hex], total errors=%u","There is a parity error in the queue memory. This condition might indicate a transient hardware problem or a more permanent problem. After 128 packet memory and queue memory errors, the switch reloads.","If this message reoccurs, reboot the switch."
"C4K_SWITCHINGENGINEMAN","3","RDPMEOPMISMATCHERROR","RdPMEopMismatch error , subcell addr=[hex], reg bits=[hex], total errors=%u","An error in a packet's cell was detected. This could indicate a problem with the packet cell linked list or subcell count memory. If this message persists, it may indicate a transient hardware problem, or a more permanent problem. After 1024 such End-Of-Packet mismatch errors, the switch will reload.","After 1024 such End-Of-Packet mismatch errors, the switch will reload. If the switch is reloading too often due to this condition, you may need to check for environmental conditions such as RFI or other interference. It may also be necessary to replace the supervisor engine."
"C4K_SWITCHINGENGINEMAN","3","RXDELIMITERERROR","Invalid packet delimiter received. Expected [hex] Received [hex]","Successive packets that are sent by the hardware to the CPU have a specific delimiter pattern. The software expected a delimiter pattern but received some other pattern. This condition might be caused by synchronization loss between the hardware and the software.","Reboot the switch."
"C4K_SWITCHINGENGINEMAN","3","SUBCELLCNTMEMORYPARITYERROR","Parity error in subcell count memory, addr=[hex], reg bits=[hex], total errors=%u","An error in subcell count memory was detected. If this message persists, it may indicate a transient hardware problem, or a more permanent problem. After 128 such subcell count errors, the switch will reload.","If the switch is reloading too often due to this condition, you may need to check for environmental conditions such as RFI or other interference. It may also be necessary to replace the supervisor engine."
"C4K_SWITCHINGENGINEMAN","3","TXCNTMEMORYPARITYERROR","Parity error in transmit count memory, addr=[hex], reg bits=[hex], total errors=%u","An error in transmit count memory was detected.If this message persists, it may indicate a transient hardware problem, or a more permanent problem. After 128 such transmit count errors, the switch will reload.","If the switch is reloading too often due to this condition, you may need to check for environmental conditions such as RFI or other interference. It may also be necessary to replace the supervisor engine."
"C4K_SWITCHINGENGINEMAN","3","VFECITOOMANYERRORS","[char]","An excessive number of errors in the Very-fast Forwarding Engine's CPU Interface Module were detected in a short time. Software will automatically reboot the supervisor engine. This could be a permanent hardware problem.","If the problem persists after the software reboots the supervisor engine, contact Cisco TAC."
"C4K_SWITCHINGENGINEMAN","3","VFEFLTOOMANYPARITYERRORS","[char]","An excessive number of errors in the Very-fast Forwarding Engine's Forwarding Lookup Module were detected in a short time. Software will automatically reboot the supervisor engine. This could be a permanent hardware problem.","If the problem persists after the software reboots the supervisor engine, contact Cisco TAC."
"C4K_SWITCHINGENGINEMAN","3","VFEICTOOMANYPARITYERRORS","[char]","An excessive number of errors in the Very-fast Forwarding Engine's Input Classification Module were detected in a short time. Software will automatically reboot the supervisor engine. This could be a permanent hardware problem.","If the problem persists after the software reboots the supervisor engine, contact Cisco TAC."
"C4K_SWITCHINGENGINEMAN","3","VFEIMTOOMANYPARITYERRORS","[char]","An excessive number of errors in the Very-fast Forwarding Engine's Input Mapping Module were detected in a short time. Software will automatically reboot the supervisor engine. This could be a permanent hardware problem.","If the problem persists after the software reboots the supervisor engine, contact Cisco TAC."
"C4K_SWITCHINGENGINEMAN","3","VFEL2TOOMANYPARITYERRORS","[char]","An excessive number of errors in the Very-fast Forwarding Engine's L2 Module were detected in a short time. Software will automatically reboot the supervisor engine. This could be a permanent hardware problem.","If the problem persists after the software reboots the supervisor engine, contact Cisco TAC."
"C4K_SWITCHINGENGINEMAN","3","VFEOCTOOMANYPARITYERRORS","[char]","An excessive number of errors in the Very-fast Forwarding Engine's Output Classification Module were detected in a short time. Software will automatically reboot the supervisor engine. This could be a permanent hardware problem.","If the problem persists after the software reboots the supervisor engine, contact Cisco TAC."
"C4K_SWITCHINGENGINEMAN","3","VFEOPTOOMANYPARITYERRORS","[char]","An excessive number of errors in the Very-fast Forwarding Engine's Output Processing Module were detected in a short time. Software will automatically reboot the supervisor engine. This could be a permanent hardware problem.","If the problem persists after the software reboots the supervisor engine, contact Cisco TAC."
"C4K_SWITCHINGENGINEMAN","3","VFERMTOOMANYPARITYERRORS","[char]","An excessive number of errors in the Very-fast Forwarding Engine's Replication Module were detected in a short time. Software will automatically reboot the supervisor engine. This could be a permanent hardware problem.","If the problem persists after the software reboots the supervisor engine, contact Cisco TAC."
"C4K_SWITCHINGENGINEMAN","3","VFERPTOOMANYPARITYERRORS","[char]","An excessive number of errors in the Very-fast Forwarding Engine's Replication Module were detected in a short time. Software will automatically reboot the supervisor engine. This could be a permanent hardware problem.","If the problem persists after the software reboots the supervisor engine, contact Cisco TAC."
"C4K_SWITCHINGENGINEMAN","3","VFESUTOOMANYPARITYERRORS","[char]","An excessive number of errors in the Very-fast Forwarding Engine's Statistics Update Module were detected in a short time. Software will automatically reboot the supervisor engine. This could be a permanent hardware problem.","If the problem persists after the software reboots the supervisor engine, contact Cisco TAC."
"C4K_SWITCHINGENGINEMAN","3","VFETQINTERRUPTDROPQUEOVERRUNERR","[char]","The drop queue in the Very-fast Forwarding Engine's Transmit Queue Module had an overrun. This could be due to excessive drop traffic. This can lead to a packet buffer leak.","Reboot the supervisor."
"C4K_SWITCHINGENGINEMAN","3","VFETQINTERRUPTSIZEINCELLSUNDERRUNERR","[char]","This error suggests that a false packet dequeue may have happened in a transmit queue on the Very-fast Forwarding Engine. This can lead to corruption of the free list.","If the problem occurs more than once, reboot the supervisor."
"C4K_SWITCHINGENGINEMAN","3","VFETQINTERRUPTSIZEINPKTSUNDERRUNERR","[char]","This error suggests that a false packet dequeue may have happened in a transmit queue on the Very-fast Forwarding Engine. This can lead to corruption of the free list.","If the problem occurs more than once, reboot the supervisor."
"C4K_SWITCHINGENGINEMAN","3","VFETQTOOMANYPARITYERRORS","[char]","An excessive number of errors in the Very-fast Forwarding Engine's Transmit Queue Module were detected in a short time.Software will automatically reboot the supervisor engine. This could be a permanent hardware problem.","If the problem persists after the software reboots the supervisor engine, contact Cisco TAC."
"C4K_SWITCHINGENGINEMAN","3","XPPEDCTOOMANYERRORS","[char]","An excessive number of errors in the Integrated Packet Processor's EDC module were detected in a short time. Contents of the log register are printed out. This could be a transient hardware problem or it could be a permanent hardware issue caused by the ASIC interposer suddenly going bad.","Reboot the switch and run POST diagnostics. If POST diagnostics reports any failures, contact Cisco TAC support."
"C4K_SWITCHINGENGINEMAN","4","IPPCIMINTERRUPT","[char]","An error in the Integrated Packet Processor's CPU Interface Module was detected. Contents of the log register are printed out. This is probably a transient hardware issue affecting a single packet in transit through the switch.","This is an informational message only; no action is required."
"C4K_SWITCHINGENGINEMAN","4","IPPHPMINTERRUPT","[char]","An error in the Integrated Packet Processor's Header Parser Module was detected. Contents of the log register are printed out. This could be a transient hardware issue affecting a single packet in transit through the switch, a parity error in a table that software is capable of correcting, or a fatal error.","If this message is a fatal error, contact Cisco TAC. Otherwise, no further actions are necessary."
"C4K_SWITCHINGENGINEMAN","4","IPPINTERRUPT","[char]","A parity error in the packet memory was detected. Contents of the log register are printed out. This is probably a transient hardware issue affecting a single packet in transit through the switch.","This is an informational message only; no action is required."
"C4K_SWITCHINGENGINEMAN","4","IPPPFMINTERRUPT","[char]","A parity error in the Integrated Packet Processor's PLD FIFO Module was detected. Contents of the log register are printed out. This is probably a transient hardware issue affecting a single packet in transit through the switch","This is an informational message only; no action is required."
"C4K_SWITCHINGENGINEMAN","4","IPPPRMINTERRUPT","[char]","A parity error in the Integrated Packet Processors's Packet Rewrite Module was detected. Contents of the log register are printed out. This error affects a table entry that software is capable of correcting.","This is an informational message only; no action is required."
"C4K_SWITCHINGENGINEMAN","4","IPPPRMINTERRUPTAUTOVALIDATION","[char]","The Integrated Packet Processor detected an error in auto validation for IPV6 tunneling. Contents of the log register are printed out. This could be a transient hardware problem or it could be a permanent hardware issue caused by the ASIC interposer suddenly going bad.","Reboot the switch and run POST diagnostics. If POST diagnostics reports any failures, contact Cisco TAC support."
"C4K_SWITCHINGENGINEMAN","4","IPPPRMINTERRUPTINNERCRC","[char]","The Integrated Packet Processor detected a CRC error when reading a tunneled packet (ie. an Ethernet header encapsulated in another) stored in packet memory. Contents of the log register are printed out. This could be a transient hardware problem or it could be a permanent hardware issue caused by the ASIC interposer suddenly going bad.","Reboot the switch and run POST diagnostics. If POST diagnostics reports any failures, contact Cisco TAC support."
"C4K_SWITCHINGENGINEMAN","4","IPPPRMINTERRUPTIPV6TO4VALIDATION","[char]","The Integrated Packet Processor detected an error in Ipv6To4 validation. Contents of the log register are printed out. This could be a transient hardware problem or it could be a permanent hardware issue caused by the ASIC interposer suddenly going bad.","Reboot the switch and run POST diagnostics. If POST diagnostics reports any failures, contact Cisco TAC support."
"C4K_SWITCHINGENGINEMAN","4","IPPPRMINTERRUPTISATAPVALIDATION","[char]","The Integrated Packet Processor detected an error in isatap tunneling validation. Contents of the log register are printed out. This could be a transient hardware problem or it could be a permanent hardware issue caused by the ASIC interposer suddenly going bad.","Reboot the switch and run POST diagnostics. If POST diagnostics reports any failures, contact Cisco TAC support"
"C4K_SWITCHINGENGINEMAN","4","IPPPRMINTERRUPTOUTERCRC","[char]","The Integrated Packet Processor detected a CRC error when reading a packet stored in packet memory. Contents of the log register are printed out. This could be a transient hardware problem or it could be a permanent hardware issue caused by the ASIC interposer suddenly going bad.","Reboot the switch and run POST diagnostics. If POST diagnostics reports any failures, contact Cisco TAC support."
"C4K_SWITCHINGENGINEMAN","4","IPPPRMINTERRUPTPKTLENGTH","[char]","The Integrated Packet Processor detected a packet length table parity error. Contents of the log register are printed out. This could be a transient hardware problem or it could be a permanent hardware issue caused by the ASIC interposer suddenly going bad.","Reboot the switch and run POST diagnostics. If POST diagnostics reports any failures, contact Cisco TAC support."
"C4K_SWITCHINGENGINEMAN","4","IPPPRMINTERRUPTPKTPARITY","[char]","The Integrated Packet Processor detected a CRC error when reading a packet stored in packet memory. Contents of the log register are printed out. This could be a transient hardware problem or it could be a permanent hardware issue caused by the ASIC interposer suddenly going bad.","Reboot the switch and run POST diagnostics. If POST diagnostics reports any failures, contact Cisco TAC support."
"C4K_SWITCHINGENGINEMAN","4","IPPPRMINTERRUPTRWFORMAT","[char]","The Integrated Packet Processor detected a rewrite Format table parity error. Contents of the log register are printed out. This could be a transient hardware problem or it could be a permanent hardware issue caused by the ASIC interposer suddenly going bad.","Reboot the switch and run POST diagnostics. If POST diagnostics reports any failures, contact Cisco TAC support."
"C4K_SWITCHINGENGINEMAN","4","IPPPRMINTERRUPTTTLEXCEPTION","[char]","The Integrated Packet Processor detected a TTL excetion error. Contents of the log register are printed out. This could be a transient hardware problem or it could be a permanent hardware issue caused by the ASIC interposer suddenly going bad.","Reboot the switch and run POST diagnostics. If POST diagnostics reports any failures, contact Cisco TAC support."
"C4K_SWITCHINGENGINEMAN","4","IPPPRMINTERRUPTVALIDATION","[char]","The Integrated Packet Processor detected an error in IPV6 IPV6 tunneling validation. Contents of the log register are printed out. This could be a transient hardware problem or it could be a permanent hardware issue caused by the ASIC interposer suddenly going bad.","Reboot the switch and run POST diagnostics. If POST diagnostics reports any failures, contact Cisco TAC support."
"C4K_SWITCHINGENGINEMAN","4","IPPPSMINTERRUPT","[char]","A parity error in the Integrated Packet Processors's Port Statistics Module was detected. Contents of the log register are printed out. This is a parity error in one of the port statistics counters.","This is an informational message only; no action is required."
"C4K_SWITCHINGENGINEMAN","4","IPPTMMINTERRUPT","[char]","A parity error in the Integrated Packet Processor's Transmit Management Module was detected. Contents of the log register are printed out. This could be a transient hardware issue affecting a single packet in transit through the switch or a fatal error.","If this message is a fatal error, contact Cisco TAC. Otherwise, no further actions are necessary."
"C4K_SWITCHINGENGINEMAN","4","IPPTMMINTERRUPTREFCNTMEMERR","[char]","An exception case was encountered when the Integrated Packet Processor accessed Reference Count Memory. Contents of the log register are printed out. This is most likely caused by misprogramming the Very-fast Forwarding Engine's Replication Expansion Table or Transmit Queue Management Module. It can also be caused due to corruption of the free list. Hardware contains the problem and limits it.","This is an informative message; no further actions are necessary."
"C4K_SWITCHINGENGINEMAN","4","PACKETMEMORYERROR","Error in Packet Memory [dec]","An error in packet memory was detected. If this message persists, it might indicate a hardware problem.","If this message persists, use the show diagnostics online command, contact your technical support representative, and provide the representative with the gathered information."
"C4K_SWITCHINGENGINEMAN","4","SYSTEMNOTRESET","System has already been reset  [dec] times due to Packet Memory errors. System will  not be reset anymore","The software detected a large number of errors in the packet memory and reset the switch. This condition indicates a hardware problem. However, the system only reset [dec] times by software to prevent an auto-boot followed by a reset loop.","Replace the switch. If you do not replace the switch, errors may persist and the system will reset again."
"C4K_SWITCHINGENGINEMAN","4","TCAMINTERRUPT","[char]","A parity error in a TCAM entry was detected. Contents of the log register are printed out Software will automatically perform error recovery on the defective TCAM entry.","This is an informational message only; no action is required."
"C4K_SWITCHINGENGINEMAN","4","VFECIINTERRUPT","[char]","An error in the Very-fast Forwarding Engine's CPU Interface Module was detected. Contents of the log register are printed out. This is probably a transient hardware issue affecting a single packet in transit through the switch.","This is an informational message only; no action is required."
"C4K_SWITCHINGENGINEMAN","4","VFEFLINTERRUPT","[char]","A parity error in the Very-fast Forwarding Engine's Forwarding Lookup Module was detected. Contents of the log register are printed out. This could be a transient hardware issue affecting a single packet in transit through the switch or a parity error in a table entry that software is capable of correcting.","This is an informational message only; no action is required."
"C4K_SWITCHINGENGINEMAN","4","VFEFLINTERRUPTFLCERR","[char]","An error in the Very-fast Forwarding Engine's Forwarding Lookup CAM reply data was detected. Contents of the log register are printed out.","This is an informatve message; no further actions are necessary."
"C4K_SWITCHINGENGINEMAN","4","VFEICINTERRUPT","[char]","An error in the Very-fast Forwarding Engine's Input Classification Module was detected. Contents of the log register are printed out. This could be a parity error in a table that software is capable of correcting or a fatal error.","If this message is a fatal error, contact Cisco TAC. Otherwise, no further actions are necessary."
"C4K_SWITCHINGENGINEMAN","4","VFEICINTERRUPTICCERR","[char]","An error in the Very-fast Forwarding Engine's Input Classfication CAM reply data was detected. Contents of the log register are printed out.","This is an informatve message; no further actions are necessary."
"C4K_SWITCHINGENGINEMAN","4","VFEIMINTERRUPT","[char]","An error in the Very-fast Forwarding Engine's Input Mapping Module was detected. Contents of the log register are printed out. This could be a transient hardware issue affecting a single packet in transit through the switch, a parity error in a table that software is capable of correcting, or a fatal error.","If this message is a fatal error, contact Cisco TAC. Otherwise, no further actions are necessary."
"C4K_SWITCHINGENGINEMAN","4","VFEL2INTERRUPT","[char]","An error in the Very-fast Forwarding Engine's L2 Module was detected. Contents of the log register are printed out. This could be a parity error in a table that software is capable of correcting or a fatal error.","If this message is a fatal error, contact Cisco TAC. Otherwise, no further actions are necessary."
"C4K_SWITCHINGENGINEMAN","4","VFEOCINTERRUPT","[char]","An error in the Very-fast Forwarding Engine's Output Classification Module was detected. Contents of the log register are printed out. This could be a parity error in a table that software is capable of correcting or a fatal error.","If this message is a fatal error, contact Cisco TAC. Otherwise, no further actions are necessary."
"C4K_SWITCHINGENGINEMAN","4","VFEOCINTERRUPTOCCERR","[char]","An error in the Very-fast Forwarding Engine's Output Classfication CAM reply data was detected. Contents of the log register are printed out.","This is an informatve message; no further actions are necessary"
"C4K_SWITCHINGENGINEMAN","4","VFEOPINTERRUPT","[char]","An error in the Very-fast Forwarding Engine's Output Processing Module was detected. Contents of the log register are printed out. This could be a transient hardware issue affecting a single packet in transit through the switch, a parity error in a table that software is capable of correcting, or a fatal error.","If this message is a fatal error, contact Cisco TAC. Otherwise, no further actions are necessary."
"C4K_SWITCHINGENGINEMAN","4","VFERMINTERRUPT","[char]","An error in the Very-fast Forwarding Engine's Replication Module was detected. Contents of the log register are printed out. This could be a transient hardware issue affecting a single packet in transit through the switch, a parity error in a table that software is capable of correcting, or a fatal error.","If this message is a fatal error, contact Cisco TAC. Otherwise, no further actions are necessary."
"C4K_SWITCHINGENGINEMAN","4","VFERMINTERRUPTINDIRERR","[char]","Software attempted to write an invalid index in the Replica Expansion Table memory. Contents of log register are printed out.","Contact Cisco TAC support."
"C4K_SWITCHINGENGINEMAN","4","VFERMINTERRUPTLINKCNTERR","[char]","Multicast expansion exceeds the allowed number of copies. This can lead to corruption of the free list.","Check for multicast traffic and see if there really is a high number of multicast receivers for a multicast group. If not, contact Cisco TAC support."
"C4K_SWITCHINGENGINEMAN","4","VFERPINTERRUPT","[char]","An error in the Very-fast Forwarding Engine's Rate Policer was detected. Contents of the log register are printed out. This could be a parity error in a table that software is capable of correcting or a fatal error.","If this message is a fatal error, contact Cisco TAC. Otherwise, no further actions are necessary."
"C4K_SWITCHINGENGINEMAN","4","VFESUINTERRUPT","[char]","A parity error in the Very-fast Forwarding Engines's Statistics Update Module was detected. Contents of the log register are printed out. This is a parity error in one of the statistics counters.","This is an informational message only; no action is required."
"C4K_SWITCHINGENGINEMAN","4","VFETQINTERRUPT","[char]","An error in the Very-fast Forwarding Engine's Transmit Queue Module was detected. Contents of the log register are printed out. This could be a transient hardware issue affecting a single packet in transit through the switch, a parity error in a table that software is capable of correcting, or a fatal error.","If this message is a fatal error, contact Cisco TAC. Otherwise, no further actions are necessary."
"C4K_SWITCHINGENGINEMAN","4","XPPEDCINTERRUPTDIAGTRIGGEROCCURRED","[char]","The Integrated Packet Processor detected a EDC DiagTrigger error. Contents of the log register are printed out. This could be a transient hardware problem or it could be a permanent hardware issue caused by the ASIC interposer suddenly going bad.","Reboot the switch and run POST diagnostics. If POST diagnostics reports any failures, contact Cisco TAC support."
"C4K_SWITCHINGENGINEMAN","4","XPPEDCINTERRUPTHPMERR","[char]","The Integrated Packet Processor detected a EDC HPM error. Contents of the log register are printed out. This could be a transient hardware problem or it could be a permanent hardware issue caused by the ASIC interposer suddenly going bad.","Reboot the switch and run POST diagnostics. If POST diagnostics reports any failures, contact Cisco TAC support."
"C4K_SWITCHINGENGINEMAN","4","XPPEDCINTERRUPTLLCERR","[char]","The Integrated Packet Processor detected a EDC LLC error. Contents of the log register are printed out. This could be a transient hardware problem or it could be a permanent hardware issue caused by the ASIC interposer suddenly going bad.","Reboot the switch and run POST diagnostics. If POST diagnostics reports any failures, contact Cisco TAC support."
"C4K_SWITCHINGENGINEMAN","4","XPPEDCINTERRUPTPREFETCHFIFOERR","[char]","The Integrated Packet Processor detected a EDC PrefetchFifo error. Contents of the log register are printed out. This could be a transient hardware problem or it could be a permanent hardware issue caused by the ASIC interposer suddenly going bad.","Reboot the switch and run POST diagnostics. If POST diagnostics reports any failures, contact Cisco TAC support."
"C4K_SWITCHINGENGINEMAN","4","XPPEDCINTERRUPTPRMERR","[char]","The Integrated Packet Processor detected a EDC PRM error. Contents of the log register are printed out. This could be a transient hardware problem or it could be a permanent hardware issue caused by the ASIC interposer suddenly going bad.","Reboot the switch and run POST diagnostics. If POST diagnostics reports any failures, contact Cisco TAC support."
"C4K_SWITCHINGENGINEMAN","4","XPPEDCINTERRUPTTMMERR","[char]","The Integrated Packet Processor detected a EDC TMM error. Contents of the log register are printed out. This could be a transient hardware problem or it could be a permanent hardware issue caused by the ASIC interposer suddenly going bad.","Reboot the switch and run POST diagnostics. If POST diagnostics reports any failures, contact Cisco TAC support."
"C4K_SWITCHINGENGINEMAN","6","PENDINGVFECIINTR","Pending interrupts in VFE CPU interface: [dec]","There is a problem with the switching ASIC.","Contact Cisco Technical Support to replace the Supervisor module."
"C4K_SWITCHINGENGINEMAN","7","PACKETMEMORYINIT","Mismatched Reads:  [dec] PM parity error:  [object-info]","Errors occurred in writing and reading Packet Memory during initialization.","This is an informational message only; no action is required."
"C4K_SWITCHINGENGINEMAN","7","PPELEAKMONITOR","Current Freelist count %u. Fell below threshold %u times consecutively","The PPE freelist count is being monitored. Packet buffer leak detection is on and the freelist count is being monitored. This message displays the current count and number of times the count reached the threshold. If the freelist count stays below the threshold for more than one minute, the system will be reset.This message may also erroneously appear if using jumbo packets or if sharing is configured and transmit queues have backed up.","This is an informational message only; no action is required. To suppress the automatic reset action use the diagnostic monitor action conservative command."
"C4K_SWITCHMANAGER","3","DUPLICATESWPHYPORT","Internal Event: Tried to create new sw PimPhyport [char], but it already exists","This message is a debug message that is used by developers only and should not occur during operation.","This is an informational message only; no action is required."
"C4K_SWITCHMANAGER","3","DUPLICATESWPORT","Internal Event: Tried to create new sw PimPort [char], but it already exists","This message is a debug message that is used by developers only and should not occur during operation.","This is an informational message only; no action is required."
"C4K_SWITCHMANAGER","3","INLINEPOWEROVERDRAWN","Inline powered device connected on port [char] exceeded its [char] threshold.Recommended Action    This message might be caused by a faulty powered device drawing more power than is allocated.Recommended Action    Verify that the powered device on the port is functioning properly and only drawing the configured power using the show power module command.Error Message    C4K_SWITCHMANAGER-3-SSOACTIVEPORTACKTIMEOUT: Internal Event: timed out after [dec] iterations waiting for Standby to acknowledge port status change for [char]","There is probably a software failure creating a communication problem between the active supervisor engine and the standby supervisor engine. SSO Redundancy mode cannot operate reliably when this condition occurs.","Contact your technical support representative."
"C4K_SWITCHMANAGER","3","SSOHARDWAREACKTIMEOUT","Internal Event: timed out after [dec] iterations waiting for the [char] hardware to be programmed","The active supervisor engine is taking more time than usual to program the hardware. This should not affect normal behavior or SSO functionality. In the worst case you may see link flaps when the supervisor engines switch over.","This is an informational message only; no action is required. If the problem persists, contact your technical support representative."
"C4K_SWITCHMANAGER","4","CANTPOWEROFF","Internal Error: PimEthAutoNegotiator - Can't power off port [char]","This is an internal software error in an inline-power state machine.","This is an informational message only; no action is required."
"C4K_SWITCHMANAGER","4","CANTPOWERON","Internal Error: PimEthAutoNegotiator - Can't power on port [char]","This is an internal software error in an inline-power state machine.","This is an informational message only; no action is required."
"C4K_SWITCHMANAGER","4","HARDWAREERROR","Power management hardware for port [char] bad.","The switch cannot change the inline-power state for this port.","This is an informational message only; no action is required."
"C4K_SWITCHMANAGER","4","S2WERROR","Power control to port [char] bad. Possibly power is turned on.","This is a communication error in PoE power management.","This is an informational message only; no action is required."
"C4K_SWITCHMANAGER","4","S2WERRORREPORT","PimEthAutoNeg: S2w Read/Write Error for port [char].","A read/write error occurred on the specified port.","Refer to the release notes to verify whether you can see all the symptoms described for CSCef87815. If you do not and do not see any adverse effect on the functionality of the PoE linecards (WS-X4248-RJ45V, WS-X4248-RJ21V, WS-X4548-RJ45V, WS-X4224-RJ45V or WS-X4524-RJ45V), then treat this message an informational message only and no action is required."
"C4K_SWITCHMANAGER","4","SSOEANWARNPORTRESET","The state of the port [char] is unknown after switchover, resetting its link.","A new switching module was inserted, and the active supervisor engine crashed unexpectedly before it could communicate the state of ports on the new module to the standby supervisor engine. The standby supervisor engine will assume that the port's link is down.","This is an informational message only; no action is required."
"C4K_SWITCHMANAGER","5","FLAPSHUTDOWN","Temporarily disabling port [char] due to flap","The specified port is going up and down (link up/down) in rapid succession. This condition is usually caused by a bad connection or problems with the link-level hardware. The switch will temporarily shut down the problem port. Every 5 seconds, the switch reenables the port to see if the problem has gone away. If not, the port will remain shut down indefinitely.","This is an informational message only; no action is required."
"C4K_SWNETFLOWMAN","4","FLOWSTATISTICSLOST","Flow rate too high.  [dec] packet byte count statistics update lost  [object-info]","The Cisco IOS flow uses 32-bit counters to store bytes per flow. The NetFlow Services Card engine uses 39-bit counters. When the switch reports a flow byte count that is greater than 32 bits, it stores the first 32 bits and logs a warning message.","This is an informational message only; no action is required."
"C4K_SWNETFLOWMAN","4","NETFLOWCACHEFULL","Netflow hardware-software map cache full. Could not create a map.","The switch uses a map to correlate flow in the software with corresponding flows in the hardware. This map is full and the switch cannot create any more mappings. This is a very rare condition. The switch is running at full capacity.","This is an informational message only; no action is required."
"C4K_SWNETFLOWMAN","6","FIXEDCREATIONTIME","Fixed creation time of  [dec] flows.","The system did not record the creation time of a flow. In this case, the system determined a creation time, which is usually the same time that was used for the last flow.","If this message reoccurs frequently, and you see that the system is fixing a lot of flows, contact your technical support representative."
"C4K_SYSMAN","2","POWERONSELFTESTFAIL","Supervisor module in slot [dec] failed Power-On-Self-Test(POST). Line cards are **NOT** initialized. Please use 'show diagnostics result module [dec]test <tid> detail' command for details.","A power-on self test (POST) failure is detected on the supervisor engine. When this occurs, the modules are not initialized.","Use the show diagnostics result module dec test tid detail command to isolate the problem. Reset the switch after you have resolved the supervisor engine failure."
"C4K_SYSMAN","3","CONTROLPATHFPGAAUTHENTICATIONFAILURE","Signature authentication of the control path FPGA failed in slot [dec].  The FPGA may be counterfeit or tampered with.","This message is displayed when the signature of the control path FPGA cannot be validated. When this happens, all ports on this module come up as faulty and cannot be used until the problem is resolved.","Remove and reinsert the module. If the problem persists, contact Cisco Technical Support."
"C4K_SYSMAN","3","LINECARDDIAGSFAILED","Module in slot [dec] failed online diagnostics. Please use 'show diagnostics result module [dec]test <tid> detail' command for details.","A module failed online diagnostics. When this occurs, all the module's ports are flagged as faulty and cannot be used until the problem is resolved.","Remove and reinsert the module. If the problem persists, copy the message exactly as it appears on the console or in the system log, contact your technical support representative, and provide the representative with the gathered information."
"C4K_SYSMAN","3","LINECARDDIAGSPARTIALFAILURE","Partial failure on module [dec]. Please use 'show diagnostics result module [dec]test <tid> detail' command for details.","Some of the module's ports have failed online diagnostics.","Remove and reinsert the module. If the problem persists, copy the message exactly as it appears on the console or in the system log, contact your technical support representative, and provide the representative with the gathered information."
"C4K_SYSMAN","4","MORETHANONEDEBUGCOMMANDEXECUTING","Cannot execute '[char]' right now, please try again later","More than one Telnet session issued a debugging command at the same time. Only one Telnet session can issue a debugging command at the same time. All Telnet sessions receive this message, except the Telnet session that issued the command first.","Try the command when other Telnet sessions are not issuing debugging commands."
"C4K_SYSMPC8540","3","MANAGEMENTPORTSTUCKINRESET","The management port driver was unable to take its  internal PHY out of reset.","During initialization, the front port management port was unable to take its internal PHY out of reset.","Reboot the supervisor. If the program occurs again, contact Cisco TAC support."
"C4K_TRANSCEIVERMAN","3","BADSEEPROM","Port [char]: Transceiver's seeprom is bad, try reinserting: vendor: [char], p/n: [char], s/n: [char]","A transceiver with a serial EEPROM has been detected in the port referred to in the message, and the read of the serial EEPROM's contents succeeded, but the contents are not valid (perhaps there was a bad checksum). The message tells the vendor, part number and serial number it read from the transceiver's serial EEPROM. This event could possibly happen because the transceiver is not seated correctly.","Try removing and reinserting the transceiver. If this message still appears after that, try the transceiver in another port, to verify that the transceiver is bad, and not the port. If the transceiver fails in another port, return the transceiver, as the transceiver must be reprogrammed for it to work. If the transceiver succeeds in other ports, but not the original port, that implies that the original port is bad, not the transceiver, and the module needs to be returned, to fix the port. As a further test of the port, other transceivers could be tried in the suspected bad port. If these other transceivers also fail in that port, it is very likely that the port is bad."
"C4K_TRANSCEIVERMAN","3","INCOMPATIBLE","Port [char]: New transceiver (speed [char]) is in compatible with this module","The inserted transceiver is an incompatible type for this module. Check documentation on supported transceivers for this module. Make sure the speed of the inserted transceiver matches with the port speed and it is of a supported type for this module.","Remove this transceiver from the port if it is found to be of incompatible type for this module."
"C4K_TRANSCEIVERMAN","3","MDIOERROR","Mdio bus error while looking for changed x2s on port [char]: [char]","There was an internal communication error when reading transceiver control data.","Remove and re-insert the transceiver. It may not be properly seated."
"C4K_TRANSCEIVERMAN","3","S2WERROR","S2w bus error while looking for changed transceivers on port [char]: [char]","Internal communication error when reading transceiver control data.","Remove and re-insert the transceiver. It may not be properly seated."
"C4K_TRANSCEIVERMAN","3","SEEPROMREADFAILED","Failed to read transceiver serial eeprom on port [char], try reinserting","A transceiver with a serial EEPROM has been detected in the port referred to in the message, but the read of the serial EEPROM's contents failed. It is necessary to read the serial EEPROM to determine what sort of transceiver it is. Sometimes the read fails because the transceiver is not seated correctly.","Try removing and reinserting the transceiver. If this message still appears after that, try the transceiver in another port, to verify that the transceiver is bad, and not the port. If the transceiver fails in another port, return the transceiver, as the transceiver must be reprogrammed for it to work. If the transceiver succeeds in other ports, but not the original port, that implies that the original port is bad, not the transceiver, and the module needs to be returned, to fix the port. As a further test of the port, other transceivers could be tried in the suspected bad port. If these other transceivers also fail in that port, it is very likely that the port is bad."
"C4K_TRANSCEIVERMAN","3","UNSUPPORTED","Port [char]: New transceiver (speed [char]) is not supported with this module.","The inserted transceiver is an unsupported type for this module.","Check product documentation to determine if the transceiver is supported for this module. Verify that the line speed of the inserted transceiver matches the port line speed."
"TRANSCEIVER","3","INTERNAL_ERROR","[char]","The TRANSCEIVER subsystem encountered an internal software error. The error message contains text that can be used to help identify the cause of the problem.","Contact your technical support representative."
"TRANSCEIVER","3","LAYER_CHANGE_ERROR","Error changing layer for port [char]","The TRANSCEIVER subsystem encountered an internal software error while changing the layer for this port.","Contact your technical support representative."
"UFAST_MCAST_SW","3","PROC_START_ERROR","UplinkFast packets will not be transmitted as the process could not be created.","The UplinkFast packets will not be transmitted as the process cannot be created.","Reload UplinkFast. If this problem persists even after the reload, copy the message exactly as it appears on the console or in the system log, contact your technical support representative, and provide the representative with the gathered information."
"UFAST_MCAST_SW","4","MEM_NOT_AVAILABLE","No memory is available for transmitting UplinkFast packets on Vlan [dec].","UplinkFast packets are not transmitted on VLAN [dec] due to a lack of memory.","Reduce other system activity to ease memory demands. Contact your technical support representative to determine whether you need to upgrade to a larger memory configuration."
"VQPCLIENT","2","CHUNKFAIL","Could not allocate memory for VQP","An error occurred when the system tried to allocate memory for the VQP client.","Copy the message exactly as it appears on the console or in the system log, contact your technical support representative, and provide the representative with the gathered information."
"VQPCLIENT","2","DENY","Host [enet] denied on interface [chars]","The VLAN Membership Policy Server (VMPS) denied access for the given host MAC address to an interface. [enet] is the host MAC address, and [chars] is the interface name.","This is an informational message only; no action is required. If you think that the host should have been allowed access, verify the configuration on the VMPS."
"VQPCLIENT","2","INITFAIL","Platform-specific VQP initialization failed. Quitting","An error occurred during initialization of the VQP client platform-specific code.","Copy the message exactly as it appears on the console or in the system log, contact your technical support representative, and provide the representative with the gathered information."
"VQPCLIENT","2","IPSOCK","Could not obtain IP socket","An error occurred when the system attempted to open an IP socket to the VMPS.","If the error message recurs, copy the message exactly as it appears on the console or in the system log, contact your technical support representative, and provide the representative with the gathered information."
"VQPCLIENT","2","PROCFAIL","Could not create process for VQP. Quitting","An error occurred while creating a process for the VQP client.","Copy the message exactly as it appears on the console or in the system log, contact your technical support representative, and provide the representative with the gathered information."
"VQPCLIENT","2","SHUTDOWN","Interface [chars] shutdown by VMPS","The VMPS directed that an interface be shut down. [chars] is the interface name.","This is an informational message only; no action is required. If you think that the port should not have been shut down, then verify the configuration on the VMPS."
"VQPCLIENT","2","TOOMANY","Interface [chars] shutdown by active host limit","The system shut down an interface because too many hosts have requested access to that port. [chars] is the interface name.","To reactivate the port, remove the excess hosts, and enter the no shutdown interface configuration command on the interface."
"VQPCLIENT","3","IFNAME","Invalid interface ([char]) in response","The VMPS sent an unsolicited response with an unknown interface name. [chars] is the name of the unknown interface.","Verify the VMPS configuration."
"VQPCLIENT","3","THROTTLE","Throttling VLAN change on [chars]","An attempt was made to change the VLAN assignment for an interface more often than once every 10 seconds. The VLAN change is denied. [chars] is the name of the interface.","This is an informational message only; no action is required. If this message reoccurs, verify the VMPS configuration and that unexpected hosts are not connected to the port."
"VQPCLIENT","3","VLANNAME","Invalid VLAN ([chars]) in response","VMPS specified a VLAN name that is unknown to the switch. [chars] is the invalid VLAN name.","Make sure that the VLAN exists on the switch. Verify the VMPS configuration."
"VQPCLIENT","7","NEXTSERV","Trying next VMPS","The system lost connectivity with the current VMPS and is changing to the next server in its list.","This is an informational message only; no action is required."
"VQPCLIENT","7","PROBE","Probing primary server [IP_address]","The system is trying to reestablish connectivity with the primary VMPS at the given IP address.","This is an informational message only; no action is required."
"VQPCLIENT","7","RECONF","Reconfirming VMPS responses","The switch is reconfirming all responses with the VMPS.","This is an informational message only; no action is required."
"C4K_WATCHDOG","3","CHILDFAILURE","Watchdog failure ([char]) - system may reset","The job [char] was unscheduled and not started soon enough to start its watchdog timer.","Determine what other activity is utilizing the supervisor engine."
"AAA","2","FORKFAIL","Cannot fork process %s","Attempted to fork a process and failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","2","FORKFAIL","Cannot fork process %s","Attempted to fork a process and failed. The reason could be either hardware or software.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","2","UNAVAILABLE","%s(%08X): Acct db for Id %08X absent","AAA internal error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","ACCT_IOMEM_LOW","AAA ACCT process suspended : low I/O memory","AAA ACCT process has been suspended due to insufficient IO memory","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","ATTRFORMATERR","Attribute with unknown format %d","An attribute was found with an invalid format","Attribute with unknown format in definition, call your technical support representative"
"AAA","3","ATTRFORMATERR","Attribute with unknown format %d","An attribute was found with an invalid format.","Attribute with unknown format in definition. Enable AAA debug and try to replicate the steps to get the message. If the meassage appears again, Check bug toolkit on Cisco website for the issue. If you didn't find one, Enter Show tech-support command, Collect all the information and error message and report it to your technical support representative."
"AAA","3","BADCURSOR","invalid cursor index %d max %d service %s protocol %s","An AAA client has provided an invalid attribute cursor to AAA.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","BADLIST","invalid list AAA ID %u","An AAA client has provided an invalid attribute list to AAA.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","BADMAGIC","Data structure failed magic number sanity check","A corrupted data structure has been found which was stored internally","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","BADMAGIC","Data structure failed magic number sanity check","A corrupted data structure has been found which was stored internally.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","BADMETHOD","Cannot process %s method %u","A method list function encountered a method list that was unknown, or could not be handled.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","BADMETHODERROR","Cannot process %s method %s","A method list function encountered a method type that was unknown, or could not be handled.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","BUFFER_OVERFLOW","Radius I/O buffer has overflowed","An unusually large number of RADIUS attributes has caused AAA to overflow its RADIUS I/O buffer.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","DROPACCTFAIL","Accounting record dropped, send to server failed: %s","An attempt to send an accounting record to a server failed.","Check that the server (TACACS+ or RADIUS) is operational. Next, check the NAS is configured properly. Finally, check that the NAS can communicate with the server"
"AAA","3","DROPACCTFAIL","Accounting record dropped, send to server failed: %s","An attempt to send an accounting record to a server failed. This happens when device exhaust all its retries and retransmission. The cause for this be the servers may not be operational or the NAS is not configured properly.","Check the server , whether they are operational or not. Next check whether the device is configured properly. Refer tothe server configuration section of the cisco IOS documentation. Finally, check that the NAS can communicate with the server. If the problem persist, Enter show running-config command, contact your cisco technical support representative and provide all the information gathered to the representative."
"AAA","3","INVALIDPARM","invalid parameter was used when accessing AAA function","A AAA client tried to use a AAA function with an invalid parameter.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","IPILLEGALMSG","Invalid use of ip_pid(%u)","This error means a process sent an illegal message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","IPILLEGALMSG","Invalid use of ip_pid(%u)","This message means a process sent an illegal message to IP which IP has not subscribed for","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","ISDNINTF","%s %s: Can not apply configuration to ISDN channel: %s","Configuration can not be applied to individual ISDN channels.","You need virtual-profiles and virtual-access interfaces to apply configuration to ISDN. Refer to the section on Configuring virtual profile by AAA Configuration in the Cisco IOS Dial Technologies Configuration Guide."
"AAA","3","MLIST_TOO_MANY_METHODS","method list '%s'","This is an internal software error. An AAA client attempted to add too many methods to a method list.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","NULLCURSOR","Null cursor","An AAA client has provided a non-existant attribute cursor to AAA.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","NULLVRF","Null vrf entry","None method authentication is not allowed in CLI","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","PARSEERR","Error(%d) parser is unable to parse %s per-user command","All attempts to parse this per_user unconfigure command failed.","The given unconfigure command was not unconfigured. Report it to your technical support representative."
"AAA","3","PARSEERR","Error(%d) parser is unable to parse %s per-user command","All attempts to parse this per_user unconfigure command failed. The unconfigure command is called when an error occurs while configuring per-user commands, to revert back. The unconfiguration may fail due to parser or AAA error.","The given unconfigure command was not executed. Switch on the debug peruser command and repeat the steps that caused the error. If you get the error, Report it to your technical support representative."
"AAA","3","SG_DEADTIME_FORKFAIL","Failed to fork process for %s.","Quite likely, we ran out of memory. Other explanations are possible.","If this message recurs. Check bug toolkit on Cisco website for the issue. If you didn't find one, Enter Show tech-support command, collect all the information and error message and report it to your technical support representative."
"AAA","3","SG_INTERNAL_ERROR","server group '%s': %s","This is an internal software error in the AAA server group subsystem.","This is an internal software error. Check bug toolkit on Cisco website for the issue. If you didn't find one, Enter Show tech-support command, collect all the information and error message, report it to your technical support representative."
"AAA","3","SG_TESTPROC_FORKFAIL","Failed to fork process for %s.","Quite likely, we ran out of memory. Other explanations are possible.","If this message recurs. Check bug toolkit on Cisco website for the issue. If you didn't find one, Enter Show tech-support command, Collect all the information and error message and report it to your technical support representative."
"AAA","3","UNAVAILABLE","%s %s: Can not apply configuration to ISDN channel: %s","Configuration can not be applied to individual ISDN channels.","You need virtual-profiles and virtual-access interfaces to apply configuration to ISDN. Refer to the section on Configuring virtual profiles by AAA Configuration in the Cisco IOS Dial Technologies Configuration Guide."
"AAA","3","UNAVAILABLE","%s :Peruser Could not sort the %s attributes","Sorting of the attributes received from AAA server failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","UNAVAILABLE","AAA ACCT process suspended : low I/O memory","AAA ACCT process has been suspended due to insufficient IO memory","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","UNAVAILABLE","AAA ID %u","Resource failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","UNAVAILABLE","AAA unable to create UID for incoming calls due to insufficient processor memory","Stop creating the AAA UID, due to LOW processor memory","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","UNAVAILABLE","AAA unable to handle accounting requests due to insufficient memory. So, we trash all queued accounting reguests, which may worry customerPlease upgrade your memory or plan to get more free memory by optimizing your configuration.","Dropping the accounting request as there is no enough processor memory","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","UNAVAILABLE","Accounting record dropped, send to server failed: %s","An attempt to send an accounting record to a server failed.","Check that the server (TACACS+ or RADIUS) is operational. Next, check the NAS is configured properly. Finally, check that the NAS can communicate with the server"
"AAA","3","UNAVAILABLE","Attribute with unknown format %d","An attribute was found with an invalid format","Attribute with unknown format in definition, call your technical support representative"
"AAA","3","UNAVAILABLE","Authorization method list '%s' is not defined. Please define it.","A given method list was listed in a command without defining it first. The method list should be defined before use.","Define the method list before using it."
"AAA","3","UNAVAILABLE","Cannot process %s method %s","A method list function encountered a method type that was unknown, or could not be handled.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","UNAVAILABLE","Cannot process %s method %u","A method list function encountered a method list that was unknown, or could not be handled.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","UNAVAILABLE","Cannot process %s server type %s","A method list function encountered a server type that was unknown, or could not be handled. This may be due to a server misconfiguration.","Research the cause of the misconfiguration and attempt to correct it, otherwise take the following 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","UNAVAILABLE","Data structure failed magic number sanity check","A corrupted data structure has been found which was stored internally","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","UNAVAILABLE","Error(%d) parser is unable to parse %s per-user command","All attempts to parse this per_user unconfigure command failed.","The given unconfigure command was not unconfigured. Report it to your technical support representative."
"AAA","3","UNAVAILABLE","Failed to fork process for %s.","Quite likely, we ran out of memory. Other explanations are possible.","If this message recurs, call your technical support representative for assistance."
"AAA","3","UNAVAILABLE","Invalid use of ip_pid(%u)","This message means a process sent an illegal message to IP which IP has not subscribed for","If this message recurs, call your technical support representative for assistance."
"AAA","3","UNAVAILABLE","Null cursor","A AAA client has provided a non-existant attribute cursor to AAA.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","UNAVAILABLE","Null vrf entry","A NULL vrf entry found while comparing the AAA VRF attributes.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","UNAVAILABLE","RADIUS process is unable to handle the requests due to insufficient low I/O memory","RADIUS process unable to handle request due to insufficient IO memory. Hence returning failure","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","UNAVAILABLE","Radius I/O buffer has overflowed","An unusually large number of Radius attributes has caused AAA to overflow it's Radius I/O buffer","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","UNAVAILABLE","Server '%i': %s","This is an internal software error in the AAA server group subsystem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","UNAVAILABLE","Unknown protocol %u","The AAA subsystem encountered an unknown protocol type.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","UNAVAILABLE","Unknown service %u","The AAA subsystem encountered an unknown service type.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","UNAVAILABLE","invalid cursor index %d max %d service %s protocol %s","A AAA client has provided an invalid attribute cursor to AAA.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","UNAVAILABLE","invalid hdl AAA ID %u, hdl %x, %s","A AAA client has provided an invalid attribute list handle to AAA.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","UNAVAILABLE","invalid list AAA ID %u","A AAA client has provided an invalid attribute list to AAA.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","UNAVAILABLE","invalid parameter was used when accessing AAA function","A AAA client tried to use a AAA function with an invalid parameter.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","UNAVAILABLE","method list '%s'","This is an internal software error. An AAA client attempted to add too many methods to a method list.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","UNAVAILABLE","method list '%s': %s","This is an internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","3","UNAVAILABLE","server group '%s': %s","This is an internal software error in the AAA server group subsystem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA","6","ACCTSESSIDWRAP","Accounting-Session-ID %d exceeded max value allowed","Accounting-Session-ID value exceeded max value allowed","This is informational only, not a error."
"AAA","6","ACCTSESSIDWRAP","Accounting-Session-ID %d exceeded max value allowed","Accounting-Session-ID value exceeded max value allowed. Now it is wrapping.","This is informational only, not an error."
"AAA","6","UNAVAILABLE","Accounting-Session-ID %d exceeded max value allowed","Accounting-Session-ID value exceeded max value allowed","This is informational only, not a error."
"AAA","6","UNAVAILABLE","Enable view requires to be authenticated by non-none methods,Please use the appropriate method with the login authentication","None method authentication is not allowed in CLI","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","3","ACCTATTR","last accounting attribute:","The data buffer overflowed while building the accounting packet.The accounting attribute that was being written to the buffer while the buffer overflow occured was logged.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","3","ACCTDUMP","dump of accounting data:","The data buffer overflowed while building the accounting packet as the total length of the attributes exceed the buffer size. Last 128 bytes of buffer data is dumped.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","3","BADAUTHENSTR","Bad authentication data: %s","The data buffer overflowed while building the authentication packet as the total length of the attributes exceeded the buffer size.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","3","BADREG","Illegal registry call.","An internal error has occurred","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","3","BADSTR","Bad accounting data: %s","During AAA accounting operations, the internal database of accounting information for a user was found to be corrupt. In all cases, this indicates an internal software error, and that accounting information for a particular user session has been lost.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","3","DROPACCTFULLQ","Accounting record dropped due to a full aaa accounting queue: %s-%s %s %s","An accounting record was dropped because there are too many accounting packets enqueued.","Disable periodic accounting if it is on. The accounting queue may have grown to be large, which is usually due to a non-responsive AAA server. Use 'show radius statistics' or 'show tacacs' to see if the number of timeouts is increasing or if the response delay is unusually high."
"AAAA","3","INTERNAL_ERROR","%s","This is an internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","3","NULUSR","accounting for null user","This message indicates an internal software error. During shutdown of a line or interface, the system tried to send accounting information via AAA, but could not find the user to which the accounting information belonged. The most likely reason for this error is trying to do accounting twice for the same event. This error message can occur without any loss of accounting information.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","3","RELOGIN","sanity check in re-login %s to %s","A software or hardware error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","3","UNAVAILABLE","%% AAA: Bad state for %s list name (%d)","A AAA method list is neither default nor named. This is bad.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","3","UNAVAILABLE","%s","Administrative process has been enabled but somehow could not runError Message    %AAAA-3-UNAVAILABLE: %% AAA: No free %s lists for %s  Explanation    You have reached the maximum number of possible authentication lists for this method.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","3","UNAVAILABLE","%% AAA: bad %s list %s","One of the AAA methods does not seem to have a list associated with it.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","3","UNAVAILABLE","%% AAA: bad argument (%0#4x)","We tried to NVGEN a non-existent AAA command.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","3","UNAVAILABLE","%% AAA: invalid %s list %d.","One of the AAA methods lists has inconsistent settings","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","3","UNAVAILABLE","%s AUTHOR/%s: Internal state is invalid: astruct 0x%x ustruct 0x%x","One of the two mentioned data-structures is not set, but is needed here. This is an internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","3","UNAVAILABLE","%s","This is an internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","3","UNAVAILABLE","%s method %d has no registry!","An internal error has occurred","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","3","UNAVAILABLE","%s: no method list-name.","An internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","3","UNAVAILABLE","AAA/ACCT/TIMER: No periodic update but timer set.","We are trying to free a timer, but the update method is not PERIODIC, and so no timer should exist.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","3","UNAVAILABLE","AAA/ACCT/TIMER: Periodic update but no timer.","We are trying to free a timer, and the method is PERIODIC, but no timer seems to exist.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","3","UNAVAILABLE","Accounting record dropped due to a full aaa accounting queue: %s-%s %s %s","An accounting record was dropped because there are too many accounting packets enqueued.","Disable periodic accounting if it is on. The accounting queue may have grown to be large, which is usually due to a non-responsive AAA server. Use 'show radius statistics' or 'show tacacs' to see if the number of timeouts is increasing or if the response delay is unusually high."
"AAAA","3","UNAVAILABLE","Accounting record dropped due to low memory: %s-%s %s %s","An accounting record dropped due to low memory.","Disable periodic accounting if it is on. Try to reduce the load on the router."
"AAAA","3","UNAVAILABLE","Accounting record dropped, send to server failed: %s-%s %s %s","An attempt to send an accounting record to a server failed.","Check that the server (TACACS+ or RADIUS) is operational. Next, check the NAS is configured properly. Finally, check that the NAS can communicate with the server"
"AAAA","3","UNAVAILABLE","Bad Subtype %d for %s (%d)","An internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","3","UNAVAILABLE","Bad accounting data: %s","During AAA accounting operations, the internal database of accounting information for a user was found to be corrupt. In all cases, this indicates an internal software error, and that accounting information for a particular user session has been lost.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","3","UNAVAILABLE","Bad authentication data: %s Error Message    %AAAA-3-UNAVAILABLE: Could not establish port information","This message indicates an internal software error. AAA could not determine a valid port string based on the information provided to it via a client.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.."
"AAAA","3","UNAVAILABLE","Duplicate free of server group 0x%x","This is an internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","3","UNAVAILABLE","Failed to create periodic accounting timer for user %s. This user may not generate periodic accounting records.","Failed to malloc a timer struct for periodic accounting.","Free up some memory and have user re-authenticate."
"AAAA","3","UNAVAILABLE","Failed to fork process for %s.","Quite likely, we ran out of memory. Other explanations are possible.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","3","UNAVAILABLE","Failed to start AAA process. AAA requests may not be processed.","Failed to create the AAA process.","Free up some memory."
"AAAA","3","UNAVAILABLE","Failed to start accounting process. Accounting records may not be sent.","Failed to create the accounting process.","Free up some memory."
"AAAA","3","UNAVAILABLE","Failed to start periodic accounting process. Periodic accounting records may not be sent.","Failed to create the periodic accounting process.","Free up some memory."
"AAAA","3","UNAVAILABLE","Illegal %s %s name %s rejected","A method-list name should not be the same as a method name. Please choose a different name for the method list.","Pick a different method-list name, that is not also a method-name."
"AAAA","3","UNAVAILABLE","Illegal registry call.","An internal error has occurred","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","3","UNAVAILABLE","Illegal server-group name %s (type %s).","The given server-group name is a name that could conflict with internally chosen lists.","Please pick a different server-group name."
"AAAA","3","UNAVAILABLE","Invalid request to create periodic accounting timer for user %s. Timer already exists.","Invalid client usuage of timer struct for periodic accounting.","Copy the error message exactly as it appears, and report it to your technical support representative."
"AAAA","3","UNAVAILABLE","No name for servergroup in method %s","An internal error has occurred","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","3","UNAVAILABLE","No server-group passed through parser.","An internal error has occurred","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","3","UNAVAILABLE","Overwrote internal buffer space %s","An internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","3","UNAVAILABLE","The list %d for %s is NULL. This should never be.","One of the method-lists, created at startup, wasn't created. This may cause a reload","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","3","UNAVAILABLE","Trying config command but should not be.","An internal error has occurred","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","3","UNAVAILABLE","accounting for null user","This message indicates an internal software error. During shutdown of a line or interface, the system tried to send accounting information via AAA, but could not find the user to which the accounting information belonged. The most likely reason for this error is trying to do accounting twice for the same event. This error message can occur without any loss of accounting information.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","3","UNAVAILABLE","accounting record dropped, output record queue full: %s-%s %s %s","An accounting record was dropped. The record could not be enqueued because the number of records in the output queue has exceeded the system limit.","Disable periodic accounting if it is on. [no] aaa accounting update newinfo periodic"
"AAAA","3","UNAVAILABLE","sanity check in re-login %s to %s","A software or hardware error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"AAAA","3","UNAVAILABLE","str_create overwrote its internal buffer.","An internal buffer, used to assemble a string, was exceeded, thus possibly corrupting other memory.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAAA","4","UNAVAILABLE","%% AAA: Unsupported option wait-start mapped to start-stop.","wait-start accounting is not supported. It is being mapped to start-stop","wait-start accounting is not supported. It is being mapped to start-stop"
"AAAA","4","UNAVAILABLE","Bad %s method-list name %s (this is only a warning)","A method-list name should not be the same as a method name. Please choose a different name for the method list.","Pick a different method-list name, that is not also a method-name."
"AAAA","4","UNAVAILABLE","Bad server-group name %s (type %s).","The given server-group name either doesn't exist or the given type does not match the defined server-group.","Verify that the group exists and has the same type."
"AAAA","4","UNAVAILABLE","Server-group %s is not of type %s.","The given server-group name does not match the specified type","Verify that the group exists and has the same type."
"AAAA","4","UNAVAILABLE","The aaa cache process is not created. Please configure aaa cache profile first","Cache was listed in a method-list without defining it first. Cache profile should be defined before use.","Define the cache profile before using it."
"AAAA","4","UNAVAILABLE","The server-group %s is not a tacacs+ server group. Please define %s as a tacacs+ server group.","The protocol used by the server-group doesn't support the configured aaa action.","Use a tacacs+ server-group."
"AAAA","4","UNAVAILABLE","The server-group %s is not defined. Please define it.","A given server-group was listed in a method-list without defining it first. Server-groups should be defined before use.","Define the server-group before using it."
"AAAA","4","UNAVAILABLE","Warning: DNIS group %s is not defined.","The DNIS group was used without defining it first. It should be defined before use.","Define the DNIS group before using it."
"AAAA","4","UNAVAILABLE","Warning: Server %i is not defined.","The given server is not on the master-list, and should be defined, or unexpected things might happen.","Please define the server on the appropriate master-list as soon as possible."
"AAAA","4","UNAVAILABLE","Warning: Server %i:%d,%d is not part of server group %s.","The server does not belong to the specified server group","Please check that the specified server belongs to the server group"
"AAAA","6","UNAVAILABLE","%s %s: %s","This administrative message was passed to the NAS from the AAA server","No action need be taken, but the message may contain usefull information regarding some event on the server"
"AAAA","6","UNAVAILABLE","%s %s: %s","This message was passed to the NAS from the AAA server","No action need be taken, but the message may contain usefull information regarding some event on the server"
"AAAA","6","UNAVAILABLE","%s","A AAA accounting start message.","This information is for information only."
"AAAA","6","UNAVAILABLE","%s","A AAA accounting stop message.","This information is for information only."
"AAAA","6","UNAVAILABLE","%s","A AAA accounting watchdog/update message.","This information is for information only."
"AAL5","1","UNAVAILABLE","%s: No buffer available for size %d bytes","There is no memory available for buffer allocation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAL5","1","UNAVAILABLE","%s","There is no memory available for allocation from heap. The error message contains text which can be used to help identify the nature of the problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAL5","1","UNAVAILABLE","msgtxt_nomemory","An operation could not be accomplished because of a low-memory condition. The current system configuration, network environment, or possibly a software error might have exhausted or fragmented the system's memory.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a configuration that has more memory."
"AAL5","2","UNAVAILABLE","%s","AAL5 datapath has encountered a critical software error. The error message contains text which can be used to help identify the nature of the problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAL5","3","UNAVAILABLE","%s","AAL5 datapath has encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAL5","3","UNAVAILABLE","%s","The AAL5 subsystem encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAL5","3","UNAVAILABLE","%x, orig %x, port=%s","This message is only seen during AAL5 debug. It is used for debugging AAL5 errors","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAL5","3","UNAVAILABLE","Flow Hdr: (%d) %s","AAL5 datapath has received a large packet it cannot handle or there are no more buffers available. So the packet is dropped. The error message contains text which can be used to help identify the nature of the problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAL5","3","UNAVAILABLE","Flow Hdr: (%d) %s","AAL5 datapath has received a packet with AAL5 checksum error. So the packet is dropped. The error message contains text which can be used to help identify the nature of the problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAL5","3","UNAVAILABLE","Input Interface %s: %s","AAL5 datapath has received a packet with invalid encap for packet type(DATA, CNTL,..). Th packet is dropped. The error message contains text which can be used to help identify the nature of the problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA_CACHE","3","NULL_TREE_PERIODIC_PROC","Cache Tree pointer is of null value","The cache tree pointer is of null value.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AAA_CACHE","3","UNAVAILABLE","Cache Tree pointer is of null value","The cache tree pointer is of null value.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AC","3","AC_PROVISION","%s","An error was encountered during Attachment Circuit [un]provisioning.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AC","3","AC_SUBBLOCK","%s","An error was encountered during Attachment Circuit sub-block creation or removal.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AC","3","AC_VECTOR","%s","An error was encountered during Attachment Circuit configuration which caused problems in the setting or restoration of the interface vectors.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AC","3","UNAVAILABLE","%s","An error was encountered during Attachment Circuit [un]provisioning.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AC","3","UNAVAILABLE","%s","An error was encountered during Attachment Circuit configuration which caused problems in the setting or restoration of the interface vectors.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AC","3","UNAVAILABLE","%s","An error was encountered during Attachment Circuit sub-block creation or removal.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AC","3","UNAVAILABLE","Circuit info missing in %s message.","AC Manager received message with missing circuit info","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AC","3","UNAVAILABLE","Corrupted L2SS handle [%x].","An internal L2SS Manager occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AC","3","UNAVAILABLE","Encountered a NULL context in %s","Encountered a NULL context in L2SS Manager.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AC","3","UNAVAILABLE","Received %s","Attachment Circuit Manager recieves invalid message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AC","3","UNAVAILABLE","Received invalid %s handle","Attachment Circuit Manager recieves invalid handle.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AC","3","UNAVAILABLE","Received unexpected %s message","L2SS recieve unexpected message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AC","3","UNAVAILABLE","Wrong set of keys in %s message","SIP sends a wrong set of keys to L2SS Manager.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACCESS_IE","3","UNAVAILABLE","Caller passed in invalid handle - traceback to follow.","An invalid handle was encountered in the Access IE library.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACE","2","UNAVAILABLE","Crypto engine error: %s (%d)","A crypto engine operation did not complete.This error condition can indicate that the crypto enginecannot bind or unbind an interface to a crypto engine.It can also indicate that the crypto engine cannot queryan interface ID.","Remove the cryptomap set from the interface by issuing no crypto map command. Then reattach the cryptomap set to the interface using crypto map command. Although removing and reattaching the crypto map might fix the cryptographic engine operation failure, report the failure to your technical support representative along with the sequence of commands that lead to the failure."
"ACE","2","UNAVAILABLE","Internal %s table error: %s","Internal table operation fails. This means the state of the module is mostly like inconsistent.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACE","3","INITFAIL","%s: initialization failed (%s)","ACE initialization sequence failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACE","3","INVTID","%s: %s of invalid %s trans id %d","An invalid transaction ID of for the indicated transaction type was encountered","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACE","3","NOMORETID","%s: out of %s transactions","Transaction pool for the indicated transaction type was exhausted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACE","3","UNAVAILABLE","%s: %s NAK trans 0x%x; opcode 0x%x; param 0x%x","An negative acknowledge occured in the indicated control transaction.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACE","3","UNAVAILABLE","%s: %s of invalid %s trans id %d","An invalid transaction ID of for the indicated transaction type was encountered","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACE","3","UNAVAILABLE","%s: %s trans 0x%x; opcode 0x%x (%s); param 0x%x; error 0x%x (%s); retry cnt %d","An error occured in the indicated control transaction.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACE","3","UNAVAILABLE","%s: %s trans 0x%x; opcode 0x%x (%s); param 0x%x; too many retries","An error occured in the indicated control transaction.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACE","3","UNAVAILABLE","%s: %s trans 0x%x; opcode 0x%x; param 0x%x; error 0x%x; retry cnt %d","An error occured in the indicated control transaction.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACE","3","UNAVAILABLE","%s: Received truncated HAPI message (tlen=%d, actual=%d)","The received ACE control packet was smaller than the size field indicated","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACE","3","UNAVAILABLE","%s: boot error: %s","The ACE completed booting, but with an error status code. ACE will not operate and it will not register with the crypto subsystem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACE","3","UNAVAILABLE","%s: crashdump retrieval error: %s %s","An error occurred during crashdump file retrieval from ACE.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACE","3","UNAVAILABLE","%s: crashdump retrieval initiated to file %s","The ACE crashed and was rebooted. Upon reboot, a crashdump file was detected and uploaded to the sup-bootflash filesystem.","Report the crash and transfer the crashdump file to your technicalsupport representative."
"ACE","3","UNAVAILABLE","%s: initialization failed (%s)","ACE initialization sequence failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACE","3","UNAVAILABLE","%s: out of %s transactions","Transaction pool for the indicated transaction type was exhausted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACE","3","UNAVAILABLE","ACE %s failed to register.","The ACE failed to register with CEAL","Reset the hw module"
"ACE","3","UNAVAILABLE","Interface %s has no crypto engine slot","An IKE SA was requested for a given interface, but no crypto engine slot was assigned to that interface","Configure the interface in question with the `crypto engine [sub]slot' command"
"ACE","3","UNAVAILABLE","Too many %s in the system. Cannot allocate a new one","All VPN-accelerator resources of a particular are in used and thus this allocation request fails.","Remove the crypto map set from the interface. Reduce the number of that resource in the system. For ACL, reduce the number of ACL permit ACE in the system. For cryptomap, reduce thenumber of cryptomaps in the system. For SPD and SPD map, reduce the number of interface with cryptomap set attached."
"ACE","3","UNAVAILABLE","Too may %s IDs in the system. Cannot allocate a new one","All the IDs of the specified type are in use","Reduce the traffic load, number of IPSec tunnels and/or frequency of re-key.If this message was seen under light loading conditions, thencopy the error message exactly as it appears, and report it to your technical support representative."
"ACE","6","UNAVAILABLE","%s has been moved from %s to %s to relieve congestion","The congestion manager has moved a tunnel from a congested crypto engine to an uncongested crypto engine","System performance is not affected. No customer action is necessary."
"ACE","6","UNAVAILABLE","%s: %s","This is informational message from ACE","This is informational message from ACE. This occurs in normal operation."
"ACE","6","UNAVAILABLE","%s: boot info: %s","The ACE completed booting, but with a non-zero informational status code. This does not indicate an error and ACE will run normally.","No action is necessary."
"ACE","6","UNAVAILABLE","%s: crashdump retrieval complete","The ACE crashed and was rebooted. Upon reboot, a crashdump file was detected and uploaded to the sup-bootflash filesystem.","Report the crash and transfer the crashdump file to your technicalsupport representative."
"ACE","6","UNAVAILABLE","%s: received unexpected IPsec packet: src IP: %i; dst IP: %i; firsthop/lasthop = %s/%s (count=%d)","An IPsec packet was unexpectedly forwarded to the RP","If this message was seen in the context of the router booting, enabling the hardware crypto accelerator, or with an invalid peer IP address then this message is normal and can be safely ignored. Otherwise, please copy the error message exactly as it appears, and report it to your technical support representative."
"ACE","6","UNAVAILABLE","%s: received unexpected IPsec packet: src: %s; dst: %s; (count=%d)","An IPsec packet was unexpectedly forwarded to the RP","If this message was seen in the context of the router booting, enabling the hardware crypto accelerator, then this message is normal and can be safely ignored. Otherwise, please copy the error message exactly as it appears, and report it to your technical support representative."
"ACE","6","UNAVAILABLE","All crypto engines are congested, assigning %s to %s","The congestion manager has assigned a new tunnel to an already congested crypto engine. All crypto engines have indicated congestion, the least congested engine was selected for the tunnel","Packets may be lost on some tunnels, either reduce bandwidth used by existing tunnels or install additional crypto engines"
"ACE","6","UNAVAILABLE","VPN-SPA switchover: %d/%d has been %s %d/%d","A blade to blade switcover has occurred. System performance is not affected.","System performance is not affected. No customer action is necessary."
"ACLMERGE","3","CUDDERROR","A CUDD Library error was detected in %s","An error was detected by the CUDD Library, the ACL-Merge for this invokation has failed. This could result in more traffic being switched by software. The effect of this could be lower performance, for the interface for which the merge failed.","Copy and save this message. Report this to Engineering along with the ACL configuration of this device. Use Topic to search for a similar DDTS. If none found, write a DDTS for this problem"
"ACLMGR","2","UNAVAILABLE","Cannot create ACL Manager data structures for VLAN Map %s","The ACL Manager could not allocate the data structures needed to describe a VLAN Map in a form that can be loaded into hardware. Probably caused by lack of free memory.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACLMGR","2","UNAVAILABLE","Cannot create VMR data structures for access list %s","The ACL Manager could not allocate the data structures needed to describe an ACL in a form that can be loaded into hardware. Probably caused by lack of available memory.","Use a less complicated configuration that requires less memory."
"ACLMGR","2","UNAVAILABLE","Cannot create memory block for VLAN %d","The ACL Manager was unable to save per-VLAN information needed for its correct operation. Some per-interface features, such as access groups or VLAN maps, will not be configured correctly.","Use a less complicated configuration that requires less memory."
"ACLMGR","3","UNAVAILABLE","%s ACL merge error %d (%s) on %s label %d","The ACL Manager was unable to complete the merge of the configured features into a form suitable for loading into the hardware. Packets potentially affected by this feature will be sent to the CPU for processing instead. The most likely cause is specifying an ACL that is too large or too complex for the system to handle.","Try specifying a smaller and less complicated configuration."
"ACLMGR","3","UNAVAILABLE","Acl Tcam Full! Sofware Forwarding packets on %s label %d on %s %s","There are too many Acl configuration for the platform specific ACL Tcam Table to support.","Reduce the number IP or MAC access lists to be configured to interfaces."
"ACLMGR","3","UNAVAILABLE","Augmenting of access-map %s on %s label %d failed","The system ran out of CPU DRAM when attempting to merge internally required elements with the configuredaccess map(s).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACLMGR","3","UNAVAILABLE","Cannot allocate %s label for vlan-id %d","The ACL Manager was unable to allocate a label for the features on this interface. This means that the hardware cannot be programmed to implement the features, and packets for this interface will be filtered in software. There is a limit of 256 labels per direction.","Allocate more space to the relevant section of the TCAM and reboot, or else use a simpler configuration. Use the same ACLs on multiple interfaces, if possible."
"ACLMGR","3","UNAVAILABLE","Insert of access-map %s #%d into %s label %d failed","The system ran out of CPU DRAM when trying to merge sections of an access map.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACLMGR","3","UNAVAILABLE","Reloading %s label %d feature","The ACL Manager was able to fit more of the configured features on this label into the hardware. One or more features had previously been unloaded because of lack of space.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACLMGR","3","UNAVAILABLE","Too many (%d) levels of recursion while merging ACLs (code %d).","The configuration is too complicated for the platform specific ACL merge code to support. Most likely cause is including too many separate access lists in a single VLAN map or policy map.","Reduce the number IP or MAC access lists (considered separately) in any one VLAN or policy map to fewer than the number of levels reported by this log message."
"ACLMGR","3","UNAVAILABLE","Unknown VMR access group action 0x%x","An internal software error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACLMGR","3","UNAVAILABLE","Unloading %s label %d feature","The ACL Manager was unable to fit the complete configuration into the hardware, so some features will have to be applied in software. This prevents some or all of the packets in a VLAN from being forwarded in hardware, and requires them to be forwarded by the CPU. Multicast packets may be dropped entirely instead of being forwarded.","Allocate more space to the relevant section of the TCAM and reboot, or else use a simpler configuration. Use the same ACLs on multiple interfaces, if possible."
"ACL_HDL_HA_API","3","UNAVAILABLE","%s","A run-time module could not obtain the resources that are required to complete a task. The failure most likely occurred because of a software error or a lack of system memory. Additional details on the nature of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized.","If you determine that this condition was caused by a lack of system memory, reduce system activity to ease memory demands, or if conditions warrant, upgrade to a larger memory configuration. Otherwise, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACL_HDL_HA_API","3","UNAVAILABLE","Failed to register with %s, rc =%d","A redundancy client could not be registered. An internal failure associated with client registration occurred in the run-time module specified in the message output. The return code that is specified in the message output identifies the type of failure that was detected. The failure most likely occurred because of a software error. The system state between the active and standby units might not be properly synchronized.",".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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACL_HDL_HA_API","3","UNAVAILABLE","Failed to send %s message to active for %s, rc=%d","The specified synchronization message, which is an internal IPC message, could not be sent to the active unit in the specified run-time module. The failure most likely occurred because of a software error. Additional details on the nature of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACL_HDL_HA_API","3","UNAVAILABLE","Failed to send %s message to standby for %s, rc=%d","The specified synchronization message, which is an internal IPC message, could not be sent to the standby unit in the specified run-time module. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the type of failure. The system state between the active and standby units might not be properly synchronized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.."
"ACL_HDL_HA_API","3","UNAVAILABLE","Invalid %s message received","A message that is used for state synchronization was not received correctly. An internal data structure for a message could not be retrieved. The failure most likely occurred because of a software error. The system state between the active and standby units might not be properly synchronized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACL_HDL_HA_API","3","UNAVAILABLE","Invalid checkpointing status code received, rc=%d","An invalid checkpoint status code has been detected. An internal status code that is associated with checkpointing was found to be invalid. The return code that is specified in the message output identifies the invalid code that was detected. The failure most likely occurred because of a software error. The system state between the active and standby units might not be properly synchronized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACL_HDL_HA_API","3","UNAVAILABLE","No checkpointing buffer for %s, rc=%d","A message data buffer that is used for state synchronization could not be obtained. An internal data structure could not be allocated for synchronization in the run-time module specified in the message output. The return code that is specified in the message output identifies the type of failure. The failure most likely occurred because of a software error or a lack of system memory. The system state between the active and standby units might not be properly synchronized.","If you determine that this condition was caused by a lack of system memory, reduce system activity to ease memory demands, or if conditions warrant, upgrade to a larger memory configuration. Otherwise, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.."
"ACL_HDL_ISSU","2","UNAVAILABLE","ACL handle ISSU client encountered unexpected client nego_done. Error: %d (%s)","An ISSU-compliant client transitions through a series of internal states. The ACL handle ISSU client encountered a 'client negotiation done' state that was unexpected. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","Show issu session and show issu negotiated capability )"
"ACL_HDL_ISSU","2","UNAVAILABLE","ACL handle ISSU client failed to get buffer for message. Error: %d (%s)","The ACL handle ISSU client failed to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","Show logging and show checkpoint client. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACL_HDL_ISSU","2","UNAVAILABLE","ACL handle ISSU client failed to register session information. Error: %d (%s)","The ACL handle ISSU client failed to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly.","Show issu capability entries, issu session and show issu negotiated capability. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACL_HDL_ISSU","2","UNAVAILABLE","ACL handle ISSU client failed to send negotiation message. Error: %d (%s)","The ACL handle ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","Show logging and show checkpoint client. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACL_HDL_ISSU","2","UNAVAILABLE","ACL handle ISSU client initialization failed to %s. Error: %d (%s)","The ACL handle ISSU client could not be initialized. This initialization failure must be addressed before in-service software upgrade or downgrade can be performed successfully. If you do not address this failure, there will be downtime during software upgrade or downgrade.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACL_HDL_ISSU","3","UNAVAILABLE","'Message Type %d' is not supported by ACL handle ISSU client at peer","The ACL handle ISSU client at the peer supervisor is not compatible for this message type. The ACL handle client will be marked as incompatible with the peer.","Show issu capability entries, issu session and show issu negotiated capability. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACL_HDL_ISSU","3","UNAVAILABLE","ACL handle ISSU client %s transform failed for 'Message Type %d'. Error: %d (%s)","The ACL handle ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In both cases, the ACL handle state between the active device and the standby device is not identical.","Show issu session and show issu negotiated version. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACL_HDL_ISSU","3","UNAVAILABLE","ACL handle ISSU client 'Message Type %d' is not compatible","The ACL handle ISSU client received an incompatible message from the peer device. The message cannot be processed.","Show issu session and show issu negotiated version. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACL_HDL_ISSU","3","UNAVAILABLE","ACL handle ISSU client capability exchange result incompatible.","The Switch Vlam ISSU client capability exchange have negotiated as incompatible with the peer.","Show issu capability entries, issu session and show issu negotiated capability. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACL_HDL_ISSU","3","UNAVAILABLE","ACL handle ISSU client capability list is empty.","The ACL handle ISSU client capability exchange list size is invalid.","LShow issu capability entries, issu session and show issu negotiated capability. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACL_HDL_ISSU","3","UNAVAILABLE","ACL handle ISSU client does not have a valid registered session.","The ACL handle ISSU client does not have a valid registered session.","Show issu session and show issu negotiated version. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACL_HDL_ISSU","3","UNAVAILABLE","ACL handle ISSU client failed to get the MTU for Message Type %d.Error: %d (%s)","The ACL handle ISSU client failed to calculate the MTU for the specified message. The ACL handle ISSU client is not able to send the message to the standby device.","Show issu session and show issu negotiated version. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ACL_HDL_ISSU","3","UNAVAILABLE","ACL handle ISSU client failed to unregister session information. Error: %d (%s)","The ACL handle ISSU client failed to unregister session information.","Show issu session and show issu negotiated version. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ADJ","3","UNAVAILABLE","Adj bundles: %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ADJ","3","UNAVAILABLE","Adj resolve request: %s %s %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ADJ","3","UNAVAILABLE","Adj stack2 error %s: %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ADJ","3","UNAVAILABLE","Adjacency distribution client: %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ADJ","3","UNAVAILABLE","Adjacency mac address for %s overflowed by %d bytes","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ADJ","3","UNAVAILABLE","Adjacency mac string for %s not byte aligned, offset %x, length %x","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ADJ","3","UNAVAILABLE","Allocating adj when adj subsystem down","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ADJ","3","UNAVAILABLE","Bundle type %s must be ISSU aware to send to slot(s) %s","The given bundle type is not ISSU aware so cannot be distributed to a slot with which ISSU negotiation has occurred. This indicates a design problem which requires code changes to fix.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ADJ","3","UNAVAILABLE","CEF Interface not found - %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ADJ","3","UNAVAILABLE","Failed to allocate an adjacency","An internal software error occurred. This is probably because not enough memory was available.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ADJ","3","UNAVAILABLE","Failed to allocate an adjacency debug filter block","An internal software error occurred. This is probably because not enough memory was available.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ADJ","3","UNAVAILABLE","Failed to allocate an adjacency interest list subblock","An internal software error occurred. This is probably because not enough memory was available.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ADJ","3","UNAVAILABLE","Failed to allocate an adjacency summary event block","An internal software error occurred. This is probably because not enough memory was available.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ADJ","3","UNAVAILABLE","Failed to allocate memory %s","An internal software error occurred. This is probably because not enough memory was available.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ADJ","3","UNAVAILABLE","Failed to deallocate an adjacency interest list subblock","An internal software error occurred. This is probably because not enough memory was available.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ADJ","3","UNAVAILABLE","Failed to deallocate memory %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ADJ","3","UNAVAILABLE","Failed to dispatch a refresh adjacency summary event","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ADJ","3","UNAVAILABLE","Failed to enqueue an adjacency summary event block","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ADJ","3","UNAVAILABLE","Failed to initialise adjacency RP broker facility","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ADJ","3","UNAVAILABLE","Failed to initialise adjacency interest list facility","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ADJ","3","UNAVAILABLE","Failed to initialise adjacency subblock facility","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ADJ","3","UNAVAILABLE","Generation of encapsulation string for %s failed","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ADJ","3","UNAVAILABLE","Illegal arguments - %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ADJ","3","UNAVAILABLE","Unexpected state transition from %s to %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ADJ","3","UNAVAILABLE","Using an unsupported address type %d when trying to add/delete/modify/find an adjacency","An internal software error occurred. An attempt to reference an adjacency with an unsupported address type has been made.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ADJ","3","UNAVAILABLE","Using an unsupported linktype %s when trying to add/delete/modify/find an adjacency","An internal software error occurred. An attempt to reference an adjacency with an unsupported address type has been made.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ADJ","3","UNAVAILABLE","Zero address length detected distributing adj %s","An internal software error occurred. An attempt to reference an adjacency with an unsupported address type has been made.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ADJ","3","UNAVAILABLE","adjacency %s is followed by bad magic","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ADJ","3","UNAVAILABLE","adjacency mac string end %x not %s aligned","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ADJ","5","UNAVAILABLE","Midchain parent maintenance for %s - %s","A midchain adjacency failed to stack onto output chain because a loop was detected. Traffic through the adjacency will be dropped until the adj is restacked. This condition is typically transient and is rectified by the control plane driving stacking. E.g. if an ip tunnel destination resolves through the tunnel transiently this message would appear. The situation would be rectified either by learning the tunnel destination through an inteface other than the tunnel itself or by bringing the tunnel down","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AFLSEC","6","OALRL","Oal logging rate-limited or missed %d packet%s","Some packet matching logs were missed because the log messages were rate-limited or cache table was full or no log buffers were available.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AFLSEC","6","OALRL","Oal logging rate-limited or missed %d packet%s","Some packet matching logs were missed because the logmessages were rate-limited or cache table was full or no log buffers were available.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AGGMGR","0","UNAVAILABLE","No space left for creator %s to add data item to agg list (items %d max %d remaining %d)","An attempt was made to add an item to an aggregation list that had just been successfully created but for some reason the add failed. This situation should never occur. If it does occur, then it is the result of a program error which would be found during development and considered an internal error. There is no work around.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AIP","3","UNAVAILABLE","%s Failed to setup vc %d (Cause: %s)","The AIP driver failed to set up a virtual circuit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AIP","3","UNAVAILABLE","Interface %s, Failed to setup vc %d (Cause: %s) Expected range [%d .. %d]Kbps for AIP Average Rate Metering. Average Rate=Peak Rate= %d Kbps turns Average Rate Metering OFF","A software or hardware error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALARM","1","UNAVAILABLE","CRITICAL alarm condition detected","An critical alarm event has happened, it will cause the serious result, and needs immediate attention and to be fixed. Syetem will shut down within two minutes.","Check the source of the critical alarms to take corresponding actions. Don't turn on power unless the situation is corrected. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALARM","2","UNAVAILABLE","Major alarm condition detected","An major alarm event has happened, it will affect the system service, and needs attention or fix.","Check the source of the major alarms to take corresponding actions. This situation should be corrected or be aware of. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALARM","3","UNAVAILABLE","Attempt to change alarm status for undefined type","The alarm subsystem has no record of this type of alarm. The type has either not be registered or has been deleted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALARM","3","UNAVAILABLE","Attempt to set alarm status for undefined source","The alarm subsystem has no record of this alarm source. The source has either not be registered or has been deleted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALARM","3","UNAVAILABLE","Max number of alarm sources exceeded","Too many alarm sources were added by the system","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALARM","3","UNAVAILABLE","Minor alarm condition detected","An minor alarm event has happened, it does not affect the system service, but needs attention.","Check the source of the minor alarms to avoid the situation getting worse. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALARM","3","UNAVAILABLE","No alarm messages left","There we no more alarm messages available in the message cache","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALARM","3","UNAVAILABLE","OUT of Memory: %s Error Message    %ALARM-3-UNAVAILABLE: Unknown Alarm Severity Class","The alarm status tables contain an alarm entry with an unknown alarm severity class.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.."
"ALIGN","3","UNAVAILABLE","%s","A trace that shows where the previous ALIGN error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALIGN","3","TRACE","-Traceback= %08x %08x %08x %08x %08x %08x %08x %08x","A trace that shows where the previous ALIGN error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALIGN","3","UNAVAILABLE","-Traceback= %08x %08x %08x %08x %08x %08x %08x %08x","A trace that shows where the previous ALIGN error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.."
"ALIGN","3","UNAVAILABLE","-Traceback= %s","A trace that shows where the previous ALIGN error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALIGN","3","UNAVAILABLE","Alignment correction made at %s %sing %s","A software component within the router needs memory optimization.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALIGN","3","UNAVAILABLE","Alignment correction made at 0x%x %sing 0x%x","A software component within the router needs memory optimization.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALIGN","3","UNAVAILABLE","Alignment log is full - no new entries will be recorded","The router identified more software components in need of memory optimization than it can record.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALIGN","3","UNAVAILABLE","Spurious memory access made at %s reading %s","An attempted but illegal access to a low memory address within a software component in the router has been temporarily blocked.","Copy the error message exactly as it appears on the console or in the system log. Issue the show alignment command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show alignment output, call your Cisco technical support representative and provide the representative with the gathered information."
"ALIGN","3","UNAVAILABLE","Spurious memory access made at 0x%x reading 0x%x","An attempted but illegal access to a low memory address within a software component in the router has been temporarily blocked.","Copy the error message exactly as it appears on the console or in the system log. Issue the show alignment command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show alignment output, call your Cisco technical support representative and provide the representative with the gathered information."
"ALIGN","3","UNAVAILABLE","Spurious memory access made at 0x%x reading 0x%x","An error was identified (and temporarily corrected) within a software component in the router.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALIGN","3","UNAVAILABLE","Warning : read accees failed at %s, still continuing","In ls1010 read access failures do not make the box reload. They can be caused by either a bad register value in the asp ver 3.3 or earlier or a real problem in the hardware","If the ASP version is 3.3 or more, report it to your technical support representative."
"ALPS","3","UNAVAILABLE","ALPS: Assertion failed: %s","An internal software error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALPS","3","UNAVAILABLE","ALPS: Assertion failed: %s","An internal software error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALPS","3","UNAVAILABLE","ASCU %02x on interface %s has an internal FSM error.","Internal error.","Turn debug flags on, capture traces & contact Cisco technical support"
"ALPS","3","UNAVAILABLE","Polling for ASCU %02x on interface %s is stalled.","The polling mechanism for an ALPS interface has become stuck.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALPS","5","ASCU_DISABLED_ASCU_STUCK","ASCU [hex] on interface [chars] has been disabled since 4 consecutive messages were received from same SID.","An ALPS agent set control unit (ASCU) has been automatically disabled.","No action is required."
"ALPS","5","ASCU_DOWN","ASCU [hex] on interface [chars] is down.","An ALPS agent set control unit (ASCU) has transitioned from up to down.","No action is required."
"ALPS","5","ASCU_UP","ASCU [hex] on interface [chars] is up.","An ALPS agent set control unit (ASCU) has transitioned from down to up.","No action is required."
"ALPS","5","CIRCUIT_CLOSED","Circuit [chars] changed state to closed, rsn = [chars].","An ALPS circuit has tranistioned from open to closed","No action is required."
"ALPS","5","CIRCUIT_OPEN","Circuit [chars] changed state to open.","An ALPS circuit has transitioned from closed to open.","No action is required."
"ALPS","5","PEER_CLOSED_DYNAMIC_INACTIVITY","Peer ([IP_address], [chars]) closed due to inactivity.","An ALPS peer connection is now closed due to inactivity.","No action is required."
"ALPS","5","PEER_CONN_ID_CHANGE","Peer ([IP_address], [chars]) ID modified to ([IP_address], [chars]).","An ALPS peer connection identifier has changed.","No action is required."
"ALPS","5","PEER_OPEN","Peer ([IP_address], [chars]) changed state to open.","An ALPS peer connection is now open.","No action is required."
"ALIGN","3","UNAVAILABLE","Warning : read accees failed at %s, still continuing","In ls1010 read access failures do not make the box reload. They can be caused by either a bad register value in the asp ver 3.3 or earlier or a real problem in the hardware","If the ASP version is 3.3 or more, report it to your technical support representative."
"ALPS","5","UNAVAILABLE","ASCU %02x on interface %s has been disabled since 4 consecutive messages were received from same SID.","An ALPS ASCU has been automatically disabled.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALPS","5","UNAVAILABLE","ASCU %02x on interface %s is down.","An ALPS ASCU has transitioned from up to down.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALPS","5","UNAVAILABLE","ASCU %02x on interface %s is up.","An ALPS ASCU has transitioned from down to up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALPS","5","UNAVAILABLE","Circuit %s changed state to closed, rsn = %s.","An ALPS circuit has tranistioned from open to closed","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALPS","5","UNAVAILABLE","Circuit %s changed state to open.","An ALPS circuit has transitioned from closed to open.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALPS","5","UNAVAILABLE","Peer (%i, %s) ID modified to (%i, %s).","An ALPS peer connection identifier has changed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALPS","5","UNAVAILABLE","Peer (%i, %s) changed state to closed.","An ALPS peer connection is now closed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALPS","5","UNAVAILABLE","Peer (%i, %s) changed state to open.","An ALPS peer connection is now open.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALPS","5","UNAVAILABLE","Peer (%i, %s) closed due to inactivity.","An ALPS peer connection is now closed due to inactivity.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALPS","6","UNAVAILABLE","Circuit %s has entered a congested state.","An ALPS circuit is experiencing congestion.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALPS","6","UNAVAILABLE","Circuit %s received a Circuit Open Confirm with a list of rejected ascus","An ALPS circuit sent a Circuit Open Request message and received a Circuit Open Confirm with a list of rejected ascus.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALPS","6","UNAVAILABLE","Circuit %s received a Circuit Open Failed message, rsn = %s.","An ALPS circuit sent a Circuit Open Request message and received a Circuit Open Failed message as a reply.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALPS","6","UNAVAILABLE","Circuit %s received a Circuit Open Failed message, rsn = %s.","An ALPS circuit sent a Circuit Update message and received a Circuit Open Failed message as a reply.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALPS","6","UNAVAILABLE","Host unresponsive on X.25 VC for circuit %s","The X.25 or EMTOX host is not advancing the transmit window for extended periods of time. This may be indicative of a temporary problem with the host application. An X.25 Reset is sent to reset the transmit and receive windows to allow communication to proceed.","None"
"ALPS","6","UNAVAILABLE","Peer (%i, %s) has entered a congested state.","An ALPS peer connection is experiencing congestion.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALPS","6","UNAVAILABLE","Peer (%i, %s) has exited a congested state.","An ALPS peer connection is no longer experiencing congestion.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALPS","6","UNAVAILABLE","Peer (%i, %s) open failed, rsn = %s","An ALPS peer connection attempted to open, but failed to open.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALPS","7","UNAVAILABLE","Circuit %s has exited a congested state.","An ALPS circuit is no longer experiencing congestion.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALPS","7","UNAVAILABLE","Threshold exceeded for TCP Queue overflow peer drops for peer (%i, %s).","The number of ALPS peer drops due to queue overflow exceeds the ALPS peer threshold value.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALPS","7","UNAVAILABLE","Threshold exceeded for X.25 VC Reset drops for circuit %s","The number of ALPS circuit drops due to X.25 VC Reset exceeds the ALPS circuit threshold value.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALPS","7","UNAVAILABLE","Threshold exceeded for circuit disabled drops for circuit %s","The number of ALPS circuit drops due to circuit disabled exceeds the ALPS circuit threshold value.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALPS","7","UNAVAILABLE","Threshold exceeded for invalid ASCU drops for circuit %s","The number of ALPS circuit drops due to invalid ASCU identifier exceeds the ALPS circuit threshold value.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALPS","7","UNAVAILABLE","Threshold exceeded for lifetime timer expiration drops for circuit %s","The number of ALPS circuit drops due to lifetime timer expiration exceeds the ALPS circuit threshold value.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALPS","7","UNAVAILABLE","Threshold exceeded for maximum size exceeded drops for peer (%i, %s).","The number of ALPS peer drops due to maximum size exceeded exceeds the ALPS peer threshold value.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALPS","7","UNAVAILABLE","Threshold exceeded for peer unreachable peer drops for peer (%i, %s).","The number of ALPS peer drops due to a peer unreachable condition exceeds the ALPS peer threshold value.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALPS","7","UNAVAILABLE","Threshold exceeded for queue overflow drops for circuit %s","The number of ALPS circuit drops due to queue overflow exceeds the ALPS circuit threshold value.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ALPS","7","UNAVAILABLE","Threshold exceeded for version mismatch peer drops for peer (%i, %s).","The number of ALPS peer drops due to version mismatch exceeds the ALPS peer threshold value.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AMDP2_FE","1","UNAVAILABLE","%s CSR%d=0x%04x","The interface could not access system resources for a long time. This problem may occur under very heavy loads.","The system should recover. No action is required. If the message recurs, call your technical support representative for assistance."
"AMDP2_FE","1","UNAVAILABLE","%s CSR%d=0x%04x","The software failed to initialize/restart an Ethernet/Fast Ethernet interface.","Try resetting the interface by doing a shutdown followed by a no shutdown. If the message recurs, try reseating the Port Adaptor. If reseating also does not work call your technical support representative for assistance."
"AMDP2_FE","1","UNAVAILABLE","%s MII transceiver not connected","The MII transceiver was disconnected while the MII port was selected.","Connect the transceiver and enter the shut and no shut commands for the interface in the configuration menu."
"AMDP2_FE","1","UNAVAILABLE","%s, Init failed, CSR%d=0x%04x","The software failed to initialize/restart an Ethernet/Fast Ethernet interface.","Clear the interface. If the message recurs, call your technical support representative for assistance."
"AMDP2_FE","1","UNAVAILABLE","%s, Memory error, CSR%d=0x%04x","The interface could not access system resources for a long time. This problem may occur under very heavy loads.","The system should recover. No action is required. If the message recurs, call your technical support representative for assistance."
"AMDP2_FE","1","UNAVAILABLE","2FE PA not supported on NPE100, shutting down bay","2FE PA is not supported on a 7200 with NPE100.","NPE150 or better is needed for 2FE PA."
"AMDP2_FE","1","UNAVAILABLE","Only found %d interfaces on bay %d, shutting down bay","The software could not identify the interface card.","Power down, reseat the interface card, and reboot. If the message recurs, call your technical support representative for assistance."
"AMDP2_FE","2","UNAVAILABLE","%s hardware does not support ISL","The interface cannot be configured as an ISL trunk.","Check the configuration."
"AMDP2_FE","2","UNAVAILABLE","Interface %s does not support ISL","The interface cannot be configured as an ISL trunk.","Check the configuration."
"AMDP2_FE","3","UNAVAILABLE","%s packet buffer, pak=0x%x","The software detected an error in descriptor ownership.","Try a later version of the software. If the message recurs, call your technical support representative for assistance."
"AMDP2_FE","3","UNAVAILABLE","%s spurious chip init, CSR%d=0x%04x","An illegal condition indicating initialization done has occurred.","Clear the interface. If this message recurs, call your technical support representative for assistance."
"AMDP2_FE","3","UNAVAILABLE","%s transmit error","While transmitting a frame, the controller chip's local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.","The system should recover. No action is required."
"AMDP2_FE","3","UNAVAILABLE","%s, Spurious chip interrupt, CSR%d=0x%04x","An illegal condition indicating initialization done has occurred.","Clear the interface. If this message recurs, call your technical support representative for assistance."
"AMDP2_FE","3","UNAVAILABLE","%s, packet buffer, pak=0x%x","The software detected an error in descriptor ownership.","Try a later version of the software. If the message recurs, call your technical support representative for assistance."
"AMDP2_FE","3","UNAVAILABLE","%s, transmit error","While transmitting a frame, the controller chip's local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.","The system should recover. No action is required."
"AMDP2_FE","3","UNAVAILABLE","Bad packet with %d particles, pak=0x%x","The software detected an invalid packet.","Try a later version of the software. If the message recurs, call your technical support representative for assistance."
"AMDP2_FE","3","UNAVAILABLE","Slot %d device ID seen as %#x, expected %#x","The software could not recognize the interface chips.","Power down, reseat the interface card, and reboot. If the message recurs, call your technical support representative for assistance."
"AMDP2_FE","4","UNAVAILABLE","%s transmit problem, CSR0=%#x","The transmitter has been on the channel longer than the timetaken to transmit the largest frame","The system should recover. No action is required."
"AMDP2_FE","4","UNAVAILABLE","%s, Spurious interrupt error, CSR0=%#x","An illegal condition encountered during initialization.","The system should recover. No action is required."
"AMDP2_FE","4","UNAVAILABLE","%s, transmit problem, CSR0=%#x","The transmitter has been on the channel longer than the time taken to transmit the largest frame.","The system should recover. No action is required."
"AMD79C971_FE","5","UNAVAILABLE","Failed to suspend the amd79c971 chip","Failed to suspend the amd79c971 chip","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AMDP2_FE","5","UNAVAILABLE","%s cable/transceiver problem?","The cable and/or transceiver is not connected.","Connect the cable and/or transceiver."
"AMDP2_FE","5","UNAVAILABLE","%s transmit error","Late collisions occurred on the Ethernet/Fast Ethernet interface.When a collision occurs after the preamble has been transmitted then such a collision is called a LATE collision. The packet will be retransmitted, but this condition could also indicate that another device is failing to detect when the network is in use.","If the interface is Fast Ethernet, verify that both peers are in the same duplex mode. For regular Ethernet, the system should recover. No action is required."
"AMDP2_FE","5","UNAVAILABLE","%s, Excessive collisions, TDR=%d, TRC=%d.","Ethernet/Fast Ethernet is seeing multiple collisions. This may occur under heavy loads.","The system should recover. No action is required."
"AMDP2_FE","5","UNAVAILABLE","%s, lost carrier. cable/transceiver problem?","The cable and/or transceiver is not connected.","Connect the cable and/or transceiver."
"AMDP2_FE","5","UNAVAILABLE","%s, transmit error","Late collisions occurred on the Ethernet/Fast Ethernet interface.","If the interface is Fast Ethernet, verify that both peers are in the same duplex mode. For regular Ethernet, the system should recover. No action is required."
"AMDP2_FE","5","UNAVAILABLE","The Internal Ethernet Interface is not configurable","The internal ethernet is for system use only.","No action is required."
"AMDP2_FE","6","UNAVAILABLE","%s TDR=%d, TRC=%d","Ethernet/Fast Ethernet is seeing multiple collisions. This may occur under heavy loads.","The system should recover. No action is required."
"AP","1","UNAVAILABLE","Distributed DOS attack","This message indicates that the auth-proxy router is possibly under a Distributed DOS attack. It has received more than 512 HTTP connections with no data.","This is a potention DDOS attack."
"AP","1","AUTH_PROXY_DDOS_ATTACK","Distributed DOS attack","This message indicates that the auth-proxy router is possibly under a Distributed DOS attack. It has received more than 512 HTTP connections with no data.","This is a potential DDOS attack."
"AP","1","UNAVAILABLE","IP-address %i has exceeded the maximum retry limit AUDITSESSID=%s","This message indicates that a host has exceeded the maximum allowed limit for login-attempts. The host may be infected by a virus which is continuously sending HTTP requests.","This maybe a potential DOS attack and the source should be shunned. It may also be a false alarm wherein the user is making legitimate attempts to log in."
"AP","1","UNAVAILABLE","POLICY=%s| POLICYNAME=%s| IP=%i| ERROR=| AUDITSESSID=%s","This message indicates that the specified policy was not applied for the given host IP due to the reason specified as Error.","In case of HOST ACL policy verify if an input access list is defined and configured on interface. While for URL REDIRECT ACL policy needs url-redirect VSA to have an assoicated access control list url-redirect-acl VSA, that is used to determine HTTP redirect critera. HTTP packets matching the access control list will be subjected to redirection. In case the 'url-redirect-acl' access control list is not specified or is not configured, the host will not be setup for HTTP redirection."
"AP","1","UNAVAILABLE","Possible DOS attack from source IP-address %i| AUDITSESSID=%s","This message indicates that a host is continuously opening HTTP connections through the auth-proxy without sending data on them. This can potentially be a DOS attack.","This is a potention DOS attack the source should be shunned. It may also be a false alarm wherein a user is connecting to an HTTP server via a telnet like program to port 80."
"AP","4","AUTH_PROXY_NOMEM","Sufficient memory was not available to %s","There was no encuogh memory to perform the specified operation.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"AP","4","POSTURE_EXCEED_MAX_INIT","Exceeded maximum limit (%d) on entires in authentication proxy posture cache in initializing state","This message indicates that the number of entires in authentication proxy posture cache which are in INIT state has exceeded the maximum limit.","This may be a potential Denial of Service attack."
"AP","4","UNAVAILABLE","Exceeded maximum limit (%d) on entires in authentication proxy posture cache in initializing state","This message indicates that the number of entires in authentication proxy posture cache which are in INIT state has exceeded the maximum limit.","This may be a potential Denial of Service attack."
"AP","4","UNAVAILABLE","Sufficient memory was not available to %s","There was no encuogh memory to perform the specified operation.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"AP","5","UNAVAILABLE","Event=AAA %s. HOST=%i| POLICY %s=%s.| AUDITSESSID=%s","This messages notifies that AAA servers defined by the methodlist are unreachable for the given host and the policy being applied.","The failure is due to unreachable AAA servers."
"AP","6","POSTURE_DOWNLOAD_ACL","Send AAA request to download (%s) named access control list","This message indicates the router has send a request to AAA to get the contents of the specified downloadable access contol list.","This is an informational message and no action is required"
"AP","6","POSTURE_POLICY","%s %s (%s) policy for host (%i)","This message specifies the policy enforced or removed for the specified host. The policy could be either an access control list or a URL to which any intercepted HTTP traffic would be redirected.","This is an informational message and no action is required"
"AP","6","POSTURE_START_VALIDATION","IP=%i| Interface=%s| AUDITSESSID=%s","This message indicates the router has created an entry for the host in authentication porxy posture cache and has initiated posture validation process.","This is an informational message and no action is required"
"AP","6","UNAVAILABLE","%s %s (%s) policy for host (%i)","This message specifies the policy enforced or removed for the specified host. The policy could be either an access control list or a URL to which any intercepted HTTP traffic would be redirected.","This is an informational message and no action is required"
"AP","6","UNAVAILABLE","IP=%i| Interface=%s| AUDITSESSID=%s","This message indicates the router has created an entry for the host in authentication porxy posture cache and has initiated posture validation process.","This is an informational message and no action is required"
"AP","6","UNAVAILABLE","IP=%i| MAC=%u| PROFILE_NAME=%s| EVENT=%s| AUDITSESSID=%s","This message indicates a fallback to authproxy has been initiated/terminated for the given host.","No action required"
"AP","6","UNAVAILABLE","IP=%i| STATE=%s| AUDITSESSID=%s","This message indicates the change of posture validation state of the specified host in the authentication proxy posture validation cache.","This is an informational message and no action is required"
"AP","6","UNAVAILABLE","Send AAA request to download (%s) named access control list","This message indicates the router has send a request to AAA to get the contents of the specified downloadable access contol list.","This is an informational message and no action is required"
"AP","6","UNAVAILABLE","initiator (%i) send %u packets %u bytes; duration time %s| AUDITSESSID=%s","This message documents the transaction log of network activities of auth-proxy. The message is issued at the stop of each auth-proxy cache and it records the source addresses, the number of bytes transmitted by the client, and the cache duration time.","This message is for informational purposed only, and can be used to collect the basic accounting for the proxyied caches."
"AP","6","UNAVAILABLE","initiator (%i) start| AUDITSESSID=%s","This message documents the transaction log of network activities of auth-proxy. The message is issued at the start of each auth-proxy cache and it records the source addresses.","This message is for informational purposed only, and can be used to collect the basic accounting for the proxyied sessions."
"APS","1","UNAVAILABLE","No Active Port In Group %s","After an active interface failure, the system switches over to the standby interface if APS has been enabled. This message is posted if after a switchover the system finds no active interface, i.e. both working and protection interfaces are found to be nonoperational.","Isolate the cause of failure on both working and protection interfaces."
"APS","2","UNAVAILABLE","%s %d","APS software detected an internal error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"APS","2","UNAVAILABLE","%s","A software error occurred during initialization of the APS subsystem","Check for sufficient processor memory. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"APS","2","UNAVAILABLE","Group %s: Channel Config Mismatch","Working and Protection interfaces do not point to the same path on local and remote network elements","Configure working and protection interfaces to point to the same path on local and remote network elements"
"APS","2","UNAVAILABLE","Group %s: Channel Mismatch - %s","This message is posted by the local network element, if the received bridged channel number (in the REVERSE-REQUEST from the remote network element) does not match the request channel number in the APS request sent by the local network element. This message is relevant only for bidirectional operation. For 1+1 APS, this message should normally be not posted unless a) the transmit bridged channel number in the REVERSE-REQUEST from remote is somehow corrupted or b) there is a bug in the APS software itself.","Check for any failures on the APS commnication channel. If APS communication channel is operational, contact Cisco TAC."
"APS","2","UNAVAILABLE","Group %s: Far End Prot Failure - %s","This message is posted by the local network element if it detects a Far End Protection Failure condition. The Far End Protection Failure condition is detected if the Far End Protection Defect count exceeds a threshold. A Far End Protection Defect is detected when the local network element receives a remote APS message with request set to SF (Signal Fail) and request channel set to 0 (NULL or Protection channel).","Isolate the cause of failure on the protection channel on the remote network element."
"APS","2","UNAVAILABLE","Group %s: Mode Mismatch - %s","This message is posted by the local network element if the local APS group has been configured for bidirectional operation but the associated remote APS group has been configured for unidirectional operation. This message indicates that a mismatch in mode (unidirectional or bidirectional) has been detected.","Configure the remote APS group for bidirectional operation."
"APS","2","UNAVAILABLE","Group %s: Prot Switch Byte Failure - %s","This message is posted by the local network element if a Protection Switch Byte Failure is detected. A Protection Switch Byte Failure is detected when the Protection Switch Byte defect count exceeds a threshold. A Protection Switch Byte Defect is detected when one of the following happens: 1) The remote APS request is not one of the supported requests. 2) The remote APS request channel number is invalid. For 1+1 APS, the channel number must be 0 or 1. 3) Operation is bidirectional and neither local nor remote network element is sending a REVERSE-REQUEST, and the remote APS request is of lower priority than the local APS request. 4) Operation is bidirectional and the sequence number in the remote APS REVERSE-REQUEST does not match the sequence number of the most recent APS request sent by the local network element. This error is posted if a) the APS request is somehow corrupted, or b) there is a bug in the APS software itself or c) if the APS communication between two network elements is broken, e.g. local network element can send and receive, whereas the remote network element can send but not receive.","Check for failures on the APS communication channel. Isolate the cause for such failures and restore the communication channel to working condition."
"APS","3","UNAVAILABLE","%s Port Fail On %s","This message is posted when APS subsystem receives a port fail indication from the driver subsystem. This message indicates that the specified interface has detected a failure condition (e.g. Loss Of Light).","Isolate the cause of the failure and restore the interface to normal operational condition."
"APS","6","UNAVAILABLE","Auto-Failover - Group %s","This message is posted if APS hardware successfully switched over to the standby interface after the failure of the active interface. This is informational only.","Isolate the cause of failure of the previous active interface and restore it to a working condition."
"APS","6","UNAVAILABLE","Disable Auto-Failover On %s","APS has disabled auto-failover for the indicated group","Show aps group."
"APS","6","UNAVAILABLE","Enable Auto-Failover On %s","This message is posted when APS software enables hardware to perform APS actions for failures detected by the hardware. This is informational only.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"APS","6","UNAVAILABLE","Group %s - %s channel is now ACTIVE","This message is posted when a previously standby channel becomes the active channel. This is informational only.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"APS","6","UNAVAILABLE","Group %s: Mode Mismatch - %s","This message is posted by the local network element if the local APS group has been configured for bidirectional operation but the associated remote APS group has been configured for unidirectional operation. This message is posted after the local network element detects the mismatch and changes the operation to unidirectional.","Configure the remote APS group for bidirectional operation."
"APS","6","UNAVAILABLE","Group %s: Remote Request - %s","This message is posted by the local network element after an APS switchover that is triggered by an APS request from the remote network element. This is informational only.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ARAP","0","UNAVAILABLE","TTY %d","An internal software error occured.","Report this error to your technical support representative."
"ARAP","0","UNAVAILABLE","TTY %d","An internal software error occured.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ARAP","0","UNAVAILABLE","TTY %d: VS queued error","An internal software error occured.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ARAP","0","UNAVAILABLE","TTY %d: arg msg bad %x","The router received an invalid packet during ARAP MNP4 connection setup phase.","Check for excessive line noise. Check the ARAP client software configuration for possible problems."
"ARAP","2","UNAVAILABLE","TTY %d: Could not malloc log","Memory not available for internal MNP4 logging.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ARAP","3","UNAVAILABLE","TTY %d: Bad packet type in arap_send_msg","Internal data structures are corrupted.","Check for abnormally high CPU usage."
"ARAP","3","UNAVAILABLE","TTY %d: arap callback aborted","An unexpected message was received during the Microcom Networking Protocol version 4 (MNP4) link setup.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ARAP","3","UNAVAILABLE","TTY %d: arap expected message timeout","The software timed out during the MNP4 link setup.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ARAP","3","UNAVAILABLE","TTY %d: arap input error","ARAP connection was terminated without a known cause.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ARAP","3","UNAVAILABLE","TTY %d: unhandled configuration command","A configuration command was not recognized.","Check the configuration file on the server for any invalid configuration commands."
"ARAP","4","UNAVAILABLE","TTY %d: ARAP connection failed: %s","The ARA protocol client was denied access, probably due to a configuration problem on the server. The error message should indicate the problem. This message does not indicate access denials due to bad passwords.","Investigate the problem reported in the error message."
"ARAP","4","UNAVAILABLE","TTY %d: arap TACACS is configured but extended TACACS is not.","Terminal Access Controller Access Control System (TACACS) authentication failed because extended TACACS is not configured.","Configure extended TACACS."
"ARAP","5","UNAVAILABLE","TTY %d: ARAP invalid packet received","A corrupted packet reached the ARA protocol code.","Check for excessive CPU usage or excessive line noise."
"ARAP","5","UNAVAILABLE","TTY %d: ARAP unexpected initialization packet %s","The startup negotiation between a client and the ARA protocol server fell out of order. If this message is received sporadically, it indicates line noise.","If this message recurs, reinstall the ARA client software."
"ARAP","6","UNAVAILABLE","TTY %d","The router repeated resending of MNP4 packets as the Macintosh client failed to acknowledge previously resent packets.","If this error message persists for several ARAP connections report it to your technical support representative."
"ARAP","6","UNAVAILABLE","TTY %d","The router resent MNP4 packets maximum number of times without receiving an acknowledgement.","To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports."
"ARAP","6","UNAVAILABLE","TTY %d: ARAP ended for user %s; address %A; %d seconds connected","This message appears only when ARA protocol logging is configured. The message notes that an ARA protocol user has logged out.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ARAP","6","UNAVAILABLE","TTY %d: ARAP started for user %s; address %d.%d","This message appears only when ARA protocol logging is configured. The message notes that an ARA protocol user has logged in.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ARAP","6","UNAVAILABLE","TTY %d: MNP4 input disconnect","This indicates that the router received disconnect request from the remote Macintosh client.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ARAP","6","UNAVAILABLE","TTY %d: MNP4 timeout error","The router is dropping the connection after doing maximum resends.","To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports."
"ARAP","6","UNAVAILABLE","TTY %d: Rcv giant. dropping frame","The router received an oversized MNP4 frame.","Check for excessive line noise. Check the ARAP client software configuration for possible problems."
"ARAP","6","UNAVAILABLE","TTY %d: Receive getbuffer failure. dropping frame","No buffer exists for an incoming packet.","Examine buffer usage statistics. Possibly more memory is required."
"ARAP","6","UNAVAILABLE","TTY %d: Received LT in CONNECTION PHASE","The router received an invalid packet during ARA connection setup phase.","Check for excessive line noise. Check the ARAP client software configuration for possible problems."
"ARAP","6","UNAVAILABLE","TTY %d: T401 %d baud rate %d","This message indicates that the router received MNP4 connection request. MNP4 acknowledgement timer value is also indicated.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ARAP","6","UNAVAILABLE","TTY %d: exited user %s: %s","A user was disconnected from ARA protocol at an unexpected time. The disconnection may be due to modems dropping, server error, client problems, or any number of other difficulties.","To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports."
"ARAP","6","UNAVAILABLE","TTY %d: exited user %s: Other side stopped answering ARAP tickles (mnp4 pak resent %d mnp4 pak sent %d last %d now %d)","The router disconnected as the remote Macintosh client stopped sending ARAP tickle or data packets.","To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports."
"ARCHIVE_CONFIG","4","UNAVAILABLE","Archive of router configuration was skipped due to a previous initiation.","Only one archive can be created at a time. Two or more simultaneous archives in progress is not allowed. This could occur for example if two users attempt to create an archive simultaneouly.","Retry the archive creation later, when the previous archive has finished being written."
"ARCHIVE_CONFIG","4","UNAVAILABLE","Delete of a previously saved archive of the router configuration could not be completed.","The router could not delete a file that was previously written. The file that was being deleted file contains an archive of the router configuration. This could occur for example if the file was manually deleted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ARCHIVE_CONFIG","6","UNAVAILABLE","Could not create an archive of the router configuration on the standby RP.","The router could not create an archive file on the standby RP. The file that was being created contains an archive of the router configuration. This could occur for example if the active RP cannot communicate with the standby RP.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ARCHIVE_CONFIG","6","UNAVAILABLE","Delete of a previously saved archive of the router configuration could not be completed on the standby RP.","The router could not delete a file that was previously written on the standby RP. The file that was being deleted file contains an archive of the router configuration. This could occur for example if the file was manually deleted. Alternatively, the file could not be deleted when the active RP cannot communicate with the standby RP.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ARCHIVE_DIFF","3","UNAVAILABLE","Could not initialize the Config Diff and Rollback subsystem","An internal software error occurred during initialization. Config Diff and Rollback cannot be used as a result of this error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ARCHIVE_DIFF","3","UNAVAILABLE","Failed to register the special case %s command:%s during initialization. Config Diff and Rollback cannot be used as a result of this error.","An internal software error occurred during initialization - Config Diff and Rollback cannot be used as a result of this error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ARCHIVE_DIFF","5","UNAVAILABLE","Backing up current running config to %s","The current running config is saved so that when the timer expires, if no confirmation has been received from user to confirm what they've configured, the system will rollback to the saved config.","This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change."
"ARCHIVE_DIFF","5","UNAVAILABLE","Failed to acquire configuration lock. Rollback did not start. Schedule to retry in 5 minutes","Failed to acquire configuration lock. Rollback did not start. In this case retry will be scheduled.","This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change."
"ARCHIVE_DIFF","5","UNAVAILABLE","Start rolling to: %s","The timer for Rollback Confirmed Change has expired. System will rollback to the previously saved config.","This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change."
"ARCHIVE_DIFF","5","UNAVAILABLE","System will rollback to config %s in one minute. Enter configure confirm if you wish to keep what you've configured","Rollback will start in one minute. User could enter configure confirm if they wish to keep what they've configured.","This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change."
"ARCHIVE_DIFF","5","UNAVAILABLE","User %s on tty %d has been idle for %lu minutes. System will rollback to config %s in oneminute if it continues to be idle. Enter configure confirm if you wish to keep what you've configured","Rollback will start in one minute. User could enter configure confirm if they wish to keep what they've configured.","This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change."
"ARCHIVE_DIFF","5","UNAVAILABLE","User: %s Reset Rollback Confirmed Change timer(idle) to %lu minute","Reset Rollback Confirmed Change timer(idle) to a new value","This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change."
"ARCHIVE_DIFF","5","UNAVAILABLE","User: %s: Confirm the configuration change","The configuration change is confirmed. The timer for rolling to the previously saved config is cancelled","This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change."
"ARCHIVE_DIFF","5","UNAVAILABLE","User: %s: Reset Rollback Confirmed Change timer(absolute) to %lu minute","Reset Rollback Confirmed Change timer(absolute) to a new value","This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change."
"ARCHIVE_DIFF","5","UNAVAILABLE","User: %s: Rollback Confirmed Change is cancelled due to %s failure","Rollback Confirmed Change is normally configured along with other configuration operations, such as config term or config replace. If those operation failed, Rollback Confirmed Change should not be activated.","Remove the error condition and try again later."
"ARCHIVE_DIFF","5","UNAVAILABLE","User: %s: Rollback immediately.","Rollback immediately and cancel the timer","This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change."
"ARCHIVE_DIFF","5","UNAVAILABLE","User: %s: Scheduled to rollback to config %s if session has been idle for %lu minutes","The system will wait for the user to confirm that they wish to keep what they've configured until the timer expires. If the confirmation is not received in time, the router will rollback.","This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change."
"ARCHIVE_DIFF","5","UNAVAILABLE","User: %s: Scheduled to rollback to config %s in %lu minutes","The system will wait for the user to confirm that they wish to keep what they've configured until the timer expires. If the confirmation is not received in time, the router will rollback.","This message DOES NOT denote any error condition. It is a part of the normal operation of the rollback confirmed change."
"ARCHIVE_ISSU","2","UNAVAILABLE","Archive ISSU client failed to get buffer for message. Error: %d (%s)","The Archive ISSU client failed to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","Show logging and show checkpoint client. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ARCHIVE_ISSU","2","UNAVAILABLE","Archive ISSU client failed to register session information. Error: %d (%s)","The Archive ISSU client failed to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly.","Show issu capability entries, issu session and show issu negotiated capability. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ARCHIVE_ISSU","2","UNAVAILABLE","Archive ISSU client failed to send negotiation message. Error: %d (%s)","The Archive ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","Show logging and show checkpoint client. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ARCHIVE_ISSU","2","UNAVAILABLE","Archive ISSU client initialization failed to %s. Error: %d (%s)","The Archive ISSU client could not be initialized. This initialization failure must be addressed before in-service software upgrade or downgrade can be performed successfully. If you do not address this failure, there will be downtime during software upgrade or downgrade.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ARCHIVE_ISSU","2","UNAVAILABLE","Failed to start Archive ISSU session negotiation. Error: %d (%s)","The Archive ISSU client failed to start session negotition.If a problem occurs with the ISSU session start, the standby device cannot be brought up properly.","Show issu session and show issu negotiated version. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ARCHIVE_ISSU","3","UNAVAILABLE","Archive ISSU client %s transform failed for 'Message Type %d'. Error: %d (%s)","The Archive ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In both cases, the Archive state between the active device and the standby device is not identical.","Show issu session and show issu negotiated version. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ARCHIVE_ISSU","3","UNAVAILABLE","Archive ISSU client 'Message Type %d' is not compatible","The Archive ISSU client received an incompatible message from the peer device. The message cannot be processed.","Show issu session and show issu negotiated version. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ARCHIVE_ISSU","3","UNAVAILABLE","Archive ISSU client does not have a valid registered session.","The Archive ISSU client does not have a valid registered session.","Show issu capability entries, issu session and show issu negotiated capability. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ARCHIVE_ISSU","3","UNAVAILABLE","Archive ISSU client failed to get the MTU for Message Type %d.Error: %d (%s)","The Archive ISSU client failed to calculate the MTU for the specified message. The Archive ISSU client is not able to send the message to the standby device.","Show issu session and show issu negotiated version. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ARCHIVE_ISSU","3","UNAVAILABLE","Archive ISSU client failed to unregister session information. Error: %d (%s)","The Archive ISSU client failed to unregister session information.","Show issu session and show issu negotiated version. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AS5400","0","UNAVAILABLE","12.2 mainline images are not compatible with the AS5400HPX system.","12.2 mainline images are not compatible with the AS5400HPX system.","Load an image compatible with the system."
"AS5400","1","UNAVAILABLE","DFC %d: Detected PCI %s Error, CSR=0x%x","PCI error is detected on the DFC. This is due to hardware failure. IOS will powerdown this DFC and cleanup the system datastructures associated with it.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AS5400","1","UNAVAILABLE","%s","The specified component should have the latest HW revision. If the hw revision is not the latest, then it needs to be updated to the printed out version.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AS5400","1","UNAVAILABLE","Unknown DFC interrupt: DFC slot no %d, interrupt %d","Unknown DFC interrupt is detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AS5400","1","UNAVAILABLE","Unknown interrupt: interrupt %d","System detected an unknown interrupt.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AS5400","3","UNAVAILABLE","NULL","DFC hardware error is detected. IOS will powerdown this DFC and cleanup the system datastructures associated with it.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AS5400_ENVM","1","UNAVAILABLE","A DFC is powered down due to board over-temperature. Slot: %d, Type: %s","The System experienced an over-temperature condition.","For AS5400, a DFC is powered down to prevent the DFC from damaging and to cool down the temperature. Check air conditioning and the surrounding of the AS5400 box. A customer should type 'show environment' to display temperature data and compare with temperature meter. If really fails, call Cisco to replace the temperature sensor"
"AS5400_ENVM","1","UNAVAILABLE","A DFC is powered on due to board temperature cooling down. Slot: %d, Type: %s","The temperature in the system cools down.","For AS5400, when the board temperature cools down, a DFC is powered on, back to work. A customer should type 'show environment' to display temperature data and compare with temperature meter to verify the recovery."
"AS5400_ENVM","1","UNAVAILABLE","All DFCs are busy out due to board over temperature.","The System experienced an Over Temperature condition.","For AS5400, all DFCs are busy out to prevent the DFCs from damaging and to cool down the temperature. Check air conditioning and the surrounding of the AS5400 box. A customer should type 'show environment' to display temperature data and compare with temperature meter. If really fails, call Cisco to replace the temperature sensor"
"AS5400_ENVM","1","UNAVAILABLE","All DFCs are unbusy out due to board temperature cooling down.","The System experienced an over-temperature condition.","For AS5400, when the board temperature cools down, all DFCs are unbusy out, back to work. A customer should type 'show environment' to display temperature data and compare with temperature meter to verify the recovery."
"AS5400_ENVM","1","UNAVAILABLE","Can't power on DFC on slot %d for unknown reason.","Powering on a DFC failed.","Check the power plug to the DFC on the slot. If still fail, unplug the DFC and do diagnostic on it."
"AS5400_ENVM","1","UNAVAILABLE","Environmental Monitor of Fans is dropped.","If a temperature sensor at inlet or outlet fails to work, the environmental monitoring of fans is dropped.","For AS5400, once the fan monitoring is dropped, only console message is sent out and alarm is activated. A customer should type 'show environment' to display temperature data and compare with temperature meter. If really fails, call Cisco to replace the temperature sensor"
"AS5400_ENVM","1","UNAVAILABLE","Environmental Monitor of Fans is recovered.","If temperature sensors at both inlet or outlet recovers to work, the environmental monitoring of fans is recovered.","For AS5400, once the fan monitoring is recovered, console message is sent out and alarm is disabled. Fan state is set as normal. A customer should type 'show environment' to display temperature data and compare with temperature meter to verify the recovery."
"AS5400_ENVM","1","UNAVAILABLE","Environmental Monitor of Temperature is dropped.","If all temperature sensors fail to work, the environmental monitoring of temperature is dropped.","For AS5400, once the temperature monitoring is dropped, only console message is sent out and alarm is activated. A customer should type 'show environment' to display temperature data and compare with temperature meter. If really fails, call Cisco to replace the temperature sensor"
"AS5400_ENVM","1","UNAVAILABLE","Environmental Monitor of Temperature is recovered.","If a temperature sensor recovers to work, the environmental monitoring of temperature is recovered.","For AS5400, once the temperature monitoring is recovered, console message is sent out and alarm is disabled. temperature state is set as normal. A customer should type 'show environment' to display temperature data and compare with temperature meter to verify the recovery."
"AS5400_ENVM","1","UNAVAILABLE","Environmental monitor is trying to power down a DFC by simulating OIR removal. Slot: %d, Type: %s","The System experienced an over-temperature condition. For AS5400, a DFC is powered down to prevent the DFC from damaging and to cool down the temperature. The environmental monitor apply the scheme of OIR removal to power down the DFC.","Make sure that the room temperature is not too high and that air flow to the card is not blocked. Check air conditioning and the surrounding of the AS5400 box."
"AS5400_ENVM","1","UNAVAILABLE","Environmental monitor is trying to power on a DFC by simulating OIR insertion. Slot: %d, Type: %s","The temperature cools down inside the chassis. For AS5400, when the board temperature cools down, a DFC is powered on, back to work. The environmental monitor apply the scheme of OIR insertion to power on the DFC.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AS5400_ENVM","1","UNAVAILABLE","System detected that temperature is in %s condition.","The environmental monitor detected a temperature change, either failure or recovery.","Make sure that the room temperature is not too high and that air flow to the card is not blocked. If this condition persists, the environmental monitor might shut down the system. Check air conditioning and the surrounding of the AS5400 box. Call your technical support representative for assistance, if necessary."
"AS5400_ENVM","1","UNAVAILABLE","Temperature sensor #%d fails to work.","The health of each temperature sensor itself is also monitored. There are three cases that we consider a sensor fails to operate normally: 1. a sensor generates extraordinary data, such as higher than 200 degree C; 2. temperature change exceeds limits in one minute, such as 25 degree C; 3. temperature differential between sensors in the same box is greater than limit, such as 25 degrees C.","For AS5400, once the failure of a temperature sensor is detected, ENVMON will set the temperature state of that sensor as disabled, send out console message. The temperature data from that sensor is ignored in temperature monitoring. A customer should type 'show environment' to display temperature data and compare with temperature meter. If really fails, call Cisco to replace the temperature sensor"
"AS5400_ENVM","1","UNAVAILABLE","Temperature sensor #%d recovers to work.","The health of each temperature sensor itself is also monitored. There are three cases that we consider these sensors fail to operate normally: 1. a sensor generates extraordinary data, such as higher than 200 degree C; 2. temperature change exceeds limits in one minute, such as 25 degree C; 3. temperature differential between sensors is greater than limit, such as 25 degrees C.","For AS5400, once the recovery of a temperature sensor is detected, ENVMON will set the senor_state of that sensor as normal, send out console message. The temperature data from that sensor is read again in temperature monitoring. A customer should type 'show environment' to display temperature data and compare with temperature meter to verify the recovery."
"AS5400_ENVM","3","UNAVAILABLE","%s fail to work.","Some cooling fans fail to work. This is detected by the temperature delta between the inlet and outlet. A big delta indicates fan failure.","Replace the fan as soon as possible or the system may shut itself down or fail to operate properly."
"AS5400_ENVM","3","UNAVAILABLE","%s recovered to work.","Some cooling fans recover to work. This is detected by the temperature delta between the inlet and outlet. A small delta indicates fan recovery.","Verify the fan work properly by checking the 4 fans and a customer should type 'show environment' to display temperature delta data and verify the recovery."
"AS5400_ENVM","3","UNAVAILABLE","AS5400 Environmental Monitor is disabled.","A configuration command can disable AS5400 environmental monitor when a user doesn't need it in certain special situations.","For AS5400, once the ENVMON is disabled, both console message and a SNMP trap are sent out. No further action."
"AS5400_ENVM","3","UNAVAILABLE","AS5400 Environmental Monitor is enabled.","A configuration command can enable AS5400 environmental monitor after it was disabled in certain special situations.","For AS5400, once the ENVMON is enabled, both console message and a SNMP trap are sent out, and all ENVMON actions will be taken if necessary."
"ASPP","3","UNAVAILABLE","%s: Unable to set Rx/Tx tty async service hooks.","This message occurs only when ASP is configured. It indicates the serial interface using ASP is configured incorrectly or does not support asynchronous mode.","Verify the correct hardware interface type is being used."
"ASPP","3","UNAVAILABLE","%s: Unable to set Rx/Tx tty async service hooks.","This message occurs only when ASP is configured. It indicates the serial interface using ASP is configured incorrectly or does not support asynchronous mode.","Verify the correct hardware interface type is being used."
"AT","1","UNAVAILABLE","Could not allocate memory for %s at line %d in %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","2","UNAVAILABLE","AppleTalk assertion failed: %s","The software detected an inconsistency. Although this error is serious, the router attempts to continue. AppleTalk processing might be impaired.","Copy the message exactly as it appears, note any AppleTalk problems you experience, and call your technical support representative."
"AT","3","UNAVAILABLE","%s: AURP connection out of sync...terminating","AURP detected packets that were out of sequence. This might be caused by a lost connection.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","3","UNAVAILABLE","%s: AppleTalk interface disabled; conflicts with interface %s","An attempt was made to configure an interface to have the same or a conflicting AppleTalk address or cable range as another interface on the same router.","Verify that you are not specifying an AppleTalk address or cable range used previously on this router, and reconfigure the interface."
"AT","3","UNAVAILABLE","%s: AppleTalk interface disabled; network incompatible with %#a","The interface was disabled because the configured AppleTalk address or cable range for the interface conflicts with that of another router on the attached network.","Reconfigure the affected routers so that there are no conflicting addresses or cable ranges on the attached network."
"AT","3","UNAVAILABLE","%s: AppleTalk interface disabled; zone list incompatible with %#a","The zone list of the configured interface is inconsistent with the zone list of other routers.","Reconfigure the zone list on the router so that it does not conflict with that the zoen lists on other routers."
"AT","3","UNAVAILABLE","%s: AppleTalk interface warning; default zone differs from %#a","During the verification startup process, there was a disagreement between the default zone (the first zone defined after the appletalk cable-range command) and the router that confirmed the configuration. When an AppleTalk end node is first connected to a network, it joins the default zone until it is overridden.","Use the appletalk zone command to correct the configuration so that all routers are advertising the same default zone. Note that several router implementations are known to mismanage the default zone."
"AT","3","UNAVAILABLE","%s: AppleTalk interface warning; zone multicast %e differs from our multicast %e","A computed multicast address disagrees with that provided by another AppleTalk router. The other AppleTalk router might be misconfigured or faulty.","Correct the problem at the other router."
"AT","3","UNAVAILABLE","%s: AppleTalk node down; no addresses available","No free node could be found on the interface.","If your AppleTalk network has less than 250 nodes, issue the debug appletalk errors command and then call your technical support representative. If your AppleTalk network has more than 250 nodes, split it into smaller networks by creating new segments and moving some nodes into the new segments."
"AT","3","UNAVAILABLE","%s: AppleTalk node warning; discovery mode disabled","A hardware or software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","3","UNAVAILABLE","%s: AppleTalk packet error; no source address available","The router could not generate an AppleTalk packet because no valid AppleTalk source address was available to identify this router in the packet.","Configure an interface to have an address or cable range. Use the show appletalk command to verify that the interface is operational."
"AT","3","UNAVAILABLE","%s: client tried to connect, but no virtual network is declared","A hardware or software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"AT","3","UNAVAILABLE","%s: client tried to open socket, but failed","open socket failed;Possible out of memory situationError Message    %AT-3-UNAVAILABLE: AppleTalk error: %s Explanation    An internal error occurred. Specifically, a programming assertion in the AppleTalk networking code was violated.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","3","UNAVAILABLE","AppleTalk not running","You tried to show or change the AppleTalk configuration when AppleTalk routing was not turned on.","Issue the appletalk routing command before issuing any other AppleTalk configuration or display command."
"AT","3","UNAVAILABLE","Cannot delete %s route %d by clearing; remove it by reconfiguring","You attempted to remove a route from the routing table by issuing the clear appletalk route command. The command failed because the route was on a directly connected interface, that is, it was created when you configured the router.","Remove the route by reconfiguring the directly connected interface with which it is associated."
"AT","3","UNAVAILABLE","Could not compute best path for network %#A","A path to the specified network could not be found.","Use the show appletalk route command to verify that a path to the specified network exists. If it does, copy the error message exactly as it appears, and report it along with the output of the show appletalk route command to your technical support representative."
"AT","3","UNAVAILABLE","Invalid NBPtest command %s","An unrecognized command was specified in the Name Binding Protocol (NBP) test facility.","Enter a valid command."
"AT","3","UNAVAILABLE","Loop detected on domain %d [%s]","The domain router detected a routing loop. Routing loops are not allowed. The domain router runs a background loop detection process. The domain router starts this process when it receives a new zone list from a domain that is identical to the list in the main routing table and whose network range length matches that in this list. The loop detection process sends several AppleTalk NBP loopback packets. When one of these packets is received on an interface that does not belong to the original domain, the domain router first shuts off all the domains involved in the loop, and then shuts off all the interfaces in these domains. The loop detection does not catch all types of loops. It is your responsibility to make sure that no loop exists.","Disable the cause of the routing loop. Then use the clear appletalk command to restart the interfaces involved."
"AT","3","UNAVAILABLE","No route to destination %a","The router could not deliver a packet to a destination because it did not know where to send it.","Use the show appletalk route command to verify that a path to the destination exists. If it does, copy the error message exactly as it appears, and report it with the output of the show appletalk route command to your technical support representative."
"AT","3","UNAVAILABLE","No such neighbor, %#a","You specified a nonexistent neighbor address in a show appletalk neighbor or clear appletalk neighbor.","Specify a valid neighbor address, that is, one that appears in the output of the show appletalk neighbor command."
"AT","3","UNAVAILABLE","Remap range overflow for %s domain %d","The remap range overflowed. If a network (range) cannot fit inside the remapping range, the network or cable range being advertised by a neighboring router is not accepted. When an overflow occurs, all interfaces in the domain are disabled.","Use the appletalk domain remap-range command to increase the remapping range. Then restart the interfaces."
"AT","4","UNAVAILABLE","%s: AppleTalk node down; conflicts with active internet","The configuration specified for the interface conflicts with the active AppleTalk internetwork. For example, a cable range might be configured that overlaps an existing route but does not match the entry exactly.","Use the appletalk cable-range command to reconfigure the interface so that there are no conflicts with the existing AppleTalk rnetwork, or take any other actions necessary to resolve the conflict. AppleTalk will periodically attempt to restart the interface."
"AT","4","UNAVAILABLE","%s: MacIP inoperable IP interface, %i","If the appletalk event-logging command is configured, this message appears on the console when a MacIP server can no longer operate due to a change in the condition of the IP interface it serves. This condition can occur if IP routing is shut down on the interface, or the IP address of the interface is changed so that the MacIP server's IP address is no longer valid on the same cable. The AppleTalk zone served by the MacIP server replaces the zone specified in the appletalk zone command. The IP address configured on the MacIP server replaces the IP address configured by the ip address command.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","4","UNAVAILABLE","%s: MacIP inoperable configuration, %i","If the appletalk event-logging command is configured, this message appears on the console when a MacIP server cannot begin or recover operations because of an invalid IP address configuration. This condition only occurs when the configured MacIP server's IP address is not valid on the same cable of any operable IP interface. The AppleTalk zone served by the MacIP server replaces the zone specified in the appletalk zone command. The IP address configured on the MacIP server replaces the IP address configured by the ip address command. When this error occurs, the MacIP configuration is considered invalid and is deleted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","4","UNAVAILABLE","AURP path %#A rejected; conflict detected","The router detected a conflicting cable range. A router is configured with a cable range that overlaps with an existing range but does not match the entry exactly.","Use the show appletalk command to identify the overlapped cable range, and then reconfigure the misconfigured router."
"AT","5","UNAVAILABLE","%s: AppleTalk interface restarting; interface cleared","A clear interface command was issued on an interface that is currently routing AppleTalk.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","5","UNAVAILABLE","%s: AppleTalk interface restarting; node address taken by %e","Another AppleTalk node on a common network interface claimed the same AppleTalk address that this router was using. This error indicates a serious, unexpected problem. If it recurs, a physical network problem in which the nodes cannot communicate with each other might exist.","The interface on this router restarts AppleTalk processing on the common network interface to resolve the address conflict.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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","5","UNAVAILABLE","%s: AppleTalk interface restarting; protocol restarted","The hardware interface was reset because of a configuration change. After the reset, AppleTalk automatically reinitialized the interface.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","5","UNAVAILABLE","%s: AppleTalk internet compatibility mode required by %#a","A neighboring router supports only extended AppleTalk networks with a cable range of 1 and with one assigned zone, for example, 25-25.","Upgrade the routers that support only the original AppleTalk specification. In the meantime, observe the compatibility rules for AppleTalk Phase 1 and Phase 2 routers."
"AT","5","UNAVAILABLE","%s: AppleTalk neighbor down; lost contact with %#a","A peer router is unreachable.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","5","UNAVAILABLE","%s: AppleTalk neighbor ignored; %#a is misconfigured","A neighboring router's AppleTalk configuration does not agree with this router's AppleTalk configuration. This condition can result from a mismatch between the neighbor's network range and this router's network range.","Modify either this router's or the neighboring router's configuration so that the network ranges agree."
"AT","5","UNAVAILABLE","%s: AppleTalk node down; line protocol down","An AppleTalk hardware interface was disabled because of a bad serial line, a configuration command, or a bad interface.","If the interface was not intentionally disabled, this message indicates a hardware problem. In this case, repair or replace the applicable hardware."
"AT","5","UNAVAILABLE","%s: AppleTalk node down; line protocol not supported","An encapsulation method on the specified interface does not support AppleTalk.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","5","UNAVAILABLE","%s: AppleTalk node warning; address %A already in use","The initial hint address was in use. A search will be made for a valid address.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","5","UNAVAILABLE","%s: AppleTalk node warning; address %A is invalid","The hint address specified for the interface was not valid for the current configuration.","The hint address is ignored and a random valid hint address is automatically computed. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","5","UNAVAILABLE","%s: AppleTalk route cache disabled; firmware is obsolete","The firmware on the MCI controller card does not support AppleTalk fast switching.","No corrective action is required. Normal AppleTalk operation continues, but the fast switching cache is disabled for the interface associated with the MCI card. If this message is unexpected, verify that the MCI firmware for the interface specified in the error message is at level 1.7 or higher."
"AT","5","UNAVAILABLE","%s: RTMP path to %#A via %#a now in %s state (metric %d, %d hops)","The state of a path changed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","5","UNAVAILABLE","AppleTalk FDDI neighbor %#a using obsolete FDDI addressing","Another AppleTalk router on the FDDI ring is running a release of the router software earlier than 9.0(2). Routers running these early software releases use an encapsulation for AppleTalk on FDDI rings that is not compatible with the Apple FDDITalk implementation.","Upgrade the routers running the software releases that use the pre-FDDITalk encapsulation for AppleTalk on FDDI rings."
"AT","5","UNAVAILABLE","AppleTalk neighbor incompatibility; %#A has multiple zones","Although this router has neighbors that require your internetwork to observe compatibility rules, AppleTalk has learned of a route with multiple zone names defined. This condition can cause node inconsistencies on your AppleTalk network.","Upgrade the routers that support only the original AppleTalk specification. In the meantime, observe the compatibility rules for AppleTalk Phase 1 and Phase 2 routers."
"AT","5","UNAVAILABLE","AppleTalk neighbor incompatibility; %#A has wide cable range","Although this router has neighbors that require your internetwork to observe compatibility rules, AppleTalk has learned of a route that has a cable range greater than 1. This condition can cause node inconsistencies on your AppleTalk network.","Upgrade the routers that support only the original AppleTalk specification. In the meantime, observe the compatibility rules for AppleTalk Phase 1 and Phase 2 routers."
"AT","5","UNAVAILABLE","No such route %d","You specified a nonexistent route in a show appletalk route or clear appletalk route command.","Specify a valid route, that is, one that appears in the output of the show appletalk route command."
"AT","5","UNAVAILABLE","Route to %#A is now using path of type %s on %s via %#a","The path to a network changed because either the old path went down or the new path was better.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","6","UNAVAILABLE","%s: AppleTalk %s path to %#A down; reported bad by %#a","A router went down somewhere on the AppleTalk network. The indicated peer notified this router of the change.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","6","UNAVAILABLE","%s: AppleTalk %s path to %#A via %#a has been deleted","A path on the AppleTalk network aged out.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","6","UNAVAILABLE","%s: AppleTalk %s path to network %#A added; via %#a (metric %d)","A new AppleTalk path has been learned. The message indicates the source of the path, its distance in hops, its metric, and the type of path.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","6","UNAVAILABLE","%s: AppleTalk interface enabled; no neighbors found","No other AppleTalk routers were found on the network attached to the interface.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","6","UNAVAILABLE","%s: AppleTalk interface enabled; verified by %#a","The AppleTalk configuration was verified by consulting the indicated router.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","6","UNAVAILABLE","%s: AppleTalk interface initializing; acquiring %s","The interface is determining the correct configuration. This message is displayed when discovery mode is enabled and no other router is detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","6","UNAVAILABLE","%s: AppleTalk interface restarting; line protocol came up","An AppleTalk interface that was previously shut down was restarted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","6","UNAVAILABLE","%s: AppleTalk neighbor added; %#a is operational","The router discovered a new AppleTalk router on the network.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","6","UNAVAILABLE","%s: AppleTalk neighbor up; %#a has restarted","A neighboring router to which this router previously lost connectivity reappeared on the network.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","6","UNAVAILABLE","%s: AppleTalk network added; %#A via %#a (%d hop %s)","A new AppleTalk route was learned. The message indicates the source of the route and its distance in hops.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","6","UNAVAILABLE","%s: AppleTalk network down; %#A reported bad by %#a","A router went down somewhere on the AppleTalk network. The indicated peer notified this router of the change.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","6","UNAVAILABLE","%s: AppleTalk network down; interface to %#A disabled","A connected route is being advertised as down (also known as otify neighbor) because the configured interface is no longer operational.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","6","UNAVAILABLE","%s: AppleTalk network up; %#A via %#a (%d hop %s)","A routing update was received for a previously suspect route.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","6","UNAVAILABLE","%s: AppleTalk node %a misconfigured; reply has been broadcast","An AppleTalk node sent a GetNet Info request to this router specifying an invalid network number for the source of the GetNet Info request. This situation occurs when an AppleTalk end node is moved to another network and is therefore misconfigured for the current network.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","6","UNAVAILABLE","%s: AppleTalk node up; using address %A","No hint address or a bad hint address was specified. This message indicates which AppleTalk address will be used for the interface.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","6","UNAVAILABLE","%s: MacIP server operational, %i","If the appletalk event-logging command is configured, this message appears on the console when a MacIP server is fully initialized and is ready to accept client requests. The AppleTalk zone served by the MacIP server replaces the zone specified in the appletalk zone command. The IP address configured on the MacIP server replaces the IP address configured by the ip address command.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","6","UNAVAILABLE","%s: MacIP server shutting down, %i","If the appletalk event-logging command is configured, this message appears on the console when a MacIP server is no longer operational for any reason. MacIP servers shut down in response to MacIP configuration changes or errors, or a change in the condition or configuration of an AppleTalk or IP interface for which the MacIP server is providing service. The AppleTalk zone served by the MacIP server replaces the zone specified in the appletalk zone command. The IP address configured on the MacIP server replaces the IP address configured by the ip address command.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","6","UNAVAILABLE","AppleTalk network deleted; %#A removed from routing table","A route on the AppleTalk network aged out.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","6","UNAVAILABLE","AppleTalk proxy defined; zone %s using network %#A","This message reports the zone name and network number that are being advertised to support the appletalk nbp-proxy command.","When proxy service is initiated, this message is generated each time the appletalk nbp-proxy command is issued. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","6","UNAVAILABLE","AppleTalk proxy deleted; zone %s freed network %#A","A previously configured Name Binding Protocol (NBP) proxy was deleted. The router can no longer convert NBP requests to a format understood by routers that support only the original AppleTalk specification.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","6","UNAVAILABLE","AppleTalk zone added; zone %*s defined","A new AppleTalk zone was created.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","6","UNAVAILABLE","AppleTalk zone deleted; zone %s released","The router removed an unused zone from the zone table.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","6","UNAVAILABLE","NBP registration of %s at [%s] pending","A name registration call is being performed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","6","UNAVAILABLE","Neighbor entry for %#a deleted","The clear appletalk neighbor command displays this command when it completes successfully.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","6","UNAVAILABLE","Route to %#A has gone bad","The system did not detect a route within the required timeout period. Therefore, the route is marked as bad. A network might have become unreachable for some reason, perhaps because of a broken connection. This message does not necessarily indicate an error condition.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AT","7","UNAVAILABLE","AppleTalk bug: %s","The software detected an unexpected condition. The router takes corrective action and continues.","Copy the message exactly as it appears, note any AppleTalk problems you experience, and call your technical support representative."
"AT","7","UNAVAILABLE","AppleTalk debug: %s","This message is generated by a debug command and provides additional information about an AppleTalk condition.","Copy the message exactly as it appears, note any AppleTalk problems you experience, and call your technical support representative."
"ATM","1","ISSU_NOMEMORY","msgtxt_nomemory","The requested operation could not be accomplished because of a low memory condition.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"ATM","1","UNAVAILABLE","Unit %d, not enough interface memory","The specified ATM interface hardware has run out of interface memory.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATM","1","UNAVAILABLE","msgtxt_nomemory","The requested operation could not be accomplished because of a low memory condition.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"ATMPA","3","CMDFAIL","%s Command Failed at %s - line %d, arg %d","The port adapter failed to process a command. A possible reason for this condition is an OIR operation was performed of a line card or port adapter and RP was in the process of executing commands. If this message is seen during any other time, it indicates a software problem.","If this message appeared while an OIR operation was being performed of a port adapter or line card, and if the slot or bay number in the message text corresponds to the removed hardware, this message indicates normal system operation and no action is required. Otherwise, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs"
"ATM","3","UNAVAILABLE","ATM ISSU: send message failed, rc = %d","The sending of a message has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATM","3","UNAVAILABLE","%s %s:%d","Internal Error (see message) occurs during ILMI Primary to Secondary Sync","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATM","3","UNAVAILABLE","%s [%08X=%s] %s:%d","Internal Error (see message) occurs during ILMI Primary to Secondary Sync","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATM","3","UNAVAILABLE","ATM failed to create VC on Interface %s","Either the configuration contains invalid traffic shaping parameters or the software ran out of rate queues.","Check the configuration for errors."
"ATM","3","UNAVAILABLE","ATM failed to create VC on Interface %s","The ATM subsystem ran out of internal resources necessary to create a new virtual circuit. This may indicate a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATM","3","UNAVAILABLE","ATM failed to create VC(VCD=%d, VPI=%d, VCI=%d) on Interface %s, (Cause of the failure: %s)","This message can occur for the following unrelated reasons. Each reason is accompanied by a recommended action. The virtual circuit descriptor (VCD) exceeded the maximum available memory. - Use a smaller VCD number. Address Resolution Protocol (ARP) is allowed only on AAL5-SNAP virtual circuits. - Change the encapsulation to AAL5SNAP. The virtual path identifier-virtual channel identifier (VPI-VCI) pair or the VCD is already in use. - Try using a different VPI-VCI or VCD number. Only one virtual channel connection (VCC) is allowed on a point-to-point interface. - Try using a different subinterface. AAL3/4-SMDS virtual circuit must be the only virtual circuit on an interface. - Turn off AAL3/4. AAL3/4-SMDS MID exceeds the maximum. - Try a smaller Multiplex ID (MID) value. Switched Multimegabit Data Service (SMDS) is not enabled. - Enable SMDS. The driver failed to accept the virtual circuit. - Try initiating the virtual circuit again.","If none of the previous actions fix the problem, copy the error message exactly as it appears and report it to your Cisco technical support representative."
"ATM","3","UNAVAILABLE","ATM failed to modify VC(VCD=%d, VPI=%d, VCI=%d) on Interface %s, (Cause of the failure: %s)","ATM failed to modify QoS params on a VC","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATM","3","UNAVAILABLE","ATM failed to remove VC(VCD=%d, VPI=%d, VCI=%d) on Interface %s, (Cause of the failure: %s)","This message can occur for the following reason. When the PVC configuration parameters are changed it is recreated, during recreation if the removal of PVC from the PA fails, this message is generated. If after generation of this error message if the PVC still remains in INACTIVE state give shut/no shut on the interface.","If none of the previous actions fix the problem, copy the error message exactly as it appears and report it to your Cisco technical support representative."
"ATM","3","UNAVAILABLE","Interface %s: Total %s allocation %u%s exceeded maximum %s of %u%s.","A software or hardware error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATM","3","UNAVAILABLE","MLPoATM not configured properly on Link %s Bundle %s :%s","The configuration of MLPPP-over-ATM (MLPoATM) on the ATM PVC is either incorrect or incomplete.","Ensure that the queueing strategy on the ATM interface is per VC queueing and queueing algorithm is FIFO.To verify the configuration, use the show inteface atm and show running-config virtual-template commands."
"ATM","4","UNAVAILABLE","%s: failed, rc=%s","The transform has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATM","4","UNAVAILABLE","atm-issu-compat: returned FALSE","The compatibility checking has failed","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATM","4","UNAVAILABLE","%s [%08X=%s] %s:%d","Recoverable Internal Error (see message) occurs during ILMI Primary to Secondary Sync","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATM","4","UNAVAILABLE","(%d/%d/%d:%d): %s. Please verify peer UNI version","The ATM peer equipment appears to be running an old version of ATM UNI. Communication with it is not possible.","The peer equipment needs to be upgraded in order to communicate with this system."
"ATM","4","UNAVAILABLE","Call from: ATM NSAP - %s has mismatched PDU size - forward size is %d - backward size is %d, int %s PDU size %s %s","The calling or called party has a maximum transmission unit (MTU) size configured that is different from the MTU size on the current interface.","Either change the configured MTU size on the current interface to that of the caller's or called party's interface, or change the caller's or called party's interface to match the current interface."
"ATM","4","UNAVAILABLE","ILMI(%s): Restarting ATM signalling and ILMI. Keepalive failure detected.","Adjacent peer device is not responding to ILMI Keepalive polling.","Check the connection of the ATM interface and the status of the adjacent peer device. Correct them if neccessary. Wait and check if ILMI Keepalive comes up again. If the problem persists, copy this warning message exactly as it appears, and report it to your technical support representative."
"ATM","4","UNAVAILABLE","ILMI(%s): Restarting ATM signalling and ILMI. Peer Configuration change detected.","Configuration of adjacent peer device has been changed.","Wait for the interface to restart itself."
"ATM","4","UNAVAILABLE","VPI/VCI range parameters are dis-joint on %s","MinSvccVci MaxVci, after negotiation with the peer through ILMI.","Disable auto-cinfiguration on both sides and change the port configuration appropriately so that SVCCs can be setup."
"ATM","4","UNAVAILABLE","clearing stuck VCD %d from map on %s","A SVC map entry has a stuck VCD attached to it, which has been previously cleared in the driver.","No action required as the stuck VCD condition is detected and cleared."
"ATM","5","UNAVAILABLE","%s","Informational Message for ILMI Redundency Support","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATM","5","UNAVAILABLE","Address registration on %s is enabled.","The command just entered enables atm address registration.","No action required."
"ATM","5","UNAVAILABLE","Changing VC %d/%d VC-state to %s","The ATM VC is either created, removed, activated, or deactivated.","No action required if status change is intended, otherwise the cause for status change may deserve to be noticed. shut/no shut CLI command deactivates/activates VC."
"ATM","5","UNAVAILABLE","ILMI(%s): %s","Informational Message for ILMI Redundency Support","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATM","5","UNAVAILABLE","New access filter setting will be applied to registration of new addresses on %s.","The command just entered sets up new ilmi access filter for address registration. It only affects new addresses to be registered. The addresses already registered will not be affected.","Shut/no shut on this interface to restart address registration if need to remove addresses already registered but not permitted by the new access filter."
"ATM","5","UNAVAILABLE","New global default access filter setting will be applied to registration of new addresses on interfaces using global default access filter.","The command just entered sets up new global default access filter for addres registration. It only affects new addresses to be registered on interfaces using the global default. The addresses already registered will not be affected.","Shut/no shut on desired interfaces to restart address registration if need to remove addresses already registered but not permitted by the new global default access filter."
"ATM","5","UNAVAILABLE","Restarting ATM signalling and ILMI on %s.","The command just entered causes ATM Soft Restart.","Stand by and let ATM Signalling and ILMI to restart."
"ATM","6","UNAVAILABLE","ILMI(%s): Auto configuration already disabled.","Atm auto-configuration has been enabled already. 'no atm auto-configuration' command just entered is ignored.","No action required."
"ATM","6","UNAVAILABLE","ILMI(%s): Auto-configuration already enabled.","Atm auto-configuration has been enabled already. 'atm auto-configuration' command just entered is ignored.","No action required."
"ATM","6","UNAVAILABLE","ILMI(%s): Auto-configuration cannot be enabled.The interface has VC configuration which cannot be supported with Auto-configuration enabled","Auto-configuration cannot be enabled if there are some conflicting configuration on an interface. Like if there are VCs with vpi 255, auto-configuration cannot be done till these VCs are removed, as with auto-configuration enabled vpi 255 cannot be supported.","Undo the conflicting configuration on the interface for this command to succeed."
"ATM","6","UNAVAILABLE","ILMI(%s): Auto-configuration is disabled, current interface parameters will be used at next interface restart.","The command just entered causes auto-configuration to be disabled, the most recently entered interface parameters will be used at next interface restart.","Be aware of what parameteres have been configured."
"ATM","6","UNAVAILABLE","ILMI(%s): This command does not apply to internal terminating port.","Internal terminating does not need to be configured with this command. The command just entered is ignored.","No action required."
"ATMCES","1","UNAVAILABLE","Invalid Port Adapter Hardware Type Type=%d","Port Adapter ID was not correct.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMCES","1","UNAVAILABLE","The 1575 device could not be initialized on bay %d, shutting down bay","The Port Adapter has failed its initialization.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMCES","1","UNAVAILABLE","The 1575 device failed to create VC %d, file:%s line:%d","The Port Adapter encounters errors in setting up VC","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMCES","1","UNAVAILABLE","The 1575 device not totally clean in removing VC %d, file:%s line:%d","The Port Adapter encounters errors in shut vc. May affect future VC creation","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMCES","1","UNAVAILABLE","The Slave device could not be initialized on bay %d, shutting down bay","The Port Adapter has failed its initialization.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMCES","3","UNAVAILABLE","Couldn't configure the Altera, DIO not reset","The Port Adapter has failed its initialization.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMCES","3","UNAVAILABLE","Couldn't get bridge configuration: %s","Bridge configuration failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMCES","3","UNAVAILABLE","Couldn't initialize the Altera, DIO not set","The Port Adapter has failed its initialization.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMCES","3","UNAVAILABLE","Device reported %08x","PCI devide ID was not correct.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMCORE","2","UNAVAILABLE","%s","The ATM core subsystem encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMCORE","3","UNAVAILABLE","%s","The ATM core subsystem encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMCORE","4","UNAVAILABLE","%s","The ATM core subsystem encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMCORE","4","UNAVAILABLE","%s","This warning is generated by the ATM core subsystem to the user. This could arise because the user request may not be granted due to some existing configuration on the device. This message serves as an alert to the user. This message contains text which can be used to help identify the nature of the problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMCORE","4","UNAVAILABLE","Configuration Error: %s","This message indicates a configuration error. The message will display more specific information about the problem location.","Change the configuration to correct the error."
"ATMCORE_RED","2","UNAVAILABLE","%s","The ATM core redundancy subsystem encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMCORE_RED","3","UNAVAILABLE","%s","The ATM core redundancy subsystem encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMCORE_RED","3","UNAVAILABLE","%s","The ATM core redundancy subsystem encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMCORE_RED","4","UNAVAILABLE","%s","The ATM core redundancy subsystem encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMLC","1","UNAVAILABLE","The ATM line card in slot %d failed to initialize (cause %s)","The ATM linecard has failed its initialization as indicated in the message. The problems can be one of the following: 1) memory allocation failure for control data, 2) framer, ATM SAR devices, or line card FPGA access failure, 3) uncorrectable multi-bit ECC errors in line card memory, 4) PCI bus timeout, 5) failure of downloading ATM SAR firmware to the SAR devices, or 6) ATM SAR device (reassembler or segmenter) does not boot up or does not respond to configuration commands.","Consult your line card installation and configuration guide and make sure the line card is properly installed and configured. If the line card is properly installed, perform an online insertion and removal (OIR) on the line card, either via a physical removal and insertion, or via the hw-module slot [slot#][stop|start] command. If the OIR does not work, try to reload the system if possible to bring the system offline. If the problem persists, the message indicates an unrecoverable hardware failure. Copy the error message exactly as it appears on the console or in the system log and call your Cisco technical support representative. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMLC","3","UNAVAILABLE","The ATM line card in slot %d encountered a hardware failure: %s","The ATM line card has encountered a hardware failure and should be deactivated. The problem can be any one of the following: 1) memory allocation failure for control data, 2) framer, ATM SAR devices, or line card FPGA access failure, 3) uncorrectable multi-bit ECC errors in line card memory, 4) PCI bus timeout, 5) ATM SAR device (reassembler or segmenter) does not respond to configuration commands, or 6) unrecoverable data corruption/parity error.","The message indicates a hardware failure. The line card may have been deactivated by the system. Perform a line card online insertion and removal(OIR) to confirm that the problem persists. If the problem persists, copy the error message exactly as it appears on the console or in the system log. Enter show c7300, show diag slot-number, show c7300 errorlog slot, show interface atm, and show controller atm and provide the gathered information to your technical support representative. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMLC","4","UNAVAILABLE","Interface ATM%d/%d, received SONET/SDH alarm: %s","The ATM framer interface received SONET/SDH alarm(s) as indicated in the message.","SONET/SDH alarms may occur when the line card is initializing and negotiating clocking with the peer. In this situation, the alarms will be cleared and the error message is used only to provide information. If the message continues to appear after the line card is initialized and the connection is set up, use the show controller atm command to check the framer alarms. If the alarms from show controller atm do not disappear, ensure that the optical fiber cable is not broken and is properly inserted and that the far end of the peer is not malfunctioning. If the error message persists, the message should reflect the alarm conditions of the SONET/SDH-based network. In this scenario, the alarm was sent by a far-end entity and the source and purpose of the alarm should be investigated by a network administrator if not already known. If you think the message itself is being received in error, copy the message exactly as it appears on the console or in the system log and capture the output of the show c7300 and the show controller atm commands. Call your Cisco technical support representative and provide the representative with the gathered information. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMLC","6","UNAVAILABLE","Interface ATM%d/%d, changed clock source to %s","The clock source of the ATM interface changed to either line clock or internal clock as indicated in the message. If the ATM interface is configured for line clocking and receives SONET/SDH alarms including one of loss of signal (LOS), loss of frame (LOF), and line alarm indication (Line AIS), the interface will first change to internal clock before changing back to line clock when the alarms are cleared. If the ATM interface is configured for internal clocking, the SONET/SDH alarms will not cause any clocking change. This message shows the run-time clock source changes on an ATM interface while the show controller atm command always shows the user-configured clock source.","No action is required."
"ATMOC3","1","UNAVAILABLE","%s error.","A non-recoverable error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMOC3","1","UNAVAILABLE","%s traffic type not allowed in a PVP.","This traffic type cannot be configured in a PVP.","Either change the traffic type of this VC or remove it from the PVP."
"ATMOC3","1","UNAVAILABLE","%s, packet(size %d) too big.","A packet greater than the 256 bytes received on this interface.","The system should recover. No action is required. If the problem reccurs, it indicates an error that might be related to data traffic patterns. Copy the error message exactly as it appears, and report it to your technical support representative."
"ATMOC3","1","UNAVAILABLE","Failed to activate F4 %s VC. PVP %d.","The required control VC was not established.","Copy the error message exactly as it appears, and report it to your technical support representative."
"ATMOC3","1","UNAVAILABLE","The ATM Network Module in slot %d is incompatible with the PCMCIA controller in the router.","The PCMCIA controller is down level.","Copy the error message exactly as it appears, and contact your technical support representative for upgrade information."
"ATMOC3","1","UNAVAILABLE","The Network Module in slot %d did not initialize.","The Network Module has failed its initialization.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMOC3","1","UNAVAILABLE","The Network Module in slot %d failed to initialize (cause %s).","The Network Module has failed its initialization.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMOC3","1","UNAVAILABLE","The network module hardware reports an invalid %s device id of %#x.","The ATMOC3 network module hardware may be bad.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMPA","0","UNAVAILABLE","misc_cntl_reg %#x. Resetting the OC12 PA...","The ASIC that interfaces the SAR engines to the VIP4 packet switching and routing processor has encountered an error that has caused it to fail. As its main function, this ASIC supports the SARs by implementing the cell and packet buffering scheme that is expected on the Port 1 interface, and by managing the commands and indications sequences on the Port 2 interface.","The OC-12 reboots itself. May need to do clear int"
"ATMPA","1","UNAVAILABLE","%s control memory bad","A memory test failed within the PCI control memory. This probably indicates a memory chip has failed.","Copy the error message exactly as it appears on the console or in the system log. Issue the 'sh tech-support' command to gather data that may help to determine the nature of error. Call your Cisco technical support representative and provide representative with the gathered information."
"ATMPA","1","UNAVAILABLE","%s failed to send report %d at %s - line %d","The port adaptor failed to send a report from vip.","Copy the error message exactly as it appears, and report it to your technical support representative."
"ATMPA","1","UNAVAILABLE","%s vc %d received a giant packet size %d - %08x %08x %08x %08x %08x %08x","The port adaptor received a giant packet.","Copy the error message exactly as it appears, and report it to your technical support representative."
"ATMPA","1","UNAVAILABLE","VIP2-40 and below only supports one OC-3 ATM PA. The other PA bay needs to be emptied in order for the ATM PA to function.","The bandwidth requirements of the installed port adapters exceed the processor's rated capability.","Either remove one of the port adapters or upgrade the VIP."
"ATMPA","1","UNAVAILABLE","register %08x write value 0x%02x but read 0x%02x","The port adaptor failed to write a register.","Copy the error message exactly as it appears, and report it to your technical support representative."
"ATMPA","2","UNAVAILABLE","Slot %d device is invalid (ID %#x)","The ATM Deluxe PCI driver found an incorrect PCI device ID during initialization. This could mean that a hardware failure caused an actual failure to read the ID, or that the software needs to be upgraded to support hardware that did not exist yet at the time the software was written.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMPA","2","UNAVAILABLE","ti1570_vc_setup failed. (vp_count %d  max_vp %d).","Attempt has been made to create more Virtual Paths than the maximum configured Virtual Paths.","ATM-Light supports 6 Virtual Paths by default. The default value can be changed using interface config command atm vc-per-vp xxx. Decrease the vc-per-vp value to increase the number of Virtual Paths that can be created."
"ATMPA","3","UNAVAILABLE","%s Command Failed at %s - line %d, arg %d","The port adapter failed to process a command. A possible reason for this condition is an OIR operation was performed of a line card or port adapter and RP was in the process of executing commands. If this message is seen during any other time, it indicates a software problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMPA","3","UNAVAILABLE","%s Have to close all VCs beforemodifying the VP tunnel %d","The VP Tunnel has open VCs assosiated with it.","Remove all the VCs associated with the VP tunnel before modifying the VP."
"ATMPA","3","UNAVAILABLE","%s Runs out of VP space for vpi %d","Unable to get a driver VP control block, neither from inuse_q nor from virgin_q. So, we cannot Setup a new Vp nor a new VC.","To increase the number of VPs configurable on PA-A3-OC12 we can use 'atm vc-per-vp' interface configuration command. So the recommended action here is to set the appropriate value in 'atm vc-per-vp'."
"ATMPA","3","UNAVAILABLE","%s SAR doing %s error: %s","ATM driver SAR operation error.","Enable 'debug atm events' & gather the log. Issue the 'sh tech-support' command to gather data that may help to determine the nature of error. Call your Cisco technical support representative and provide representative with the gathered information."
"ATMPA","3","UNAVAILABLE","%s SAR firmware checksum error (expected 0x%04x, obtained 0x%04x)","CM622 ATM SAR firmware checksum errors.","Enable 'debug atm events' & gather the log. Issue the 'sh tech-support' command to gather data that may help to determine the nature of error. Call your Cisco technical support representative and provide representative with the gathered information."
"ATMPA","3","UNAVAILABLE","%s Tx Indication FIFO full.","TX Indication FIFO full. From TX FPGA.","None. The OC-12 reboots itself."
"ATMPA","3","UNAVAILABLE","%s bad vcd %d packet - %08x %08x %08x %08x %08x %08x","The port adaptor received packet on a non-existent vc.","Copy the error message exactly as it appears, and report it to your technical support representative."
"ATMPA","3","UNAVAILABLE","%s tx cmd ack error (%#x), vcd %d.","Error while processing the Tx Ack cmd.","Enable 'debug atm events' & gather the log. Issue the 'sh tech-support' command to gather data that may help to determine the nature of error. Call your Cisco technical support representative and provide representative with the gathered information."
"ATMPA","3","UNAVAILABLE","%s: Platform Setup_vc failed for %d/%d, vcd %d","RSP Platform Setup VC failed.","Turn on debug atm error on platform console and see why."
"ATMPA","3","UNAVAILABLE","%s: Platform Setup_vp failed for vpi %d","RSP Platform Setup VP failed.","Turn on debug atm error on platform console and see why."
"ATMPA","3","UNAVAILABLE","%s: SAR%d Chip Crashdump:","The SAR chip crashed and interface is being reset.","Copy the error message exactly as it appears on the console or in the system log. Issue the 'sh cont atm xxx' command to gather data that may help to determine the nature of error. Call your Cisco technical support representative and provide representative with the gathered information."
"ATMPA","3","UNAVAILABLE","%s: bad rx particle 0x%08x flags 0x%08x index %d","The PA host driver dectected a duplicate rx host buffer returned","Copy the error message exactly as it appears, and report it to your echnical support representative."
"ATMPA","3","UNAVAILABLE","%s: bad tx packet on vcd %d size %d","The PA host driver dectected a bad tx host buffer with size 0","Enable 'debug atm events' & gather the log. Issue the 'sh tech-support' command to gather data that may help to determine the nature of error. Call your Cisco technical support representative and provide representative with the gathered information."
"ATMPA","3","UNAVAILABLE","%s: receive freeze %d","This message indicates excessive traffic congestion on the ATM interface may have resulted in cell loss. The PCI-ATM interface's cell buffers were full when a cell arrived on the interface, resulting in a receive freeze condition.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMPA","3","UNAVAILABLE","%s: transmit freeze %d","This message indicates the PCI-ATM interface had to stop the transmitter while waiting for data.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMPA","3","UNAVAILABLE","ATMPA (bay %d), Init Failed at %s - line %d","The port adaptor failed to complete hardware initialization.","Copy the error message exactly as it appears, and report it to your technical support representative."
"ATMPA","3","UNAVAILABLE","In file %s - line %d","Cannot create the CM622 Process Agent process, which is a temp process to download firmware.","Enable 'debug atm events' & gather the log. Issue the 'sh tech-support' command to gather data that may help to determine the nature of error. Call your Cisco technical support representative and provide representative with the gathered information."
"ATMPA","3","UNAVAILABLE","Interface %s: %s command not supported","An attempt was made to configure a rate queue on an ATM Lite port adapter that does not support rate queues.","Check the configuration and try again, avoiding unsupported features."
"ATMPA","3","UNAVAILABLE","Only %#x bytes of memory available for %s","The port adaptor needs more PCI memory. The installed amount is less than required by the drivers for packet buffers.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMPA","3","UNAVAILABLE","RX DMA entry %#x not going inactive","A receive DMA channel failed to deactivate during shutdown of a virtual circuit. This failure could originate in hardware or software.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMPA","3","UNAVAILABLE","Slot %d device is not TI1570 (ID %#x)","The driver found a device type other than what it expected in the specified PCI slot. If the device is a TI1570 then a hardware failure may have occurred.","Power down the system, re-seat the interface card, and reboot. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMPA","3","UNAVAILABLE","Slot %d device is not a valid PCI device vendor ID used onOC-12 PA (ID %#x)","The driver found a device type other than what it expected in the specified PCI slot.","Power down the system, re-seat the interface card, and reboot. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMPA","3","UNAVAILABLE","TI1570 unit %s: PCI parity error (0x%08x)","A parity error occurred on the PCI bus. This probably indicates an existing or developing hardware failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMPA","3","UNAVAILABLE","TX CMD %d failed for vcd %d.","Failure while processing a Batman tx SAR cmd or unable to performa cmd ack.","Enable 'debug atm events' & gather the log. Issue the 'sh tech-support' command to gather data that may help to determine the nature of error. Call your Cisco technical support representative and provide representative with the gathered information."
"ATMPA","3","UNAVAILABLE","TX DMA not flushed","A transmit DMA channel failed to flush its buffers during shutdown of an ATM interface. This failure could originate in hardware or software.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMPA","3","UNAVAILABLE","found %d interfaces on bay %d (device ID %08X)","The software could not identify the interface card.","Power down the system, reseat the interface card, and reboot. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMPA","4","UNAVAILABLE","%s: Shaped peak rate adjusted to %d","CM622 only allows shaped rate up to half of line rate.","You can either specify a value within range oruse the adjusted value"
"ATMPA","4","UNAVAILABLE","RX SAR cmd %s error: %s (indication=0x%08x 0x%08x 0x%08x)","ATM driver RX SAR indication errors.","Enable 'debug atm events' & gather the log. Issue the 'sh tech-support' command to gather data that may help to determine the nature of error. Call your Cisco technical support representative and provide representative with the gathered information."
"ATMPA","5","UNAVAILABLE","ti1570_vc_setup failed. (vci %d of the lastvpi %d exceeds (vc-per-vp - 3)).","The TI1570 chip reserves 3 RX DMA channels for OAM cells.As a result, the last 3 VCIs of the last VPI block cannotbe used for regular traffic.","Avoid try different vci/vpi combinations."
"ATMPA","7","UNAVAILABLE","%s 0x%08x, %s 0x%08x, %s 0x%08x","SAR APU Registers dump","Copy the error message exactly as it appears, and report it to your technical support representative."
"ATMPA","7","UNAVAILABLE","%s 0x%08x, %s 0x%08x, %s 0x%08x, %s 0x%08x","SAR CW4010 Registers dump","Copy the error message exactly as it appears, and report it to your technical support representative."
"ATMPA","7","UNAVAILABLE","00 0x%08x, 01 0x%08x, 02 0x%08x, 03 0x%08x","SAR Misc. dump","Copy the error message exactly as it appears, and report it to your technical support representative."
"ATMPA","7","UNAVAILABLE","04 0x%08x, 05 0x%08x, 06 0x%08x, 07 0x%08x","SAR Misc. dump","Copy the error message exactly as it appears, and report it to your technical support representative."
"ATMPA","7","UNAVAILABLE","08 0x%08x, 09 0x%08x, 10 0x%08x, 11 0x%08x","SAR Misc. dump","Copy the error message exactly as it appears, and report it to your technical support representative."
"ATMPA","7","UNAVAILABLE","12 0x%08x, 13 0x%08x, 14 0x%08x, 15 0x%08x","SAR Misc. dump","Copy the error message exactly as it appears, and report it to your technical support representative."
"ATMSIG","3","UNAVAILABLE","%s","An internal software error or unexpected condition occured during PNNI (Connection/Path) Trace related processing","Show atm pnni trace information.Also gather information about where/how trace was initiated, and for what type of VC.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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSIG","3","UNAVAILABLE","1st halfLeg failed, %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSIG","3","UNAVAILABLE","2nd halfLeg failed, %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSIG","3","UNAVAILABLE","ATMSIG(%s %d,%d - %04d/%02d) SVC wavl del failed:svc 0x%x","A software error occurred during closure of an SVC. Other error messages appearing immediately prior to this one may be related.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSIG","3","UNAVAILABLE","ATMSIG(%s %d,%d - %04d/%02d) SVC wavl ins failed:svc 0x%x","A software error occurred during creation of an SVC. Other error messages appearing immediately prior to this one may be related.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSIG","3","UNAVAILABLE","ATMSIG(%s %d,%d - %04d/%02d) avl prty del failed:svc 0x%x party 0x%x","A software error occurred during removal of a party from a point-to-multipoint call. Other error messages appearing immediately prior to this one may be related.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSIG","3","UNAVAILABLE","ATMSIG(%s %d,%d - %04d/%02d) avl prty ins failed:svc 0x%x party 0x%x","A software error occurred during addition of a party to a point-to-multipoint call. Other error messages appearing immediately prior to this one may be related.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSIG","3","UNAVAILABLE","ATMSIG(%s)","A software error occurred during addition of a member to a closed user group. Other error messages appearing immediately prior to this one may be related.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSIG","3","UNAVAILABLE","ATMSIG(%s)","A software error occurred during removal of a member from a closed user group. Other error messages appearing immediately prior to this one may be related.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSIG","3","UNAVAILABLE","Assertion failed: %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSIG","3","UNAVAILABLE","Cannot find a Callref value to allocate: %s","This indicates an internal software error, probably including memory exhaustion.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSIG","3","UNAVAILABLE","Duplicate LISTEN by %s for existing NSAP %s owned by %s","An application attempted to either LISTEN on an NSAP owned by another application or to LISTEN for the same NSAP twice","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSIG","3","UNAVAILABLE","Invalid msg from routing/pnni : %s","This message indicates an error in the PNNI routing subsystem. It could be caused by an internal software error or by bad control information received from peer equipment. The message will contain additional information that can help locate the cause. Any message with 'NULL' probably indicates a problem with this system, others probably point at the peer equipment.","Check this system and the peer equipment for any obvious errors. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSIG","3","UNAVAILABLE","Signalling control block initialization failure, %s","An internal software or resource error occurred","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSIG","3","UNAVAILABLE","Xconnect failed, %s","An internal software error occurred during installation of an SVC cross-connect.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSIG","3","UNAVAILABLE","halfLeg removal failed, %s","An internal software error occurred. This message should only be displayed when verbose debugging is enabled for an SVC.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSIG","3","UNAVAILABLE","no SVC, %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSIG","3","UNAVAILABLE","process_enqueue failed, %s","An internal software error occurred while handling a user request.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSIG","4","UNAVAILABLE","Configuration Error: %s %s","This message indicates a configuration error in the ATM Signaling subsystem. The message will display more specific information about the problem location.","Change the configuration to correct the error."
"ATMSPA","2","UNAVAILABLE","%s - Init Failed return code: %u","The SPA failed to complete hardware initialization. One of the devices in the SPA failed to initialize successfully. Information about the failed device is specified in the message text on the console or in the system log.","Please power down and reseat the indicated SPA card. If the condition persists, copy the error message exactly as it appears. Next research and attempt to resolve the issue using the SPA hardware troubleshooting documentation as well as the tools and utilities provided at http://www.cisco.com/public/support/tac/tools.shtml. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact your Cisco technical support representative. Be sure to provide the the information you have gathered and a 'show tech-support' to your support representative, or attach it to your case in non-zipped, plain text format (.txt)."
"ATMSPA","3","UNAVAILABLE","%s %s %s: %d","Traffic shaping parameters could not be configured because the number of unique shaping parameters that are configured on the PVCs or PVPs in this specified ATM SPA is over the maximum limit. The maximum number of unique shaping parameters that can be configured on the PVCs or PVPs is 4096.","Ensure that the total number of unique shaping parameters that are configured on both PVCs and PVPs does not exceed the maximum limit of 4096."
"ATMSPA","3","UNAVAILABLE","%s Error 0x%x %s","A datapath protocol violation or sequence error has been detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSPA","3","UNAVAILABLE","%s Error 0x%x %s","The specified error has been detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSPA","3","UNAVAILABLE","%s Error 0x%x %s","The specified hardware error has been detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSPA","3","UNAVAILABLE","%s Error 0x%x %s","The specified software error has been detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSPA","3","UNAVAILABLE","%s: VC queue configuration failed due to un-initialized queue table(global identifier %d)","Software configuration of a VC queue failed due to un-initialized queue table.","Attempt to perform a soft OIR operation by entering the command that is described in the shared port adapter software configuration guide. If the condition persists, copy the error message exactly as it appears, and report it to your technical support representative. Also supply a 'show tech-support' at that time."
"ATMSPA","3","UNAVAILABLE","Cannot perform the requested FPD update operation because %s in subslot %u/%u has incompatible HW version %u.%u with FPD image version %d.%d for FPD ID %d. Only image version greater than %u.%u can be used in the update operation of %s with HW version greater than %u.%u.","The version of the FPD image from the FPD image bundle or package is not compatible with the HW version of the target card","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSPA","3","UNAVAILABLE","occurred on %s. Resetting SPA","The SPA has been reset due to a critical error in one of its devices. The error could either be a single occurrence of an event or multiple occurrences within a period of time. The message text on the console or in the system log provides more information on the specific nature of the error.","If the SPA is reset more than once, copy the error message exactly as it appears. Next research and attempt to resolve the issue using the SPA hardware troubleshooting documentation as well as the tools and utilities provided at http://www.cisco.com/public/support/tac/tools.shtml. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact your Cisco technical support representative. Be sure to provide the the information you have gathered and a 'show tech-support' to your support representative, or attach it to your case in non-zipped, plain text format (.txt)."
"ATMSPA","4","UNAVAILABLE","%s: VC setup command received on the LC for an existing VC (VCD %d)","A command to set up a VC has been received for a VC that has already been set up. The VC has already been configured by a previous setup VC command from the RP. A duplicate setup command may indicate that the RP did not receive a response from the LC for the previous setup command.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSPA","4","UNAVAILABLE","%s: VC tear down command received on the LC for a non-existing VC (VCD %d)","The VC does not exist on the LC. Most likely, it has been torn down by a previous teardown command from RP. A duplicate teardown command may indicate that the RP did not receive a response from the LC for the previous teardown command.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSPA","4","UNAVAILABLE","%s: VP setup command received on the LC for an existing VP (VPI %d)","A command to set up a VP has been received for a VP that has already been set up. The VP has already been configured by a previous setup VP command from the RP. A duplicate setup command may indicate that the RP did not receive a response from the LC for the previous setup command.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSPA","4","UNAVAILABLE","%s: VP tear down command received on the LC for a non-existing VP (VPI %d)","The VP does not exist on the LC. Most likely, it has been torn down by a previous teardown command from RP. A duplicate teardown command may indicate that the RP did not receive a response from the LC for the previous teardown command.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSSCOP","3","UNAVAILABLE","INIT SSCOP - Intf : %s, Event : %s, State : %s.","A software error occurred in the ATM SSCOP subsystem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSSCOP","4","UNAVAILABLE","(%s): %s. Please verify peer UNI version","The ATM peer equipment appears to be running an old version of ATM UNI. Communication with it is not possible.","The ATM peer equipment may need attention. Please verify its UNI version is at least 3.1, and upgrade if necessary."
"ATMSSCOP","5","UNAVAILABLE","- Intf : %s, Event : %s, State : %s.","This message indicates a routine step of the ATM SSCOP initialization sequence.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMPA","1","INVALIDCONFIG","VIP2-40 and below only supports one OC-3 ATM PA. The other PA bay needs to be emptied in order for the ATM PA to function.","The bandwidth requirements of the installed port adapters exceed the processor's rated capability.","Either remove one of the port adapters or upgrade the VIP."
"ATOM_TRANS","3","INIT_FAIL","Failed to start AToM Manager","Failed to start and initialize AToM Manager.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"ATMSPA","2","INITFAIL","[chars] - Init Failed return code: [int]","The shared port adapter (SPA) failed to complete hardware initialization. One of the devices in the SPA failed to initialize successfully. Information about the failed device is specified in the message text on the console or in the system log.","Power down and reseat the indicated SPA card. If the condition persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSPA","3","DATA_ERROR","[chars] Error [hex] [chars]","A data path protocol violation or sequence error has been detected. The message text on the console or in the system log provides more information on the specific cause of the error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSPA","3","FATAL_ERROR","occurred on [chars]. Resetting SPA","The shared port adapter (SPA) has been reset because of a critical error in one of its devices. The error could either be a single occurrence of an event or multiple occurrences within a period of time. The message text on the console or in the system log provides more information on the specific cause of the error.","If the SPA is reset more than once, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSPA","3","FPD_VER_DEPENDENCY_NOTE","Cannot perform the requested FPD update operation because [chars] in subslot [int]/[int] has incompatible HW version [int].[int] with FPD image version [dec].[dec] for FPD ID [dec]. Only image version greater than [int].[int] can be used in the update operation of [chars] with HW version greater than [int].[int].","The version of the field-programmable device (FPD) image from the FPD image bundle or package is not compatible with the hardware (HW) version of the target card.","If the SPA is reset more than once, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSPA","3","GEN_ERROR","[chars] Error [hex] [chars]","The error that is specified in the message has been detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSPA","3","HW_ERROR","[chars] Error [hex] [chars]","A hardware error has been detected. The message text on the console or in the system log provides more specific informationabout the error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSPA","3","QOS_ALLOC_FAILED","[chars] [chars] [chars]: [dec]","Traffic-shaping parameters could not be configured because the number of unique shaping parameters that are configured on the PVCs or PVPs in this specified ATM SPA is over the maximum limit. The maximum number of unique shaping parameters that can be configured on the PVCs or PVPs is 4096.","Ensure that the total number of unique shaping parameters that are configured on both PVCs and PVPs does not exceed the maximum limit of 4096."
"ATMSPA","3","SW_ERROR","[chars] Error [hex] [chars]","A software error has been detected. The message text on the console or in the system log provides more specific information about the error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSPA","3","VCQ_ERROR","[chars]: VC queue configuration failed due to un-initialized queue table(global identifier [dec])","The software configuration of a virtual circuit (VC) queue failed because of an uninitialized queue table.","Attempt to perform a soft OIR operation by entering the command that is described in the shared port adapter software configuration guide. If the condition persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATMSPA","4","VCSETUP","[chars]: VC setup command received on the LC for an existing VC (VCD [dec])","A command to set up a virtual circuit (VC) has been received for a VC that has already been set up and configured by a previous setup VC command from the RP. A duplicate setup command may indicate that the RP did not receive a response from the line card for the previous setup command.","No action is required."
"ATMSPA","4","VCTEARDOWN","[chars]: VC tear down command received on the LC for a non-existing VC (VCD [dec])","The virtual circuit (VC) does not exist on the line card. The VC probably has been torn down by a previous teardown command from the route processor (RP). A duplicate teardown command may indicate that the RP did not receive a response from the line card for the previous teardown command.","No action is required."
"ATMSPA","4","VPSETUP","[chars]: VP setup command received on the LC for an existing VP (VPI [dec])","A command to set up a virtual path (VP) has been received for a VP that has already been set up. The VP has already been configured by a previous setup VP command from the route processor (RP). A duplicate setup command may indicate that the RP did not receive a response from the line card for the previous setup command.","No action is required."
"ATMSPA","4","VPTEARDOWN","[chars]: VP tear down command received on the LC for a non-existing VP (VPI [dec])","The virtual path (VP) does not exist on the line card. The VP probably has been torn down by a previous teardown command from the route processor (RP). A duplicate teardown command may indicate that the RP did not receive a response from the line card for the previous teardown command.","No action is required."
"ATOM_NP_CLIENT","3","INFO","%s","ATOM NP Client failed to initialize properly which will result in improper operation of Any Transport Over MPLS feature","Try to reload the IOS image on the affected card or platform. If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative."
"ATOM_NP_CLIENT","3","NOMEM","%s","ATOM NP Client failed to initialize properly which will result in improper operation of Any Transport Over MPLS feature","This error may indicate that more memory must be installed on the affected card or platform in order to service all the features and related entities enabled via the configuration. Try to reload the IOS image on the affected card or platform. If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative."
"ATOM_NP_CLIENT","3","UNAVAILABLE","%s","ATOM NP Client failed to initialize properly which will result in improper operation of Any Transport Over MPLS feature","This error may indicate that more memory must be installed on the affected card or platform in order to service all the features and related entities enabled via the configuration. Try to reload the IOS image on the affected card or platform. If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative."
"ATOM_NP_CLIENT","4","WARN","%s %d %s","AToM Entry could not be added because: 1. Entry passed is invalid.","Try to reload the IOS image on the affected card or platform. If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative."
"ATOM_SEG","3","UNAVAILABLE","Error freeing %s","ATOM Segment Handler error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATOM_SEG","3","UNAVAILABLE","Illegal label %d update %s","AToM Segment Handler error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATOM_SEG","3","UNAVAILABLE","Unsupported update %s","AToM Segment Handler error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATOM_TRANS","3","UNAVAILABLE","%s","An action attempted by the layer 2 transport over MPLS implementation encountered an unexpected condition","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATOM_TRANS","3","UNAVAILABLE","Failed to allocate local label for peer:%i, vcid:%u","Failed to allocate local label for specified AToM VC.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATOM_TRANS","3","UNAVAILABLE","Failed to start AToM Manager","Failed to start and initialize AToM Manager.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATOM_TRANS","4","UNAVAILABLE","%s","AToM pseudowire uses undesirable configuration.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATOM_TRANS","5","UNAVAILABLE","%s","Disposition disabled for specified AToM VC.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATOM_TRANS","5","UNAVAILABLE","%s","Disposition enabled for specified AToM VC.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATOM_TRANS","5","UNAVAILABLE","%s","Imposition disabled specified AToM VC.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ATOM_TRANS","5","UNAVAILABLE","%s","Imposition enabled for specified AToM VC.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AUDIT","1","UNAVAILABLE","Audit File Roll-over: %d","Audit Circular File Rolled Over.","Increase Audit filesize."
"AUDIT","3","UNAVAILABLE","Cannot create Audit file.","File system error while creating the audit file.","Check DISK filesystems on the router."
"AUDIT","3","UNAVAILABLE","Cannot create Audit process.","Insufficient internal resource available to create process.","Check available memory on router."
"AUDIT","3","UNAVAILABLE","Cannot resize Audit file.","File system error while resizing the audit file.","Check DISK filesystems on the router."
"AUDIT","3","UNAVAILABLE","Cannot write to Audit file.","File system error while writing to the audit file.","Check DISK filesystems on the router."
"AUDIT","5","UNAVAILABLE","Auditing disabled","Audit was disabled on the router.","Check if Audit was disabled by someone authorized to do so"
"AUDIT","5","UNAVAILABLE","Auditing enabled","Audit was enabled on the router.","Audit logs can be verified, if changes are valid"
"AUDIT","5","UNAVAILABLE","Filesystem changed. Hash: %s","FLASH/DISK Filesystems on the router changed.","Check if it is a valid change."
"AUDIT","5","UNAVAILABLE","Hardware changed. Hash: %s","Hardware on the router changed.","Check if it is a valid change."
"AUDIT","5","UNAVAILABLE","Running Configuration changed. Hash: %s","Running Config on the router changed.","Check if it is a valid change in config."
"AUDIT","5","UNAVAILABLE","Running Version changed. Hash: %s","Running Version on the router changed.","Check if it is a valid change."
"AUDIT","5","UNAVAILABLE","Startup Configuration changed. Hash: %s","Startup config on the router changed.","Check if it is a valid change."
"AUTHMGR","5","UNAVAILABLE","Authorization failed for client (%s) on Interface %s","Authorization was unsuccessful","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AUTHMGR","5","UNAVAILABLE","Authorization succeeded for client (%s) on Interface %s","Authorization was successful","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AUTHMGR","5","UNAVAILABLE","Interface %s unauthorized","Port has become unuthorized","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AUTHMGR","5","UNAVAILABLE","Security violation on the interface %s, new MAC address (%e) is seen.","A host on the specified interface is attempting to gain access into the network or is trying to authenticate in a host mode that does not support the number of hosts attached. This is treated as a security violation and the port has been error-disabled.","Ensure that the port is configured to support the number of hosts attached. Enter the shutdown command followed by no shutdown command to restart the port."
"AUTHMGR","5","UNAVAILABLE","Starting '%s' for client (%s) on Interface %s","Starting an authentication method","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AUTHMGR","5","UNAVAILABLE","VLAN %d assigned to Interface %s","VLAN assignment","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AUTHMGR","7","UNAVAILABLE","Authentication result '%s' from '%s' for client (%s) on Interface %s","Authentication result received from a method","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AUTHMGR","7","UNAVAILABLE","Exhausted all authentication methods for client (%s) on Interface %s","All available authentication methods have been tried","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AUTHMGR","7","UNAVAILABLE","Failing over from '%s' for client (%s) on Interface %s","Failing over from the current authentication method","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AUTHMGR","7","RESULT","Authentication result '[chars]' from '[chars]' for client ([chars]) on Interface [chars]","The authentication result and method are displayed for the client.","No action is required."
"AUTH_MGR_ISSU","2","UNAVAILABLE","Auth Mgr ISSU client encountered unexpected client nego_done. Error: %d (%s)","An ISSU-compliant client transitions through a series of internal states. The Auth Mgr ISSU client encountered a 'client negotiation done' state that was unexpected. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","Show issu session and show issu negotiated capability. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AUTH_MGR_ISSU","2","UNAVAILABLE","Auth Mgr ISSU client failed to get buffer for message. Error: %d (%s)","The Auth Mgr ISSU client failed to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","Show logging and show checkpoint client. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AUTH_MGR_ISSU","2","UNAVAILABLE","Auth Mgr ISSU client failed to register session information. Error: %d (%s)","The Auth Mgr ISSU client failed to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly.","Show issu capability entries, issu session and show issu negotiated capability. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AUTH_MGR_ISSU","2","UNAVAILABLE","Auth Mgr ISSU client failed to send negotiation message. Error: %d (%s)","The Auth Mgr ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","Show logging and show checkpoint client. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AUTH_MGR_ISSU","2","UNAVAILABLE","Auth Mgr ISSU client initialization failed to %s. Error: %d (%s)","The Auth Mgr ISSU client could not be initialized. This initialization failure must be addressed before in-service software upgrade or downgrade can be performed successfully. If you do not address this failure, there will be downtime during software upgrade or downgrade.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AUTH_MGR_ISSU","3","UNAVAILABLE","'Feature Id %d, Tag %d' is not supported by Auth Mgr ISSU client at peer","The Auth Mgr ISSU client at the peer supervisor is not compatible for this message type. The Auth Mgr client will be marked as incompatible with the peer.","Show issu session and show issu negotiated version. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AUTH_MGR_ISSU","3","UNAVAILABLE","Auth Mgr ISSU client %s transform failed for 'Feature Id %d, Tag %d'. Error: %d (%s)","The Auth Mgr ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In both cases, the Auth Mgr state between the active device and the standby device is not identical.","Show issu session and show issu negotiated version. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AUTH_MGR_ISSU","3","UNAVAILABLE","Auth Mgr ISSU client 'Feature Id %d, Tag %d' is not compatible","The Auth Mgr ISSU client received an incompatible message from the peer device. The message cannot be processed.","Show issu session and show issu negotiated version. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AUTH_MGR_ISSU","3","UNAVAILABLE","Auth Mgr ISSU client capability exchange result incompatible.","The Auth Mgr ISSU client capability exchange have negotiated as incompatible with the peer.","Show issu negotiated capability.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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AUTH_MGR_ISSU","3","UNAVAILABLE","Auth Mgr ISSU client capability list is empty.","The Auth Mgr ISSU client capability exchange list size is invalid.","Show issu message group and issu session, and show issu negotiated version. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AUTH_MGR_ISSU","3","UNAVAILABLE","Auth Mgr ISSU client does not have a valid registered session.","The Auth Mgr ISSU client does not have a valid registered session.","Show issu capability entries, issu session and show issu negotiated capability. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AUTH_MGR_ISSU","3","UNAVAILABLE","Auth Mgr ISSU client failed to get the MTU for Feature Id %d, Tag %d. Error: %d (%s)","The Auth Mgr ISSU client failed to calculate the MTU for the specified message. The Auth Mgr ISSU client is not able to send the message to the standby device.","Show issu session and show issu negotiated version. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AUTH_MGR_ISSU","3","UNAVAILABLE","Auth Mgr ISSU client failed to unregister session information. Error: %d (%s)","The Auth Mgr ISSU client failed to unregister session information.","Show issu session and show issu negotiated capability. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AUTORP","2","UNAVAILABLE","Error initializing the Auto-RP radix tree","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AUTORP","4","UNAVAILABLE","AutoRP %s packet is received on interface %s with Source address=%i, Destination address=%i, TTL=%u, IP length=%u Datagram size/UDP length=%u","The AutoRP packet was received with wrong packet length. The packet has been dropped as it may be a malformed packet.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AUTORP","4","UNAVAILABLE","AutoRP %s packet, group %i with mask %i removed because of multicast boundary for %i with mask %i","The multicast boundary has a longer network mask than the AutoRP encoded group.","Use postive permit clauses in the AutoRP Access Control List"
"AUTORP","4","UNAVAILABLE","Error expiring semi-static RP-mapping entry (%i/%d, RP:%i)","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AUTORP","4","UNAVAILABLE","Error inserting a new entry into the RP-mapping radix tree","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AUTORP","5","UNAVAILABLE","C-RP %i on interface %s has been removed","This is performed either because PIM is disabled on the interface or the interface card has been removed","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AUTORP","5","UNAVAILABLE","RP for %i/%d is now %i","A new RP has been elected for the subject group prefix","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AUTORP","6","UNAVAILABLE","AutoRP RP-MAPPING IDB %s is deleted","The configured rp-mapping idb has been deleted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AUTOSHUT","4","MOD_AUTOSHUT","Module [dec] shutdown automatically, reset [dec] times within [dec] minutes due to [chars].","This message includes information about the automatic shutdown of a module.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AUTOSHUT","5","MOD_AUTOSHUT_SLOW","Module [dec] reset frequency exceeded threshold but over [dec] minutes. Hence NOT powering down module.","The module's reset frequency has exceeded the threshold, but over a period more than the preset period.","No action is required."
"AUTOSEC","3","UNAVAILABLE","Applying AutoSecure config to running-conf failed with error %d","Configuration of the AutoSecure session could not be applied to the running configuration","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"AUTOSEC","5","UNAVAILABLE","AutoSecure is configured on the device","Security configuration of the device is doneusing AutoSecure.","Notification message only. No action required."
"BACKPLANE_BUS_ASIC","3","FAILURE_INTR_CFG","Failure to setup the Backplane Bus ASIC device interrupts.","The line card internal ASIC could not be initialized. As a result, the device has been disabled and the datapath will not be operational.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BACKPLANE_BUS_ASIC","4","DEV_RESET","Backplane Bus Asic reset, interrupt [chars]","The backplane bus ASIC in the MSC/FlexWAN-ENH has received a fatal error. The ASIC will be reset and the MSC/FlexWAN-ENH will attempt to continue normal operation.","No action is required if traffic recovers. Otherwise, No action is required if traffic recovers. If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative."
"BACKPLANE_BUS_ASIC","4","EARL_BUS_SYNC_ERR","Failed to sync Earl bus, Backplane Bus Asic version [dec]","The backplane bus ASIC in the line card failed to synchronize with the EARL bus.","If traffic recovers, no action is required. Otherwise, if the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative.)"
"BACKPLANE_BUS_ASIC","4","UNEXPECTED_VERSION","Unexpected Backplane Bus ASIC version.","The line card is unable to recognize the version of the Hyperion ASIC.","No action is required if traffic passes through the line card. Otherwise, check the Bug Toolkit on Cisco's web site to determine a version in which the bug is fixed and upgrade accordingly. If traffic does not pass after the upgrade, enter the show platform hardware hyperion all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BACKPLANE_BUS_ASIC","5","BUS_MODE_CHANGE","The System Switching Bus Mode changed to %s mode","The System Switching Bus Interface device has changed switching bus modes.","The Supervisor has instructed this linecard to change the mode on the switching bus. No action is required from the user."
"BACKPLANE_BUS_ASIC","5","BUS_MODE_CHANGE","The System Switching Bus Mode changed to [chars] mode","The supervisor engine has instructed this line card to change the mode on the switching bus.","No action is required."
"BACKPLANE_BUS_ASIC","5","BUS_SEQ_ERR","Constellation bus Sequence Error. Resetting Backplane Bus Asic.","The switch processor has detected a sequence error on the backplane bus. A reset sequence from the EARL has been called to recover from this error. System traffic should recover and continue normally.","No action is required if traffic recovers. Otherwise, enter the show platform hardware hyperion all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BACKPLANE_BUS_ASIC","5","DEV_INIT_FAILURE","The Backplane Bus Asic initialization failed","The backplane bus ASIC could not be initialized. As a result, this device is not operational and has been disabled.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BACKPLANE_BUS_ASIC","5","DEV_INTR_INFO","[chars]","This message provides more information about the interrupts from the backplane bus ASIC to the line card CPU.","No action is required if traffic recovers. Otherwise, enter the show platform hardware hyperion all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BACKPLANE_BUS_ASIC","5","DEV_RESET_INFO","[chars]","This message provides more information about the interrupts leading to the reset of the backplane bus ASIC.","No action is required if traffic recovers. Otherwise, enter the show platform hardware hyperion all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BACKPLANE_BUS_ASIC","5","MET_TIMEOUT","Backplane Bus Asic MET table access timeout patch invoked","The linecard experienced an IO-BUS timeout while accessing the MET table. Recovery action taken.","No action is required if traffic recovers. Otherwise, enter the show platform hardware hyperion all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BACKPLANE_BUS_ASIC","5","NULL_DEV_OBJECT","The Backplane Bus Asic device object pointer is set to NULL","The memory location of the backplane bus ASIC device object is invalid. The backplane bus ASIC operation is disabled and the device interrupt is now masked.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BACKPLANE_BUS_ASIC","5","UNEXPECTED_ERRMODE","Unexpected Backplane Bus Asic mode.","The linecard experienced an internal Backplane Bus Asic error condition when operating in flow through mode.","No action is required if traffic recovers. If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative."
"BACKUP_INTERFACE","5","PREEMPT","Preempting interface %s in backup pair (%s, %s), preemption mode is %s","Preempting the current forwarding interface in the backup interface pair.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BAP","4","UNAVAILABLE","%s %s %s in illegal state %d","An internal software error occurred.","Call your technical support representative and report the error message, the system version, and the router configuration. (Use the show version command to obtain the software version.)"
"BAP","4","UNAVAILABLE","Failed to initialize AVL tree, BAP not started","BAP will not be operational and will not be negotiated.","Call your technical support representative and report the error message, the system version, and the router configuration. (Use the show version command to obtain the software version.)"
"BCM","4","UNAVAILABLE","Corrected ECC from L2 cache","A soft-parity error from the Layer 2 cache has been detected and corrected. Normal system operation should continue.","If there is a regular or sustained occurrence of this message, copythe error message exactly as it appears and report it totechnical support representative."
"BCM","4","UNAVAILABLE","Corrected ECC from memory","A soft-parity error from the memory has been detected and corrected. Normal system operation should continue.","If there is a regular or sustained occurrence of this message, copythe error message exactly as it appears and report it totechnical support representative."
"BCM3220","1","UNAVAILABLE","msgtxt_initfail","The hardware failed to initialize correctly.","Repair or replace the controller."
"BCM3220","3","UNAVAILABLE","CM trasmission error occurred. Error Message    %BCM3220-3-UNAVAILABLE: msgtxt_badunit","An internal software error occurred.","If either message recurs, call your technical support representative for assistance."
"BCM3220","3","UNAVAILABLE","msgtxt_ownerror","An Ethernet interface is malfunctioning, or an internal software error occurred.","Repair or replace the controller."
"BCM3220","3","UNAVAILABLE","CM trasmission error occurred. Error Message    %BCM3220-3-UNAVAILABLE: msgtxt_badunit","An internal software error occurred.","If either message recurs, call your technical support representative for assistance."
"BCM3220","3","UNAVAILABLE","msgtxt_ownerror","An Ethernet interface is malfunctioning, or an internal software error occurred.","Repair or replace the controller."
"BDOMAIN","3","UNAVAILABLE","Bridge-domain MAC Security back-end subsystem did not initialize correctly (Reason: %s).","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BDOMAIN","3","UNAVAILABLE","Bridge-domain MAC Table back-end subsystem did not initialize correctly (Reason: %s).","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BDOMAIN","3","UNAVAILABLE","Bridge-domain MAC Table back-end subsystem did not initialize correctly (Reason: %s).","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BEEP","3","UNAVAILABLE","%s %s","This is an internal BEEP library error message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BEEP","3","UNAVAILABLE","%s at %s:%d","The BEEP subsystem had an error and may stop running.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD_CFG","3","MALLOC_CFG","Malloc failure %s %s","malloc failure","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD","3","UNAVAILABLE","Chunk malloc failure - %s - 0x%X","chunk malloc failure","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD","3","UNAVAILABLE","Client not found","client does not exist in client list","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD","3","UNAVAILABLE","Creation of BFD Private Buffer Pool failed","could not create private buffer pool","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD","3","UNAVAILABLE","Failed deleting node %x from wavl tree thread %d","wavl delete failed to a thread.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD","3","UNAVAILABLE","Failed initializing wavl tree.","wavl_init failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD","3","UNAVAILABLE","Failed inserting node %x to wavl tree thread %d (%s)","wavl insert failed to a thread.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD","3","UNAVAILABLE","Failed to create BFD IOU Process","IOU process failed to start","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD","3","UNAVAILABLE","Failed to create BFD PP Process","pseudo-preemptive process failed to start","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD","3","UNAVAILABLE","Failed to get kadis timer tick to start kadis timer.","kadis failed to get timer tick","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD","3","UNAVAILABLE","Failed to malloc space for wavl tree.","wavl tree malloc failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD","3","UNAVAILABLE","Failed to start Kadis. Status %d","kadis failed to start","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD","3","UNAVAILABLE","Illegal interface %d%s","interface number is out of range for platform","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD","3","UNAVAILABLE","Interface %s(%d) already in use","interface number is already in use","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD","3","UNAVAILABLE","Invalid queue element - %s","invalid queue element","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD","3","UNAVAILABLE","Invalid version type","invalid version type","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD","3","UNAVAILABLE","Neighbor address type not specified as ADDR_IP(%d), %d","client called bfd_neighbor with uninitialized addrtype","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD","3","UNAVAILABLE","Unable to destroy %s %s","chunk destroy failure","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD","3","UNAVAILABLE","bfd_pak_coalesce - %s failed","could not obtain or coalesce packet buffer","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD","6","UNAVAILABLE","BFD discrminators exhausted. No more sessions can be created.","Max. discriminators assigned","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD","6","UNAVAILABLE","BFD transmit detected on standby","BFD packet transmission on standby","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD","6","UNAVAILABLE","Maximum session creation limit %d reached.","Max. sessions created","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD_CFG","3","MALLOC","Malloc failure %s","malloc failure","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD_CFG","3","WAVL_DELETE","Wavl delete failed for %p","wavl delete failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD_CFG","3","WAVL_INIT_FAIL","Failed initializing wavl tree","wavl_init failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD_CFG","3","WAVL_INSERT_FAIL","Wavl insert failed %s %s","wavl insert failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFDFSM","3","UNAVAILABLE","Invalid current state 0x%X","state machine invalid state","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFDFSM","3","UNAVAILABLE","Invalid event_id 0x%X","state machine invalid event","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFDFSM","3","UNAVAILABLE","Invalid machine pointer 0x%X","state machine invalid pointer","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFDFSM","3","UNAVAILABLE","Unable to apply event 0x%08X","state machine transition failure","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFDFSM","3","UNAVAILABLE","obj: [0x%08X] event_id: [0x%08X] er_p: [0x%08X] arg: [0x%08X] session state %s - %s","state machine invalid transition","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD_HA","2","CF","[chars][dec]","An error occurred with the CompactFlash device.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD_HA","2","RESOURCE","[chars]","An error occurred in a system resource.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD_HA","2","RF","[chars][dec]","An error occurred in the RF system.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD_HA","3","DELSESS","[chars][dec]","An error occurred while deleting a session.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD_ISSU","2","GET_BUFFER","BFD ISSU client failed to get buffer for message. Error: [dec] ([chars])","The BFD ISSU client was unable to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show checkpoint client commands and your pertinent troubleshooting logs."
"BFD_ISSU","2","INIT","BFD ISSU client initialization failed to [chars]. Error: [dec] ([chars])","The BFD ISSU client could not be initialized. This initialization failure must be addressed before an in-service software upgrade or downgrade can be performed successfully. Otherwise, a software upgrade or downgrade will result in downtime.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD_ISSU","2","SEND_NEGO_FAILED","BFD ISSU client failed to send negotiation message. Error: [dec] ([chars])","The BFD ISSU client was unable to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show checkpoint client commands and your pertinent troubleshooting logs."
"BFD_ISSU","2","SESSION_NEGO","BFD ISSU client encountered unexpected client nego_done. Error: [dec] ([chars])","An ISSU-compliant client transitions through a series of internal states. The BFD ISSU client encountered a client negotiation done state that was unexpected. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"BFD_ISSU","2","SESSION_REGISTRY","BFD ISSU client failed to register session information. Error: [dec] ([chars])","The BFD ISSU client was unable to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"BFD_ISSU","3","INVALID_SESSION","BFD ISSU client does not have a valid registered session.","The BFD ISSU client does not have a valid registered session.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"BFD_ISSU","3","MSG_SIZE","BFD ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] ([chars])","The BFD ISSU client was unable to calculate the MTU for the specified message. The BFD ISSU client is not able to send the message to the standby device.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"BFD_ISSU","3","SESSION_UNREGISTRY","BFD ISSU client failed to unregister session information. Error: [dec] ([chars])","The BFD ISSU client was unable to unregister session information.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"BFD_ISSU","3","TRANSFORM_FAIL","bfd ISSU client [chars] transform failed for message [dec]'. Error: [dec] ([chars])","The BFD ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In either case, the BFD state between the active device and the standby device is not identical.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"BFD_MAP","3","MALLOC","Malloc failure %s","malloc failure","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"BFD_MAP","3","MALLOC_MAP","Malloc failure %s %s","malloc failure","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"BFD_MAP","3","WAVL_DELETE","Wavl delete failed for %p","wavl delete failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"BFD_MAP","3","WAVL_INIT_FAIL","Failed initializing wavl tree","wavl_init failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"BFD_MAP","3","WAVL_INSERT_FAIL","Wavl insert failed %s %s","wavl insert failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"BFD_MPLS","3","CFC_REG_FAIL","CFC registration failed rc %d","CFC registration failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"BFD_MPLS","3","CFC_UNREG_FAIL","CFC unregistration failed rc %d","CFC unregistration failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"BFD_MPLS","3","TP_LSP","Session not created for intf %s/lsp %d. In-label %u in use for intf %s/lsp %d","BFD session mismatch.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"BFD_SCALE","6","INSUFFICIENT_RESOURCES","Configuration not changed, exceeds maximum resource limit.","The configuration could not be changed due to a resource limitation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD_SCALE","6","RESOURCES_EXHAUSTED","BFD adjacency can not be created due to resource limitation.","A BFD adjacency cannot be created due to a resource limitation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD_TEST","3","BAD_ADDR_TYPE","Invalid address type [dec]","The BFD test process detected an invalid address type.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD_TEST","3","BAD_TYPE","Invalid session type [dec]","The BFD test process detected an invalid session type.Explanation    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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message    %BFD_TEST-3-WAVL_INIT_FAIL: Failed initializing wavl tree. Explanation    The BFD test process was unable to initialize a wrapped AVL (WAVL) tree.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD_TEST","3","WAVL_INSERT_FAIL_IPV4","Failed inserting neighbor address %30i to wavl tree thread [dec]","The BFD test process was unable to insert an IPv4 node in a wrapped AVL (WAVL) tree.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD_TEST","3","WAVL_INSERT_FAIL_IPV6","Failed inserting neighbor address %30P to wavl tree thread [dec]","The BFD test process was unable to insert an IPv6 node in a wrapped AVL (WAVL) tree.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD_TEST","3","WAVL_TREE","Failed to malloc space for wavl tree.","The BFD test process was unable to allocate memory for a wrapped AVL (WAVL) tree.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD_TEST","3","WAVL_WALK_FAIL","wavl_walk failed while walking wavl tree thread [dec] interface [dec]","A thread failed while walking the wrapped AVL (WAVL) tree.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD_TEST","7","FSM_STATE","Session [[IP_address],[IP_address],[chars],[int]], event [chars], state [chars] -> [chars]","State information is shown in the message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BFD_TEST","7","RECV_START","First packet has come in.","The first packet has been received.","This is an informational message only. No action is required."
"BGP","2","INSUFMEM","Insufficient memory for [chars] entry","The requested operation could not be accomplished because of a low memory condition.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"BGP","3","ADDROUTE","Unable to add route for [chars] to radix trie","An addition to the radix trie could not be completed because of an error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BGP","3","BADMASK","Attempt to install route for %i without valid mask in [chars]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BGP","3","BADROUTEMAP","Bad parameters in the route-map [chars] applied for [chars]","The route map contains incorrect entries.","Correct the route map."
"BGP","3","BGP_INCONSISTENT","[chars] Inconsistent [chars]","An error was detected in a data structure. This is an internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BGP","3","DELPATH","Attempted to delete path from an empty net for [chars]","A BGP path could not be deleted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BGP","3","DELROUTE","Unable to remove route for [chars] from radix trie","The system was unable to delete a route from the radix trie.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BGP","3","INSUFCHUNKS","Insufficient chunk pools for [chars], requested size [dec]","The static chunk pools size is too small.","Collect the chunk and BGP summary. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BGP","3","INVALID_MPLS","Invalid MPLS label ([dec]) received in update for prefix [chars] from [chars]","An invalid MPLS label was found in a received BGP message. This indicates that there is some problem on the remote router.","Check the configuration of the remote router."
"BGP","3","MARTIAN_IP","[chars] Martian prefix [chars] in [chars]","A Martian prefix was found in the BGP message. This indicates that there is some problem on the remote router.","Check the configuration of the remote router."
"BGP","3","MAXPFXEXCEED","No. of prefix received from [chars][chars][chars] (afi [dec]): [dec] exceed limit [dec]","The number of prefixes received from a neighhor exceeeds the configured limit. The message displays the session number or VRF identifier, if applicable.","Check the number of prefixes received from the neighbor and determine whether the limit should be increased."
"BGP","3","NOBITFIELD","Could not allocate bitfield. Cannot open session to [chars]","The allocation of a neighbor index for this neighbor has failed because of a low memory condition.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"BGP","3","NOTIFICATION","[chars] neighbor [chars] [dec]/[dec] ([chars]) [dec] bytes [chars]","An error condition has been detected in the BGP session. A notification message is being sent or received and the session will be reset. This message appears only if the log-neighbor-changes command is configured for the BGP process.","This message represents an error in the session and its origin should be investigated. If the error is reported periodically, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BGP","3","ORF_PFXLIST","Received misformatted prefixlist ORF from [chars]","The received prefix list outbound route filter (ORF) is misformatted.","Check the prefix list ORF implementation on the neighboring router."
"BGP","3","PER_VRF_AGGR","pervrfaggr label: [chars]","The TFIB asks for a label for a prefix in the VRF routing table. The per-VRF-aggregate label will be assigned to the connected type or BGP aggregate prefix when BGP runs a best-path calculation. This message might appear when a prefix changes to a connected type or BGP aggregate type.","No action is required. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BGP","3","RADIXINIT","Radix trie initialization failed","Initialization of the radix tree could not be accomplished because of a low memory condition.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"BGP","4","AFIMPORT","[chars] prefixes imported to [chars] vrf reached the limit [dec]","The number of prefixes imported from an address family to a VRF has reached the configured limit","Check the number of imported prefixes from the address family and determine whether the limit should be increased or if the ip vrf import route-map command is configured correctly."
"BGP","4","ATTRNULL","A NULL attribute has been assigned to a path","The path was incorrectly assigned a value of NULL instead of a valid attribute.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BGP","4","BFD_NOT_ONEHOP","BFD is supported for single hop neighbors. [chars] is not single hop neighbor","Bidirectional forwarding detection (BFD) is not enabled because the configured neighbor is not a single hop. BFD is supported only for single hop neighbors.","Unconfigure BFD from BGP."
"BGP","4","MAXDYNNBR","BGP:DN: Cannot create new neighbor [chars], for range [chars]: maximum number of [dec] dynamic neighbors limit reached","The number of dynamically created subnet range neighbors has reached a warning limit.","Check the number of listen range limit configured for dynamic subnet neighbors and determine whether the limit should be increased."
"BGP","4","MAXPFX","No. of prefix received from [chars][chars][chars] (afi [dec]) reaches [dec], max [dec]","The number of prefixes received from a neighhor has reached a warning limit. The message displays the session number or VRF identifier, if applicable.","Check the number of prefixes received from the neighbor and determine whether the limit should be increased."
"BGP","4","MAX_EXTCOMM_EXCEED","Exceeded limit of [dec] extended communities per advertised prefix","An attempt was made to advertise a prefix with an extended community attribute containing more extended communities than the allowed limit.","Reduce the configured number of route targets or other extended communities that will be added to prefix advertisements."
"BGP","4","NBRTRACK","Route Tracking failed on memory. Neighbor tracking for route-fall-over will stop","The route tracking system failed to allocate memory. Neighbor route fallover will stop tracking neighbor routes in order to free some memory.","If the system is stable, then reconfigure neighbor route fallover. If this message reappears, neighbor route fallover has been unconfigured."
"BGP","3","NEGCOUNTER","Prefix-accepted counter negative for peer [chars], prefix [chars]","The counter value for accepted prefixes is less than zero, which is an illegal value. This indicates an internal software error.","Reset the session."
"BGP","4","NORTRID","BGP could not pick a router-id. Please configure manually.","The BGP router ID has not been manually configured and BGP is unable to allocate a router ID from the IPv4 address of one of its interfaces.","Make sure that at least one interface is up and has a valid IPv4 address, or configure the router ID manually."
"BGP","4","RIDSYNC","BGP routes are redistributed to OSPF. For synchronization to work, you must manually configure the BGP router-id to be the same as the OSPF router-id.","For synchronization to work, the BGP router ID must be the same as the OSPF router ID at all times that the router is up.","If synchronization is turned on between one instance of OSPF and BGP, make sure to manually configure a BGP router ID that is identical to the router ID of the particular OSPF instance."
"BGP","4","VPNV4NH_MASK","Nexthop %i may not be reachable from neigbor [chars] - not /32 mask","We are sending to an IBGP neighbor a VPNv4 route whose next hop address is our loopback, which does not have a 32 bit mask. In addition, we are using OSPF on this loopback, and the OSPF network type of this interface is loopback. OSPF advertises this address as a host route (with mask /32) regardless of what mask is configured. This conflicts with the Tag Distribution Protocol (TDP), which uses configured masks, so our TDP neighbors may not receive a tag for this route. As a result, connectivity could be lost between sites that belong to the same VPN.","Configure the loopback used as the next hop with a 32 bit IP host mask (/32), or configure the ip ospf network point-to-point command on this loopback."
"BGP","4","VPN_NH_IF","Nexthop [chars] may not be reachable from neigbor [chars] - not a loopback","We are sending to an IBGP neighbor a VPN route whose the next hop is one of our directly-connected physical interfaces. The label for the next hop address may be removed in the MPLS cloud one hop soon. Since the P routers do not have VPN information, they do not know where to forward packets with the BGP label. As a result, connectivity could be lost between VPN sites.","Use loopback interfaces as the next hops for VPN IBGP neighbors."
"BGP","5","ADJCHANGE","neighbor [chars][chars][chars][chars] [chars]","A BGP neighbor has either come up or gone down, as indicated. This message appears only if the log-neighbor-changes command is configured for the BGP process.","This informational message normally appears as routers and BGP neighbors go up or down. However, unexpected neighbor loss might indicate high error rates or high packet loss in the network and should be investigated."
"BGP","5","DAMPENING_DECAY_TIME","Decay time from maximum penalty to suppress penalty is [dec] secs. Maximum penalty: [dec], suppress penalty: [dec]","The configured dampening parameters may not be feasible. The time window between maximum penalty and suppress penalty may be low.","If the decay time from maximum penalty to suppress penalty is too low, increase the half-life time or the maximum penalty values."
"BGP","5","DAMPENING_HIGH_MAX_PENALTY","Maximum penalty ([dec]) is more than allowed maximum ([dec]). Dampening is OFF","The configured dampening parameters may not be feasible. The maximum penalty is more than the allowed maximum. As a result, dampening will be off.","Depending on the value of the maximum penalty, adjust the maximum suppress time. Because the maximum penalty is more than the allowed maximum, reduce maximum suppress time. The maximum penalty should be greater than the suppress penalty but less than the maximum allowable penalty."
"BGP","5","DAMPENING_LOW_MAX_PENALTY","Maximum penalty ([dec]) is less than suppress penalty ([dec]), Dampening is OFF","The configured dampening parameters may not be feasible. The maximum penalty is less than the configured suppress penalty. As a result, dampening will be off.","Depending on the value of the maximum penalty, adjust the maximum suppress time. Because the maximum penalty is less than the suppress penalty, increase the maximum suppress time. The maximum penalty should be greater than the suppress penalty but less than the maximum allowable penalty."
"BGP","5","VERSION_WRAP","bgp version wrapped of [chars]","The BGP table version has reached its maximum value and has wrapped around. The message describes this event.","This message is informational. However, frequent occurrences of such an event might indicate high error rates or high packet loss in the network and should be investigated."
"BGP","6","ASPATH","[chars] AS path [chars] received from [chars]: [chars]","The remote BGP peer sent an update with an invalid autonomous system (AS) path.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BGP","6","BIGCHUNK","Big chunk pool request ([dec]) for [chars]. Replenishing with malloc","This is an informational message describing an internal software operation. If the static chunk pool size can not service the request, it will be serviced with a memory allocation (malloc) process.","No action is required."
"BGP","6","NEXTHOP","Invalid next hop (%i) received from [chars]: [chars]","The remote BGP peer sent a route with an illegal next hop. The route was ignored.","No action is required."
"BGP_MPLS","3","GEN_ERROR","[chars]","This message describes a general runtime error related to BGP MPLS.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BGP_MPLS","3","IPRMCONNECT","[chars]","BGP VPNv4 failed to register to the IP rewrite manager (IPRM) component.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BGP_MPLS","3","LABELALLOC","[chars]","An MPLS label could not be allocated for a prefix.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BGP_MPLS","3","LSDCONNECT","[chars]","BGP VPNv4 failed to register to the MPLS forwarding component.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BGP_MPLS","3","NBR_ROUTE","[chars]","An error occurred in manipulating the BGP neighbor route needed for MPLS operations.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BGP_MPLS","3","PERVRF","pervrfaggr label: [chars]","An error occurred related to the per-VRF label feature.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BGP_MPLS","3","PER_VRF_AGGR","pervrfaggr label: [chars]","An error occurred related to the per-VRF aggregate label feature.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BGP_MPLS","3","SIZEMISMATCH","Label table size ([dec]) mismatch, checkpt key creation failed","A BGP MPLS label table size mismatch was detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BGP_MPLS","3","VPN_REWRITE","[chars]","An error occurred in installing, updating, or removing a VPN rewrite entry in the MPLS forwarding tabl.e","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BGP_MPLS","4","LABELALLOC","Label allocation failure","A resource limitation was encountered while allocating a local label on the router.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BGP_MPLS","7","IASLABELALLOC","Failed to create rewrite for prefix [chars], reason: [chars]","A BGP MPLS VPN rewrite creation failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BGP_MPLS","7","IPv4LABELALLOC","Failed to allocate label for IPv4 prefix %i/[dec]","A BGP MPLS IPv4 label allocation failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BIT","4","UNAVAILABLE","bit %d is not in the expected range of %d to %d","An invalid request was detected by the bitlist subsystem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BPE","3","UNAVAILABLE","Invalid IDB type passed [%d - %s]","Idb type passed is not supported by this function","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BPE","3","UNAVAILABLE","Invalid MAC for slot [%d/%d/%d]","Could not get proper MAC address for a given slot/subcard/port","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BPE","3","UNAVAILABLE","Malloc Failed [%s]","Could not allocate memory","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BPE","3","UNAVAILABLE","Null idb pointer [%s:%x]","Interface pointer is not initialized","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BPE","3","UNAVAILABLE","Port number[%d] is not valid","Port number is invalid","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BPE","3","UNAVAILABLE","Slot number[%d] is not valid","Slot number is invalid","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BRI","1","UNAVAILABLE","msgtxt_initfail","The hardware failed to initialize correctly.","Repair or replace the controller."
"BRI","1","UNAVAILABLE","msgtxt_nomemory","The requested operation could not be accomplished because of a low memory condition.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"BRI","4","UNAVAILABLE","msgtxt_initfail","ISDN leased line requires an ISDN switch type configure.","Choose and configure a BRI switch type; if unsure, choose any switch."
"BRIMUX","1","UNAVAILABLE","Software error: %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BRIMUX","3","UNAVAILABLE","Slot %d %s","A BRIMUX firmware problem may be present.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BRIMUX","3","UNAVAILABLE","Slot %d BRIC, failed to acknowledge download data block %d","A BRIMUX firmware problem may be present.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BRIMUX","3","UNAVAILABLE","Slot %d BRIC, failed to send upload data block %d","A BRIMUX firmware problem may be present.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BRIMUX","3","UNAVAILABLE","Slot %d BRIC, upload data length read %d, truncate to %d bytes","A BRIMUX firmware problem may be present.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BRIMUX","3","UNAVAILABLE","Slot %d BRIC, wrong block %d for data upload, expect %d","A BRIMUX firmware problem may be present.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BRIMUX","3","UNAVAILABLE","Slot %d BRIC, wrong upload address received 0x%x, requested 0x%x","A BRIMUX firmware problem may be present.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BRIMUX","3","UNAVAILABLE","Slot %d DPM, test failed at offset 0x%x, expect 0x%x, read 0x%x","A BRIMUX board hardware problem may be present.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BRIMUX","4","UNAVAILABLE","Slot %d BRIC, lost heartbeat for %d seconds","A BRIMUX board hardware or firmware problem may be present.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BRIMUX","5","UNAVAILABLE","B%d of BRI%d on slot %d BRIC, changed state to %s","A B-channel on the BRIMUX board changed state.","No action is required."
"BRIMUX","5","UNAVAILABLE","BRI%d on slot %d BRIC, changed state to %s","A port on the BRIMUX board changed state.","No action is required."
"BRIMUX","5","UNAVAILABLE","Slot %d BRIC, changed state to %s","A BRIMUX board changed state.","No action is required."
"BSC","2","UNAVAILABLE","No buffers available on interface %s.","This message indicates that memory in the router was exhausted.","Perform diagnostics on the router to locate the subsystem or interface responsible for consuming memory. The only method that will clear this situation is to reload the router."
"BSC","3","UNAVAILABLE","Line state Tx when receiving %s on line %s","An unexpected receive occurred during a transmission.","Verify that the line has been consistently defined in regards to the carrier. If a message report was sent, hard-on stop and start the bisynchronous interface in question."
"BSC","3","UNAVAILABLE","Peer %s is incorrect type","This message occurs only when BSC local-ack is configured. It indicates the serial interfaces that are using the BSTUN tunnel are configured incorrectly, that is, both have been configured as a secondary.BSR MessagesThis section contains Bootstrap Router (BSR) messages.BSR-5Error Message    %BSR-5-CBSR_REMOVED: Candidate-BSR on interface [chars] has been removed Explanation    The interface card has been removed.","No action is required."
"BSR","5","CRP_REMOVED","Candidate-RP on interface [chars] has been removed","The interface card has been removed.","No action is required."
"BSTUN","2","UNAVAILABLE","Interface %s, no buffer available to %s","A memory shortage existed at the time that the configuration command was issued. This condition is rare and, under normal conditions, temporary.","Reconfigure the BSTUN group. If memory shortages persist, call your technical support representative for assistance."
"BSTUN","3","UNAVAILABLE","%s: bad len or unknown op, op %d, len %d","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BSTUN","3","UNAVAILABLE","%s: peer %s, wrong magic, mine %x, theirs %x","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BSTUN","3","UNAVAILABLE","%s: sent %s to %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BSTUN","3","UNAVAILABLE","%s: wrong magic, mine %x, theirs %x (%d)","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BSTUN","3","UNAVAILABLE","CONN: Peer %s, illegal state %d","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BSTUN","3","UNAVAILABLE","CONN: bad connection (%d), peer: %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BSTUN","3","UNAVAILABLE","Could not setup interface for protocol %s","BSTUN was unable to start the interface for handling the specified protocol traffic.","If this message appears while you are configuring BSTUN, check for other system errors, such as no available memory in the router, or the interface shutting down. If no obvious problem can be detected, record all the displayed values and any other BSTUN error messages, and contact your technical support representative."
"BSTUN","3","UNAVAILABLE","No bstun group defined on interface %s","An action was taken that requires the previous definition of a BSTUN group number.","Make sure encapsulation bstun and the bstun group have been defined for the interface."
"BSTUN","3","UNAVAILABLE","No peer configured to route frame with destination address %s (bstun group %d)","A BSTUN route has not been configured for the frame with a destination address.","If this message appears while you are debugging bstun, it indicates that no specific bstun route has been configured for the frames being received with the device address listed in the packet debug trace. You may choose to configure a bstun route, or ignore this message."
"BSTUN","3","UNAVAILABLE","Unknown protocol event %d on interface %s","An event passed to the BSTUN layer for processing could not be decoded.","Perform a hard restart on the indicated interface."
"BSTUN","3","UNAVAILABLE","passive open from %i(%d) - %d failed","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BSTUN","4","UNAVAILABLE","%s: sent %s to ([%u])%i","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BSTUN","4","UNAVAILABLE","Cannot define duplicate route on the same group","This route command is defined on another interface belonging to the same group. Cannot define duplicate route on the same group","Consider defining a new group and moving this interface onto that group"
"BSTUN","4","UNAVAILABLE","Peer %s, wrong state %d (%d)","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BSTUN","6","UNAVAILABLE","%s %s, %i(%d)","This route closed a BSTUN connection with a remote peer.","Examine this router to see why it closed this connection with this peer. This can be caused by normal events, such as reconfiguration."
"BSTUN","6","UNAVAILABLE","%s: %s: %s, op %x, len %d","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BSTUN","6","UNAVAILABLE","%s: peer %s opened, [previous state %s]","A connection attempt to a remote peer completed successfully (OPENED, PASSIVE-OPEN) or is in the process of being opened (OPENING). This is good, expected behavior.","Informational message only. No action required."
"BSTUN","6","UNAVAILABLE","CONN: opening peer %s, %d","A connection attempt to a remote peer completed successfully (OPENED, PASSIVE-OPEN) or is in the process of being opened (OPENING). This is good, expected behavior.","Informational message only. No action required."
"BSTUN","6","UNAVAILABLE","CONN: peer %s open failed, %s [%u]","An attempt to connect to a remote TCP BSTUN peer failed.","Verify that the remote peer is accessible from this router, that it is running software capable of supporting BSTUN, and that it is configured correctly."
"BSTUN","6","UNAVAILABLE","PHDR: reconnect from peer %s","A remote peer reestablished a connection to this router.","Informational message only. No action required."
"BSTUN","6","UNAVAILABLE","Process terminating. Due to signal %d. Subcode %d. Address %x.","The BSTUN background process is terminating.","If this message appears while you are unconfiguring BSTUN, no action is required. Otherwise, record all the displayed values and any other BSTUN error messages, and contact your technical support representative."
"BSTUN","6","UNAVAILABLE","passive open %i(%d) - %d","A connection attempt to a remote peer completed successfully (OPENED, PASSIVE-OPEN) or is in the process of being opened (OPENING). This is good, expected behavior.","Informational message only. No action required."
"BSTUN","6","UNAVAILABLE","peer %s closed [previous state %s]","A remote peer closed a BSTUN connection with this router.","Examine the other router to see why it closed this connection with this peer. This can be caused by normal events, such as reconfiguration."
"BSTUN","6","UNAVAILABLE","shutting down peer %s on %s","A connection to a remote peer is being shut down. This is typically the result of user intervention in BSTUN reconfiguration or disabling. This is good, expected behavior.","Informational message only. No action required."
"BUFCAP","3","ACTIVE_CAPPOINT","Invalid operation was attempted on an active capture point %s.","Invalid operation was attempted on an active capture point.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BUNDLES","3","ALLOCATION","Bundle allocation error: [chars]","An internal software error occurred. This error is probably caused by a low-memory condition.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BUNDLES","3","PLATFORMSPACE","Platform attempted to access unreserved space","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"BUNDLES","3","TYPENOTISSUAWARE","Bundle type [chars] must be ISSU aware to send to slot(s) [chars]","The bundle type is not In Service Software Upgrade (ISSU) aware so cannot be distributed to a slot with which ISSU negotiation has occurred. This indicates a design problem that requires code changes to fix.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C2950_MONITOR","3","C2950MONITOR_UNKNOWN_PARAM","Unknown trap type:[dec] received in emt_call function.","An unknown trap type occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C1400_PCI","3","UNAVAILABLE","Conversion of address (0x%x) to big_endian failed.","A software error occurred in trying to determine PCI device addressing.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C1400_PCI","3","UNAVAILABLE","Conversion of address (0x%x) to little_endian failed.","A software error occurred in trying to determine PCI device addressing.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C1400_PCI","3","UNAVAILABLE","Conversion of address (0x%x) to little_endian is not supported","Conversion of an address to an equivalent little endian address is not supported by QSpan PCI device.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C1400_PCI","3","UNAVAILABLE","PCI Bus bridge does not exist","The device initialization code was unable to locate the PCI Bus bridge. It may be necessary to replace the board.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C1400_PCI","3","UNAVAILABLE","PCI Configuration Read Cycle Failed for bus %d, Device %d, function %d,register %d","The system could not read from the PCI Bus. It may be necessary to replace the board.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C1400_PCI","3","UNAVAILABLE","PCI Configuration Write Failed for bus %d, Device %d, function %d, register %d","The device initialization code was unable to write to the PCI Bus. It may be necessary to replace the board.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C1600","4","UNAVAILABLE","Unable to load images or communicate over interface","The operation might have failed because of a transient network problem.","Retry the operation. If the problem persists, call your technical support representative for assistance."
"C1600","4","UNAVAILABLE","Interface %d, (0-1 Onboard interfaces 2=WIC) Invalid interface (Unknown, Uninitialized or Bad Cookie value read)","Your router is functional; however, there is an interface that the software does not recognize.","Copy the error message exactly as it appears, and report it to your technical support representative."
"C1700","1","UNAVAILABLE","System detected OVERTEMPERATURE condition. Putting the system in Power save mode and going to rommon. Please resolve cooling problem and restart system!","The environmental monitor detected a high-temperature condition.","Make sure that the room temperature is not too high and that air flow to the card is not blocked. If this condition persists, the environmental monitor might shut down the system. Call your technical support representative for assistance, if necessary."
"C1700","1","UNAVAILABLE","The shutdown button is pressed, MRP will be into shutdown mode","The machine enters the checkstop state, which stops all the tasks and has to be hardware reset in order to bring back","Power cycle reset"
"C1700","3","UNAVAILABLE","Could not download startup configuration from the tftp server.","Startup configuration could not be downloaded from the tftp server. The specified file might not be available or the server might be unreachable.","Check the file name and availability on the server. Check if the network is up and the tftp server could be reached."
"C1700","3","UNAVAILABLE","Invalid Port Adaptor type (%d) reported for mainboard","The 'virtual' port adaptor type derived from the mainboard type isnot one of the supported types. It may be that this mainboard is a newmainboard type and the software release you are running does not supportthe new mainboard type.","Copy the error message exactly as it appears, and report it to your technical support representative."
"C1700","3","UNAVAILABLE","TDM Module does not support WAN Interface module %x in slot %d","The WAN interface card was not recognized by the TDM module. Internal connections required for this WAN interface card to function were not made","Copy the error message exactly as it appears, and report it to your technical support representative."
"C1700","3","UNAVAILABLE","The IOS image loaded supports voice. The platform you are running is not voice capable.","The voice-capable IOS detects it is running on a platform which does not support voice.","Check the image and the platform. If you need to use voice, you should get a c1750. If you do not need voice, you should load an image which does not include voice."
"C1700","3","UNAVAILABLE","The eeprom version field has an invalid entry (%c)","The Cookie has an invalid version number and could possibly becorrupt.C1700-5Error Message    %C1700-5-UNAVAILABLE: NVRAM configuration is not supported. Explanation    Startup configuration could not be stored in NVRAM. It is stored in the SBC","The config is automatically saved by the management application. It could also be saved by copying the running config to a server using ftp."
"C1700_EM","1","UNAVAILABLE","%s","An error occured in the application using VPN Module.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C1700_EM","1","UNAVAILABLE","%s creation failed for slot %d","The VPN Module driver could not allocate memory for the specified data structure.","Consider adding more memory. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C1700_EM","1","UNAVAILABLE","%s packet buffer, pak=0x%08x","A software or hardware error occurred. The VPN Module driver detected that the buffer ring is in an inconsistent and unrecoverable state.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C1700_EM","1","UNAVAILABLE","%s received a packet with size %d.","Packet exceeds MTU size","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C1700_EM","1","UNAVAILABLE","Alignment failure on packet buffer: 0x%08x","A software error occurred. The VPN Module driver detected that the buffer is not aligned correctly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C1700_EM","1","UNAVAILABLE","Multiple VPN Modules not supported, (%d) found","Multiple VPN Modules not supported","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C1700_EM","1","UNAVAILABLE","Slot %d: %s","The VPN Module driver failed to initialize at the specified point.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C1700_EM","1","UNAVAILABLE","VPN Module CGX mailbox bad state: found=%x, expect=%x","VPN Module CGX mailbox bad state.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C1700_EM","1","UNAVAILABLE","VPN Module Command Processor alignment error: (%s=%#X)","VPN Module Command Processor alignment error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C1700_EM","1","UNAVAILABLE","VPN Module Command Processor initialization failed: (%s)","VPN Module Command Processor initialization failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C1700_EM","1","UNAVAILABLE","VPN Module cannot lock semaphore sem=%d","VPN Module cannot lock semaphore.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C1700_EM","3","UNAVAILABLE","VPN Module Command Processor error: (%s)","VPN Module Command Processor error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C1700_EM","3","UNAVAILABLE","VPN Module Command Processor got event: major=%d, minor=%d","VPN Module Command Processor error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C1700_EM","3","UNAVAILABLE","VPN Module DSP is not responding.","VPN Module DSP is not responding.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C1700_EM","3","UNAVAILABLE","VPN Module could not read its own NVRAM configuration: (%d)","VPN Module NVRAM error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C1700_EM","3","UNAVAILABLE","VPN Module failed its onboard memory test. Page 0x%X, Addr 0x%X, Wrote 0x%X, Read 0x%X","VPN Module memory test error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C1700_EM","3","UNAVAILABLE","VPN Module firmware download failed: %s","VPN Module firmware download failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C1700_EM","3","UNAVAILABLE","VPN Module returned bad boot status: (%d)","VPN Module boot sequence error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C1700_EM","6","UNAVAILABLE","%s shutting down","The specified VPN Module is shutting down. It may have been physically removed.","This is an informational message only. It occurs in normal operation."
"C2600","1","UNAVAILABLE","System detected OVERTEMPERATURE condition. Putting the system in Power save mode and going to rommon. Please resolve cooling problem and restart system!","The environmental monitor detected a high-temperature condition.","Make sure that the room temperature is not too high and that air flow to the card is not blocked. If this condition persists, the environmental monitor might shut down the system. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C2600","3","UNAVAILABLE","Can't allocate MAC address for interface %u/%u","All the available MAC addresses for the system have been allocated.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C2600","3","UNAVAILABLE","Detected invalid NVRAM size: %d bytes","The detected size of NVRAM is not one of the supported sizes.The NVRAM may be bad.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C2600","3","UNAVAILABLE","Failed to erase config due to internal error","Password protection feature failed to erase config due to internal error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C2600","3","UNAVAILABLE","Invalid Port Adaptor type (%d) reported for mainboard","The 'virtual' port adaptor type derived from the mainboard type isnot one of the supported types. It may be that this mainboard is a newmainboard type and the software release you are running does not supportthe new mainboard type.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C2600","3","UNAVAILABLE","PCI Configuration Read Cycle Failed for bus %d, Device %d, function %d, register %d","A PCI Bus Configuration Read cycle failed. The mainboard needs to be replaced.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C2600","3","UNAVAILABLE","PCI Configuration Write Cycle Failed for bus %d, Device %d, function %d, register %d","A PCI Bus Configuration Write cycle failed. The mainboard needs to be replaced.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C2600","3","UNAVAILABLE","c2600_big_endian_addr: Attempted conversion of invalid address (0x%x)","A software error occurred in trying to determine PCI device addressing. This is most likely a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C2600","3","UNAVAILABLE","c2600_little_endian_addr: Attempted conversion of invalid address (0x%x)","A software error occurred in trying to determine PCI device addressing. This is most likely a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C2600","3","UNAVAILABLE","get_pci_dev_num: Invalid bay (%d) or device number offset (%D)","A software error occurred in trying to determine PCI device addressing. This is most likely a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C2600","3","UNAVAILABLE","pas_get_device_subunit: Invalid PCI device number: %d","A software error occurred in trying to determine PCI device addressing. This is most likely a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C2600_MAINBOARD_ASYNC_PQUICC","3","UNAVAILABLE","No memory for %s of unit %d","The router does not have enough memory to perform the function","Consider adding more shared memory. Copy the error message exactly as it appears, and report it to your technical support representative."
"C2950_MONITOR","3","UNAVAILABLE","Unknown trap type:%d received in emt_call function.","Unknow trap type. Some feature requires this trap type to be handledError Message    %C29ATM-3-UNAVAILABLE: Cannot create VCC %s.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C29ATM","3","UNAVAILABLE","Cannot create VCC for %s, run out of VCD","The module was unable to create a VCC for the specified service.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C29ATM","3","UNAVAILABLE","The IF index array is full, count 0x%x 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message    %C29ATM-3-UNAVAILABLE: The module attempted to transmit frame on a closed or non-existent VCD: vcd = %dRecommended 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.C29ATM-4Error Message    %C29ATM-4-UNAVAILABLE: %s discarded because it is not associated with a VCD: vpi = %d vci = %d","An OAM cell or an AAL5 frame was discarded because it was not associated with a VCD","Check the configuration of your ATM switch."
"C29ATM","4","UNAVAILABLE","%s: %s : %d","Address Table Managment","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C29ATM","4","UNAVAILABLE","%s: %s : %e","Address Table Managment","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C29ATM","4","UNAVAILABLE","%s: %s","ATM IDB","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C29ATM","4","UNAVAILABLE","AAL5 discarded because it is too large to buffer: vpi = %d, vci = %d, size = %d","An AAL5 frame destined for IOS was discarded because it was too large to buffer.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C2KATM","0","UNAVAILABLE","Host interface bit not set. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.C2KATM-3Error Message    %C2KATM-3-UNAVAILABLE: Cannot create VCC %s.","The module was not able to create a VCC for the specified service.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C2KATM","3","UNAVAILABLE","Cannot create VCC for %s, no free VCDs","The module was unable to create a VCC for the specified service.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C2KATM","3","UNAVAILABLE","The IF index array is full, count 0x%x 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message    %C2KATM-3-UNAVAILABLE: The module attempted to transmit frame on a closed or non-existent VCD: vcd = %d","The module attempted to transmit frame on a closed or non-existent VCD.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C2KATM","4","UNAVAILABLE","%s discarded because it is not associated with a VCD: vpi = %d vci = %d","An OAM cell or an AAL5 frame was discarded because it was not associated with a VCD","Check the configuration of your ATM switch."
"C2KATM","4","UNAVAILABLE","AAL5 discarded because it is too large to buffer: vpi = %d, vci = %d, size = %d","An AAL5 frame destined for IOS was discarded because it was too large to buffer.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C3600","3","UNAVAILABLE","Can't allocate MAC address for interface %u/%u","MAC address allocation failed because of an incorrect slot and port combination, which exceeds the maximum available hardware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C3600","3","UNAVAILABLE","Detected invalid NVRAM size: %d bytes","The detected size of NVRAM is not one of the supported sizes.The NVRAM may be bad.","Copy the error message exactly as it appears, and report it to your technical support representative."
"C3600","3","UNAVAILABLE","Failed to erase config due to internal error","Password protection feature failed to erase config due to internal error","Copy the error message exactly as it appears, and report it to your technical support representative."
"C3600","3","UNAVAILABLE","Number of slots in chassis is undefined.","Data stored in midplane is bad or incomplete.","Contact technical support to update your system."
"C3600","3","UNAVAILABLE","Unknown chassis model.","Data stored in midplane is bad or incomplete.","Contact technical support to update your system."
"C3600","3","UNAVAILABLE","Unknown platform type","The Cisco IOS software image does not recognize the motherboard revision of this router. This could indicate either a hardware failure or that the software needs to be upgraded to recognize newer hardware.","Verify you are using a recommended revision of the Cisco IOS Software for your hardware. Upgrade if necessary. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C3600","4","UNAVAILABLE","Corrupt or missing MAC address cookie using random base %e","Data stored in midplane is bad.","Contact technical support to update your system."
"C3600","4","UNAVAILABLE","Midplane data version mismatch.","Data stored in midplane is out of date and needs update.","Contact technical support to update your system."
"C3600","4","UNAVAILABLE","Unknown MAC address block size.","Data stored in backplane is bad or incomplete.","Contact technical support to update your system."
"C4GWY_DSPRM","3","UNAVAILABLE","Insufficient DSP resources for timeslot %d on port %s","The configuration requires more DSP resources than are available.","Change the configuration to specify fewer used timeslots. Install additional DSP resources to allow more complex configurations."
"C4GWY_DSPRM","5","UNAVAILABLE","Configured codec %d is not supported with this dsp image.","Codec negotiation failed.Error Message    %C4GWY_DSPRM-5-UNAVAILABLE: DSP %d in slot %s, NOT RESPONDING - auto restart(%d times) Explanation    The DSP failed the background keep-alive test.","LOG_STD_NO_ACTION"
"C4GWY_DSPRM","5","UNAVAILABLE","DSP %d is in the failed state","The DSP entered the FAILED state due to alarm indications.","Replace the DSP resource."
"C4GWY_DSPRM","5","UNAVAILABLE","DSP %d is not present","All 4 DSP SIMMs not available .","Install all 4 hardware DSP SIMMs ."
"C4GWY_DSPRM","5","UNAVAILABLE","DSP %d, changed state to %s","The DSP resource changed state.","LOG_STD_NO_ACTION"
"C4K_IOSINTF","4","UNAVAILABLE","Failed to allocate internal VLAN for interface %s. The interface will remain down.","When a routed port or port channel interface is enabled, it must allocate an internal VLAN in order to operate. If there are no internal VLANs available when an interface is enabled, the interface remains down and this message is logged.","An internal VLAN can be freed up by disabling some other routed port or port channel interface or by deleting a user configured VLAN in the 1006 to 4094 range. Once a VLAN is made available, the interface will come up if it is disabled and re-enabled."
"C4K_IOSINTF","4","UNAVAILABLE","Reflexive Acls are not supported. Ignoring the %s entry.","Reflexive Acls are not supported. Aces with Evaluate and Reflect keywords are ignored.","Do not configure Aces with Evaluate or Reflect keyword."
"C4K_IOSINTF","5","UNAVAILABLE","Dropping packets to be transmitted out on port %s ( Linecard in Slot %d may have been removed )","During hot-swapping operations, sometimes, a prevously queued packet may be transmitted after a delay, by which time, the linecard does not exist anymore. This indicates such packets are being dropped","This occurs when there are queued packets that are transmitted, by which time the linecard in that slot has been removed already. If the problem persists even without any hotswapping operations, please contact your Cisco Technical Support representative"
"C4K_IOSINTF","5","UNAVAILABLE","Dropping transmit packet out of interface %s","A packet to be transmitted out of a Port-Channel is being dropped during transitions in the Port-Channel membership","This occurs when a packet is being transmitted out of the aggregate port by higher layer protocols, but the software cannot find specific state information. This can temporarily happen when physical ports transition into or out of the channel. If the problem persists, please contact your Cisco Technical Support representative"
"C4K_IOSINTF","5","UNAVAILABLE","Router Port %s has no internal vlan assigned to transmit packet","The L3 Interface specified does not have an internal vlan assigned.","This can occur if there is a duplicate IP network assignment on different L3 interfaces. Remove the duplicate IP network configured on the interface; assign the correct IP network and do 'no shutdown' on this interface."
"C4K_IOSINTF","5","UNAVAILABLE","Transmitting L3 packet on a physical port %s that is part of %s (%d packets). Make sure the physical port in the L3 port channel does not have an ip addresses configured on it.","The L3 protocols operate at the logical port level and not on physical port level. This message indicates an situation that causes L3 protocol packets to be sent on a physical port that is part of a bundle. This can happen if there is a misconfiguration. Maybe there is an ip address assigned to a physical port that is part of a layer 3 port channel","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C4K_IOSSYS","7","INVALIDVALUE","[chars] Type [dec] not handled, returning a default of 0","This message is for debugging purposes. When you see this message, report it to your technical support representative.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C4K_REDUNDANCY","2","IOS_VERSION_CHECK_FAIL","[chars]","For the redundancy utility to operate properly, the system must be configured with symmetrical hardware and software. A mismatch in versions of Cisco IOS software between the active and standby systems has been detected. Redundancy operations cannot be guaranteed.","Configure the system so that the active and standby supervisor engines are using the same versions of Cisco IOS software."
"C4K_REDUNDANCY","2","NON_SYMMETRICAL_REDUNDANT_SYSTEM","[chars]","For the redundancy utility to operate properly, the system must be configured with symmetrical hardware and software. A mismatch in hardware has been detected between the active and standby systems. Redundancy operations cannot be guaranteed.","Configure the hardware so that the active and standby supervisor engines are identical."
"C4K_REDUNDANCY","2","POSTFAIL","POST failure on [chars] supervisor detected","An active supervisor engine failed during a POST operation. The standby supervisor engine will reset the current active supervisor engine, and the standby supervisor engine will attempt to become the active supervisor engine.","Perform offline diagnostic operations on the failed supervisor engine to isolate the failure."
"C4K_REDUNDANCY","4","UNAVAILABLE","Persistent-config Sync to Standby supervisor failed.","Active supervisor failed to receive PLATFORM_SYNC_DONE message from Standby. Potential problem with Standby.C4K_REDUNCANCY-5Error Message    %C4K_REDUNDANCY-5-UNAVAILABLE: The %s has been successfully synchronized to the standby supervisor Explanation    The configuration has been successfully synchronized to the standby supervisor","This is an informational message. No action is required."
"C4K_REDUNDANCY","5","UNAVAILABLE","The %s has been successfully synchronized to the standby supervisor","The configuration has been successfully synchronized to the standby supervisor This is a rate limited message. These messages are logged at 1 min interval when lots of messages are generated continuously","This is an informational message. No action is required."
"C4K_REDUNDANCY","6","UNAVAILABLE","Active supervisor not found.","Informational message on standby supervisor when it fails to communicate with active supervisorError Message    %C4K_REDUNDANCY-6-UNAVAILABLE: Attempting to become active supervisor. Explanation    Informational message on standby supervisor when it fails to communicate with active supervisor and attempts to takeover as active supervisorError Message    %C4K_REDUNDANCY-6-UNAVAILABLE: Initializing as %s supervisor Explanation    Informational message regarding the state of the supervisorError Message    %C4K_REDUNDANCY-6-UNAVAILABLE: Switchover activity detected, changing role from STANDBY to ACTIVE Explanation    Informational message on standby supervisor when it detects switchover activity.C542-1Error Message    %C542-1-UNAVAILABLE: %s , Error interrupt occured type = 0x%x. Explanation    The DMA engine cannot get to the PCI bus, to read descriptors.","Copy the error message exactly as it appears, and report it to your technical support representative."
"C542","1","UNAVAILABLE","%s, packet(size %d) is empty.","A packet greater than the 256 bytes received on this interface.","The system should recover. No action is required. If the problem reccurs, it indicates an error that might be related to data traffic patterns. Copy the error message exactly as it appears, and report it to your technical support representative."
"C542","1","UNAVAILABLE","%s, packet(size %d) too big. Error Message    %C542-1-UNAVAILABLE: No more ring descriptors available on %d slot.","The c542 driver cannot queue messages upto the xilinx dma engine for transmit.","Copy the error message exactly as it appears, and report it to your technical support representative. Reset the DSP's on this port module."
"C542","1","UNAVAILABLE","VNM(%d), cannot support all voice channels on VICs.","There are more voice channels on the VICs than can be supported by this Network Module. Some channels will be inoperative.","This is normal when a BRI VIC coexists on a VNM with an analog VIC or when a BRI VIC is on a VNM-1. Otherwise, check the part number on the VIC card to see if it is supported in the version of IOS operational on the router or contact your technical support representative."
"C542","1","UNAVAILABLE","VNM(%d), vic card has an no known daughter cards","The software did not recognize any of the VIC card plugged in the Port Module.","Check the part number on the VIC card to see if it is supported in the version of IOS operational on the router or contact your technical support representative."
"C542","1","UNAVAILABLE","VNM(%d), vic daughter card has an unknown id of %x","The software did not recognize the type of VIC daughter card plugged into the Port Module.","Check the part number on the VIC card to see if it is supported in the version of IOS operational on the router or contact your technical support representative."
"C542","1","UNAVAILABLE","VPM (%d/%d), PCI memory unavailable.","The router or access server could not allocate memory for the descriptors.","Copy the error message exactly as it appears, and report it to your technical support representative."
"C542","1","UNAVAILABLE","VPM at slot %d: Incorrect %d DSP-ID passed by SPI.","The DSP ID provided by the SPI for download is not valid.","Call your technical support representative for assistance."
"C542","3","UNAVAILABLE","%s Unable to download the Application overlay firmware. Status returned 0x%x","Error initializing the DSP with the application/overlay firmware.","Power down, reinsert Port Module and reboot. If message recurs, call your technical support representative for assistance."
"C542","3","UNAVAILABLE","%s Unable to download the Boot loader firmware, ret = 0x%x","Error initializing the DSP with the bootloader firmware.","Power down, reinsert Port Module and reboot. If message recurs, call your technical support representative for assistance."
"C542","3","UNAVAILABLE","Error analyzing the device in slot %d.","The Port module in this slot could not be recognized.","Power down, reinsert Port Module and reboot. If message recurs, call your technical support representative for assistance."
"C542","3","UNAVAILABLE","No buffers available for DSP buffer pool","The c542 driver does not have enough memory to coalesce a multi-particle packet.","Copy the error message exactly as it appears, and report it to your technical support representative."
"C542","3","UNAVAILABLE","VPM at slot %d: Incorrect %d PM-ID device not supported.","A interface controller device did not have the correct PM-ID in eeprom cookie.","Run test pas eeprom, command, and set the correct PM ID. If message recurs, call your technical support representative for assistance."
"C542","3","UNAVAILABLE","VPM in slot %d: PCI device not supported.","A interface controller device did not report correct PCI device ID","Power down, reinsert Port Module and reboot. If message recurs, call your technical support representative for assistance."
"C54X","1","UNAVAILABLE","%s , Error interrupt occured type = 0x%x.","The DMA engine cannot get to the PCI bus, to read descriptors.","Copy the error message exactly as it appears, and report it to your technical support representative."
"C54X","1","UNAVAILABLE","%s, packet(size %d) too big.","A packet greater than the 256 bytes received on this interface.","The system should recover. No action is required. If the problem reccurs, it indicates an error that might be related to data traffic patterns. Copy the error message exactly as it appears, and report it to your technical support representative."
"C54X","1","UNAVAILABLE","No more ring descriptors available on %d slot.","The c54x driver cannot queue messages upto the xilinx dma engine for transmit.","Copy the error message exactly as it appears, and report it to your technical support representative. Reset the DSP's on this port module."
"C54X","1","UNAVAILABLE","VPM (%d/%d), PCI memory unavailable.","The router or access server could not allocate memory for the descriptors.","Copy the error message exactly as it appears, and report it to your technical support representative."
"C54X","1","UNAVAILABLE","VPM (%d/%d), memory unavailable.","The router or access server could not allocate memory for the descriptors.","Copy the error message exactly as it appears, and report it to your technical support representative."
"C54X","1","UNAVAILABLE","VPM at slot %d: Incorrect %d DSP-ID passed by SPI.","The DSP ID provided by the SPI for download is not valid.","Call your technical support representative for assistance."
"C54X","1","UNAVAILABLE","vpm(%d), vic card has an no known daughter cards","The software did not recognize any of the VIC card plugged in the Port Module.","Check the part number on the VIC card to see if it is supported in the version of IOS operational on the router or contact your technical support representative."
"C54X","1","UNAVAILABLE","vpm(%d), vic cards has an invalid configuration.","The software did recognized more vic interface port than it can support on this port Module.","Check the part number on the VIC card to see if it is supported in the version of IOS operational on the router or contact your technical support representative."
"C54X","1","UNAVAILABLE","vpm(%d), vic daughter card has an unknown id of %x","The software did not recognize the type of VIC daughter card plugged into the Port Module.","Check the part number on the VIC card to see if it is supported in the version of IOS operational on the router or contact your technical support representative."
"C54x","1","UNAVAILABLE","%s, packet(size %d) too big.","A packet greater than the 256 bytes received on this interface.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C54x","1","UNAVAILABLE","No more ring descriptors available on %d slot.","The c54x DSP driver cannot queue messages up to the dma engine for transmit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. Reset the DSP's on this port module."
"C54X","3","UNAVAILABLE","%s Unable to download the Application overlay firmware. Status returned 0x%x","Error initializing the DSP with the application/overlay firmware.","Power down, reinsert Port Module and reboot. If message recurs, call your technical support representative for assistance."
"C54X","3","UNAVAILABLE","%s Unable to download the Boot loader firmware, ret = 0x%x","Error initializing the DSP with the bootloader firmware.","Power down, reinsert Port Module and reboot. If message recurs, call your technical support representative for assistance."
"C54X","3","UNAVAILABLE","Error analyzing the device in slot %d.","The Port module in this slot could not be recognized.","Power down, reinsert Port Module and reboot. If message recurs, call your technical support representative for assistance."
"C54X","3","UNAVAILABLE","VPM at slot %d: Incorrect %d PM-ID device not supported.","A interface controller device did not have the correct PM-ID in eeprom cookie.","Run test pas eeprom, command, and set the correct PM ID. If message recurs, call your technical support representative for assistance."
"C54X","3","UNAVAILABLE","VPM in slot %d: PCI device not supported.","A interface controller device did not report correct PCI device ID","Power down, reinsert Port Module and reboot. If message recurs, call your technical support representative for assistance."
"C5RSP","3","UNAVAILABLE","Invalid loveletter type, %d, sent by c5ip","IOS is receiving bogus messages from the C5IP.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C5RSP","3","UNAVAILABLE","Length error occurred on dma channel 0","A hardware error has occurred on dma channel 0","Report this error to your technical support representative."
"C5RSP","3","UNAVAILABLE","Length error occurred on dma channel 1","A hardware error has occurred on dma channel 1","Report this error to your technical support representative."
"C5RSP","3","UNAVAILABLE","NMP returned invalid bridge id %d for %d","NMP returned invalid bridge id to the RSM","Make sure that the tr-brf vlan on the RSM is configured on the NMP"
"C5RSP","3","UNAVAILABLE","NMP won't allow vlan %d configuration","In band IPC message to the NMP from the router to create a vlan has failed.","Try these actions to remedy the problem: Check the state of Vlan 0. Check the state of the C5IP via the front panel LED. Check the state of the NMP. Reset the router"
"C5RSP","3","UNAVAILABLE","RSM NMP mismatch in config for %d, RSM %d, NMP %d","There is mismatch in config for this vlan on NMP and RSM","Make sure that the params for this vlan are the same on NMP and on the RSM"
"C5RSP","3","UNAVAILABLE","bad message received from the NMP","An unsolicited in band IPC message was received by the router from the NMP.","LOG_STD_NO_ACTION"
"C5RSP","3","UNAVAILABLE","can't configure more than 256 VLANS","The Vlan Router product can configure a maximum of 256 vlans.","Try these actions to remedy the problem: Delete unused vlans before configure new ones."
"C5RSP","3","UNAVAILABLE","can't get C5 Line Card Mac Addr","An attempt by the RSP to query the C5IP for Vlan 0 IP address failed.","Try these actions to remedy the problem: Reset the router from the NMP's console. If problems persist, please RMA the router and or Catalyst 5000"
"C5RSP","3","UNAVAILABLE","can't get Catalyst 5000 Slot number of router","An attempt by the RSP to query the C5IP for theslot it is plugged into has failed.","Try these actions to remedy the problem: Reset the router from the NMP's console. If problem persists, please contact Cisco for replacement."
"C5RSP","3","UNAVAILABLE","can't get NMP Mac Addr","An attempt by the RSP to query the C5IP for Vlan 0 MAC address failed.","Try these actions to remedy the problem: Reset the router from the NMP's console. If problems persist, please contact Cisco for replacement"
"C5RSP","3","UNAVAILABLE","can't talk to NMP during initialization","In band IPC router initialization message to the NMP has failed","Try these actions to remedy the problem: Check the state of Vlan 0. Check the state of the C5IP via the front panel LED. Check the state of the NMP. Reset the router"
"C5RSP","3","UNAVAILABLE","having problems deleting vlan %d on the NMP","In band IPC message to the NMP from the router to delete a vlan has failed.","Try these actions to remedy the problem: Check the state of Vlan 0. Check the state of the C5IP via the front panel LED. Check the state of the NMP. Reset the router"
"C5RSP","3","UNAVAILABLE","unknown timer for NMP programming","An unknown timer event has expired.","LOG_STD_NO_ACTION"
"C5RSP","3","UNAVAILABLE","vlan %d can not be created. media not supported","An attempt to create a vlan of a media that is not supported has failed","Try these actions to remedy the problem: Configure the vlan with a different media type."
"C5RSP","6","UNAVAILABLE","vlan %d could/could not be configured for bridging","A Vlan could not be reset with the proper bridging information.","Try these actions to remedy the problem: Configure the vlan with or with bridging."
"C5RSP","6","UNAVAILABLE","vlan %d info errant. something very wrong","Internal information about the Vlan is missing.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C5RSP","6","UNAVAILABLE","vlan %d missing IDB","Internal data structure of the Vlan is missing.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CAIM","1","UNAVAILABLE","AIM in slot %u not supported by this HW revision.","The revision level of the C2600 'Elmer' PLD does not support compression AIM. The PLD needs to be reprogrammed.","The C2600 'Elmer' PLD needs to be reprogrammed to a later revision. Refer to CCO Release Notes for the C2600 and Compression AIM for an explanation of how to reprogram the PLD."
"CAIM","1","UNAVAILABLE","AIM slot %d: Could not locate Compression AIM; found PCI vendor id 0x%x instead","The AIM ID PROM indicates that a Compression AIM is present but the PCI vendor / device ID was not that expected for a Compression AIM.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CAIM","1","UNAVAILABLE","CAIM %d: Initialization failed at %s","The CAIM device would not reset properly. Indicative of a compression AIM hardware failure.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CAIM","1","UNAVAILABLE","CAIM %d: Memory allocation failure; could not allocate %s","An attempt to allocate memory for the specified compression AIM failed. More RAM may be required to execute this image.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CAIM","1","UNAVAILABLE","Caim %u: Hifn 9711 Errors reported: 9711 Status 0x%lx DMA status 0x%lx","The specified CAIM reported a Hifn9711 error.","This is an indication of a serious malfunction of the Compression AIM or of the system bus. The Compression AIM should be replaced."
"CAIM","1","UNAVAILABLE","Caim %u: PCI Abort reported: status 0x%lx","The specified CAIM reported a bus error (PCI Abort).","This is an indication of a serious malfunction of the Compression AIM or of the system bus. The Compression AIM should be replaced. A second possible explanation is that there is a mismatch in the configured compression algorithm on either side of a serial link. This situation can also give rise to PCI Abort problems. The recommended action in such cases is to configure matching compression algorithms on either side of the link and then to reboot the router which experienced the PCI Abort."
"CAIM","1","UNAVAILABLE","Compression AIM type in slot %u is not supported by this platform.","The compression AIM installed is not supported by this platform.","Power off and replace the Compression AIM card."
"CAIM","1","UNAVAILABLE","Invalid CAIM element: %d","The CAIM element number specified in the command is invalid.","CAIM element numbers range from 0 to one less than the number of CAIMs possible in your system. Verify the number of CAIMs present in your system."
"CAIM","1","UNAVAILABLE","No such CAIM element: %d","The CAIM element number specified is not present in the system","CAIM element numbers range from 0 to one less than the number of CAIMs present in your system. Verify the number and presence of CAIMs in your system."
"CAIM","1","UNAVAILABLE","Unexpected AIM Interrupt","We received an AIM interrupt from an unknown AIM device. There is no recognizable AIM installed in the system, and yet we received an AIM interrupt.","If there is a compression AIM installed in the C2600, then it is defective and must be replaced. If there is some other AIM installed in the C2600 then it must be removed. If there is no AIM installed, then the C2600 unit is defective and must be replaced."
"CAIM","6","UNAVAILABLE","%s shutting down","The specified CAIM is shutting down. It may have been physically removed. It also occurs when the 'clear aim' command is used.","This is an informational message only. It occurs in normal operation."
"CAIM","6","UNAVAILABLE","%s starting up","The specified CAIM has initialized successfully.","This is an informational message only. It occurs in normal operation."
"CALLPROG","3","UNAVAILABLE","api front init failed for %s","Failed to init Call Progress Notification support structures for APIs.","System running low on available memory."
"CALLPROG","3","UNAVAILABLE","no free front-end q elt's; dropping api call info (func=%d)","Failed to get free element from front end queue.","Platform requires additional free elements to properly function. Stop using Call Progress Notification applications. Call TAC to report the problem."
"CALLRECORD","3","UNAVAILABLE","%s","Record Generated Exceeded Syslog Capability","LOG_STD_NO_ACTION"
"CALLRECORD","3","UNAVAILABLE","%s","Terse Mcom Call Failed Record","LOG_STD_NO_ACTION"
"CALLRECORD","3","UNAVAILABLE","%s","Terse Mcom Call Record","LOG_STD_NO_ACTION"
"CALLRECORD","3","UNAVAILABLE","%s","Terse Mica Call Failed Record","LOG_STD_NO_ACTION"
"CALLRECORD","3","UNAVAILABLE","%s","Terse Mica Call Record","LOG_STD_NO_ACTION"
"CALLRECORD","6","UNAVAILABLE","%s","Terse Mica Call Failed Record","LOG_STD_NO_ACTION"
"CALLRECORD","6","UNAVAILABLE","%s","Terse Mica Call Record","LOG_STD_NO_ACTION"
"CALLTRKR","3","UNAVAILABLE","%s","Record Generated Exceeded Syslog Capability","LOG_STD_NO_ACTION"
"CALLTRKR","3","UNAVAILABLE","Init of CT's %s table failed; CT unusable","Failed to init calltracker record table.","Disable calltracker first [no calltracker enable], enable it again."
"CALLTRKR","3","UNAVAILABLE","Memory allocation failed for CT %s (%d bytes)","Calltracker couldn't allocate new record due to no free memory.","Disable calltracker [no calltracker enable]. Run show memory to find out where is the memory been allocated."
"CALLTRKR","3","UNAVAILABLE","calltrkr cli print buffer %s","calltrkr cli internal print buffer overflow.","Stop to using calltrkr show commands, call TAC to report the problem"
"CALLTRKR","3","UNAVAILABLE","can't spawn %s","Couldn't spawn calltracker process.","Disable calltracker first [no calltracker enable], enable it again."
"CALLTRKR","6","UNAVAILABLE","%s","Modem Information Verbose CallTracker Call Record","LOG_STD_NO_ACTION"
"CALLTRKR","6","UNAVAILABLE","%s","Modem Line Verbose CallTracker Call Record","LOG_STD_NO_ACTION"
"CALLTRKR","6","UNAVAILABLE","%s","Modem Negotiation Verbose CallTracker Call Record","LOG_STD_NO_ACTION"
"CALLTRKR","6","UNAVAILABLE","%s","Modem Verbose CallTracker Call Record","LOG_STD_NO_ACTION"
"CALLTRKR","6","UNAVAILABLE","%s","Terse CallTracker Call Record","LOG_STD_NO_ACTION"
"CALL_CONTROL","3","UNAVAILABLE","no free raw msg structure available from %s for signaling message","There were no rawmsg structures remaining in the system pools to alert the router of a voice or signaling event.","Check that the voice port for which the event was reported is still operational. If not, clear the voice port."
"CALL_CONTROL","6","UNAVAILABLE","Application %s in dial-peer %d not found. Handing callid %d to the alternate app %s.","The inbound dial-peer points to an unavailable application.The call is being handed to the alternate application or is rejected.","Reconfigure the dial-peer to have a valid application name or verify the application is accesible at its location."
"CALL_CONTROL","6","UNAVAILABLE","Maximum number of connections reached for dial-peer %d","The dial-peer in question has reached its maximum connections configurations. No more calls will be taken on this dial-peer.","No action is required, however, to increase the number of connections allowed to this dial peer see 'maximum connections' configuration under the dial-peer configuration mode."
"CALL_CONTROL","6","UNAVAILABLE","The called number numbering type did not matchThe event for the callid %d is being discarded.","The event points to a session application which does not exist any more. The event is being discarded.","No action is required for the users"
"CALL_CONTROL","6","UNAVAILABLE","The incoming call has a global identfier already present in the list of currently handled calls. It is being refused. Recommended Action    Please check your configuration.Error Message    %CALL_CONTROL-6-UNAVAILABLE: The requested application does not exist any more. The event for the callid %d is being discarded.","The event points to a session application which does not exist any more. The event is being discarded.","No action is required for the users"
"C6KENV","2","BADFLOWCTRL","Module [dec] not at an appropriate hardware revision level to support DFC. Power denied","The fabric-capable module in the specified slot is not at an appropriate hardware revision level and cannot support a DFC. If a DFC is present, the module will not be activated and remains powered down.","Remove the DFC to enable the module to operate at its current hardware revision level. To enable DFC operation, ensure that the module is at an appropriate hardware revision level."
"C6KENV","2","BADFLOWCTRL_WARN","WARNING: Module [dec] not at an appropriate hardware revision level to support DFC3","The fabric-capable module in the specified slot is not at an appropriate hardware revision level to support a DFC3 or higher.","When you upgrade the DFC daughter card, also upgrade the module to an appropriate hardware revision level."
"C6KENV","2","BADPINN1","Module [dec] not at an appropriate hardware revision level to coexist with PFC3 system. Power denied","The module specified in the error message has a revision of 2.x or below. Modules with this revision will experience problems when they are used with a supervisor engine with a PFC3 installed and should not be used.","Upgrade the module to an appropriate hardware revision level."
"C6KENV","2","BADTRANSCEIVER","Module [dec] will be power disabled because an inappropriate transceiver is inserted at [chars].","An incompatible transceiver is inserted at the interface specified in the error message. This transceiver should not be used in this system.","Remove the specified transceiver and restore power to the module. If this transceiver was purchased from Cisco, contact your Cisco technical support representative to get the transceiver replaced."
"C6KENV","2","C2PLUSWITHNODB","The constellation 2 plus module in slot [dec] has no forwarding daughter board. Power denied","The module in the slot specified has no forwarding daughter card and is expected to have either a distributed, accelerated, or centralized forwarding card. This module will not be activated and will remain powered down.","Enter the show module command to view error message details."
"C6KENV","2","DFCMISMATCH","Module [dec] DFC incompatible with Supervisor DFC. Power denied","The DFC in the specified module is different from the DFC in the supervisor engine. The module will not be activated and remains powered down.","Enter the show module command to view the difference between the DFC in the module and the DFC in the supervisor engine."
"C6KENV","2","DFCMISMATCHMINOR","Module [dec] DFC installed is incompatible with system operating mode. Power denied. To enable Module [dec] DFC, the system must be reset.WARNING: Any system reset will change the system operating mode which can result in degradation of system performance. To eliminate this from occurring, remove Module [dec] DFC or replace with a system compatible DFC.","The DFC in the specified slot does not have the same software operating mode as the rest of the system. The DFC will remain powered down and cannot be activated.","Enter the show module and show platform earl-mode commands to view the difference between the DFC in the specified slot and the operating mode of the rest of the system."
"C6KENV","2","FANUPGREQ","Module [dec] not supported without fan upgrade","The supervisor engine and the DFC in the specified slot require a fan tray upgrade. A system shutdown is scheduled.","Upgrade the system fan tray."
"C6KENV","2","SHUTDOWN_NOT_SCHEDULED","Major sensor alarm for [chars] is ignored, [chars] will not be shutdown.","The system detected that the specified module should be shut down because it exceeded major sensor thresholds. However, the command that shuts down the module in the event of a major sensor alarm has been overridden, so the specified module will not be shut down. The command used to override the shutdown is no environment-monitor shutdown.","Remove the configuration that bypasses the module shutdown due to sensor thresholds being exceeded. Shut down the module after removing the configuration."
"C6KENV","2","SHUTDOWN_SCHEDULED","shutdown for [chars] scheduled in [dec] seconds","A major alarm condition will be corrected by shutting down the affected component. [chars] is the component, and [dec] is the time in seconds before shutdown.","Replace the component as soon as possible."
"C6KENV","4","ALARMCLR","[chars] alarm cleared","The specified alarm condition has been cleared. The shutdown has been cancelled.","No action is required."
"C6KENV","4","FANCOUNTFAILED","Required number of fan trays is not present","The system is missing the number of required fan trays to operate properly. Although this is a minor alarm, system components could overheat and be shut down.","Insert the required fan tray as soon as possible."
"C6KENV","4","FANCOUNTOK","Required number of fan trays is present","The number of required fan trays has been restored.","No action is required."
"C6KENV","4","FANHIOUTPUT","Version [dec] high-output fan-tray is in effect","The system has detected that the fan tray is a high-output (version 2) fan tray. The system has updated the cooling capacity for the fan tray.","No action is required."
"C6KENV","4","FANLOOUTPUT","Version [dec] low-output fan-tray is in effect","The system has detected that the fan tray is a low-output (version 1) fan tray. The system has updated the cooling capacity for the fan tray.","No action is required."
"C6KENV","4","FANPSINCOMPAT","Fan tray and power supply [dec] are incompatible","An upgrade of the power supply is required to sufficiently operate this fan tray. Although this is a minor alarm, overcurrent protection on the power supply could start without further warning.","Upgrade the power supply."
"C6KENV","4","FANTRAYFAILED","fan tray failed","One or more fans in the system fan tray have failed. Although this is a minor alarm, system components could overheat and be shut down.","Reseat the fan tray. If the error recurs, replace the system fan tray at the earliest opportunity."
"C6KENV","4","FANVERCHK","Power-supply [dec] inserted is only compatible with Version [dec] fan-tray. Please make sure fan is low-output fan-tray","The system has detected that the fan tray is a low-output (version 1) fan tray. If the fan tray is a low-output tray, no action is required. If the fan tray is actually a high-output (version 2) fan tray, the specified power supply is not able to support the high-output fan tray.","If the fan tray is a high-output (version 2) fan tray, enter the hw-module fan-tray version 2 command to update the system with the upgrade information. Replace the 1000 W or 1300 W power supply, as these two power supplies are not compatible in this chassis with the version 2 fan tray."
"C6KENV","4","INSUFFCOOL","Module [dec] cannot be adequately cooled","The fan tray cannot adequately cool the specified module. Although this is a minor alarm, system components could overheat and be shut down.","Upgrade the system fan tray."
"C6KENV","4","MINORTEMPOKALARM","[chars] all temperature sensor have failed. If the module temperature sensor does not recover by itself, please power cycle the module when it is feasible","All module temperature sensors have failed.","If the module temperature sensors do not recover, power cycle the module when possible."
"C6KENV","4","MINORTEMPOKALARMRECOVER","[chars]. It has returned to normal operating status.","All module temperature sensors have returned to normal operating status.","No action is required."
"C6KENV","4","MINORTEMPSUPOKALARM","All temperature sensors of Supervisor in slot [dec] have failed. If the temperature sensor does not recover by itself, please power cycle the chassis when it is feasible","All temperature sensors have failed in the supervisor engine.","If the temperature sensors do not recover, power cycle the chassis when possible."
"C6KENV","4","MINORTEMPSUPOKALARMRECOVER","Supervisor in slot [dec] has returned to normal operating status.","The supervisor engine temperature sensors have returned to normal operating status.","No action is required."
"C6KENV","4","MINORVTTOKALARM","All the backplane vtt temperature sensor have failed. If the backplane vtt temperature sensor does not recover by itself, please power cycle the chasis when it is feasible","All backplane VTT temperature sensors have failed.","If the backplane VTT temperature sensors do not recover, power cycle the chassis when possible."
"C6KENV","4","MINORVTTOKALARMRECOVER","Backplane VTT has returned to normal operating status.","The backplane VTT has returned to normal operating status.","No action is required."
"C6KENV-SP","4","FANTRAYFAILED","Fan tray failed.","One or more fans in the system fan tray have failed. Although this is a minor alarm, system components can overheat and be shut down.","Replace the system fan tray as soon as possible."
"C6KENV-SP","4","MINORTEMPALARM","[chars] has exceeded normal operating temperature range.","Message indicates that the normal operating temperature range has been exceeded. This message can indicate a trend for the module or component, and also a trend for other components in the system.","Inspect the indicated module or component closely to determine why it operates out of normal operating temperature range and determine if it eventually exceeds the allowed operating temperature range. Verify the air flow to the device is not blocked and that the fan is operational. Enter the show environment temperature command to see temperature readings and the show environment alarm threshold command to see the alarm thresholds."
"C6KERRDETECT","2","SWBUSSTALL","The switching bus is experiencing stall for [dec] seconds","During an Online Insertion or Removal (OIR), some switching modules will assert a stall signal on the backplane to pause data transmission for the duration of the OIR. When the OIR is performed smoothly and quickly, traffic is usually interrupted for less than one second. If the OIR is performed slowly or is paused, the longer traffic interruption will result in this error message being reported.","Perform the OIR smoothly and quickly. Do not pause with the module partially inserted."
"C6K_BFD","6","CONF_BFD_SVI_PLAT_KNOB","This will allow BFD on SVI interface. While unconfiguring please un-configure BFD sessions first and then do no platform bfd allow-svi","Notification to user that BFD sessions over SVI interface will be allowed after configuring this hidden cli.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_BFD","6","UNCONF_BFD_SVI_PLAT_KNOB","BFD over SVI sessions may be alive even though SVI interface config might not show the bfd configurations if bfd is not un-configured manually prior to un-configuring platform bfd allow-svi command","Due to insufficient power, the fan cannot operate in HP mode to meet the cooling requirement of the switch.","Check the power availabilty or power down the some modules."
"C6K_BFD","6","UNCONF_BFD_SVI_PLAT_KNOB","BFD over SVI sessions may be alive even though SVI interface config might not show the bfd configurations if bfd is not un-configured manually prior to un-configuring platform bfd allow-svi command","Notification to customer that BFD sessions may be alive even though BFD configuration is not seen under SVI interface when no platform bfd allow-svi is done","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_BFD","6","UNCONF_BFD_SVI_PLAT_KNOB","BFD over SVI sessions may be alive even though SVI interface config might not show the bfd configurations if bfd is not un-configured manually prior to un-configuring platform bfd allow-svi command","The lower slot physically adjacent to this module might be empty. System components could overheat and be shut down.","Insert airdam card to adjacent empty slot as soon as possible"
"C6K_EOM","5","TCAM_EXCEPTION","Layer2 TCAM exception occurred, EoM/VPLS traffic will be dropped","The switch failed to insert an EoM/VPLS entry into the hardware FIB TCAM because the total number of forwarding entries exceeded the hardware FIB TCAM limit. Some EoM/VPLS packets might be dropped in hardware.","Reduce the number of Virtual Circuit in the system to free up TCAM space. Layer2 TCAM exception recovery is not supported. The number of layer2 TCAM entries can be tuned with the configuration command platform cef maximum-routes. Increase the number of eompls entries, save configuration and reload the router. This configuration will only be effective on reloading the router. The maximum number of entries currently configured for EoM/VPLS can be observed with the command show platform hardware cef maximum-routes"
"C6K_IVRF","3","C6K_IVRF_ERROR","[chars]","A VRF infrastructure failure occurred involving the platform's internal VRFs (IVRFs).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_MPLS","5","ADJ_EXCEPTION","Adjacency exception occurred for MPLS, traffic will be software switched","The switch failed to allocate hardware adjacencies because the adjacency table has run out of entries. Some MPLS packets might be forwarded by the software.","Reduce the number of routes in the system to free up adjacencies. However, no adjacency recovery is currently in place. The routes need to be re-learnt so that hardware adjacencies can be re-allocated and re-programmed."
"C6K_MPLS","5","TCAMEXPRECOVER","TCAM exception recovered for MPLS, traffic will be hardware switched","At some earlier point in time some of the MPLS forwarding table couldn't fit into the hardware TCAM. Now the complete MPLS forwarding table is in hardware. Forwarding of incoming MPLS packets will be done in hardware.","Informational only. No action required."
"C6K_MPLS","5","TCAM_EXCEPTION","TCAM exception occurred for MPLS, traffic will be software switched","The switch failed to insert an MPLS entry into the hardware FIB TCAM because the total number of software forwarding entries exceeded the hardware FIB TCAM limit. Some MPLS packets might be forwarded by the software.","Reduce the number of routes in the system to free up TCAM space. When enough TCAM space is freed, the software will start TCAM recovery and re-install those label entries that failed before into TCAM. If the number of labels has been tuned down with the configuration command platform cef maximum-routes, increase the number of labels, save configuration and reload the router, since this configuration will only be effective on reloading the router. The maximum number of routes currently configured can be observed with the command show platform hardware maximum-routes, and the current number of routes in the system can be observed with the command show platform hardware cef summary."
"C6K_MPLS_COMMON","3","L2_CONFIG_NOT_RECOMMENDED","xconnect is configured on interface vlans and WAN interfaces are facing the MPLS Core. Do not configure LAN interfaces facing the MPLS Core.","An attempt was made to configure a LAN interface to face the MPLS core. The current network configuration has cross-connection services configured on interface VLANs and has WAN interfaces facing the MPLS core.","Do not configure MPLS on LAN interfaces facing the MPLS core if the network has cross-connect services configured on an interface VLAN and WAN interfaces that face the MPLS core."
"C6K_MPLS_COMMON","3","L3_CONFIG_NOT_RECOMMENDED","LAN interfaces are facing the MPLS Core. Do not configure xconnect on interface vlans.","An attempt was made to configure a cross-connection service on an interface VLAN. The current network configuration has MPLS configured on a LAN interface that is facing the MPLS core.","Do not configure cross-connection services on an interface VLAN if the network has MPLS configured on a LAN interface."
"C6K_MPLS_COMMON","3","OSM_BB1_CONFIG_UNSUPPORTED","The maximum label range configured for this system exceeds the [int]limit supported by the module in slot [int]. For proper MPLS functionality on any of the interfaces on this module the maximum label range should be set to [int].","The OSM cannot support the MPLS label range configured for this system.","Change the maximum MPLS label range by using the mpls label range command."
"C6K_MPLS_COMMON","3","VPLS_CONFIG_EXCEEDED","The number of EoMPLS/VPLS VCs exceeded the maximum supported on [IP_address]/[int].","The number of destination routers or the global number of virtual circuits exceeded the maximum limit supported by the device.","Refer to network configuration guidelines for the maximum limits."
"C6K_MPLS_LC","3","INFINITE_OCE","In label: [dec] Invalid OCE previous oce type: [dec] prev ptr:Unrecognized format ` %p', next oce type: [dec] next oce ptr:Unrecognized format ` %p'","The Output Chain Element(OCE) specified in the system message is invalid because it has exceeded the maximum depth. One known cause is invalid static route configuration. Traffic for this path will be dropped.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C6K_MPLS_LC","3","INVALID_TABLEID","Invalid tableid([dec]) for label([dec])","The system has received an invalid table identifier number. The table identifier should be in the range from 0 to 4095. This is an internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_MPLS_LC","3","INVALID_TE_IF_NUMBER","An invalid Traffic Engineering interface number [[int]] was passed to the statistics update routine","The traffic engineering interface number sent to the statistics update routine is invalid.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_MPLS_LC","3","INVALID_VRFID","Invalid vrf_id(%u) for label([dec])","An invalid VRF identifier (ID) was received. The VRF ID should be in the range of 0 to 4095. This is an internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_MPLS_LC","3","LABEL_STACK_SIZE","Label [[dec]] is not added to label stack. Current label stack is [[dec] [dec] [dec] [dec] [dec]]","The label specified in the system message was not added to the label stack because the stack already contains the maximum number of allowed labels. The system cannot forward data correctly. This condition is an internal software error.","Enter the show mpls forwarding-table labels command, and gather label information about the label that was not added to the stack and about the labels that are in the stack already. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_MPLS_LC","3","MALLOCFAIL","failed to create [chars]","The system failed to allocate memory for an MPLS entry for the incoming label. Some MPLS packets might be forwarded by the software.","Reduce other system activity to ease memory demands. If necessary, increase system memory. When more memory is available, wait for a few minutes and enter the clear ip route command. If sufficient memory has not been made available, this message will display again. If this problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_MPLS_LC","3","OCE_ERROR","Invalid OCE [[chars]] [hex]","The Output Chain Element (OCE) specified in the system message is invalid because it cannot be processed. This issue can cause problems in data forwarding. This condition is an internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_MPLS_LC","3","REWRITEFAIL","null adj for incoming label [dec]","The specified incoming label has a NULL adjacency entry. The hardware adjacency entry might not be programmed because the incoming label has the NULL adjacency entry. This condition is an internal software error.","Enter the show mpls forwarding-table labels command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_MPLS_LC","3","SIX_PE_REW_LBL_ENTRY_MISMATCH","The label entry([hex]) in the 6PE rewrite table for incoming label [dec] does not match the passed in label entry([hex])","The label entry in the IPv6 on Provider Edge router (6PE) rewrite table does not match the label entry for an incoming label. This is an internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_MPLS_LC","3","TCAMFAIL","TCAM validation check failed for label [dec]","The validation check on an inserted TCAM entry failed for the specified label.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_MPLS_LC","5","TCAM_EXCEPTION","TCAM exception occured for MPLS, traffic will be software switched","The switch failed to insert an MPLS entry into the hardware FIB TCAM because the total number of software forwarding entries exceeds the hardware FIB TCAM limit. As a result, some MPLS packets might be forwarded by the software.","Reduce the number of routes in the system to free up TCAM space. When enough free TCAM space is available, the software starts the TCAM recovery mechanism automatically, which will reinstall into TCAM those MPLS label entries that failed before. If the number of labels has been tuned down with the mls cef maximum-routes configuration command, increase the number of labels, save the configuration, and reload the router, bacause this configuration will only be effective on reloading the router. The maximum number of routes currently configured can be observed with the show mls cef maximum-routes command, and the current number of routes in the system can be observed with the show mls cef summary command."
"C6K_MPLS_LC","5","TCAMEXPRECOVER","TCAM exception recovered for MPLS, traffic will be hardware switched","At some earlier point in time some of the MPLS forwarding table could not fit into the hardware TCAM. The complete MPLS forwarding table is now in hardware, and forwarding for the incoming MPLS packets will be done in hardware.","No action is required."
"C6K_MPLS_RP","2","INIT","[chars]","The initialization of the Constellation MPLS forwarding infrastructure failed. This condition causes problems in the MPLS packet forwarding. The router will be forced to reboot to recover from the problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_MPLS_RP","2","NO_IP_ACL_RSVD_VLAN","IP ACL features will not be applied to MPLS-IP packets due to a lack of internal VLAN resources","This error might occur if the total number of VLANs in use exceeds 4096. The VLAN resources are shared by VLANs used for SVI, VLANS used for subinterfaces, hidden VLANs used for routed ports, and internal VLANs used for some VRFs. An internal VLAN is needed when an IP ACL feature is applied to a VRF interface. If the total number of VLANs in use exceeds 4096, no more internal VLANs can be allocated, so IP ACL features will not be applied to MPLS-to-IP packets.","Reduce the total number of VLANs in use by removing SVI interfaces, subinterfaces, or VRF interfaces."
"C6K_MPLS_RP","2","NO_IP_QOS_RSVD_VLAN","IP QoS features will not be applied to MPLS->IP packets due to a lack of internal VLAN resources","This message indicates a condition that might occur if the total number of VLANs in use exceeds 4096. The VLAN resources are shared by VLANs used for SVI, VLANS used for subinterfaces, hidden VLANs used for routed ports, and internal VLANs used for some VRFs. An internal VLAN is needed when an IP QoS feature is applied to a VRF interface. If the total number of VLANs in use exceeds 4096, no more internal VLANs can be allocated, so IP QoS features will not be applied to MPLS-to-IP packets.","Reduce the total number of VLANs in use by removing SVI interfaces, subinterfaces, or VRF interfaces."
"C6K_MPLS_RP","3","GET_RSVD_VLAN_TABLEID_MISMATCH","Tableid [int] in reserved VLAN idb [chars] mismatched application tableid [int]","An application provided a table ID for a reserved VLAN, but the table ID does not match the value in the reserved VLAN interface descriptor block (IDB).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_MPLS_RP","3","GET_RSVD_VLAN_VRFID_MISMATCH","Tableid %u in reserved VLAN idb [chars] mismatched application tableid %u","An application gave a table identifier (ID) to get a reserved VLAN interface descriptor block (IDB) but the table ID within the IDB does not match the specified value.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_MPLS_RP","3","INFINITE_OCE","In label: [dec] Invalid OCE previous oce type: [dec] prev ptr:Unrecognized format ` %p', next oce type: [dec] next oce ptr:Unrecognized format ` %p'","The Output Chain Element(OCE) specified in the system message is invalid because it has exceeded the maximum depth. One known cause is invalid static route configuration. Traffic for this path will be dropped.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_MPLS_RP","3","INVALID_TABLEID","Invalid tableid([dec]) for label([dec])","An invalid table ID was received. The table ID should be in the range of 0 to 4095. This is an internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_MPLS_RP","3","INVALID_VRFID","Invalid vrfid(%u) for label([dec])","An invalid VRF identifier (ID) was received. The VRF ID should be in the range of 0 to 4095. This is an internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_MPLS_RP","3","L2_CONFIG_NOT_RECOMMENDED","xconnect is configured on interface vlans and WAN interfaces are facing the MPLS Core. Do not configure LAN interfaces facing the MPLS Core.","An attempt was made to configure a LAN interface to face the MPLS core. The current network configuration has cross-connection services configured on interface VLANs and has WAN interfaces facing the MPLS core.","Do not configure MPLS on LAN interfaces facing the MPLS core if the network has cross-connection services configured on an interface VLAN and WAN interfaces that face the MPLS core."
"C6K_MPLS_RP","3","L3_CONFIG_NOT_RECOMMENDED","LAN interfaces are facing the MPLS Core. Do not configure xconnect on interface vlans.","An attempt was made to configure a cross-connection service on an interface VLAN. The current network configuration has MPLS configured on a LAN interface that is facing the MPLS core.","Do not configure cross-connection services on an interface VLAN if the network has MPLS configured on a LAN interface."
"C6K_MPLS_RP","3","NO_RSVD_VLAN_ERROR","Failed to allocate reserved VLAN for vrf [int]","The system failed to allocate an MPLS-reserved VLAN.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_MPLS_RP","3","PKT_DROP_NO_RSVD_VLAN_IDB","Packet dropped, no idb for reserved VLAN [int]","A packet received on a reserved VLAN was dropped because it did not contain an interface descriptor block (IDB) for the VLAN.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_MPLS_RP","3","RECIRC_DROP","Re-circulated packet dropped due to error.Possible causes: MTU or TTL failTotal drops = [int] pkts, Last packet size [int] BytesTop 3 Labels and partial packet dump -{[int](exp:[dec] eos:[dec] ttl:[dec]), [int](exp:[dec] eos:[dec] ttl:[dec]), [int](exp:[dec] eos:[dec] ttl:[dec])}[hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]","A recirculated packet was dropped due to an error. This condition might occur if the size of a recirculated packet exceeds the egress interface MTU.","Increase the MTU size on the egress interface to accomodate the incoming packets. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_MPLS_RP","3","RSVD_VLAN_RELEASE_ERROR","Failed to release reserved VLAN [int] from vrf [int]","The system failed to release an MPLS-reserved VLAN from a VRF either because the VRF was not found or because a failure occurred when dissociating the VLAN from the VRF.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_MPLS_RP","3","RSVD_VLAN_SET_ACL_ERROR","Failed to set ACL default for reserved VLAN [int] for vrf [int]","The system failed to set an ACL default for an MPLS-reserved VLAN.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_MPLS_RP","3","RSVD_VLAN_SET_IDB_ERROR","Failed to set idb of reserved VLAN [int] for vrf [int]","The system failed to set the IDB for an MPLS-reserved VLAN.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_MPLS_RP","6","PKT_DROP_RSVD_VLAN_TABLEID","Packet dropped, reserved VLAN idb [chars] has incorrect tableid [int]","A packet received on a reserved VLAN was dropped due to an incorrect table ID in the IDB. This situation might occur during VRF removal. The aggregate label will stay in the H state for a few minutes, while the table ID in the reserved VLAN IDB has already cleared.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_MPLS_RP","6","PKT_DROP_RSVD_VLAN_VRFID","Packet dropped, reserved VLAN idb [chars] has incorrect tableid %u","A packet received on a reserved VLAN was dropped due to an incorrect table identifier (ID) in the interface descriptor block (IDB). This condition might occur when, during VRF removal, an aggregate label will stay in the H state for a few minutes, while the table ID in the reserved VLAN IDB has already cleared.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_PLATFORM","0","UNKNOWN_CHASSIS","The chassis type is not known.([hex])","The Cisco IOS software installed on the system does not recognize the chassis type specified in the error message.","Ensure that your Cisco IOS software release train supports the chassis type. Upgrade your system to the latest Cisco IOS software release in your release train."
"C6K_PLATFORM","2","PEER_RESET","[chars] is being reset by the [chars]","The local CPU is being reset by the peer CPU when the peer CPU reloads because of exceptions.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_PLATFORM","3","INFO1","[chars]=[hex] [chars]=[hex]","This message provides information regarding the internal state of the SiByte processor.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_PLATFORM","4","ENVMON","System shutdown due to temperature alarms is [chars].","The system has a configuration to shut down a module if its operating temperature exceeds a temperature threshold. This configuration has been bypassed, and a module will still operate in an over-temperature condition. Operating at an over-temperature condition can damage the hardware.","Do not override the sensor alarms that act on an over-temperature condition. Enter the environment-monitor shutdown temperature command to bring the system back to standard temperature detection."
"C6K_PLATFORM","4","RTC_OSCILLATOR","The oscillator in the Real Time Clock is [chars]. Calendar [chars] be maintained during the powered down state of the switch.","A command has been entered that will cause the system calendar not to be maintained during a power down of the switch. The system date and time will require manual setting when the system is powered up during the next boot time. This command is useful to conserve the battery power of the CMOS, which is used to keep the real-time clock active while the switch is powered down. This condition is useful only if the switch is powered down for a long period of time.","If the switch need not be powered down for a long period of time, remove the configuration by entering the no hw-module rtc-oscillator shutdown command."
"C6K_PLATFORM","6","PACKET_BUFFER","This setting will cause a packet buffer error to [chars]","This warning message appears when the configuration contains the error-detection packet-buffer action command. Upon detecting a packet buffer failure on an ASIC, the supervisor engine takes the action specified by the error-detection packet-buffer action command (and shown in [chars]). The choices include error-disabling the ports on a particular ASIC, error-disabling the the module, or automatically power-cycling the module. To view the default and configured actions on all modules, enter the show error-detection packet-buffer command.",".This message is informational only. No action is required."
"C6KPWR-SP","2","PSFAIL","power supply [dec] output failed.","Power supply [dec] has failed.","Replace the power supply."
"C6KPWR-SP","4","PSOK","power supply [dec] turned on.","Power supply [dec] is turned on.","No action is required."
"C6KPWR-SP","4","PSREDUNDANTBOTHSUPPLY","in power-redundancy mode, system is operating on both power supplies.","When the system is in power redundancy mode, it operates on both power supplies.","No action is required."
"C6K_POWER","3","NOTIFY_FAIL","Failed to notify RP of change in operator status for [chars] number [dec] from '[chars]' to '[chars]'","The SP is unable to acquire the resources needed to notify the RP of the event specified in the error message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_POWER","4","PD_NOLINKUP","The device connected to [dec]/[dec] is powered up but its link is not up in [dec] seconds. Therefore, power is withdrawn from the port.","The system withdrew the power that was allocated to the specified port because the port link was not operational in the specified number of seconds.","Try to connect the device to a different port or connect a different device to the port specified in the message."
"C6K_POWER","6","NOLPP","Because of lack of system power, devices that require the system to power them on may not come up within one second.","The local power pools have been deallocated. The module firmware cannot power up the device until it has received authorization for power allocation from the software running on the supervisor engine.","No action is required."
"C6K_PROCMIB","3","IPC_PORTOPEN_FAIL","Failed to open port while connecting to process statistics: error code = [chars]","An error occurred during an attempt to open a port for an IPC message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_PROCMIB","3","IPC_TRANSMIT_FAIL","Failed to send process statistics update : error code = [chars]","An error occurred during an attempt to send an IPC message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_PROCMIB","3","MALLOC_FAILURE_IPC","Failed to allocate IPC message to contact process","A memory allocation failure occurred during the processing of an IPC message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6KPWR","2","INSUFFICIENTPOWER","Powering down all linecards as there is not enough power to operateall critical cards","The switch was operating with two power supplies in combined mode. One of power supplies has failed. Available power is insufficient to support all critical service modules. Critical service modules include modules that support VPNs or IP security. If these critical modules fail, security issues could arise; therefore, all modules have been powered down.","Replace the failed power supply."
"C6KPWR","2","MAJORPOWERALARM","In the absence of power supply 1, system power usage exceeds allowed range of [chars]W. Power total will be reduced in [dec] seconds","This message indicates a major power alarm condition. The power supply in slot 2 has exceeded its allowed range. The range is specified in the error message.","Enter the show power command to determine the actual power usage. Insert a power supply in power supply slot 1, or power down some modules to reduce system power usage. If downtime can be scheduled, move the power supply from slot 2 to slot 1. If this condition persists, the environmental monitor will shut down some modules to prevent a complete power failure."
"C6KPWR","2","MAJORPOWERALARMRECOVER","System power usage has returned to allowed operating range","This message indicates that system power usage has returned to the permitted operating range. The scheduled shutdown is cancelled, and the system will continue operating.","No action is required."
"C6KPWR","2","MINORPOWERALARM","In the absence of power supply 1, system power usage exceeds the recommended range of [chars]W","This message indicates a minor power alarm condition. The power supply in slot 2 has exceeded its allowed range. The range is specified in the error message. Selected modules will be shut down to prevent a complete power failure.","Enter the show power command to determine the actual power usage. Insert a power supply in power supply slot 1, or power down some modules to reduce system power usage. If downtime can be scheduled, move the power supply from slot 2 to slot 1."
"C6KPWR","3","PSUNKNOWN","Unknown power supply in slot [dec] (idprom read failed).","The IDPROM of the power supply in the specified slot cannot be read.","Remove and reinsert the power supply. Fasten the screw and attempt to operate the power supply again. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6KPWR","4","INPUTCHANGE","Power supply [dec] input has changed. Power capacity adjusted to [chars]W","The power supply in the specified slot has detected a change in its input supply. The power capacity for the power supply has been adjusted accordingly.","Enter the show power command to see the current power status. Otherwise, no action is required."
"C6KPWR","4","MAJORPOWERALARMRECOVER","System power usage has returned to allowed operating range","This message indicates that system power usage has returned to the allowed operating range, so the scheduled shutdown was cancelled. The system will continue operating.","No action is required."
"C6KPWR","4","MINORPOWERALARM","In the absence of power supply 1, system power usage exceeds the recommended range of [chars]W","This message indicates a minor power alarm condition. The power supply in slot 2 has exceeded its allowed range. The range is specified in the error message. Selected modules will be shut down to prevent a complete power failure.","Enter the show power command to determine the actual power usage. Insert a power supply in power supply slot 1, or power down some modules to reduce system power usage. If downtime can be scheduled, move the power supply from slot 2 to slot 1."
"C6KPWR","4","MINORPOWERALARMRECOVER","System power usage has returned to normal operating range","This message indicates that system power usage has returned to the normal operating range.","No action is required."
"C6KPWR","4","PS1FAILALERT","Do not remove power supply 1 without inserting another supply. In the absence of power supply 1, system power capacity will be reduced to [chars]W after a [dec] second grace period.","The system is experiencing heavy traffic. In this condition, the single power supply should be used in slot 1 rather than in slot 2.","Insert a power supply in slot 1, or move the power supply from slot 2 to slot 1."
"C6KPWR","4","PS2ONLY","Single power supply system should utilize power supply slot 1","The system is experiencing heavy traffic. In this condition, the single power supply should be used in slot 1 rather than in slot 2.","Move the power supply from slot 2 to slot 1."
"C6KPWR","4","PSINPUTDROP","Power supply [dec] input has dropped","The power supply in the specified slot has detected a drop in its input supply. The power capacity for the power supply has been adjusted accordingly.","Enter the show power command to see the current power status. Otherwise, no action is required."
"C6KPWR","4","PSMISMATCH","power supplies rated outputs do not match.","The two power supplies in the system have different output ratings.","For more efficient load sharing, use power supplies with the same output rating."
"C6KPWR","4","PSNOREDUNDANCY","Power supplies are not in full redundancy, power usage exceeds lower capacity supply","The two power supplies in the system have different output ratings. Current power usage exceeds the capacity of the lower-rated power supply. If the higher-rated power supply fails, the lower-rated power supply will not be able to support all modules that are currently powered up.","To ensure that the system power supplies are optimally redundant, use power supplies with identical output ratings or reduce system power consumption."
"c6k_VSD_ROIR","2","ROIR_INVALID_MODULE_TYPE","Remote switch module type is invalid : slot [dec]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","2","ROIR_INVALID_SYNC_EVENT","ROIR: [chars] receiver process has received an invalid sync event OrIt can't sync the event to its standby counter part","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","2","ROIR_NULL_MODULE_DATA_STRUCTURE","[chars] bay(per-module) data structure ptr is NULL","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","2","ROIR_NULL_MODULE_DATA_STRUCTURE_TYPE","ROIR: [chars] bay(per-module) data structure ptr is not NULLmodule data structure TYPE is NULL","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","2","UNKNOWN_OR_NULL_EVENT_RECEIVED","[chars]: Received [chars] event","The system was unable to create a watched boolean for the ROIR event receiver process, which is used to recieve ROIR messages. This message could indicate a catastrophic software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","2","VECTOR_IS_NULL","[chars] [chars]: Vector is NULLResource or config callbacks couldn't be called when module hadProblems coming online","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","3","ROIR_HUGE_BAY_SIZE","ROIR: [chars], failed to send bulk sync for bay type [dec] due to its huge unit size [dec]","Remote OIR failed to bulk sync for one bay typebecause of its huge unit size.","This is a system error. Please contact Cisco tech-support."
"CDP","3","CHUNK","Chunk_malloc Failure","chunk malloc failure","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","3","ROIR_ISSU_SESS_INCOMPLETE","ROIR ISSU SESSION INVALID: issu nego session not completed","The remote OIR did not complete the ISSU session negotiation. The system is trying to transform a message sent or received. This is a system error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","3","ROIR_LATE_EVENT_RESPONSE","ROIR: sender dropped late response for slot [dec] type [dec] seq [dec] result [dec]","The remote OIR sender received a late processing response. The request timed out while waiting for a response. This is a system error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","3","ROIR_TIMER_WB_FAIL","ROIR Timer Process : Unable to create watched boolean","The system was unable to create a watched boolean for a timer process of ROIR. This message could indicate an internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","BAD_IDPROM","ROIR:idprom error [chars] for index [chars], switch_id [dec]physical_slot [dec]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","BAY_IS_NULL","[chars], bay is NULL bay_type:[dec], index:[dec]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","BULK_SYNC_MSG_SEND_FAILED","[chars] Failure sending Bulk sync msg","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","ERR_GET_SWID","[chars] Error ([dec]) in getting swid and phy_idx for vidx [dec]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","EVENT_SEND_FAILED","Remote Oir::Sender: Events for for Module Type [dec] Slot [dec] could not be sent to core because [chars]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","FAILED_TO_GET_PAK","ROIR:Notify Failed to get pak for [chars] notification","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","FAILED_TO_SEND_NOTIFICATION","ROIR:Notify Failed to send [chars] notification","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","GETBUFFER_FAILED","ROIR: [chars] getbuffer failed. Mod type = [dec], slot# = [dec]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","INVALID_SM_INSTANCE","Unable to get remote module State Machine instance forswitch [dec] slot [dec] module_type [dec]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","MALLOC_FAILURE","Switch Id: [dec] : malloc for [chars] failed","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","NACKED_EVENT","[chars] Remote Oir::CORE NACK'ed event status [dec]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","POST_PROCESSING_NOTIFY_FAILED","ROIR:sender [chars] Post processing notifications to local applns failed","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","PROCESSING_FAILED","ROIR::Sender:: For Bay type [dec] slot [dec] - Core unsuccessful in processing event type [dec] status [dec]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","RECEIVED_NULL_ARG","[chars] received NULL argument","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","REGISTRY_ADDITION_FAILED","Registry addition failed for [chars]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","REMOTE_MODULE_SANITY_CHK_FAILED","sanity check failed for remote module virtual slot number [dec]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","REMOTE_SWITCH_NOT_ONLINE","[chars] remote switch not online [dec]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","RF_CLIENT_NOTIFY_TIMER","[chars](): Could not extend notification timer","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","RF_ROIR_MESG_SEND_FAILED","[chars] (): Error sending remote oir rf message","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","RF_SEND_PEER_MSG_FAILED","[chars] - rf_send_peer_msg failed","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","ROIR_BAD_VSLOT_NUM","[chars] virtual slot [dec] number is invalid for virtual switch module","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","ROIR_EVENT_SEND_NULL_IDPROM","ROIR Event Send failed : fru type [dec] bay type [dec] unit [dec] name [chars] description [chars] - reason: [chars]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","ROIR_RECV_EVENT_ERROR","ROIR:incoming event error received [chars] event","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","ROIR_UNABLE_TO_GET_REMOTE_MODULE_DATA_STRUCT","Unable to get remote switch module data structure forswitch [dec] slot [dec] module type [dec]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","SLOT_IS_ZERO","[chars] slot is ZERO","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","TIMER_EVENT_RECV","ROIR::Receiver::Timer Process got TIMER event","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","TIMER_EXPIRED","ROIR::Receiver::For Switch:[dec] Type [dec] Phy Slot [dec] - [chars] timer expired","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","UNABLE_TO_COMMUNICATE_THREAD","Remote Oir::Sender:: Cannot communicate thread sub block to type [dec] slot [dec]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","2","UNABLE_TO_CREATE_PROCESS","Could not create [chars] Process","The system was unable to create a watched boolean for the timer process of ROIR. This could indicate an internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","UNABLE_TO_CREATE_ROIR_PROCESS","ROIR:Core Process creation failedswitch [dec] slot [dec] module_type [dec]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","UNABLE_TO_CREATE_SWOVER_PROCESS","ROIR:HA error Could not create Remote Swover process!!pid: [dec] for slot [dec]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","UNABLE_TO_CREATE_THREAD_INSTANCE","Remote Oir::Sender::Unable to create a [chars] for process type [dec] slot [dec]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","UNABLE_TO_CREATE_WB","ROIR: [chars] Unable to create [chars] watched boolean","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","UNABLE_TO_GET_THREAD_SUBLOCK","Unable to get thread sub-block. Unable to continue. Remote switch sender thread aborting.","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","UNABLE_TO_INIT","ROIR: Core: Unable to init [chars]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","UNABLE_TO_RETRIEVE_MODULE_DATA_STRUCTURE","Unable to get module data structure for remote module","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","WORKER_THREAD_IDENT_FAILED","ROIR::Recvr [chars] - Could not get identify worker thread id","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","WORKER_THREAD_INVALID_THREAD","ROIR::Recvr - Bay sw[dec] type[dec] slot[dec] - [chars]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","WORKER_THREAD_PACK_DROPPED","ROIR::Rcvr Worker Thread [dec] dropped packet because data section NULL!","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"c6k_VSD_ROIR","6","WORKER_THREAD_SET_OR_CREATE_WORKER_THREAD","ROIR::Rcvr Worker Unable to [chars] thread [chars]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_WAN_C2W","4","READERROR","C2Wire read failed reg [hex] on device [chars]","The SMbus driver failed to read from the specified C2W device.","No action is required if this warning message appears occasionally. If the message appears often in a short period of time, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C6K_WAN_C2W","4","WRITEERROR","C2Wire write failed reg [hex] on device [chars]","The SMbus driver failed to write to the specified C2W device.","No action is required if this warning message appears occasionally. If the message appears often in a short period of time, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_ES","2","CRITICAL_ERR","C7600-ES Line Card Failure: [chars]","A critical error has occured on the C7600-ES Line Card. The message that was previously received on the console or in the system log and cash dump should provide more information of the problem.","If the problem persists, then collect crash dump and File a DDTS. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_ES","2","IOFPGA_IO_BUS_ERROR","C7600-ES Line Card IOFPGA IO [chars] Bus Error: Error = [hex] Error Address = [hex], Error Data = [hex]","An unexpected hardware error condition has occured on the C7600-ES Line Card. SELENE/LINKFPGA/PEFPGA FPGA failed to respond to a read or write access. This message indicates a hardware failure or a malfunction. The linecard will reload to attempt to fix the problem.Error Message    %C7600_ES-2-NMI_RESET: C7600-ES Line Card NMI reset by SUP Explanation    The Supervisor detected C7600-ES line card as unresponsive and attempted to recover line card by issuing an Non Maskable Interrupt.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_ES","2","NP_FAILURE","C7600-ES Line Card NP [dec] Failure: [chars]","An unexpected fatal condition has occured on the C7600-ES Line Card. The message that was previously received on the console or in the system log and cash dump should provide more information of the problem. This message indicates a NP failure or malfunction. The LC will reset to attempt to fix the problem.","If the problem persists, then collect crash dump and File a DDTS. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_ES","2","NP_WORKAROUND","C7600-ES Line Card NP[[dec]] Workaround [chars] after [[dec]] retries","The NP workaround routine on the C7600-ES Line Card Passed/Fail.If the workaround failed, it will result in packets not being forwarded.","Attempt to reload the line card. If the problem persists, then 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_ES","2","PEX_INIT_FAILED","C7600-ES Line Card PCI Express Initialization failed at [chars][[dec]]","The C7600-ES Line Card received an error during initialization when attempting to initialize the PCI Express interface with the forwarding hardware. A hardware problem has prevented the target line card from fully initializing. This will result in packets not being forwarded.","Attempt to reload the line card. If the problem persists, then copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C7600_ES","2","UNRECOVERABLE_FAILURE","C7600-ES Line Card Unrecoverable Failure for Device: [chars]","An unexpected fatal condition has occured on the C7600-ES Line Card. The message that was previously received on the console or in the system log should provide more information on the specific nature of the problem. This message indicates a hardware failure or malfunction. The system will reload to attempt to fix the problem.","If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C7600_ES_LINK","3","FPGA_NOT_READY","[chars] reports Link FPGA is not ready (ConfigPLD status [hex])!","The Link FPGA configuration is not done properly. This could be caused by an incompleted Link FPGA update in a previous FPD upgrade process.","Restart the FPD upgrade. If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C7600_ES","3","KPFPGA_FIFO_INT","C7600-ES Line Card Packet Engine Supertycho KPFPGA Interrupt","An unexpected hardware error condition has occured on the C7600-ES Line Card. Some data traffic between EARL and the firmware ASIC Metropolis is flow controlled.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_ES","3","KPFPGA_PARITY_ERR_INT","C7600-ES Line Card Packet Engine Supertycho KPFPGA Parity Error","An unexpected hardware error condition has occured on the C7600-ES Line Card. A parity error occured during KPFPGA register access.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_ES","3","PE_INT_BUS_ACL_PARITY","C7600-ES Line Card Packet Engine ACL Counter FPGA Parity ErrorIO Bus Error Address = [hex], IO Bus Error Data = [hex]","An unexpected hardware error condition has occured on the C7600-ES Line Card. A parity error is detected when reading from the ACL Counter FPGA.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_ES","3","PE_INT_BUS_INV_ADDR_ERR","C7600-ES Line Card Packet Engine Invalid Address Access on Earl CardIO Bus Error Address = [hex], IO Bus Error Data = [hex]","An unexpected hardware error condition has occured on the C7600-ES Line Card. An IO Bus transfer from the Baseboard goes to an undefined address on the EARL card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_ES","3","PE_INT_BUS_PARITY","C7600-ES Line Card Packet Engine Bus Parity ErrorIO Bus Error Address = [hex], IO Bus Error Data = [hex]","An unexpected hardware error condition has occured on the C7600-ES Line Card. A parity error is detected on the IO Bus from the Baseboard.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C7600_ES","3","PE_INT_BUS_PROTOCOL_ERR","C7600-ES Line Card Packet Engine IO Bus Protocol ErrorIO Bus Error Address = [hex], IO Bus Error Data = [hex]","An unexpected hardware error condition has occured on the C7600-ES Line Card. A transfer on the IO Bus between the Baseboard and the Earl FPGA did not follow the bus protocol.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C7600_ES","3","PE_INT_BUS_ST_PARITY","C7600-ES Line Card Packet Engine Supertycho Parity ErrorIO Bus Error Address = [hex], IO Bus Error Data = [hex]","An unexpected hardware error condition has occured on the C7600-ES Line Card. A parity error is detected when reading from the Supertycho register.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C7600_ES","3","PE_INT_BUS_TIMEOUT","C7600-ES Line Card Packet Engine Bus Timeout: IO Bus Error Address = [hex], IO Bus Error Data = [hex]","An unexpected hardware error condition has occured on the C7600-ES Line Card. Supertycho or the ACL Counter FPGA failed to respond to a read or write access within 1 usec.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C7600_ES","5","BRIDGE_ASIC_INTR","The Bridge-ASIC-[chars][[dec]] interrupt asserted. Addr[[hex]]=[hex]","The Bridge-ASIC on the linecard has experienced an interrupt. The recovery action is already taken and no further action is needed.","No action is required."
"C7600_ES","5","FPGA_IMAGE_CORRUPTED","[chars] failed to program at power up, presumed corrupted.","One of the FPGAs failed to program at boot. The board will not and cannot forward traffic in this state. Failure to program presumably caused by corrupted FPGA image. Likely cause of corrupted FPGA image: write failure during FPGA FPD upgrade. Likely cause of FPGA FPD upgrade fauilure: unexpected LC reset during FPD upgrade.","If failure occured during a FPGA FPD upgrade, ensure that LC was not or will not be inadvertently reset during upgrade. Some FPGA FPD upgrades might require a longer time to complete, and an inadvertent reset during the programming interval will corrupt the FPGA image. If failure did not occur during an FPD upgrade, the FPGA recovery logic will nevertheless necessitate a FPGA FPD upgrade. As a reminder, this requires an FPD bundle file on the supervisor to complete."
"C7600_ES","5","FPGA_RECOVERY","[chars] recovery invoked.","FPD is being invoked to recover corrupted FPGA FPD image. Allow a few minutes for programming to complete. FPD will report results from programming FPGA. If FPD reports success, recovery has completed successfully.","Verify that FPD successfully recovered image."
"C7600_ES","5","MET_TIMEOUT","Rewrite Engine Multicast Expansion Table access timeout recovery action invoked, Address = [hex]","The linecard experienced an IO-BUS timeout while accessing the Multicast Expansion Table. The recovery action is already taken and no further action is needed.","No action is required"
"C7600_ES_LINK","3","FPGA_NOT_READY","[chars] reports Link FPGA is not ready (ConfigPLD status [hex])!","The Link FPGA configuration is not done properly. This could be caused by an incompleted Link FPGA update in a previous FPD upgrade process.","Restart the FPD upgrade. If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C7600_ES_LINK","3","INIT_FAILED","Failed to initialize Link Daughtercard.","Link Daughter card initilization process failed caused by a Link FPGA not ready, memory allocation failure, or a fatal OS kernel error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_ES_LINK","3","INTR_THROTTLE","Interface [chars] PHY interrupt is throttled. Total throttle count [dec].","A 10GE PHY interrupt burst has occurred on one of the interfaces on the link daughter card. The error message indicates that a throttling mechanism has been applied to this port to avoid any operational damage that could be provoked by this event. Possible causes of this problem include a bad transceiver, frequently flapping optical signals, or mismatched path signals (that is, receiving a 10GBASE-W signal on 10GE LAN interface).","Check the interface configuration and received signal characteristics. Verify the XFP transceiver and receive signal path to determine the exact root cause. If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical suppor"
"C7600_ES_LINK","3","SEND_MSG","Link DC failed to notify driver process about a line state change in the interface port [dec]","A line state change has occurred on one of the interface ports on the link daughter card. The error message indicates the port number. The state change notification could not be sent to the link daughter card processor. The cause for this problem could be memory exhaustion.","Enter the show memory summary command to attempt to determine the cause of the error. If it is insufficient system memory, Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"C7600_ES_LINK","4","SCPBUF_ERR","Failed to get packet from SCP packet pool for [chars]","The Line Card failed to allocate a packet from the SCP packet pool for the transceiver control message specified in the error message.","No action is required."
"C7600_ES_LINK","5","ALS_RESTARTREJ","ALS manual restart command on the Interface [chars] is rejected.","The most recent Automatic Laser Shutdown manual restart command (als restart mode manual) on the given interface was issued when the ALS statemachine was not in the IDLE state and could not be accepted.","No action is required."
"C7600_SIP200","3","BADIFCTRL","Corrupted sip-200 information for interface [chars] [[hex]]","The interface SIP 200 information is not valid. This message indicates an internal software error.","Copy the message exactly as it appears on the console or in the system log. Enter the show memory command on the line card. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_SIP200","3","SONET_CLOCK_FAILED","SPA Sonet clock has failed (status = [hex])","The SPA SONET clock has failed. SPAs that rely on the SPA SONET clock for proper operation, such as PoS and ATM, will be affected.","If the SPA SONET clock does not recover, perform an OIR."
"C7600_SIP200","3","SONET_CLOCK_RECOVERED","SPA Sonet clock has recovered (status = [hex])","The SPA SONET clock has recovered.","No action is required."
"C7600_SIP200","4","MEM_MODULE_MISMATCH","Memory modules are not identical","The memory modules do not have identical parameters. This condition might impact performance.","Copy the message exactly as it appears on the console or in the system log. Enter the show memory command on the line card. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_SIP200_MP","1","UNSAFE","Multiprocessor error on [chars]","The line card CPU contains two CPU cores, one of which is the master CPU. The CPU specified in the error message attempted to perform an operation that is illegal for multiprocessor operation between the two CPU cores.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_SIP200_MP","3","INIT_FAILURE","Second CPU initialization failed","The line card CPU unit has two CPU cores in it. The second CPU core is not initialized successfully, so the line card is operating with one CPU core only. You may also see a SYS-2-MALLOCFAIL warning message.","If this message appears when a line card boots up, reload the line card by entering the hw-module module slot reset command. Also, check the amount of memory on the line card by entering the show controller cwan command."
"C7600_SIP200_MP","4","PAUSE","Non-master CPU is suspended for too long, from [hex]([int]) to [hex] for [int] CPU cycles. [chars]","The line card CPU contains two CPU cores, one of which is the master CPU. The master CPU caused the second nonmaster CPU to be suspended for too long a time. This condition could cause the nonmaster CPU to drop packets. This warning indicates a transient software problem, and the line card should continue to operate normally.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_SIP200_MP","4","TIMEOUT","Master CPU request timed out [chars]","The line card CPU contains two CPU cores, one of which is the master CPU. The nonmaster CPU is not responding in time to the request from the master CPU. This warning indicates a transient software problem. The line card should continue to operate normally.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_SIP200_SPIRX","3","INITFAIL","Failed to configure the ingress SPI4.2 device. Error = [hex]","The system cannot program or configure the ingress SPI4.2 device on the line card. This condition indicates an internal hardware error.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPIRX","3","SPA_INTERRUPT","SPA [int] - [chars], SPA Int status = [hex]","A SPA interrupt from the ingress SPI4.2 device has occurred.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPIRX","3","SPI4_LINKERROR","SPA Bay [int], [int] SPI4 Link Failures","Link errors from the ingress SPI4.2 device have occurred.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPIRX","3","SRAM_ERROR_DATA","SRAM[dec] Address = [hex][hex] Data = [hex][hex][hex]_[hex][hex][hex]_[hex][hex][hex]_[hex][hex] [hex]","An SRAM address and data dump has occurred.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPIRX","3","SRAM_INTERRUPT","[chars], Sram Int status = [hex]","An SRAM interrupt has occurred from the ingress SPI4.2 device.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPIRX","3","STATUS_INTERRUPT","[chars], Global Int status = [hex]","A status interrupt has occurred from the ingress SPI4.2 device.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","BADDESC","descriptor [hex], tag [hex], global channel [int]","The egress SPI4.2 device on the line card returns a descriptor entry that is corrupted.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","BADPAK","corrupted packet to [chars]","The egress SPI4.2 device on the line card is handling a packet that is corrupted. This condition indicates that an internal software error has occurred. The corrupted packet has been dropped.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","CHANNEL_ENABLE_FAIL","SPI4 Channel [int] for Bay [int], [chars] Failed","The specified SPI4 channel could not be enabled or disabled.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","DESCR_ERR_SPA0","SPAstatus=[hex], syndrome=[hex], RdRspOvf=[int], RdRspTo=[int], OvfVal=[int], OvfCh=[int], OvfDescHi=[hex], OvfDescLo=[hex], DisChk=[int], SeqErrVal=[int], SeqErrCh=[int]","The egress SPI4.2 device on the line card detected a sequence or FIFO overflow error while processing a TX descriptor. This condition could cause packets to drop.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","DESCR_ERR_SPA1","SPAstatus=[hex], syndrome=[hex], RdRspOvf=[int], RdRspTo=[int], OvfVal=[int], OvfCh=[int], OvfDescHi=[hex], OvfDescLo=[hex], DisChk=[int], SeqErrVal=[int], SeqErrCh=[int]","The egress SPI4.2 device on the line card detected a sequence or FIFO overflow error while processing a TX descriptor. This condition could cause packets to drop.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","DESCR_ERR_SPA2","SPAstatus=[hex], syndrome=[hex], RdRspOvf=[int], RdRspTo=[int], OvfVal=[int], OvfCh=[int], OvfDescHi=[hex], OvfDescLo=[hex], DisChk=[int], SeqErrVal=[int], SeqErrCh=[int]","The egress SPI4.2 device on the line card detected a sequence or FIFO overflow error while processing a TX descriptor. This condition could cause packets to drop.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","DESCR_ERR_SPA3","SPAstatus=[hex], syndrome=[hex], RdRspOvf=[int], RdRspTo=[int], OvfVal=[int], OvfCh=[int], OvfDescHi=[hex], OvfDescLo=[hex], DisChk=[int], SeqErrVal=[int], SeqErrCh=[int]","The egress SPI4.2 device on the line card detected a sequence or FIFO overflow error while processing a TX descriptor. This condition could cause packets to drop.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","DMA_SQERR","Syndrome=[hex], SPA=[int], Ch=[int], RdSz=[int], RdOff=[int][chars]","The egress SPI4.2 device on the line card detected a sequence error while processing a DMA operation. This condition could cause packets to drop.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","EFC_ERR_SPA0","SPAstatus=[hex][chars]","The egress data path device on the line card detected an error condition with the extended flow control (EFC) bus interface. This condition could cause packets to drop.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","EFC_ERR_SPA1","SPAstatus=[hex][chars]","The egress data path device on the line card detected an error condition with the extended flow control (EFC) bus interface. This condition could cause packets to drop.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","EFC_ERR_SPA2","SPAstatus=[hex][chars]","The egress data path device on the line card detected an error condition with the extended flow control (EFC) bus interface. This condition could cause packets to drop.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","EFC_ERR_SPA3","SPAstatus=[hex][chars]","The egress data path device on the line card detected an error condition with the extended flow control (EFC) bus interface. This condition could cause packets to drop.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","EFCEVNT_ERR","[chars]","The egress data path device on the line card detected an error while processing internal extended flow-control events. This condition could cause a reduced packet rate.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","EFC_QUEUE_STUCK","[chars]","The egress data path device on the line card detected an error condition with the Extended Flow Control Bus interface. This condition could cause packets to drop.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","EFCSTAT_FAIL_SPA0","[chars]","The egress SPI4.2 device on the line card detected an EFC status clock or synchronization failure. This condition could cause packets to drop.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","EFCSTAT_FAIL_SPA1","[chars]","The egress SPI4.2 device on the line card detected an EFC status clock or synchronization failure. This condition could cause packets to drop.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","EFCSTAT_FAIL_SPA2","[chars]","The egress SPI4.2 device on the line card detected an EFC status clock or synchronization failure. This condition could cause packets to drop.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","EFCSTAT_FAIL_SPA3","[chars]","The egress SPI4.2 device on the line card detected an EFC status clock or synchronization failure. This condition could cause packets to drop.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","FCSTAT_FAIL_SPA0","[chars]","The egress SPI4.2 device on the line card detected a SPI4.2 status clock or synchronization failure. This condition could cause packets to drop.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","FCSTAT_FAIL_SPA1","[chars]","The egress SPI4.2 device on the line card detected a SPI4.2 status clock or synchronization failure. This condition could cause packets to drop.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","FCSTAT_FAIL_SPA2","[chars]","The egress SPI4.2 device on the line card detected a SPI4.2 status clock or synchronization failure. This condition could cause packets to drop.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","FCSTAT_FAIL_SPA3","[chars]","The egress SPI4.2 device on the line card detected a SPI4.2 status clock or synchronization failure. This condition could cause packets to drop.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","INITFAIL","Failed to configure the egress SPI4.2 device. Error = [hex]","The egress SPI4.2 device on the line card could not be programmed or configured. This indicates an internal hardware error.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","INT_PERR_SPA0","IntMemPerr=[hex][chars]","The egress SPI4.2 device on the line card detected an internal memory parity error. This condition could cause packets to drop.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","INT_PERR_SPA1","IntMemPerr=[hex][chars]","The egress SPI4.2 device on the line card detected an internal memory parity error. This condition could cause packets to drop.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","INT_PERR_SPA2","IntMemPerr=[hex][chars]","The egress SPI4.2 device on the line card detected an internal memory parity error. This condition could cause packets to drop.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","INT_PERR_SPA3","IntMemPerr=[hex][chars]","The egress SPI4.2 device on the line card detected an internal memory parity error. This condition could cause packets to drop.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","MISMATCH","Descriptor ring mismatch: expects [int] got [int]","The egress SPI4.2 device on the line card returned a descriptor entry that did not match what the line card CPU expected. This condition could cause packets to drop.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","OVERRUN_DROP","SPI4 overrun drops packet for SPA [int], queue [int], count [int]","While the egress SPI4.2 device on the line card sends an packet on the extended flow controlled channel, it overruns the SPI4 channel but cannot queue it to the internal hold queue. This indicates an internal software error.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","SPI4_ERR_SPA0","SPAstatus=[hex][chars]","The egress SPI4.2 device on the line card detected an error condition with the SPI4.2 bus interface. This condition could cause packets to drop.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","SPI4_ERR_SPA1","SPAstatus=[hex][chars]","The egress SPI4.2 device on the line card detected an error condition with the SPI4.2 bus interface. This condition could cause packets to drop.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","SPI4_ERR_SPA2","SPAstatus=[hex][chars]","The egress SPI4.2 device on the line card detected an error condition with the SPI4.2 bus interface. This condition could cause packets to drop.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","SPI4_ERR_SPA3","SPAstatus=[hex][chars]","The egress SPI4.2 device on the line card detected an error condition with the SPI4.2 bus interface. This condition could cause packets to drop.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SIP200_SPITX","3","SRAM_ECCERR","EccSynd=[hex], Err1bit=[int], ErrMbit=[int], SecHalf=[int], SPA=[int], Ch=[int], Addr=[hex], DataHi=[hex], DataLo=[hex], DataEcc=[hex]","The egress SPI4.2 device on the line card detected a a parity error in the egress packet memory. This condition could cause packets to drop.","If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"C7600_SSC","3","BRDTYPE_INDEX_MISMATCH","[chars]: Board type ([dec]) and card index ([dec]) do not match","A mismatch was detected between the card index and board type. The C7600-SSC-400 board type is 4 and the card index is 191. The C7600-SSC-600 board type is 5 and the card index is 224.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_SSC","3","DCM_FAIL","[chars]: [chars] FPGA module DCM Lock Failure, status:[hex]","One or more of the Digital Clock Managers (DCMs) for the data path FPGAs failed to lock. This indicates a hardware failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_SSC","3","DP_COUNTERS","[chars]: Failed to create DP counter process.","A process is initiated on bootup to monitor the counters of the data path FPGAs. There was an error creating this process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_SSC","3","DP_ERROR","[chars]: Bus Error initializing [chars] FPGA, addr: [hex].","This FPGA could not be initialized due to a bus error. This condition indicates a hardware failure, possibly due to a failed FPD upgrade.","Enter the show hw-module slot fpd command. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_SSC","3","DP_PROGRAMMING","[chars]: [chars] FPGA failed to program.","This FPGA failed to program. This condition indicates a hardware failure, possibly due to a failed FPD upgrade.","Enter the show hw-module slot fpd command. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_SSC","3","DPRX_ERR","[chars]. [chars]","There was an error receiving data from the SPA, possibly due to data corruption.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_SSC","3","DPTX_ERR","[chars]: [chars].","There was an error sending data to the SPA, possibly due to data corruption.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_SSC","3","DPTX_ERR_MECC","[chars]: [chars]. ERR addr register:[hex].","There was an error sending data to the SPA, possibly due to data corruption.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_SSC","3","DPTX_ERR_SECC","[chars]: [chars]. Single bit error count:[hex], ECC ERR addr register:[hex].","A data corruption error that was automatically fixed was detected while sending data to the SPA.","No action is required if you see this message once. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_SSC","3","DPTX_QDR","[chars]: Error clearing QDR queue [dec].","One of the QDR queues did not flush completely.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_SSC","3","SINGLE_SPA_MODE","[chars]: Module will use only bay [dec]. Bay [dec] is shut.","The 7600-SSC is in single SPA mode.","No action is required."
"C7600_SSC","3","SSC_BAY_SHUT","[chars]: Bay [dec] is shutdown because [chars] is in single-spa-mode","The specified bay is shut down. In single SPA mode, only one bay is active.","Refer to the IPsec VPN SPA documentation for information about single SPA mode."
"C7600_SSC","3","SW_ERROR","[chars]: [chars]","This error is seen when there is a problem in internal software coding; it should not be seen under normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_SSC","3","UNKNOWN_BRDTYPE","[chars]: SSC board type [dec] is not supported","Board type does not belong to either C7600-SSC-600 or C7600-SSC-400.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_SSC","7","DP_DISABLE","[chars]: [chars] FPGA is forced disabled.","This FPGA has been disabled. Forced disabling is a debugging feature.","No action is required."
"C7600_SSC600","3","DCM_FAIL","[chars] FPGA module DCM Lock Failure, status:[hex]","One or more of the Digital Clock Managers (DCM) for the data path FPGAs failed to lock. This condition indicates a hardware failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_SSC600","3","DP_COUNTERS","Failed to create DP counter process.","A process is initialized at bootup to monitor the counters of the data path FPGAs. There was an error in creating this process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_SSC600","3","DP_ERROR","Bus Error initializing [chars] FPGA, addr: [hex].","This FPGA could not be initialized because of a bus error. This condition indicates a hardware failure, possibly due to a failed FPD upgrade.","Enter the show hw-module slot fpd command to gather more information on the specific nature of the condition. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_SSC600","3","DP_PROGRAMMING","[chars] FPGA failed to program.","This FPGA failed to program. This condition indicates a hardware failure, possibly due to a failed FPD upgrade.","Enter the show hw-module slot fpd command to gather more information on the specific nature of the condition. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_SSC600","3","DPRX_ERR","[chars].","There was an error receiving data from the SPA, possibly due to data corruption.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_SSC600","3","DPTX_ERR","[chars].","There was an error sending data to the SPA, possibly due to data corruption.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_SSC600","3","DPTX_QDR","Error clearing QDR queue [dec].","One of the QDR queues did not clear completely.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_SSC600","3","SINGLE_SPA_MODE","Module will use only bay [dec]. Bay [dec] is shut.","The 7600-SSC-400 is in single SPA mode.","This message is informational. No action is required."
"C7600_SSC600","3","SSC_BAY_SHUT","Bay [dec] is shutdown because 7600-SSC-400 is in single-spa-mode","The specified bay is shut down. In single SPA mode, only one bay is active.","Refer to the IPsec VPN SPA documentation for information about single SPA mode."
"C7600_SSC600","3","SW_ERROR","NULL","This condition occurs when there is a problem in internal software coding; it should not occur under normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"C7600_SSC600","7","DP_DISABLE","[chars] FPGA is forced disabled.","This FPGA has been disabled. Forced disabling is a debugging feature.","No action is required."
"CALL_HOME","3","CLI_CMD_RUN_FAILED","No VTY connection available to run CLI command for event notification message (ERR [dec])","Call Home was unable to open a VTY connection to run CLI commands and collect output for use in notification messages.","Increase the number of configured VTY lines or change the Alert Group subscriptions to make them more restrictive (to reduce the number of simultaneous event triggers)."
"CALL_HOME","3","HTTP_REQUEST_FAILED","Call-Home HTTP request failed (ERR [dec])","The Call Home HTTP message failed to send to an HTTPS server.","Check whether you have configured a valid trustpoint certificate for secure HTTP messages."
"CALL_HOME","3","HTTP_REQUEST_FAILED","failed to send HTTP request to : %s (ERR %d : %s)","The call-home HTTP message failed to send to HTTPS server,","Please check the connectivity of your network and the DNS setting"
"CALL_HOME","3","MESSAGE_SIZE_OVER_LIMIT","XML message size over limit, failed to send call-home message. configured message size limit ([dec]) is less than current message minimum length required ([dec]).","Unable to create the message because the message size exceeds the configured message size limit.","Increase the destination message size limit."
"CALL_HOME","3","REQUEST_MESSAGE_FAILED","call-home request message failed to send (ERR [dec], [chars])","An attempt to send a call-home request message has failed.","Configure Call Home to send call-home request messages."
"CALL_HOME","6","REQUEST_MESSAGE_SUCCEEDED","call-home request message succeeded","A call-home request message was sent successfully.","No action is required."
"CALL_HOME","3","SMTP_SEND_FAILED","Unable to send notification using all SMTP servers (ERR [dec], [chars])","Call Home was unable to send notification using any of the configured SMTP servers.","Verify the configuration of the Call Home SMTP servers and ports used to connect to the servers. Verify that the remote SMTP servers are reachable and that they are operating correctly."
"CALL_HOME","4","MESSAGE_IS_TRUNCATED","message size over limit, call-home message is truncated. configured message size limit ([dec]) is less than current message total length required ([dec]).","The Call Home message is truncated because it exceeds the configured message size limit.","Increase the destination message size limit."
"CALL_HOME","5","HTTPS_NOT_SUPPORTED","This image version does not support HTTPS","The configured message destination is a secure HTTP (HTTPS) URL, but this image does not support secure HTTP.","Upgrade your system image to a crypto image, which supports secure HTTP."
"CALL_MGMT","1","UNAVAILABLE","%s","The specific message text is supplied by the Call Management software. This indicates an initialization failure. When this occurs, the Call Management subsystem is not operational.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CALL_MGMT","1","UNAVAILABLE","%s","The specific message text is supplied by the Call Management software. This indicates that internal data was corrupted due to a software error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CALL_MGMT","4","UNAVAILABLE","%s","The specific message text is supplied by the Call Management software. This indicates that a call record is missing from active call list","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CARRIER","2","UNAVAILABLE","3 NP108s were not found on Tetryl card, %d detected.","Tetryl requires 3 NP108s to be present","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CARRIER","2","UNAVAILABLE","Cannot mix E1 PRI and CT3 DFC in chassis, do not power up invalid card in slot %d","The user has put E1 PRI and CT3 DFC cards in the same chassis.","Remove the extra E1 PRI or CT3 DFC card."
"CARRIER","2","UNAVAILABLE","Cannot mix T1 and E1 8PRI DFC cards in chassis, do not power up invalid card in slot %d","The user has put T1 and E1 8PRI DFC cards in the same chassis.","Remove the extra T1 or E1 8PRI DFC card."
"CARRIER","2","UNAVAILABLE","Too many 8PRI DFC cards, do not power up invalid card in slot %d","The user has put too many 8PRI DFC cards in the chassis.","Remove the extra 8PRI DFC card."
"CARRIER","2","UNAVAILABLE","Too many CT3 DFC cards, do not power up invalid card in slot %d","The user has put too many CT3 DFC cards in the chassis.","Remove the extra CT3 DFC card, or 8PRI DFC card causing problem"
"CARRIER","2","UNAVAILABLE","Too many trunk DFC cards, do not power up invalid card in slot %d","The user has put too many trunk DFC cards in the chassis.","Remove the extra trunk DFC card."
"CARRIER","3","UNAVAILABLE","DFC Carrier Platform Init Failed - Slot %d","DFC Carrier Platform Init Failed","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CARRIER","3","UNAVAILABLE","DFC Power Changed - DFC %d","DFC Power is fluctuating","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CARRIER","3","UNAVAILABLE","DFC Power-On Failed - DFC %d","DFC Power-On Failed","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CARRIER","3","UNAVAILABLE","DFC Reset Failed - DFC %d","During OIR Removal process, DFC reset failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CARRIER","3","UNAVAILABLE","DFC initialization is failed - DFC %d","DFC initialization is failed because of several reasons","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CARRIER","3","UNAVAILABLE","DFC is already initialized - DFC %d","DFC is already initialized, no need to initialize again","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CARRIER","3","UNAVAILABLE","Invalid DFC - DFC %d type %d","DFC has invalid board id/type","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CASA","3","UNAVAILABLE","Incoming packet is CASA v%d, this router is v%d","A packet was received for the wrong version of CASA","Verify that all CASA devices are running the same version of the protocol"
"CASA","4","UNAVAILABLE","%s security information in CASA packet.","Security check failed.","Make sure all CASA systems are configured with the same password."
"CASA","4","UNAVAILABLE","Message parsing error: %s","Failed to parse an incoming packet","If this message is occurring repeatedly, enable 'debug ip casa error' and record the output, call your Cisco technical support representative, and provide the gathered information."
"CASA","4","UNAVAILABLE","Unexpected condition: %s","An unexpected condition was detected while performing CASA operation","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CASA","4","UNAVAILABLE","Unexpected error: %s","An unexpected error occurred while performing CASA operation","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CASA","4","UNAVAILABLE","Wildcard overlap: %s","A CASA wildcard, received on one port, has been overwritten by a service manager sending to another port. This message may appear once if you are migrating your service to a new forwarding-agent port, if it recurs, it could indicate a configuration problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CAMP","3","MP_INIT_FAILURE","Second CPU initialization failed","The module CPU unit has two CPU cores in it. The second CPU core did not initialize successfully, so the module is operating with only one CPU core.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CAPI_EC","4","GROUP_RATE_LIMITED","Adding interfaces of the same port-group ([dec]-[dec]) on [chars] to an etherchannel will not increase the channel throughput!","Because ports on the specified slot use oversubscription, the total throughput of the port channel is limited by the port group.","If more throughput is required, either use ports from a line card that does not use oversubscription, or use ports from different line cards or port groupings on oversubscribed line cards. For example, if the line card has 48 ports in groups of 8, you can select ports 1, 9, 17, 25, 33, and 41 for the same port channel."
"CAPI_EC","4","RATE_LIMITED","Adding [chars] interfaces to an etherchannel will limit channel throughput to 1 Gbps!","Because ports on the indicated card type use oversubscription, throughput of the port channel is limited.","If more throughput is required, either use ports from a line card that does not use oversubscription, or use ports from different line cards or port-groupings on oversubscribed line cards. For example, if the line card has 48 ports in groups of eight, you can select ports 1, 9, 17, 25, 33, and 41 for the same port channel."
"CAPI_EC","4","SLOT_RATE_LIMITED","Adding interfaces on slot [dec] to an etherchannel will limit channel throughput to 1 Gbps!","Because ports on the indicated slot use oversubscription, the total throughput of the port channel is limited.","If more throughput is required, either use ports from a line card that does not use oversubscription, or use ports from different line cards or port-groupings on oversubscribed line cards. For example, if the line card has 48 ports in groups of eight, you can select ports 1, 9, 17, 25, 33, and 41 for the same port-channel."
"CARDMGR","2","ESF_DEV_ERROR","An error has occurred on [chars]: [chars]","The ESF encountered an error during normal operation. Steps need to be taken to resolve the problem and allow traffic through the SIP 400 line card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CARDMGR","2","ESF_LOAD_FAIL","[chars] failed to load: [chars]","The ESF could not be loaded because one of the steps in the startup sequence failed. This ESF is now not operational, which stops the traffic through the SIP-400 line card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CARDMGR","2","NULL_OBJECT","Missing device object (%s) for pending interrupt","A hardware device asserted an interrupt to report an event, but there is no device object for this device.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CARDMGR","2","SPABUS_ERROR","A [chars] FSM SPA bus error has occurred in subslot [dec]","An FSM SPA bus error occurred during normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CARDMGR","2","SYNC_CHECK_FAIL","The SPA in subslot %d/%d %s SPI4 interface sync with the host failed.","The syncing of the SPA to the host on the SPI4 bus failed for either ingress, egress, or both, as specified.","Please attempt to reseat the specified SPA, making sure it is properly screwed down. If it still fails, try the SPA in another subslot if possible to determine if the problem is the SPA or the host card. If you still require assistance, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CARDMGR","2","TCAM_REG_OVERWRITE","Attempt made to overwrite registered TCAM callback function %08X with %08X","A single function can be set as a callback for TCAM events. This message indicates that an attempt to set a new callback has failed because a callback function has already been set.","Please attempt to reseat the specified SPA, making sure it is properly screwed down. If it still fails, try the SPA in another subslot if possible to determine if the problem is the SPA or the host card. If you still require assistance, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CARDMGR","4","ESF_DEV_RELOADED","The ESF microcode has automatically recovered from an internal inconsistency.","An ESF internal inconsistency was detected during normal operation. The ESF microcode was reloaded to resolve the inconsistency.","No action is required unless this message appears multiple times. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CARDMGR","4","ESF_LOAD_WARN","[chars] microcode load: [chars]","The ESF was loaded even though a potential problem exists.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CARDMGR","4","ESF_LOOPBACK_FAIL","ESF loopback packet test failed: tried [dec] sent [dec] received [dec]","The ESF loopback packets sent after a microcode reload experienced excessive packet loss. This condition is usually an indication that data traffic through this line card is impacted as well.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CARDMGR","5","ESF_DEV_INFO","ESF internal inconsistency corrected on [chars]: [chars]","An ESF internal inconsistency was detected and corrected during normal operation.","No action is required unless this message appears multiple times. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CARDMGR","5","ESF_UCODE_DONE","Microcode download complete for [chars], time elapsed [time-stamp]","The ESF microcode was successfully downloaded and started. The forwarding engine is now configured and operational. The time elapsed is measured from the ESF_UCODE_START message.","This is a normal activity at Cisco IOS boot time or after a fatal ESF error occurs. No action is necessary."
"CARDMGR","5","ESF_UCODE_START","Downloading microcode [chars] for [chars], version=[chars], [chars]","The platform code was starting to download a particular ESF microcode image.","This is a normal activity at Cisco IOS boot time or after a fatal ESF error occurs. No action is necessary."
"CAT6000_SSC","3","BRDTYPE_INDEX_MISMATCH","[chars]: Board type ([dec]) and card index ([dec]) do not match","A mismatch was detected between the card index and board type. For the C7600-SSC-400, the board type is 4 and the card index is 191. For the C7600-SSC-600, the board type is 5 and the card index is 224.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CAT6000_SSC","3","DCM_FAIL","[chars]: [chars] FPGA module DCM Lock Failure, status:%08x","One or more of the digital clock managers (DCM) for the data path FPGAs failed to lock. This indicates a hardware failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CAT6000_SSC","3","DPRX_ERR","[chars]. [chars]","An error occurred while receiving data from the SPA, possibly due to data corruption.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CAT6000_SSC","3","DPTX_ERR","[chars]: [chars].","An error occurred while sending data to the SPA, possibly due to data corruption.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CAT6000_SSC","3","DPTX_ERR_MECC","[chars]: [chars]. ERR addr register:0x%08lx.","An error occurred while sending data to the SPA, possibly due to data corruption.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CAT6000_SSC","3","DPTX_ERR_SECC","[chars]: [chars]. Single bit error count:0x%08lx, ECC ERR addr register:0x%08lx.","A data corruption error was detected and automatically fixed while sending data to the SPA.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CAT6000_SSC","3","DPTX_QDR","[chars]: Error clearing QDR queue [dec].","One of the QDR queues did not flush completely.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CAT6000_SSC","3","DP_COUNTERS","[chars]: Failed to create DP counter process.","A process is spawned on bootup to monitor the counters of the data path (DP) FPGAs. There was an error creating this process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CAT6000_SSC","3","DP_ERROR","[chars]: Bus Error initializing [chars] FPGA, addr: 0x%08x.","This FPGA could not be initialized due to a bus error. This condition indicates a hardware failure, possibly due to a failed FPD upgrade.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show hw-module slot fpd commands and your pertinent troubleshooting logs."
"CAT6000_SSC","3","DP_PROGRAMMING","[chars]: [chars] FPGA failed to program.","This FPGA failed to program. This condition indicates a hardware failure, possibly due to a failed FPD upgrade.","f this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show hw-module slot fpd commands and your pertinent troubleshooting logs."
"CAT6000_SSC","3","SINGLE_SPA_MODE","[chars]: Module will use only bay [dec]. Bay [dec] is shut.","The 7600-SSC is in single SPA mode.","No action is required."
"CAT6000_SSC","3","SSC_BAY_SHUT","[chars]: Bay [dec] is shutdown because [chars] is in single-spa-mode","The specified bay is shut down. In single SPA mode, only one bay is active.","Refer to the IPsec VPN SPA documentation for information about single SPA mode."
"CAT6000_SSC","3","SW_ERROR","[chars]: [chars]","This error indicates a problem in internal software coding.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CAT6000_SSC","3","UNKNOWN_BRDTYPE","[chars]: SSC board type [dec] is not supported","The board type is not supported.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CAT6000_SSC","7","DP_DISABLE","[chars]: [chars] FPGA is forced disabled.","This FPGA has been forced disabled. This is a debugging feature.","No action is required."
"CAT6000_SVC_APP_HW","0","DPFPGAINTFATALERR","[chars], hardware register offset [hex] value [hex]","A Data Path FPGA fatal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CAT6000_SVC_APP_HW","2","APP_PROC_ALERT","Service Application Processor alert: [chars]","A hardware problem was detected on the Service Application Processor.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CAT6000_SVC_APP_HW","2","HW_INTERRUPT","Hardware interrupt for Device: [chars]","A hardware interrupt occured on the Line card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CAT6000_SVC_APP_HW","2","UNSUPPORTED_HW","Unsupported Hardware: [chars]","Unsupported hardware was found on the Line card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CAT6000_SVC_APP_HW","3","BAD_IFCOMTYPE","Bad ifcom message type=[int]","A Trifecta module passed down a message that the RP software was not prepared to handle.","lcp-services"
"CAT6000_SVC_APP_HW","3","DPFPGADRVFAIL","DPFPGA object driver [chars] failure","DPFPGA object driver create or pll check or TSE and XAUIs bring-up or check all blocks except GLOBAL and XAUIs or check global interrupt register or check XAUIs global status or check XAUIs global error status failure","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CAT6000_SVC_APP_HW","3","DPFPGAHWFAIL","Hardware bring-up failure","The DPFPGA manager failed to bring-up the hardware prior to constructing the device object driver.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CAT6000_SVC_APP_HW","3","DPFPGAIMAGE","DPFPGA image [chars] error, IOFPGA config flash status register [hex]","A datapath FPGA image download or CRC error has occurred. The actual hardware reason is stored in IOFPGA config flash register.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CAT6000_SVC_APP_HW","3","DPFPGAINTERR","[chars], hardware register offset [hex] value [hex]","A datapath FPGA error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CAT6000_SVC_APP_HW","3","DPFPGAMNGRFAIL","DPFPGA manager [chars] failure","The DPFPGA manager create various processes failure or initialization failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CAT6000_SVC_APP_HW","3","DPFPGASEUERR","A [chars] occured on the DPFPGA. SEU_EMR_REG = [hex]","DPFPGA error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CAT6000_SVC_APP_HW","3","DPFPGATIMEOUT","DPFPGA [chars] timeout after [dec]ms","DPFPGA init done or pll lock timeout during bring-up","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CAT6000_SVC_APP_HW","3","IPCALLOCFAIL","Failed to allocate IPC buffer [chars]","The Linecard failed to allocate a buffer for communication with the Route Processor (Draco).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CAT6000_SVC_APP_HW","3","IPCPORT","Failed to [chars] IPC port '[chars]', error [chars]","The Linecard failed to create a port for communication with the Route Processor (Draco).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CAT6000_SVC_APP_HW","3","IPCSENDFAIL","Failed to send IPC message [chars]","The Linecard failed to send a message to the Route Processor (Draco).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CAT6000_SVC_APP_HW","3","SHMEMFAIL","Shared memory write time out after [dec]ms","The DPFPGA manager failed to get into the critical section for update the statistics counters in the PCI shared memory","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CAT6000_SVC_APP_HW","6","APP_FPGAVER_MISMATCH","Module [dec]: [chars]","Service application FPGA version mismatch.","No action is required."
"CAT6000_SVC_APP_HW","6","APP_RESTART_REASON","[chars] : [chars]","Service application restart reason.","No action is required."
"CAT6000_SVC_APP_HW","6","APPONLINE","Service application in slot [int] is online.","Service application has finished booting up and is online","No action is required."
"CAT6000_TRIFECTA","0","DPFPGAINTFATALERR","[chars], hardware register offset [hex] value [hex]","A DPFPGA fatal error has occurred.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"CAT6000_TRIFECTA","2","APP_PROC_ALERT","Service Application Processor alert: [chars]","A hardware problem was detected on the Service Application Processor.","If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"CAT6000_TRIFECTA","2","HW_INTERRUPT","Hardware interrupt for Device: [chars]","A hardware interrupt occured on the line card.","If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"CAT6000_TRIFECTA","3","BAD_IFCOMTYPE","Bad ifcom message type=[int]","A Trifecta module passed down a message that the RP software was not prepared to handle.","If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"CAT6000_TRIFECTA","3","DPFPGADRVFAIL","DPFPGA object driver [chars] failure","DPFPGA object driver create or pll check or TSE and XAUIs bring-up or check all blocks except GLOBAL and XAUIs or check global interrupt register or check XAUIs global status or check XAUIs global error status failure","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"CAT6000_TRIFECTA","3","DPFPGAHWFAIL","Hardware bring-up failure","The DPFPGA manager failed to bring-up the hardware prior to construct the device object driver","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"CAT6000_TRIFECTA","3","DPFPGAIMAGE","DPFPGA image [chars] error, IOFPGA config flash status register [hex]","DPFPGA image download or CRC error, the actual hardware reason is stored in IOFPGA config flash register","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"CAT6000_TRIFECTA","3","DPFPGAINTERR","[chars], hardware register offset [hex] value [hex]","A DPFPGA error has occurred.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"CAT6000_TRIFECTA","3","DPFPGAMNGRFAIL","DPFPGA manager [chars] failure","The DPFPGA manager has created a processes failure or an initialization failure.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"CAT6000_TRIFECTA","3","DPFPGATIMEOUT","DPFPGA [chars] timeout after [dec]ms","DPFPGA init done or pll lock timeout during bring-up","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"CAT6000_TRIFECTA","3","IPCALLOCFAIL","Failed to allocate IPC buffer [chars]","The linecard failed to allocate a buffer for communication with the Route Processor (Draco).","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"CAT6000_TRIFECTA","3","IPCPORT","Failed to [chars] IPC port '[chars]', error [chars]","The linecard failed to create a port for communication with the Route Processor (Draco).","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"CAT6000_TRIFECTA","3","IPCSENDFAIL","Failed to send IPC message [chars]","The linecard failed to send a message to the Route Processor (Draco).","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"CAT6000_TRIFECTA","3","SHMEMFAIL","Shared memory write time out after [dec]ms","The DPFPGA manager failed to get into the critical section for update the statistics counters in the PCI shared memory.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"CAT6000_TRIFECTA-3-X86_SHUT_ERR%CBUS","3","ADDRFILTR","Interface %s, address filter %s command failed, code %#04x","The specified address filter command sent to the specified interface failed with the displayed error code.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","ADDRFILTR","Interface %s, address filter %s command failed, code %#04x","The specified address filter command sent to the specified interface failed with the displayed error code.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CBUS","3","BADRXEOFVEC","%s ustatus: %s (%04x), %04x %04x %04x %04x","Debugging information when an IP panics.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CBUS","3","BADTXSTATE","%s ustatus: %s (%04x), %04x %04x %04x %04x","Debugging information when an IP panics.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CBUS","3","BADVC","%s %d/%d got bad VC packet %08x %08x %08x %08x %08x %08x %08x %08x","An interface received a packet with bad VC encapsulation. This indicates either a software or hardware problem.","If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative."
"CBUS","3","CATMCFG","Interface %s, Cannot config interface, CBus ATM MEM 0x%x, status %d","A software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CBUS","3","CATMREJCMD","%s %s command failed (error code 0x%04x)","The cBus ATM microcode rejected a command sent by the Route Processor (RP). The error code is the status value returned by the command.","If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative."
"CBUS","3","CCBCMDFAIL0","Controller %d, cmd (%d) failed (0x%-04x)","A command sent from the system to an interface processor failed to complete successfully.","The system recovered by generating an error code to the requester."
"CBUS","3","CCBCMDFAIL1","Controller %d, cmd (%d 0x%-08x) failed (0x%-04x)","A command sent from the system to an interface processor failed to complete successfully.","The system recovered by generating an error code to the requester."
"CBUS","3","CCBCMDFAIL3","Controller %d, cmd (%d 0x%-04x, 0x%-04x, 0x%-04x) failed (0x%-04x)","A command sent from the system to an interface processor failed to complete successfully.","The system recovered by generating an error code to the requester."
"CBUS","3","CE3DSX3ERR","(%s)Illegal E3 value - unit is %d","A status information message was received from the CT3 VIP, but during message processing it was detected that an element in the data structure corresponding to the status information message has not been set. This condition may be caused by either an element that has not been passed by the VIP or a corruption in the status message.","If this error recurs, enter the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information."
"CBUS","3","CFGCMDDROPPED","Config queue is full, command was dropped, slot %d","Sending a config command was retried. The receiving queues were still full after retries therefore the command was dropped.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CBUS","3","CMD","Cmd failed: %s, response %#04x, %s","A software or hardware error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CBUS","3","CT3STAT","Out of buffers--losing status information for CT3 on VIP card","A status information message from the VIP was received. A memory buffer is required to process the status information message, but the memory allocation routine due to insufficient system buffer memory. Therefore, the status information message was not processed. This condition may be caused either by a heavy memory utilization at the time of the memory buffer request or by insufficient memory in the system.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If this message recurs or appears regularly, contact your Cisco technical representative to upgrade the memory of the system."
"CBUS","3","CTRACHECK","Interface %s, Adapter Check Error (%04x %04x %04x %04x)","The Token Ring monitor firmware detected a fatal error on the interface card.","Issue a clear interface command. If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative."
"CBUS","3","CTRBADLOVE1","Interface %s, SRB_COMPLETE lovenote received with unknown command (0x%04x)","The system received a message from the Token Ring interface but does not recognize the message.","If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative."
"CBUS","3","CTRBADLOVE1_DUMP","Dump of MEMB follows -SRB_ADDR: %04x %04x %04x %04x %04x %04x %04x %04x","The system is printing codes related to a previous lovenote error message.","If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative."
"CBUS","3","CTRCMDFAILED2","Interface %s, CTR Command %s Failed, Code %#04x","A command sent from the system to the Token Ring interface failed to complete successfully.","If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative."
"CBUS","3","CTRCMDFAILED","Interface %s, CTR Command %s Failed, %s (%#04x)","A command sent from the system to the Token Ring interface failed to complete successfully.","If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative."
"CBUS","3","CTRINIT","Interface %s, CTR Initialization Failed - %s","The Token Ring interface failed one of its internal self-tests.","Issue a clear interface command. If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative."
"CBUS","3","CTRLRCMDFAIL0","Controller %d, cmd (%d) failed (0x%-04x) count (%d)","A command sent from the system to an interface processor failed to complete successfully.","The system recovered by generating an error code to the requester."
"CBUS","3","CTRLRCMDFAIL1","Controller %d, cmd (%d 0x%-08x) failed (0x%-04x) count (%d)","A command sent from the system to an interface processor failed to complete successfully.","The system recovered by generating an error code to the requester."
"CBUS","3","CTRRAMTEST","Interface %s, RAM Addressing Test Failed - %s","The Token Ring interface failed its memory diagnostic tests.","Issue a clear interface command. If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative."
"CBUS","3","CTRRSET","Interface %s failed to initialize","The Token Ring interface failed to insert into the Token Ring. The interface is placed into reset state and will not automatically try to re-insert itself.","Issue a clear interface command. If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative."
"CBUS","3","CTRUCHECK","Interface %s, Microcode Check Error","The Token Ring interface microcode detected an unrecoverable error.","Issue a clear interface command. If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative."
"CBUS","3","DAUGHTER","Unit %d, daughter controller %d failed %s test - interface disabled","A hardware component failed an internal diagnostic test. Test output and descriptions of ranges follow: Unit [dec] (ranges 0-14): Indicates the Multibus jumper setting for the ciscoBus controller, or in the Cisco 7000, a slot number. daughter controller [dec] (ranges 0-3): Indicates the ciscoBus relative slot number (0 to 3, or in the Cisco 7000, 0 to 4) of the daughter card that failed the test. failed [chars] test ([chars]= memd read, memd write):If the failed test was memd read, the processor was able to write to shared ciscoBus buffer memory from the ciscoBus registers, but was unable to read back that memory through special commands to the daughter card. If the failed test was memd write, writes to the memory device through the daughter card were not verified successfully with reads through the ciscoBus controller. The daughter card under test responds successfully to some commands (otherwise the software would have received a DAUGHTER_NO_RSP message), but its memory device tests failed. The daughter card must be able to write to some memory device addresses; otherwise, it cannot respond to any commands.","First check that the daughter controller card is properly seated in its Multibus and ciscoBus connectors. Next, swap daughter cards and check whether the error follows the daughter card or the slot. If the message recurs, call your technical support representative for assistance."
"CBUS","3","DAUGHTER_NO_RSP","Unit %d, daughter %d, not responding (0x%04x) - disabled","A hardware component failed an internal diagnostic test. Test output and descriptions of ranges are as follows: Unit [dec] (ranges 0-14): Indicates the Multibus jumper setting for the ciscoBus controller. daughter controller [dec] (ranges 0-3): Indicates the ciscoBus relative slot number (0 to 3, or in the Cisco 7000, 0 to 4) of the daughter card that failed the test. The daughter card hardware was recognized across the cBus backplane, but the daughter card did not respond to the first command issued to it. This condition is a result of one of the following: the daughter card did not reset, or the microcode on the card is in a hung state, or the card cannot fully communicate across the ciscoBus backplane (cannot read or write shared MEMD or does not get the MALU_ATTENTION signal across the ciscoBus).","First, make sure that the daughter card is properly seated in its Multibus and ciscoBus connectors. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information"
"CBUS","3","FCICMDFAIL0","Controller %d, cmd (%d) failed (0x%-04x) count (%d)","A command sent from the system to an interface processor failed to complete successfully.","The system recovered by generating an error code to the requester."
"CBUS","3","FCICMDFAIL1","Controller %d, cmd (%d 0x%-08x) failed (0x%-04x) count (%d)","A command sent from the system to an interface processor failed to complete successfully.","The system recovered by generating an error code to the requester."
"CBUS","3","FSIPRSET","Interface %s, Error (%-04x) %s - fsip_reset()","A Fast Serial Interface Processor (FSIP) did not respond to a reset request from the Route Processor.","Check FSIP electrical connections, cable, and ciscoBus connections. An FSIP microcode reload will be required. If the check of electrical connections reveals no problems and the message recurs, call your technical support representative for assistance."
"CBUS","3","HALSDHERR","(%s)Illegal sdh value - unit is %d","Internal data structure is corrupted, which causes the love letter to drop.","If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative."
"CBUS","3","HALSTAT","Out of buffers--losing status information for ChSTM-1 on VIP card","An internal software resource has been exhausted.","If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative."
"CBUS","3","HSSIRSET","Interface %s, Error (%-04x) %s - hssi_reset()","A command to reset an HSSI interface was issued by the RSP, but the interface did not respond to the command within the expected time delay. The delay is given for the processor to return the buffers that it has allocated and to perform any necessary cleanup. This condition may be caused by a large number of buffers that have been allocated by the interface due to either heavy traffic or a hardware problem with the interface.","Verify that the card is properly seated. If this error recurs, then issue the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information."
"CBUS","3","INITERR","Interface %d, Error (%-04x), idb %08x %d %s - cbus_init()","The switch processor or ciscoBus controller signaled an error while processing a packet or selecting an interface. This indicates a software problem.","If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative."
"CBUS","3","INTR","Interface %d, idb %08x %d %s - cbus_interrupt()","The switch processor or ciscoBus controller returned a nonsensical value.","If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative."
"CBUS","3","OUTHUNG","%s: tx%c output hung (%-04x - %s), %s","A transmission attempt on an interface failed. The interface might not be attached to a cable or there might be a software problem.","Check that the interfaces are all connected to the proper cables. If that is not the problem, call your technical support representative."
"CBUS","3","POLLFAIL","Interface %s failed to respond, debug info follows","A Token Ring interface card failed to respond to periodic polling. This can indicate a software or hardware problem. See CBUS-3-POLLFAILDAT for the syntax of this message.","If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative."
"CBUS","3","POTSTAT","Out of buffers--losing status information for POTENT on VIP card","An internal software resource has been exhausted.","If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative."
"CBUS","3","RESETNXI","Reset of removed interface %x (%s)","An interface reset was attempted on an interface that was removed from the router. This message appears if you use the shutdown command to bring down a removed interface.","Informational only. No action required."
"CBUS","3","SENDIPCMDFAIL","Send Ip Cmd Failed. Command dropped after %d retries, CCB 0x%x, slot %d, cmd code %d","Sending an ip command was retried. The receiving queues were still full after retries therefore the command was dropped.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CBUS","3","SRPRSET","Interface %s, Error (%-04x) %s - srp_reset()","A command to reset an SRP interface was issued by the RSP, but the interface did not respond to the command within the expected time delay. The delay is given for the processor to return the buffers that it has allocated and to perform any necessary cleanup. This condition may be caused by a large number of buffers that have been allocated by the interface due to either heavy traffic or a hardware problem with the interface.","Verify that the card is properly seated. If this error recurs, then issue the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information."
"CBUS","3","TESTFAIL","Unit %d, failed %s test - interface disabled","A hardware component failed an internal diagnostic test.","Check switch settings on the interface cards. Check for proper unit numbers. Reset the cards. Replace the malfunctioning device."
"CBUS","3","TXSTARTPENDACTIVE","%s ustatus: %s (%04x), %04x %04x %04x %04x","Debugging information when an IP panics.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CBUS","3","TXVCENCAPFAIL","Detected bad tx vc encap on %s, vc %d. Board encap failed %#x, %#x, %#x","Board encap failed on a transmit packet on a channelized serial interface which does not have the vc number encapsulation","If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative"
"CBUS","3","UNAVAILABLE","%s %d/%d got bad VC packet %08x %08x %08x %08x %08x %08x %08x %08x","An interface received a packet with bad VC encapsulation. This indicates either a software or hardware problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","%s %s command failed (error code 0x%04x)","The cBus ATM microcode rejected a command sent by the Route Processor (RP). The error code is the status value returned by the command.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","%s ustatus: %s (%04x), %04x %04x %04x %04x","Debugging information when an IP panics.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CBUS","3","UNAVAILABLE","%s: tx%c output hung (%-04x - %s), %s","A transmission attempt on an interface failed. The interface might not be attached to a cable or there might be a software problem.","Check that the interfaces are all connected to the proper cables. If that is not the problem, call your technical support representative."
"CBUS","3","UNAVAILABLE","(%s)Illegal E3 value - unit is %d","A status information message was received from the CT3 VIP, but during message processing it was detected that an element in the data structure corresponding to the status information message has not been set. This condition may be caused by either an element that has not been passed by the VIP or a corruption in the status message.","If this error recurs, enter the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information."
"CBUS","3","UNAVAILABLE","(%s)Illegal dsx3 value - unit is %d Error Message    %CBUS-3-UNAVAILABLE: (%s)Illegal sdh value - unit is %d","Internal data structure is corrupted, which causes the love letter to drop.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","Buffer allocation failure: %s","A hardware or software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","CCB handover timed out, CCB 0x%x, slot %d","A hardware or software error occurred.","Please gather the logs and tracebacks and contact the TAC"
"CBUS","3","UNAVAILABLE","CCB semaphore acquired traceback:%s CCB semaphore released traceback:%s","More information on the CCB semaphore. The tracebacks indicate the program counters and stack that point to the code that was the last to acquire this semaphore and the last to release this semaphore respectively","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","Cmd dropped, CCB 0x%x, slot %d, cmd code %d","A software or hardware error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","Cmd failed: %s, response %#04x, %s","A software or hardware error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CBUS","3","UNAVAILABLE","Cmd timed out, CCB 0x%x, slot %d, cmd code %d","A software or hardware error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","Config queue is full, command was dropped, slot %d","Sending a config command was retried. The receiving queues were still full after retries therefore the command was dropped.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CBUS","3","UNAVAILABLE","Controller %d, Error (%-04x), Buffersize = %d, Bufferpool = %d, number %d","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","Controller %d, cmd (%d 0x%-04x, 0x%-04x, 0x%-04x) failed (0x%-04x)","A command sent from the system to an interface processor failed to complete successfully.","The system recovered by generating an error code to the requester."
"CBUS","3","UNAVAILABLE","Controller %d, cmd (%d 0x%-08x) failed (0x%-04x)","A command sent from the system to an interface processor failed to complete successfully.","The system recovered by generating an error code to the requester."
"CBUS","3","UNAVAILABLE","Controller %d, cmd (%d 0x%-08x) failed (0x%-04x) count (%d)","A command sent from the system to an interface processor failed to complete successfully.","The system recovered by generating an error code to the requester."
"CBUS","3","UNAVAILABLE","Controller %d, cmd (%d) failed (0x%-04x)","A command sent from the system to an interface processor failed to complete successfully.","The system recovered by generating an error code to the requester."
"CBUS","3","UNAVAILABLE","Controller %d, cmd (%d) failed (0x%-04x) count (%d)","A command sent from the system to an interface processor failed to complete successfully.","The system recovered by generating an error code to the requester."
"CBUS","3","UNAVAILABLE","Controller %d, wrote 0x%-04x, read 0x%-04x, loc 0x%-04x - dci_memtest()","A hardware component failed an internal diagnostic test.","Replace the malfunctioning device."
"CBUS","3","UNAVAILABLE","Detected bad tx vc encap on %s, vc %d. Board encap failed %#x, %#x, %#x","Board encap failed on a transmit packet on a channelized serial interface which does not have the vc number encapsulation","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","Dump of MEMB follows -SRB_ADDR: %04x %04x %04x %04x %04x %04x %04x %04x","The system is printing codes related to a previous lovenote error message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","Error (%-04x) tx_allocate - cbus_init()","A hardware device did not respond appropriately to a request.","Make sure the device is functioning and is configured correctly."
"CBUS","3","UNAVAILABLE","Failed to select a BCE, response 0x%04x - cbus_bce_permissions_update()","A hardware or software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","Failed to select a BCE, response 0x%04x - cbus_bce_update_ifa()","A hardware or software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","Int %d: %04X %04X %04X %04X %04X %04X","This is the debugging information for the CBUS-3-POLLFAIL error.","LOG_STD_DBG_ACTION"
"CBUS","3","UNAVAILABLE","Interface %d, Error (%-04x), idb %08x %d %s - cbus_init()","The switch processor or ciscoBus controller signaled an error while processing a packet or selecting an interface. This indicates a software problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","Interface %d, idb %08x %d %s - cbus_interrupt()","The switch processor or ciscoBus controller returned a nonsensical value.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","Interface %s failed to initialize","The Token Ring interface failed to insert into the Token Ring. The interface is placed into reset state and will not automatically try to re-insert itself.","Issue a clear interface command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","Interface %s failed to respond, debug info follows","A Token Ring interface card failed to respond to periodic polling. This can indicate a software or hardware problem. See CBUS-3-POLLFAILDAT for the syntax of this message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","Interface %s, Adapter Check Error (%04x %04x %04x %04x)","The Token Ring monitor firmware detected a fatal error on the interface card.","Issue a clear interface command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","Interface %s, CTR Command %s Failed, %s (%#04x)","A command sent from the system to the Token Ring interface failed to complete successfully.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","Interface %s, CTR Command %s Failed, Code %#04x","A command sent from the system to the Token Ring interface failed to complete successfully.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","Interface %s, CTR Initialization Failed - %s","The Token Ring interface failed one of its internal self-tests.","Issue a clear interface command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","Interface %s, Cannot config interface, CBus ATM MEM 0x%x, status %d","A software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CBUS","3","UNAVAILABLE","Interface %s, Error (%-04x) %s - aip_reset()","A software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","Interface %s, Error (%-04x) %s - fddi_reset()","A hardware device did not respond appropriately to a request.","Make sure the device is functioning and is configured correctly."
"CBUS","3","UNAVAILABLE","Interface %s, Error (%-04x) %s - fsip_reset()","A Fast Serial Interface Processor (FSIP) did not respond to a reset request from the Route Processor.","Check FSIP electrical connections, cable, and ciscoBus connections. An FSIP microcode reload will be required. If the check of electrical connections reveals no problems and the message recurs, call your technical support representative for assistance."
"CBUS","3","UNAVAILABLE","Interface %s, Error (%-04x) %s - hssi_reset()","A command to reset an HSSI interface was issued by the RSP, but the interface did not respond to the command within the expected time delay. The delay is given for the processor to return the buffers that it has allocated and to perform any necessary cleanup. This condition may be caused by a large number of buffers that have been allocated by the interface due to either heavy traffic or a hardware problem with the interface.","Verify that the card is properly seated. If this error recurs, then issue the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information."
"CBUS","3","UNAVAILABLE","Interface %s, Error (%-04x) %s - serial_reset()","A software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","Interface %s, Error (%-04x) %s - srp_reset()","A command to reset an SRP interface was issued by the RSP, but the interface did not respond to the command within the expected time delay. The delay is given for the processor to return the buffers that it has allocated and to perform any necessary cleanup. This condition may be caused by a large number of buffers that have been allocated by the interface due to either heavy traffic or a hardware problem with the interface.","Verify that the card is properly seated. If this error recurs, then issue the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information."
"CBUS","3","UNAVAILABLE","Interface %s, Invalid PLIM detected. Interface downed","A software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","Interface %s, Microcode Check Error","The Token Ring interface microcode detected an unrecoverable error.","Issue a clear interface command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","Interface %s, RAM Addressing Test Failed - %s","The Token Ring interface failed its memory diagnostic tests.","Issue a clear interface command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","Interface %s, SRB_COMPLETE lovenote received with unknown command (0x%04x)","The system received a message from the Token Ring interface but does not recognize the message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","Interface %s, address filter %s command failed, code %#04x","The specified address filter command sent to the specified interface failed with the displayed error code.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CBUS","3","UNAVAILABLE","Interface %s, unknown encaps type %x","A packet was received from the CIP with an unknown encapsulation type. The packet will be dropped.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","Missing %s for %s","A hardware or software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","Out of buffers--losing status information for CT3 on VIP card","A status information message from the VIP was received. A memory buffer is required to process the status information message, but the memory allocation routine due to insufficient system buffer memory. Therefore, the status information message was not processed. This condition may be caused either by a heavy memory utilization at the time of the memory buffer request or by insufficient memory in the system.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If this message recurs or appears regularly, contact your Cisco technical representative to upgrade the memory of the system."
"CBUS","3","UNAVAILABLE","Out of buffers--losing status information for ChSTM-1 on VIP card","An internal software resource has been exhausted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","Out of buffers--losing status information for POTENT on VIP card","An internal software resource has been exhausted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","Reset of removed interface %x (%s)","An interface reset was attempted on an interface that was removed from the router. This message appears if you use the shutdown command to bring down a removed interface.","LOG_STD_NO_ACTION"
"CBUS","3","UNAVAILABLE","Select invalid vc number %d.","An invalid channel number is selected","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","Send Ip Cmd Failed. Command dropped after %d retries, CCB 0x%x, slot %d, cmd code %d","Sending an ip command was retried. The receiving queues were still full after retries therefore the command was dropped.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CBUS","3","UNAVAILABLE","Unexpected interface type for %s%u, port %u, type %u","A hardware or software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","Unit %d, Error (%-04x) %s - cbus_atm_reset()","A software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","3","UNAVAILABLE","Unit %d, Error (%-04x) %s - fddi_reset()","A hardware device did not respond appropriately to a request.","Make sure the device is functioning and is configured correctly."
"CBUS","3","UNAVAILABLE","Unit %d, daughter %d, not responding (0x%04x) - disabled","A hardware component failed an internal diagnostic test. Test output and descriptions of ranges are as follows: Unit [dec] (ranges 0-14): Indicates the Multibus jumper setting for the ciscoBus controller. daughter controller [dec] (ranges 0-3): Indicates the ciscoBus relative slot number (0 to 3, or in the Cisco 7000, 0 to 4) of the daughter card that failed the test. The daughter card hardware was recognized across the cBus backplane, but the daughter card did not respond to the first command issued to it. This condition is a result of one of the following: the daughter card did not reset, or the microcode on the card is in a hung state, or the card cannot fully communicate across the ciscoBus backplane (cannot read or write shared MEMD or does not get the MALU_ATTENTION signal across the ciscoBus).","First, make sure that the daughter card is properly seated in its Multibus and ciscoBus connectors. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information"
"CBUS","3","UNAVAILABLE","Unit %d, daughter controller %d failed %s test - interface disabled","A hardware component failed an internal diagnostic test. Test output and descriptions of ranges follow: Unit [dec] (ranges 0-14): Indicates the Multibus jumper setting for the ciscoBus controller, or in the Cisco 7000, a slot number. daughter controller [dec] (ranges 0-3): Indicates the ciscoBus relative slot number (0 to 3, or in the Cisco 7000, 0 to 4) of the daughter card that failed the test. failed [chars] test ([chars]= memd read, memd write):If the failed test was memd read, the processor was able to write to shared ciscoBus buffer memory from the ciscoBus registers, but was unable to read back that memory through special commands to the daughter card. If the failed test was memd write, writes to the memory device through the daughter card were not verified successfully with reads through the ciscoBus controller. The daughter card under test responds successfully to some commands (otherwise the software would have received a DAUGHTER_NO_RSP message), but its memory device tests failed. The daughter card must be able to write to some memory device addresses; otherwise, it cannot respond to any commands.","First check that the daughter controller card is properly seated in its Multibus and ciscoBus connectors. Next, swap daughter cards and check whether the error follows the daughter card or the slot. If the message recurs, call your technical support representative for assistance."
"CBUS","3","UNAVAILABLE","Unit %d, failed %s test - interface disabled","A hardware component failed an internal diagnostic test.","Check switch settings on the interface cards. Check for proper unit numbers. Reset the cards. Replace the malfunctioning device."
"CBUS","3","UNKENC","Interface %s, unknown encaps type %x","A packet was received from the CIP with an unknown encapsulation type. The packet will be dropped.","If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative."
"CBUS","3","UNKNOWN","%s ustatus: %s (%04x), %04x %04x %04x %04x","Debugging information when an IP panics.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CBUS","4","CTRBADLOVE2","Interface %s, Unexpected SRB_COMPLETE lovenote, command=0x%04x, result=0x%04x","The system received an unsolicited message from the Token Ring interface. The system ignored the message and continued normal processing.","If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative."
"CBUS","4","FIXBADTXVC","Detected and fixed bad tx vc encap on %s, bad vc %d, fixed vc %d","A transmit packet on a channelized serial interface does not have the vc number encapsulation","If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative."
"CBUS","4","NOCOOKIE","%s-%d controller missing configuration data - disabled","The controller type was derived from a hardware probe. The controller number indicates the ciscoBus relative slot number. This is a hardware error","If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative."
"CBUS","4","RSETFAIL","Interface %s failed to reset properly in %s, code %#x","An interface reset command failed. This may be a software or hardware problem.","If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative."
"CBUS","4","UNAVAILABLE","%s-%d controller missing configuration data - disabled","The controller type was derived from a hardware probe. The controller number indicates the ciscoBus relative slot number. This is a hardware error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","4","UNAVAILABLE","Detected and fixed bad tx vc encap on %s, bad vc %d, fixed vc %d","A transmit packet on a channelized serial interface does not have the vc number encapsulation","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","4","UNAVAILABLE","Interface %s failed to reset properly in %s, code %#x","An interface reset command failed. This may be a software or hardware problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","4","UNAVAILABLE","Interface %s, Unexpected SRB_COMPLETE lovenote, command=0x%04x, result=0x%04x","The system received an unsolicited message from the Token Ring interface. The system ignored the message and continued normal processing.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CBUS","5","SENDIPCMDRECOV","Send Ip Cmd Succeeded after %d retries, CCB 0x%x, slot %d, cmd code %d","Sending an ip command was retried due to receiving queues being full. But after some retries, command was send successfuly.","Informational only. No action required."
"CBUS","5","UNAVAILABLE","'%s' is not supported on %s","This command is not supported on this FDDI interface.","Informational only. No action required."
"CBUS","5","UNAVAILABLE","Interface %s excessive input error rate","Interface disabled because too many input errors occurred.","Inspect condition of attached network hardware"
"CBUS","5","UNAVAILABLE","Interface %s, setup vc failed with vci exceeding (vc-per-vp - 3) on the last vpi.","The TI1570 chip reserves 3 RX DMA channels for OAM cells. As a result, the last 3 VCIs of the last VPI block cannot be used for regular traffic.","Avoid try different vci/vpi combinations."
"CBUS","5","UNAVAILABLE","Send Ip Cmd Succeeded after %d retries, CCB 0x%x, slot %d, cmd code %d","Sending an ip command was retried due to receiving queues being full. But after some retries, command was send successfuly.","LOG_STD_NO_ACTION"
"CCE_DP","4","CCE_DP_DYNAMIC_CLASS","Sig:[dec] Content type does not match the specified type - [chars] [chars] from %i:[dec] to %i:[dec]","The HTTP message violates the content-type-verification application firewall inspection rule.","This message is informational only, but may indicate a security problem."
"CCE_DP","4","CCE_DP_ICMP","ICMP Classification Result Invalid","The HTTP message violates the request-method application firewall inspection rule.","This message is informational only, but may indicate a security problem."
"CCE_DP","4","CCE_DP_NAMED_DB","Sig:[dec] Content type not found - [chars] [chars] from %i:[dec] to %i:[dec]","The HTTP message violates the content-type-verification application firewall inspection rule.","This message is informational only, but may indicate a security problem."
"CCE_DP","4","CCE_DP_PACKET_PATH","Sig:[dec] Content type: [chars] does not match the Accept-Type from %i:[dec] to %i:[dec]","The HTTP message violates the content-type-verification application firewall inspection rule.","This message is informational only, but may indicate a security problem."
"CCE_DP","4","CCE_DP_POLICY","Sig:[dec] HTTP protocol violation detected - [chars] [chars] from %i:[dec] to %i:[dec]","The HTTP message violates the strict-http application firewall inspection rule.","This message is informational only, but may indicate a security problem."
"CCE_DP","4","CCE_DP_TARGET","content-length","The HTTP message violates the content-length application firewall inspection rule.","This message is informational only, but may indicate a security problem."
"CCE_DP","4","CCE_DP_TIMERS","Sig:[dec] Content size %lu out of range - [chars] [chars] from %i:[dec] to %i:[dec]","The HTTP message violates the content-type-verification application firewall inspection rule.","This message is informational only, but may indicate a security problem."
"CCE_DP","4","CCE_DP_UDP","UDP Classification Result Invalid","The HTTP message violates the request-method application firewall inspection rule.","This message is informational only, but may indicate a security problem."
"CCE_DP","4","CCE_DP_VFR","Fragment classification result invalid","The HTTP message violates the max-uri-len application firewall inspection rule.","This message is informational only, but may indicate a security problem."
"CCE_DP","4","CCE_DP_VTCP","Virtual VTCP Classification result invalid","The HTTP message violates the max-hdr-len application firewall inspection rule.","This message is informational only, but may indicate a security problem."
"CCH323","2","UNAVAILABLE","%s: E164 address length %d is not supported","Received E164 address with the length that is not supported.","Report this immediately to the technical support representative."
"CCH323","2","UNAVAILABLE","Gatekeeper %s requested unregister from Gateway %s","Gatekeeper requested unregister from Gateway","Verify whether this is user intended or otherwise report this to the technical support representative."
"CCH323","2","UNAVAILABLE","Gateway %s failed attempt to register with Alternate Gatekeeper %s","Gateway failed attempt to register with Alternate Gatekeeper","Report this immediately to the technical support representative."
"CCH323","2","UNAVAILABLE","Gateway %s failed to register with Gatekeeper %s even after %d retries","Gateway failed to register with Gatekeeper","Report this immediately to the technical support representative."
"CCH323","2","UNAVAILABLE","Gateway %s unregistered from Gatekeeper %s","Gateway unregistered from the Gatekeeper","Verify whether this is user intended or otherwise report this to the technical support representative."
"CCH323","3","UNAVAILABLE","cch323_store_call_history: %s","Insert an active H323 call record into call history list failed","No action is required"
"CCH323","3","UNAVAILABLE","unknown event %x","Unknwon CCH323 Event","No action is required"
"CCH323","3","UNAVAILABLE","%s%d","A failure was encountered in setting up the monitoring of H323 resources.","Try power cycling the system. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CCH323","3","UNAVAILABLE","%s: OSS init failure: errno = %d","OSS ASN1 initialization failed","This can be catastrophic"
"CCH323","3","UNAVAILABLE","%s: call setup failed","The call setup request failed","Verify that the remote destination identified by the IP address is reachable"
"CCH323","3","UNAVAILABLE","%s: cannot allocate call control block","Allocation of the CCH323 call control block failed. This is possibly due to the fact that system memory pool is exhausted.","This can be a catastrophic error"
"CCH323","3","UNAVAILABLE","%s: cannot allocate call info data structure","Allocation of the CCH323 call info structure failed. This is possibly due to the fact that system memory pool is exhausted.","This call will be terminated due to lack of resource"
"CCH323","3","UNAVAILABLE","%s: cannot allocate gateway structure","Allocation of the CCH323 gateway instance failed. This is possibly due to the fact that system memory pool is exhausted.","This can be a catastrophic error"
"CCH323","3","UNAVAILABLE","%s: cannot allocate message buffer","Allocation of the CCH323 message buffer failed. This is possibly due to the fact that system memory pool is exhausted.","This can be a catastrophic error"
"CCH323","3","UNAVAILABLE","%s: cannot create the H.323 ccb Tree","Creation of the H.323 CCB Tree failed. This is possibly due to the fact that system memory pool is exhausted.","This can be a catastrophic error"
"CCH323","3","UNAVAILABLE","%s: cannot find CCH323 call control block based on callID %d","Cannot find a CCH323 call control block based on the specified callID","No action is required. This is an indication that some events happen out of sequence"
"CCH323","3","UNAVAILABLE","%s: cannot insert control block 0x%x to tree","Insertion of this CCH323 call control block to the RBTree failed. This can be related to a corrupted RBTree","This can be a catastrophic error"
"CCH323","3","UNAVAILABLE","%s: cc_api_call_disconnected returns %d","An error is returned when CCH323 attempts to call cc_api_call_connected","None"
"CCH323","3","UNAVAILABLE","%s: cc_api_call_disconnected returns %d","An error is returned when CCH323 attempts to call cc_api_call_disconnected","None"
"CCH323","3","UNAVAILABLE","%s: create and send event to H.225 state machine failed","create and send event to H.225 state machine failed. This is possibly due to the missing call control block","This can be a catastrophic error"
"CCH323","3","UNAVAILABLE","%s: illegal destination %s","The IP address passed from CCAPI in the call setup request is invalid","Check the dial-peer configuration for the dial-peer that matches the called party number. Make sure that the session target field contains valid IP address. or DNS name"
"CCH323","6","UNAVAILABLE","Gateway %s registered with Gatekeeper %s","Gateway registered with the Gatekeeper","no action is required"
"CCM","5","FMD_FLOWS_EXCEEDED","CCM Cache Resource Exceeded. Number of metadata flows exceeded the limit for the platform.","Currently Cat6k support only 10000 metadata flows on the switch for QoS service policies. Subsequent flows added will not be used for QoS classification.","Informational only. No action required."
"CDP","3","UNAVAILABLE","Chunk_malloc Failure","chunk malloc failure","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CDP","4","UNAVAILABLE","Native VLAN mismatch discovered on %s (%d), with %s %s (%d).","CDP discovered a mismatch of native-VLAN configuration","Configure the interfaces to the same native VLAN."
"CDP","4","UNAVAILABLE","duplex mismatch discovered on %s (%s), with %s %s (%s).","CDP discovered a mismatch of duplex configuration","Configure the interfaces to the same duplex (full or half)."
"CE3","1","UNAVAILABLE","%s could not be disabled by %s","The shutdown failed to disable the interface.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CE3","1","UNAVAILABLE","%s could not be enabled by %s","The restart failed to enable the interface.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CE3","1","UNAVAILABLE","%s could not be reset by %s","The restart failed to reset the interface.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CE3","1","UNAVAILABLE","%s init failed at %s","CE3 initialization failure.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CE3","1","UNAVAILABLE","Failed to configure %d interfaces in bay %d, shutting down bay","The CE3 hardware failed. Some components on the board failed to initialize.","Replace the CE3 port adapter."
"CE3","1","UNAVAILABLE","Found %d interfaces in bay %d, shutting down bay","The CE3 hardware failed. Some components on the board failed to initialize.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CE3","1","UNAVAILABLE","Microcode to slot %d","Failed to download firmware into the CE3 port adapter.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CE3","1","UNAVAILABLE","Slot %d firmware init (%s)","CE3 firmware initialization failure.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CE3","1","UNAVAILABLE","Slot %d for microcode download","An error was detected on the communication path between VIP and CE3.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CE3","2","UNAVAILABLE","%08x %08x %08x %08x","CE3 firmware does not update the software watchdog.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CE3","2","UNAVAILABLE","%s: packet received for unknown VC %d","The virtual channel encapsulation is corrupted.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CE3","2","UNAVAILABLE","CE3 F/W crashed: %x - VIP reset","CE3 firmware does not update the software watchdog.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CE3","3","UNAVAILABLE","%s - Accumulator is not available","An invalid TX accumulator is detected.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CE3","3","UNAVAILABLE","%s","General error information.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CE3","3","UNAVAILABLE","%s: failed to send %s love letter","A love letter was not sent to RSP.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CE3","3","UNAVAILABLE","Failed to receive reply %d from bay %d firmware","A message was not received from CE3 firmware.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CE3","3","UNAVAILABLE","Failed to receive reply %d to %s driver firmware","A port related message was not received from CE3 firmware.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CE3","3","UNAVAILABLE","Failed to send msg %d to %s driver firmware","A port related message was not sent to CE3 firmware.","Copy the error message exactly as it appears, collect the output of 'show tech-support' command immediately, and report it to your technical support representative. If possible, try to do an OIR (Online Insertion and Removal). Please refer to the Cisco documentation for information on 'Online Insertion and Removal' for your platform"
"CE3","3","UNAVAILABLE","Failed to send msg %d to bay %d firmware","A message was not sent to CE3 firmware.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CE3","3","UNAVAILABLE","Received unexpected mailbox message (id = %d)","Unexpected message from CE3 firmware.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CE3","3","UNAVAILABLE","Slot %d device ID seen as %#x, expected %#x (FREEDM)","Failed to detect the hdlc controller on the CE3.","Replace the CE3 port adaptor."
"CE3","3","UNAVAILABLE","Slot %d device ID seen as %#x, expected %#x (PLX9060)","The PLX 9060 was not detected on the CE3.","Replace the CE3 port adaptor."
"CERF","2","UNAVAILABLE","%s","This message is emitted when a cache error has occured, but an attempt to recover has been aborted","Copy the error message exactly as it appears, and report it to your technical support representative."
"CES","2","UNAVAILABLE","%s","The CES subsystem encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CES","3","UNAVAILABLE","%s","The CES subsystem encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CES","4","UNAVAILABLE","%s","The CES subsystem encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CERF","3","UNAVAILABLE","%s","This message is emitted when there has been a full recovery after a cache error","Copy the error message exactly as it appears, and report it to your technical support representative."
"CFC_LISP","3","ADJ","Request to %s adjacency %s%s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","ADJ_SEQ","Adjacency %s is still complete after interface shutdown","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","ALLOCATEFAIL","Failed to allocate memory for %s","An internal software error occurred. This is probably because not enough memory was available.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","BG_PROCESS","Background process failed to %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","DEPRECATED_API","Use of a deprecated API %s%s Recommended Action    Increase the MTU of the path to the remote RLOCError Message    %CFC_LISP-3-DEP_ELEM: Request to %s dependency %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","ELIG_OCE","Failed to %s LISP eligibility oce %s%s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","FREE_WITH_DEPS","Request to remove dependency sb on %s with dependents","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","INVALID_INPUT","Invalid input %s to %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","IPL_SRC","Failed to %s IPL source %s %s/%u%s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","ISSU_NEGO_ERR","Failed to negotiate %s for XDR client %s, error %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","ISSU_REG_ERR","Failed to register %s for ISSU client %s (%u) entity %u, error %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","ISSU_XFORM_ERR","Failed to ISSU transform XDR message %s, error %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","LOCAL_EID","Failed to %s local EID prefix %s/%u","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","NO_ADJ","Failed to find adjacency for %s %s %s %u","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","NO_FIBIDB","Failed to find fibidb for %s %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","NO_SB","Failed to find subblock for %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","NO_TABLE","Failed to find table for %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","NO_VIF","Unable to find %svirtual interface %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","PUSH_CNTR","Failed to %s push counter for %s%s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","REMOTE_EID","Failed to %s remote EID prefix %s/%u%s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","REMOTE_EID_PREFIX","Failed to %s remote EID prefix %s%s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","RLOC_VRF_IN_USE","RLOC vrfid %u already in use by top-id %u, cannot assign to top-id %u","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","SBINIT","Error initializing %s subblock data structure. %s","Initialization of the specified subblock data structure couldnot be accomplished.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","SB_OPERATION_FAILED","Failed to %s subblock on %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","TABLE_BIND","Error setting %s table %s for top-id %u, iid %u, %s%s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","TABLE_STATE","Error setting state for table %s to top-id %u, iid %u, role %s, %s%s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","TERM_ADJ","Terminal adjacency %s%s%s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","TIMESTAMP_CTRL_PKT","Failed to timestamp LISP control packet","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","TREE_OP_FAIL","Tree %s failed for %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","UNABLE_TO_IDENTIFY_TABLE","Unable to identify table for packet from %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","UNKNOWN_PAYLOAD","Dropping LISP encapsulated packet, unknown payload 0x%08x","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","UNKN_INSTANCE","Unknown instance, unable to find/create virtual interface","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","VIF","Unable to %s virtual interface %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","WALK_DEP","Walking dependents %s%s%s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","XDR_LEN_ERR","Failed to %s XDR message %s len %u  max %u","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","3","XDR_REG_ERR","Failed to register XDR client %s (%u), error %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","5","ADJ_STACK","Stacking adjacency %s %s%s%s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFC_LISP","5","BELOW_MIN_MTU","Cannot set %s MTU for RLOC %s to %u, %s MTU for %s %s is %u, below minimum MTU %u+%u required for LISP encap","Unable to set the EID payload MTU for a remote RLOC below the minimal MTU, this will cause the encapsulated packet to be bigger than the MTU of the path to the remote RLOC, and may cause packet loss.","Increase the MTU of the path to the remote RLOC"
"CFC_LISP","5","IGNOREICMPMTU","Ignoring received ICMP Type 3 Code 4, %s-%s next hop mtu %u, due to pmtu min or max setting","An ICMP Type 3 Code 4 (fragmentation needed and DF set) packet has been received. This packet has specified a Next-Hop MTU that is smaller or greater than the current minimum or maximum path MTU discovery mtu value. The ICMP packet has been ignored and the MTU has not been changed.","If you want the ICMP packet to be accepted and used, use the ip lisp pmtu min NUMBER max NUMBER command to decrease the minimum MTU allowed and/or increase the maximum MTU that is allowed."
"CFC_LISP","5","IGNOREICMPV6MTU","Ignoring received ICMPv6 Type 2, %s-%s next hop mtu %u, due to pmtu min or max setting","An ICMPv6 Type 2 (Packet Too Big) packet has been received. This packet has specified a Next-Hop MTU that is smaller or greater than the current minimum or maximum path MTU discovery mtu value. The ICMP packet has been ignored and the MTU has not been changed.","If you want the ICMP packet to be accepted and used, use the ipv6 lisp pmtu min NUMBER max NUMBER command to decrease the minimum MTU allowed and/or increase the maximum MTU that is allowed."
"CFC_STATS","3","BADSTATSCLIENTSEND","%s: %s 0x%08X/%u expected 0x%08X/%u","Internal error. May result in unpredictable behaviour.","Copy the message exactly as it appears, and report it to your technical support representative."
"CFC_STATS","3","BADSTATSPULL","%s: %s","Internal error. May result in unpredictable behaviour.","Copy the message exactly as it appears, and report it to your technical support representative."
"CFC_STATS","3","STATSNOMEM","CFC Stats failed to allocate memory during %s creation.","Allocation of memory by the XDR subsystem failed. This may result in an unpredictable behavior of XDR","Make sure that there is enough memory for the operations being performed by your machine. Copy the message exactly as it appears, and report it to your technical support representative."
"CFC_STATS","3","TESTSTATSCLIENT_DECODE","XDR test stats %s saw error (%s).","The XDR statistics test client has an internal error. This only affects internal test infrastructure and so should not have any effect on normal system operation","Copy the message exactly as it appears, and report it to your technical support representative."
"CFC_STATS","3","TESTSTATSCLIENT_UNEXPECTED_EVENT","Selftest failure: unexpected event (%x, %x) during wait for update","The XDR statistics infrastructure has experienced a self test failure. This should only occur when a self test is running and a failure is detected. It does not directly imply a problem with normal operation.","Copy the message exactly as it appears, and report it to your technical support representative."
"CFC_STATS","4","BADSTATSCLIENTRECEIVE","context %u, length %u from %s","The XDR statistics infrastructure received a message it could not decode from a peer. This has no harmful effects but might be a evidence of a more serious problem.","Copy the message exactly as it appears, and report it to your technical support representative."
"CFC_STATS","4","STATSCLIENTADDMCASTGRPFAIL","Stats client %s failed to add linecards %s","The XDR statistics infrastructure has seen an internal error. This may prevent counters to fail to be reported to the RP.","Copy the message exactly as it appears, and report it to your technical support representative."
"CFC_STATS","4","STATSCLIENT_REGISTRATION","Unable to register XDR client %s client due to %s","The XDR statistics infrastructure has seen an internal error. This may prevent counters to fail to be reported to the RP.","Copy the message exactly as it appears, and report it to your technical support representative."
"CFC_STATS","4","STATSUNEXPECTEDEVENT","%s","The XDR statistics infrastructure has seen an internal error. This may prevent counters to fail to be reported to the RP.","Copy the message exactly as it appears, and report it to your technical support representative."
"CFC_STATS","4","STATSUNEXPECTEDNEWMCASTGRP","Add req for %s but already sending stats to %s","The XDR statistics infrastructure has seen an internal error. This may prevent counters to fail to be reported to the RP.","Copy the message exactly as it appears, and report it to your technical support representative."
"CFGMGR","1","UNABLE_TO_SEND_RUN_CFG","unable to send running-cfg, bits: [hex], retrying...","The system is attempting to push the running configuration to the slaves.","No action is required."
"CFGMGR","1","UNABLE_TO_SEND_STARTUP_CFG","unable to send startup-cfg, bits: [hex], retrying...","The system is attempting to push the startup configuration to the slaves.","No action is required."
"CFGMGR","3","ERROR_APPLYING_STARTUP_CFG","Error Applying Startup Config to Running Config","The system encountered an error while automatically applying the startup configuration to the running configuration.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFGMGR","4","SLAVE_WRITING_STARTUP_CFG","only master can do that","An attempt to write to the startup configuration was made on a slave, but is allowed only on the master.","No action is required."
"CFGMGR","6","APPLYING_RUNNING_CFG","as new master","The new master is applying a backed-up running configuration.","No action is required."
"CFGMGR","6","SPURIOUS_SLAVE_ADD","CFG MGR Recvd Spurious New Slave Notification: [int]","Configuration Manager was notified about a slave that it already knows about.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFGMGR","6","UNABLE_TO_NVGEN_BUSY_RUNNING_CFG","config file busy, retrying...","The master is temporarily unable to complete the nonvolatile generation process (NVGEN) to construct the running configuration.","No action is required."
"CFGMGR","6","UNABLE_TO_NVGEN_RUNNING_CFG","config file too large...","The master is unable to complete the nonvolatile generation process (NVGEN) to construct the running configuration because the configuration file is too large.","Remove some configuration commands."
"CGC","0","UNAVAILABLE","%s","CGC_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CGC","1","UNAVAILABLE","%s","CGC_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CGC","2","UNAVAILABLE","%s","CGC_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CGC","3","UNAVAILABLE","%s","CGC_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CGC","4","UNAVAILABLE","%s","CGC_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CGC","5","UNAVAILABLE","%s","Normal but significant conditions","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CGC","7","UNAVAILABLE","Assertion Failure ( %s @%s:%d ) : %s","CGC_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CHAT","3","UNAVAILABLE","%t in use, can't run startup script","When the startup script attempted to run, it found another process had Already been started on the line","Remove startup script from line configuration if it's inappropriate. Report to cisco."
"CFIB","3","CFIB_UNEXPECTED_OCE_CHAIN","Unexpected oce length obj:Unrecognized format ` %p' type: [dec]","The Output Chain Element(OCE) specified in the system message is invalid because it has exceeded the maximum depth. One known cause is invalid static route configuration. Traffic for this path will be dropped.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"CFIB","3","REQ_VPN_MAPPER_IPV4_FAIL","CFIB vpn mapper request fails for ipv4 appid [chars]","All vpn ids for ipv4 app are used","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"CFIB","3","REQ_VPN_MAPPER_IPV6_FAIL","CFIB vpn mapper request fails for ipv6 appid in [chars]","All vpn ids for ipv6 app are used.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"CFIB","7","CFIB_ADJBASE","Failed to free adjacency base from hash table (entry not found)","An error has occurred while attmepting to free an adjacency from a hash table. This condition might be caused by an inconsistent use of hash key during creation of the adjacency hash table. This condition might cause a memory leak","Copy the message exactly as it appears on the console or in the system log. To check memory usage over time, enter the show process memory command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFIB","7","CFIB_EXCEPTION","FIB TCAM exception, Some entries will be software switched","Because there are no free memory blocks in the FIB TCAM, some switching will be done in software rather than hardware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFIB","7","END_CFIB_EXCEPTION","FIB TCAM exception cleared, all CEF entries will be hardware switched","Because free memory blocks have become available in the FIB TCAM, switching will be done in hardware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CFIB_TUNNEL_RP","4","TUN_RECIR_FORCED","The current configuration of hardware and software requires MPLS tunnel recirculation to be enabled. 'mls mpls tunnel-recir' has been added to the running configuration","When the chassis contains a SIP-600 line card, and VRF forwarding is configured on a tunnel interface, MPLS tunnel recirculation must be enabled to prevent the creation of corrupted packets from EARL. The mls mpls tunnel-recir command has been added to the running configuration automatically.","No action is required."
"CFM_CONST","3","AEB_ON_EC_UNSUPPORTED","CFM AEB mode is unsupported on etherchannels. Cannot set CFM AEB mode","CFM AEB mode is unsupported on etherchannels.","Set CFM AEB mode only on physical (unbundled) ports."
"CFM_CONST","3","CFM_ON_SUPERVISOR_PORTS_DISABLED","CFM is enabled system wide except it's disabled on supervisor ports due to spanning tree configuration.","Unable to program all port ASIC MAC match registers on supervisor ports for CFM due to hardware limitations on these ports. Continued with enabling CFM system-wide to allow coexistence with other protocols such such as PVST.","System has handled this by disabling CFM on all supervisor ports. If this is unacceptable configure STP mode to MST and re-enable CFM or disable CFM completely."
"CFM_CONST","3","CFM_ON_SUPERVISOR_PORTS_DISALLOWED","CFM is enabled system wide except on supervisor ports due to spanning tree configuration.","Unable to program all port ASIC MAC match registers on supervisor ports for CFM due to hardware limitations on these ports. Continued with enabling CFM system-wide to allow coexistence with other protocols such such as PVST.","Administrator action may be required. Ensure no CFM traffic is presented to any supervisor ports via configuration. If not possible configure STP mode to MST and re-enable CFM or disable CFM completely"
"CFM_CONST","3","MAC_OPERATIONALLY_ERROR","The set MAC operationally action on interface [chars] has encountered an error.","The set MAC operationally action failed and ended abnormally.","No action is required."
"CFM_CONST","3","MATCH_REG_GLOBAL_RESERVE_FAILED","Unable to program port ASIC MAC match register on one or more slots. Cannot run CFM","The Content Flow Monitor (CFM) attempted to reserve and program the port ASIC MAC match registers, but there are insufficient match registers available. CFM cannot be run.","To free MAC match registers, disable protocols that use the MAC match register. Protocols using port ASIC match registers can be viewed with the remote command switch show platform mrm info command."
"CFM_CONST","3","MATCH_REG_RESERVE_FAILED","Unable to reserve port ASIC MAC match register on slot [dec]. Cannot run CFM","CFM attempted to reserve a port ASIC MAC match register for the slot indicated and there is no register available. CFM cannot be run without support from all line cards.","To free MAC match registers, disable protocols that use the MAC match register. Protocols using port ASIC match registers can be viewed with the remote command switch show platform mrm info command."
"CFM_CONST","3","MATCH_REG_RESERVE_ON_SUPERVISOR_FAILED","Unable to program port ASIC MAC match register on supervisor slot [dec]. Cannot run CFM on supervisor ports","CFM attempted to reserve a port ASIC MAC match register for the indicated supervisors' slot and there is no register available. CFM cannot run on supervisors ports.","Protocols that use the MAC match register must be disabled to free MAC match registers. Protocols using port ASIC match registers can be can be viewed with remote command switch show platform mrm info."
"CFM_CONST","3","MST_SIMULATE_PVST_PLAT_ENABLED_FAILED","Unable to enable CFM when spanning tree mode is MST and PVST simulation is enabled on the platform","CFM does not work along with MST plus PVST simulation.","Disable PVST simualation on the platform."
"CFM_CONST","3","STP_MODE_CHANGE_NOT_ALLOWED","Unable to change STP mode while CFM is enabled","STP modes PVST and rapid PVST are not compatible with CFM due to hardware limitations.","Either configure STP mode MST or disable CFM."
"CFM_CONST","6","CFM_ON_SUPERVISOR_PORTS_ENABLED","CFM is enabled on supervisor ports also due to spanning tree mode change to mst configuration.","Able to program all port ASIC MAC match registers on supervisor ports for CFM due to spanning tree mode change to mst configuration.","No action is required."
"CFM_CONST","6","MAC_OPERATIONALLY","Interface [chars] is MAC operationally [chars].","The specified interface is MAC operationally up or down.","No action is required."
"CH","1","RM_STATE","_state_ attribute still available","The _state_ attribute was still available in CH db re_auth recand it should have been removed by now as part of the re_auth process.","No action required."
"CHARLOTTE","1","INITFAIL","Failed to initialize port [dec].","The dual OC-3 PoS port adapter failed to complete IDB initialization.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CHARLOTTE","1","PCIINITFAIL","PCI initialization failed.","The dual OC-3 PoS port adapter failed to complete hardware initialization.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CHARLOTTE","3","INVALIDPCI","Device reported [hex]","The dual OC-3 PoS port adapter hardware failed. The PCI device has an invalid ID.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CHARLOTTE","3","UNSUPPORTED","[chars]","The dual OC-3 PoS port adapter hardware is not supported on the specified platform.","Upgrade your system so that it supports the dual OC-3 PoS port adapter."
"CHKPT","3","INVALID_CALLBACK_ARG","Attempt to add a checkpointing client with an invalid [chars] argument","An invalid argument was supplied to an internal application program interface (API). As a result, the system state between one or more checkpointing clients might not be properly synchronized. The message output identifies the type of error that occurred. This failure is probably caused by a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CHKPT","3","ISSU_MSG_NOT_COMPATIBLE","Checkpointing message type not compatible","An error was detected when verifying the checkpointing message type compatibility between checkpointing client peers. As a result, the system state between one or more checkpointing clients might not be properly synchronized. This failure is probably caused by a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show checkpoint client commands and your pertinent troubleshooting logs."
"CHKPT","3","ISSU_NEGO_FAILED","Checkpointing Facility failed to start ISSU negotiation with the peer ([chars])","The checkpointing facility was unable to start the ISSU negotiation successfully. The failure to start negotiation is a fatal error condition and is probably caused by a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CHKPT","3","ISSU_RCV_TRANSFORM_FAILED","Checkpointing receive message header transformaton failed ([chars])","An error was detected while performing a receive-level transformation on a checkpointing message. As a result, the system state between one or more checkpointing clients might not be properly synchronized. The message output identifies the type of error that occurred. This failure is probably caused by a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show checkpoint client commands and your pertinent troubleshooting logs."
"CHKPT","3","ISSU_XMIT_TRANSFORM_FAILED","Checkpointing transmit message header transformaton failed ([chars])","An error was detected while performing a transmit-level transformation on a checkpointing message. As a result, the system state between one or more checkpointing clients might not be properly synchronized. The message output identifies the type of error that occurred. This failure is probably caused by a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show checkpoint client commands and your pertinent troubleshooting logs."
"CHKPT","3","RMI_CALLBACK","Checkpointing Facility encountered an error while processing a callback from the Resource Manager (RMI), [chars]","The checkpointing facility registers with the Resource Manager (RMI) to receive status notifications about resources (such as IPC) and uses them to throttle the sending of messages to the peer. The checkpointing facility encountered an error while processing a callback from RMI. This error is probably caused by a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CHKPT","3","RMI_FAILED","Checkpointing Facility failed to register with the Resource Manager (RMI), [chars]","The checkpointing facility registers with the Resource Manager (RMI) to get status notifications about resources (such as IPC) and uses them to throttle the sending of messages to the peer. The checkpointing facility was unable to register itself with RMI and cannot throttle the sending of any messages. The system may still operate normally. This error is probably caused by a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CHKPT","3","SYSMGR_LOOKUP","Failed to get process Job ID from SysMgr","The checkpointing facility was unable to get a job ID for an ION (run-time Modular IOS) process from the System Manager. The job ID lookup is done when any ION checkpointing facility client first registers itself with the checkpoint facility. The error does not affect the checkpointing capabilities of the system. The job ID is used by the reset manager for tracking process restarts.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CHKPT","3","TRANSFORMFAILED","Checkpointing msg header transform failed ([dec])","A transform error related to check pointing occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show checkpoint client commands and your pertinent troubleshooting logs."
"CHKPT","3","TRANSMIT_FAILED","Checkpointing message transmission failure ([chars])","An error was detected when transmitting a checkpointing message between checkpointing client peers. As a result, the system state between one or more checkpointing clients might not be properly synchronized. The failure is probably caused by a software error. The message output identifies the type of error that occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show checkpoint client commands and your pertinent troubleshooting logs."
"CHKPT","4","GET_BUFFER","Checkpointing ISSU session ([dec]) failed to get buffer","The checkpointing ISSU session failed to get a buffer.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show checkpoint client commands and your pertinent troubleshooting logs."
"CHKPT","4","INIT","Checkpoint [chars] initialization failed in RF state ([chars])","The checkpointing standby initialization failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CHKPT","4","INVALID_STATE","Checkpoint State ([dec]) is invalid","The checkpointing state is invalid.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CHKPT","4","MSG_SEND","Checkpointing ISSU session ([dec]) failed to send message","The checkpointing ISSU session failed to send a negotiate message to the peer.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show checkpoint client commands and your pertinent troubleshooting logs."
"CHKPT","4","NOCLIENT","CF client is NULL, ([chars])","The checkpointing facility cannot send the message because the client is NULL.","This is a warning message; no action is required."
"CHKPT","4","NOIPCPORT","IPC port is NULL, ([chars])","The checkpointing facility cannot send the message because the IPC port information is NULL.","This is a warning message; no action is required."
"CHKPT","4","NOMESSAGE","Message is NULL, ([chars])","The checkpointing facility cannot send the message because the message is NULL.","This is a warning message; no action is required."
"CHOPIN","1","CONFIGURE","Fail to configure %d interfaces on bay %d, shutting down bay","Cannot configure some interfaces on board","Copy the error message exactly as it appears, and report it to your technical support representative."
"CHOPIN","1","DISCOVER","only found %d interfaces on bay %d, shutting down bay","Mismatched type or CHOPIN hardware failure","Copy the error message exactly as it appears, and report it to your technical support representative."
"CHOPIN","1","DWNLDCKSM","Failed for bay %d, sent = 0x%x, received = 0x%x","The download of the internal firmware to the CHOPIN failed to checksum correctly. This usually indicates a hardware failure","Perform a power cycle. If the problem persists, the CHOPIN hardware may have a problem."
"CHOPIN","1","DWNLDFAIL","Download failed","Microcode download to CHOPIN port adapter failed.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CHOPIN","1","INITFAIL","Slot %d: %s","The PRI port adaptor failed to complete hardware initialization.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CHOPIN","1","NOTCMPLT","Microcode download failed to complete","The CHOPIN hardware has failed. It could not download its operational microcode.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CHOPIN","1","NOTREADY","Not ready for download.","Error on the communication path between DRIVER and CHOPIN","Copy the error message exactly as it appears, and report it to your technical support representative."
"CHOPIN","1","STARTFAIL","%s channel not enabled;called from function %s","A software or hardware error occurred. The CHOPIN serial interface is not responding to commands used to initialize it.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CHOPIN","1","STOPFAIL","%s channel not disabled","The PRI port adaptor failed to respond to a request to disable an interface.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CHOPIN","1","UNAVAILABLE","%s channel not enabled;called from function %s","A software or hardware error occurred. The CHOPIN serial interface is not responding to commands used to initialize it.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CHOPIN","1","UNAVAILABLE","Download failed","Microcode download to CHOPIN port adapter failed.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CHOPIN","1","UNAVAILABLE","Fail to configure %d interfaces on bay %d, shutting down bay","Cannot configure some interfaces on board","Copy the error message exactly as it appears, and report it to your technical support representative."
"CHOPIN","1","UNAVAILABLE","Failed for bay %d, sent = 0x%x, received = 0x%x","The download of the internal firmware to the CHOPIN failed to checksum correctly. This usually indicates a hardware failure","Perform a power cycle. If the problem persists, the CHOPIN hardware may have a problem."
"CHOPIN","1","UNAVAILABLE","Microcode download failed to complete","The CHOPIN hardware has failed. It could not download its operational microcode.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CHOPIN","1","UNAVAILABLE","Not ready for download.","Error on the communication path between DRIVER and CHOPIN","Copy the error message exactly as it appears, and report it to your technical support representative."
"CHOPIN","1","UNAVAILABLE","Slot %d: %s","The PRI port adaptor failed to complete hardware initialization.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CHOPIN","1","UNAVAILABLE","System detected OVERTEMPERATURE condition. Putting the system in Power save mode and going to rommon. Please resolve cooling problem and restart system!","The environmental monitor detected a high-temperature condition.","Make sure that the room temperature is not too high and that air flow to the card is not blocked. If this condition persists, the environmental monitor might shut down the system. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CHOPIN","1","UNAVAILABLE","only found %d interfaces on bay %d, shutting down bay","Mismatched type or CHOPIN hardware failure","Copy the error message exactly as it appears, and report it to your technical support representative."
"CHOPIN","2","CHOPINFWCRASHEDINFO","%#08x %08x %08x %08x","CHOPIN firmware crash info","Copy the error message exactly as it appears, and report it to your technical support representative."
"CHOPIN","2","POTBADCMD","bad CHOPIN command %d","CHOPIN got an unsupported command","Copy the error message exactly as it appears, and report it to your technical support representative."
"CHOPIN","2","TXBADVC","[chars], vc [dec]","The VIP multichannel port adapter had a bad transmit VC.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech and show controllers vip slot tech-support commands and your pertinent troubleshooting logs."
"CHOPIN","3","BADMSG","Received unexpected mailbox message (id = %d)","CHOPIN mailbox received an unexpected message","Copy the error message exactly as it appears, and report it to your technical support representative."
"CHOPIN","3","CMDFAIL","%s Command Failed at %s - line %d, arg %d","CHOPIN command error","Copy the error message exactly as it appears, and report it to your technical support representative."
"CHOPIN","3","ERROR","%s","CHOPIN general error","Copy the error message exactly as it appears, and report it to your technical support representative."
"CHOPIN","3","FWFATAL","Bay %d: firmware needs reset due to %s","CHOPIN experienced firmware problems","Copy the error message exactly as it appears, and report it to your technical support representative."
"CHOPIN","3","LOVEFAIL","%s: failed to send %s love letter","CHOPIN failed send for a love letter","Copy the error message exactly as it appears, and report it to your technical support representative."
"CHOPIN","3","MBOXRECV","Bay %d: fail receiving mbox reply %d","CHOPIN mailbox failed receive","Copy the error message exactly as it appears, and report it to your technical support representative."
"CHOPIN","3","MBOXSEND","Bay %d: fail sending mbox msg %d","CHOPIN mailbox failed send","Copy the error message exactly as it appears, and report it to your technical support representative."
"CHOPIN","3","MBOXSENDP","Bay %d: fail sending mbox msg %d for port %d","CHOPIN mailbox failed send for a given port","Copy the error message exactly as it appears, and report it to your technical support representative."
"CHOPIN","3","MBXREAD","%s has stale msg - mbx0:%lx, mbx1:%lx, mbx2:%lx","The CHOPIN has not responded to a message within a specified time.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CHOPIN","3","NOTCHOPIN","Device is not FREEDM - Device reported %#x","The CHOPIN hardware failed. A non-CHOPIN device pointed at the software for the CHOPIN serial.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CHOPIN","3","NOTPLX","Device is not PLX 9060 - Device reported %#x","Wrong device reported on CHOPIN","Copy the error message exactly as it appears, and report it to your technical support representative."
"CHOPIN","3","OWNERR","serial (%d), Buffer ownership error, pak=0x%x","Internal buffer ownership error on CHOPIN","Copy the error message exactly as it appears, and report it to your technical support representative."
"CHOPIN","3","PANIC","Exception %d, trace %d","The CHOPIN firmware detected an illegal or unexpected CPU exception or condition. This may be caused by a software error or by a hardware failure.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CHOPIN","3","TOOSMALL","%s - packet was less than two bytes","A packet that is too small ( (%i:%d) not found.Explanation    The CBAC code was searching its database for information for a particular inspection session, but this information was not found.","If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance."
"CHOPIN","3","UNAVAILABLE","%s - packet was less than two bytes","A packet that is too small (lsp %#xExplanation    An internal error occurred in the Intermediate System-to-Intermediate System (ISIS) or NetWare Link Services Protocol (NLSP).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CI","0","SHUT_LC_CRITICALTEMP","Line cards shutdown as critical temperature exceeded [chars]","The chassis temperature has exceeded a critical threshold and line cards have been shut down.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CI","0","SHUT_LC_FANFAIL","Line cards are being shut on fan failure","The chassis fan tray failure timer has expired and line cards have been shut down.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CI","0","SHUT_LC_FANGONE","Line cards are being shut as fan tray is missing","The chassis fan missing timer has expired and line cards have been shut down.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CI","1","CHASSISFAULTYSENSOR","Alarm: Chassis temperature sensor is faulty","This error indicates that the chassis temperature sensor is faulty.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CI","1","CHASSISTEMPCRITICAL","Chassi temperature CRITICAL limit exceeded","The system chassis temperature critical limit has been exceeded.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CI","1","CRITICALTEMP_LC_SHUT","Alarm: [chars], [chars], [chars], [chars], [chars]","This error indicates that line cards have been shut down due to the core temperature exceeding the critical threshold.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CI","1","FAN_FAILURE_LC_SHUT","Alarm: [chars], [chars], [chars], [chars], [chars]","This error indicates that line cards have been shut down due to total fan failure or a missing fan tray.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CI","3","CHASSISTEMPLOW","Chassis temperature too low","The system chassis temperature is below -15 degrees Celsius.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CI","3","CHASSISTEMPMAJOR","Chassis temperature major limit exceeded","The system chassis temperature major limit has been exceeded.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CI","3","CHASSISTEMPMINOR","Chassis temperature minor limit exceeded","The system chassis temperature minor limit has been exceeded.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CI","3","MIB_ALM_SUBMIT","MIB alarm: [chars], [chars], [chars], [chars], [chars]","An alarm message is contained in the MIB.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CI","3","PS_FAIL","Power supply module [dec] failure","The specified power supply module has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CI","4","MULTIPLE_FAN_FAILURE","[chars] [dec] [chars][chars]","When two or more of the fans in the chassis fan tray have failed or the fan try is missing, the line cards will be powered down after the user-configured timer interval. This warning message is generated one minute after the fans have failed or the fan tray is detected to be missing.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CI","6","CHASSIS_SHUTDOWN","Chassis shutdown. Card/subcard not powered up","The chassis is shut down. Line cards will not be powered up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CI","6","FANOK","Fan tray module OK","The chassis fan tray is operating normally.","No action is required."
"CI","6","LINECARD_SHUTDOWN","[chars]","When two or more of the fans in the chassis fan tray have failed or the fan tray is missing, the line cards will be powered down after a user configured timer interval. This message is generated before shutting down line cards.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CI","6","PS_MISSING","Power supply module [dec] missing","The specified power supply module is not present in the system","No action is required."
"CI","6","PSNORMAL","Power supply [int] normal","A failed power supply is working normally now.","If the situation does not correspond with a normal operation of the system's power supplies, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CI","6","PS_OK","Power supply module [dec] OK","The specified power supply module is operating normally.","No action is required."
"CI","6","PS_PRESENT","Power supply module [dec] present","The specified power supply module is present in the system .","No action is required."
"CLNS","3","UNAVAILABLE","%s: L%d LSP %s database checksum error, restarting","A hardware or software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CLNS","3","UNAVAILABLE","%s: L%d LSP %s size %d bigger than interface %s MTU %d, LSP dropped","A software or hardware error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CLNS","3","UNAVAILABLE","%s: L%d LSP filled to capacity %s","A hardware or software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CLNS","3","UNAVAILABLE","%s: LSPix %s %d head %#x doesn't match first prev %#x","An internal error occurred in the Intermediate System-to-Intermediate System (ISIS) or NetWare Link Services Protocol (NLSP).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CLNS","3","UNAVAILABLE","%s: LSPix entry %d mismatch with LSP %#x, LSP %s is %d, entry %d","An internal error occurred in the Intermediate System-to-Intermediate System (ISIS) or NetWare Link Services Protocol (NLSP).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CLNS","3","UNAVAILABLE","%s: LSPix entry %d should be null, is %#x","An internal error occurred in the Intermediate System-to-Intermediate System (ISIS) or NetWare Link Services Protocol (NLSP).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CLNS","3","UNAVAILABLE","%s: Schedule L%d LSP to set overload bit","The LSP was filled to capacity and after applying any lsp-full suppress options, we still can't recover out of it. So we are going to set overload bit on the LSP","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CLNS","3","UNAVAILABLE","%s: non-null %s pointer %#x on freed LSP, index %d","An internal error occurred in the Intermediate System-to-Intermediate System (ISIS) or NetWare Link Services Protocol (NLSP).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CLNS","3","UNAVAILABLE","Checkpoint initialization error (%s)","An unrecoverable error occurred during initialization of the checkpoint client.","At the current time there is no work around. If the error message continues to occur, report the problem to the TAC."
"CLNS","3","UNAVAILABLE","Checkpoint send error (%s)","An unrecoverable error occurred following a request to checkpoint a new or changed adjacency or LSP.","At the current time there is no work around. If the error message continues to occur, report the problem to the TAC."
"CLNS","3","UNAVAILABLE","Checkpointed ADJ circuit id mismatch for %s (%d/%d)","A checkpoint message for an ISIS adjacency was dropped by the standby RP because the circuit id interface does not match the circuit ID reported by the active RP.","At the current time there is no work around. The circuit id problem should disappear following the next switchover."
"CLNS","3","UNAVAILABLE","ISIS bulk sync failed to complete","The bulk sync of ISIS adjacency and LSP data from the active to the standby RP failed to complete successfully. Any attempt by ISIS to perform a non-stop forwarding restart may be incomplete. (Note that ISIS should still converge correctly.)","At the current time there is no work around. The adjacency and LSP databases should still sync up between the active and standby RPs, following completion of the bulk sync. If they do not, report the output from 'show isis nsf', 'show clns neighbor', and 'show isis database' on both RPs and contact the TAC."
"CLNS","3","UNAVAILABLE","ISIS: Bad if number, pdb %#x, idb %#x, if %#x","An internal error occurred in the Intermediate System-to-Intermediate System (ISIS) or NetWare Link Services Protocol (NLSP). An inconsistency was detected in an internal data structure related to tracking protocol/interface state, possibly related to enable/disable of the protocol on an interface.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CLNS","3","UNAVAILABLE","ISIS: LSP list traversal incomplete (%s)","An internal error occurred in the Intermediate System-to-Intermediate System (ISIS) or NetWare Link Services Protocol (NLSP).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CLNS","3","UNAVAILABLE","ISIS: entry already threaded, prev %#x, next %#x, index %d, ver %d","An internal error occurred in the Intermediate System-to-Intermediate System (ISIS) or NetWare Link Services Protocol (NLSP).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CLNS","3","UNAVAILABLE","Interface %s cannot be encoded for nsf cisco","Adjacency and LSP information learned from this interface cannot be checkpointed due to an interface encoding error.","Please verify that this interface type is supported for NSF in this release. If so, report the problem to the TAC."
"CLNS","3","UNAVAILABLE","Invalid NSAP type in ES table: %x for %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CLNS","4","UNAVAILABLE","%s Invalid interface clns MTU %d","This message occurs if the interface MTU becomes unusable while ISIS is running on the interface. This condition maybe temporary and recoverable.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CLNS","4","UNAVAILABLE","%s%s: attempt to exceed LSP maximum sequence number for LSP %s","Attempt was made to exceed maximum sequence number for an LSP.","Protocol will shutdown for max-lsp-lifetime + 1 minute. This is a very unlikely natural occurrence. Investigate to find the source of any out of order reception, generation, or incrementing of this LSP's sequence number."
"CLNS","4","UNAVAILABLE","%s: %s authentication failed","An ISIS packet(IIH, CSNP, PSNP or LSP) was received and did not pass authentication check.","If the error persists, check the originating router for matching authentication mode and password."
"CLNS","4","UNAVAILABLE","%s: Bad L%d LSP %s checksum %04x received on %s, length %d, should be %04x, bad count %d","A link-state packet (LSP) was received for either Intermediate System-to-Intermediate System (ISIS) or NetWare Link Services Protocol (NLSP), which failed an internal data checksum, but which passed the data-link checksum. The interface on which the LSP was received is indicated, along with the total count of checksum errors received, the LSP ID, and the level of the failing LSP. This message usually indicates data corruption occurring on a link, but might also indicate data corruption in a neighboring router's memory.","If the error is in a neighboring router's memory, the problem will correct itself within 15 minutes. That router will detect its internal error and regenerate the corrupted data. This case is usually indicated by a single LSP ID appearing repeatedly in these messages. The same LSP ID might appear in this message on other routers as well. If data-link corruption has caused the error, check the link for errors and deal with them appropriately. This case is usually indicated by a number of different LSP IDs appearing in these messages."
"CLNS","4","UNAVAILABLE","%s: possible duplicate system ID %s detected","This is a configuration error.","One of the duplicate IDs needs to be corrected."
"CLNS","4","UNAVAILABLE","Encapsulation failed, dst= %s","This message can occur when an interface is down and a static neighbor entry exists in the system's CLNS routing table. If this is not the case, the message indicates an internal software error.","Check the interface. If the interface is not down and no static neighbor entry exists for that interface, call your technical support representative for assistance."
"CLNS","4","UNAVAILABLE","ISIS: Inconsistent ip prefix and mask(%i%#m) in ISIS LSP: pdb=%s, level=%d, lspid=%s. The route wasn't added into RIB.","The system received a link-state packet (LSP) which contained a bad IP prefix TLV (type length value). The mask corresponding with the address was incorrect.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CLNS","4","UNAVAILABLE","Invalid NSAP type in IS table: %x %d","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CLNS","4","UNAVAILABLE","Redirect found for non-route entry, dst= %s, next-hop= %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CLNS","4","UNAVAILABLE","Too many IS-IS areas--can't route to area %s","Intermediate System-to-Intermediate system (IS-IS) allows only three area addresses per area. Multiple routers with at least one area address in common merge all of their configured area addresses into a single set. If the resulting set includes more than three area addresses, this message appears and indicates that there will be a loss of connectivity to the specified area.","Reconfigure the network so that the area has fewer area addresses, or split the area into multiple areas."
"CLNS","5","UNAVAILABLE","%s%s: All %sadjacencies cleared","All Intermediate System-to-Intermediate System (ISIS) or NetWare Link Services Protocol (NLSP) adjacencies of the specified type have been cleared. This message appears only if the log-adjacency-changes command is configured for the ISIS or NLSP process.","This informational message appears as a normal side effect of appropriate console or configuration commands."
"CLNS","5","UNAVAILABLE","%s: %scast address in use on %s","A NetWare Link Services Protocol (NLSP) adjacency with a neighboring router has either come up or gone down. The message describes whether the NLSP multicast address is in use for future updates sent on the LAN. This message appears only if the log-adjacency-changes command is configured for the NLSP process.","This message is primarily informational and appears normally as routers and links go up or down."
"CLNS","5","UNAVAILABLE","%s: Adjacency to %s (%s) %s, %s","An Intermediate System-to-Intermediate System (ISIS) or NetWare Link Services Protocol (NLSP) adjacency with a neighboring router has either come up or gone down. The message describes the change and the reason for it. This message appears only if the log-adjacency-changes command is configured for the ISIS or NLSP process.","This informational message normally appears as routers and links go up or down. However, unexpected adjacency loss might indicate high error rates or high packet loss in the network and should be investigated."
"CLNS","5","UNAVAILABLE","%s: MPLS TE Forwarding Adjacency to %s (%s) %s, %s","A Multiprotocol Label Switching forwarding adjacency associated with the Intermediate System-to-Intermediate System (ISIS) routing protocol has either come up or gone down. The message describes the change and the reason for it. This message appears only if the log-adjacency-changes command is configured for the ISIS or NLSP process.","This informational message normally appears as routers and links go up or down. However, unexpected adjacency loss might indicate high error rates or high packet loss in the network and should be investigated."
"CLNS","5","UNAVAILABLE","ISIS NSF cancelled - 'nsf interval' expiration pending","ISIS cancelled the NSF restart since either the active or standby RP had not been up long enough. In Cisco mode, the active RP must signal that it has been up for a minimum of 'nsf interval' seconds. For IETF mode, the standby RP must be up for a minimum of 'nsf interval' seconds.","Review the setting of the 'nsf interval' command"
"CLNS","5","UNAVAILABLE","ISIS NSF cancelled - ISSU negotiation failed for NSF CISCO","ISIS cancelled the NSF restart since ISSU negotiation failed in Cisco mode.","Review the output of 'show issu negotiated version' command"
"CLNS","5","UNAVAILABLE","ISIS NSF completion","ISIS performed an NSF restart","This informational message appears as a normal side effect of a restart performed while NSF is enabled."
"CLNS","7","UNAVAILABLE","%s: %08x %08x %08x %08x %08x %08x","Internal use only","Should not be seen in the field"
"CLNS","7","UNAVAILABLE","Debug: %s","Debug information.","No action required"
"CLOCK","3","UNAVAILABLE","Hardware Calendar (RTC) Error.","The hardware calendar contains an invalid date. The accepted range is from 1993 to 2035.","To correct the invalid date, use the calendar set command and the clock read-calendar command."
"CLOCKSW","3","UNAVAILABLE","%s: bogus plimtype 0x%x","This indicates an internal error in the IDB. This interface can not be selected as a network clocking source.","Select another interface as the network clocking source."
"CLOCKSW","3","UNAVAILABLE","All selected network clock sources have failed","All of the configured network clocking sources have failed.","Restore proper operation to one or more of the selected interfaces"
"CLOCKSW","3","UNAVAILABLE","Network clock source %s, priority %d, failure","Specified network clocking source has failed.","Restore proper operation of the selected interface"
"CLOCKSW","6","UNAVAILABLE","Bypassing FC-PFQ PLL","The FC-PFQ clock is non-operational, bypassing","LOG_STD_NO_ACTION"
"CLOCKSW","6","UNAVAILABLE","Network clock source %s, priority %d, ok","Specified network clocking source is operational.","LOG_STD_NO_ACTION"
"CLOCKSW","6","UNAVAILABLE","Switching from %s to %s at priority level %d","The network clock source has changed from one source to another.","LOG_STD_NO_ACTION"
"CLS","3","UNAVAILABLE","%s","A software error detected while manipulating CLSIMsg objects.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CLS","3","UNAVAILABLE","CLS: Assertion failed: %s","A software or hardware error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CLS","3","UNAVAILABLE","Unknown CLS verb for %s context, DlcOpcodeT=%04x","A bad opcode was generated by the DLC for the STN or CEP.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CLSDR","3","UNAVAILABLE","%s couldn't get a message","The destination logical unit (DLU) could not send a correct message to Cisco Link Services I (CLSI) because the message was formed incorrectly. CLSI will not perform the desired 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CLSDR","3","UNAVAILABLE","%s failed error 0x%x","An error was returned from Cisco Link Services I (CLSI) to the destination logical unit (DLU) because CLSI did not perform the action desired by the DLU.","Refer to CLSI software documentation for more information about this error. Report this error to your technical support representative."
"CLSDR","3","UNAVAILABLE","CLSDRIVER not initialized","A CLSDRIVER initialization failed earlier. Trying to use the driver now results in an error condition.","Remove and then restore the destination logical unit (DLU) in the configuration file and try and reboot the system. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CLSDR","3","UNAVAILABLE","Cannot create DLU for this type %d","The CLSDRIVER does not understand the destination logical unit (DLU) type. Currently, only STUN uses the CLSDRIVER. Any other value results in an error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CLSDR","3","UNAVAILABLE","Cannot create PORT structure","The CLSDRIVER cannot enable this port for processing.","Try rebooting the router. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CLSDR","3","UNAVAILABLE","Cannot found cep in free pool","A software or hardware error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CLSDR","3","UNAVAILABLE","Incorrect port pointer in USapId","Cisco Link Services I (CLSI) returned an incorrect port pointer in the USapID.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CLSDR","3","UNAVAILABLE","RemoveCep : Cep 0x%x not on list","The destination logical unit (DLU) is trying to remove a nonexistent connection end point from the internal data structure. This creates a problem in the connection end point (CEP) maintenance logic.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CLSDR","3","UNAVAILABLE","RemovePort: port 0x%x not on list","The destination logical unit (DLU) is trying to remove an nonexistent port from the list of active ports because it does not have the correct list of active ports.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CLSDR","3","UNAVAILABLE","Should never be here, cls message type unknown 0x%x","The CLS message type is unknown to the destination logical unit (DLU).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CLSDR","3","UNAVAILABLE","unable to start the Server process","Could not start the CLSDRIVER process, possibly due to a resource problem. The subsystem using CLSDRIVER does not work.","Remove and then restore the destination logical unit (DLU) in the configuration file and try and reboot the system. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CLUE","3","CHECKSUM_ERROR","CLUE record checksum error in record, id [dec], record starting address %#x, new checksum %#x, previous checksum %#x","A Compact Local Unit Exchange (CLUE) record stored in the CLUE memory has a bad checksum and cannot be accessed. The CLUE record was either modified by a CLUE client but not committed or it was modified by memory corruption.","Internal CLUE client software will attempt to automatically correct the error. If the error persists, reload the unit."
"CLUE","3","CLIENT_REGISTRY_FULL","Maximum of [dec] CLUE clients registered. Cannot register callback %#x","No more Compact Local Unit Exchange (CLUE) clients can be registered because the client registry for callback service is full. Unregistered CLUE clients will not be informed about CLUE service events such as CLUE service ready status or CLUE record corruptions.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show clue commands and your pertinent troubleshooting logs."
"CLUE","3","COMMIT_FAILED","CLUE cannot commit record, id [dec]","The specified CLUE record was not committed in the CLUE storage memory, so the CLUE record cannot be accessed. Either the CLUE record was not allocated by the CLUE client before committing or there was an error in the internal CLUE record index table.","The internal CLUE client software will attempt to automatically correct the error. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CLUE","3","EOR_CORRUPT","CLUE record corruption in end of record field, record id [dec], record starting address %#x","A CLUE record's end of record delimiter was corrupted in the CLUE storage memory, so the CLUE record cannot be accessed. The CLUE record was overwritten by the previous CLUE record or by a memory corruption.","Internal CLUE client software will attempt to automatically correct the error. If the error persists, reload the unit."
"CLUE","3","INDEX_BUILD_FAIL","Failed to build CLUE internal record index due to [chars]","CLUE could not build an internal record index table, so the CLUE service will not be available and any data in the CLUE storage cannot be accessed. This failure can occur either when CLUE storage does not exist or when any CLUE record within the CLUE storage is corrupted.","Internal CLUE client software will attempt to automatically correct the error. If the error persists, reload the unit."
"CLUE","3","INIT_ERROR","Failed to initialise the reserved memory for new CLUE context due to [chars]","Reserved memory for the Compact Local Unit Exchange (CLUE) storage area was not initialized due to the reason given. The CLUE storage area will not be available to provide any CLUE service.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show clue commands and your pertinent troubleshooting logs."
"CLUE","3","INTERNAL_SW_ERROR","[chars]","An internal Compact Local Unit Exchange (CLUE) software error was reported.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show clue commands and your pertinent troubleshooting logs."
"CLUE","3","INVALID_AREA","Either address %#x or size [dec] reserved for CLUE storage area is invalid","An internal Compact Local Unit Exchange (CLUE) software error occurred. In order to initialize and use the reserved area as a CLUE storage area, CLUE expected a non-zero reserved memory address and a non-zero reserved memory size.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show clue commands and your pertinent troubleshooting logs."
"CLUE","3","INVALID_REC_DATA_SIZE","CLUE record size [dec] is invalid to allocate CLUE record [dec]","An internal Compact Local Unit Exchange (CLUE) software error occurred. When the CLUE client requested to allocate the CLUE record, the record size was zero or was not the same as expected. The CLUE record was not allocated.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show clue commands and your pertinent troubleshooting logs."
"CLUE","3","INVALID_REC_ID","Invalid CLUE record id [dec] has been received so CLUE cannot [chars] it","An internal Compact Local Unit Exchange (CLUE) software error occurred. The indicated action cannot be carried out on the specified CLUE record ID because the record ID is not valid.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show clue commands and your pertinent troubleshooting logs."
"CLUE","3","NOT_ENOUGH_CLUE_STORAGE","CLUE storage has not enough space to allocate record, id [dec] and data size [dec]","An internal Compact Local Unit Exchange (CLUE) software error occurred. The CLUE record was not allocated for the record ID because not enough space for CLUE storage was reserved or the CLUE storage contingency space was full.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show clue commands and your pertinent troubleshooting logs."
"CLUE","3","NOT_ENOUGH_MEMORY","[dec]-bytes of local memory has not enough space left to reserve [dec]-bytes of CLUE storage","Insufficient local memory was available to reserve the required Compact Local Unit Exchange (CLUE) storage space.","Add more local memory."
"CLUE","3","NO_SIGNATURE","CLUE cannot [chars] record, id [dec]","The specified CLUE record was not serviced because CLUE storage was not available or because the CLUE storage signature was invalid.","The internal CLUE client software will attempt to automatically correct the error. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CLUE","3","SOR_CORRUPT","CLUE record corruption in start of record field, record id [dec], record starting address %#x","A CLUE record's start of record delimiter was corrupted in the CLUE storage memory, so the CLUE record cannot be accessed. The CLUE record was overwritten by the previous CLUE record or by a memory corruption.","The internal CLUE client software will attempt to automatically correct the error. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CM622_CM155","4","UNAVAILABLE","(%d/%d) %s command error: %s","Linecard ATM driver handles RP command errors.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CM622_CM155","4","UNAVAILABLE","(%d/%d) ATM Clock Internal Set on (%d/%d) too","CM155 ATM Clock Internal is enabled for the other channel on the same framer too, the framer defines one bit for both channels.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CM622_CM155","4","UNAVAILABLE","(%d/%d) RX SAR doing %s error: %s (indication=0x%08x 0x%08x 0x%08x)","Linecard ATM driver RX SAR indication errors.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CM622_CM155","4","UNAVAILABLE","(%d/%d) VC:%u %s error (cause: %s)","CM622/CM155 ATM SAR VC operation error.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CM622_CM155","4","UNAVAILABLE","(%d/%d) VC:%u is close pending","The VC is in the TX SAR close pending state.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CM622_CM155","4","UNAVAILABLE","(%d/%d) VC:%u unsupported vc encapsulation type=%u","CM622/CM155 ATM SAR VC operation error.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CM622_CM155","4","UNAVAILABLE","(Port %d): %s SAR doing %s error: %s","Linecard ATM driver SAR operation error.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CM622_CM155","4","UNAVAILABLE","(Port %d): %s SAR firmware selftest failure (expected 0x%04x, obtained 0x%04x)","Linecard ATM SAR firmware checksum errors.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CM622_CM155","4","UNAVAILABLE","(Port %d): TX SAR %s command error: %s (indication=0x%08x)","Linecard ATM driver TX SAR indication error.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CM622_CM155","4","UNAVAILABLE","Error: (%d/%d) %s (value=0x%04x)","Linecard ATM driver framer operation errors.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CM622_CM155","4","UNAVAILABLE","Error: (%d/%d) %s","Linecard ATM driver general operation errors.","Copy the error message exactly as it appears, and report it to your technical support representative"
"CMCC","3","UNAVAILABLE","DNS lookup failed - %s","The InterProcess Communication (IPC) service used by the TN3270 Server on the CMCC has experienced a DNS lookup failure.","Verify that the proper revisions of code are selected."
"CMCC","3","UNAVAILABLE","Interface %s: Error (%-04x) %s","An error occurred sending an interface enable or disable command.","The interface was reset by the software and the condition rectified. If that did not occur, then issue the debug channel events command and try each of the following tasks in sequence. If an action corrects the problem, the remaining tasks do not need to be performed."
"CMCC","3","UNAVAILABLE","Interface %s: No elements avail for msg (%08X %08X); interface reset.","An encapsulated control message arrived, but no elements were available to receive it. It is likely that a configuration will now be in a PENDING state. An interface reset was attempted to clear this condition.","Issue thedebug channel events command and try each of the following tasks in sequence. If an action corrects the problem, the remaining tasks do not need to be performed. Clear the interface using the clear interface command. Reload the microcode. Reload the router. If the error still occurs, copy the error message exactly as it appears. Record the output from the following commands: show tech show log Provide this information to your technical support representative."
"CMCC","3","UNAVAILABLE","Interface %s: No pre-allocated buffers available; enable not sent","An attempt to get a pre-allocated buffer for the enable command was unsuccessful. The interface will not be enabled.","Issue thedebug channel events command and try each of the following tasks in sequence. If an action corrects the problem, the remaining tasks do not need to be performed. Clear the interface using the clear interface command. Reload the microcode. Reload the router. If the error still occurs, copy the error message exactly as it appears. Record the output from the following commands: show tech show log Provide this information to your technical support representative."
"CMCC","3","UNAVAILABLE","Interface %s: encaps msg size (%d) smaller than min (%d); dropped.","An encapsulated control message had a size smaller than the minimum expected size. The message was dropped.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CMCC","3","UNAVAILABLE","Interface %s: unknown encapsulated msg(%d) len(%d)","An encapsulated control message had an unknown encapsulation type. The message was dropped.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CMCC","3","UNAVAILABLE","Invalid IPC request (%d) received from (%x)","The InterProcess Communication (IPC) service used by the TN3270 Server on the CMCC has received an invalid message.","Verify that the proper revisions of code are selected."
"CMCC","3","UNAVAILABLE","Unable to initialize IPC %s services","The InterProcess Communication (IPC) service used by the TN3270 Server on the CMCC has failed to initialize.","The CMCC will not load properly. The router must be reloaded to clear the problem."
"CMCC","3","UNAVAILABLE","Unable to obtain IPC resources","The InterProcess Communication (IPC) service used by the TN3270 Server on the CMCC has failed to obtain a buffer.","The CMCC will not load properly. Try the reload command again. If this message recurs, call your technical support representative for assistance."
"CMCC","4","UNAVAILABLE","DNS lookup failed - the DNS server has no entry for hostname %s","The InterProcess Communication (IPC) service used by the TN3270 Server on the CMCC has experienced a DNS lookup failure.","Verify that the DNS server entries are up to date."
"CMCC","4","UNAVAILABLE","Interface %s: Channel-protocol %s cmd failed; resetting to default","The channel-protocol configuration command sent after a reset failed to complete successfully.","The channel data transfer rate was reset to the default value. Reissue the configuration command."
"CMCC","4","UNAVAILABLE","Interface %s: Unable to pre allocate response element; cfg not sent","An attempt to allocate a buffer for the configuration response, or for the configuration state change request, was unsuccessful. The configuration request was not sent.","The configuration command must be reissued."
"CMCC","4","UNAVAILABLE","Interface %s: configuration command %s %s failed","An error occurred sending the configuration command to the CMCC card, or the CMCC negatively acknowledged the command","Reissue the configuration command."
"CMCC","4","UNAVAILABLE","Interface %s: encapsulated msg size (%d) exceeds max (%d); truncated.","An encapsulated control message had a size greater than the maximum expected size. The message was truncated.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CMCC","5","UNAVAILABLE","DNS lookup failed - DNS server %i is unreachable","The InterProcess Communication (IPC) service used by the TN3270 Server on the CMCC has experienced a DNS lookup failure.","Check for available routes to DNS servers."
"CMCC","5","UNAVAILABLE","DNS lookup failed - query to DNS server %s timed out","The InterProcess Communication (IPC) service used by the TN3270 Server on the CMCC has experienced a DNS lookup failure.","Check the status of the DNS server."
"CMCC","6","UNAVAILABLE","Interface %s: adapter type changed from %s to %s","The interface reported a different interface type than it previously did. This should not happen without removing the CMCC card and replacing it with one that has an interface of the reported type.","This is an informational message, no action is required"
"CMAPP","6","UNAVAILABLE","Cannot create Call Manager Application process","Failed to create the Call Manager Application process.","Check the size of free memory to make sure there is enough memory."
"CMP","5","NBR_UPD_SIZE_TOO_BIG","Number of neighbors in neighbor update is [int], maximum number of neighbors allowed in neighbor update is [int]","The number of cluster neighbors in the clustering neighbor update packet exceeds the number of neighbors supported by the clustering module design.","No action is required."
"CM_DSPRM","1","UNAVAILABLE","DSPRM event unavailable","The router or access server could not allocate internal resources.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CM_DSPRM","1","UNAVAILABLE","DSPRM internal error[%s:%d","The router or access server has detected an internal error.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CM_DSPRM","1","UNAVAILABLE","IOS buffer pool unavailable [%s:%d]","The router or access server could not allocate internal resources.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CM_DSPRM","1","UNAVAILABLE","IOS memory unavailable [%s:%d]","The router or access server could not allocate memory for internal data structures.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CM_MONITOR","5","UNAVAILABLE","Sending DNS response to %i (request was for %i)","A hardware or software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CM_MONITOR","5","UNAVAILABLE","Starting DNS process","A hardware or software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CM_MONITOR","5","UNAVAILABLE","Terminating DNS process","A hardware or software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CM_SYNC","3","UNAVAILABLE","Unable to transmit message type %d from %s","A transmit error occurred while sending msg to other CPU, due to msg translation","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CM_SYNC","3","UNAVAILABLE","Unable to transmit message type %d from %s","A transmit error occurred while sending msg to other CPU, due to non-availability of buffer","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CNS","3","MEMORY","[chars]","CNS subsystem has experienced a problem gettting the required memory to complete this operation.","Check system memory for other memory allocation errors and contact Technical support for problem resolution. In the absence of IOS errors, upgrading the memory in the network device may be required."
"CNS","3","TRANSPORT","[chars]","The CNS subsystem has experienced a problem contacting an external application.","See specific message text for an indication of what the cause might be. Check the network configuration and cables to make sure that the remote application is running and the address is accessible."
"CNS","3","WARNING","[chars]","The CNS subsystem has encountered an unexpected condition while executing a set of commands that did not cause a failure but suggests things did not go totally correctly.","Check the error log for additional information. This is an informational message and does not necessarily indicate that an error occurred."
"CNS","3","XML_SEMANTIC","[chars]","The CNS subsystem has encountered an error while processing the XML encapsulation of configuration command.","The externally supplied XML has errors in it and connot be processed. See the specific message text for an indication of what the cause might be. This condition could possibly require that the command be checked and reissued from the server."
"CNS","5","CONFIG_SUCCESS","SUCCESSFUL_COMPLETION","The configuration download has been applied successfully.","No action is required."
"CNS","6","NO_EVENT_AGENT","CNS EVENT AGENT IS NOT CONFIGURED","The CNS event agent is not configured. The event that was to be sent to it will be dropped","Configure the CNS event agent."
"COLLECTION","3","UNAVAILABLE","Attempted to start a walk with incompatible mode and priority (mode %s priority %s)","COLLECTION_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COLLECTION","3","UNAVAILABLE","Attempted to start a walk with incompatible mode and process (mode %s process %s)","COLLECTION_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COLLECTION","3","UNAVAILABLE","Initialization of process %s failed, unable to %s","COLLECTION_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COLLECTION","3","UNAVAILABLE","Subwalk mismatch, walk %p (priority %s mode %s) subwalk %p (priority %s mode %s)","COLLECTION_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","2","UNAVAILABLE","Attempt to create CEF interface for %s with illegal if_number: %d","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","2","UNAVAILABLE","Attempt to create CEF interface for %s with illegal index: %d","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","2","UNAVAILABLE","Attempt to use out of bounds interface index: %d","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","2","UNAVAILABLE","Attempt to used uninitialized CEF data structure.","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","%s %s","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","%s %s subblock doesn't support ISSU and can't be used.","The given SW subblock doesn't support ISSU so may not be processed correctly on the LC. It has not been registered by the CEF component.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","%s","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","%s NULL fibidb in broadcast sb","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","%s broker failed to encode msg type %d for slot(s) %s","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","%s chunk pool could not be %s. Possible memory leak.","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","%s distribution broker not found - distributing %s","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","%s for %s - %s","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","%s path list %s","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","%s: %s","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","API called with NULL fibidb","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","An internal software error occurred. %s linked to wrong hwidb %s","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","An internal software error occurred. %s linked to wrong idb %s","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","An internal software error occurred. %s should be first fibidb","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","Assertion '%s' failed in %s CEF [0x%08x]: %s (%s)%s.","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","Attached export tracking error: %s","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","Attempt to clear the name of %s table with tableid %d, previous name %s","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","Attempt to create %s table with illegal tableid %d (%s)","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","Attempt to update fibidb prior to completion of idb initialization.","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","Bad magic for element %p (0x%08x != 0x%08x)","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","Cannot find ISSU message type for FIB %s (%d) %sSB %s msg","The given SW subblock is being sent to an ISSU aware endpoint but CEF cannot verify that this message has been negotiated successfully and cannot send it. This is a coding error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","FIB%sIDB name %s error (lengths %d (%d), short %d (%d))","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","Failed to start %s of %sentries in table %s","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","Generic subblock error: %s","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","HW API failure for %s CEF [0x%08x]: %s (%s)%s.","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","IPMFI Timing Tool present in image - performance will be degraded","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","IPV6_SWSB_CTRL name length error, %s (acl_in %d (%d), acl_out %d (%d), pbr %d (%d))","IPv6 in/out ACL and IPv6 PBR name lengths for/from an IPC XDR message are invalid. The names will not be used so as to prevent any buffer overrun errors. There is a possibility that either the XDR message or an internal IPv6 FIB structure is corrupted","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","Illegal arguments - %s","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","Invalid XDR format. %s","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","Invalid XDR length. Type %d (%s). XDR/buffer len %d/%d","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","Invalid address family %d%s","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","Invalid address type %d%s","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","Manipulating interest list - %s","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","Memory allocation failure for %s in %s CEF [0x%08x] (%s)%s.","An attempt to allocate memory has failed. Depending on the criticality of the data to be stored, CEF operation may be impacted.","Verify that the configuration is supported by the memory present in the system. Copy the message exactly as it appears, and report it to your technical support representative."
"COMMON_FIB","3","UNAVAILABLE","Message %s (%d) is ISSU aware so cannot use old FIB API.","ALL FIB subblocks must be ISSU aware. The subblock code must be rewritten for ISSU. Otherwise this may lead to unpredictable behaviour when running in SSO mode with two different versions of IOS.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","Missing name for fibhwidb (ifindex %d)","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","No %s subblock control decode function for %s","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","No fibidb for %s (ignoring path) during path no %d update for %s","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","No handler for units (%s) - from slot %s","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","No valid paths for prefix %s in vrf %s.","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","Subtree context unexpected error: app %s: %s","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","Unable to find MPLS oce for %s IP oce","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","Unexpected disposition information for %s","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","Unexpected element type %u","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","Walk specification %p missing handler for type %d dependency","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","dqueue has an active collection just prior to destruction","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","dqueue is not empty just prior to destruction","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","elem %p type 0x%x elem-next %p elem-next_type 0x%x elem-next-prev %p","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","elem %p type 0x%x elem-prev %p elem-prev_type 0x%x elem-prev-next %p","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","3","UNAVAILABLE","fibidb %s if_nb %d could not be %s db","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","4","UNAVAILABLE","%s CEF is being disabled due to a fatal error.","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","4","UNAVAILABLE","Attempted add of subblock of type '%s' (%d) for %s failed%s","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","4","UNAVAILABLE","Attempting to insert %p after %p but it has prev set to %p","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","4","UNAVAILABLE","Attempting to insert %p after %p but it is still pointed at by %p","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","4","UNAVAILABLE","Attempting to remove %p but it has no prev (next is %p)","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","4","UNAVAILABLE","Attempting to remove %p but prev %p points at %p instead","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","4","UNAVAILABLE","Attempting to remove %p with next %p thinks its prev is %p","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","4","UNAVAILABLE","CEF %s database auto-repair executed","The CEF consistency checkers have detected an inconsistent prefix in one of the CEF forwarding databases. The auto-repair function has been executed to repair the problem. Details of the prefix can be found using the 'show cef table consistency' command.","Copy the message exactly as it appears, together with the output of the 'show cef table consistency' command and report it to your technical support representative,"
"COMMON_FIB","4","UNAVAILABLE","Encoding of %s %s stats XDR too big","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","4","UNAVAILABLE","HW subblock decode (%s / %d) - wrong length read (expected %d, decoded %d)","The given HW subblock is not being processed correctly on the linecard. The error has been corrected, but should be reported in case there are related problems that need to be addressed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","4","UNAVAILABLE","Hardware in slot %s missing prefix for %s/%d in FIB table %s (present in LC FIB) [%s]","A passive consistency checker discovered a prefix in the LC FIB table which is not present in the hardware forwarding table on this linecard. This may be a transient condition.","LOG_SH_FIB_PREFIX_ACTION"
"COMMON_FIB","4","UNAVAILABLE","Hardware on RP missing prefix for %s/%d in FIB table %s (present in RP FIB) [%s]","A passive consistency checker discovered a prefix in the RP FIB table which is not present in the hardware forwarding table on the RP. This may be a transient condition.","LOG_SH_FIB_PREFIX_ACTION"
"COMMON_FIB","4","UNAVAILABLE","Invalid message received. Type %s, event/sub-type %d, length %d","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","4","UNAVAILABLE","Invalid message: %s, type %s, len %d","An invalid message has been received by this broker.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","4","UNAVAILABLE","Message %s for slots %s is too large (%d bytes, max %d)","There is not enough buffer space for ISSU transformations. The message must not proceed any further or a buffer overrun may result.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","4","UNAVAILABLE","Message %s for slots %s is wrong length (%d, should be %d)","The encoded message length doesn't match the expected length. Message will not be sent.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","4","UNAVAILABLE","Mis-match between hwidb %s (ifindex %d) and fibhwidb %s (ifindex %d)","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","4","UNAVAILABLE","Mis-match between idb %s (if_number %d) and fibidb %s (if_number %d)","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","4","UNAVAILABLE","Missing hwidb for fibhwidb %s (ifindex %d)","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","4","UNAVAILABLE","Missing idb for fibidb %s (if_number %d).","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","4","UNAVAILABLE","No fibhwidb for %s found during %s","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","4","UNAVAILABLE","No fibhwidb while initializing fibidb for %s (if_number %d)","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","4","UNAVAILABLE","No fibidb found for %s during %s","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","4","UNAVAILABLE","RP has prefix %s/%d in FIB table %s (missing in routing table) [%s]","A passive consistency checker discovered a prefix in the CEF forwarding table which is not present in the routing table. This may be a transient condition.","LOG_SH_FIB_PREFIX_ACTION"
"COMMON_FIB","4","UNAVAILABLE","RP missing prefix for %i%m in FIB table %s (present in routing table) [%s]","A passive consistency checker discovered a prefix in the routing table which is not present in the CEF forwarding table on the RP. This may be a transient condition.","LOG_SH_FIB_PREFIX_ACTION"
"COMMON_FIB","4","UNAVAILABLE","RP missing prefix for %s/%d in FIB table %s (present in RP hardware) [%s]","A passive consistency checker discovered a prefix in the hardware table which is not present in the FIB forwarding table on the RP. This may be a transient condition.","LOG_SH_FIB_PREFIX_ACTION"
"COMMON_FIB","4","UNAVAILABLE","RP prefix for %s/%d in FIB table %s (inconsistent on slot %s - %s) [%s]","A passive consistency checker discovered a prefix in the forwarding table of the linecard which is inconsistent on the RP. This may be a transient condition.","If the same prefix gives repeated errors check the CEF prefix on the RP and linecard. If necessary, a clear cef linecard will download a new CEF table to the linecard."
"COMMON_FIB","4","UNAVAILABLE","Ratio of unequal path weightings (%s) prevents oce %s from being used.","When attempting to setup the load balancing infrastructure for a prefix with unequal path weightings, CEF discovered that the range of weightings caused one or more paths to be excluded from the final set of load balancing paths. Load balancing will continue with the remaining paths.","Reduce the range of weightings to allow all the paths to be used."
"COMMON_FIB","4","UNAVAILABLE","SW subblock decode (%s / %d) - wrong length read (expected %d, decoded %d)","The given SW subblock is not being processed correctly on the linecard. The error has been corrected, but should be reported in case there are related problems that need to be addressed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","4","UNAVAILABLE","Slot %s missing prefix entry for %s in FIB table %s when looking up %s [%s]","A packet arrived on the linecard, but the lookup of the destination IP address failed to find this prefix in the forwarding table. However the prefix is present on the RP. This may be a transient condition.","If the same prefix gives repeated errors check the CEF prefix on the RP and linecard. If necessary, a clear cef linecard will download a new CEF table to the linecard. You can also try a clear adjacency command to reload host prefixes."
"COMMON_FIB","4","UNAVAILABLE","Slot %s missing prefix for %s/%d in FIB table %s (present in LC hardware) [%s]","A passive consistency checker discovered a prefix in the LC hardware table which is not present in the FIB forwarding table on this linecard. This may be a transient condition.","LOG_SH_FIB_PREFIX_ACTION"
"COMMON_FIB","4","UNAVAILABLE","Slot %s prefix entry for %s/%d in FIB table %s [%s] reason: %s","A passive consistency checker discovered a prefix that is present on the RP, but is inconsistent in the forwarding table of the linecard. This may be a transient condition.","If the same prefix gives repeated errors check the CEF prefix on the RP and linecard. If necessary, a clear cef linecard will download a new CEF table to the linecard. You can also try a clear adjacency command to reload host prefixes."
"COMMON_FIB","4","UNAVAILABLE","The platform has enabled and prohibited %s for %s","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","4","UNAVAILABLE","Unable to register XDR client (%s).","COMMON_FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_FIB","6","UNAVAILABLE","%s has too many (%u) levels of recursion during %s","CEF discovered that the routing for a prefix involved excessive many levels of recursion and was forced to terminate an operation on the entry for that prefix. This is likely to be caused by a recursion loop","If the problem persists use show commands to display the RIB and CEF information for the prefix in question and check its configuration"
"COMMON_FIB","6","UNAVAILABLE","%s is found to resolve via itself during %s","CEF discovered that the routing for a prefix has recursive paths that leads back to itself and CEF was forced to terminate an operation on the entry for that prefix.","If the problem persists use show commands to display the RIB and CEF information for the prefix in question and check its configuration"
"COMMON_FIB","6","UNAVAILABLE","Test subblock error: %s","The subblock test command could not be completed successfully","LOG_STD_NO_ACTION"
"COMMON_MFIB","3","UNAVAILABLE","%s broker failed to encode msg type %d for slot(s) %s","COMMON_MFIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_MFIB","3","UNAVAILABLE","%s distribution broker not found - distributing %s","COMMON_MFIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_MFIB","3","UNAVAILABLE","%s: %s","COMMON_MFIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_MFIB","3","UNAVAILABLE","Assertion '%s' failed in %s MFIB [0x%08x]: %s (%s)%s.","COMMON_MFIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_MFIB","3","UNAVAILABLE","Attempt to clear the name of %s table with tableid %d, previous name %s","COMMON_MFIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_MFIB","3","UNAVAILABLE","Attempt to create %s table with illegal tableid %d (%s)","COMMON_MFIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_MFIB","3","UNAVAILABLE","Failed to %s table %s%s","COMMON_MFIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_MFIB","3","UNAVAILABLE","Failed to initialise %s RP broker facility","COMMON_MFIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_MFIB","3","UNAVAILABLE","Generic subblock error: %s","COMMON_MFIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_MFIB","3","UNAVAILABLE","Illegal arguments - %s","COMMON_MFIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_MFIB","3","UNAVAILABLE","Invalid XDR format. %s","COMMON_MFIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_MFIB","3","UNAVAILABLE","Invalid XDR length. Type %d %s. XDR/buffer len %d/%d","COMMON_MFIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_MFIB","3","UNAVAILABLE","Invalid address family %d%s","COMMON_MFIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_MFIB","3","UNAVAILABLE","Memory allocation failure for %s in %s MFIB [0x%08x].","An attempt to allocate memory has failed. Depending on the criticality of the data to be stored, MFIB operation may be impacted.","Verify that the configuration is supported by the memory present in the system. Copy the message exactly as it appears, and report it to your technical support representative."
"COMMON_MFIB","4","UNAVAILABLE","%s MFIB is being disabled due to a fatal error.","COMMON_MFIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_MFIB","4","UNAVAILABLE","Failed to %s table %s %s","An MFIB table was found to be missing when attempting to perform a change to it. This may be a transient condition","If the same table gives repeated warnings or generates more seriouserrors, copy the message exactly as it appears and report it to your technical support representative"
"COMMON_MFIB","4","UNAVAILABLE","Invalid message received. Type %s, event/sub-type %d, length %d","COMMON_MFIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_MFIB","4","UNAVAILABLE","Invalid message: %s, type %s, len %d","An invalid message has been received by this broker.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_MFIB","4","UNAVAILABLE","Unable to register XDR client (%s).","COMMON_MFIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMMON_MFIB","4","UNAVAILABLE","XDR client (%s) should be registered.","COMMON_MFIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMP","3","UNAVAILABLE","%s: COMPRESS: (stac error!) status: %d, size in: %d, size out: %d","An internal software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"COMP","3","UNAVAILABLE","Interface %s Bad status returned from packet compression operation","An internal software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"COMP","3","UNAVAILABLE","Interface %s Compression Version mismatch expected %x received %x","One interface is configured for predictor compression, the other is not.","Configure both interfaces for predictor compression."
"COMP","3","UNAVAILABLE","Interface %s Compression internal configuration error","An internal software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"COMP","3","UNAVAILABLE","Interface %s Decompression size error","One interface is configured for predictor compression, the other is not.","Configure both interfaces for predictor compression."
"COMP","3","UNAVAILABLE","Interface %s Decompression sync error","One interface is configured for predictor compression, the other is not.","Configure both interfaces for predictor compression."
"COMP","3","UNAVAILABLE","Interface %s compression subblock creation failed.","An internal software error occurred.Copy the error message exactly as it appears, and report it to your technical support representative.COMP-5Error Message    %COMP-5-UNAVAILABLE: Interface %s %s Explanation    Interface serial0 compression getbuffer failed, causing Link Access Procedure, Balanced (LAPB) retransmissions.","Configure additional large and big buffers."
"COMP_MATRIX","3","UNAVAILABLE","ISSU Compatibility Matrix was unable to delete a persistent variable from the %s system (rc = %d).","The ISSU compatibility matrix was unable to access a persistent variable. There is no way to determine if issu image-version compatibility checking should be enabled or disabled.","Show persistent variable. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMP_MATRIX","3","UNAVAILABLE","ISSU Compatibility Matrix was unable to read a persistent variable from the local system (rc = %d).","The ISSU compatibility matrix was unable to access a persistent variable. There is no way to determine if issu image-version compatibility checking should be enabled or disabled.","Show persistent variable. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMP_MATRIX","3","UNAVAILABLE","ISSU Compatibility Matrix was unable to write to persistent variables on the %s system (rc = %d).","The ISSU compatibility matrix was unable to access a persistent variable. There is no way to determine if issu image-version compatibility checking should be enabled or disabled.","Show persistent variable. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COMP_MATRIX","4","UNAVAILABLE","Compatibility Matrix has been disabled. No image compatibility checking will be done.","The ISSU compatibility matrix check has been disabled via configuration command no service image-version compatibility. When the standby comes up, no image compatibility checking will be done, which results in SSO redundancy mode even if the active and standby are running different images.","The ISSU compatibility matrix check has been disabled using the global configuration command no service image-version compatibility.Redundancy mode would be SSO. Please be sure this is your intention or change configuration using service image-version compatibility."
"COT","1","UNAVAILABLE","%s","Failed to allocate memory for COT DSP event queue","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COT","1","UNAVAILABLE","%s","Failed to create a periodic process or chunk pool or cot/dsp queue for COT","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COT","1","UNAVAILABLE","%s","Failed to enqueue DSP event to COT DSP event queue","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COUGAR_EHSA","5","UNAVAILABLE","%s %d","A significant Running config sync file event has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COUGAR_EHSA","5","UNAVAILABLE","Forcibly closing fd: %d name:%s","A file activity timeout occurred on the secondary.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPAD","1","UNAVAILABLE","%s creation failed for slot %d","The CSA driver, in its initialization phase, could not allocate memory for the specified data structure.","Consider adding more shared memory. Copy the error message exactly as it appears, and report it to your technical support representative."
"CPAD","1","UNAVAILABLE","%s: %s","An error occured in the application using the CSA.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CPAD","1","UNAVAILABLE","Slot %d: %s","The CSA driver failed to initialize at the specified point.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CPAD","1","UNAVAILABLE","bay %d Invalid vendor/device id %d","The CSA driver, in its initialization phase, encountered a communication failure with the CSA in the specified bay.","Consider reseating the specified CSA. Copy the error message exactly as it appears, and report it to your technical support representative."
"CPAD","1","UNAVAILABLE","bay %d: Deactivating card","An error occured during initialization. The CSA is being deactivated","Copy the error message exactly as it appears, and report it to your technical support"
"CPAD","6","UNAVAILABLE","%s shutting down","The specified CSA is shutting down. It may have been physically removed.","This is a informational message only. It occurs in normal operation."
"CPAD","6","UNAVAILABLE","%s starting up","The specified CSA has initialized successfully.","This is a informational message only. It occurs in normal operation."
"CPM","3","UNAVAILABLE","CPM at slot %d: PCI device not supported","An interface controller device did not report the correct PCI device ID.","Power down, reinsert the port module, and reboot. If the message recurs, call your technical support representative for assistance."
"CPM","3","UNAVAILABLE","CPM at slot %d: PCI discovery failed count = %d","One of the interface controller devices on the module did not initialize properly.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CPU_NET","0","UNAVAILABLE","The interface between the CPU and the switch has become stuck. The switch must now reset to clear this condition .Retrieval queue %d.","The CPU can no longer communicate with the network.","Reload the system."
"CPU_REDUN","2","UNAVAILABLE","%s","A software error occurred during initialization of the CPU redundancy subsystem","Check for sufficient processor memory. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_REDUN","3","UNAVAILABLE","%s %d %d","A subsystem initialization error occurred.","LOG_STD_NO_ACTION"
"CPU_REDUN","3","UNAVAILABLE","%s %d","The 4msec timer interrupt was shut off for an extended period while the hardware watchdog was enabled.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_REDUN","3","UNAVAILABLE","%s %d sec, %s = %x","The CPU redundancy process didn't run for a long time, because an interrupt routine ran too long.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_REDUN","3","UNAVAILABLE","%s %s","An error occurred that affects CPU Redundancy services. The details about what was attempted and what went wrong will be printed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_REDUN","3","UNAVAILABLE","%s %s software subsystem. Active=%d, Standby=%d.","Standby CPU software subsystem is older or missing. See message text for software subsystem type. May result in feature losses in the event of a switchover.","May require a software upgrade on the Standby CPU. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_REDUN","3","UNAVAILABLE","Alarm: %s, %s, %s, %s, %s","If the alarm appears when this is asserted for a standby processor with a different software image, it indicates an alarm condition on the peer that the active processor can not decode. If this is asserted for the active processor, it indicates a software error condition.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_REDUN","3","UNAVAILABLE","Alarm: %s, %s, %s, %s, %s","The alarm appears when the active processor is detecting bad parity on the active/standby bits read from the standby processor.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_REDUN","3","UNAVAILABLE","Alarm: %s, %s, %s, %s, %s","The alarm appears when the capabilities reported by the standby processor are less than the active processor. The processors are conditionally redundant, which means that a switchover could result in a partial loss of system control.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_REDUN","3","UNAVAILABLE","Alarm: %s, %s, %s, %s, %s","The alarm appears when the peer processor is either missing or can not be detected. The active processor currently is not being protected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_REDUN","3","UNAVAILABLE","Alarm: %s, %s, %s, %s, %s","The alarm appears when the peer processor is present but not responding or sending keepalives.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_REDUN","3","UNAVAILABLE","Alarm: %s, %s, %s, %s, %s","The alarm appears when the processor can not access its backplane IDPROM.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_REDUN","3","UNAVAILABLE","Alarm: %s, %s, %s, %s, %s","The alarm appears when the processor has failed the linecard access test for multiple linecards.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_REDUN","3","UNAVAILABLE","Alarm: %s, %s, %s, %s, %s","The alarm appears when the processor has failed the online diagnostic internal PCI bus test.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_REDUN","3","UNAVAILABLE","Alarm: %s, %s, %s, %s, %s","The alarm appears when the processor has failed the online diagnostic internal PCMCIA slot test.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_REDUN","3","UNAVAILABLE","Alarm: %s, %s, %s, %s, %s","The alarm appears when the processor has failed the online diagnostic internal SRC test.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_REDUN","3","UNAVAILABLE","Alarm: %s, %s, %s, %s, %s","The alarm appears when the processor redundancy state is either not consistent with the peer state, or the software state is not consistent with the hardware state.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_REDUN","3","UNAVAILABLE","Alarm: %s, %s, %s, %s, %s","The alarm appears when the slot ID read from the backplane IDPROM does not match the slot ID read from the SRC.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_REDUN","3","UNAVAILABLE","Alarm: %s, %s, %s, %s, %s","This alarm appears when the processor can't transmit characters on the console UART. It indicates a probable equipment failure","If the symptom persists following a reload, remove and replace the processor module."
"CPU_REDUN","3","UNAVAILABLE","Attempt to sync %s config to standby failed","Unable to send Startup or Private Config file to Standby CPU","LOG_STD_NO_ACTION"
"CPU_REDUN","3","UNAVAILABLE","Attempt to sync running config to standby failed","Unable to send Running Config file to Standby CPU","LOG_STD_NO_ACTION"
"CPU_REDUN","3","UNAVAILABLE","Can't change my state. desired state %s, read-back %s","Local CPU can't set its redundancy state to the desired calculated value","Check health of local CPU. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_REDUN","3","UNAVAILABLE","Can't get Global Lock","Peer CPU won't relinquish the arbitration lock.","Check that both the local and peer CPUs are fully seated in the backplane. Check the health of the Peer CPU. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_REDUN","3","UNAVAILABLE","Detected invalid redundancy states, local = %s, peer = %s","Detected an invalid combination of redundant states","LOG_STD_NO_ACTION"
"CPU_REDUN","3","UNAVAILABLE","Error/Mismatch in readingVendor ID for PCI device %d 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message    %CPU_REDUN-3-UNAVAILABLE: Incorrectly formatted message (0x%x, 0x%x) received by %s","Inconsistent message data was received from the peer CPU, possibly due to an incompatible image version.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_REDUN","3","UNAVAILABLE","Invalid peer CPU severity (%d) (current peer register=0x%x)","Peer CPU is reporting an invalid severity value.","Check that both the local and peer CPUs are fully seated in the backplane. Check the health of the Peer CPU. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_REDUN","3","UNAVAILABLE","Invalid peer CPU state (%s) (current peer register=0x%x)","Peer CPU is reporting an invalid redundancy state.","Check that both the local and peer CPUs are fully seated in the backplane. Check the health of the Peer CPU. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_REDUN","3","UNAVAILABLE","Mismatch in %s driver versions. Active=%d.%d, Standby=%d.%d.","Standby CPU is reporting lower versions than the Active CPU. See message text for type of limitation.May result in a loss of connections.","May require a software upgrade on the Standby CPU. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_REDUN","3","UNAVAILABLE","Mismatch in %s. Active=%d, Standby=%d.","Standby CPU is reporting lower Capabilities than the Active CPU. See message text for type of limitation.","Check for sufficient Standby CPU capabilities. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_REDUN","3","UNAVAILABLE","Mismatch in %s. Active=%d.%d, Standby=%d.%d.","Standby CPU is reporting lower versions than the Active CPU. See message text for type of limitation.","Check Standby CPU version numbers. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_REDUN","3","UNAVAILABLE","Missing %s driver support on Standby. Active=%d.%d","Standby CPU is missing support for one of the drivers available on the Active CPU. The corresponding linecard will go down in the event of a switchover.","May require a software upgrade on the Standby CPU. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_REDUN","3","UNAVAILABLE","Parity Error on PCI Bus fromPCI Device 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message    %CPU_REDUN-3-UNAVAILABLE: Software state (%s) doesn't reflect local hardware (%s)","Software state is not following the underlying hardware redundancy state","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_REDUN","3","UNAVAILABLE","Status error in PCI device %d 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message    %CPU_REDUN-3-UNAVAILABLE: Unknown message type 0x%x received by %s","An unknown message type was received from the peer CPU, possibly due to an incompatible image version.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_REDUN","4","UNAVAILABLE","%s %d %s","System is running for an extended period in an unprotected mode even though a peer CPU is present","Check the health of the Peer CPU. Configure as maintenance mode to intentionally suppress error messages. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_REDUN","4","UNAVAILABLE","Active CPU FPGA has been reprogrammed. Please remove and re-insert the CPU in slot %d or power-cycle the box, for the new FPGA to take effect.","Active CPU FPGA has been reprogrammed. This CPU is now running with old FPGA and it needs to be hot-swapped or the system needs to be power-cycled for the new FPGA to take effect.","LOG_STD_NO_ACTION"
"CPU_REDUN","4","UNAVAILABLE","Non-volatile configuration memory is not present","The startup-config is missing. This may be due to eithera manual user erase command or an interrupted write to thestartup-config.","Do a copy running-config startup-config to savecurrent system configuration. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_REDUN","5","UNAVAILABLE","%s %d","Reloading due to a negotiated switchover.","LOG_STD_NO_ACTION"
"CPU_REDUN","5","UNAVAILABLE","%s (sev %d), peer is %s (sev %d)","A CPU hardware redundancy status change occurred.","LOG_STD_NO_ACTION"
"CPU_REDUN","5","UNAVAILABLE","%s","Reloading due to a hardware software state mismatch.","LOG_STD_NO_ACTION"
"CPU_REDUN","5","UNAVAILABLE","%s","Reloading standby since Active CPU shows loss of comm.","LOG_STD_NO_ACTION"
"CPU_REDUN","5","UNAVAILABLE","Forcibly closing fd: %d name:%s","A file activity timeout occurred on the slave.","LOG_STD_NO_ACTION"
"CPU_REDUN","5","UNAVAILABLE","Msgtype %s sent by %s unsupported by peer.","Peer responded that it didn't recognize a message sent by this CPU, possibly due to a different image version.","May require a software upgrade on the Standby CPU. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_REDUN","5","UNAVAILABLE","Peer CPU hardware and software is fully compatible.","Standby CPU H/W, drivers and software subsystems have matching versions and capabilities.","LOG_STD_NO_ACTION"
"CPU_REDUN","5","UNAVAILABLE","Peer CPU has been removed from the chassis","Peer CPU has been removed from the chassis.","LOG_STD_NO_ACTION"
"CPU_REDUN","5","UNAVAILABLE","Peer CPU has exited IOS","Peer CPU has exited IOS.","LOG_STD_NO_ACTION"
"CPU_REDUN","5","UNAVAILABLE","Running config successfully synced to standby","Running Config file was sent to the Standby CPU","LOG_STD_NO_ACTION"
"CPU_REDUN","5","UNAVAILABLE","Sending %s = %d","Normal response for CPU EHSA Redundancy services. The details about what was sent will be printed.","LOG_STD_NO_ACTION"
"CPU_REDUN","5","UNAVAILABLE","Startup config successfully synced to standby","Startup Config file was sent to the Standby CPU","LOG_STD_NO_ACTION"
"CPU_REDUN","5","UNAVAILABLE","Switchover occurred. Reason: %s","A CPU switchover took place. The reported reason is listed in the error message text.","LOG_STD_NO_ACTION"
"CPU_REDUN","6","UNAVAILABLE","%s %s","A significant EHSA Redundancy services event occurred. The details will be printed.","LOG_STD_NO_ACTION"
"CPU_REDUN","6","UNAVAILABLE","After returning to ROM by %s","Informational message notifying about a system startup with no switchover.","LOG_STD_NO_ACTION"
"CPU_REDUN","6","UNAVAILABLE","Running config on this CPU has possibly changed","Informational message to notify of possible changes to the running-config file","LOG_STD_NO_ACTION"
"CPU_REDUN","6","UNAVAILABLE","Startup config on this CPU has possibly changed","Informational message to notify of possible changes to the startup-config file","LOG_STD_NO_ACTION"
"CSM","1","UNAVAILABLE","%s","Failed to create a periodic process for CSM or the number of digit collectors reported to CSM exceeds the maximum number of digit collectors.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CSM","1","UNAVAILABLE","%s","The modem signaling module failed initialization","Copy the error message exactly as it appears, and report it to your technical support representative."
"CSM","1","UNAVAILABLE","%s at slot %d, controller %d, timeslot %d","This is an internal software error. An attempt is made to add non existent CAS signalling interface.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CSM","1","UNAVAILABLE","%s at slot %d, port %d","An initialization error occurred on the specified port. The error message specifies more details","Try reseting the port or power cycling the system. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CSM","1","UNAVAILABLE","%s: %d/%d received invalid event %d","An invalid operation was detected by the router","Copy the error message exactly as it appears, and report it to your technical support representative."
"CSM","1","UNAVAILABLE","%s: hwidb is NULL","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CSM","1","UNAVAILABLE","%s: hwidb is NULL","An invalid operation was detected by the router","Copy the error message exactly as it appears, and report it to your technical support representative."
"CSM","1","UNAVAILABLE","%s: hwidb subblock for b channel %d is in use","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CSM","1","UNAVAILABLE","%s: modem_info is NULL","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CSM","1","UNAVAILABLE","A new RBS channel added Error Message    %CSM-1-UNAVAILABLE: An Unexpected event received by tone process - %d %d.","An invalid operation was detected by the router","Copy the error message exactly as it appears, and report it to your technical support representative."
"CSM","1","UNAVAILABLE","An error was encountered in enqueuing a %s (%d) for slot/port %d/%d.","The modem may no longer be usable.","The amount of memory available in the router may not be sufficient. Copy the error message exactly as it appears and contact your technical support representative."
"CSM","1","UNAVAILABLE","An error was encountered in enqueuing a CAS message - %s.","The modem may no longer be usable.","The amount of memory available in the router may not be sufficient. Copy the error message exactly as it appears and contact your technical support representative."
"CSM","1","UNAVAILABLE","Modem %d/%d has been marked as bad by the router software.","The modem is no longer usable due to a runtime error.","The modem may become operational following a reset of the router. If not, copy the error message exactly as it appears and contact your technical support representative."
"CSM","1","UNAVAILABLE","String copy exceeded buffer size","The string written into the allocated buffer exceeded the size of the buffer. This can cause memory corruption.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CSM","1","UNAVAILABLE","The T1 or E1 network module is incompatible with the digital modems: %s","The T1 or E1 network module cannot be used with digital modems.","Copy the error message exactly as it appears, and contact your technical support representative for upgrade information."
"CSM","5","UNAVAILABLE","%s at slot %d, unit %d, channel %d with index %d","An ISDN PRI interface has changed states. Details of the new state are shown in the error message.","LOG_STD_NO_ACTION"
"CSM","5","UNAVAILABLE","%s at slot %d, unit %d, with index %d","An ISDN MBRI insterface has changed states. Details of the new state are shown in the error message.","LOG_STD_NO_ACTION"
"CSM","5","UNAVAILABLE","CAS mbox at %x in use - message has been %s.","A CAS IPC message has been queued because the mailbox is in use.","This is a notification message. Copy the error message exactly as it appears and contact your technical support representative if the modems are not functional or this message appears frequently."
"CSM_SLB","3","UNAVAILABLE","Module %d FT error: %s","An error occurred in CSM-SLB fault tolerance.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CSM_SLB","3","UNAVAILABLE","Module %d configuration reload failed: %s","Configuration reload of the CSM-SLB card failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CSM_SLB","3","UNAVAILABLE","Module %d error: %s","An error occurred in a CSM-SLB module.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CSM_SLB","3","UNAVAILABLE","Module %d image version mismatch, RP = %s, CSM = %s: %s","Router image and CSM-SLB image do not correspond.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CSM_SLB","3","UNAVAILABLE","Module %d memory error: %s","Out of memory condition while downloading SLB configurations onto CSM card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CSM_SLB","3","UNAVAILABLE","Module %d script error: %s","An error occurred in a CSM-SLB script.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CSM_SLB","3","UNAVAILABLE","Module %d unexpected error: %s","An unexpected error condition occurred on the CSM-SLB card while performing Server Load Balancing.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CSM_SLB","3","UNAVAILABLE","Portchannel allocation failed for module %d.","Unable to allocate enough portchannel groups for CSM-SLB card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CSM_SLB","3","UNAVAILABLE","Unknown error occurred while configuring IDB for CSM-SLB module: %s.","Unable to configure data path for CSM-SLB card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CSM_SLB","4","UNAVAILABLE","Module %d ARP configuration error: %s","Error creating or removing a static ARP route.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CSM_SLB","4","UNAVAILABLE","Module %d FT warning: %s","Some possibly undesired event occurred in CSM-SLB fault tolerance.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CSM_SLB","4","UNAVAILABLE","Module %d configuration warning: %s","Syntax error in a URL or COOKIE regular expression in SLB configuration.","LOG_STD_NO_ACTION"
"CSM_SLB","4","UNAVAILABLE","Module %d duplicate ID: %s","Same ID was used to create multiple entities.","LOG_STD_NO_ACTION"
"CSM_SLB","4","UNAVAILABLE","Module %d invalid ID: %s","The entity identified does not exist.","LOG_STD_NO_ACTION"
"CSM_SLB","4","UNAVAILABLE","Module %d probe configuration error: %s","Health probe configuration failed.","LOG_STD_NO_ACTION"
"CSM_SLB","4","UNAVAILABLE","Module %d regular expression memory error: %s","A lookup table does not contain enough space to store the configured URL and COOKIE regular expressions. Use 'show ip slb memory' to determine which virtual server(s) were unable to be configured because of insufficient memory.","LOG_STD_NO_ACTION"
"CSM_SLB","4","UNAVAILABLE","Module %d script warning: %s","Some possibly undesired event occurred in CSM-SLB scripting.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CSM_SLB","4","UNAVAILABLE","Module %d warning: %s %s","There is a mismatch between the configuration andthe specified environment variable","Check the documentation for any caveats regardingthe use of the concerned environment variable."
"CSM_SLB","4","UNAVAILABLE","Module %d warning: %s","Some possibly undesired event occurred in a CSM-SLB module.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CSM_SLB","4","UNAVAILABLE","Module %d warning: %s","There may be a problem with your network topology or configuration.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CSM_SLB","4","UNAVAILABLE","Received CSM-SLB module version wildcard on slot %d. Supervisor has version %d.","User issued a command from the linecard to bypass the safeguard against module version mismatch. As a result, configuration may fail.","LOG_STD_NO_ACTION"
"CSM_SLB","6","UNAVAILABLE","Module %d FT info: %s","Some event occurred in CSM-SLB fault tolerance.","LOG_STD_NO_ACTION"
"CSM_SLB","6","UNAVAILABLE","Module %d gateway state changed: %s","A gateway changed states.","LOG_STD_NO_ACTION"
"CSM_SLB","6","UNAVAILABLE","Module %d info: %s","Some event occurred in a CSM-SLB module.","LOG_STD_NO_ACTION"
"CSM_SLB","6","UNAVAILABLE","Module %d script info: %s","Some event occurred in CSM-SLB scripting.","LOG_STD_NO_ACTION"
"CSM_SLB","6","UNAVAILABLE","Module %d server state changed: %s","A real server changed states (failed or recovered). Possible causes might be configuration changes, arp checks or health probes.","LOG_STD_NO_ACTION"
"CSM_VOICE","3","UNAVAILABLE","CSM failed to add the CAS TDM hairpinning call","The CSM voice software interface was unable to add this call as hairpinning because of presence of another call for the same DS0. Internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CSM_VOICE","3","UNAVAILABLE","CSM failed to get a free dsp tdm channel from the DSP Resource Manager (DSPRM) to handle an incoming call","The voice software was unable to obtain the tdm channel for a free dsp from the DSP Resource Manager. All of the dsp's have been used to process calls, or have been taken out of service.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CSM_VOICE","3","UNAVAILABLE","Invalid interface slot:controller:group(%d/%d:%d)","The voice interface defined by slot:controller:group is not yet defined within the voice software but attempts were made to use this interface.","Internal software fault. Contact your field service representative if this message is coincident with dropped calls."
"CSM_VOICE","3","UNAVAILABLE","Invalid voice interface controller:group(%d:%d)","The voice interface defined by controller:group is not yet defined within the voice software but attempts were made to use this interface.","Internal software fault. Contact your field service representative if this message is coincident with dropped calls."
"CSM_VOICE","3","UNAVAILABLE","No memory is available to build any internal data structure for the voice software.","The voice software was unable allocate memory to build any internal data structures. The system may be out of memory.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CSM_VOICE","3","UNAVAILABLE","No memory is available to build the voice interface (%d:%d)","The voice software was unable allocate memory to build a voice interface data structure. The system may be out of memory.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CSM_VOICE","3","UNAVAILABLE","No signaling data block is available to build the voice interface(%d/%d:%d)","The voice software was unable to obtain a signaling data block from the Voice Telephony Service Provider. The system may be out of memory.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CSM_VOICE","3","UNAVAILABLE","No signaling data block is available to build the voice interface(%d:%d)","The voice software was unable to obtain a signaling data block from the Voice Telephony Service Provider. The system may be out of memory.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CSM_VOICE","3","UNAVAILABLE","The Voice Telephony Service Provider has rejected our request to add this voice interface (%d/%d:%d)","The voice software was unable to report a new signaling interface to the Voice Telephony Service Provider","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CSM_VOICE","3","UNAVAILABLE","The Voice Telephony Service Provider has rejected our request to add this voice interface (%d:%d)","The voice software was unable to report a new signaling interface to the Voice Telephony Service Provider","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CSM_VOICE","3","UNAVAILABLE","Undefined dsx0 interface for controller(%d)","The dsx0 interface for the specified controller is not defined but the voice software use it.","Internal software fault. Contact your field service representative if this message is coincident with dropped calls."
"CSM_VOICE","3","UNAVAILABLE","Undefined dsx0 interface for controller(%d/%d)","The dsx0 interface for the specified controller is not defined but the voice software use it.","Internal software fault. Contact your field service representative if this message is coincident with dropped calls."
"CT3","1","UNAVAILABLE","%s","A CT3 Port Adapter was detected which has a revision earlier than rev3. This port adapter pre-dates the router platform it has been installed in, and is not a supported combination.","Upgrade to a CT3 Port Adapter which is rev3 or above."
"CT3","1","UNAVAILABLE","%s could not be disabled by %s","The shutdown failed to disable the interface.","Copy the error message exactly as it appears, collect the output of 'show tech-support' command immediately, and report it to your and report it to your technical support representative. If possible, try to do an OIR (Online Insertion and Removal). Please refer to the Cisco documentation for information on 'Online Insertion and Removal' for your platform"
"CT3","1","UNAVAILABLE","%s could not be enabled by %s","The restart failed to enable the interface.","Copy the error message exactly as it appears, and report it to your technical support representative. If possible, try to do an OIR (Online Insertion and Removal). Please refer to the Cisco documentation for information on 'Online Insertion and Removal' for your platform"
"CT3","1","UNAVAILABLE","%s could not be reset by %s","The restart failed to reset the interface.","Copy the error message exactly as it appears, collect the output of 'show tech-support' command immediately, and report it to your technical support representative."
"CT3","1","UNAVAILABLE","%s init failed at %s","CT3 initialization failure.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CT3","1","UNAVAILABLE","Failed to configure %d interfaces in bay %d, shutting down bay","The CT3 hardware failed. Some components on the board failed to initialize.","Replace the CT3 port adapter."
"CT3","1","UNAVAILABLE","Found %d interfaces in bay %d, shutting down bay","The CT3 hardware failed. Some components on the board failed to initialize.","Copy the error message exactly as it appears, collect the output of 'show tech-support' command immediately, and report it to your technical support representative."
"CT3","1","UNAVAILABLE","Microcode to slot %d","Failed to download firmware into the CT3 port adapter.","Copy the error message exactly as it appears, collect the output of 'show tech-support' command immediately, and report it to your technical support representative. If possible, try to do an OIR (Online Insertion and Removal). Please refer to the Cisco documentation for information on 'Online Insertion and Removal' for your platform"
"CT3","1","UNAVAILABLE","Slot %d firmware init (%s)","CT3 firmware initialization failure.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CT3","1","UNAVAILABLE","Slot %d for microcode download","An error was detected on the communication path between VIP and CT3.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CT3","2","UNAVAILABLE","%#08x %08x %08x %08x","CT3 firmware crash information","Copy the error message exactly as it appears, and report it to your technical support representative."
"CT3","2","UNAVAILABLE","%s: packet received for unknown VC %d","The virtual channel encapsulation is corrupted.","Copy the error message exactly as it appears, collect the output of 'show tech-support' command immediately, and report it to your technical support representative."
"CT3","3","UNAVAILABLE","%s - Accumulator is not available","An invalid TX accumulator is detected.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CT3","3","UNAVAILABLE","%s","General error information.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CT3","3","UNAVAILABLE","%s packet buffer, pak=0x%x","A software or hardware error occurred. The CT3 driver detected that the transmit ring is in an inconsistent and unrecoverable state.","Copy the error message exactly as it appears, collect the output of 'show tech-support' command immediately, and report it to your technical support representative."
"CT3","3","UNAVAILABLE","%s: failed to send %s love letter","A love letter was not sent to RSP.","Copy the error message exactly as it appears, collect the output of 'show tech-support' command immediately, and report it to your technical support representative."
"CT3","3","UNAVAILABLE","Failed to receive reply %d from bay %d firmware","A message was not received from CT3 firmware.","Copy the error message exactly as it appears, collect the output of 'show tech-support' command immediately, and report it to your technical support representative. If possible, try to do an OIR (Online Insertion and Removal). Please refer to the Cisco documentation for information on 'Online Insertion and Removal' for your platform"
"CT3","3","UNAVAILABLE","Failed to send msg %d to %s driver firmware","A port related message was not sent to CT3 firmware.","Copy the error message exactly as it appears, collect the output of 'show tech-support' command immediately, and report it to your technical support representative. If possible, try to do an OIR (Online Insertion and Removal). Please refer to the Cisco documentation for information on 'Online Insertion and Removal' for your platform"
"CT3","3","UNAVAILABLE","Failed to send msg %d to bay %d firmware","A message was not sent to CT3 firmware.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CT3","3","UNAVAILABLE","Failed to send msg %s to bay %d firmware","Specified message was not sent to CT3 firmware.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CT3","3","UNAVAILABLE","Received unexpected mailbox message (id = %d)","Unexpected message from CT3 firmware.","Copy the error message exactly as it appears, collect the output of 'show tech-support' command immediately, and report it to your technical support representative."
"CT3","3","UNAVAILABLE","Slot %d device ID seen as %#x, expected %#x (Mueslix)","Failed to detect the hdlc controller on the CT3.","Replace the CT3 port adaptor."
"CT3","3","UNAVAILABLE","Slot %d device ID seen as %#x, expected %#x (PLX9060)","The PLX 9060 was not detected on the CT3.","Replace the CT3 port adaptor."
"CTRC","3","UNAVAILABLE","%s","An APPC error occurred. ctrc uses APPC API calls to SNASW to communicate with the remote database server.","This usually indicates a problem in the SNA network. Try the ctrc ping command to test connectivity to the remote database server. If the ctrc ping fails, check the status of the SNA link to the remote database server with the show snasw link command. If the link is active try stopping and starting the link. If the problem persists, contact your SNA network administrator for help in troubleshooting. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.If possible, also provide the output of the debug ctrc appc command, and an SNA line trace between the router and the remote database server, for the period during which this message appeared."
"CTRC","3","UNAVAILABLE","No buffers available to %s","CTRC attempted to allocate a buffer while performing the operation described in the message text. A buffer pool does not contain enough items to satisfy the allocation request.","This problem most commonly occurs whenever a public buffer pool runs out of elements. Determine the which pool has run out of buffers using the show buffers command. Adjust the pool size using the buffers configuration command."
"CTRC","3","UNAVAILABLE","SNASW is not started -- unable to connect to remote database.","A client connected to a ctrc server, but ctrc was unable to connect out to the remote database because SNASW is not started. ctrc uses SNASW to connect to the remote database server. You must start SNASW before ctrc clients attempt to connect.","Start SNASW, and retry the client connection."
"CTRC","3","UNAVAILABLE","SNASW was stopped -- existing connections have been closed.","SNASW was stopped while ctrc connections were open. Stopping SNASW caused all open SNA connections to the remote database server to be lost. As a result, all client connections were disconnected. You should not stop SNASW while there are open ctrc connections.","Restart SNASW. Disconnected clients must reconnect."
"CTRC","3","UNAVAILABLE","Unexpected APPC error: opcode %04x, primary code %04x, secondary code %08lx","An unexpected APPC error occurred. ctrc uses APPC API calls to SNASW to communicate with the remote database server. Opcode identifies the APPC API call that received the error. Primary and secondary return codes are returned by the APPC API.","This usually indicates a problem in the SNA network. Try the ctrc ping command to test connectivity to the remote database server. If the ctrc ping fails, check the status of the SNA link to the remote database server with the show snasw link command. If the link is active try stopping and starting the link. If the problem persists, contact your SNA network administrator for help in troubleshooting. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.If possible, also provide the output of the debug ctrc appc command, and an SNA line trace between the router and the remote database server, for the period during which this message appeared."
"CTRC","4","UNAVAILABLE","%s","An APPC error occurred. ctrc uses APPC API calls to SNASW to communicate with the remote database server.","This usually indicates a temporary problem in the SNA network. Try the ctrc ping command to test connectivity to the remote database server. If the ctrc ping fails, check the status of the SNA link to the remote database server with the show snasw link command. If the link is active try stopping and starting the link. If the problem persists, contact your SNA network administrator for help in troubleshooting. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.If possible, also provide the output of the debug ctrc appc command, and an SNA line trace between the router and the remote database server, for the period during which this message appeared."
"CONST_V6","5","FIB_EXCEP_OFF","Protocol IPv6 recovered from FIB exception","The IPv6 CEF table successfully reloaded to the hardware FIB TCAM. All IPv6 packets will be switched by the hardware.","No action is required."
"CONST_V6","5","FIB_EXCEP_ON","Failed to insert an IPv6 prefix in hardware FIB TCAM","The switch failed to insert an IPv6 entry into the hardware FIB TCAM because the total number of software-forwarding entries exceeded the hardware FIB TCAM limit. Some IPv6 packets might be switched by the software.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CONTROLLER","2","UNAVAILABLE","Controller %s, %s","A software or hardware error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CONTROLLER","2","UNAVAILABLE","For controller %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CONTROLLER","2","UNAVAILABLE","Interface Processor in slot %d not responding (%x): shutting it down","A controller stopped responding to commands over the cBus, so it was put into shutdown mode.","Re-enable the controllers by issuing the no shut configuration command on all controllers on the card, or hotswap out the bad card and install the new one. You must still manually no shut the controllers."
"CONTROLLER","5","UNAVAILABLE","Controller %s, %s","A configurable controller clock changed its state.","No action is required."
"CONTROLLER","5","UNAVAILABLE","Controller %s, %s","A configurable controller loopback status.","No action is required."
"CONTROLLER","5","UNAVAILABLE","Controller %s, %s","A software or hardware error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"CONTROLLER","5","UNAVAILABLE","Controller %s, changed state to %s","A configurable controller changed its state.","No action is required."
"CONTROLLER","5","UNAVAILABLE","Controller %s, changed state to %s due to %s","A configurable controller changed its state.","No action is required."
"CONTROLLER","5","UNAVAILABLE","Controller %s, remote loop %s %s","A configurable controller entered remote loopback.","No action is required."
"CONTROLLER","5","UNAVAILABLE","Insufficient HDLC resources to enable channel %d","Limited number of HDLC channels can be allocated for this trunk","Please check the number of HDLC resources supported for this trunk card. Please contact your technical support representative"
"COPTMONMIB","3","UNAVAILABLE","An entry is already present for the registering interface with ifIndex %d","An entry in the OPTICAL MONITORING MIB is already existing for the registering interface","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COPTMONMIB","3","UNAVAILABLE","Registering of the interface with ifIndex %d to local data structure failed","An attemt to make an entry for the registering interface failed","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"COUGAR_EHSA","3","NCLK_FUNCVER_MISMATCH","Mismatch in the Network Clock Module Functional Version number. The Functional Version of the Network clock module in the Primary = [dec].[dec]","This may lead to loss of Network Clocking functionality if and when a CPU switchover occurs. The system is now running CONDITIONALLY REDUNDANT - subject to the above mentioned restrictionError Message    No action required.%COUGAR_EHSA-3-TWO_PRIM_DETECT: Other RP has declared PRIMARY, two primaries active in chassis. This RP will now crash to avoid this condition. Explanation    N/A","No action required."
"CPU_INTF_FPGA","2","DEV_INIT_FAILURE","The CPU Interface FPGA initialization failed due to [chars]","The CPU interface FPGA initialization was not successful due to a hardware problem. This condition will cause packet drops.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_INTF_FPGA","2","INT","[chars]","A fatal interrupt has occurred and the device has been reinitialized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_INTF_FPGA","2","NULL_DEV_OBJECT","The CPU Interface FPGA device object pointer is set to NULL","The memory location of the CPU Interface FPGA device object is invalid. The CPU interface FPGA operation is disabled and the device interrupt is now masked.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_INTF_FPGA","3","DEV_UNPAUSE_FAIL","Status register is [hex]","An attempt to unpause traffic from the CPU interface FPGA to the backplane interface ASIC has timed out. This failure may lead to traffic disruption.","If normal traffic processing does not resume, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_INTF_FPGA","3","QUEUE_ALLOC_FAILED","Failed to allocate queue in the CPU Interface FPGA for 	SPA in bay ([dec])","Failed to allocate a queue for the SPA in the given bay. This failure may lead to traffic disruption.","If normal traffic processing does not resume, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_INTF_FPGA","4","DEV_WARN_INT","[chars]","The CPU interface FPGA received a nonfatal interrupt. This event should not affect the normal operation of the device.","No action is required."
"CPU_INTF_FPGA","5","PAUSE_FAIL","FPGA status register is [hex]","An attempt to pause traffic from the CPU interface FPGA to the backplane interface ASIC has timed out. This event may lead to traffic disruption.","If normal traffic processing does not resume, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CPU_MONITOR","2","NOT_RUNNING","CPU_MONITOR messages have not been sent for [dec] seconds [[chars] [dec]%/[dec]% ([time-stamp] [dec]%/[dec]%)] [[chars] [time-stamp]] [[chars] [time-stamp]] [[chars] [time-stamp]]","CPU monitor messages have not been detected for a significant amount of time. A timeout is likely to occur soon, which will reset the system.","No action is required."
"CPU_MONITOR","2","NOT_RUNNING_TB","CPU_MONITOR traceback: [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]","This message provides additional debugging information for the NOT_RUNNING message. The message displays the traceback of the interrupted functions.","No action is required."
"CPU_MONITOR","3","KERNEL_OPERATION","CPU_MONITOR kernel operation failed: [chars]","A CPU_MONITOR kernel operation required to identify supect threads has failed.","This is an informational message only. No action is required."
"CPU_MONITOR","3","PEER_EXCEPTION","CPU_MONITOR peer has failed due to exception , resetting [[dec]/[dec]]","The CPU monitor messages failed on the peer processor. The system is no longer operational.","No action is required."
"CPU_MONITOR","3","PEER_FAILED","CPU_MONITOR peer process has failed to receive heartbeats, reset by [%d/%d]","The CPU monitor messages have failed on the peer process and the system is no longer operational.","No action is required."
"CPU_MONITOR","3","TIMED_OUT","CPU_MONITOR messages have failed, resetting %s [%d/%d]","The CPU monitor messages failed and the system is no longer operational.","No action is required."
"CPU_MONITOR","6","NOT_HEARD","CPU_MONITOR messages have not been heard for %d seconds [%d/%d]","CPU monitor messages have not been detected for a significant amount of time. [dec] is the number of seconds. A timeout is likely to occur soon, which will reset the system. This error can be caused by a badly seated module or by high traffic in the EOBC channel.","Verify that all modules are seated properly in the chassis. Pull out the module mentioned in the message and inspect the backplane and module for bent pins or hardware damage. If the message persists after reseating all the modules, a hardware problem may exist, such as a defective module or chassis."
"CRYPTO","3","UNAVAILABLE","%s","An IKE initialization error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CRYPTO","3","UNAVAILABLE","Bad %s magic number (%04x).","An internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CRYPTO","3","UNAVAILABLE","Crypto Engine id %d is invalid","The packet has its engine_id set to something otherthan software crypto or hardware crypto.Unable to determine which crypto engine to useThe packet will be default sent to software crypto engine.","No action required"
"CRYPTO","3","UNAVAILABLE","Crypto engine failed to allocate a connection ID for negotiation from %i to %i","The crypto engine has exhausted all available connection IDs or is otherwise malfunctioning.","Decrease the number of concurrent connections or inspect the crypto engine."
"CRYPTO","3","UNAVAILABLE","Crypto policy checksum failure. 	Crypto access list %s, crypto map %s, interface %s","Crypto policy checksum failure has been detected in this router whose traffic is protected by the crypto policy. This event may be caused by memory corruption occuring in crypto policy data, or the memory area has been illegally modified. It may also be caused by software defects. As a result of this event, the router has been forced to reload.","Contact your Cisco support representatives."
"CRYPTO","3","UNAVAILABLE","Cryptographic Token %s ADMIN Login FAILED","The cryptographic token has rejected the administrator PIN offered bythe router","Issue 'crypto pki token admin-pin' command to enter correct PIN"
"CRYPTO","3","UNAVAILABLE","Cryptographic Token %s API FAILED, error = %d","The cryptographic token returned an unexpected error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CRYPTO","3","UNAVAILABLE","Cryptographic Token %s Administrator PIN Locked due to too many unsuccessful login attempts","The cryptographic token has disabled the Admin PIN due to too many login failures","If the user PIN is also locked out, it will be necessary to reinitialize the card.The data on the card will be lost"
"CRYPTO","3","UNAVAILABLE","Cryptographic Token %s Change PIN FAILED","The cryptographic token has rejected the new PIN offered bythe router","Be sure you are logged in to the token as admin. Try a longer PIN."
"CRYPTO","3","UNAVAILABLE","Cryptographic Token %s Login FAILED","The cryptographic token has rejected the PIN offered bythe router","Issue 'crypto pki token user-pin' command to enter correct PIN"
"CRYPTO","3","UNAVAILABLE","Cryptographic Token %s PIN Locked due to too many unsuccessful login attempts","The cryptographic token has disabled the user PIN due to too many login failures","Issue 'crypto pki token admin-pin' command to enter correct ADMINISTRATOR PIN"
"CRYPTO","3","UNAVAILABLE","EZVPN(%s): Virtual-access interface creation failed","The virtual-interface feature will not work without a virtual-access interface. The EzVPN configuration is unusable. You can choose to remove virtual-interface configuration from ezvpn as a workaround","If this message occurs, contact your technical support representative."
"CRYPTO","3","UNAVAILABLE","Generated RSA key failed self test","An automatic test of the newly generated RSA keypair %s failed. That RSA key was automatically deleted.","File a DDTS. As an immediate workaround, attempt to create another pair"
"CRYPTO","3","UNAVAILABLE","IKE failed to create IKE peer tree or leaf node.","IKE failed to allocate memory for the IKE peer tree","More DRAM may be required in order to run the image."
"CRYPTO","3","UNAVAILABLE","Key %s store on Cryptographic Token %s Failed","An error occurred attempting to write a new keypair out to the cryptographic token","Try logging in to the token. If the error persists, try logging in as admin"
"CRYPTO","3","UNAVAILABLE","Mtree command %d was blocked from the the mtree process queue.","An attempt was made to enqueue a command to the crypto mtree manager process even though IPsec is currently operating in HAPX mode.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CRYPTO","3","UNAVAILABLE","Pak spent too much time in the IKE input queues","An incoming IKE packet spent too much time in the IKE input queues. This can happen when the IKE subsystem is under heavy load, due to a lot of peers trying to setup SAs simultaneously, and IKE is not able to handle all the incoming packets, in a timely manner.","It is important to understand why many peers are simultaneously trying to setup SAs at the same time. If possible, try to avoid or minimize such network conditions."
"CRYPTO","3","UNAVAILABLE","Querying key pair failed.","Querying public key/private key using subject name failed","Check the subject name in the certificate."
"CRYPTO","3","UNAVAILABLE","Unable to open %s","The requested operation could not be accomplished because of a low memory condition.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration and restart crypto isakmp process"
"CRYPTO","4","UNAVAILABLE","Please recheck your crypto map %s.","Transform set entry removed from crypto-map as it is no longer validwith hardware crypto engine enabled.","Create and apply valid transform set to cryptomap"
"CRYPTO","4","UNAVAILABLE","Transform %s is not supported with the current hardware configuration. Global transform %s will be deleted.","System configuration modified.Some ipsec transforms which were earliervalid with software crypto are no longer valid now after switchinghardware crypto.","Create valid transform sets & update cryptomaps"
"CRYPTO","4","UNAVAILABLE","%s","The limit for maximum no of ezvpn tunnels that can be setup on the platform, has reached. Active SAs shall not be terminated, but no additional SAs can be established until the number of existing SAs decreases.Error Message    %CRYPTO-4-UNAVAILABLE: %s 	(ip) dest_addr= %i, src_addr= %i, prot= %d 	(ident) local=%i, remote=%i 	 local proxy=%i/%i/%d/%d, 	 remote_proxy=%i/%i/%d/%d Explanation    Decapsulated IPSEC packet not maching negotiated identity The peer is sending other traffic through this SA. It may be due to an SA selection error by the peer. Some might consider this a hostile event.","Contact the peer's administrator to compare policy settings."
"CRYPTO","4","UNAVAILABLE","%s 	connection id=%d, sequence number=%lu","Replay processing failed. This may be a temporary condition due to waiting for new SAs to be established. In the inbound case, this may also be due to an actual replay attack. Some might consider this a hostile event.","If the problem appears to be more than a transient one, contact the peer's administrator."
"CRYPTO","4","UNAVAILABLE","Encryption audit check could not be performed","The audit check verifying encryption entitlement within the IOS image could not be performed due to incompete system configuration.","Manually verify that this IOS image is entitled to contain encryption."
"CRYPTO","4","UNAVAILABLE","IKE active SA count is %lu but SA limit has been set to %lu.","The IKE SA limit that was set is less than the number of active IKE SA. Active SA will not be terminated but no additional IKE SAs can be established unless the limit is increased or the number of active SAs decreases.","Increase the IKE SA limit if necessary to establish connectivity"
"CRYPTO","4","UNAVAILABLE","IKE denied an %s SA request from %s to %s due to %s","Call Admission Control is configured globally or at the IKE level on this device. Consequently an IKE SA request was denied do to the reason described in the error message.","Depending on the reason that the request was denied, either reduce the load on the system so that it can handle new IKE SA requests, or increase the maximum allowed IKE sessions if more are needed."
"CRYPTO","4","UNAVAILABLE","IKE in-negotiation SA count currently is %lu but new limit has been set to %lu.","The IKE in-negotiation SA limit that was set is less than the current number of in-negotiation IKE SA. As of a result of this, no more new IKE SAs can be created. However, those already in negotiation are allowed to finish.","Increase the IKE SA limit if necessary to establish connectivity"
"CRYPTO","4","UNAVAILABLE","IKE message from %s failed its sanity check or is malformed","A quick sanity check is done on all received ISAKMP messages toverify that all component payload types are valid, and that thesum of their individual lengths equals the total length of thereceived message. This message failed the sanity check.Persistantly bad messages could be a denial of service attackor bad decryption.","Contact the remote peer's administrator."
"CRYPTO","4","UNAVAILABLE","IKE message from %s has no SA and is not an initialization offer","IKE maintains state for a communication in the formof security associations. No security association existsfor this packet and it is not an initial offer from the peerto establish one.This situation could denote a denial of service attack.","Contact the remote peer and/or his administrator"
"CRYPTO","4","UNAVAILABLE","INV SPI RECOV LIMIT %d maxed %s %s %s","INVALID SPI RECOVERY SAs maximum limit has been reached.","Possibly the local box reloaded."
"CRYPTO","4","UNAVAILABLE","IPSEC Accounting was unable to send start record","The AAA subsystem was unable to send the accounting starton behalf of IPSec. This could be due to the AAA Server being unreachable.","Ensure that the AAA server is reachable and enabledfor accounting."
"CRYPTO","4","UNAVAILABLE","IPSEC Accounting was unable to send stop record","The AAA subsystem was unable to send the accounting stopon behalf of IPSec. This could be due to the AAA Server being unreachable.","Ensure that the AAA server is reachable and enabledfor accounting."
"CRYPTO","4","UNAVAILABLE","ISAKMP message from %s larger (%ld) than the UDP packet length (%ld)","ISAKMP messages are carried in UDP packets.They have their own message length field. The message length fieldof this message was greater than the length of the UDP packet!This situation could denote a denial of service attack.","Contact the remote peer and/or his administrator"
"CRYPTO","4","UNAVAILABLE","ISAKMP policy rsa-encr not supported by crypto HW accelerator %s","rsa-encr is not supported by Hifn based crypto HW accelerators","Use ISAKMP policy rsa-sig"
"CRYPTO","4","UNAVAILABLE","Invalid encryption method for IKE policy %u","Configured encryption method is not supported","Use any of the valid encryption methods for the ISAKMP policy"
"CRYPTO","4","UNAVAILABLE","RSA keypairs for token %s and associated IPSEC sessions will be deactivated in %d seconds","Router RSA keypairs and associated IPSEC sessionswill be deactivated when the timeout expires","Re-insert the crypto token before the timeout expires"
"CRYPTO","4","UNAVAILABLE","RSA keypairs from token %s and associated IPSEC sessions being deactivated now","Router RSA keypairs and associated IPSEC sessionsare being deactivated because the token containing them was removed","Re-insert the crypto token"
"CRYPTO","4","UNAVAILABLE","Rec'd packet has invalid udp wrapper protocol. 	cryptoflags = %x, sa-udp_wrapper_support = %d,transform = %x","Rec'd packet either udp encapsulated, but is not correct negotiation transform. Or it expected an udp encapsulated packet, but it received a non-udp packet. There may simply be a policy setup error on the peer. Some might consider this a hostile event.","Contact the peer's administrator to compare policy settings."
"CRYPTO","4","UNAVAILABLE","Rec'd packet not an IPSEC packet. (ip) vrf/dest_addr= %s/%i, src_addr= %i, prot= %d","Rec'd packet matched crypto map ACL, but is not IPSEC-encapsulated. IPSEC Peer is sending unencapsulated packets. There may simply be a policy setup error on the peer. Some might consider this a hostile event.","Contact the peer's administrator to compare policy settings."
"CRYPTO","4","UNAVAILABLE","Security warning: crypto ipsec optional is configured","Currently, the router has the CRYPTO IPSEC OPTIONAL ENABLE setting, which allows data which normally would be encrypted to be sent in the clear.","If you did not intend to configure the crypto optional setting, you should reconfigure the box to turn it off"
"CRYPTO","4","UNAVAILABLE","Sum of priority class bandwidth exceeds crypto engine's throughput for small packets (crypto b/w=%u kbps, allocated b/w=%u kbps). Some priority traffic may be dropped.","The crypto engine may be oversubscribed by priorityclass traffic. This happens when the user tries toprovision more priority class bandwidth than what thecrypto engine can handle. If each class is sendingat its max rate, some priority packets may be dropped","Reduce the priority class bandwidth or reducethe number of priority classes in the policy-map"
"CRYPTO","4","UNAVAILABLE","Transform %s not usable with IKE because of IPSec transform %s","Configured encryption algorithm not uable with IKE with current hardware configuration","If you need to negotiate this with IKE, specify a valid encryption algorithm for the ipsec transform"
"CRYPTO","4","UNAVAILABLE","Transform %s not valid under IPSec transform %s","Configured encryption algorithm not supported","Specify a valid encryption algorithm for the ipsec transform"
"CRYPTO","4","UNAVAILABLE","Transform %s will run with reduced performance because of IPSec transform %s","Configured encryption algorithm will not run on the hardware encryption card. The transform is still usable, but will run with reduced performance.","If you need to use the full performance of the encryption card, specify another encryption algorithm for the ipsec transform"
"CRYPTO","4","UNAVAILABLE","Unencrypted traffic %s %i because crypto optional is configured","Cleartext traffic is passing through an interface that is configured for encryption. This traffic is accepted because the router has the CRYPTO IPSEC OPTIONAL ENABLE setting, which allows such traffic.","If you did not intend to configure the crypto optional setting, you should reconfigure the box to turn it off"
"CRYPTO","4","UNAVAILABLE","decaps: rec'd IPSEC packet has invalid spi for 	destaddr=%s, prot=%d, spi=0x%x(%u), srcaddr=%s","Rec'd IPSEC packet specifies SPI that doesn't exist in SADB. This may be a temporary condition due to slight differences in aging of SAs between the IPSEC peers, or it may be because the local SAs have been cleared. It may also be because of bogus packets sent by the IPSEC peer. Some might consider this a hostile event.","If the local SAs have been cleared, the peer may not know this. In this case, if a new connection is established from the local router, the two peers may reestablish successfully. Otherwise if the problem occurs for more than a brief period, either attempt to establish a new connection or contact the peer's administrator."
"CRYPTO","4","UNAVAILABLE","decapsulate: packet has bad %s length destadr=%i, prot=%d, len=%d","Rec'd IPSEC packet is malformed: possibly encapsulation error? The peer is sending malformed packets. It may be due to a decryption error. Some might consider this a hostile event.","Contact the peer's administrator."
"CRYPTO","4","UNAVAILABLE","decapsulate: packet missing %s, destadr=%i, actual prot=%d","Rec'd IPSEC packet missing an expected AH or ESP header The peer is sending packets that don't match the negotiated security policy. Some might consider this a hostile event.","Contact the peer's administrator."
"CRYPTO","4","UNAVAILABLE","decrypt: mac verify failed for connection id=%d","MAC verify processing failed. This may be due to the use of the wrong key by either party during the MAC calculations. Some might consider this a hostile event.","Contact the peer's administrator."
"CRYPTO","4","UNAVAILABLE","encrypted connection attempted with a peer without the configured certificate attributes","An encrypting peer attempted to establish an IPSec session with an interface which it was not authorized for. Some might consider this a hostile event.","Check if the peer should be authorized to connect with the IPSec connection. If he should be allowed, it may be a configuration issue. Otherwise, you should contact the peer's administrator."
"CRYPTO","4","UNAVAILABLE","ipsec check access: identity not allowed by ACL 	(ip) dest_addr= %i, src_addr= %i, prot= %d","After all is said and done, the decaps packet fails the ACL check The peer is sending other traffic through this SA. It may be due to an SA selection error by the peer. Some might consider this a hostile event.","Contact the peer's administrator to compare policy settings."
"CRYPTO","4","UNAVAILABLE","pcp: %d byte packet failed to decompresspcp: dest_addr=%i, src_addr=%i","The received IPPCP packet failed to decompress.This may be due to a decompression buffer error.Error Message    %CRYPTO-4-UNAVAILABLE: pcp: wrong CPI, %x, in packet from %i Explanation    The receive IPPCP packet had an improper CPI.This may be due to use of an old IPPCP security association.CRYPTO-5CRYPTO-5Error Message    %CRYPTO-5-UNAVAILABLE: Certificate received from %s is bad: %s Explanation    The certificate given by remote peer has either been revoked orexpired (certificate invalid) or the signature check on thecertificate failed (bad signature)","Contact the CA of the remote peer. Possibly bad CA certificate."
"CRYPTO","5","UNAVAILABLE","Crypto tunnel is %s. Peer %s:%d %s %s %s %s %s %s %s %s","This is a notification message for IPSEC tunnel status","No action is required"
"CRYPTO","5","UNAVAILABLE","IKE sa's if any, for vip %i will change from %s to %s","This is a notification message for crypto ike sa'schanging their HA status","No action is required"
"CRYPTO","5","UNAVAILABLE","IPSec sa's if any, for vip %i will change from %s to %s","This is a notification message for crypto ipsec sa'schanging their HA status","No action is required"
"CRYPTO","5","UNAVAILABLE","Start registration for group %s using address %s","Start registration for one group","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CRYPTO","5","UNAVAILABLE","Unable to initiate or respond to Aggressive Mode while disabled","The router is configured not to accept or respond to ISAKMP aggressive mode with any peer","If you did not intend to disable aggressive-mode then remove the command"
"CRYPTO","6","UNAVAILABLE","%s","Ezvpn connection is being closed. The IPsec and IKE security associations will also be brought down along with it.Error Message    %CRYPTO-6-UNAVAILABLE: %s Explanation    Ezvpn connection is up for the client mentioned. Both IPsec and IKE security Associations are up now.Error Message    %CRYPTO-6-UNAVAILABLE: %s Explanation    VPN tunnel status.Error Message    %CRYPTO-6-UNAVAILABLE: %s caused early termination of show output%s Explanation    While showing a list, the list was changed or elements changed. This can happen if SA's are re-negotiated at the time the show-command was paused, or if someone reconfigured or cleared SA's, amongst other things. This is not an error, but a side-effect of a dynamic system.","In general, this is merely a warning, that the output from the show command is most likely incomplete. Re-running the show-command should provide the newest information. On a busy system, with ever-changing SA's, this may appear frequently."
"CRYPTO","6","UNAVAILABLE","A pseudo-random number was generated twice in succession","A pseudo-random number generator produced the same number twice in succession.","Under normal circumstances a pseudo-random number generator will occasionally produce the same number twice in succession and this is not a problem. However if this message occurs frequently, the system should be manually reloaded. If the message is persistent across reloads, copy the error message exactly as it appears, and report it to your technical support representative."
"CRYPTO","6","UNAVAILABLE","Authentication method %d failed with host %s","The IKE process was unable to authenticate its securityAssociation with its remote peer.","Contact the remote peer's administrator."
"CRYPTO","6","UNAVAILABLE","CET connection msg in an IPSEC_ONLY_IMAGE","CET has been End-of-lifed in IOS release 12.2(1)Error Message    %CRYPTO-6-UNAVAILABLE: Cannot accept Quick Mode exchange from %s if SA is not authenticated! Explanation    The IKE security association with the remote peer was notauthenticated yet the peer attempted to begin a Quick Modeexchange. This exchange must only be done with an authenticatedsecurity association","Contact remote peer"
"CRYPTO","6","UNAVAILABLE","Certificate for peer at %s prohibits attempted use (%s).","X.509v3 certificates can contain usage restrictions.These can restrict use of the certificate only for signaturesor only for key exchange (encryption). The peer attempted touse his certificate in a manner which violated these restrictions.","Contact the remote peer, and the remote peer's CA"
"CRYPTO","6","UNAVAILABLE","Cryptographic Token %s ADMIN Login Successful","The cryptographic token has accepted the administrator PIN offered bythe router","Informational message only. No action required."
"CRYPTO","6","UNAVAILABLE","Cryptographic Token %s ADMIN PIN change Successful","The cryptographic token has accepted the new administrator PIN offered bythe router","Informational message only. No action required."
"CRYPTO","6","UNAVAILABLE","Cryptographic Token %s Login Successful","The cryptographic token has accepted the PIN offered bythe router","Informational message only. No action required."
"CRYPTO","6","UNAVAILABLE","Cryptographic Token %s Logout Successful","The router has logged out from the cryptographic token","Informational message only. No action required."
"CRYPTO","6","UNAVAILABLE","Cryptographic Token %s PIN change Successful","The cryptographic token has accepted the new PIN offered bythe router","Informational message only. No action required."
"CRYPTO","6","UNAVAILABLE","Cryptographic Token %s re-inserted. removal timeout cancelled","A cryptographic token containing private keyfiles has been re-inserted in time.Router RSA keypairs and associated IPSEC sessionswill be NOT be deactivated","Informational message only. No action required."
"CRYPTO","6","UNAVAILABLE","Cryptographic token %s inserted in %s","A cryptographic token has been detected","Informational message only. No action required."
"CRYPTO","6","UNAVAILABLE","Cryptographic token %s removed from %s","A cryptographic token has been detected","Informational message only. No action required."
"CRYPTO","6","UNAVAILABLE","DOI of %d in notify message from %s","The DOI field in notify messages give the receiver a contextin which to understand the message being notified. This DOIvalue is not understood and the message therefore cannot beunderstood.","If this situation persists contact the remote peer."
"CRYPTO","6","UNAVAILABLE","DOI value %d from SA offer from %s is invalid","The DOI field of an SA offer defines how to parse the fieldsSAs with an unknown DOI cannot be parsed","If this situation persists contact the remote peer's administrator"
"CRYPTO","6","UNAVAILABLE","Generated new %d bit key pair","Auto-Enroll has generated a new router key pair","No action required. Informational message"
"CRYPTO","6","UNAVAILABLE","ID of %s (type %d) and certificate DN with %s","ISAKMP entities assume an identity to inform the peer of who orwhat they are. The claimed identity did not match the informationgleaned from the distinguished name of the peer's certificate.","Contact the remote peer if this situation persists"
"CRYPTO","6","UNAVAILABLE","ID of %s (type %d) and certificate addr with %s","ISAKMP entities assume an identity to inform the peer of who orwhat they are. The claimed identity did not match the informationgleaned from the ip address of the peer's certificate.","Contact the remote peer if this situation persists"
"CRYPTO","6","UNAVAILABLE","ID of %s (type %d) and certificate fqdn with %s","ISAKMP entities assume an identity to inform the peer of who orwhat they are. The claimed identity did not match the informationgleaned from the fqdn of the peer's certificate.","Contact the remote peer if this situation persists"
"CRYPTO","6","UNAVAILABLE","ID of %s (type %d) and certificate user fqdn with %s","ISAKMP entities assume an identity to inform the peer of who orwhat they are. The claimed identity did not match the informationgleaned from the user fqdn of the peer's certificate.","Contact the remote peer if this situation persists"
"CRYPTO","6","UNAVAILABLE","IKE (connection id %d) unable to %s packet","Encryption or decryption on a particular IKE thread failed.","Contact remote peer"
"CRYPTO","6","UNAVAILABLE","IKE SA manually deleted. Do 'clear crypto sa peer %s' to manually clear IPSec SA's covered by this IKE SA.","The IKE SA was deleted by user command. However, keepalives this connection are enabled, and IPSec SA's covered by this IKE SA still exist. Since this IKE SA is now deleted, these IPSec SA's have no IKE SA covering them. The recommended action is to manually delete this IPSec SA's.","Use parser command clear crypto sa to clear IPSec SA's."
"CRYPTO","6","UNAVAILABLE","IKE packet from %s was not encrypted and it should've been.","A portion of the IKE exchange takes place in the clearand a portion is encrypted. This message should have beenencrypted but was not.","Contact remote peer"
"CRYPTO","6","UNAVAILABLE","IKE peer at %s sent a message with unknown exchange %d","IKE preforms actions on messages based on defined exchanges.The message received had an unknown exchange.","Contact the remote peer's administrator"
"CRYPTO","6","UNAVAILABLE","ISAKMP is %s","The ISAKMP process has been switched on or off either by CLI or because no crypto map or EzVPN configuration is applied to any interface.","No action required."
"CRYPTO","6","UNAVAILABLE","Key %s stored on Cryptographic Token %s Successfully","A new keypair has been written out to the cryptographic token","Informational message only. No action required."
"CRYPTO","6","UNAVAILABLE","Processing of %s mode failed with peer at %s","Negotiation with the remote peer failed.","If this situation persists contact the remote peer"
"CRYPTO","6","UNAVAILABLE","Pseudo-random number generator seed and seed key was identical","The X9.17 random number specification requires us to check for the same value appearing as the seed and the seed key. This message indicates that the condition was discovered.","The X9.17 random number will occasionally produce this condition, and this is not a problem. However if this message occurs frequently, the system should be manually reloaded. If the message is persistent across reloads, copy the error message exactly as it appears, and report it to your technical support representative."
"CRYPTO","6","UNAVAILABLE","Received TED reply that did not correspond to a TED probe","Rec'd TED reply that does not match a TED probe we currently have outstanding. This may be a one time occurance due to the TED reply being delayed. It may also be because of ill-formed packets sent by the peer. Some might consider this a hostile event.","If the problem occurs more than once, contact the peer's administrator."
"CRYPTO","6","UNAVAILABLE","Remote peer %s responded with attribute %s not offered or changed","IKE peers negotiate policy by the initiator offering a listof possible, alternate, protection suites. The responderresponded with one that the initiator did not offer","Contact the remote peer"
"CRYPTO","6","UNAVAILABLE","Unable to add public key for %s (%15i) to key ring","Keys are stored in keyrings on the router. An attempt toadd another key to the ring failed.","Check local key rings. This is probably due to other failures."
"CRYPTO_HA","3","IKEADDENTRYFAIL","(VIP=[IP_address])ISAKMP SA entry insertion on standby device failed for src=[IP_address], dst=[IP_address]","An attempt to insert an SA entry transferred from the active device has failed. The SA database is no longer synchronized with that on the active device.","Initiate a manual resynchronization of the ISAKMP SA table."
"CRYPTO_HA","3","IKEDELENTRYFAIL","(VIP=[IP_address])ISAKMP SA entry deletion on standby device failed for src=[IP_address], dst=[IP_address]","An attempt to delete an SA entry that was removed on the active device has failed. The SA database is no longer synchronized with that on the active device.","Initiate a manual resynchronization of the ISAKMP SA table."
"CRYPTO_HA","3","IKEINSERTKEYFAIL","(VIP=[IP_address])ISAKMP SA entry key insertion on standby device failed for src=[IP_address], dst=[IP_address]","An attempt to insert keys for a new SA entry on the standby device has failed. The standby device will not receive this entry.","Initiate a manual resynchronization of the ISAKMP SA table from the standby device."
"CRYPTO_HA","3","IKEQUERYKEYFAIL","(VIP=[IP_address])ISAKMP SA entry key query on active device failed for src=[IP_address], dst=[IP_address]","An attempt to query an SA entry for key information to send to the standby device has failed. The standby device will not receive this entry.","Initiate a manual resynchronization of the ISAKMP SA table from the standby device."
"CRYPTO_HA","3","IPSECADDENTRYFAIL","(VIP=[IP_address])IPSEC SA entry insertion on standby device failed","An attempt to insert an SA entry transferred from the active device has failed. The SA database is no longer synchronized with the database on the active device.","Initiate a manual resynchronization of the IPsec SA table."
"CRYPTO_HA","3","IPSECDELENTRYFAIL","(VIP=[IP_address])IPSEC SA entry deletion on standby device failed","An attempt to delete an SA entry that was removed on the active device has failed. The SA database is no longer synchronized with the database on the active device.","Initiate a manual resynchronization of the IPsec SA table."
"CRYPTO_HA","6","IKEDOWN","(VIP=[IP_address])Disabling High Availability functionality for the ISAKMP failover group.","This is a normal notification message when HA is unconfigured for this failover group, or a tracked interface is shut down. However, it may also be a result of a failure.","If the failover was initiated deliberately (for example, by shutting down a tracked interface), then no action is required. Otherwise, investigate the status of the redundancy protocol (HSRP, for example) that may have lead to the Down state notification to the high availability framework."
"CRYPTO_HA","6","IKEFAILOVER","(VIP=[IP_address])Taking over as the new Active device for the ISAKMP failover group.","This is a normal notification message when an active device is first elected. Alternatively, it is triggered when a failover occurs within the high availability group. In that case, the formerly active device within the ISAKMP failover group has gone down and this device is taking over as the new active device for the group.","If the failover was initiated deliberately (for example, by shutting down a tracked interface), then no action is required. Otherwise, investigate the status of the previous active device to troubleshoot the reason for failure and take appropriate action."
"CRYPTO_HA","6","IKEHAINFINITEMSGLOOP","(VIP=[IP_address])Dropping remainder of this HA IKE SSP message because of suspected infinite message loop.","HA IKE SSP message processing seems to be looping on this message. The processing of this message will be dropped to prevent an infinite loop.","Turning on detailed IKE HA debugs on both HA pairs can help determine what message may be causing this problem."
"CRYPTO_HA","6","IKEHANOTENABLE","IKE HA is not enabled.","IKE HA received a state notification or an SSP message for a VIP that does not have HA enabled.","Verify that IKE stateful failover is configured for the interface with this VIP."
"CRYPTO_HA","6","IKEHASYNCCOMPLETE","(VIP=[IP_address])IKE HA state synchronization with Active device complete.","This is a normal notification message after the standby has received either REPLY_ENTRY or DELETE_ENTRY messages for all requests during synchroniztion.","No action is required."
"CRYPTO_HA","6","IKESTANDBY","(VIP=[IP_address])Setting up as a Standby device for the ISAKMP failover group.","This is a normal notification message after a standby device comes up.","No action is required."
"CRYPTO_HA","6","IKEUPDATEENTRYFAIL","(VIP=[IP_address])ISAKMP SA entry update on standby device failed for src=[IP_address], dst=[IP_address]","An attempt to update an SA entry as specified by the active device has failed. The SA entry will be missing the latest packet level update until another update entry is sent by the active device.","Normally, a subsequent update entry message will self-correct the problem. Manual resynchronization of the ISAKMP SA table by the standby device may be necessary if this message appears repeatedly."
"CRYPTO_HA","6","IPSECDOWN","(VIP=[IP_address])Disabling High Availability functionality for the IPSEC failover group.","This is a normal notification message when HA is unconfigured for this failover group, or a tracked interface is shut down. However, it may also be a result of a failure.","If the failover was initiated deliberately (for example, by shutting down a tracked interface), then no action is required. Otherwise, investigate the status of the redundancy protocol (HSRP, for example) that may have lead to the Down state notification to the high availability framework."
"CRYPTO_HA","6","IPSECFAILOVER","(VIP=[IP_address])Taking over as the new Active device for the IPSEC failover group.","This is a normal message when a device first becomes active, or when failover occurs within the high availability group. In the failover case, the former active device within the IPsec failover group has gone down and this device is taking over as the new active device for the group.","If the failover was initiated deliberately (for example, by shutting down a tracked interface), then no action is required. Otherwise, investigate the status of the previous active device to troubleshoot the reason for failure and take appropriate action."
"CRYPTO_HA","6","IPSECHAMAXINSERTERRORS","IPsec HA has failed inserting SAs for the last [int] seconds, the box is either out of resources or has suffered a hardware failure","The device is normally out of resources for short periods of time, and retries will automatically occur. In this case, however, the retries have not succeeded and have stopped. Action is required from the administrator.","Verify that both devices in the HA pair are identical and that the hardware is working properly."
"CRYPTO_HA","6","IPSECHANOTENABLE","(VIP=[IP_address])IPSEC HA is not enabled.","IPsec HA received a state notification or an SSP message for a VIP that does not have HA enabled.","Verify that IPsec stateful failover is configured for the interface with this VIP."
"CRYPTO_HA","6","IPSECHASYNCCOMPLETE","(VIP=[IP_address])IPSEC HA state synchronization with Active device complete.","This is a normal notification message after the standby has received either a REPLY_ENTRY or a DELETE_ENTRY message for all requests during synchroniztion.","No action is required."
"CRYPTO_HA","6","IPSECSTANDBY","(VIP=[IP_address])Setting up as a Standby device for the IPSEC failover group.","This is a normal notification message when a standby device comes up.","No action is required."
"CRYPTO_HA","6","IPSECUPDATEENTRYFAIL","(VIP=[IP_address])IPSEC SA entry update on standby device failed","An attempt to update an IPsec SA entry as specified by the active device failed. The SA entry will be missing the latest packet level update, until another update entry is sent by the active device.","Normally, a subsequent update entry message will self-correct the problem. Manual resynchronization of the IPsec SA table by the standby device may be necessary, if this message appears repeatedly."
"CRYPTO_HA_IKE","3","FAILOVER_ERROR","Attempt to failover IKE SA ([IP_address]:[IP_address]) failed due to [chars]. No stateful failover available for this SA.","The HA active device attempted to checkpoint the state of an IKE SA to the standby device, but the standby device was unable to create the standby IKE SA.","Search for other error messages at WARNING log level or turn on debugging messages to find the specific cause of the failure."
"CRYPTO_HA_IKE","4","CRYPTO_HA_NOT_SUPPORTED_BY_HW","Crypto hardware is enabled and it does not support HA operation '[chars]'","Crypto hardware is enabled, but the hardware does not support HA operations such as insertion and extraction of keys.","Replace the crypto module with one that supports HA operations, or disable the hardware and use the software crypto engine."
"CRYPTO_RSA_ISSU","3","GET_BUFFER","Crypto RSA ISSU client failed to get buffer for message. Error: %d (%s)","The crypto RSA ISSU client was unable to obtain a buffer for building a negotiation message. As a result, the client cannot send the negotiation message to the standby unit and the standby unit cannot be brought up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show checkpoint client commands and your pertinent troubleshooting logs."
"CRYPTO_RSA_ISSU","3","INIT","Crypto RSA ISSU client initialization failed to %s. Error: %d (%s)","The crypto RSA ISSU client could not be initialized. This condition will cause a catastrophic failure when an ISSU upgrade or downgrade is performed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CRYPTO_RSA_ISSU","3","INVALID_SESSION","Crypto RSA ISSU client does not have a valid registered session.","The crypto RSA ISSU client does not have a valid registered session. This condition will prevent the standby unit from coming up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"CRYPTO_RSA_ISSU","3","MSG_NOT_OK","Crypto RSA ISSU client message type %d is not compatible","The crypto RSA ISSU client received an incompatible message from the peer unit. Because the message is not compatible, it cannot be processed by this unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"CRYPTO_RSA_ISSU","3","MSG_SIZE","Crypto RSA ISSU client failed to get the MTU for message type %d. Error: %d (%s)","The crypto RSA ISSU client was unable to calculate the MTU for the message specified. The 802.1X ISSU client will be unable to send the message to the standby unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"CRYPTO_RSA_ISSU","3","SEND_NEGO_FAILED","Crypto RSA ISSU client failed to send negotiation message. Error: %d (%s)","The crypto RSA ISSU client failed to send a session negotiation message to the peer. This condition will prevent the standby unit from coming up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"CRYPTO_RSA_ISSU","3","SESSION_NEGO","Crypto RSA ISSU client encountered unexpected client nego_done. Error: %d (%s)","The crypto RSA ISSU client encountered an unexpected 'client negotiation done'. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"CRYPTO_RSA_ISSU","3","SESSION_REGISTRY","Crypto RSA ISSU client failed to register session information. Error: %d (%s)","The crypto RSA ISSU client failed to register session information. This condition will prevent the standby unit from coming up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"CRYPTO_RSA_ISSU","3","SESSION_UNREGISTRY","Crypto RSA ISSU client failed to unregister session information. Error: %d (%s)","The crypto RSA ISSU client failed to unregister session information.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"CRYPTO_RSA_ISSU","3","TRANSFORM_FAIL","Crypto RSA ISSU client %s transform failed for message type %d. Error: %d (%s)","The crypto RSA ISSU client could not transform the message. If the transmit transformation failed, the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, the checkpoint message cannot be applied on the standby unit. In either case, the crypto RSA state will not match with the active unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"CSG","3","ERROR","Module [dec]: [chars]","An error occurred in a CSG module.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CSG","3","RELOADNOTOK","CSG ACCOUNTING [chars] reload on module [dec] failed.","This informational message appears whenever a CSG configuration is reloaded as a result of power cycling a CSG card.","This is an informational message only. No action is required."
"CSG","4","WARNING","Module [dec]: [chars]","An undesired event has occurred in a CSG module.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CSG","6","LIRELOADOK","CSG LI reload on module [dec] successful","The CSG lawful intercept (LI) configuration was reloaded because of the power cycling of a CSG module.","No action is required."
"CSG","6","RELOADOK","CSG ACCOUNTING [chars] reload on module [dec] successful","This informational message appears whenever a CSG configuration is reloaded as a result of power cycling a CSG card.","This is an informational message only. No action is required."
"CSM_SLB","4","ENV_VARIABLE","Module %d warning: %s %s","There is a mismatch between the configuration and the specified environment variable.","Check the documentation for any caveats regarding the use of the specified environment variable."
"CT3","3","CT3NOACC","[chars] - Accumulator is not available","An invalid TX accumulator is detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CT3","3","MBOXRECV","Failed to receive reply [dec] from bay [dec] firmware","A message was not received from CT3 firmware.","Copy the error message exactly as it appears, collect the output of the show tech-support command immediately, and report it to your technical support representative. If possible, try to do an OIR (Online Insertion and Removal). Please refer to the Cisco documentation for information on 'Online Insertion and Removal' for your platform"
"CARRIER","2","TOOMANY_CT3","Too many CT3 DFC cards, do not power up invalid card in slot [dec]","The user has put too many CT3 DFC cards in the chassis.","Remove the extra CT3 DFC card, or 8PRI DFC card causing the problem."
"CTS","0","AUTHZ_OUT_OF_MEM","%s failed to create %s due to insufficient memory","A Cisco TrustSec (CTS) process failed due to insufficient system memory.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","0","CTS_EMERG","[chars]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","0","IFC_OUT_OF_MEM","%s failed to create %s due to insufficient memory","A Cisco TrustSec (CTS) process failed due to insufficient system memory.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","1","CTS_ALERT","[chars]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","2","CTS_CRIT","[chars]","An internal software error occurred.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"CTS","3","AUTHZ_ADD_DATA_FAILED","%s failed to add %s to %s","An error occurred while the Cisco TrustSec (CTS) authorization attempted to build its database.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","AUTHZ_DATA_CREATE_FAILED","%s failed to create %s","Cisco TrustSec (CTS) authorization was unable to create an internal data structure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","AUTHZ_DATA_EXCEEDS_LIMIT","%s encountered %s(%d) exceeds max(%d)","Cisco TrustSec (CTS) authorization data exceeded the maximum allowed limit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","AUTHZ_DATA_FAILED","%s failed to obtain %s","Cisco TrustSec (CTS) authorization was unable to get or create a data structure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","AUTHZ_DATA_NULL","%s encounters NULL %s","Cisco TrustSec (CTS) authorization encountered an unexpected NULL pointer or data.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","AUTHZ_DATA_UNINIT","%s appears uninitialized","Cisco TrustSec (CTS) authorization unexpectedly encountered uninitialized data.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","AUTHZ_FAILED_SYNC_RCV","Standby failed receive sync msg(%s)","An error occurred while the standby unit was receiving synchronization data from the active unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","AUTHZ_GENERIC_FAILURE","%s %s","Cisco TrustSec (CTS) authorization encountered an internal error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","AUTHZ_INSTALL_FAILED","%s failed to install %s %s","An error occurred while Cisco TrustSec (CTS) authorization attempted to build its database.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","AUTHZ_INVALID_DATA","%s encountered invalid %s","Cisco TrustSec (CTS) authorization encountered an invalid data type.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","AUTHZ_NOT_SUPPORTED","%s encountered %s not unsupported","Cisco TrustSec (CTS) authorization encountered an unsupported data type or feature, possibly due to incompatibility.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","AUTHZ_POLICY_FALLBACK_FAILED","Failed to %s Fallback policy for %s","Cisco TrustSec (CTS) was unable to install a fallback authorization policy.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","AUTHZ_POLICY_INGRESS_FAILED","Failed to %s Ingress policy for %s","Cisco TrustSec (CTS) was unable to acquire or install an ingress policy from the access control server.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","AUTHZ_POLICY_INTERNAL_FAILED","Failed to acquire/install policy for %s due to internal error","Cisco TrustSec (CTS) was unable to acquire or install a policy due to an internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","AUTHZ_POLICY_PEER_DOWNLOAD_FAILED","Failed to download peer policy for %s","Cisco TrustSec (CTS) was unable to acquire a peer policy from the access control server.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","AUTHZ_POLICY_RBACL_FAILED","Failed to %s RBACL %s for SGT=%d","Cisco TrustSec (CTS) was unable to acquire a role-based access control list (RBACL) policy from the access control server.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","AUTHZ_POLICY_WILDCARD_FAILED","Failed to download wildcard policy","Cisco TrustSec (CTS) was unable to acquire a wildcard policy from the access control server.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","AUTHZ_SYNC_FAILED","Failed to send %s sync msg(%s) to Standby","An error occurred while Cisco TrustSec (CTS) authorization was performing a synchronization of the standby unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","CTS_ERR","[chars]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","DOT1X_CONFIG_FAILED","Failed to configure dot1x for int(%s)","Cisco TrustSec (CTS) was unable to configure 802.1X for a CTS link.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","DOT1X_FORCE_PORT_AUTHORIZED_FAILED","Failed to force dot1x port authorized for int(%s)","Cisco TrustSec (CTS) authorization was unable to FORCE AUTHORIZED an 802.1X port on a CTS link.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","DOT1X_INIT_FAILED","Failed to initialize dot1x for int(%s)","Cisco TrustSec (CTS) was unable to initialize 802.1X for a CTS link.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","DOT1X_PAE_FAILED","Failed to %s dot1x PAE(%s) for int(%s)","Cisco TrustSec (CTS) was unable to start or stop an 802.1X Port Access Entity (PAE) for a CTS link.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","GENERIC_FAILURE","%s %s","Cisco TrustSec (CTS) encountered an internal error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","GLOBAL_DOT1X_DISABLED","Global dot1x config is currently disabled - CTS will not run","Because global 802.1X is not enabled, Cisco TrustSec (CTS) will not run.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","IFC_DATA_DESC_DECODE_FAILED","%s failed to decode the data-descriptori - swidb unknown","Cisco TrustSec (CTS) was unable to decode the data descriptor in order to obtain the software interface descriptor block (SWIDB).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","IFC_DATA_DESC_ENCODE_FAILED","%s failed to encode the data-descriptor for int(%s)","Cisco TrustSec (CTS) was unable to encode the software interface descriptor block (SWIDB) into the data descriptor.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","IFC_DATA_NULL","%s encounters NULL %s","Cisco TrustSec (CTS) encountered an unexpected NULL pointer or data.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","IFC_LINK_OBJ_FAILED","%s failed to get link_obj for int(%s)","Cisco TrustSec (CTS) IFC was unable to access the link object.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","IFC_SYNC_FAILED","Failed to send %s sync msg(%s) to Standby","An error occurred while Cisco TrustSec (CTS) IFC was performing a synchronization of the standby unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","IFC_SYNC_FAILED_2","%s, Failed to send %s sync msg(%s) to Standby","An error occurred while Cisco TrustSec (CTS) IFC was performing a synchronization of the standby unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","INVALID_MSGID_RCV","%s received invalid HA/ISSU msgId(%d)","Cisco TrustSec (CTS) encountered an unexpected invalid HA/ISSU message ID.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","PORT_AUTHORIZED_FAILED","Failed to authorize Port for int(%s)","A port could not be authorized on a Cisco TrustSec (CTS) link.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","PP_CTS_EC_NOT_CTS","Physical port is not configured for CTS, but port-channel is.","A physical port cannot join the channel group (port channel) because its Cisco TrustSec (CTS) configuration does not match the channel group's CTS configuration.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","PP_CTS_MODE_EC_MISMATCH","Physical port CTS mode does not match the port-channel's CTS mode.","A physical port cannot join the port channel because its Cisco TrustSec (CTS) mode does not match the port channel's CTS mode.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","PP_CTS_TIMER_REAUTH_EC_MISMATCH","Cannot bundle interface. CTS Reauth Timer mismatch. %s = %d %s = %d","A physical port cannot join the port channel because its Cisco TrustSec (CTS) reauthentication timer value does not match the port channel's timer value.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","PP_NOT_CTS_EC_CTS","Physical port is configured for CTS, but port-channel is not.","A physical port cannot join the channel group (port channel) because its Cisco TrustSec (CTS) configuration does not match the channel group's CTS configuration.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","SEND_MSG_TO_CORE_FAILED","Failed to send msg([dec]) to core process","An error occcured while CTS attempts to to send a message event to the core process","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","SXP_BINDING_ERR","Binding [chars]- [chars]","SXP binding update error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","SXP_CONN_STATE_CHG_OFF","Connection [chars]-[dec] state changed from [chars] to Off.","SXP Connection with the specified instance number changed state.","No action is required."
"CTS","3","SXP_LISTENER","Fail to start global listening socket after TCP process restart.","The Security Exchange Protocol (SXP) process could not start after a restart.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","3","SXP_MSG_PARSE","Connection [chars] [chars]","An error occurred while parsing SXP message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","4","CTS_WARNING","[chars]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","4","SXP_INTERNAL","CTS SXP [chars]","The CTS SXP system encountered internal failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","5","CTS_NOTICE","[chars]","Normal but significant conditions","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","5","SXP_BINDING_ADD","Binding [chars]- added to SXP database.","Binding added to the SXP database.","No action is required."
"CTS","5","SXP_BINDING_CHG","Binding [chars]- changed: old connection instance number:[dec], old sgt:[dec].","Binding changed in the SXP database.","No action is required."
"CTS","5","SXP_BINDING_DEL","Binding [chars]- deleted in SXP database.","Binding deleted in the SXP database.","No action is required."
"CTS","5","SXP_BINDING_FWD","Binding [chars]- is forwarded to the peer.","SXP forwarded binding to the peer.","No action is required."
"CTS","5","SXP_BINDING_REQ","SXP received binding forwarding request ([chars]) binding [chars].","SXP received a binding forwarding request.","No action is required."
"CTS","5","SXP_BINDING_UPD","Binding [chars] [chars]. Update binding manager.","SXP updated binding manager with the binding change.","No action is required."
"CTS","5","SXP_DFT_PASSWORD_CHANGE","CTS SXP password changed.","The SXP system password has been changed.","No action is required."
"CTS","5","SXP_DFT_SRCIP_CHG","SXP default source IP is changed [IP_address] -- [IP_address].","SXP default source IP is changed on this device.","No action is required."
"CTS","5","SXP_STATE_CHANGE","CTS SXP [char].The SXP feature has changed operational state.","SXP feature is functioning only when the feature is enabled.","No action is required."
"CTS","5","SXP_VRF_DEL","SXP Connection  configuration in VRF:[chars] is removed.","A VRF is removed, the connections configured in this VRF should be removed.","No action is required."
"CTS_HA_ISSU","3","CAP_INVALID_SIZE","CTS HA empty tlv size.","Received empty tlv list during capability negotiation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS","6","DOT1X_FORCE_PORT_AUTHORIZED_SUCCESS","Successfully forced dot1x port authorized for int(%s)","Cisco TrustSec (CTS) authorization caused FORCE AUTHORIZED on an 802.1X port on a CTS link.","No action is required."
"CTS","6","DOT1X_PAE_CONFIG","%s dot1x PAE(%s) for int(%s)","The specified interface has been configured to be an 802.1X Port Access Entity (PAE).","No action is required."
"CTS","6","IFC_CACHE_APPLIED","Cache data applied for int(%s)","The Cisco TrustSec (CTS) link was brought up using cache data.","No action is required."
"CTS","6","CTS_INFO","[chars]","Informational messages","No action is required."
"CTS","6","PORT_AUTHORIZED_SUCCESS","Port authorized for int(%s)","A port was authorized on a Cisco TrustSec (CTS) link.","No action is required."
"CTS","6","PORT_UNAUTHORIZED","Port unauthorized for int(%s)","A port has become unauthorized on a Cisco TrustSec (CTS) link.","No action is required."
"CTS","6","SXP_CONFIG","Connection [chars] [chars]","A SXP configuration error occurred. The connection can not be setup correctly.","Ensure that the connection configure on both ends have the matched mode, IP addresses."
"CTS","6","SXP_CONN_STATE_CHG","Connection [chars]-[dec] state changed from [chars] to [chars].","SXP Connection with the specified instance number changed state.","No action is required."
"CTS","6","SXP_SRC_IP","Source IP address ([chars] [IP_address]) does not belong to this device.","An error occurred while using this source IP address to set up SXP connection.","Re-configure SXP connection to have a valid source IP address."
"CTS","6","SXP_TIMER_START","Connection [chars] [chars] timer started.","The specified SXP timer started.","No action is required."
"CTS","6","SXP_TIMER_STOP","Connection [chars] [chars] timer stopped.","The specified SXP timer stopped.","No action is required."
"CTS","7","CTS_ASSERT","Assertion Failure ( [chars] @[chars]:[dec] ) : [chars]","An internal software error occurred.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"CTS_HA","3","CHKPT_REG_FAIL","CTS HA add CTS checkpoint client failure","The Cisco TrustSec (CTS) high availability (HA) process failed to add a checkpoint client. No CTS data will be synchronized with the standby device.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS_HA","3","RECEIVE_FAILED","CTS HA client failed to process message recieved from Active device.","The Cisco TrustSec (CTS) high availability (HA) client on the standby device failed to process a checkpoint message from the active device. The CTS state between the active device and the standby device is not identical.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS_HA","3","SEND_FAILED","CTS HA client on Active device failed to send checkpoint message. CTS component Id %d, message Id %d","The Cisco TrustSec (CTS) high availability (HA) client on the active device failed to send a checkpoint message to the standby device. The CTS state between the active device and the standby device is not identical.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS_HA_ISSU","3","CAP_INVALID_SIZE","CTS HA empty tlv size.","Received empty tlv list during capability negotiation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS_HA_ISSU","3","CAP_NOT_COMPATIBLE","CTS HA capability not compatible","CTS HA failed during capability negotiation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS_HA_ISSU","3","GET_BUFFER","CTS HA ISSU client failed to get buffer for message. Error: %d (%s)","The Cisco TrustSec (CTS) high availability (HA) ISSU client failed to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"CTS_HA_ISSU","3","INIT","CTS HA ISSU client initialization failed to %s. Error: %d (%s)","The Cisco TrustSec (CTS) high availability (HA) ISSU client could not be initialized. This initialization failure must be addressed before an in-service software upgrade or downgrade can be performed successfully. Otherwise, a software upgrade or downgrade will result in downtime.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS_HA_ISSU","3","MSG_NOT_COMPATIBLE_WITH_PEER","Message [dec] in component [dec] is not compatible with the peer.","Message not compatible with the peer.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CTS_HA_ISSU","3","SEND_NEGO_FAILED","CTS HA ISSU client failed to send negotiation message. Error: %d (%s)","The Cisco TrustSec (CTS) high availability (HA) ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"CTS_HA_ISSU","3","SESSION_REGISTRY","CTS HA ISSU client failed to register session information. Error: %d (%s)","The Cisco TrustSec (CTS) high availability (HA) ISSU client failed to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"CTS_HA_ISSU","3","SESSION_UNREGISTRY","CTS HA ISSU client failed to unregister session information. Error: %d (%s)","The Cisco TrustSec (CTS) high availability (HA) ISSU client failed to unregister session information.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"CTS_HA_ISSU","6","INCOMPAT","CTS HA ISSU client negotiation results incompatible","The Cisco TrustSec (CTS) high availability (HA) ISSU client message version is not compatible on the active and standby devices. As a result, no CTS data will be synchronized to the standby device.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"CWAN_ALARM","6","INFO","[chars] [chars] [chars] [chars] [chars]","This message provides alarm assertion or deassertion information.","This is an informational message only. No action is required."
"CWAN_ALARM","6","SONET","[chars] [chars] [chars] [chars] [chars]","This message is generated whenever an alarm is present in the system (and the alarm status has been reported to the RP) or an alarm has been removed from the system (and the alarm status has been reported to the RP .","This is an informational message only. No action is required."
"CTS","6","SXP_PASSWORD_CHANGE","CTS SXP password changed","The Cisco TrustSec (CTS) Security Exchange Protocol (SXP) system password has been changed.","No action is required."
"CTS","6","SXP_STATE_CHANGE","CTS SXP %s","The Cisco TrustSec (CTS) Security Exchange Protocol (SXP) system component has changed its operational state.","No action is required."
"CWAN_ATM","3","LOWMEM","Could not allocate memory for RFC 1483 packet cloning.","Memory is running low.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"CWAN_ATM","3","PORT_ERR","Invalid PORT [dec]","The specified port does not exist.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_ATM","3","VCD_ERR","Invalid PortVCD [hex]","The specified port VCD does not exist.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_ATM","3","VC_ERR","Invalid VC [hex]","The specified VC does not exist on the port.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_ATM","3","VC_OR_PORT_ERR","Invalid VCD [hex] or Port: [dec]","Either the port or the VCD is invalid.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_ATM","5","UNKNOWN_VCD","Unknown port vcd [hex] in egress packet","An unknown VCD has been received in the egress path of the module. This condition is most likely a transient condition, and it is usually caused by VCs that are being disassembled and reassembled while traffic is being passed.","No action is required."
"CWAN_ATOM_HA","2","ISSU_ERROR","[chars] [chars]","Platform ATOM HA ISSU client error.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"CWAN_ATOM_HA","3","CF_ERROR","[chars] [dec]","Platform ATOM HA CF client error.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"CWAN_ATOM_HA","3","RF_ERROR","[chars] [dec]","Platform ATOM HA RF client error.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"CWAN_CHOC","4","CORRUPT","[chars] information seems to be corrupted, bad value =[int]","Incorrect parameters were detected internally.","This is only a debug warning message. The unexpected value is discarded."
"CWAN_CHOC_DSX","3","NODESTROYSUBBLOCK","The [chars] subblock named [chars] was not removed","A software error occurred. This message displays when IDB subblocks cannot be removed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_CT3","4","CORRUPT","[chars] information seems to be corrupted, bad value =[int]","Incorrect parameters were detected internally.","This is only a debug warning message. The unexpected value is discarded."
"CWAN_FWD_TABLES","3","CHUNK_CREATE_FAIL","[chars]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_FWD_TABLES","3","CHUNK_DESTROY_FAIL","[chars]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_FWD_TABLES","3","CHUNK_MALLOC_FAIL","[chars]","There is a problem with internal software coding. This message should not appear under normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_FWD_TABLES","3","ENTRY_BUILD_FAIL","[chars] [int]","There is a problem with internal software coding. This message should not appear under normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_FWD_TABLES","3","INVALID_DEST_INFO","[chars] [hex] [hex] [hex]","There is a problem with internal software coding. This message should not appear under normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_FWD_TABLES","3","INVALID_INDEX","[chars] [int]","There is a problem with internal software coding. This message should not appear under normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_FWD_TABLES","3","INVALID_OPR_TYPE","[chars] [dec]","There is a problem with internal software coding. This message should not appear under normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_FWD_TABLES","3","MALLOC_FAILED","[chars]","There is a problem with internal software coding. This message should not appear under normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_FWD_TABLES","3","TABLE_ERROR","[chars]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_HA","2","CCB_PLAYBACK_ERROR","CCB playback failed for slot [dec].","The high availability component for WAN modules failed to synchronize new state information for the specified slot.","Reload the redundant supervisor engine to force a fresh bulk synchronization. If this error recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. Examine both the active supervisor engine and the redundant supervisor engine for messages."
"CWAN_HA","2","CCB_RECORD_ERROR","CCB record failed for slot [dec].","The high availability component for WAN modules failed to record new state information for the specified slot. The system is falling back to RPR mode for high availability.","Examine both the active supervisor engine and the redundant supervisor engine for messages. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_HA","2","IFCFG_PLAYBACK_ERROR","Interface Configuration command [int] playback failed for slot [int]/[int].","The high availability component for WAN modules failed to synchronize new state information for the specified slot. The redundant system is no longer synchronized with the active system. The redundant supervisor engine was reloaded shortly after this error was encountered.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_HA","2","IFCFG_RECORD_ERROR","Interface Configuration command [int] record failed for slot [int]/[int].","The high availability component for WAN modules failed to record some new state information for the specified slot. The system is falling back to RPR mode for high availability.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_HA","3","CCB_INIT_ERROR","Failed to initialize CCB list for slot [dec].","The high availability component for WAN modules failed to properly initialize state information for the specified slot. The system is falling back to RPR mode for high availability.","Examine both the active supervisor engine and the redundant supervisor engine for messages. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_HA","3","IFCFG_CMD_NOT_UNIQUE","More than one command registered for unique-key generator for interface configuration command [int].","The high availability component for WAN modules is unable to properly synchronize state information for the current configuration due to a conflict in command identifiers.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_HA","3","IFCFG_INIT_ERROR","Failed to initialize Interface Configuration list for slot [int]/[int].","The high availability component for WAN modules failed to properly initialize state information for the specified slot. The system is falling back to RPR mode for high availability.","Examine both the active supervisor engine and the redundant supervisor engine for messages. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. Examine both the active supervisor engine and the redundant supervisor engine for messages."
"CWAN_HA","3","IFCFG_NO_UNIQUE_KEY","No unique-key generator registered for interface configuration command [int].","The high availability component for WAN modules is unable to properly synchronize state information for the current configuration. The system is falling back to RPR mode for high availability.","Examine both the active supervisor engine and the redundant supervisor engine for messages. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_HA","4","CCB_PLAYBACK_ERROR","CCB playback failed for slot [dec].","The high availability component for WAN modules failed to synchronize some new state information for the specified slot.","Reload the standby supervisor engine to force a fresh bulk synchronization. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_HA","4","CCB_RECORD_ERROR","CCB record failed for slot [dec].","The high availability component for WAN modules failed to record some new state information for the specified slot.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_HA","4","IFCFG_DFLT_LIST_ERROR","For Interface Configuration command %u, default retval list search resulted 0x%x for slot %u/%u","The high availability (HA) component for WAN modules failed to synchronize new state information for the specified slot.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show platform redundancy if-config default-retvals commands and your pertinent troubleshooting logs."
"CWAN_HA","4","IFCFG_PLAYBACK_ERROR","Interface Configuration command [int] playback failed for slot [int]/[int].","The high availability component for WAN modules failed to synchronize some new state information for the specified slot.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information."
"CWAN_HA","4","IFCFG_RECORD_ERROR","Interface Configuration command [int] record failed for slot [int]/[int].","The high availability component for WAN modules failed to record some new state information for the specified slot.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_HA","4","LTLSYNCFAIL","Failed to sync LTL data during [chars] for [chars] [int]: (slot=[dec],slotunit=[dec],if_num=[dec]) to standby (vlan=[int],hash=[int],ltl=[int])","Some local target logic (LTL) data did not synchronize correctly from the active to the standby RP.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_HA","4","NOSRPBULKSYNC","Failed to [chars] srp bulk data (slot=[dec], intf=[dec], type=[dec]), ret code [dec]","The synchronization of RP bulk data and SRP bulk data failed from the active supervisor engine to the redundant supervisor engine.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_HA","4","NOSRPSYNC","Failed to sync srp packet (slot=[dec],intf=[dec]) to standby, HA_SYNC_STATUS=[dec]","The RP dynamic synchronization of SRP packets failed from the active supervisor engine to the redundant supervisor engine.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_HA","4","SRPSYNC","Slot [dec]: [chars]","The specified error occurred while synchronizing the SRP states from the active supervisor engine RP to the redundant supervisor engine RP.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_HAL","3","CHUNK_CREATE_FAIL","[chars]","There is a problem with internal software coding. This message should not appear under normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_HAL","3","CHUNK_MALLOC_FAIL","[chars]","There is a problem with internal software coding. This message should not appear under normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_HAL","3","DELETION_FAILED","[chars]","There is a problem with internal software coding. This message should not appear under normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_HAL","3","FILL_OCE_INFO_FAIL","[chars]","There is a problem with internal software coding. This message should not appear under normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_HAL","3","ILLEGAL_DEAGG_PROT_TYPE","[chars]","There is a problem with internal software coding. This message should not appear under normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_HAL","3","ILLEGAL_OBJ_TYPE","[chars] [chars]","There is a problem with internal software coding. This message should not appear under normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_HAL","3","INSERTION_OR_UPDATION_FAILED","[chars]","There is a problem with internal software coding. This message should not appear under normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_HAL","3","LABEL_SPACE_INCONSISTENT","[chars] [chars]","There is a problem with internal software coding. This message should not appear under normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_HAL","3","NULL_OBJ_HANDLE","[chars]","There is a problem with internal software coding. This message should not appear under normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_HAL","3","NULL_PLT_SPACE","[chars]","There is a problem with internal software coding. This message should not appear under normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_HAL","3","TABLE_CREATION_FAILED","[chars] [chars]","There is a problem with internal software coding. This message should not appear under normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_HAL","3","TABLE_DELETION_FAILED","[chars] [chars]","There is a problem with internal software coding. This message should not appear under normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_HAL","4","UN_SUPPORTED_CONFIG","%s","The configuration of the WAN module is not supported. A common cause is configuring TE on a GRE tunnel.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_IFMGR","4","CREATEFAIL","IM Driver Creation Failed: Interface [dec]/[dec]: [chars]","Driver failed to create an interface with the interface manager.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"CWAN_IFMGR","4","DESTROYFAIL","IM Driver Destroy Failed: Interface [dec]/[dec]: [chars]","Driver failed to destroy the interface with the interface manager.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"CWAN_IFMGR","4","REGISTERFAIL","IM Registration Failed: [chars]","Driver failed to register with the interface manager.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"CWANLC","3","FPD_INCOMPATIBLE","FPD ID=[int] image in this FPD package is for revision [int].x boards. It is incompatible with current board revision of [int].[int]","This FPD package does not contain images that are compatible with the current line card revision.","Perform the FPD upgrade operation with a newer version of an FPD image package that is compatible with the Cisco IOS software that is operating on the switch. Consult with the FPD image package section of the Cisco IOS software release note to confirm that your line card revision is supported for a particular release."
"CWANLC","3","CWANLC_EARL_VERSION_NOTICE","CWAN receives mismatch Earl version notification. New Earl[int] vs Earl[int]","The RP determined through an SCP find operation that the version of the EARL switching engine on the module has changed. This message occurs during a switchover operation. The version of the EARL switching engine is specified in the message text.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWANLC","3","FATAL","[chars]","The OSM encountered a fatal error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWANLC","3","FPD_INCOMPATIBLE","FPD ID=[int] image in this FPD package is for revision [int].x boards. It is incompatible with current board revision of [int].[int]","This FPD package does not contain images that are compatible with the current board revision.","Perform the FPD upgrade operation with a newer version of the FPD image package that is compatible with the running Cisco IOS software. Consult with the FPD image package section of the Cisco IOS software release note to confirm if your board revision is supported for a particular release."
"CWANLC","3","IPCPORT","Failed to %s IPC port '%s', error %s","The line card failed to create a port for communication with the route processor.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWANLC","3","LTL_NOPPEPORTMAP","Failed to retrieve default port mapping for packet processor [int]","The line card software initialization was not completed correctly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWANLC","3","TVPN_NOMEM","Failed to start vpn, not enough memory","The OSM could not start VPN due to insufficient memory.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWANLC","5","NOSCPPING","Linecard has not sent SCP PING responses for too long","The SCP ping mechanism is used by the RP and SP processors to monitor whether the line card that is executing Cisco IOS is in a healthy state. This SCP ping response has not been sent by the line card for a long time; the line card has exported its context information to the RP and may be power cycled. The exported context is available in the output of the show diag command.","Save the show diag command output and contact your Cisco technical support representative if the line card is reset."
"CWANLC_ATM","3","NOVPSPACE","[chars]: out of VP space for VPI [dec]","Out of virtual paths (VPs) on the segmentation and reassembly (SAR) engine.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWANLC_ATM","3","VCCLOSEFAIL","[chars]: Failed to remove VC [dec]/[dec] cause [int]","An attempt to remove a virtual circuit on the module failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_POSEIDON","6","ALARM_INFO","[chars] [chars] [chars] [chars] [chars]","This message is generated whenever an alarm is present in the system and the alarm status has been reported to the RP, or an alarm has been removed from the system and the alarm status has been reported to the RP.","This is an informational message only. No action is required."
"CWAN_QINQ","3","CWAN_POCH_QINQ_NULL_EGRESS","[chars] QinQ Ether VC have received invalid egress assignment on phyport [chars]for trunk encapsulation dot1q [int]","The port channel QinQ Ether VC subinterface being configured contains an invalid egress port assignment. The egress traffic of the OSM port will be stopped for this EVC.","Copy the message exactly as it appears on the console or in the system log. At the line card, enter the show cwan qinq command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_QINQ","3","CWAN_QINQ_TRUNK_DATAINCONSISTENCY","QinQ data integrity check failed for bridge-vlan [int] dot1q [int] using trunk encapsulation dot1q [int], existing record shows mapping with encapsulation dot1q [int].","A data integrity error related to QinQ was detected while a trunk was being configured for the bridge VLAN that is indicated in the message text. The error will be ignored, and the QinQ update will proceed normally.","Enter the show cwan qinq command on the module. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_RP","1","OVERRIDE_MAC_INVALID","[chars] has invalid override-mac-address.","The user issued an override MAC address that does not match the MAC address of the MSFC. This condition can occur if the configuration was moved to new hardware or the MAC address command was used on another interface. While the system automatically corrects this condition, the configuration needs to be adjusted.","Modify the override MAC address command in the configuration."
"CWAN_RP","3","FAILED_CONFIG","Failed to send line card config message [chars] for slot [int] port [int]","The RP could not send the specified configuration message to the line card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_RP","3","IFCFG_CMD_NOT_OWNER","Process '[chars]' waiting for interface configuration command ([hex]) to slot [int]/[int] without acquiring lock owned by process '[chars]'","A process on the RP sent a configuration command to the slot specified in the message and a different process waited for the result. This condition could cause incorrect line card configuration states.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_RP","3","MODULE_TYPE","cannot find FCI for module type [int] in slot [int]","An internal software error occurred while the system was detecting the module type in the specified slot. The module operation will be affected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_RP","3","PROCMSG","Process msg send failed for process[dec]","An attempt to send a process message failed for the specified process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_RP","3","UPGRADE_ERROR","Slot [int]: The ROMMON upgrade failed to complete.","An error occurred during the upgrade process.","If the module reloads successfully, examine the file and try the upgrade process. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_RP","3","WAN_BRIDGING_CONFIG_EXCEEDED","The number of VPLS/EoMPLS/Bridging/QinQ VCs exceeded the maximum supported by the platform","The user attempted to configure more VPLS, EoMPLS, and bridging VCs than the number that is supported by the platform.","Review the configuration guidelines for the features that are being configured, and reduce the number of VPLS, EoMPLS, and bridging VCs to the number that is supported by the platform."
"CWAN_RP","4","CONFIG_MISMATCH","Irreconcilable Configuration difference between Active & Standby Supervisors due to OIR/Config Event -> Reloading Standby Supervisor to synchronize the configuration.","An unexpected configuration difference exists between the active and standby supervisor engines.","The standby supervisor engine is being reloaded. No action is required."
"CWAN_RP","4","EMPTY_CWANBAYS","FLEXWAN in slot [dec] is empty. Please remove the Flexwan or insert it with atleast one PA","The FlexWAN in the specified slot does not contain any port adapters.","The FlexWAN should be removed. This is an unsupported configuration."
"CWAN_RP","4","IFCFG_CMD_TIMEOUT","Interface configuration command ([hex]) to slot [int]/[int] timed out","The RP sent a configuration command to the slot specified in the message and received no confirmation for the command.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_RP","4","INCR_CFG_SYNC_FAIL","7600 incremental running-config sync for [[dec]/[dec]] failed - [chars]([dec]), Reload Standby","The specified 7600 series router incremental running configuration synchronization has failed.","Power cycle the redundant supervisor engine."
"CWAN_RP","4","INVALID_UNIT","Invalid 7600 Unit: [[dec]/[dec]].","The specified 7600 series router slot and CPU are beyond the chassis limit.","Power cycle the redundant supervisor engine."
"CWAN_RP","4","MODULE_CONFIG_MISSING","configuration missing for slot [int]","Some information is missing regarding the configuration of the module in the specified slot. Any startup configuration for the interfaces will not be applied. If the module in the specified slot is a FlexWAN, details about the port adapters in the FlexWAN are missing from the configuration information. This information is missing from the SLOTCACHE ROMMON variable.","If the module in the slot specified in the error message has not previously been inserted, it has no previous configuration; therefore, no action is required. If the configuration for the specified slot in the startup configuration is suitable for the module in that slot, after the module has loaded, manually apply the configuration by using one of the following two methods. The second method requires a system reload."
"CWAN_RP","6","ADF_FILE","Slot [int]: Using VPN-SM Upgrade File: '[chars]'","The system is booting the specified upgrade image for the VPN Services Module.","No action is required."
"CWAN_RP","6","AUX_FILE","Slot [int]: Found VPN-SM Firmware in File: '[chars]'","The file specified in the message was found and will be loaded instead of the bundled image by the VPN Services Module.","No action is required."
"CWAN_RP","6","LC_RESET","The RP is reloaded, resetting slot [dec] is necessary. Please ignore errors if any, till the linecard comes up.","If the system is running Catalyst operating system software on the supervisor engine and Cisco IOS software on the MSFC, the WAN line cards that power up before the RP powers up will be reset automatically.","This is an informational message only. No action is required."
"CWAN_RP","6","NO_LC_IMAGE","Line card image in slot [dec] for card_id [dec] is not bundled with IOS.","The line card in the specified slot will be powered down to prevent it from running an image that is not supported by the RP. If the line card image is compatible with the image running on the RP, there might be another problem with the software.","Follow any instructions provided in the error message text. If no instructions are provided, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_RP","6","OUT_OF_RESOURCE","[chars] configuration has exceeded available internal resources.","The resources required for configuration are no longer available. They may have been acquired by another application.","If the requested resources have not been allocated to another application, contact your Cisco technical support representative for further assistance."
"CWAN_RP","6","OVERRIDE","Slot [int]: ...Overriding Intrinsic VPN-SM Firmware.","The specified image will be used instead of the bundled image.","No action is required."
"CWAN_RP","6","UPGRADE_COMPLETE","Slot [int]: ROMMON upgrade complete. Reset the card for the changes to take effect.","The ROMMON upgrade has completed successfully. The module must be reloaded for the changes to take effect.","No action is required."
"CWAN_SLOT","1","CF_ADDFAILED","Failed to register chkpt client, client = %d","The checkpoint facility client could not be registered.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_SLOT","1","CF_NOBUF","Failed to get chkpt buffer, client = %d","The checkpoint facility could not obtain buffer memory.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"CWAN_SP","3","INIT_FAIL","Failed to allocate [dec] bytes memory needed for CWAN SP module initialization","A memory allocation failure has occurred during initialization of WAN SP module.","Upgrade to a higher memory size on the switch processor (SP)."
"CWAN_SP","4","UNKNOWN_PW","Unknown CWAN pseudo wire on vlan [dec], port [dec]/[dec]","An unknown WAN pseudowire is being used.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_SPA","3","CREATION_FAILURE","slot=[dec] subslot=[dec], spa_type=[hex], lc_type=[hex].","An attempt to create a SPA object has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_SPA","3","DIAG_CONFIG","[chars] did not complete [dec]/[dec]","An error has occurred during diagnostic test.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_SPA","3","INVALID_DATA_INSTANCE","interface type [chars], slot [dec] port [dec] vc [dec] : [chars]","The data required to support the specified interface is not available.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_SPA","3","INVALID_IF_INDEX","index= [dec], cardType=[hex], spaType=[hex], slot [dec] subSlot [dec] slotunit [dec] vc [dec]","The index for the interface is not valid.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_SPA","3","INVALID_INDX_RANGE","index1= [dec], index2= [dec], maxIndex= [dec]","Invalid index range.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_SPA","3","MEM_ALLOC_ERROR","[chars]","A memory allocation error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_SPA","3","NULL_SPA_PTR",',"The pointer to a SPA object is null.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_SPA","3","NULL_VFT","[chars] virtual function table is not initialized. spaType=[hex]","A required function table is not initialized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_SPA","3","NULL_VFUNC","[chars] vector is not initialized. spaType=[hex]","A required function vector is not initialized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_SPA","3","POWER_CYCLE","[chars] occurred on Shared Port Adapter [int]/[int]","An error has occurred that will cause the shared port adapter to be power cycled.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWAN_SPA","3","SPA_CREATION_FAILURE","slot=[dec] subslot=[dec], PID=[chars] lc_type=[hex].","An attempt to create a SPA object has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWPA","2","BAD_HWVERS","Unable to determine board hardware version","The module software cannot read the module hardware version. This condition indicates a hardware error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWPA","2","PAOIR","Port adapter OIR not supported, reloading","An OIR operation occurred on the port adapters of the specified module, but OIR is not supported on the port adapter. This error has caused the module to fail and reload.","Do not attempt OIR on the port adapters of the specified module."
"CWPA","2","PA_VOLFAIL","Port adapter [dec]V failed, Reloading flexwan","The module encountered an error involving power delivery to the module. Probable causes for this error are an environmental condition, an overtemperature condition, or inconsistent voltage to the module.","Verify that the input voltage and the temperature of the module are within acceptable ranges."
"CWPA","2","WHICH_INT","Unexpected [chars] interrupt, INT status = [hex]","The module specified in the error message has encountered an unexpected interrupt.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWPA","3","DIAGFAIL","Failed to handle diag [chars] [dec]","The module failed to execute a diagnostics command.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWPA","3","PROCCREATEFAIL","Failed to create [chars] process","A module failed to create a process that is necessary for proper functioning of the module.","If a statistics export process was not created, check the I/O rate and the bytes that are getting incremented in the show interface command output for the nonchannelized interfaces on the FlexWAN and Enhanced FlexWAN modules. You can also get the statistics from the show interface acc command output or the show interface stats command output. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWPA","4","HEADER_TOO_BIG","Needs [dec] bytes, with only [dec] bytes available. Packet size [int], received from [chars], buffer [hex] packet start [hex]:[hex]:[hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex][hex]:[hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]","A packet was sent from the port adapter to either the route processor or the line card. That packet did not have enough available space to append the header. A new particle has been linked to the packet to store the header.","No action is required."
"CWPABRIDGE","3","BADLTL","[chars] got bad LTL index [hex] for vlan [int] ckt_id [int] sent from RP","The RP has provided the line card with an invalid value for the local target logic (LTL) index value.","If the bridging traffic stops going through, copy the message exactly as it appears on the console or in the system log. At the RP console exec prompt, enter the following commands:"
"CWPABRIDGE","3","NOCLONEDPAK","Unable to allocate pak header for cloned pak","A line card is not able to allocate a pak header for a cloned pak that is used for flooding packets among bridged WAN links.","On the Cisco support website, use the online Software Advisor and check the release notes for the code you are running to determine the minimum amount of memory. If you have sufficient memory and are still seeing this error message, load the previous image on the unit to return the unit to an operational state and retrieve the information needed to report this problem. Copy the contents of the line card's crashinfo data from the cwan slot/bay bootflash: command, where slot and bay belong to the line card. When you open a TAC case, provide the line card's crashinfo data and the output of the show tech command from the router."
"CWRPSPA","3","HWIDB_FAILURE","Creation: slot [dec] subSlot [dec] port [dec] vc [dec]","Failed to create a hardware interface descriptor block (HWIDB).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWRPSPA","3","INVALID_PORT_NUM","slot=[dec] port=[dec], hwidbType=[hex], max_port_num=[dec], LCtype=[hex]","The port number is out of range.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWRPSPA","3","MAX_SPA","Power to IPSEC-SPA-2G in [chars] is denied because it has exceeded the number allowed([dec])","The number of IPSEC-SPA-2G port adapters in a chassis is limited. This message displays when the number of IPSEC-SPA-2G port adapters in the chassis has exceeded the limit.","Use only the number of supported IPSEC-SPA-2G port adapters."
"CWRPSPA","3","NO_HOST_INFO","slot [dec] subSlot [dec], spaType [hex]","Failed to get information about the host line card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWRPSPA","4","SPA_CMD_NO_RESP","[chars]: No response for interface configuration command [int]","A timeout occurred while the RP was waiting for a response from the line card. This condition may occur when the line card CPU is too busy to respond to the configuration command.","Retry the configuration command."
"CWRPSPA","4","SPA_RESP_CMD_MISMATCH","[chars]: Expecting response to interface configuration command [int] but received response to command [int].","An internal synchronization error occurred while configuring the interface. The configuration may not have succeeded.","Check that the running configuration for the interface is correct. If this message occurred on the standby, try reloading the standby to ensure that its configuration is in sync. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWRPSPA","6","CARDRELOAD","Module [int] reload due to SPA insert in [int]/[int].","When inserting a SPA on the specified module, the module resets.","This message is informational. No action is required."
"CWSLC","3","DIAGFAIL","Failed to handle diag [chars] [dec]","The module failed to execute a diagnostics command.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWSLC","3","DIAGSKIP","Skipped diag for port [dec]","The module skipped diagnostics for the specified port.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWSLC","3","DIAGWARNING","Backplane DIP switches settings incorrect","The backplane DIP switches need to be set properly.","Refer to the 7600 SIP and SPA Hardware Installation Guide for information about how DIP switches must be set."
"CWSLC","3","IPCALLOCFAIL","Failed to allocate IPC buffer [chars]","An Enhanced FlexWAN module failed to allocate a buffer for communication with the route processor (MSFC).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWSLC","3","IPCSENDFAIL","Failed to send IPC message [chars]","An Enhanced FlexWAN module failed to send a message to the route processor (MSFC).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWSLC","3","LC_ENCAP_UPDATEFAIL","Could not update encapsulation on [chars] to [int]","The line card failed to update the new encapsulation that was requested. The interface data structures could not be temporarily locked to perform the encapsulation change","If the interface does not come up with the new encapsulation, remove and reconfigure the encapsulation on the interface. If the error persists after a few attempts at reconfiguration, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","0","FATAL_EXCEPTION","[chars]","The OSM encountered a fatal exception.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","2","FATAL_ATM","[chars]","The OSM encountered a fatal line management interrupt. This error is not recoverable and will cause the system to fail.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","2","PCITIMEOUT","Fatal Local I-O Bus [dec] Timeout Addr = [hex]","The OSM encountered a PCI timeout.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","2","PLIM_RX","[chars]","The OSM encountered an FPGA error that caused a sequence error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","2","SLAVEPCI","[chars]","The OSM encountered a PCI error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","2","TESTCRASH","[chars]","The user entered a command that caused the module to fail.","No action is required."
"CWTLC","3","ATMTXFIFO","[chars]","The OSM encountered an error with the FPGA that has caused the FIFO queue to exceed the maximum limit. This condition will cause the system to fail.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","3","CONST_SWITCHING_BUS_INTERFACE_ASIC_ERR","Constellation Switching Bus Interface Asic [[dec]] error: [chars]","The CWTLC switching bus interface ASIC received an error.","If traffic recovers, no action is required. Otherwise, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","3","CONST_SWITCHING_BUS_INTERFACE_ASIC_HWERR","Constellation Switching Bus Interface Asic [[dec]] HW error: [chars]","The CWTLC switching bus interface ASIC received a hardware error and will be reset.","If traffic recovers, no action is required. Otherwise, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","3","DMA_ENGINE_ASIC_ERR","DMA Engine Asic [[dec]] error: [chars]","The CWTLC DMA engine ASIC received an error.","If traffic recovers, no action is required. Otherwise, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","0","DMA_ENGINE_ASIC_FATAL_ERR","DMA Engine Asic[[dec]] fatal error: [chars]","The CWTLC DMA engine ASIC received a fatal error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","3","ERR_DETAIL","[chars]","This message provides additional error details for a previous message, which may be of use to your technical support representative.","Follow the instructions for any system messages preceding this one and be sure to include the text from this error."
"CWTLC","3","EXCEPTION_ERR","[chars]","The OSM encountered an error exception.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","3","FABRIC_INTERFACE_ASIC_FATAL","OSM Fabric Interface ASIC Fatal Error. ERROR CODE: [chars]","The OSM fabric interface ASIC received a fatal error.","If traffic recovers, no action is required. Otherwise, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","3","FABRIC_INTERFACE_ASIC_PXF","CWAN PXF Client [[dec]] Not Running","An ASIC device on the OSM has detected that the designated PXF client is not running.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","3","FR_BAD_BRIDGING","Frame Relay: old bridge-vlan([int]) or new bridge-vlan([int]) on the bridged interface [chars] is malformed","This is an unexpected update from the route processor and should be ignored.","This is an informational message only. No action is required."
"CWTLC","3","FR_INTLEVEL","unexpected interrupt level invocation of frame-relay handler:[chars] if_number([dec]) dlci([dec])","Some feature code mistakenly invoked the module Frame Relay handler, which is designed to run at process level. This condition may lead to data corruption and a module failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","3","LTL_ERR","Inconsistent port selection [hex] assigment for PXF([dec]) Vlan([dec]) on PXF([int])","The port selection information stored in the database is not valid.","Shut down the interface VLAN and restart the interface VLAN."
"CWTLC","3","MCAST_REPL_ENGINE_FATAL","Multicast Replication Engine Asic Fatal Error. Resetting ASIC.","The OSM multicast replication engine ASIC received a fatal error.","If traffic recovers, no action is required. Otherwise, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","3","MEDUSA_FATAL","OSM Medusa ASIC Fatal Error. ERROR CODE: [chars]","The OSM Medusa ASIC received the specified fatal error.","No action is required if traffic recovers. If traffic does not recover, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","3","MEDUSAPXF","CWAN PXF Client [[dec]] Not Running","An ASIC device on the OSM has detected that the specified PXF client is not running.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","3","NOMEM","[chars]","The OSM could not obtain statistics due to depleted memory.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","3","NO_STATID","PXF([dec]): no stat_id is available for statistics collection","The OSM has used up all resources for statistics collection. No additional resources are available for further statistics collection.","Reduce the number of features configured on the specified PXF. If conditions warrant, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","3","OLDIOFPGA","Upgrade your I/O FPGA","The OSM has an earlier release of the I/O FPGA software.","Contact your Cisco technical support representative to upgrade the I/O FPGA software."
"CWTLC","3","PLIM_TX","[chars]","The OSM encountered an FPGA error that caused a sequence error. The module will attempt to recover from the error.","If the system recovers, no action is required. If the system does not recover, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","3","PORTERROR","Port control error, cmd=[chars], port=[dec]","The port control command function has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","3","SECPAIRINT","Unexpected VA/Toaster interrupt from second pair","The OSM experienced an unexpected interrupt.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","3","TITANFATAL","Titan Fatal Error. Resetting ASIC.","The OSM Titan ASIC received a fatal error.","No action is required if traffic recovers. If traffic does not recover, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","3","TMC_STATID_INCONSISTENCY","PXF([dec]):Inconsistent stats id([hex]) [int] packets dropped.","The WAN module received inconsistent statistics from the PXF. The PXF reported that a packet was dropped, but the PXF did not report the correct packet count.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","3","TMTRIE_ALLOC_FAILED","Failed to allocate toaster mtrie nodes.","The system encountered an error while it was attempting to allocate memory from a WAN OSM component.","Reduce the number of routes associated with a VRF identifier or upgrade the WAN OSM to a higher version."
"CWTLC","3","UNSUPPORTED_LABEL_RANGE","The maximum label range configured for this system exceedsthe [int] limit supported by the OSM module.","The MPLS label range configured for this system is not supported. The maximum label range limit is specified in the message.","Change the maximum MPLS label range by entering the mpls label range command."
"CWTLC","3","VTMS","[chars]","The OSM could not schedule the wheel entry. The reason for the error is specified in the error message text.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","3","VTMSQ_NOTIDLE","Queue not idle when modifying Q([hex])","The VTMS queue was in the process of being modified for a change in QoS configuration, but packets were still going through the queue. When the queue is being modified, there is usually no traffic in the queue.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","4","ASIC_RESET","Reset asics - [chars]","The ASICs on the OSM are resetting. System traffic should recover and continue normally after the module resets.","No action is required."
"CWTLC","4","CONST_SWITCHING_BUS_INTERFACE_ASIC_CONFIG_ERR","Constellation Switching Bus Interface Asic [[dec]] configuration failed after [dec] retries.","The CWTLC switching bus interface ASIC failed to be configured correctly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","4","MEDUSAERROR","Medusa Error. [chars]","The CWTLC Medusa ASIC received a recoverable error.","No action is required if traffic recovers. If traffic does not recover, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","4","PINNACLE_OLDIOFPGA","Link negotiation maybe be affected, upgrade I/O FPGA","The system detected an earlier release of the I/O FPGA software. The I/O FPGA software needs to be upgraded to the latest release.","Upgrade the I/O FPGA software to the newest release. If you require assistance, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","4","PORT_ASIC_OLDIOFPGA","Link negotiation maybe be affected, upgrade I/O FPGA","An earlier version of the I/O FPGA software has been detected.","Upgrade the I/O FPGA software to the latest version. If you require assistance, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","4","TMC_INVALID_STATID","PXF:Invalid-Statid ([dec]) for vc [int] under interface [int]","The OSM has encountered an internal error while setting up the statistics system.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","5","BUS_SEQ_ERR","Constellation bus Sequence Error. Resetting port ASICS.","The SP detected a sequence error on the backplane bus of the OSM. The system called a reset sequence from the EARL to recover from this error. System traffic should recover and continue normally.","If traffic recovers, no action is required. If traffic does not recover, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","5","DATAPATH_RECOVERY_PATCH","EARL reset patch invoked.","The ASICs on the OSM were reset so that the module could recover from a bus sequence error. This condition usually occurs under heavy traffic with HA-related switchover or a module OIR operation. System traffic should recover and continue normally.","If traffic recovers, no action is required. If traffic does not recover, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","5","FABRIC_INTERFACE_ASIC_RE_INIT","Fabric Interface Asic Re-initialize.","The OSM fabric interface ASIC is being reinitialized because of a system backplane bus sequence error, a fatal ASIC error, or a line card error.","If traffic recovers, no action is required. Otherwise, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","5","MEDUSA_RE_INIT","Medusa Re-initialize.","The OSM Medusa ASIC is being reinitialized because of a system backplane bus sequence error or a fatal ASIC error on the module itself.","If traffic recovers, no action is required. If traffic does not recover, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","5","PENDING_PATCH","Invoke pending data recovery patch.","The ASICs on the OSM line card has been reset so that it can recover from backplane switching bus sequence errors or local hardware ASIC errors. This condition is usually occurs under stress trafficwith HA-related switchover or a line card OIR operation. System traffic should recover and continue normally.","If traffic recovers, no action is required. Otherwise, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC","6","FABRIC_INTERFACE_ASIC_MODECHANGE","Fabric Interface Asic switching bus Mode changed to [chars]","The supervisor engine has changed the CWTLC fabric interface ASIC switching bus mode.","No action is required."
"CWTLC_ATOM","3","INTFID_ERR","The internal interface ID [hex] for the AToM interface [chars] is invalid for the connection ID [hex]","The internal interface ID that is required by the OSM to establish an AToM connection is either invalid or is mismatched with the control plane MPLS data structure for this connection. The current interface ID of the OSM has lost its synchronization with the interface ID of the control plane for this connection. This condition is usually caused by unfavorable network conditions such as a failover operation and can occur during normal system operation.","Enter the appropriate AToM commands for either the Frame Relay over MPLS, Cell Relay over MPLS, AAL5 over MPLS, or Frame Relay local switching to remove the AToM connection, then add the connection again. Performing this action once should successfully reestablish the connection."
"CWTLC_ATOM","3","OSM_BB1_CONFIG_UNSUPPORTED","Attempt to configure Frame Relay over MPLS or Frame Relay localswitching on a non-enhanced OSM","Frame Relay over MPLS and Frame Relay local switching features are supported only on enhanced Optical Services Modules. Nonenhanced OSMs do not support these features.","Remove the configuration of the unsupported features, or upgrade this module to an enhanced OSM."
"CWTLC_CHOC","3","HWERROR","[chars]","The module hardware has experienced the specified error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC_CHOC_DSX","3","HWERROR","[chars]","A hardware error involving the OSM line card has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC_CHOCX","3","HWERROR","[chars]","The module hardware has experienced the specified error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC_GEWAN","3","FPGA_PROG_FAILED","[chars] FPGA initialization failed due to [chars]","The FPGA could not be initialized. The cause of this condition is specified in the message text on the console or in the system log. As a result of this condition, the device is not operational and has been disabled.","Reload the line card. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show module command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC_GEWAN","3","GEMAC_9K_MODE_FIX_FAILED","Fix for 9k buffer mode failed for GEMAC[[dec]]","An error has occurred while the system was setting the GEMAC component of the Gigabit Ethernet WAN module in 9,000-buffer mode (a buffer mode that supports jumbo frames). This condition occurred on the port specified in the error message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC_GEWAN","3","GEMAC_INIT_FAILED","Device initialization failed for GEMAC[[dec]]","An error occurred during initialization of the GEMAC device.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC_GEWAN","3","IF2PORT","Cannot determine port from interface [dec] for operation [dec] with [[enet]]","The port number could not be determined from the given interface number.","Reload the line card. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show module command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC_GEWAN","3","MAC_OP_BAD","Unknown MAC address operation [dec] with [[enet]] on port [dec]","The specified MAC address operation is unknown and cannot be performed.","Reload the line card. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show module command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC_GEWAN","3","PORT_AUTONEG_FAIL","Failed to [chars] auto-negotiation [chars] on port [dec]","The enabling/disabling of the auto-negotiation functionality on a GE-WAN port has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC_GEWAN","3","PORT_CMD_FAIL","Port [chars] failed on port [dec]","A GE-WAN port command has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC_GEWAN","3","TABLE_ADD_REMOVE_FAILED","MAC address table [chars] with [[enet]] failed on port [dec]","The addition or removal of a MAC address from the MAC address table has failed.","Reload the line card. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show module command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC_GEWAN","3","ZICO_INIT_FAILED","Device initialization failed for Zico FPGA[[dec]]","An error occurred during initialization of the protocol converter FPGA.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC_GEWAN","5","GEMAC_INTR","[chars]: [chars]","The GEMAC component of the Gigabit Ethernet WAN module caused an error interruption.","Reload the module. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC_GEWAN","5","LINKFPGA_INTR","Index[[dec]] Cause[[hex]]: [chars]","The link FPGA component of the Gigabit Ethernet WAN module caused an error interruption to occur.","Reload the module. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC_QOS","3","CHUNK_INIT_FAIL","[chars]: [chars] allocation failed","The OSM detected a memory allocation failure. The installed amount of memory could be insufficient for the software features that are configured.","If this message appears continuously, a memory upgrade might be required."
"CWTLC_QOS","3","CHUNK_MALLOC_FAIL","[chars]: chunk_malloc for [chars] failed","The OSM detected a memory allocation failure. The installed amount of memory could be insufficient for the software features that are configured.","If this message appears continuously, a memory upgrade might be required."
"CWTLC_QOS","3","MISC","[chars]: [chars] [dec]","The OSM detected the software error event that is specified in the message text.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC_QOS","4","STATS_CLASS_INFO_INVALID","Stats process found invalid class_info [[hex]], stat_type [[hex]] caller_pc [[hex]] caller_pc1 [[hex]].","The OSM has detected invalid class data. This condition is transient when the policy map is modified and the update is propagated to the OSM.","If this message appears continuously, reset theline card by entering the hw-module module <> reset command. Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"CWTLC_QOS","3","WRED_CLASS_INDEX_NOT_FOUND","sub-class limit has exceeded","The OSM supports only 29 WRED classes: 8 CS, 12 AF, 1 EF, and 8 user-defined DSCP values.","Refer to the technical documentation for more information about WRED configurations on the OSM."
"CWTLC_RP","3","TMEM_IMPROPER_SEL","Improperly nested PXF [int] memory select/deselect at nested level [int]. Value stored with select ([hex]) does not match the value passed with deselect ([hex])","The last PXF select operation was not followed by a deselect operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DATACORRUPTION","1","UNAVAILABLE","%s, -PC= 0x%08X","Data corruption has been detected","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DATA_DESCR","3","UNAVAILABLE","Defer failure on %s for descriptor %u-%u/%u/%u/%u","Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An error occurred during the processing of a data descriptor. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DATA_DESCR","3","UNAVAILABLE","Encode failure: %s, descriptor type=%d","An internal data descriptor could not be encoded for synchronization for the interface or controller in the run-time module specified in the message output. The failure most likely occurred because of a software error. The descriptor type specified in the message output identifies the type of failure. The system state between the active and standby units might not be properly synchronized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DATA_DESCR","3","UNAVAILABLE","Found expired message entry for descriptor %u-%u/%u/%u/%u","Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An error occurred during the processing of a data descriptor. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DATA_DESCR","3","UNAVAILABLE","Internal error on data descriptor queue: %s","Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An error occurred during the processing of a data descriptor. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DATA_DESCR","3","UNAVAILABLE","Lookup Failure: %0-8x.%0-8x.%0-8x.%0-8x.%0-8x (%u-%u/%u)","Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An interface corresponding to a data descriptor index was not found on the Standby unit when it was looked up. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized.","Gather system logs and error messages at both the active and the standby units. Issue the recommended show commands at the active unit. Show data-descriptor controller. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DATA_DESCR","3","UNAVAILABLE","Lookup Failure: %0-8x.%0-8x.%0-8x.%0-8x.%0-8x (%u-%u/%u/%u/%u)","Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An interface corresponding to a data descriptor index was not found on the Standby unit when it was looked up. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized.","Gather system logs and error messages at both the active and the standby units. Issue the recommended show commands at the active unit. Show data-descriptor hwidb. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DATA_DESCR","3","UNAVAILABLE","Lookup Failure: %0-8x.%0-8x.%0-8x.%0-8x.%0-8x (%u-%u/%u/%u/%u/%u)","Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An interface corresponding to a data descriptor index was not found on the Standby unit when it was looked up. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized.","Gather system logs and error messages at both the active and the standby units. Issue the recommended show commands at the active unit. Show data-descriptor [hwidb|swidb|controller]. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DATA_DESCR","3","UNAVAILABLE","Lookup Failure: %0-8x.%0-8x.%0-8x.%0-8x.%0-8x (%u-%u/%u/%u/%u/%u)","Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An interface corresponding to a data descriptor index was not found on the Standby unit when it was looked up. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized.","Gather system logs and error messages at both the active and the standby units. Issue the recommended show commands at the active unit. Show data-descriptor [hwidb|swidb|controller]. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DBCONN","3","UNAVAILABLE","Bad TP name configured for server %s","The tpname configured for the dbconn server is not recognized by the remote database server.","Configure a TP name that is available on the remote database server. Most DB2 systems will accept the DRDA default TP name of except for SQL/DS. Contact your SNA network administrator and/or your DB2 administrator to determine the TP name used by your DB2. To use the DRDA default, do not explicitly configure a TP name for your dbconn server."
"DBCONN","3","UNAVAILABLE","Bad license key configured for Database Connection.","The license key configured with the dbconn license configuration command is not valid.","Check that the license key was entered correctly in the dbconn license configuration command. Refer to the dbconn feature documentation for information on how to obtain a valid license key."
"DBCONN","3","UNAVAILABLE","Bad remote LU '%s' configured for server %s","The remote LU configured for the dbconn server is incorrect.","Contact your SNA network administrator to determine the correct name of the remote LU for DB2 on the remote database server. Be sure to check that the SNA network name is correct as well as the LU name."
"DBCONN","3","UNAVAILABLE","DRDA protocol error from server %s, SYNERRCD x'%02X'","An unexpected DRDA protocol error occurred between dbconn and the remote database server.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. If possible, also provide the output of the debug dbconn drda command, and an SNA line trace between the router and the remote database server, for the period during which this message appeared."
"DBCONN","3","UNAVAILABLE","License is about to expire for Database and Transaction Connection.","This system is using a temporary key for its Database and Transaction Connection. The license is about to expire.","Contact StarQuest Software to acquire a permanent key."
"DBCONN","3","UNAVAILABLE","License is expired for Database and Transaction Connection.","This system is using a temporary key for its Database and Transaction Connection. The license is expired.","Contact StarQuest Software to acquire a permanent key."
"DBCONN","3","UNAVAILABLE","Number of connections for TXCONN and DBCONN is at 90%% license limit.","The number of allowed Database and Transaction Connection client in this system is reaching the limit.","Contact StarQuest Software to acquire more license."
"DBCONN","3","UNAVAILABLE","Unknown mode '%s' configured for server %s","The mode configured for the dbconn server was rejected by the remote database server.","Contact your SNA network administrator to determine the correct name of the mode to use to connect to DB2 on the remote database server."
"DBCONN","5","UNAVAILABLE","APPC security failed, client %i using userid '%s' for server %s","An unspecified security failure has occurred. The database host system may be able to provide more specific information.","This is an informational message only. LOG_STD_NO_ACTION"
"DBCONN","5","UNAVAILABLE","APPC security failed, client %i using userid '%s' for server %s","The password passed in by the client was rejected by the remote database server because it's expired.","This is an informational message only. LOG_STD_NO_ACTION"
"DBCONN","5","UNAVAILABLE","APPC security failed, client %i using userid '%s' for server %s","The password passed in by the client was rejected by the remote database server.","This is an informational message only. LOG_STD_NO_ACTION"
"DBCONN","5","UNAVAILABLE","APPC security failed, client %i using userid '%s' for server %s","The remote database server requires a userid and password, but the password was not provided.","This is an informational message only. LOG_STD_NO_ACTION"
"DBCONN","5","UNAVAILABLE","APPC security failed, client %i using userid '%s' for server %s","The remote database server requires a userid, but the userid was not provided.","This is an informational message only. LOG_STD_NO_ACTION"
"DBCONN","5","UNAVAILABLE","APPC security failed, client %i using userid '%s' for server %s","The userid and/or password passed in by the client were rejected by the remote database server.","This is an informational message only. LOG_STD_NO_ACTION"
"DBCONN","5","UNAVAILABLE","APPC security failed, client %i using userid '%s' for server %s","The userid used to connect to the remote database server has been revoked.","This is an informational message only. LOG_STD_NO_ACTION"
"DBCONN","5","UNAVAILABLE","APPC security failed, client %i using userid '%s' for server %s","The userid used to connect to the remote database server is not valid.","This is an informational message only. LOG_STD_NO_ACTION"
"DBCONN","5","UNAVAILABLE","All WLM routes on server %s have become unavailable. Recovery is in progress.","A load balanced WLM server has lost connectivity to all destinations in its server list. All client connections to this server will be rejected until a host in the complex becomes available again.","This is an informational message only. LOG_STD_NO_ACTION"
"DBCONN","5","UNAVAILABLE","Client %i connected to server %s has timed out after %TE.","The client was idle for too long, and the idle timeout configured for the dbconn server expired.","This is an informational message only. LOG_STD_NO_ACTION"
"DBCONN","5","UNAVAILABLE","WLM transport type mismatch on server %s.","The transport type within a server list received from a Workload Manager load balanced database does not match the transport type of the corresponding dbconn server. If the conflicting server list specifies SNA transport type, the default mode #INTER will be used to establish the connection.","This is an informational message only. LOG_STD_NO_ACTION"
"DBUS","2","UNAVAILABLE","Slot %d, unknown controller type 0x%x, ignoring","A processor reported a controller type that is unknown to the system. The processor will not be used and needs to be repaired.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DBUS","3","UNAVAILABLE","DBUS software not ready for slot %d after %s, elapsed %u, status 0x%x","An interface processor failed to come online after being reset. A software or hardware error occurred.","Please refer to Bug Toolkit on the Cisco web-site to check for existing bugs. If you do not find one, obtain the output of show tech and show log and open a TAC case."
"DBUS","3","UNAVAILABLE","Down rev RSP EPROM found HSA system, upgrade EPROM, or remove one RSP","A software or hardware error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DBUS","3","UNAVAILABLE","Invalid EEPROM data found for card in slot %d, card disabled","The ID EEPROM on the indicated card is not programmed correctly.","Call your Cisco technical support representative for a replacement."
"DBUS","3","UNAVAILABLE","Invalid controller type %d in slot %d","An interface processor responded with an unknown or illegal controller type when queried. This should not happen unless the running software does not support the interface processor in question, or the interface processor fails.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DBUS","3","UNAVAILABLE","No driver support in this image for %s in slot %d (card type %d) - disabled","The Cisco IOS image does not have driver support code for the specified interface processor.","Remove the unsupported interface processor card, or reload the router with a Cisco IOS image that has driver support code for that interface processor card."
"DBUS","3","UNAVAILABLE","No magic number found in RP1 EEPROM","The structure containing the system MAC address needed by the OIR facility cannot be found in the RP EEPROM. The RP must be returned for reprogramming.","Return the RP for reprogramming and call your Cisco technical support representative for assistance."
"DBUS","3","UNAVAILABLE","ORFS is not initialized","When oir-remove-failing-slot is invoked, the software attempts to initialize parameters. This initialization failed and the service will not be available.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DBUS","3","UNAVAILABLE","Slot %d control 0x%x, status 0x%x","A processor reported an error. This message is sent out in conjunction with other error messages to provide additional information.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DBUS","3","UNAVAILABLE","Slot %d disabled, will be restarted.","A processor was disabled due to an error. The processor will be reset and not used until the next OIR event or microcode download, when it will be retested.","Reinstall the processor or download the microcode. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DBUS","3","UNAVAILABLE","Slot %d has an unsucessfully configured PA in bay %d","The PA in the slot is not sucessfully configured, either because the VIP is incompatible with it or because the IOS has no pertinent drivers.","Please refer to the documentation of the PA to get a list of compatible VIP's. If the VIP that contains the PA is listed as supported, please refer to the CCO page for IOS versions that support the PA. Otherwise, seat the PA in one of the supported VIP's and verify that the IOS version supports the PA."
"DBUS","3","UNAVAILABLE","Slot %d has an unsupported PA in bay %d","The PA in the slot is not supported, either because the VIP is incompatible with it or because the IOS has no pertinent drivers.","Please refer to the documentation of the PA to get a list of compatible VIP's. If the VIP that contains the PA is listed as supported, please refer to the CCO page for IOS versions that support the PA. Otherwise, seat the PA in one of the supported VIP's and verify that the IOS version supports the PA."
"DBUS","3","UNAVAILABLE","Slot %d, CBus Error","A processor reported a bus error. The processor will be reset and not used until the next on-line insertion and removal (OIR) event or microcode download, when it will be retested.","Reinstall the processor or download the microcode. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DBUS","3","UNAVAILABLE","Slot %d, Internal Error","A processor reported an internal error. The processor will be reset and not used until the next OIR event or microcode download, when it will be retested.","Reinstall the processor or download the microcode. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DBUS","3","UNAVAILABLE","Slot %d, Internal Error due to VIP crash","A processor reported an error. The processor will be reset and not used until the next OIR event or microcode download, when it will be retested.","Reinstall the processor or download the microcode. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DBUS","3","UNAVAILABLE","Slot %d, WCS Controller Instruction Error","The writable control store (WCS) is the set of devices on each interface processor that contains the running microcode. It can be loaded either from the ROM on the interface processor or from the system by using the downloadable microcode facility. In this message, a processor reported a WCS controller instruction error. The processor will be reset and not used until the next OIR event or microcode download, when it will be retested.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DBUS","3","UNAVAILABLE","Slot %d, WCS Controller Parity Error","A processor reported a WCS parity error. The processor will be reset and not used until the next OIR event or microcode download, when it will be retested.","Replace the processor or download microcode. If this message recurs, call your Cisco technical support representative for assistance."
"DBUS","3","UNAVAILABLE","Slot %d, WCS controller in error state (0x%x), resetting","The processor in the slot identified in the error message reported a writable control store (WCS) controller error. The processor will be reset and new microcode loaded. This error message appears only when microcode is downloaded.","Reset the processor and load new microcode. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DBUS","3","UNAVAILABLE","Slot %d, dbus error, slot (0x%x) and complement (0x%x) do not match","A processor reported a mismatch between the contents of the slot register and its complement. This condition indicates a hardware failure in the diagnostic bus controller on that processor or on the diagnostic bus. The processor will be reset and not used until the next OIR event or microcode download, when it will be retested.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DBUS","3","UNAVAILABLE","Slot %d, error loading WCS, status 0x%x cmd/data 0x%x pos %d","A processor indicated an error condition while downloading microcode. The status, cmd/data, and pos numbers shown in the message reflect the error condition, the last byte of microcode loaded, and the position in the file, respectively. If this error appears, the microcode download is aborted and the ROM microcode is loaded.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs"
"DBUS","3","UNAVAILABLE","Slot %d, flow cntrl error loading WCS, last data 0x%x pos %d","A processor indicated an error condition while downloading microcode. The status, cmd/data, and pos numbers shown in the message reflect the error condition, the last byte of microcode loaded, and the position in the file, respectively. If this error appears, the microcode download is aborted and the ROM microcode is loaded.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DBUS","3","UNAVAILABLE","Slot %d, too many DBUS messages","A board in the slot identified in the error message tried to send too many logger messages.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DBUS","3","UNAVAILABLE","bad or no response, slot %u","A board in the slot identified in the error message failed to respond.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DBUS","3","UNAVAILABLE","ready wait timeout, slot %u","The field-programmable gate arrays on an interface processor failed to load after being reset. This indicates a probable software or hardware problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DCU","1","UNAVAILABLE","The maximum number of DCU ports (%d) is exceeded","System detected too many DCU ports.","Check the configuration."
"DCU","3","UNAVAILABLE","%s: DCU keep-alive failure, card reset","Port Adapter has stopped processing keep-alives.The system should recover. No action is required.DEC21140-1Error Message    %DEC21140-1-UNAVAILABLE: %s timed out, csr5=%#x Explanation    The software failed to initialize/restart a Fast Ethernet interface.","Try resetting the interface by doing a shutdown followed by a no shutdown. If the message recurs, try reseating the Port Adaptor. If reseating also does not work call your technical support representative for assistance. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DEC21140","1","UNAVAILABLE","Only found %d interfaces on bay %d, shutting down bay","The number of interfaces found was not what was expected. This possibly indicates a hardware failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DEC21140","1","UNAVAILABLE","msgtxt_initfail","The Fast Ethernet port initialization failed. This can be caused by disconnected cabling or a failure to detect the media in use.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DEC21140","2","UNAVAILABLE","Interface %s does not support ISL","ISL is not supported on the specified interface's hardware.","LOG_STD_NO_ACTION"
"DEC21140","3","UNAVAILABLE","%s csr0=%#x, csr5=%#x","The Fast Ethernet controller has signalled an error condition on the specified port. CSR5 Register Description: bit 13: Fatal Bus Error bit 11: General-Purpose Timer Expired bit 09: Receive Watchdog Timeout bit 08: Receive Process Stopped bit 07: Receive Buffer Unavailable bit 03: Transmit Jabber Timeout bit 02: Transmit Buffer Unavailable bit 01: Transmit Process Stopped bit 25:23 Error Bits (Valid only when csr5 is set) CSR5 Error Type 000 Parity error 001 Master abort 010 Target abort","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DEC21140","3","UNAVAILABLE","%s doesn't support the configured duplexand speed combination","The Fast Ethernet port was configured for a duplex/speed combination that this particular hardware doesn't support.","Specify a different speed and duplex combination. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DEC21140","3","UNAVAILABLE","%s overflow error Error Message    %DEC21140-3-UNAVAILABLE: %s overflow error","The Fast Ethernet receiver was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data. This could be caused by excessive system load.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DEC21140","3","UNAVAILABLE","%s packet buffer, pak=0x%x","This indicates an internal software inconsistency.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DEC21140","3","UNAVAILABLE","%s transmit error","The DEC21140 chip set operates in cut-through mode. The controller initiates the transmission before the complete packet is received by the internal FIFOs and expects that remaining portion of the packet will follow. Because of excessive traffic on the PCI or system bus, the remaining portion does not arrive on time in the internal FIFOs.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DEC21140","3","UNAVAILABLE","Bay %d device ID seen as %#x, expected %#x","The Fast Ethernet driver failed to initialize.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DEC21140","3","UNAVAILABLE","Unit %d, Tx FIFO underflow","The Fast Ethernet transmitter was ready to transmit before a packet was in the buffer. This could be caused by excessive system load.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DEC21140","3","UNAVAILABLE","Unit %d, receive FIFO overflow","The Fast Ethernet receiver was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data. This could be caused by excessive system load.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DEC21140","5","UNAVAILABLE","%s cable/connector problem?","The Fast Ethernet port did not find a carrier when preparing to transmit a packet, meaning that it is no longer receiving signals from the LAN. This can be caused by disconnected Fast Ethernet cabling or a transceiver failure.","Check your Fast Ethernet wiring and port adapter. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DEC21140","5","UNAVAILABLE","%s cable/transceiver problem?","The Fast Ethernet port lost carrier while transmitting, meaning that it is no longer receiving signals from the LAN. This can be caused by disconnected Fast Ethernet cabling or a transceiver failure.","Check your Fast Ethernet wiring and port adapter. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DEC21140","5","UNAVAILABLE","%s excessive collisions","The Ethernet Controller failed to transmit a packet because of excessive collisions. The packet was dropped. This condition can happen only in half-duplex mode and when the Ethernet segment is congested.Error Message    %DEC21140-5-UNAVAILABLE: %s transmit error Explanation    Late collisions happen when a collision occurs after transmitting the preamble. The packet will be retransmitted but this could indicate that another device is failing to detect when the network is in use.","Verify that both peers are in the same duplex mode.If this recurs, check for malfunctions in other devices on the Fast Ethernet."
"DEC21140","5","UNAVAILABLE","%s transmit timed out","The transmitter for the port adapter's Fast Ethernet port has timed out and caused the transmission of a packet to fail.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DEC21140","5","UNAVAILABLE","Interface %s failed to remove Addr:=%e from HWAF","Removal of hardware address from HWAF failed. We encountered failure because search in the HWAF table failed, for the requested address. Failure should not occur, when interface is not operating in promiscuous mode.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DEC21140","5","UNAVAILABLE","Unit %d, enormous packet received","A packet received via Fast Ethernet was dropped due to excessive size.","Adjust the MTU of the interface if necessary. Otherwise no action is required."
"DEC21140","5","UNAVAILABLE","Unit %d, excessive collisions","A Fast Ethernet packet has been dropped because too many attempts to transmit it were stopped by collisions. This can be caused by a Fast Ethernet segment which is full to capacity or by other equipment on the LAN malfunctioning.","LOG_STD_NO_ACTION"
"DEC21140","5","UNAVAILABLE","Unit %d, jabber timeout","The transmitter for the port adapter's Fast Ethernet port has timed out and caused the transmission of a packet to fail.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DEC21140","5","UNAVAILABLE","Unit %d, late collision error","Late collisions happen when a collision occurs after transmitting the preamble. The packet will be retransmitted but this could indicate that another device is failing to detect when the network is in use.","If this recurs, check for malfunctions in other devices on the Fast Ethernet."
"DEC21140","5","UNAVAILABLE","Unit %d, lost carrier","The Fast Ethernet port lost carrier while transmitting, meaning that it is no longer receiving signals from the LAN. This can be caused by disconnected Fast Ethernet cabling or a transceiver failure.","If the message recurs, check your Fast Ethernet cabling and port adapter first. If the problem cannot be located, follow these directions. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DEC21140","5","UNAVAILABLE","Unit %d, no carrier","The Fast Ethernet port did not find a carrier when preparing to transmit a packet, meaning that it is no longer receiving signals from the LAN. This can be caused by disconnected Fast Ethernet cabling or a transceiver failure.","Check your Fast Ethernet cabling and port adapter. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DFC","1","UNAVAILABLE","DFC in slot %d has incorrect board id of %d","A DFC board should have a correct board ID. Have the board cookie programmed correctly, or try a new board.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DFC","1","UNAVAILABLE","DFC in slot %d has old Tulum version %d when should be %d","A DFC board should have the latest Tulum Version. If the Tulum version is not the latest, then board needs to be updated appropriately.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DFC","1","UNAVAILABLE","DFC in slot %d has old hw rev %d.%d when should be %d.%d","A DFC board should have the latest revision. If the hw revision is not the latest, then board needs to be updated to the printed out version.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DFC_CARRIER","1","UNAVAILABLE","DFC Carrier in slot %d has old hw revision %d.%d when hw revision should be %d.%d.","A DFC carrier card should have the latest revision. If the hw revision is not the latest, then board needs to be updated to the printed out version.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DEV_SELENE","3","DEV_INIT_FAILURE","Selene [dec] initialization failed.","The initailazation of the Selene FPGA device on this linecard failed.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"DEV_SELENE","3","EFIFO_ECC","Selene [dec] Egress [dec] Burst FIFO Read ECC error","A FIFO ECC error condition was detected in a FPGA device on the linecard. This may be caused by a hardware malfunction.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"DEV_SELENE","3","FIFO_ECC","Selene [dec] Ingress [dec] [chars] Priority FIFO Read ECC Error","An ECC Error was detected while reading from a queue in a FPGA device on the linecard. This may be caused by a hardware malfunction.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"DEV_SELENE","3","FIFO_FULL","Selene [dec] Ingress [dec] [chars] Priority FIFO Full","An ingress packet queue full condition was detected in a FPGA device on the linecard. This may be caused by a flow-control misconfiguration due to incorrect software.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"DEV_SELENE","3","FIFO_SEQ","Selene [dec] Egress [dec] Burst FIFO Read Sequence error","A FIFO sequence error condition was detected in a FPGA device on the linecard. This may be caused by a hardware malfunction.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"DEV_SELENE","3","INV_POE","Selene [dec] Egress [dec] Invalid POE error, [hex]","An invalid Port of Exit error condition was detected in a FPGA device on the linecard. This may be caused by incorrect software.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"DEV_SELENE","3","INV_VLAN","Selene [dec] Egress [dec] Invalid Vlan error","An invalid vlan error condition was detected in a FPGA device on the linecard. This may be caused by a software error.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"DEV_SELENE","3","MRX_CRC","Selene [dec] Metropolis Rx [dec] Packet CRC Error","A packet checksum error was detected in a FPGA device on the linecard. This may be caused by a hardware malfunction.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"DEV_SELENE","3","MRX_FCS","Selene [dec] Metropolis Rx [dec] Packet Header Checksum Error","A packet header checksum error was detected in a FPGA device on the linecard. This may be caused by a hardware malfunction.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"DEV_SELENE","3","MRX_GNT","Selene [dec] Metropolis Rx [dec] Giant Packet Error","A giant frame was received in a FPGA device on the linecard. This may be due to incorrect software.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"DEV_SELENE","3","MRX_LEN","Selene [dec] Metropolis Rx [dec] Packet Length Mismatch","An incorrect length was detected for packet received in a FPGA device on the linecard. This may be caused by a hardware malfunction.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"DEV_SELENE","3","MRX_MIN","Selene [dec] Metropolis Rx [dec] Minimum Packet Length Error","A frame smaller than the minimum size was received in a FPGA device on the linecard. This may be due to incorrect software.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"DEV_SELENE","3","MRX_SEQ","Selene [dec] Metropolis Rx [dec] Sequence Error","A sequence error was detected in a FPGA device on the linecard. This may be caused by a hardware malfunction.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"DEV_SELENE","3","SRAM_ECC","Selene [dec] SRAM [chars] [chars] ECC error, error status: [hex]","An ECC error was detected in SRAM memory in a FPGA device on the linecard. This may be caused by a hardware malfunction.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"DEV_SELENE","3","XAUI_CODE","Selene [dec] XAUI [dec] Coding Error","A XAUI lane coding error was detected in a FPGA device on the linecard. This may be caused by a hardware malfunction","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"DEV_SELENE","3","XAUI_CRC","Selene [dec] XAUI [dec] Checksum Error","A XAUI interface checksum error was detected in a FPGA device on the linecard. This may be caused by a hardware malfunction","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"DEV_SELENE","3","XAUI_FRM","Selene [dec] XAUI [dec] Framing error","XAUI interface framing error was detected on a FPGA device on the linecard. This may be caused by a hardware malfunction.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"DEV_SELENE","3","XAUI_GNT","Selene [dec] XAUI [dec] Giant Frame Error","A giant frame was detected in a FPGA device on the linecard. This may be due to incorrect software.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"DEV_SELENE","3","XAUI_LEN","Selene [dec] XAUI [dec] Packet Length Error","A packet with bad length value was detected in a FPGA device on the linecard. This may be caused by incorrect Network Processor software.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"DEV_SELENE","3","XAUI_MIN","Selene [dec] XAUI [dec] Min Packet Size Error","A frame smaller than the minimum allowed size was detected in a FPGA device on the linecard. This may be due to incorrect software.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"DEV_SELENE","3","XAUI_RX_RDY","Selene [dec] XAUI [dec] Rx Rdy changed state","XAUI interface on a FPGA device on the linecard changed receive ready state. This may be caused by a hardware malfunction.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"DEV_SELENE","3","XAUI_SEQ","Selene [dec] XAUI [dec] Sequence Error","A XAUI interface sequence error was detected in a FPGA device on the linecard. This may be caused by a hardware malfunction","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"DEV_SELENE","3","XAUI_TX_ECC","Selene [dec] XAUI [dec] Tx FIFO ECC error","A FIFO queue ECC error was detected in a FPGA device on the linecard. This may be caused by a hardware malfunction.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"DEV_SELENE","3","XAUI_TX_FULL","Selene [dec] XAUI [dec] Tx FIFO Full","A FIFO queue full condition was detected in a FPGA device on the linecard. This may be caused by a hardware malfunction.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"DEV_SELENE","3","XAUI_TX_RDY","Selene [dec] XAUI [dec] Tx Rdy changed state","XAUI interface on a FPGA device on the linecard changed transmit ready state. This may be caused by a hardware malfunction.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"DEV_SELENE","5","FC_CS","Selene [dec] Channel [int] Egress Flow-control Status change","A flow-control status change was detected between a FPGA device and a network processor on the linecard.","No action is required."
"DFP","4","UNAVAILABLE","%s Application did not set pointer","Application passed invalid pointer to DFP subsystem","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DFP","4","UNAVAILABLE","%s Application sent too many values","Application sent too many values to DFP subsystem","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DFP","4","UNAVAILABLE","%s Service has not been registered with DFP.","No such service registered with DFP subystem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DFP","4","UNAVAILABLE","%s security information in CASA packet from manager %i service %s.","Security check failed.","Make sure all CASA/DFP systems are configured with the same password."
"DFP","4","UNAVAILABLE","Could not queue request for %s for service %s","Could not queue request to the DFP process for specific 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DFP","4","UNAVAILABLE","Could not start process for service %s","Could not start DFP Process for service %s","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DFP","4","UNAVAILABLE","Failure binding port %u to socket for service %s.","Problem with call to socket bind.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DFP","4","UNAVAILABLE","Manager %i Service %s - Unknown connection state %u","Unknown connection state processing DFP timer","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DFP","4","UNAVAILABLE","Manager %i: Service %s - Could not parse message","Could not parse message from DFP Manager","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DFP","4","UNAVAILABLE","Manager %i: Service %s - Socket_recv error %d","Socket_recv error receiving message from DFP Manager","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DFP","4","UNAVAILABLE","Manager %i: Service %s - Too many read errors","Too many errors reading message header from DFP Manager","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DFP","4","UNAVAILABLE","Manager %i: Service %s - Unknown message type %u","Message from DFP Manager has unknown type","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DFP","4","UNAVAILABLE","Manager %i:%u - Send failed","Sending a message to DFP Manager failed","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DFP","4","UNAVAILABLE","Process enqueue failed: %s","An unexpected error occurred while enqueueing a DFP element","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DFP","4","UNAVAILABLE","Service %s - Listen failed","Listen for DFP Manager failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DFP","4","UNAVAILABLE","Service %s - attempted to register before DFP Subsytem is up.","Problem with order of subsystem initialization.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DFP","4","UNAVAILABLE","Service %s is already intialized, cannot re-initialize","The application has atempted to re-initialize a service","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DFP","4","UNAVAILABLE","The DFP packet is too small from manager %i service %s.","A DFP packet has been received that is too small.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DFP","4","UNAVAILABLE","The string %s exceeds 15 characters - too long for service name.","The user input a service string that exceeds 15 characters","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DHCPD","2","UNAVAILABLE","DHCP could not open UDP port %u.","DHCP could not open UDP port 67 (bootps).","Check if another application is using UDP port 67. If the port is available, add more memory."
"DHCPD","2","UNAVAILABLE","DHCP could not start its %s process.","DHCP could not start one of its processes.","Add more memory."
"DHCPD","2","UNAVAILABLE","DHCP has detected a deadlock condition (excessive read failures).","The DHCP server could not read bindings from any database agent. All read attempts have failed. To prevent a possible deadlock, the server has made all pool addresses available for assignment.","Verify that all URLs are correct and connectivity exists between the server and all database agents. Check for corrupt database files. All files must contain the *time* and *end* keywords. Execute the command, show ip dhcp database. If there are aborted file transfers, increase the appropriate timeouts. Restart the DHCP server."
"DHCPD","2","UNAVAILABLE","Recvmsg failed unexpectedly. DHCP services have been terminated.","Reason for failure is unknown.","Copy the error message exactly as it appears, and report it to your technical support representative."
"DHCPD","2","UNAVAILABLE","There is inadequate memory for DHCP services.","DHCP could not allocate mandatory data structures.","Add more memory."
"DHCPD","3","UNAVAILABLE","DHCP could not read bindings from %s.","The DHCP server could not read bindings from the specified database agent.","Verify that the URL is correct and connectivity exists between the server and database agent. Check for a corrupt database file. The file must contain the *time* and *end* keywords. Execute the command, show ip dhcp database. If there are aborted file transfers, increase the database transfer timeout."
"DHCPD","3","UNAVAILABLE","DHCP could not write bindings to %s.","The DHCP server could not write bindings to the specified database agent.","Verify that the URL is correct and connectivity exists between the server and database agent. Execute the command, show ip dhcp database. If there are aborted file transfers, increase the database transfer timeout."
"DHCPD","4","UNAVAILABLE","DHCP address conflict: client %s declined %I.","The DHCP client has detected an address conflict. Another host is using the specified IP address. After resolving the conflict, execute the command, clear ip dhcp conflict.","Resolve the misconfiguration. Clear the conflict from the DHCP database."
"DHCPD","4","UNAVAILABLE","DHCP address conflict: server pinged %I.","The DHCP server has detected an address conflict. Another host is using the specified IP address. After resolving the conflict, execute the command, clear ip dhcp conflict.","Resolve the misconfiguration. Clear the conflict from the DHCP database."
"DHCPD","4","UNAVAILABLE","DHCP will run as a relay agent only.","DHCP could not start its database process. The server component has been disabled. Only the relay agent is active.","Add more memory."
"DHCP_SNOOPING","3","DHCP_SNOOPING_INTERNAL_ERROR","DHCP Snooping internal error, [chars]","A software verification test failed in the DHCP snooping process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DHCP_SNOOPING","4","AGENT_OPERATION_FAILED","DHCP snooping binding transfer failed. [chars]","This message provides the reason for failure when a database transfer has failed.","No action is required."
"DHCP_SNOOPING","4","AGENT_OPERATION_FAILED_N","DHCP snooping binding transfer failed([dec]). [chars]","This message provides the reason for failure when a database transfer has failed. This log message is rate limited.","No action is required."
"DHCP_SNOOPING","4","DHCP_SNOOPING_ERRDISABLE_WARNING","DHCP Snooping received [dec] DHCP packets on interface [chars]","DHCP Snooping detected a DHCP packet rate limit violation on a particular interface. The interface will be error disabled.","No action is required."
"DHCP_SNOOPING","4","IP_SOURCE_BINDING_PVLAN_WARNING","IP source filter may not take effect on secondary vlan [dec] where IP source binding is configured. [chars]","If the private VLAN feature is enabled, the IP source filter on the primary VLAN will automatically propagate to all secondary VLANs.","No action is required."
"DHCP_SNOOPING","4","QUEUE_FULL","Fail to enqueue DHCP packet into processing queue: [chars], the queue is most likely full and packet will be dropped.","DHCP packets are coming into the CPU at a much higher rate than the DHCP snooping process can handle them. These unhandled DHCP packets will be dropped to prevent system from denial of service attack.","No action is required."
"DHCP_SNOOPING","4","SSO_SYNC_ACK_ERROR","Error is encountered in processing acknowledgement for DHCP snooping binding sync, %s. ack message txn id: 0x%x","An error occurred in handling the acknowledgement of DHCP snooping binding synchronization. This message is usually caused by the ACK message being ignored.","No action is required."
"DHCP_SNOOPING","4","STANDBY_AGENT_OPERATION_FAILED","DHCP snooping binding transfer failed on the Standby Supervisor. %s","This message provides the reason of failure when a database transfer has failed on the standby supervisor.","No action is required."
"DHCP_SNOOPING","5","DEST_NOT_FOUND","%s: Could not find destination port. Destination MAC %e","The switch is unable to determine the destination port for a DHCP reply. This message may be an indication of a malicious user connected to the port.","Using debug commands, identify the users that are attached to the port. Enter the debug ip dhcp snooping mac-addr command, where mac-addr is the MAC address shown in the error message. Any subsequent DHCP packet that is received with mac-addr as the source MAC or DHCP CHADDR (client hardware address) will cause a message to appear on the console indicating the port from which the packet originated. If the error message recurs, check the user connected to the port indicated in the debug message."
"DHCP_SNOOPING","6","AGENT_OPERATION_SUCCEEDED","DHCP snooping database [chars] succeeded.","The given binding transfer has succeeded. This message is logged only once after some failure to indicate that the switch has recovered from failures.","No action is required."
"DHCP_SNOOPING","6","BINDING_COLLISION","Binding collision. [dec] bindings ignored","The given number of bindings from the database file have been ignored when the file is read. The bindings are ignored because the system has a binding for the given MAC address and VLAN combination by the time the switch read the ignored binding from the file.","No action is required."
"DHCP_SNOOPING","6","INTERFACE_NOT_VALID","Interface not valid. [dec] bindings ignored.","The given number of bindings from the database file have been ignored when the file is read. The bindings are ignored because the interface specified by the ignored binding either does not exist in the system or it's a router or DHCP snooping trusted port.","No action is required."
"DHCP_SNOOPING","6","LEASE_EXPIRED","Lease Expired. [dec] bindings ignored.","The specified number of bindings from the database file have been ignored when the file is read. The bindings are ignored because their lease has expired.","No action is required."
"DHCP_SNOOPING","6","PARSE_FAILURE","Parsing failed for [dec] bindings.","The specified number of bindings from the database file have been ignored when the file is read. The bindings are ignored because of parsing failures.","No action is required."
"DHCP_SNOOPING","6","VLAN_NOT_SUPPORTED","Vlan not supported. [dec] bindings ignored.","The specified number of bindings from the database file have been ignored when the file is read. The bindings are ignored because the VLAN specified by the ignored binding no longer exists in the system.","No action is required."
"DHCP_SNOOPING_CAT3550","3","MVR_INSTALL","Cannot install [chars] ACLs for DHCP Snooping, probably no TCAM space","There is insufficient space in the TCAM to install the specified ACLs for DHCP snooping.","Reduce the number of PACLs or VACLs to make space in the TCAM."
"DHCP_SNOOPING_CAT3550","3","UNEXPECTED_EVENT","Process received unknown event (major [hex], minor [hex]).","A process can register to be notified when various events occur in the router. This message indicates that a process received an event it did not know how to handle.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DHCP_SNOOPING_ISSU","2","GET_BUFFER","DHCP Snooping ISSU client failed to get buffer for message. Error: %d (%s)","The DHCP snooping ISSU client failed to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"DHCP_SNOOPING_ISSU","2","INIT","DHCP Snooping ISSU client initialization failed to %s. Error: %d (%s)","The DHCP snooping ISSU client could not be initialized. This initialization failure must be addressed before an in-service software upgrade or downgrade can be performed successfully. Otherwise, a software upgrade or downgrade will result in downtime.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DHCP_SNOOPING_ISSU","2","SEND_NEGO_FAILED","DHCP Snooping ISSU client failed to send negotiation message. Error: %d (%s)","The DHCP snooping ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"DHCP_SNOOPING_ISSU","2","SESSION_NEGO","DHCP Snooping ISSU client encountered unexpected client nego_done. Error: %d (%s)","An ISSU-compliant client transitions through a series of internal states. The DHCP snooping ISSU client encountered a 'client negotiation done' state that was unexpected. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"DHCP_SNOOPING_ISSU","2","SESSION_REGISTRY","DHCP Snooping ISSU client failed to register session information. Error: %d (%s)","The DHCP snooping ISSU client failed to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"DHCP_SNOOPING_ISSU","3","INVALID_SESSION","DHCP Snooping ISSU client does not have a valid registered session.","The DHCP snooping ISSU client does not have a valid registered session.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"DHCP_SNOOPING_ISSU","3","MSG_NOT_OK","DHCP Snooping ISSU client 'Message Type %d' is not compatible","The DHCP snooping ISSU client received an incompatible message from the peer device. The message cannot be processed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"DHCP_SNOOPING_ISSU","3","MSG_SIZE","DHCP Snooping ISSU client failed to get the MTU for Message Type %d. Error: %d (%s)","The DHCP snooping ISSU client was unable to calculate the MTU for the specified message. The DHCP snooping ISSU client is not able to send the message to the standby device.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"DHCP_SNOOPING_ISSU","3","SESSION_UNREGISTRY","DHCP Snooping ISSU client failed to unregister session information. Error: %d (%s)","The DHCP snooping ISSU client failed to unregister session information.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"DHCP_SNOOPING_ISSU","3","TRANSFORM_FAIL","DHCP Snooping ISSU client %s transform failed for 'Message Type %d'. Error: %d (%s)","The DHCP snooping ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In either case, the DHCP snooping state between the active device and the standby device is not identical.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"DHCPV6C","3","NOPACKET","Cannot setup or duplicate a socket packet","An error occurred that is probably related to a resource problem within the system.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"DHCPV6C","3","NOSOCKET","Cannot create DHCPv6 client socket","A DHCPv6 socket could not be created. This error is probably the result of either IP not being enabled on any interface or a resource problem with the system.","Enable IP on the interface. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"DHCPV6S","3","DBNOTLOADED","Binding database not loaded","A DHCPv6 binding database could not be loaded.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DHCPV6S","3","DBOPEN","Openning [chars]: [chars]","A DHCPv6 binding database file could not be opened.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DHCPV6S","3","DBREAD","Reading file: [chars]","A DHCPv6 binding database file could not be read.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DHCPV6S","3","DBWRITE","Writing file: [chars]","The system could not write to a DHCPv6 binding database file.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DHCPV6S","3","NOPACKET","Cannot setup or duplicate a DHCPv6 server socket packet","An error occurred that is probably due to a resource problem within the system.","No action is required."
"DIAG","3","ALWAYS_ENABLE_TEST","[chars]: The users are not allow to disable monitoring for Test #[dec]","The specified health monitoring test cannot be disabled.","No action is required. The system is working properly."
"DIAG","3","FIXED_INTERVAL_TEST","[chars]: The users are not allow to change monitoring interval of Test #[dec]","The specified health monitoring test interval cannot be changed.","No action is required. The system is working properly."
"DIAG","3","INVALID_DEVICE","Invalid device number : [chars]","The system made a diagnostics request on a device that does not exist.","Ensure that the specified device number exists and is valid."
"DIAG","3","INVALID_MONITORING_INTERVAL","[chars]: The [chars][ID=[dec]] monitoring interval must be at least [dec] millisec","The specified test monitoring interval is too small.","No action is required. The system is working properly."
"DIAG","3","INVALID_TEST","Invalid test: [chars]","A test that does not exist was requested. [chars] describes the test.","Ensure the specified test is supported by the switching module. The list of available tests and their associated test IDs can be retrieved using the show diagnostic content command."
"DIAG","3","MONITOR_DISABLE","[chars]: The monitoring test:[dec] is disable since default interval is Zero","The specified test is no longer a health-monitoring test.","No action is required. The system is working properly."
"DIAG","3","MONITOR_INTERVAL_ZERO","[chars]: Monitoring interval is 0. Cannot enable monitoring for Test #[dec]","The system cannot enable health monitoring for the specified test because the interval is set to zero.","Reset the health monitoring interval for the test, and reenable health monitoring."
"DIAG","3","NOT_MONITORING_TEST","[chars]: The test:[dec] cannot be used as health monitoring test","The specified test is not a health-monitoring test.","No action is required. The system is working properly."
"DIAG","3","TEST_SKIPPED","[chars]: [chars]{ID=[dec]} is skipped","The diagnostic test cannot be run.","No action is required. The system is working properly."
"DIAG","4","CONFIG_REAPPLY","Please reapply config command [chars] after the card is online.","This message appears when the specified configuration command cannot be applied. [chars] is the configuration command that you must reapply.","The system is working properly and the specified command cannot be applied. Reapply the configuration command after the module is online."
"DIAG","6","SCHEDULE_IS_REMOVED","[chars]: Schedule Diagnostic for [[chars] [chars] [dec]:[dec].] is removed","The scheduled online diagnostics test was removed because the test is no longer applicable.","No action is required. The system is working properly."
"DIAG","6","SIMULATED_TEST_RESULT","[chars]: [chars] test result is simulated.","The result of the specified test is simulated. The message does not indicate a software or hardware fault. The first [chars] is the message notification and the second [chars] is the test name.","No action is required. The test failure is simulated as specified by the user."
"DIAG","6","SKIP_ONDEMAND_ACTIVE_TO_STANDBY_TEST","[chars]: [chars] cannot be executed.","The diagnostics test is bypassing the specified redundant test because the redundant test cannot be executed.","No action is required. The system is working properly."
"DIAG","6","TEST_SKIPPED_FROM_ACTIVE","[chars]: [chars] cannot be executed from active supervisor.","The specified test cannot be run from the active supervisor engine.","No action is required. The test cannot be run, but the system is working properly."
"DIALER","2","UNAVAILABLE","Dialer count 0 on %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DIALER","2","UNAVAILABLE","No software interface associated with hw interface %s","An internal software error occurred.","Call your technical support representative and report the error message, the system version, and the router configuration. (Use the show version command to obtain the software version.)"
"DIALER","2","UNAVAILABLE","Unexpected null pointer in %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DIALER","4","UNAVAILABLE","Current MTU setting of %d on %s is being overwritten by setting of %d defined by %s.","This is a warning message indicating that an interface setting is changed based on a dialer rotary group memebership.","LOG_STD_NO_ACTION"
"DIALER","6","UNAVAILABLE","Interface %s bound to profile %s","This is a status message indicating that a dialer interface has been bound to a dialer profile.","LOG_STD_NO_ACTION"
"DIALER","6","UNAVAILABLE","Interface %s unbound from profile %s","This is a status message indicating that a dialer interface has been unbound to a dialer profile.","LOG_STD_NO_ACTION"
"DIALPEER_DB","3","UNAVAILABLE","Addition of dial-peers limited by available memory","The available memory does not permit the addition of more dial-peers.","Increase the processor memory in order to be able to add more dialpeers."
"DIALPEER_DB","3","UNAVAILABLE","Addition of dial-peers limited by platform","This platform does not permit the addition of more dial-peers.","Reduce the number of dial-peers in your numbering plan."
"DIALPEER_DB","6","UNAVAILABLE","Addition of too many dial-peers may affect performance","The number of dial-peers is high. This will have an effect on the dial-peer lookup time, resulting in longer call setup time.","Use the minimum number of dial-peers necessary for your numbering plan."
"DIALSHELF","2","UNAVAILABLE","%s slot %d after %d secs in state '%s'","The specified dial shelf slot timed out as per the message. Either a software or a hardware component has failed.","Try removing and reinserting the card. If that does not help, try a different card. If problem persists, contact your technical support representative."
"DIALSHELF","2","UNAVAILABLE","Card type %d in slot %d","The software does not have a driver for the card in specified slot.","Copy the error message exactly as it appears, and report it to your technical support representative."
"DIALSHELF","2","UNAVAILABLE","DSC in slot %d changes state to down.","DSC in dial shelf went down.","Try to bring up that DSC by 1) Check LCD and LEDs of the DSC. 2) Check RS DSC connection. If none of above works, please report it to your technical support representative."
"DIALSHELF","3","UNAVAILABLE","%s (%d)","The router shelf received an invalid message from the DSC in the dial shelf. This is a software error or compatibility issue. Check the software versions on the router shelf and the DSC.","Copy the error message exactly as it appears, and report it to your technical support representative."
"DIALSHELF","3","UNAVAILABLE","Invalid change from %s (%d) to %s (%d) for slot %d","The software detected an invalid state change for the specified slot. This is a software error.","Copy the error message exactly as it appears, and report it to your technical support representative."
"DIALSHELF","3","UNAVAILABLE","Unknown event %d for slot %d","The software generated an unknown event for the specified slot. This is a software error.","Copy the error message exactly as it appears, and report it to your technical support representative."
"DIALSHELF","3","UNAVAILABLE","Unknown message type %d from DSC","The router shelf received an unknown message from the DSC in the dial shelf. This is a software error or compatibility issue. Check the software versions on the router shelf and the DSC.","Copy the error message exactly as it appears, and report it to your technical support representative."
"DIALSHELF","4","UNAVAILABLE","Number of %s may exceed recommended configuration","On NPE200 more than one CT3 or more than two T1/E1 are installed, this exceeds the recommended configuration.","Stay within recommended limit of CT3/T1/E1, or install split dial-shelf configuration or upgrade router-shelf to NPE300."
"DIALSHELF","6","UNAVAILABLE","Reload requested for card in shelf %d slot %d.","The command 'hw-module slot / reload' was entered. This is a confirmation that the command is being processed.","None"
"DIGISIGN","2","UNAVAILABLE","%%CRITICAL: System identified a mismatch between the show version output and the key type used in signing. %s is a signed %s software","System identified a mismatch in software type.This might be a modified software.","Do not use this file. The file might be corrupted or modified.Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, and contact your Cisco technical support representative with the image and version information you have gathered."
"DIGISIGN","3","UNAVAILABLE","%%ERROR: Failure in processing signature envelope for system image: %s","The loaded Cisco IOS software image has an invalid digital signature envelope.A valid digital signature envelope ensures the integrity of the image.The loaded Cisco IOS software image might be corrupted or modified.The failure type is one of the following: (1) Signature envelope version is not supported (2) Duplicate entries are found in signature envelope (3) Signature envelope is incomplete (4) Invalid image type (5) Invalid length in signature envelope (6) Invalid pad bytes (7) Invalid signature length (8) Unable to allocate memory (9) Invalid type in signer ID (10) Invalid signer ID length (11) Unknown signature algorithm (12) Invalid key type","Do not use this file. The file might be corrupted or modified.Please attempt to copy the file again, or download the file again from the http://www.cisco.com page before copying it.If you continue to get this error message, open a case withthe Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, and contact your Cisco technical support representative with the image and version information you have gathered."
"DIGISIGN","3","UNAVAILABLE","%%ERROR: No keys found for verifying the digital signature in file %s","No keys found in the device key storage for validating the digital signature. A valid key is needed to validate the digital signature in the image.","The device does not have a vlaid key to verify the digitalsignature. Open a case with the Technical Assistance Centervia the internet athttp://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, and contact your Cisco technical support representative with the information you have gathered."
"DIGISIGN","3","UNAVAILABLE","Cannot verify %s, as it is signed with development key","The software image cannot be verified becauseit is signed with a development key.","To allow booting a development-signed image, use thesoftware authenticity development command"
"DIGISIGN","4","UNAVAILABLE","%%WARNING: Digital signature is not found in file %s","The specified image file does not have a digital signature. Only Cisco IOS Software Images are digitally signed. If you enter verify, copy, or reload command, and the specified file is not a digitally signed Cisco IOS Software Image the system displays this warning message because the file does not have a signature. A valid digital signature ensures the integrity of the image.","If the specified file is an unsigned Cisco IOS Software image be cautious when deciding whether or not to use this file. The system will not boot using this image."
"DIGISIGN","4","UNAVAILABLE","%%WARNING: Digital signature verification failed for file %s: %s","Validation failure due to invalid key while verifying the digital signature.","Do not use this file. The file might be corrupted or modified. Please attempt to copy the file again, or download the file again from the http://www.cisco.com page before copying it. If you continue to get this error message, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, and contact your Cisco technical support representative with the device information you have gathered."
"DIGISIGN","4","UNAVAILABLE","%%WARNING: Digital signature verification failed for file %s: %s","Validation failure while verifying the digital signature.","Do not use this file. The file might be corrupted or modified. Please attempt to copy the file again, or download the file again from the http://www.cisco.com page before copying it. If you continue to get this error message, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, and contact your Cisco technical support representative with the information you have gathered."
"DIGISIGN","4","UNAVAILABLE","%s signed with development key will not be booted","With this configuration enabled, the system will be unable to boot software that is signed with a development key.","Use the [no] form of this configuration (no software authenticity development)to correct the condition."
"DIGISIGN","6","UNAVAILABLE","%s","System identified a key version mismatch between the key whichwas used to sign the image and the keys stored on the device","If the image is signed with a key version newer than the devicekeys, then follow the procedure for key revocation, which iswhich is documented at cisco.com. If the image is signed with akey version that is now obsolete, please obtain the latest signedcopy of this image from cisco.com."
"DIRECTOR","3","UNAVAILABLE","%s can not create ip alias","Most likely a resource problem within the system.","Reboot the system as soon as possible. If the problem continues to occur, report it to your technical support representative."
"DIRECTOR","3","UNAVAILABLE","%s port in use","The IP address requested has been found to be already in use on some interface connected to the system or within the system itself.","Either select another IP address for use, or locate the system making use of this address and reconfigure it to use another."
"DIRECTOR","3","UNAVAILABLE","%s unable to create socket","A software or hardware error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"DIRECTOR","3","UNAVAILABLE","%s unable to write to socket","A software or hardware error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"DIRECTOR","3","UNAVAILABLE","DRP %i was down %TE ago in the last %d minute period ! There may be problems related to this DRP agent.","The remote DRP agent has not responded within the time period reported","Make sure the remote DRP agent is running and that it is accessible from the system reporting the problem."
"DIRECTOR","3","UNAVAILABLE","Excessive HTTP request overloading: dropping HTTP req from .","HTTP requests are overloading the web redirector","Web redirector is automatically discarding HTTP request traffic."
"DIRECTOR","3","UNAVAILABLE","Metric %s referenced but not found Error Message    %DIRECTOR-3-UNAVAILABLE: Server error ('%s'), Code %d - %s","The HTTP return code indicates a server failure error","Check the URL configured. Check the configured HTTP server."
"DIRECTOR","3","UNAVAILABLE","URL is elsewhere ('%s'), Code %d - %s","The HTTP return code indicates the page is not actually on this server","Check the URL configured. Check the configured HTTP server."
"DIRECTOR","3","UNAVAILABLE","plug-in returned orphan status","A software or hardware error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"DIRECTOR","3","UNAVAILABLE","unable to create %s process","Most likely a resource problem within the system.","Reboot the system as soon as possible. If the problem continues to occur, report it to your technical support representative."
"DIRECTOR","5","UNAVAILABLE","server %i (on port %d) has gone %s","The remote server has gone up or down","None."
"DIRECTOR","6","UNAVAILABLE","answer type %s host %s cli %i id# %d none","DNS reply logging: no server found.","None."
"DIRECTOR","6","UNAVAILABLE","answer type %s host %s cli %i id# %d svr %i","DNS reply logging with server found.","None."
"DIRECTOR","6","UNAVAILABLE","no answer for (host %s cli %i type %s id# %d) %s","No server found.","None."
"DIRECTOR","6","UNAVAILABLE","query type %s host %s cli %i id# %d","DNS query logging.","None."
"DIRECTOR","6","UNAVAILABLE","select %i (host %s cli %i type %s id# %d) %s","Report server selection process.","None."
"DLC","2","UNAVAILABLE","no memory for %s","There was not enough free memory to complete the operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DLC","3","UNAVAILABLE","Close Station, invalid P_CEP","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DLC","3","UNAVAILABLE","Function %s: value %#x passed in parameter %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DLC","3","UNAVAILABLE","unknown port type %x","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DIAG-SP","6","DIAG_OK","%s: Passed %s","The diagnostic tests did not detect any error on the card.","This is an informational message stating that the line card passed the diagnostic tests."
"OIR-SP","6","DOWNGRADE_EARL","Module %d %s installed is not identical to system PFC and will perform at current system operating mode.","The PFC/DFC module is at a higher hardware revision than the level of the system PFC. The PFC/DFC module will operate at the same level as that of the system PFC.","No action is required."
"DIAG-SP","6","RUN_MINIMUM","%s: Running Minimal Diagnostics...","Minimum Diagnostic is running on the card","This is an informational message and the system is working properly."
"DLSWC","3","UNAVAILABLE","%s %d","A data-link switching system error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DLSWC","3","UNAVAILABLE","%s Bad clsi SAP id = %x %s","A data-link switching system error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DLSWC","3","UNAVAILABLE","%s","A data-link switching system error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DLSWC","3","UNAVAILABLE","%s","A data-link switching system error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DLSWC","3","UNAVAILABLE","%s Invalid confirm %s %s","A data-link switching system error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DLSWC","3","UNAVAILABLE","%s Invalid indication %s, %s","A data-link switching system error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DLSWC","3","UNAVAILABLE","%s Invalid ret code (0x%x) %s, %s","A data-link switching system error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DLSWC","3","UNAVAILABLE","%s primitive not valid for dlsw %s %s","A data-link switching system error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DLSWC","3","UNAVAILABLE","SSP OP = %d(%s) %s from %s","A Silicon Switch Program (SSP) frame was received from the remote peer.","LOG_STD_NO_ACTION"
"DLSWC","3","UNAVAILABLE","SSP OP = %d(%s) %s to %s %s","A Silicon Switch Program (SSP) frame was sent to the remote peer.","LOG_STD_NO_ACTION"
"DLSWC","3","UNAVAILABLE","bad peer op in peer_to_core %d","A data-link switching system error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DLSWC","3","UNAVAILABLE","bad ssp hdr in proc ssp - %s = 0x%x","A Silicon Switch Processor (SSP) header received from the remote peer contains errors in one of the fields.","If the remote peer is a nonCisco router, confirm that it supports the DLSw RFC 1795 standard."
"DLSWMasterSlave","3","UNAVAILABLE","%s %x from %e","DLSw Master-Slave Error","LOG_STD_NO_ACTION"
"DLSWMasterSlave","3","UNAVAILABLE","%s","DLSw Master-Slave Error","LOG_STD_NO_ACTION"
"DLSWMasterSlave","3","UNAVAILABLE","%s from %e","DLSw Master-Slave Error","LOG_STD_NO_ACTION"
"DLSWMasterSlave","3","UNAVAILABLE","%s, %s","DLSw Master-Slave Error","LOG_STD_NO_ACTION"
"DLSWMasterSlave","3","UNAVAILABLE","%s: %s","DLSw Master-Slave Error","LOG_STD_NO_ACTION"
"DLSWMasterSlave","3","UNAVAILABLE","%s: %s from %e","DLSw Master-Slave Error","LOG_STD_NO_ACTION"
"DLSWMasterSlave","3","UNAVAILABLE","%s: %s to %e","DLSw Master-Slave Error","LOG_STD_NO_ACTION"
"DLSWP","3","UNAVAILABLE","%s %d; %s","The largest frame size configured in the DLSW remote peer definition is being changed because the MTU size configured on the interface, used by DLSW, is less than the configured value of the largest frame on DLSW remote peer definition. The largest frame size is being changed to that configured on the interface.","If you wish to use this largest frame size for DLSW, increase the MTU on the interface to a value larger than the configured largest frame size."
"DLSWP","3","UNAVAILABLE","%s %s","A DLSW peer failed: - keepalive failure, dlsw between cisco peers is sending a peer keepalive by default every 30 sec. After missing 3 consecutive keepalives the peer is taken down. - We are not promiscuous, Rej conn from peer a.b.c.d The local dlsw peer is not configured for promiscuous and we receive a request to open a dlsw peer for which we have no corresponding dlsw remote peer statement. - received tcp fini, dlsw peer code has received a tcp fini from the underlaying tcp subsystem. To obey the tcp fini dlsw wring bring down the peer connection for which the tcp fini was received.","- keepalive failure Check end to end connectivity between the DLSW peers - We are not promiscuous, Rej conn from peer a.b.c.d correct your configuration. - received tcp fini, Check the underlaying tcp connection between the two dlsw peers."
"DLSWP","3","UNAVAILABLE","%s","A general error condition was detected as described in the message text. This error should not cause any network problems unless it happens repeatedly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DLSWP","3","UNAVAILABLE","%s: %s","Priority keyword was used on one router but not on the other. The priority keyword is an option on the DLSW remote peer definition. If priority keyword is used on one router, it must be used on the other.","If you wish to use prioritization, use it on both routers."
"DLSWP","3","UNAVAILABLE","%s: invalid %s %d","A bad parameter value was passed to function chars1 - invalid parameter chars2 with value. This error should not cause any network problems unless it happens repeatedly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DLSWP","3","UNAVAILABLE","No memory to %s","The router ran out of system memory for operation, as described in the message text. Most likely, the router image requires more system memory (RAM) than the router contains.","Consult with your Cisco technical support representative about memory requirements for a specific image."
"DLSWP","3","UNAVAILABLE","passive open failed from %i(%d) - %d","The system does not have enough main memory (RAM) for TCP to allocate the data structures required to accept an incoming TCP connection. Most likely, the router image requires more system memory (RAM) than the router contains.","Consult with your Cisco technical support representative about memory requirements for a specific image."
"DLSWP","3","UNAVAILABLE","uninitalized peer %s from %i(%d) to %i(%d)","DLSw received a packet on an uninitialized peer connection.","Verify configuration and DLSw peer status on both routers."
"DLSWP","5","UNAVAILABLE","%s %s","A DLSW peer is either connected or disconnected","None, informational message only."
"DMA","1","UNAVAILABLE","DRQ stalled. Dumping DRQ.","The path from VIP to backplane has stalled. The DRQ table is being dumped for debugging","Copy the error message exactly as it appears, and report it to your technical support representative. If possible also provide the hex dump following this message"
"DMA","1","UNAVAILABLE","Empty packet is being sent to backplane. particle_ptr=%#x","drq_io receives a packet that has particle count 0. coding error -- hurt performance","Copy the error message exactly as it appears, and report it to your technical support representative. If possible also provide the show log on the reporting VIP"
"DMA","1","UNAVAILABLE","Giant detected; size %d","This error message appears only in custom built images when a sanity check fails. A packet that was too large was sent over the backplane by a VIP.","Copy the error message exactly as it appears, and report it to your technical support representative. If possible also provide the output of show tech."
"DMA","1","UNAVAILABLE","Not enough pci memory left over for DMA","Misconfiguration has resulted in overutilization of PCI memory","Copy the error message exactly as it appears, and report it to your technical support representative. If possible also provide the output of show diag and show controller cbus"
"DMA","1","UNAVAILABLE","Not enough processor memory left over for DMA","Misconfiguration has resulted in overutilization of memory","Copy the error message exactly as it appears, and report it to your technical support representative. If possible also provide the output of show diag and show controller cbus"
"DMA","3","UNAVAILABLE","pak not cleaned up by Egress processing (appId %d)","After dtq dispatched a packet to Egress processing, packet is not cleaned up by application","Copy the error message exactly as it appears, and report it to your technical support representative. If possible also provide the show log on the reporting VIP"
"DMB","0","UNAVAILABLE","%s","DMB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DMA","3","DTQ_DISPATCH_DIRTY_PAK","pak not cleaned up by Egress processing (appId [dec])","After DTQ dispatched a packet to egress processing, the packet was not cleaned up by the application.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. If possible, also provide the show log on the reporting VIP."
"DMB","0","DMB_EMERG","%s","An internal error occurred in the Dynamic Message Broker (DMB).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DMB","1","DMB_ALERT","%s","An internal error occurred in the Dynamic Message Broker (DMB).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DMB","2","DMB_CRIT","%s","An internal error occurred in the Dynamic Message Broker (DMB).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DMB","3","DMB_ERR","%s","An internal error occurred in the Dynamic Message Broker (DMB).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DMB","4","DMB_WARNING","%s","An internal error occurred in the Dynamic Message Broker (DMB).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DMB","5","DMB_NOTICE","%s","An internal error occurred in the Dynamic Message Broker (DMB).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DMB","6","DMB_INFO","%s","This message displays information from the Dynamic Message Broker (DMB).","No action is required."
"DMB","7","DMB_ASSERT","Assertion Failure ( %s @%s:%d ) : %s","An internal error occurred in the Dynamic Message Broker (DMB).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DMTDSL","1","UNAVAILABLE","DMTDSL(%d/%d), Init failed, %s","The ADSL network module hardware may be bad","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DMTDSL","3","UNAVAILABLE","DMTDSL(%d/%d), Could not find ATM interface.","The DSL network module hardware may be bad","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DMTDSL","3","UNAVAILABLE","DMTDSL(%d/%d), Hardware failed self test","The DSL chipset failed its self test","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DMTDSL","3","UNAVAILABLE","DMTDSL(%d/%d), Out of memory","The router does not have enough memory installed to run this image","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DMTDSL","3","UNAVAILABLE","DMTDSL(%d/%d),interface not initialized.","The ATM network module hardware may be bad","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DMTDSL","3","UNAVAILABLE","DMTDSL, Could not find ATM interface.","The DSL network module hardware may be bad","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DNET","3","UNAVAILABLE","Hello type %x for my address from %d.%d via %s","The system is receiving its own DECnet packets. Either a serial line is looped back or another host with the same DECnet address is already present on the LAN.","Check the serial lines (if present) and the DECnet configuration."
"DNET","4","UNAVAILABLE","Map entry %d.%d conflicts with adjacency to %d.%d","Your DECnet configuration is incorrect. A host that is specified as nonlocal is present on your local network.","Correct the configuration. Call your technical support representative if you need assistance."
"DNSSERVER","3","UNAVAILABLE","Bad DNS query from %i","A client sent a DNS query to the server which has been found to be incorrectly formatted.","Check the DNS server and the network attached to it."
"DNSSERVER","3","UNAVAILABLE","Can't initialize DNS server","Internal problems with initializing ports for the DNS server","Make sure the DNS server port is available on the local machine."
"DNSSERVER","3","UNAVAILABLE","DNS query from %i too short","A client sent a short DNS query packet to the server","Check the client and the network attached to it."
"DNSSERVER","3","UNAVAILABLE","Low available memory: dropping  from .","There is not enough free memory to handle DNS queries.","DNS server is automatically discarding DNS request traffic."
"DNSSERVER","3","UNAVAILABLE","Low available memory: dropping TCP request from .","There is not enough free memory to handle DNS queries.","DNS server is automatically discarding DNS request traffic."
"DOSFS","3","UNAVAILABLE","%s %s","disk could not be reset while the system is initiated reload. This will cause a transient disk error, disk timeout error, when the ROMMON initialization code tries to reads the DIB.This is a transient error and the system will be able to access the disk and continue normal operation.","LOG_STD_NO_ACTION"
"DOSFS","3","RESETERR","[chars] [chars]","The disk could not be reset while the system has initiated reload. A transient disk error or disk timeout error will occur when the ROMMON initialization code tries to reads the device information block. This is a transient error and the system will be able to access the disk and continue normal operation.","No action is required."
"DOSFS","4","DFS_FSCK_ERR","Error while running fsck on the file [chars].","The file system consistency check (fsck) program became stuck in a loop while walking through the cluster chain of a file and has aborted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DOSFS","5","DFS_CLOSE_ERR","Error during close of the file [chars]. [chars]","An error occurred during a file-close operation.","Enter the fsck filesystem prefix: command to check and attempt to repair the disk. If this does not fix the problem, format the disk."
"DOSFS","5","DIBERR","[chars] [chars]","The system cannot boot an image from the flash disk because the device information block (DIB) is different. The flash disk can be read by the router, but will require formatting by the router before an image can be booted from it.","Follow any instructions provided in the error message. Before storing an image to the flash disk and trying to boot from this device, enter the format command to format the flash disk from the router. Copy the desired image to the flash disk and boot from the device."
"DOT1AD","4","DOT1QTUNNEL_PORT","Port %s is a dot1q-tunnel port, it conflicts with Dot1ad configuration","IEEE 802.1ad configuration cannot coexist with 802.1q tunnel ports.","Disable the 802.1q tunnel configuration on the ports before enabling 802.1ad."
"DOT1AD","4","DOT1X_PORT","Port %s is configured for DOT1X, it conflicts with Dot1ad configuration","IEEE 802.1ad configuration cannot coexist with 802.1X enabled ports.","Disable the 802.1X configuration on the ports before enabling 802.1ad."
"DOT1AD","4","ETHERTYPEMISMATCH_PORT","Port %s ethertype cannot be changed to Dot1ad ethertype, it conflicts with Dot1ad configuration","The Ethertype on the port cannot be changed to 802.1ad Ethertype.","Replace the module with a unit that supports Ethertype change, or power down the module before enabling 802.1ad."
"DOT1AD","4","L2PT_PORT","Port %s is a l2protocol-tunnel port, it conflicts with Dot1ad configuration","IEEE 802.1ad configuration cannot coexist with a Layer 2 protocol tunnel port.","Disable the Layer 2 protocol tunnel configuration on the port before enabling 802.1ad."
"DOT1AD","4","LACP_PORT","Port %s is a part of an LACP channel, it conflicts with Dot1ad configuration","IEEE 802.1ad configuration cannot coexist with LACP ports.","Disable the LACP configuration on the port before enabling 802.1ad."
"DOT1AD","4","OAM_PORT","Port %s is configured for OAM, it conflicts with Dot1ad configuration","IEEE 802.1ad configuration cannot coexist with OAM-enabled ports.","Disable the OAM configuration on the port before enabling 802.1ad."
"DOT1AD","4","PLATFORM_RESOURCE_UNAVAILABLE","Platform does not have resouces to support dot1ad configuration","The hardware match registers required by 802.1ad are not available.","Unconfigure the features that use the match registers (such as CFM or CGVRP) before enabling 802.1ad."
"DOT1AD","4","STP_CONFLICT","STP mode conflicts with Dot1ad configuration as it is not in MST mode","The current Spanning Tree Protocol (STP) mode conflicts with the 802.1ad configuration.","Change the STP mode to Multiple Spanning Tree (MST) before enabling 802.1ad."
"DOT1Q_TUNNELLING","4","MTU_WARNING","System MTU of [dec] might be insufficient for 802.1Q tunnelling.802.1Q tunnelling requires system MTU size of [dec] to handle maximum size ethernet frames.","The system MTU setting might not be a large enough value to support 802.1Q tunnelling. When 802.1Q tunnelling is being used, the system MTU setting might need to be adjusted to add the 4-byte overhead associated with the additional 802.1Q tag.","Enter the system mtu command in global configuration mode to adjust the system MTU setting to take into account the additional 802.1Q tag."
"DOT1X","4","UNKN_ERR","An unknown operational error occurred.","The 802.1X process cannot operate due to an internal system error.","Reload the device."
"DOT1X","5","DROP_MAC","Disallowed MAC address [enet] trying to authenticate.","Authentication using 802.1X is not allowed for a host whose MAC address is configured as a drop entry in the MAC address table.","Remove the drop entry if this host is to be allowed access."
"DOT1X","5","ERR_INVALID_AAA_ATTR","Got invalid AAA attribute settings [chars]","The authorization settings that were obtained are either unsupported or are invalid.","Change the value so that the correct settings are obtained."
"DOT1X","5","ERR_INVALID_TUNNEL_MEDIUM_TYPE","Got an invalid value [chars] for TUNNEL_MEDIUM_TYPE [chars]","The provided TUNNEL_MEDIUM_TYPE is either unsupported or invalid.","Change the tunnel medium type value to one that is supported."
"DOT1X","5","ERR_INVALID_TUNNEL_TYPE","Got an invalid value of [chars] for TUNNEL_TYPE [chars]","The provided TUNNEL_TYPE is either unsupported or invalid.","Change the tunnel type value to one that is supported."
"DOT1X","5","ERR_PER_USR_IP_ACL","Applied per-user IP ACL was unsuccessful on interface [chars]","The 802.1X process could not successfully apply a per-user IP ACL. A possible reason for this condition could be an invalid per-user base (or pub) ACL from the RADIUS server.","Examine the per-user base configuration for the RADIUS server and configure a correct one."
"DOT1X","5","ERR_PER_USR_MAC_ACL","Applied per-user MAC ACL was unsuccessful on interface [chars]","The 802.1X process could not successfully apply a per-user MAC ACL. A possible reason for this condition could be an invalid per-user base (or pub) ACL from the RADIUS server.","Examine the per-user base configuration for the RADIUS server and configure a correct one."
"DOT1X","5","ERR_PVLAN","Dot1x cannot be enabled on private vlan port [chars]","802.1X could not be enabled on the specified private VLAN port. This condition was caused by trying to set 802.1X port control to automatic mode on a PVLAN port.","Change the port to access or routed mode, and retry enabling 802.1X on the port."
"DOT1X","5","ERR_PVLAN_EQ_VVLAN","Dot1x can not be enabled on a port with Access VLAN equal to Voice VLAN.","A port could not enable 802.1X because the access VLAN is equal to a voice VLAN. This condition was caused by trying to set 802.1X port control to automatic or force-unauthorized mode on a voice VLAN that is equal to an access VLAN port.","Change the voice VLAN or the access VLAN on the interface, and retry the 802.1X operation."
"DOT1X","5","ERR_PVLAN_TRUNK","Dot1x can not be enabled on private VLAN trunk ports.","802.1X cannot coexist with private VLAN trunking on the same port.","This is an informational message only. No action is required."
"DOT1X","5","ERR_RADIUSVLAN_EQ_VVLAN","RADIUS attempted to assign a VLAN to Dot1x port [chars] whose Voice VLAN is same as AccessVlan","The RADIUS server attempted to assign a VLAN to a supplicant on a port with a voice VLAN that is equal to an access VLAN.","Either update the RADIUS configuration so that an access VLAN is not equal to voice VLAN or change the voice VLAN on the specified port."
"DOT1X","5","ERR_STATIC_MAC","Dot1x can not be enabled on a port configured with Static MAC addresses.","A port could not enable 802.1X because the port is configured with static MAC addresses. This condition was caused by trying to set 802.1X port control to auto or force-unauthorized mode on a port that is configured with static MAC addresses.","Remove the static MAC addresses on the port, and retry the 802.1X operation."
"DOT1X","5","ERR_VLAN_INTERNAL","The VLAN [dec] is being used internally and cannot be assiged for use on the Dot1x port [chars] Vlan","The VLAN is used internally and cannot be assiged for use again on this port","Update the configuration to not use this VLAN."
"DOT1X","5","ERR_VLAN_INVALID","The VLAN [dec] is invalid and cannot be assiged for use on the Dot1x port [chars] Vlan","The VLAN specified is out of range and cannot be assiged for use on this port.","Update the configuration to use a valid VLAN."
"DOT1X","5","ERR_VLAN_RESERVED","The VLAN [dec] is a reserved vlan and cannot be assiged for use on the Dot1x port [chars] Vlan","The VLAN specified is a reserved VLAN and cannot be assiged for use on this port.","Update the configuration to not use this VLAN."
"DOT1X","5","ERR_VVID_NOT_SUPPORTED","Dot1x can not be enabled on this port with Voice VLAN configured.","802.1X cannot coexist on the same port with Voice VLANs.","Remove voice VLANs configuration on this port and retry the 802.1X operation."
"DOT1X","5","FAIL","Authentication failed for client (%s) on Interface %s","Authentication was unsuccessful for the specified client.","No action is required."
"DOT1X","5","SUCCESS","Authentication successful for client (%s) on Interface %s","Authentication was successful for the specified client.","No action is required."
"DOT1X_SWITCH","4","PROC_START_ERR","Unable to start dot1x switch process.","The system failed to create the 802.1X switch process.","Reload the device."
"DOT1X_SWITCH","5","ERR_ADDING_ADDRESS","Unable to add address %e on %s","The authenticated host's address could not be added. This is probably because either the TCAM is full or the address exists as a secure address on another port.","If the TCAM is full, clear some dynamic addresses to make room for the host's address. If the host's address is secured on another port, manually remove it from that port."
"DOT1X_SWITCH","5","ERR_INVALID_PRIMARY_VLAN","Attempt to assign primary VLAN %d to 802.1x port %s","An attempt was made to assign a primary VLAN to an 802.1x port, which is not allowed.","Update the configuration to use a different VLAN."
"DOT1X_SWITCH","5","ERR_INVALID_SEC_VLAN","Attempt to assign invalid secondary VLAN %d to PVLAN host 802.1x port %s","An attempt was made to assign a non-secondary VLAN to a PVLAN host 802.1x port.","Change the mode of the port so that it is no longer a PVLAN host port or use a valid secondary VLAN."
"DOT1X_SWITCH","5","ERR_PRIMARY_VLAN_NOT_FOUND","Primary VLAN for VLAN [dec] does not exist or is shutdown for dot1x port [chars]","An attempt was made to use a private VLAN whose primary VLAN does not exist or is shut down.","Make sure the primary VLAN exists and is not shut down. Also verify that the private VLAN is associated with a primary VLAN."
"DOT1X_SWITCH","5","ERR_RADIUS_VLAN_NOT_FOUND","Attempt to assign non-existent VLAN %s to dot1x port %s","An attempt was made by RADIUS to assign a VLAN with a particular name or ID to a supplicant on a port, but the name or ID could not be found on the switch.","Make sure a VLAN with the specified name or ID exists on the switch."
"DOT1X_SWITCH","5","ERR_SEC_VLAN_INVALID","Attempt to assign secondary VLAN %d to non-PVLAN host 802.1x port %s","An attempt was made to assign a secondary VLAN to a port that is not a PVLAN host port, which is not allowed.","Change the mode of the port so that it is configured as a PVLAN host port or use a different VLAN that is not configured as a secondary VLAN."
"DOT1X_SWITCH","5","ERR_SPAN_DST_PORT","Attempt to assign VLAN %d to 802.1x port %s, which is configured as a SPAN destination","An attempt was made to assign a VLAN to an 802.1x port that is configured as a SPAN destination port.","Change the SPAN configuration so that the port is no longer a SPAN destination port or change the configuration so that no VLAN is assigned."
"DOT1X_SWITCH","5","ERR_VLAN_EQ_MDA_INACTIVE","Multi-Domain Authentication cannot activate because Data and Voice VLANs are the same on port %s","Multi-Domain Authentication (MDA) host mode cannot be activated if the configured data VLAN on a port is the same as voice VLAN.","Change either the voice VLAN or the access (data) VLAN on the interface so they are not equal."
"DOT1X_SWITCH","5","ERR_VLAN_EQ_VVLAN","Data VLAN [dec] on port [chars] cannot equal to Voice VLAN.","The 802.1x assigned VLAN on a port cannot be the same as the voice VLAN.","Change either the voice VLAN or the access 802.1X assigned VLAN on the interface so they are not equal anymore. This change will cause the authentication to proceed normally on the next retry."
"DOT1X_SWITCH","5","ERR_VLAN_INTERNAL","The VLAN [dec] is being used internally and cannot be assiged for use on the Dot1x port [chars] Vlan","The VLAN is used internally and cannot be assiged for use again on this port.","Update the configuration to not use this VLAN."
"DOT1X_SWITCH","5","ERR_VLAN_INVALID","The VLAN [dec] is invalid and cannot be assiged for use on the Dot1x port [chars] Vlan","The VLAN specified is out of range and cannot be assiged for use on this port.","Update the configuration to use a valid VLAN."
"DOT1X_SWITCH","5","ERR_VLAN_NOT_FOUND","Attempt to assign non-existent or shutdown VLAN [dec] to dot1x port [chars]","An attempt was made to assign a VLAN to a supplicant on a port, but the VLAN was not found in the VTP database.","Make sure the VLAN exists and is not shutdown or use another VLAN."
"DOT1X_SWITCH","5","ERR_VLAN_NOT_VALID","Attempt to assign non-existent group or shutdown VLAN to 802.1x port [chars]","An attempt was made to assign a VLAN to an 802.1x port, but the VLAN was not found in the VTP database. Group not found.Error Message    Make sure the VLAN exists and is not shutdown or use another VLAN.%DOT1X_SWITCH-5-ERR_VLAN_ON_ROUTED_PORT: Attempt to assign VLAN %d to routed 802.1x port %s Explanation    An attempt was made to assign a VLAN to a routed 802.1x port, which is not allowed.","Change the mode of the port so that it is no longer a routed port or change the configuration so that no VLAN is assigned."
"DOT1X_SWITCH","5","ERR_VLAN_PROMISC_PORT","Attempt to assign VLAN %d to promiscuous 802.1x port %s","An attempt was made to assign a VLAN to a promiscuous 802.1x port, which is not allowed.","Change the mode of the port so that it is no longer a promiscuous port or change the configuration so that no VLAN is assigned."
"DOT1X_SWITCH","5","ERR_VLAN_RESERVED","The VLAN [dec] is a reserved vlan and cannot be assiged for use on the Dot1x port [chars] Vlan","The VLAN specified is a reserved VLAN and cannot be assiged for use on this port.","Update the configuration not to use this VLAN."
"DOT1X_SWITCH","5","ERR_VLAN_RSPAN","Attempt by 802.1x to assign RSPAN VLAN [dec]. 802.1x is incompatible with RSPAN","Remote SPAN should not be enabled on a VLAN in which ports are configured with 802.1X enabled.","Either disable the remote SPAN configuration on the VLAN OR disable 802.1X on all of the ports in this VLAN."
"DP83815","1","UNAVAILABLE","%s failed to initialized","The software failed to initialize/restart an Ethernet/Fast Ethernet interface.","Show tech-support. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DP83815","1","UNAVAILABLE","%s status = 0x%08x","The interface could not access system resources for a long time. This problem may occur under very heavy loads.","Show tech-support. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DP83815","1","UNAVAILABLE","Only found %d interfaces on bay %d, shutting down bay","The software could not identify the interface card.","Show tech-support. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DP83815","3","UNAVAILABLE","%s packet buffer, pak=0x%x","The software detected an error in descriptor ownership.","Show tech-support. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DP83815","3","UNAVAILABLE","%s transmit error","While transmitting a frame, the controller chip's local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.","The system should recover. LOG_STD_NO_ACTION"
"DP83815","3","OWNERR","[chars] packet buffer, pak=[hex]","The software detected an error in descriptor ownership.","Clear the interface. If the problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DP83815","3","UNDERFLO","[chars] transmit error","While transmitting a frame, the controller chip's local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.","The system should recover. No action is required."
"DP83815","5","LATECOLL","[chars] transmit error","Late collisions occurred on the Ethernet or Fast Ethernet interface.","If the interface is Fast Ethernet, verify that both peers are in the same duplex mode. For regular Ethernet, the system should recover. No action is required."
"DP83815","5","LOSTCARR","[chars] cable/transceiver problem?","The cable or transceiver is not connected.","Connect the cable or transceiver. No action is required."
"DP83815","6","EXCESSCOLL","[chars]","Ethernet or Fast Ethernet is seeing multiple collisions. This condition may occur under heavy loads.","The system should recover. No action is required."
"DP83815","6","NOTDP83815","Slot [dec] device ID seen as [hex], expected [hex]","The software did not recognize the interface chips.","Reseat the interface card. If the message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DRIP","3","UNAVAILABLE","DRIP: Assertion failed: %s","An internal software error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DRIP","6","UNAVAILABLE","DRIP conflict with CRF %d.","A DRIP conflict has occured. The virtual ring or pseudo ring's CRF is being re-used in the network.","Make sure that the CRF vlanid of the virtual ring and the pseudo ring is unique in the network."
"DRP","3","UNAVAILABLE","Unable to open socket","The requested operation could not be accomplished because of a low memory condition.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"DRP","3","UNAVAILABLE","multiple DRP commands encountered","Multiple DRP commands were found in a single DRP packet.","Copy the error message exactly as it appears, and report it to your technical support representative."
"DRP","3","UNAVAILABLE","unable to determine metric for %i, %i subnetted","A software or hardware error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"DRP","3","UNAVAILABLE","unable to send response to %i:%d","A software or hardware error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"DRP","7","UNAVAILABLE","no route for destination %i","A software or hardware error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"DS3E3SUNI","1","UNAVAILABLE","msgtxt_nomemory","An operation could not be accomplished because of a low-memory condition. The current system configuration, network environment, or possibly a software error might have exhausted or fragmented the system's memory.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a configuration that has more memory."
"DSC","4","UNAVAILABLE","Setting config-register to 0x0 will prevent the feature boards from booting when router shelf is rebooted","Dial-shelf Controller cannot be booted manually","Set the config-register to 0x2 for auto boot"
"DSCC4","1","UNAVAILABLE","DSCC4(%d/%d), SCC%d init failed","The software failed to initialize/restart an SCC of a serial interface","Clear the serial interface. If the message recurs, call your technical support representative for assistance."
"DSCC4","3","UNAVAILABLE","%s","DSCC4 analyze device failure is detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSCC4","3","UNAVAILABLE","%s","Generic error messageError Message    %DSCC4-3-UNAVAILABLE: DSCC4(%d/%d), Buffer ownership error, pak=0x%x Explanation    An internal software error occurred.","Call your technical support representative to obtain a software upgrade."
"DSCC4","3","UNAVAILABLE","DSCC4(%d/%d), invalid clock rate (index %d) requested","An internal software error occurred.","Call your technical support representative to obtain a software upgrade."
"DSCC4","3","UNAVAILABLE","DSCC4(%d/%d), packet (size %d) too big","A packet greater than the assigned MTU of this serial interface was queued up for transmission.","The system should recover. No action is required. If the message recurs, it may indicate an error related to data traffic patterns. Copy the error message exactly as it appears, and report it to your technical support representative."
"DSCC4","3","UNAVAILABLE","DSCC4(%d/%d), packet (size %d) was less than 2 bytes","A small packet (less than 2 bytes) was queued up for transmission. The interface cannot handle such small packets for transmission.","The system should recover. No action is required. If the message recurs, it may indicate a hardware error related to data traffic patterns. Copy the error message exactly as it appears, and report it to your technical support representative."
"DSCC4","3","UNAVAILABLE","DSCC4, Incorrect SCC number","An internal software error occurred.","Call your technical support representative to obtain a software upgrade."
"DSCC4","3","UNAVAILABLE","No memory for %s of unit %d","The router does not have enough memory to perform the function","Consider adding more shared memory. Copy the error message exactly as it appears, and report it to your technical support representative."
"DSCCLOCK","3","UNAVAILABLE","Clock moving to FREERUN from HOLDOVER","The current primary TDM clock has been deleted and hence the system primary has switched to the DSC local oscillator, which is the current highest priority good clock. Phase continuity is maintained during the switchover.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSCCLOCK","3","UNAVAILABLE","Clock moving to NORMAL from HOLDOVER, selected clock is on slot %d port %d line %d","The current primary TDM clock has been deleted and hence the system primary has switched to the clock coming in via the trunk specified by the slot/port, which is the current highest priority good clock. Phase continuity is maintained during the switchover.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSCCLOCK","3","UNAVAILABLE","Duplicate priority (%d) clock sources: slot %d port %d, and slot %d port %d.","While using split-dial-shelf separate clocks sources (one on each router shelf) with the same priority have been configured","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSCCLOCK","3","UNAVAILABLE","Failed to allocate memory for the DSC clocks","The clock switching software has failed to allocate memory while adding a clock.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSCCLOCK","3","UNAVAILABLE","Failed to select any clock as the system clock. Remaining in HOLDOVER mode","The clock selection algorithm has failed to select any clock as the TDM primary clock.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSCCLOCK","3","UNAVAILABLE","Moving to NORMAL mode from HOLDOVER mode without phase correction, clock is slot %d port %d line %d","The source trunk port of the TDM primary clock which had gone bad, has turned good again before the holdover timer expiry. Hence the primary has moved from HOLDOVER to NORMAL state without phase correction between input trunk reference and the output TDM clock.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSCCLOCK","3","UNAVAILABLE","Moving to NORMAL mode from HOLDOVER mode, clock is slot %d port %d line %d","The TDM primary clock which is in HOLDOVER mode and whose source was a trunk port, has switched to the same trunk port and moved to NORMAL mode with a phase alignment between input source clock and output TDM reference clock. Most likely the router-shelf and hence the feature boards have reloaded.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSCCLOCK","3","UNAVAILABLE","Switching to the clock on slot %d port %d line %d","The TDM primary clock is switching to the clock coming in via the trunk specified, most likely after the router-shelf and hence feature boards reload. The phase of the output TDM clock is forced to align with the input reference during the switchover.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSCCLOCK","3","UNAVAILABLE","Switching to the clock on slot %d port %d line %d as the current primary has gone bad","The TDM primary clock has switched to a backup clock coming in via the specified trunk as the current primary clock has gone bad.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSCCLOCK","3","UNAVAILABLE","Switching to the user configured clock on slot %d port %d line %d","The TDM primary clock is switching from a default clock or a lower priority user configured clock to a (higher priority) user configured clock coming in via a trunk. Phase continuity is maintained during the switchover.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSCCLOCK","3","UNAVAILABLE","The System Primary Clock is down. Moving to HOLDOVER state and waiting to see if it comes up","This message is generated whenever the current primary clock goes bad. The TDM clock circuit goes into HOLDOVER mode and a holdover timer is started to see if the bad clock turns good within the holdover time.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSCCLOCK","3","UNAVAILABLE","The System Primary Clock is up. Moving to NORMAL state from HOLDOVER","The TDM primary clock which had gone bad, has turned good within the holdover time. Hence the TDM primary clock switches to the NORMAL mode from the HOLDOVER mode.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSCCLOCK","5","UNAVAILABLE","Clock moving to NORMAL from FREERUN, selected clock is on slot %d port %d line %d","The primary TDM clock, which has been running off the local oscillator of DSC in FREERUN mode, has switched to the line clock coming in via the specified trunk.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSCEXTCLK","3","UNAVAILABLE","Clock moving to NORMAL from HOLDOVER, selected clock is external clock on DSC","The current primary TDM clock has been deleted and hence the system primary has switched to the clock coming in via the external network reference clock on the DSC front panel, which is the current highest priority good clock. Phase continuity is maintained during the switchover","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSCEXTCLK","3","UNAVAILABLE","Moving to NORMAL mode from HOLDOVER mode without phase correction, selected external clock on DSC","The DSC front panel clock which is the source of the current TDM primary clock and which had gone bad, has turned good again before the holdover timer expiry. Hence the primary has moved from HOLDOVER to NORMAL state without phase correction between input reference and the output TDM clock.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSCEXTCLK","3","UNAVAILABLE","Moving to NORMAL mode from HOLDOVER mode, selected external clock on DSC","The TDM primary clock which is in HOLDOVER mode and whose source was a the DSC front panel clock, has switched to the same clock and moved to the NORMAL mode.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSCEXTCLK","3","UNAVAILABLE","Switching to the external clock on DSC","The TDM primary clock is switching to the clock coming in via the DSC front panel, most likely after the router-shelf and hence feature boards reload. The phase of the output TDM clock is forced to align with the input reference during the switchover.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSCEXTCLK","3","UNAVAILABLE","Switching to the external clock on DSC as the current primary has gone bad","The TDM primary clock has switched to a backup clock coming in via the DSC front panel external clock feed as the current primary clock has gone bad.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSCEXTCLK","3","UNAVAILABLE","Switching to the user configured external clock on DSC","The TDM primary clock is switching from a default clock or a lower priority user configured clock to the (higher priority) user configured clock coming in via the DSC front panel clock feed. Phase continuity is maintained during the switchover.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSCEXTCLK","5","UNAVAILABLE","Clock moving to NORMAL from FREERUN, selected clock is external clock on DSC","The primary TDM clock, which has been running off the local oscillator of DSC in FREERUN mode, has switched to the external network reference clock being fed from the DSC front panel.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSCREDCLK","2","UNAVAILABLE","Clock command hardware failed","The","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSCREDCLK","2","UNAVAILABLE","Clock on other DSC has failed - immediate clock takeover","The backup DSC clock has detected failure on the other DSC clock hardware and is taking over to become the active clock manager.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSCREDCLK","2","UNAVAILABLE","Removal of other DSC detected - immediate clock takeover","The backup DSC clock has detected removal of the other DSC","Reinstall a DSC in other DSC slot to provide DSC."
"DSCREDCLK","3","UNAVAILABLE","Active DSC requests backup to takeover clock - delaying for sync","The other DSC has requested the current DSC to take over active clock management, but the current DSC is waiting for clock hardware synchronization before doing so, to avoid call loss.","LOG_STD_NO_ACTION"
"DSCREDCLK","3","UNAVAILABLE","Active DSC requests backup to takeover clock - done","The other DSC has requested the current DSC to take over active clock management, and the current DSC has done so.","LOG_STD_NO_ACTION"
"DSCREDCLK","3","UNAVAILABLE","Other DSC IOS keepalive failure - clock takeover","The other DSC has failed to respond to keepalives to the current DSC and so the current DSC is taking over to become the active clock manager.","Recover DSC in other DSC slot to provide backup DSC."
"DSCREDCLK","5","UNAVAILABLE","Backup clock matched to active clock reference, external clock on DSC","The backup DSC has detected a change in the selected clock reference on the active DSC and has changed it's own clock hardware to match the new selection. The selected clock reference is now from the DSC front panel external clock feed.","LOG_STD_NO_ACTION"
"DSCREDCLK","5","UNAVAILABLE","Backup clock matched to active clock reference, slot %d line %d","The backup DSC has detected a change in the selected clock reference on the active DSC and has changed it's own clock hardware to match the new selection. The selected clock reference is now from the specified trunk line.","LOG_STD_NO_ACTION"
"DSCREDCLK","5","UNAVAILABLE","Backup clock moving to NORMAL to phase lock to active clock","The backup DSC has detected a change to the clock","LOG_STD_NO_ACTION"
"DSC_ENV","0","UNAVAILABLE","Slot %d, %s %u %s","The card enviromental parameters specified are outside the normalrange of operation.","Check blowers and ambient room temperature"
"DSC_ENV","0","UNAVAILABLE","Slot %d, %s","Fans in the blower unit have failed. Operation of unit may lead to cards overheating and being shutdown","Power down dial-shelf to avoid overheating. Replace faulty fans"
"DSC_ENV","0","UNAVAILABLE","Temperature/Voltage has reached a critical level for DSC in slot %d. No backup DSC available. Powering down all feature boards in the chassis.","The temparature or voltage sensor has reached a condition outside the acceptable range for the DSC. No backup is available to takeover control/monitoring of the feature boards so all feature boards are being shutdown.","Attempt to resolve voltage/temperature problems. If the problem is not resolved, call your technical support representative for assistance."
"DSC_ENV","1","UNAVAILABLE","Slot %d, %s %u %s","The card enviromental parameters specified are outside the normalrange of operation.","Check blowers and ambient room temperature"
"DSC_ENV","2","UNAVAILABLE","Slot %d, %s %s %u %s","The environmental parameters have returned from a state other thannormal to normal","Do nothing. Conditions are nominal"
"DSC_ENV","2","UNAVAILABLE","Slot %d, %s %u %s","The card enviromental parameters specified are outside the normalrange of operation.","Check blowers and ambient room temperature"
"DSC_ENV","2","UNAVAILABLE","Slot %d, %s","A fan in the blower unit has failed. Operation of unit can continue but failure should be looked into","Replace faulty fan"
"DSC_REDUNDANCY","3","UNAVAILABLE","Other DSC/router in split mode","There is another router connected to the dial shelf. In this situation both must be configured in split mode","Configure the other router in split mode"
"DSC_REDUNDANCY","3","UNAVAILABLE","Slot ownership conflict detected for slot %d","There is another router connected to the dial shelf, it is claiming ownership of a slot that this router is also claiming","Fix the ownership conflict by reconfiguring one of the routers so that it doesn't own the slot"
"DSC_REDUNDANCY","3","UNAVAILABLE","Tdm Split conflict detected,my tdm %d, other rs %d","There is another router connected to the dial shelf, it is claiming ownership of backplane timeslots that this router requires. This is probably due to OIR activity moving trunk cards from one half of the split to the other.","Fix the ownership conflict by reloading the router whose tdm number is greater than the trunk capacity for that router. In some cases it may be necessary to reset both routers."
"DSI","2","UNAVAILABLE","Out of range PCI port %d","The software specified an out-of-range port on the dial shelf interconnect board. This is a software error.","Copy the error message exactly as it appears, and report it to your technical support representative."
"DSI","3","UNAVAILABLE","From %s (%d) to %s (%d) for slot %d","The software detected a state change for the specified slot.","None. Message is informational."
"DSI","3","UNAVAILABLE","From %s (%d) to %s (%d) for slot %d","The software detected an mbus agent state change for the specified slot.","None. Message is informational."
"DSI","3","UNAVAILABLE","Invalid change from %s (%d) to %s (%d) for slot %d","The software detected an invalid state change for the specified slot's mbus agent. This is a software error.","Copy the error message exactly as it appears, and report it to your technical support representative."
"DSI","3","UNAVAILABLE","Invalid change from %s (%d) to %s (%d) for slot %d","The software detected an invalid state change for the specified slot. This is a software error.","Copy the error message exactly as it appears, and report it to your technical support representative."
"DSI","3","UNAVAILABLE","Unknown event %d for slot %d","The software generated an unknown event for the specified slot. This is a software error.","Copy the error message exactly as it appears, and report it to your technical support representative."
"DSPDD","1","UNAVAILABLE","DSPDD internal error[%s:%d","The router or access server has detected an internal error.","Copy the error message exactly as it appears, and report it to your technical support representative."
"DSPDD","1","UNAVAILABLE","DSPDD internal firmware error[%s:%d","The router or access server has detected an internal error.","Copy the error message exactly as it appears, and report it to your technical support representative."
"DSPDD","1","UNAVAILABLE","DSPRM internal error[%s:%d","The router or access server has detected an internal error.","Copy the error message exactly as it appears, and report it to your technical support representative."
"DSPDD","1","UNAVAILABLE","IOS buffer pool unavailable [%s:%d]","The router or access server could not allocate internal resources.","Copy the error message exactly as it appears, and report it to your technical support representative."
"DSPDD","1","UNAVAILABLE","IOS memory unavailable [%s:%d]","The router or access server could not allocate memory for internal data structures.","Copy the error message exactly as it appears, and report it to your technical support representative."
"DSPRM","3","UNAVAILABLE","Insufficient DSP resources for timeslot %d on port %s","The configuration requires more DSP resources than are available.","Change the configuration to specify fewer used timeslots. Install additional DSP resources to allow more complex configurations."
"DSPRM","3","UNAVAILABLE","Unable to create internal interface descriptor","There are insufficient resources to create a necessary data structure.","Verify that there is sufficient main memory."
"DSPRM","5","UNAVAILABLE","DSP %d in slot %s, NOT RESPONDING - auto restart(%d times)","The DSP failed the background keep-alive test.","LOG_STD_NO_ACTION"
"DSPRM","5","UNAVAILABLE","DSP %d in slot %s, changed state to %s","The DSP resource changed state.","LOG_STD_NO_ACTION"
"DSPRM","5","UNAVAILABLE","DSP %d in slot %s, is in the failed state","The DSP entered the FAILED state due to alarm indications.","Replace the DSP resource."
"DSPRM","5","UNAVAILABLE","DSP Jukebox(%d) in slot %s, changed state to %s","The DSP JUKEBOX changed state.","LOG_STD_NO_ACTION"
"DSPRM","5","UNAVAILABLE","Jukebox transmit overlay resp %d on slot %s, failed","The Jukebox received failed response code.","LOG_STD_NO_ACTION"
"DSIP","3","UNAVAILABLE","IPC subsystem API error(%s), %s, %s","This message indicates that Nitro Interconnect Protocol has encountered a problem while dealing with the port specfied in the error message. The exact problem can be further decoded by the IPC error message(first parameter), the action involved (second parameter) and the port name (third parameter)Error Message    %DSIP-3-UNAVAILABLE: IPC subsystem API error, can not create seat by the seatid %d for the slot %d Nitro Interconnect Protocol reliable stack has failed to create seat for the specified slot. DTP MessagesThis section contains Dynamic Trunking Protocol (DTP) filtering messages.Error Message    %DTP-5-DOMAINMISMATCH: Unable to perform trunk negotiation on port [chars] because of VTP domain mismatch. Explanation    The two ports involved in trunk negotiation belong to different VTP domains. Trunking is possible only when the ports involved belong to the same VTP domain.","Ensure that the two ports that are involved in trunk negotiation belong to the same VTP domain."
"DSPRM","5","UNAVAILABLE","DSP %d in slot %s, NOT RESPONDING - auto restart(%d times)","The DSP failed the background keep-alive test.","LOG_STD_NO_ACTION"
"DSPRM","5","UNAVAILABLE","DSP %d in slot %s, changed state to %s","The DSP resource changed state.","LOG_STD_NO_ACTION"
"DSPRM","5","UNAVAILABLE","DSP %d in slot %s, is in the failed state","The DSP entered the FAILED state due to alarm indications.","Replace the DSP resource."
"DSPRM","5","UNAVAILABLE","DSP Jukebox(%d) in slot %s, changed state to %s","The DSP JUKEBOX changed state.","LOG_STD_NO_ACTION"
"DSPRM","5","UNAVAILABLE","Jukebox transmit overlay resp %d on slot %s, failed","The Jukebox received failed response code.","LOG_STD_NO_ACTION"
"DSPU","3","UNAVAILABLE","ACTPU Neg rsp received from PU %s","Remote PU rejected the router's request for an SSCP-PU session.","Verify PU configuration parameters at the router and at the remote PU. Determine whether the problem exists at the remote PU, and correct it. If the problem persists, call your Cisco technical support representative for assistance."
"DSPU","3","UNAVAILABLE","Bad SNA data received from PU %s, data= %s","Unrecognized SNA data was received from the remote PU.","Correct the problem at the remote PU. If the problem persists, call your Cisco technical support representative for assistance."
"DSPU","3","UNAVAILABLE","CLSI bad Adaptor correlator, header= %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSPU","3","UNAVAILABLE","CLSI bad identifier type, header= %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSPU","3","UNAVAILABLE","CLSI bad identifier, header= %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSPU","3","UNAVAILABLE","CLSI bad length, header= %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSPU","3","UNAVAILABLE","CLSI bad primitive command, header= %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSPU","3","UNAVAILABLE","CLSI bad primitive type, header= %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSPU","3","UNAVAILABLE","CLSI bad return code: %d, header= %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSPU","3","UNAVAILABLE","CLSI unexpected ActivateSapCnf, header= %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSPU","3","UNAVAILABLE","CLSI unexpected DeactivateSapCnf, header= %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSPU","3","UNAVAILABLE","CLSI unexpected EnableCnf, header= %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSPU","3","UNAVAILABLE","CLSI unexpected IdStnInd, header= %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSPU","3","UNAVAILABLE","Connect in from host %s with remote address %s failed.","Connection with the remote host could not be established.","Verify host configuration parameters at the router and at the host. Determine whether the router is configured to accept connection from this host."
"DSPU","3","UNAVAILABLE","Connect in from pu %s with remote address %s failed.","Connection with the remote PU could not be established.","Verify PU configuration parameters at the router and at the remote PU. Determine whether the router is configured to accept connectIn from this remote PU."
"DSPU","3","UNAVAILABLE","Connect in from remote address %s failed.","Connection with remote station could not be established.","Verify configuration parameters at the router and at the remote station. Determine whether the router is configured to accept connectIn from this remote station."
"DSPU","3","UNAVAILABLE","Connect in from remote address %s failed; insufficient memory.","Connection with the remote station could not be established because of insufficient memory in the router.","Correct low memory problem in the router. If the problem persists, call your technical support representative for assistance."
"DSPU","3","UNAVAILABLE","Connect out to host %s failed.","Connection with the remote host could not be established.","Verify host configuration parameters at the router and at the host. Determine whether the host is active and responding to connection requests."
"DSPU","3","UNAVAILABLE","Connect out to pu %s failed.","Connection with the remote PU could not be established.","Verify PU configuration parameters at the router and at the remote PU. Determine whether the remote PU is active and responding to connection requests."
"DSPU","3","UNAVAILABLE","Connection attempt failed from XID= %s, ACTPU not supported","The remote station did not request PU 2.0 activation; connection with remote station is terminated.","Correct link station configuration parameters at the remote station to request a system services control point (SSCP)-PU session with the router."
"DSPU","3","UNAVAILABLE","Connection attempt failed from XID= %s, Invalid MaxIFrame= %d","An invalid MaxIFrame value in an exchange identification (XID) was received from the remote station; connection with remote station could not be established.","Correct link station configuration at the remote station."
"DSPU","3","UNAVAILABLE","Connection attempt failed from XID= %s, Invalid WindowSize= %d","An invalid WindowSize value in an exchange identification (XID) was received from the remote station; connection with remote station could not be established.","Correct link station configuration at the remote station."
"DSPU","3","UNAVAILABLE","DSPU could not free buffer - buffer corrupted","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSPU","3","UNAVAILABLE","LU %d received a Notify Neg Resp from host %s","Remote host rejected the router's request to activate/deactivate an SSCP-LU session.","Verify host configuration parameters at the router and at the remote host. Determine whether the problem exists at the remote host and correct it. If the problem persists, call your technical support representative for assistance."
"DSPU","3","UNAVAILABLE","XID Format not supported, XID= %s","Unsupported XID received from the remote station; connection with remote station could not be established.","Configure the remote station to send supported XID (if possible). Supported XID formats are: XID Format 0 XID Format 3"
"DSPU","3","UNAVAILABLE","XID Negotiation Error, bad byte= %d, bad bit= %d, sense data= %s","XID3 with an error indication was received from the remote station; connection with the remote station could not be established.","Determine, from the CV 22 byte or bit information, which field in the XID3 is rejected by the remote station, and correct the link station configuration parameters at either the router or the remote station."
"DSX0","5","UNAVAILABLE","RBS of controller %d timeslot %d is down","This message indicates that Robbed-Bit Signaling (RBS) has been disabled on the specified timeslot and controller.","LOG_STD_NO_ACTION"
"DSX0","5","UNAVAILABLE","RBS of controller %d timeslot %d is up","This message indicates that Robbed-Bit Signaling (RBS) has been enabled on the specified timeslot and controller.","LOG_STD_NO_ACTION"
"DSX0","5","UNAVAILABLE","RBS of slot %d controller %d timeslot %d is dynamic busyout","This message indicates that Robbed-Bit Signaling (RBS) has been dynamically busied-out on the specified timeslot and controller.","LOG_STD_NO_ACTION"
"DSX0","5","UNAVAILABLE","RBS of slot %d controller %d timeslot %d is static busyout","This message indicates that Robbed-Bit Signaling (RBS) has been statically busied-out on the specified timeslot and controller.","LOG_STD_NO_ACTION"
"DSX0","5","UNAVAILABLE","RBS of slot %d controller %d timeslot %d is unbusyout","This message indicates that Robbed-Bit Signaling (RBS) has been restored from a busied-out condition on the specified timeslot and controller.","LOG_STD_NO_ACTION"
"DSX1","1","UNAVAILABLE","Munich 32 channel input queue is congested","Can't allocate receive buffers since input queue is at its maximum, this indicates data is coming faster than the receiver can handle.","Reduce data goes into this channel and or increase the number of input queue."
"DSX1","1","UNAVAILABLE","T1/E1 Firmware in slot %d is not running","Critical error occurred in the T1/E1 Firmware and it stopped running. Access server needs to be reloaded.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSX1","1","UNAVAILABLE","T1/E1 Firmware in slot %d is running","T1/E1 Firmware is now running after recovering from critical error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSX1","1","UNAVAILABLE","Trunk Firmware in slot %d reset failed","Trunk could not be restarted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSX1","3","UNAVAILABLE","Munich 32 action request failure: Ctrl = 0x%08x, Channel = %d","Munich 32 does not respond to request","If message continue to print out, contact customer support"
"DSX1","3","UNAVAILABLE","Munich 32 action request timeout: Ctrl = 0x%08x, Channel = %d","Munich 32 is not response to action request","If problem persist, contact customer support"
"DSX1","3","UNAVAILABLE","Munich 32 bad interrupt queue: Ctrl = 0x%08x, Channel = %d","There might be an overflow on interrupt queue","Contact tech support"
"DSX1","3","UNAVAILABLE","Munich 32 bit rate not match: Ctrl = 0x%08x, Channel = %d","Command can not be carried out, there is a mismatch on bit rate","Make sure the configured data matched the supported speed"
"DSX1","3","UNAVAILABLE","Munich 32 channel invalid: Ctrl = 0x%08x, Channel = %d","The channel select is not valid","Make sure the channel supports the needed feature"
"DSX1","3","UNAVAILABLE","Munich 32 channel memory allocation error: Ctrl = 0x%08x, Channel = %d","The requested operation could not be accomplished because of a low memory condition.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"DSX1","3","UNAVAILABLE","Munich 32 error configuring channelized interface: Ctrl = 0x%08x, Channel = %d","There is unidentify error occurs to Munich 32","If message repeat, contact tech support"
"DSX1","3","UNAVAILABLE","Munich 32 in unknown state: Ctrl = 0x%08x, Channel = %d","Munich 32 goes into unknown state","If message persists, contact customer support"
"DSX1","3","UNAVAILABLE","Munich 32 no timeslot available: Ctrl = 0x%08x, Channel = %d","All timeslot on Munich are assigned.","Make sure there are channel available before use"
"DSX1","3","UNAVAILABLE","Munich 32 timeslot already configured: Ctrl = 0x%08x, Channel = %d","This timeslot was assigned and can not be used","Make sure the timeslot is available before use"
"DSX1","3","UNAVAILABLE","T1/E1 Firmware in slot %d restarted","T1/E1 Firmware restarted. All the active calls on the T1/E1 lines will be disconnected and the controllers will come back up within few seconds","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DSX1","3","UNAVAILABLE","msgtxt_nomemory","The requested operation could not be accomplished because of a low memory condition.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"DSX1","6","UNAVAILABLE","%s clock is now selected as clock source","One of the events (LOS or AIS or CLI command ..) has caused a change in clock selected","LOG_STD_NO_ACTION"
"DS_MODEM","3","UNAVAILABLE","DS-RS flow control has got out of sync, connection has too many particles free. slot:%d ttynum:%d parts_avail:%d","Indicates the flow control accounting on the DS has got out of sync.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DS_MODEM","3","UNAVAILABLE","Not enough particles - modem number:%d particles needed:%d available:%d; CTS %s","Indicates a break down of flow control between RS-DS, RS has sent more particles than are available for this connection.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DS_MODEM","3","UNAVAILABLE","Output drop - modem number:%d refunded %d; particle count %d, pool size %d, queue size %d","Temporarily unable to allocate particle for sending traffic to modem module, indicates a break down of flow control between RS-DS.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DS_MODEM","3","UNAVAILABLE","Static receive paktype unavailable","A software structure was found in an unexpected state during run-time for the indicated modem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DS_MODEM","3","UNAVAILABLE","Unexpected DSIP data callback for modem","An unexpected software event occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DS_TDM","3","UNAVAILABLE","Slot %d: convention broken for Mezz's Recomb. bus t'slots: %s-st%02u-ts%03u/gts%04u %s  (%i:%d) not found.","The CBAC code was searching its database for information for a particular inspection session, but this information was not found.","If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance."
"DUAL","3","BADIGRPSAP","Cannot send incremental SAP update to peer on %s. Increasing output-sap-delay may help","An incremental SAP update could not be sent because it might cause a loss of synchronization of the SAP tables between peers.","Increase the output SAP delay on the listed interface to reduce buffer usage. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"DUAL","3","BADIGRPSAPTYPE","Unsupported SAP type for EIGRP being %s - type %x","This message appears when you receive or attempt to send a SAP message with a type code that is neither a general query nor a general response, or when you receive a general query that is not addressed to the broadcast address.","Copy the error message exactly as it appears, and report it to your technical support representative. If possible, also provide the output of the debug ipx sap activity and debug ipx sap event commands for the period during which this message appeared."
"DUAL","3","PFXLIMIT","%s %d: %s prefix limit reached.","The number of prefixes for the Enhanced Interior Gateway Routing Protocol (EIGRP) has reached the configured or default limit.","Take preventive action by identifying the source of the prefixes. Enter the show ip eigrp accounting command for details."
"DUAL","4","PFXLIMITTHR","%s %d: %s threshold prefix level reached.","The number of prefixes in the topology database has reached the configured or default threshold level.","Take preventive action by identifying the source of the prefixes. Enter the show ip eigrp accounting command for details."
"DUAL","5","NBRCHANGE","[chars] [dec]: Neighbor [chars] ([chars]) is [chars]: [chars]","A neighbor has gone up or down. The displayed information is [routing protocol] [Autonomous System number]: Neighbor [IP address] ([interface]) is [up or down]: [reason].","No action is required."
"DUAL_ACTIVE","1","DETECTION","Dual-active condition detected: shutting down all non-VSL interfaces","A dual-active situation has occurred because VSL went down. The VSL has become inactive and both virtual switches have taken over the role of the active virtual switch. To fix this condition, the standby virtual switch has become active and taken control of the network. All non-VSL interfaces on the original active virtual switch will be internally shut down in hardware.","Attempt to determine the reason why VSL has gone down and correct it. Once VSL has been reestablished, the original active virtual switch will reload. Enter all variations of the commands:"
"DUAL_ACTIVE","1","RECOVERY","BFD running on [chars] triggered dual-active recovery","Bidirectional Forwarding Detection (BFD) detected a dual-active scenario on the specified interface and caused the switch to go into recovery mode.","No action is required."
"DUAL_ACTIVE","1","VSL_DOWN","VSL is down - switchover, or possible dual-active situation has occurred","The virtual switch link (VSL) between the active and standby switches has gone offline. The following are possible reasons for the switchover condition:-A switchover has occurred and the standby virtual switch has become the active virtual switch.-A dual-active situation has occurred, and the original active virtual switch has gone into recovery mode, which would bring down all non-VSL interfaces on the original active virtual switch.-A dual-active situation has occurred, but the original active virtual switch did not detect the dual active state and did not go into recovery mode. This condition may be the result of multiple system failures or an incorrect configuration that caused the dual-active situation to not be detected.","Attempt to determine the reason why the VSL has gone offline and correct it if it is a dual-active situation. Enter all variations of the commands:"
"DUAL_ACTIVE","1","VSL_RECOVERED","VSL has recovered during dual-active situation: Reloading switch [dec]","The virtual switch link (VSL) between the two active virtual switches in a dual-active situation has gone online. The virtual switch in recovery mode must be reloaded to reenable all non-VSL interfaces that were shut down when the dual-active situation first occurred.","No action is required."
"DUAL_ACTIVE","3","PORT_ERR_IN_RECOVERY","Port [chars] [chars] error","Port information could not be extracted or a non-VSL port could not be disabled while the active virtual switch was going into recovery mode.","Attempt to determine why the port information could not be extracted or why the non-VSL port could not be disabled."
"DUAL_ACTIVE","3","REGISTRY_ADD_ERR","Failure in adding to [chars] registry","Could not add a function to the registry.","No action is required."
"DUAL_ACTIVE","4","CONFIG","[chars]","If VSL goes down due to any reason, standby switch will take over as active immediately.If the original active chassis is still operational, both chassis are now active. This situation is called a dual-active scenario. A dual-active scenario can have adverse affects on network stability, because both chassis use the same IP addresses, SSH keys, and STP bridge ID.The virtual switching system (VSS) must detect a dual-active scenario and take recovery action for which at least one of the following detection methods should be configured: a/ Ehanced Pagp b/ IP BFD c/ Fast-hello. Please refer to Software configuration guide for more details.","Configure one or more dual-active detection methods as per configuration guide."
"DVMRP","5","NBRUP","Neighbor [IP_address] is up on [chars]","A DVMRP multicast neighbor is active on the specified interface. This is caused by the arrival and acceptance of DVMRP probes via that interface. This may indicate that a multicast session has been subscribed via a path passing through this router. Note that DVMRP activity is mutually exclusive of tagswitching, so this will cause tagswitching to be disabled on that interface.","No action is required."
"DWDM","3","CLEAR_G709_CTR","23414.2.c:205:64: backslash and newline separated by spaceUnable to clear g709 counter in slot [dec] rc = [dec]","The SPA driver was unable to clear the G.709 OTN protocol counters for bit errors.","Please check the configuration of the interfaces and controllers and correct the configuration if necessary. If the problem persists contact your Cisco technical support representative."
"DWDM","3","CONFIG_ALARM_REPORT","Failed to config report alarm [chars] slot [dec] rc = [dec]","The SPA driver could not configure one of the reporting status of the alarms.","Please check the configuration of the interfaces and controllers and correct the configuration if necessary. If the problem persists contact your Cisco technical support representative."
"DWDM","3","CONFIG_ALARM_THRESHOLD","Failed to config threshold  alarm [chars] slot [dec] rc = [dec]","The SPA driver could not configure one of the threshold alarms for the optical data or transport unit.","Please check the configuration of the interfaces and controllers and correct the configuration if necessary. If the problem persists contact your Cisco technical support representative"
"DWDM","3","CONFIG_TX_POWER","Failed to config transmit power [dec] on slot [dec] rc = [dec]","The SPA driver detected a error in configuring the Tx power level for the UT2 transponder module","Please power down and reseat the indicated SPA card. If the condition persists, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"DWDM","3","DWDM_CONFIG_FAIL","Failed to [chars] [chars] in slot [dec] rc = [dec]","The SPA driver detected failure during configuring one of the DWDM parameters","Reload the SPA card and if the problem persists, contact the technical support representative."
"DWDM","3","DWDM_GET_INFO_FAIL","Failed receiving [chars] from slot [dec] rc = [dec]","The SPA driver did not receive the necessary optics information from the slot.","Please check the configuration of the interfaces and controllers and correct the configuration if necessary. If the problem persists contact your Cisco technical support representative."
"DWDM","3","DWDM_NULL_INFO","DWDM info is NULL in [dec]","The SPA driver detected NULL information for DWDM.","Reload the SPA and if the problem persists contact the technical support representative."
"DWDM","3","IPC_SHIM_INIT","DWDM IPC SHIM init failed","The SPA driver detected failure during DWDM IPC SHIM initialization","Please power down and reseat the indicated SPA cardIf the problem persists please contact yourtechnical support representative"
"DWDM","3","LC_ERR_STATS","error sending LC stats to RP","The SPA driver encountered an error while sending the LC stats to the RP.","Reload the SPA card and if the problem persistscall the technical support representative."
"DWDM","3","MALLOC_FAIL","malloc failure creating G.709 port on slot [dec]","The SPA driver detected a memory error on the SPA card.","Reload the card and if the problem persists call TAC."
"DWDM","3","RPC_FAILED","Application error rc = [dec]:","The system failed to retrieve the information required to execute the command.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"DWDM","3","RPC_INIT_FAIL","DWDM RPC init failure","The system failed to create the resources required to process user interface commands for transceivers. The error is not fatal but some show commands could fail.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"DWDM","3","RPC_PROCESSING_ERROR","DWDM RPC error: [chars]","Non Fatal error occurred in processing an RPC messsage.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"DWDM","3","RX_G709_INFO","Failed receiving G709 info from slot [dec] rc = [dec]","The SPA driver did not receive the necessary G.709 OTN protocol information from the slot.","Please check the configuration of the interfaces and controllers and correct the configuration if necessary. If the problem persists contact your Cisco technical support representative."
"DWDM","3","RX_LOS_THRESHOLD","Failed to config rx los threshold = [dec] on slot [dec] rc = [dec]","The SPA driver detected an error in configuring the transponder receive power threshold.","Reload the SPA card and if the problem persistscall TAC."
"DWDM","3","TIMER_ERR","Timer error","The Driver did not obtain an expired timer from the timer tree for the DWDM process.","The SPA driver has encountered an error event on the SPA card. If the condition persists, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"DWDM","4","G709ALARM","[chars]: [chars] [chars]","The specified G709 Alarm has been declared or released.","Repair the source of the alarm."
"EAP","2","PROCESS_ERR","[chars]","A critical condition exists that prevents the system from performing an operation related to an EAP process.","Reload the system."
"EAP","4","BADPKT","IP=[IP_address]| HOST=[chars]","The system received an invalid or malformed EAP packet from the specified host.","Check the specified host for the EAP operation."
"EAP","6","MPPE_KEY","IP=[chars]| MPPE_RECV_KEY_LENGTH=[dec]","The system received an MPPE key for the specified host.","No action is required."
"EARL","0","TASK_SPAWN_FAIL","Failed to initialize task '[chars]'","The EARL component failed to start a task required by the system to work properly. The task name is specified in the error message. Most errors will cause a system reload. However, in some cases, only the feature that failed to start will be affected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EARL","2","PATCH_INVOCATION_LIMIT","[dec] Recovery patch invocations in the last 30 secs have been attempted. Max limit reached","The system attempted the EARL recovery for the maximum number of times that are permitted in the last 30 seconds. The module has been automatically reset instead of attempting recovery.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EARL","2","SWITCH_BUS_IDLE","Switching bus is idle for [dec] seconds","The EARL did not switch any packets on the EARL bus. A module or line card attempted to access the bus and could not. In most cases, this error appears when a card is not properly seated. A recovery mechanism will attempt to fix the problem. The system reloads if the problem cannot be corrected.","Reseat all modules and line cards on the switch. If the error message recurs after reseating the cards, a hardware problem may exist."
"EARL","2","SWITCH_BUS_STALL","Switching bus stall detected. Backplane bus stall status: [dec]","The EARL did not switch any packets on the EARL bus. A recovery mechanism will attempt to fix the problem. The system reloads if the problem cannot be corrected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EARL","3","RESET_LC","Resetting module in slot [dec]. (Errorcode [dec])","The specified module did not respond to a critical message. This condition indicates a hardware error and might be a transient error only. The system has reset the module to fix the error.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EARL","4","EBUS_SEQ_ERROR","Out of Sync error.","The EARL has detected an out-of-synchronization condition on the bus. A recovery mechanism will attempt to fix the problem.","Reseat and then reset the module. If the error remains, upgrade the software to Cisco IOS Release 12.2(18)SXF or later."
"EARL","4","NF_USAGE","Current Netflow Table Utilization is [dec]%","The NetFlow table utilization exceeds a preset threshold percentage.","No action is required."
"EARL_ACL_FPGA","2","INTR_FATAL","EARL ACL FPGA : Non-fatal interrupt [chars]","The EARL ACL FPGA detected the specified unexpected fatal condition. This message indicates a hardware failure or malfunction. The system will reload to attempt to fix the problem.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EARL_ACL_FPGA","3","INTR_WARN","EARL ACL FPGA : Non-fatal interrupt [chars]","The EARL ACL FPGA detected the specified unexpected nonfatal condition.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EARL_ACL_FPGA","4","CPU_PAR_ERR","EARL ACL FPGA : CPU Parity error [chars]","The EARL ACL FPGA detected a CPU parity error.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EARL_ACL_FPGA","4","MEM_PAR_ERR","EARL ACL FPGA: Counter Memory Parity error. Error address [hex]","The EARL ACL FPGA detected a memory parity error.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EARL_DRV_API","0","TASK_SPAWN_FAIL","Failed to spawn task '[chars]'","The system failed to perform the specified task.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EARL_DRV_API","2","SIG_INST_FAIL","[chars]: Failed to install signal handler","The system failed to install the process signal handler.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EARL_DRV_API","4","NOMEM","Malloc failed: [chars] [dec]","The system is running out of memory.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EARL_L2_ASIC","0","EXCESSIVE_FT_TBL_ECC_ERR","EARL L2 ASIC [dec]: Too many bad entries in L2 Forwarding Table","The EARL Layer 2 ASIC detected too many errors in the forwarding table. This condition indicates hardware malfunction and causes the system to reload.","If this problem is seen more than once, it could be a case of faulty hardware. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EARL_L2_ASIC","0","FATAL_INTR","L2 Forwarding Engine: fatal interrupt: interrupt status [hex], interrupt mask [hex]","Critical interrupts might have caused system forwarding to cease.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EARL_L2_ASIC","2","PARITY_ERR","L2 Forwarding Engine: parity interrupt #[dec]: address [hex], Data: [hex], [hex], [hex], [hex]","A parity error was detected while accessing the Layer 2 forwarding table.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EARL_L2_ASIC","3","INTR_FATAL","EARL L2 ASIC [dec]: fatal interrupt [chars]","The EARL Layer 2 ASIC detected an unexpected fatal condition. This message indicates a hardware failure or malfunction. The system will reload to fix the problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EARL_L2_ASIC","3","INTR_WARN","EARL L2 ASIC [dec]: Non-fatal interrupt [chars]","The EARL Layer 2 ASIC detected an unexpected nonfatal condition.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EARL_L2_ASIC","4","DBUS_HDR_ERR","EARL L2 ASIC #[dec]: Dbus Hdr. Error occurred. Ctrl1 [hex]","The EARL Layer 2 ASIC detected an invalid header in the DBUS. This error is due to hardware that has failed, an incorrect configuration of the module software, or invalid packets that were dropped because of an OIR operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EARL_L2_ASIC","4","DBUS_SEQ_ERR","EARL L2 ASIC #[dec]: Dbus Seq. Error occurred (Ctrl1 [hex])","The EARL Layer 2 ASIC detected a DBUS sequence mismatch error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EARL_L2_ASIC","4","FT_ERR","EARL L2 ASIC [dec]: Forwarding table bank [dec] encountered [chars] ecc error at address [hex]","The EARL Layer 2 ASIC detected a nonfatal condition in one of the banks of the forwarding table. The bank and address of the forwarding table are specified in the error message.","This message is informational. The device has detected and corrected the error."
"EARL_L2_ASIC","4","FT_INVLD_ADDR","Forwarding table bank [dec] encountered invalid address [hex]","The EARL Layer 2 ASIC attempted to access an invalid address in the forwarding table. Because there are only 12 pages (0-11) per line, access to page 12-15 will be invalid.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EARL_L2_ASIC","4","INTR_THROTTLE","Throttling '[chars]' interrupt exceeded permitted [int]/[dec] interrupts/msec","Excessive interrupts were generated by the EARL ASIC. Interrupt throttling has been performed to protect the supervisor engine.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EARL_L2_ASIC","4","INV_REG","EARL L2 ASIC: Attempt to [chars] invalid register","An attempt was made to read or write to an invalid register of the EARL Layer 2 ASIC.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EARL_L2_ASIC","4","L2L3_SEQ_ERR","EARL L2 ASIC #[dec]: L2L3 Mismatch seq #[hex]","The EARL Layer 2 ASIC detected a Layer 2-Layer 3 sequence mismatch error. A recovery mechanism will attempt to fix the problem.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EARL_L2_ASIC","4","SRCH_ENG_FAIL","EARL L2 ASIC Search Engine has failed","The EARL Layer 2 ASIC search engine failed to terminate a search. A recovery mechanism fixes the unexpected condition.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EARL_L3_ASIC","3","INTR_FATAL","EARL L3 ASIC: fatal interrupt [chars]","The EARL Layer 3 ASIC detected an unexpected fatal condition. This message indicates a hardware failure or malfunction. The system will reload to attempt to fix the problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EARL_L3_ASIC","3","INTR_WARN","EARL L3 ASIC: Non-fatal interrupt [chars]","The EARL Layer 3 ASIC detected an unexpected non-fatal condition. This indicates that a bad packet was received and dropped. Several conditions can cause a packet to be considered bad; for example, the size of an Ethernet frame was reportedto be different than the expected IP packet size. In older Cisco IOS releases, these packets are normally dropped without being logged.","This message is informational only, and can occur due to conditions such as bad NIC cards, bad NIC drivers, or a bad application. Use a network sniffer or configure a SPAN session to identify the source device that is sending the erroneous packets. Also, examine the adjacent Cisco device for errors. The following commands can be configured to stop verifying checksum or length errors:"
"EARL_L3_ASIC","4","CPU_PAR_ERR","EARL L3 ASIC: CPU Parity error. Error data [hex]. Error address [hex]","The EARL Layer 3 ASIC detected a CPU parity error. This condition is caused by an interprocess communication error between the CPU and Layer 3 ASIC.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EARL_L3_ASIC","4","INTR_THROTTLE","Throttling '[chars]' interrupt exceeded permitted [int]/[dec] interrupts/msec","Excessive interrupts were generated by the EARL ASIC. Interrupt throttling has been performed to protect the supervisor engine.EARL_NETFLOW MessagesThis section contains Enhanced Address Recognition Logic NetFlow (EARL_NETFLOW) messages.EARL_NETFLOW-0Error Message    %EARL_NETFLOW-0-NF_ECC_MAX: Netflow ECC Error Threshold Reached, Total Ecc Errors [[dec]] Explanation    The total number of NetFlow ECC errors has crossed the maximum threshold. The maximum allowable of NetFlow ECC errors is 2000. The system will perform a crash dump and will be inoperable. The output of the show tech-support command will also be displayed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EARL_NETFLOW","3","NF_ECC_RSRV","Netflow ECC Error Occured, Reserved NF location [[hex]]","The number of ECC errors per NetFlow TCAM entry has reached the maximum threshold (three or more ECC errors). The NetFlow TCAM location will now be marked as reserved and can no longer be used.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EARL_NETFLOW","3","NF_ECC_SOFT_MAX","Too many Netflow ECC errors have occurred, Total Ecc Errors [[dec]]","The total number of NetFlow ECC errors has exceeded the soft limit number. The soft limit of NetFlow ECC errors is 2500. The hard limit is 5000. When the hard limit is reached, the line card will reboot.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EARL_NETFLOW","4","ICAM_THRLD","Netflow ICAM threshold exceeded, ICAM Utilization [[dec]%]","The NetFlow ICAM is almost full. Aggressive aging is temporarily enabled.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EARL_NETFLOW","4","NF_AGG_CACHE_THR","Netflow [chars] aggregation cache is almost full.","The aggregation cache for NetFlow is almost full. This condition might cause a high CPU load.","Consider increasing the size of the aggregation cache, or remove the aggregation cache configuration specified in the error message."
"EARL_NETFLOW","4","NF_FULL","Netflow Table Full, ICAM occupancy [[dec]%], TCAM occupancy [[dec]%], Entry creation failures [[dec]]","The NetFlow table is full, possibly because of faulty hashing behavior.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EARL_NETFLOW","4","NF_TIME_SAMPLING","Time-based sampling requests could not be processed in time.","Time-based sampling requests could not be processed in a timely fashion. This condition means that the sampling result might not be accurate.","Consider using packet-based sampling. Packet-based sampling uses an algorithm that ensures the sampling results will be accurate, even if they are not processed in the allotted time."
"EARL_NETFLOW","4","TCAM_THRLD","Netflow TCAM threshold exceeded, TCAM Utilization [[dec]%]","The NetFlow TCAM is almost full. Aggressive aging is temporarily enabled.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EARL_NETFLOW","5","NF_ECC_REMOVE","Netflow ECC Error Occured, Deleted NF entry [[hex]]","A NetFlow ECC error occurred. The affected NetFlow entry has been deleted at the address specified so that a new entry will be created.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EC","5","CANNOT_BUNDLE_QOS1","Removed [chars] from port channel as QoS attributes of port and port-channel are different.","The port specified in the error message cannot join the port channel, because the QoS attributes of this port are not consistent withthe QoS attributes of the port channel.","Match the QoS attributes of the specified port to the QoS attributes of other member ports in the port channel. Use the show queueing interface command to display the QoS attributes of a port."
"EC","5","COMPATIBLE","[chars] is compatible with port-channel members","The specified port was not operational earlier because its attributes were different from the attributes of the port channel or the attributes of the ports within the port channel. The system detects that the attributes of the specified port now match the port channel attributes.","This is an informational message only. No action is required."
"EC","5","DONTBNDL2","[chars] suspended: port in half-duplex for LACP","For LACP EtherChannel, if the member port is in half-duplex mode, the port will be in a suspended state.","Configure port duplex to full duplex."
"EC","5","MINLINKS_MET","Port-channel [chars] is up as its bundled ports ([dec]) meets min-links","The administrative configuration of minimum links is equal to or less than the number of bundled ports. As a result, this port channel is operational.","No action is required."
"EC","5","MINLINKS_NOTMET","Port-channel [chars] is down bundled ports ([dec]) doesn't meet min-links","The administrative configuration of minimum links is greater than the number of bundled ports. As a result, this port channel is no longer operational.","Reduce the number of minimum links for the specified group, or add more ports to this port channel so that they bundle."
"EC","5","PROTO_MISMATCH","Port-Channel [dec] has one aggregator with protocol mismatch","EtherChannel software disabled an aggregator under this port-channel and encountered a protocol mismatch on the aggregator. This means that the ports in the port-channel have not been all configured with the same protocol and this needs to be fixed.","Please verify the port-channel members configuration and fix it so that all the ports use the same protocol."
"EC","5","SUSPENDED","Port [chars] in port-channel [chars] is being suspended","EtherChannel software is unable to bundle the physical port in the port-channel. As the standalone disable feature is enabled, the port is going in the suspended state. Please check the configuration on the peer side of this port-channel.","Please verify the port-channel configuration of the port connected to the port for which this error messsage appeared."
"EC","5","VSS_MINLINKS_MET","Members of the Port-channel [chars] on switch [dec] is up as its bundled ports ([dec]) meets min-links","The administrative configuration of minimum links is equal or less than the number of bundled ports from the switch. Therefore all the ports in the port channel from that switch has been brought up.","None."
"EC","5","VSS_MINLINKS_NOTMET","All the members of the Port-channel [chars] is down on switch [dec] as the number of bundled ports ([dec]) doesn't meet min-links","The administrative configuration of minimum links is greater than the number of bundled ports from the switch. Therefore all the ports in port-channel from that switch has been brought down.","Reduce the min-links configuration for this group or add more ports to this port-channel from the switch to have them bundle."
"EM","3","EXCEED","EM exceed maximum open events ([dec]).","The total number of open events exceeded the maximum number of possible open events. The maximum number that the EM server permits is specified in the error message. EM clients are either opening too many events or not closing events within the permitted time period.","Enter the show em state | inc em_type command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EM","3","FAIL","The specified EM Function failed ([chars]).","The specified EM function failed. This condition might be caused by incorrect logic or a memory corruption.","Enter the show em state command and the show em status command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EM","3","NOMEM","The EM failed to allocate memory resources for the specified EM function ([chars]).","The EM failed to allocate memory resources for the specified function because memory is running low.","Enter the show memory summary command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EM","3","NULLPTR","The pointer in a specified EM function ([chars]) is incorrectly NULL.","The pointer in the specified EM function is incorrectly NULL. This condition might be caused by incorrect logic or a memory corruption.","Enter the show em state command and the show em status command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EM","4","AGED","The specified EM client (type=[dec], id=[dec]) did not close the EM event within the permitted amount of time ([dec] msec).","A timeout occurred. This condition is minor and should not affect the functionality of the switch.","Enter the show em state command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EM","4","INVALID","The specified EM function ([chars]) received Invalid operands <[dec]>.","The EM client used invalid API parameters.","Enter the show em state command and the show em status command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EM","4","LIMIT","EM exceed open events limit ([dec]).","The EM has exceeded the permitted number of open events. The open event limit is 5000.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EM","4","NOTUP","The EM is not available ([chars]).","The EM is not available because some basic initialization failed. This condition might be caused by failure of a basic infrastructure functionality or a memory corruption.","Enter the show em state command and the show em status command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EM","4","SEARCH","The EM function ([chars]) searched for the specified open event ([dec]), but the search failed.","The specified EM function could not find the specified open event. This condition might be caused by a memory corruption.","Enter the show em state command and the show em status command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EM","4","SENDFAILED","The specified EM client (type=[dec]) failed to send messages to standby.","The redundant supervisor engine is not updated because the specified EM client failed to send messages to the redundant supervisor engine. Do not attempt to failover to redundant supervisor engine.","Enter the show checkpoint clients command. If you cannot determine the cause of the error from the error message text or from the show checkpoint clients output, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EM_ISSU","2","GET_BUFFER","Event Manager ISSU client failed to get buffer for message. Error: %d (%s)","The Event Manager ISSU client failed to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"EM_ISSU","2","INIT","Event Manager ISSU client initialization failed to %s. Error: %d (%s)","The Event Manager ISSU client could not be initialized. This initialization failure must be addressed before an in-service software upgrade or downgrade can be performed successfully. Otherwise, a software upgrade or downgrade will result in downtime.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EM_ISSU","2","SEND_NEGO_FAILED","Event Manager ISSU client failed to send negotiation message. Error: %d (%s)","The Event Manager ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"EM_ISSU","2","SESSION_NEGO","Event Manager ISSU client encountered unexpected client nego_done. Error: %d (%s)","The Event Manager ISSU client encountered a 'client negotiation done' state that was unexpected. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"EM_ISSU","2","SESSION_REGISTRY","Event Manager ISSU client failed to register session information. Error: %d (%s)","The Event Manager ISSU client failed to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"EM_ISSU","3","INVALID_SESSION","Event Manager ISSU client does not have a valid registered session.","The Event Manager ISSU client does not have a valid registered session.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"EM_ISSU","3","MSG_NOT_OK","Event Manager ISSU client 'Message Type %d' is not compatible","The Event Manager ISSU client received an incompatible message from the peer device. The message cannot be processed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"EM_ISSU","3","MSG_SIZE","Event Manager ISSU client failed to get the MTU for Message Type %d. Error: %d (%s)","The Event Manager ISSU client was unable to calculate the MTU for the specified message. The Event Manager ISSU client is unable to send the message to the standby device.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, show issu message group, and show issu negotiated version commands and your pertinent troubleshooting logs."
"EM_ISSU","3","OPAQUE_MSG_NOT_OK","Event Manager ISSU client 'Opaque Message Type %d' is not compatible","The Event Manager ISSU client received an incompatible (opaque) message from the peer device. The message cannot be processed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, show issu message group, and show issu negotiated version commands and your pertinent troubleshooting logs."
"EM_ISSU","3","SESSION_UNREGISTRY","Event Manager ISSU client failed to unregister session information. Error: %d (%s)","The Event Manager ISSU client failed to unregister session information.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"EM_ISSU","3","TRANSFORM_FAIL","Event Manager ISSU client %s transform failed for 'Message Type %d'. Error: %d (%s)","The Event Manager ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In either case, the Event Manager state between the active device and the standby device is not identical.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"ENT_ALARM","3","NOALARMENT","[chars]","All entities that could have alarm conditions set for them should be registered with the alarm subsystem for the Cisco IOS software. This message indicates that the normal registration of entities in the Cisco IOS software alarm subsystem has failed, and that one or more entities could not be registered. The message text indicates the alarm entity that could not be registered. Any alarm conditions against the entity specified in the message text cannot be reported. This message does not indicate that the entity specified in the message has undergone an error condition.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ENT_ALARM","6","INFO","[chars] [chars] [chars] [chars] [chars]","This message provides alarm assertion or deassertion information.","This is an informational message only. No action is required."
"ENT_API","4","NOALIAS","Physical entity not found when adding an alias with physical index = [dec] and logical index = [dec] to the Entity MIB","A timing issue was detected when the system or the module is brought up. This issue has no impact on system performance or management functionality.","No action is required."
"ENT_API","4","NOPORT","Physical entity does not have a Port PhysicalClass when adding an alias with physical index = [int], logical index = [int], phyDescr = [chars], phyName = [chars], phyClass = [int], phyContainedIn = [int], to the Entity MIB","An attempt to add an alias entry to the Entity MIB was made. The physical entity with the specified index does not have an entPhysicalClass of 10 (Port class) and so the alias entry creation failed. See RFC2737 for the definition of the PhysicalClass textual convention and the aliasMappingEntry object.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ENVIRONMENT","3","OVERTEMP","[chars] [chars] [chars] [chars]","The internal chassis temperature has exceeded the maximum temperature threshold.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ENVIRONMENT","3","RPS_FAILED","[chars] [chars] [chars] [chars]","Only one power supply was detected for the system in dual-power mode, or the power supply is failing.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ENVIRONMENT","3","UNDERTEMP","[chars] [chars] [chars] [chars]","The internal chassis temperature is below the minimum temperature threshold.","No action is required."
"ENVIRONMENT","4","CONFIG_OVERTEMP","[chars] [chars] [chars] [chars]","The chassis inside temperature has exceeded the configured threshold, but is less than or equal to the maximum allowable internal chassis temperature.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ENVM","2","TEMP_SENSOR_READFAIL","Failed to access the Temperature sensor on the linecard. Resetting the linecard.","The local CPU on the Enhanced FlexWAN module was unable to access the temperature sensor on the module. The module will attempt to recover by resetting itself.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ENVM","3","DISABLE","Environmental monitoring for [chars] disabled ([chars])","Environmental monitoring for the indicated hardware component could not be initiated. This error message is displayed if environmental monitoring for the whole system, or a particular hardware component is disabled. Operating the system with the environmental monitoring disabled can be dangerous.","Address the cause for the environmental monitoring being disabled as indicated in the error message. Depending on whether a particular hardware component is affected or the whole system, either the card should be removed or the entire system taken offline for a power shutdown until the problem is resolved. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ENVM","3","ENVDATA_MISSING","Environmental monitoring information for card in [chars] is not present in the IDPROM","Environmental threshold data for the card in the specified slot is not present in the board IDPROM. The system will not monitor the voltage and temperature readings for the specified card.","Enter the show diag slot-number command for the specified slot. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ENVM","3","ENVINFO_MISSING","Voltage threshold information for [chars] is not present in the [chars]IDPROM for the card in [chars]","Environmental threshold data for the specified voltage is missing from the threshold table in the IDPROM. The system will not monitor the voltage and temperature readings for the specified card.","Enter the show diag slot-number command for the specified slot. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ENVM","3","SUBSLOT_SHUTDOWN","Environmental monitor initiated shutdown of the card in subslot [dec]/[dec] ([chars] measured at [chars])","The environmental monitor initiated a subslot shutdown due to a temperature or voltage condition.","Look at previous environmental messages to determine the cause of the shutdown and correct if possible. If you think the shutdown was in error, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ENVM","3","TEMP_SENSOR_DISABLED","Access to Temperature sensor on module in slot [dec] is disabled","During previous reloads, this module experienced a timeout while accessing the temperature sensor. All further access to the temperature sensor will be disabled. This condition indicates a possible problem with the temperature sensor.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ENVM","4","LONGBUSYREAD","C2W Interface busy for long time reading temperature sensor [dec]","The Cisco 2 wire (C2W) interface has taken an unusually long time to read the specified temperature sensor.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ENVM","4","LONGBUSYWRITE","C2W Interface busy for long time writing temperature sensor [dec]","The Cisco 2 wire (C2W) interface has taken an unusually long time to write to the specified temperature sensor.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ENVM","4","RPSFAIL","[chars] may have a failed channel","One of the power supplies in a dual (redundant) power supply may have failed.","Check the inputs to the power supply or replace the faulty power supply as soon as possible to avoid an unplanned outage. If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support"
"ENVM","4","WRITEERROR","Error writing temperature sensor [dec]","The Cisco 2 wire (C2W) interface has encountered an error while writing to the specified temperature sensor.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ENV_MON","2","BUSBRD_TEMP","[chars] temperature has reached critical levels","The specified temperature sensor has signaled an overtemperature condition.","Check the supply. Attempt to resolve the temperature problem. Check to ensure that all router doors are in place and are closed. Check to ensure that the fans are operating. Remove the affected cards, check their temperature and, if required, allow them to cool and reinsert them. Operation of overtemperature equipment is not recommended because the equipment might become damaged. If the condition is not resolved, power the unit off. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ENV_MON","5","CSC_FAIL_SUPPLY_POWER_TO_FANS","CSC in slot [dec] could not supply power to fan tray","The indicated clock and scheduler card (CSC) could not supply power to the fan trays.","Turn the router off and then on to attempt to clear the problem. Remove and reinsert the fan tray, and then the CSC. If the problem persists, contact your Cisco technical support representative to replace the indicated CSC."
"ENV_MON","6","CANTSHUT","Cannot shut down card in this slot","The attempt to shut down the line card has failed.","No action is required."
"ENV_MON","6","INSALM","ALARMCARD [chars] was inserted in slot [dec]","The OIR facility has detected the insertion of an alarm card from the slot specified in the message text.","No action is required."
"ENV_MON","6","INSFAN","The Fan tray has been inserted into slot [dec]","The OIR facility has detected the insertion of a PEM from the slot specified in the message text.","No action is required."
"ENV_MON","6","INSPEM","PEM number [chars] inserted into slot [dec]","The OIR facility has detected the insertion of a PEM from the slot specified in the message text.","No action is required."
"ENV_MON","6","INSPEM_GSR_POWERSHELF","Powersupply [chars] inserted","The OIR facility detected the insertion of a PEM on the power shelf-basedinternet router.","No action is required."
"ENV_MON","6","INTERNAL_ERROR","Internal error [dec] in [chars] - contact Cisco technical support","An unexpected internal error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ENV_MON","6","REMALM","ALARMCARD [chars] was removed from slot [dec]","The OIR facility detected the removal of alarm card from the slot specified in the message text.","No action is required."
"ENV_MON","6","REMFAN","The Fan tray has been removed from slot [dec]","The OIR facility has detected that the fan tray has been removed.","No action is required."
"ENV_MON","6","REMPEM","PEM number [chars] removed from slot [dec]","The OIR facility has detected the removal of a PEM from the slot specified in the message text.","No action is required."
"ENV_MON","6","REMPEM_GSR_POWERSHELF","Powersupply [chars] removed","The OIR facility has detected the removal of a PEM on a power shelf-based internet router.","No action is required."
"EOBC","0","EOBC_JAM_FATAL","[chars] in slot [dec] is jamming the EOBC channel.  It has been disabled.","The primary supervisor engine EOBC hardware is faulty. There is no redundant supervisor engine to take over, so the switch has been shut down.","Immediately replace the supervisor engine in the slot specified in the error message."
"EOBC","2","EOBC_JAM","EOBC channel is jammed.  Attempting to diagnose the source of the problem and recover if possible.","The SP is unable to communicate with other processors in the system because of a problem with the EOBC channel. The problem could be due to faulty EOBC hardware on the supervisor engine or due to a module with a faulty connector to the EOBC channel. The SP will attempt to recover automatically. The success of this automatic recovery will be communicated through more messages.","No action is required."
"EOBC","2","EOBC_JAM_RECOVERED","[chars] in slot [dec] is jamming the EOBC channel.  It has been disabled. [chars]","The specified module has faulty hardware and is adversely affecting the operation of the switch. The remaining modules will be power cycled and brought online.","Immediately replace the module in the slot specified in the error message."
"EOBC","3","NOEOBCBUF","No EOBC buffer available.  Dropping the packet.","The EOBC receive buffer pool has been exhausted. No further input packets can be processed until some buffers are returned to the pool.","After buffers are returned to the pool, if processing continues normally, no action is required. Otherwise, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EOS","3","EOS_PAUSE_FAIL","[chars]","An attempt to pause the forwarding of traffic from an EOS ASIC interface FPGA to another ASIC has timed out. Depending on the status register value of the ASIC interface FPGA, traffic disruption might occur.","If normal traffic processing does not resume, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EOS","3","QUEUE_ALLOC_FAILED","Failed to allocate queue in the EOS FPGA for SPA in bay ([dec])","The system failed to allocate the EOS ASIC queue for the SPA in the specified bay. This condition might lead to traffic disruption.","If normal traffic processing does not resume, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EOS","4","EOS_WARN_INT","[chars]","The EOS ASIC interface FPGA received a nonfatal interrupt. This interrupt should not affect normal operation.","No action is required."
"EOS","5","PAUSE_FAIL","[chars]","An attempt to pause the forwarding of traffic from an EOS ASIC interface FPGA to another ASIC has timed out. Depending on the status register value of the ASIC interface FPGA, traffic disruption might occur.","If normal traffic processing does not resume, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EOU","2","PROCESS_ERR","Router could not create a EAPoUDP process","The system could not create an Extensible Authentication Protocol over UDP process.","Reload the system."
"EOU","4","BAD_PKT","IP=[IP_address]| Bad Packet=[chars]","The system received an invalid or malformed EAP packet from the specified host.","Check the specified host for the EAP operation."
"EOU","4","MSG_ERR","Unknown message event reveived","The EOU authentication process received an unknown message event.","If this message recurs, reload the system."
"EOU","4","PROCESS_STOP","PROCESS=[chars]| ACTION=[chars].","The specified process has stopped.","Reload the system."
"EOU","4","SOCKET","EAPoUDP socket binding fails for PORT=[hex]. Check if the interface has valid IP address.","The EOU socket could not bind its port to an valid interface address.","This condition is probably caused by a missing IP address on the interface. Configure a valid IP address for the interface."
"EOU","4","UNKN_EVENT_ERR","UNKNOWN Event for HOST=[IP_address]| Event=[dec].","An unknown event for the EOU process has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EOU","4","UNKN_PROCESS_ERR","An unknown operational error occurred.","The EOU process cannot function due to an internal system error.","Reload the system."
"EOU","4","UNKN_TIMER_ERR","An unknown Timer operational error occurred","The EOU process cannot function due to an internal system error.","Reload the system."
"EOU","4","VALIDATION","Unable to initiate validation for HOST=[IP_address]| INTERFACE=[chars].","EOU could not start posture validation for the specified host. This condition is probably caused by a failure to bind the EOU port.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EOU","4","VERSION_MISMATCH","HOST=[IP_address]| Version=[dec]","The specified host detected a mismatch in EOU versions.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EOU","5","AAA_DOWN","AAA unreachable. METHODLIST=[chars]| HOST=[IP_address]| POLICY=[chars].","AAA servers defined by the method list are unreachable for the given host and the policy being applied.","Check connectivity to the AAA servers."
"EOU","5","RESPONSE_FAILS","Received an EAP failure response from AAA for host=[IP_address]","The system received an EAP failure response from AAA, which indicates the unsuccessful validation of host credentials.","No action is required."
"EOU","6","AUTHSTATUS","[chars]|[IP_address]","This message displays the authentication status (Success, Failure) for the specified host.","This message is informational. No action is required."
"EOU","6","AUTHTYPE","IP=[IP_address]| AuthType=[chars]","This message displays the authentication type for the specified host.","This message is informational. No action is required."
"EOU","6","CTA","IP=[IP_address]| CiscoTrustAgent=[chars]","This message indicates whether or not Cisco Trust Agent was detected on the specified host.","Install Cisco Trust Agent on the host if it was not detected."
"EOU","6","IDENTITY_MATCH","IP=[IP_address]| PROFILE=EAPoUDP| POLICYNAME=[chars]","Because the system found the specifed host in the EOU identity profile, there will be no EOU association with the host and the local policy.","If you do not want the specified host to be exempted from authentication, remove its entry from EOU identity profile."
"EOU","6","POLICY","IP=[IP_address]| [chars]=[chars]","The system received policy attributes from AAA for the specified host.","This message is informational. No action is required."
"EOU","6","POSTURE","IP=[IP_address]| HOST=[chars]| Interface=[chars]","This message displays the posture validation status for the specified host.","This message is informational. No action is required."
"EOU","6","SESSION","IP=[IP_address]| HOST=[chars]| Interface=[chars]","An entry was created or deleted for the host on the specified interface.","This message is informational. No action is required."
"EOU","6","SQ","IP=[IP_address]| STATUSQUERY|[chars]","The status query result for the specified host either failed or was invalid.","This message is informational. No action is required."
"EPIF_PORT","0","INTERNAL_PANIC","[chars]","A Panic Condition.EPLD_STATUS_OPEN MessagesThis section contains EPLD programming status file data processing (EPLD_STATUS_OPEN) messages.EPLD_STATUS_OPEN-4Error Message    %EPLD_STATUS_OPEN-4-ERROR_ALLOC: %Error: Can't allocate [dec] bytes for epld status data Explanation    The system is unable to allocate required memory to access the file.","Determine the memory usage of the system, and retry the operation."
"EPLD_STATUS_OPEN","4","ERROR_OPEN","%Error: Can't open [chars]","The system is unable to open the specified file.","Ensure that the filename is correct. Enter the dir command to verify the filename."
"EPLD_STATUS_OPEN","4","ERROR_READ","%Error: status file [chars] read failed","An unknown error occurred while the system was reading the status program file to a local buffer.","Delete and recopy the file. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EPLD_STATUS_OPEN","4","ERROR_REMOVE","%Error: status file [chars] remove failed","An unknown error occurred while the system was removing the status program file from nonvolatile memory.","Delete the file manually. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EPLD_STATUS_OPEN","4","ERROR_SIZE","%Error: Bad file size [chars]","The file is too small or too large for a programming status file.","Enter the dir command, and determine the size of the file. Retry the operation."
"EPLD_STATUS_OPEN","4","ERROR_WRITE","%Error: status file [chars] write failed","An unknown error occurred while the system was writing the status program file to nonvolatile memory.","Delete and recopy the file. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EPM","4","POLICY_APP_FAILURE","IP=%i| MAC=%e| AUDITSESID=%s| AUTHTYPE=%s| POLICY_TYPE=%s| POLICY_NAME=%s| RESULT=FAILURE| REASON=%s","The displayed policy for the client could not be applied by the Policy Enforcement Module (EPM) for the reason indicated in the message.","Take appropriate action based the failure reason indicated in the message."
"EPM","6","AAA","POLICY=%s | EVENT=%s","A download request has been sent and downloaded successfully for the specified downloadable ACL (dACL).","No action is required."
"EPM","6","IPEVENT","IP=%i| MAC=%e| AUDITSESID=%s| AUTHTYPE=%s| EVENT=%s","An IP wait, release, or assignment event has occurred with respect to the specified host.","No action is required."
"EPM","6","POLICY_APP_SUCCESS","IP=%i| MAC=%e| AUDITSESID=%s| AUTHTYPE=%s| POLICY_TYPE=%s| POLICY_NAME=%s| RESULT=SUCCESS","The displayed policy for the client has been applied successfully by the EPM.","No action is required."
"EPM","6","POLICY_REQ","IP=%i| MAC=%e| AUDITSESID=%s| AUTHTYPE=%s| EVENT=%s","A policy application or remove request has been received by the EPM.","No action is required."
"ERR_C6K_STACK_MIB","3","ERR_C6K_STACK_MIB_ICC_NO_PROC","[chars]: Failed to create the vs_stack_mib_sp ICC Process","Failed to create the vs_stack_mib_sp ICC Process.","No action is required."
"ERR_C6K_STACK_MIB","3","ERR_C6K_STACK_MIB_ICC_Q_NULL","[chars]: Failed to create the ICC queue for C6K STACK MIB","Failed to create the ICC queue for C6K STACK MIB.","No action is required."
"ERR_DET","5","ERR_DET_LOW_MEM","Very low memory, dump debuginfo, local %u, io %u","A low-memory condition was detected. Debugging information will be dumped.","No action is required."
"ERR_DET","5","ERR_DET_NO_EOBC_INPUT","No EOBC input, dump debuginfo, interval %u, times %u","No Ethernet Out-of-Band Channel (EOBC) input was received. Debugging information will be dumped.","No action is required."
"ESCON","3","ACCESS_FAIL","LRC access Failed","Line card redundancy controller (LRC) access has failed.","Remove and reinsert the ESCON aggregation card. If the problem persists, power cycle the ESCON aggregation card. If the problem still persists, replace the ESCON aggregation card."
"ESCON","3","CRC16_ERR_THR_ALM","ESCON CRC-16 Error Threshold [chars]","The threshold of allowable CRC-16 errors has been exceeded.","Check the client receive cable and the SFP optics. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESCON","3","CRC32_ERR_THR_ALM","CRC-32 Error Threshold [chars]","The threshold of allowable CRC-32 errors has been exceeded.","Check the client receive cable and SFP optics. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESCON","3","ESCON_RDWRFAIL","Read/write failed [[chars]]","A read or write error occurred while the hardware was being accessed.","Remove and reinsert the ESCON aggregation card. If the problem persists, power cycle the ESCON aggregation card. If the problem still persists, replace the ESCON aggregation card."
"ESCON","3","HEC_ERR_THR_ALM","CDL-HEC Error Threshold [chars]","The threshold of allowable CDL HEC errors has been exceeded.","Check the network cable for sharp bends, and ensure the connectors are clean and connected properly."
"ESCON","3","HW_LASER_DOWN_ALM","Remote Loss of Light [chars]","The optics laser has been disabled.","Check the remote client receive cable and the SFP optics."
"ESCON","3","IDPROM_ACCESS_FAIL","Access to IDPROM Failed","The IDPROM could not be accessed.","Remove and reinsert the ESCON aggregation card. If the problem persists, power cycle the ESCON aggregation card. If the problem still persists, replace the ESCON aggregation card."
"ESCON","3","INT_LPBK_FAIL","Internal CardLoopback Failed","An internal card loopback has failed.","Remove and reinsert the ESCON aggregation card. If the problem persists, power cycle the ESCON aggregation card. If the problem still persists, replace the ESCON aggregation card."
"ESCON","3","LASER_TX_FAULT_ALM","Optic Laser Transmit Fault [chars]","An optical laser transmission fails on an ESCON aggregation card.","Remove and reinsert the ESCON SFP optics. If the problem persists, replace the ESCON SFP optics."
"ESCON","3","LOCAL_FL_LASER_DOWN_ALM","Local Failure [chars]","The optics laser has been disabled.","Check the trunk and switch fabric connection."
"ESCON","3","LOSS_OF_LIGHT_ALM","Transceiver Loss of Light [chars]","The cable for the transceiver has been cut or removed.","Check the client receive cable and the SFP optics."
"ESCON","3","LOSS_OF_LOCK_ALM","Transceiver CDR Loss of Lock [chars]","The CDR cannot lock onto the signal.","Check the client receive cable and the SFP optics."
"ESCON","3","LOSS_OF_SYNC_ALM","Transceiver Loss of Sync [chars]","The transceiver has lost its synchronization.","Check the client receive cable and the SFP optics."
"ESCON","3","LPBK_THRU_PSC_FAIL","Loopback through PSC Failed","An attempt to loopback through the processor and switch card (PSC) has failed.","Remove and reinsert the ESCON aggregation card. If the problem persists, power cycle the ESCON aggregation card. If the problem still persists, replace the ESCON aggregation card."
"ESCON","3","MIB_HW_LASER_DOWN_ALM","Laser Disabled [chars] [chars] [chars]","The client-side laser has been disabled.","Check the remote client receive cable and the SFP optics."
"ESCON","3","MIB_LASER_TX_FLT_ALM","Laser Transmit Fault [chars] [chars] [chars]","The client laser encountered a fault during transmittal.","Remove and reinsert the ESCON SFP optics. If the problem persists, replace the ESCON SFP optics."
"ESCON","3","MIB_LOCAL_FL_LASER_DOWN_ALM","Local Failure, Laser Disabled [chars] [chars] [chars]","The client-side laser has been disabled.","Check the trunk and switch fabric connection."
"ESCON","3","MIB_LOSS_OF_LIGHT_ALM","Loss of Light [chars] [chars] [chars]","The client side transceiver detects a loss of light on an ESCON aggregation card.","Check the client receive cable and the SFP optics."
"ESCON","3","MIB_LOSS_OF_LOCK_ALM","Loss of Lock [chars] [chars] [chars]","The client side transceiver detects a loss of lock on an ESCON aggregation card.","Check the client receive cable and the SFP optics."
"ESCON","3","MIB_LOSS_OF_SYNC_ALM","Loss of Sync [chars] [chars] [chars]","The client side transceiver detects a loss of synchronization on an ESCON aggregation card.","Check the client receive cable and the SFP optics."
"ESCON","3","SEQ_ERR_THR_ALM","ESCON SEQ Error Threshold [chars]","The threshold of allowable sequence errors has been exceeded.","Check the network cable for sharp bends, and ensure that the connectors are clean and connected properly."
"ESCON","3","SYM_ERR_THR_ALM","8b/10b Error Threshold [chars]","The threshold of allowable 8-byte or 10-byte errors has been exceeded.","Check the client receive cable and the SFP optics."
"ESCON","3","UNKNOWN_SFP_INSERTED","Unknown SFP inserted [chars]","An SFP has been inserted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_CRASHINFO","2","CRASHINFO_BAD_REGION","Unable to initialize crashinfo data collection Unknown region type specified: [chars]","Initialization of the crashinfo data collection facility failed. An unknown region type was specified.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_CRASHINFO","2","CRASHINFO_BAD_VENDOR_ID","Unable to initialize crashinfo data collection - the device vendor ID is invalid: [hex], should be: [hex]","Initialization of the crashinfo data collection facility failed due to an incorrect device vendor ID.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_CRASHINFO","2","CRASHINFO_COLLECTION_FAILED","Unable to collect ESF crashinfo data","ESF crashinfo data collection has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_CRASHINFO","2","CRASHINFO_DEV_IN_RESET","Unable to initialize crashinfo data collection - the device is still in reset: [chars]","Initialization of the crashinfo data collection facility failed due to the device being in reset state.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_CRASHINFO","2","CRASHINFO_INIT_FAILED","Unable to initialize ESF crashinfo data collection: [chars]","Initialization of the ESF crashinfo data collection facility failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_CRASHINFO","2","CRASHINFO_PCI_CMD_STAT","Unable to initialize crashinfo data collection PCI_CMD_STAT error indication: [hex]","Initialization of the crashinfo data collection facility failed due to a PCI_CMD_STAT error indication.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_CRASHINFO","2","CRASHINFO_UNSUPPORTED_START_STR","Unable to initialize crashinfo data collection Start string symbol not supported: [chars]","Initialization of the crashinfo data collection facility failed due to unsupported start string.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_CRASHINFO","2","INIT_FAILED","Unable to create crashinfo file, subsystem not properly initialized","An attempt to produce a crashinfo prior to successful completion of subsystem initialization has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_CRASHINFO","2","OPEN_FAILED","Unable to open crashinfo file [chars] ([dec])","Unable to open the file that was used to gather crashinfo.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_CRASHINFO","2","WRITE_FAILED","Unable to write to crashinfo file [chars]: [chars]","Unable to open the file that was used to gather crashinfo.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_CRASHINFO","2","WRITING_CRASHINFO","Writing crashinfo to [chars]","Crashinfo data is written to the specified file.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_DRIVER","2","CHECKSUM_FAILURE","Loading of the CPU code on [chars] failed due to checksum error","When code is loaded onto the CPU of the ESF engine, the code is read back and a checksum is calculated. The checksum that was read before the code was loaded onto the CPU does not match the checksum that was read after the code was loaded. This condition is an indication of a failure of the Rambus RAM for the ESF engine.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_DRIVER","2","FORWARDING_PROCESSOR_READ_FAILURE","Read of register address [hex] failed on [chars].","The host processor tried to read a forwarding processor register on the ESF engine. The read failed after several retries because of collisions with other accesses to that register.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_DRIVER","2","FORWARDING_PROCESSOR_WRITE_FAILURE","Write of register address [hex] failed on [chars].","The host processor attempted to write a register on the forwarding processor for the ESF engine. The write failed after several retries because of collisions with other messages that were attempting to access that register.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_DRIVER","2","PCI_BUS_ERROR","A PCI bus error occurred on [chars]: [chars] (addr=[hex]).","The host processor communicates with the ESF engine by using a PCI interface. While a PCI transaction was being performed, the transaction failed, which caused a bus error on the host processor. The address specified in the message text is the approximate address of the PCI transaction","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_DRIVER","2","PROD_ID_FAILURE","Retrieving the product id failed on [chars]","The host processor could not read the product ID register of the ESF engine. This condition occurs if the ESF engine fails to initialize.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_DRIVER","2","RDRAM_INIT_FAILURE","RDRAM failed to init on [chars]: condition = [chars].","During initialization of the Rambus DRAM, several waiting conditions occur while the code is polling a register to obtain a lock bit. One of the waiting conditions has exceeded the timeout period.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_DRIVER","2","RDRAM_SETUP_FAILURE","The initialization of the RDRAM failed on the [chars]","The Rambus DRAM could not be initialized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_DRIVER","2","SRAM_SETUP_FAILURE","The initialization of the SRAM failed on the [chars]","The SRAM could not be initialized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_DRIVER","2","START_FORWARDING_PROCESSOR_FAILURE","The starting of forwarding processor failed on the [chars]","The forwarding processors of the ESF engine have to be started before processing can begin. The CPU on the ESF engine assists in the starting of the forwarding engines. The CPU reported that an error occurred while the forwarding engines were being started.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_DRIVER","2","UCODE_LOAD_FAILURE","The loading of microcode failed (rc=[dec]) on [chars]","Before processing can begin, microcode has to be loaded on each forwarding processor of the ESF engine. The CPU on the ESF engine assists in the loading of the microcode. While microcode was being loaded, the CPU reported an error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_DRIVER","2","UNEXPECTED_PCI_DOORBELL_INT","Received an unexpected PCI interrupt ([dec]) from [chars] (mb0=[hex] mb1=[hex] mb2=[hex] mb3=[hex]","The CPU on the ESF engine communicates to the host processor through the PCI interface using various bits in an interrupt register. This error indicates that the host processor does not know how to interpret one of those bits.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_DRIVER","2","UNKNOWN_VENDOR_ID","The vendor id ([hex]) of [chars] does not match any known vendor id.","The vendor ID on the ESF engine does not match the vendor ID that is supplied by the manufacturer.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_IPC","2","BAD_HANDLER_ID","An invalid handler ID was specified: [hex]","An invalid handler ID was specified. The handler ID is required to specify which thread the IPC message is being sent to.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_IPC","2","INVALID_ARGUMENT","An invalid argument was specified: [chars]","An invalid argument was specified to one of the IPC library functions.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_IPC","2","PRINT_DATA_INDICATION_FAILED","An error occurred trying to process a PRINT DATA request: [hex] ([dec]:[dec]:[dec]): [chars] ([hex] [hex] [hex])","An error occurred in processing the PRINT DATA request from a thread.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_IPC","2","SEND_MSG_TIMEOUT","IPC command timeout: [hex] [hex] [hex] [hex].","The thread to which an IPC command was issued did not respond in the required time period.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_IPC","2","START_MSG_TIMEOUT","A timeout occurred waiting for the NP to register to support processing IPC commands.","Each network processor (NP) must register to handle processing an IPC soon after startup. If it does not register within the required time period, then initialization cannot be completed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_IPC","2","UNABLE_TO_ACCESS_ESF_MEMORY","Unable to access NP memory: [chars]","An error occurred trying to access network processor (NP) memory.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_IPC","2","UNABLE_TO_CREATE_MSG","Unable to create IPC message","Insufficient resources exist to create a message used for processing the requested IPC command.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_IPC","2","UNABLE_TO_SEND_MSG","Unable to send IPC message","Insufficient resources exist to send a message used for processing the requested IPC command.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_IPC","3","FATAL_ERROR_MSG","Fatal Error indication from [hex] ([dec]:[dec].[dec]): [chars]","A thread has generated a fatal error indication.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_IPC","3","NON_FATAL_ERROR_MSG","Error indication from [hex] ([dec]:[dec].[dec]): [chars]","A thread has generated a nonfatal error indication.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_IPC","3","NON_FATAL_ERROR_MSG_ERROR","Error indication from [hex] ([dec]:[dec].[dec]): [hex] [hex] [hex]","An error occurred trying to process a nonfatal error indication from a thread running on a network processor.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_IPC","6","PRINT_DATA_INDICATION","Print Data indication from [chars] - [hex] ([dec]:[dec].[dec]): [chars]","A network processor thread requested the display of a particular section of memory. This is normally used for debugging.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ESF_IPC","6","STATUS_UPDATE_MSG","Status update from [hex] ([dec]:[dec].[dec]): [hex]","A thread has generated a status update indication.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ETHCNTR","2","MOLSENDTIMEOUT","Molecule send timeout, queue [dec], molecule [hex] [hex]","An attempt to read or write one or more of the hardware settings failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ETHCNTR","3","FLOWCONTROL_DUPLEX_ERROR","Flowcontrol will not take effect until duplex is set to auto.","Flow control cannot take effect until the duplex mode has been set to auto.","Set the duplex mode to auto."
"ETHCNTR","3","HALF_DUX_COLLISION_EXCEED_THRESHOLD","Collisions at [chars] exceed threshold. Considered as loop-back.","The collision at a half-duplex port has exceeded the threshold, and the port is considered to be a loopback port.","No action is required."
"ETHCNTR","3","MOLSENDINT","Molecule send from interrupt handler","An interrupt handler is accessing the hardware in a manner that is not permissible for an interrupt handler.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ETHCNTR","3","NO_HARDWARE_RESOURCES","Not enough hardware resources. Shutting down [chars]","The system currently contains more VLANs and routed ports than the hardware can support.","Reduce the total number of VLANs and routed ports to fewer than 1,023. To maintain this configuration and connectivity across reboots, save the configuration to NVRAM."
"ETHER_CFM","3","CROSS_CONNECTED_CSI","Service ID of received CC [chars] does not match local Service ID [chars].","For a specified service within a domain, the service ID in the continuity check (CC) message should match the locally configured service ID.","Verify that the service IDs are configured correctly using the show ethernet cfm domain command."
"ETHER_CFM","3","LR_FROM_WRONG_FP","received Loopback Reply with correct Transaction IDentifier, but from a Maintenance Point different than Loopback Message's destination","An unknown destination sent a reply to a loopback message that was intended for another device.","Verify that the correct destination MAC address was specified in the CLI while sending the loopback message."
"ETHER_CFM","3","MEP_NOT_CONFIGURED","received CC from unconfigured remote MEP.","While performing a crosscheck, a continuity check (CC) message was received from a remote maintenance endpoint (MEP) that is not configured under the domain submode.","Verify whether the remote MEP should be added to the remote MEP list under the domain using the show ethernet cfm domain command."
"ETHER_CFM","3","RCV_LOCAL_MPID","MPID of CC matches local MPID.","The remote maintenance endpoint identifier (MPID) matches a MPID configured locally for the service.","Either the local MPID or remote MPID should be changed because the MPID should be unique for each service in a network."
"ETHER_CFM","3","TM_EGRESS_BOUNDRY","egress path found for TM is at a higher level than the traceroute message.","Traceroute found a domain boundary on egress because the egress port level is higher than the traceroute message level.","Check that the MIP level on the egress port is at an appropriate level."
"ETHER_CFM","5","IGNORED_VLAN","Ignored VLAN %u in '%s'","An invalid VLAN was ignored in the configuration.","No action is required."
"ETHER_LMI","6","MISMATCHED_VLAN_CONFIGURED","VLAN %s configured but not in VLAN mapping for UNI %s","VLANs are configured on the user network interface (UNI) but do not exist according to VLAN mapping received from the network by the Ethernet local management interface (LMI).","Verify that the configuration of VLANs on the UNI match those assigned."
"ETHER_LMI","6","MISMATCHED_VLAN_NOT_CONFIGURED","VLAN %s not configured but in VLAN mapping for UNI %s","VLAN mappings received from the network by the Ethernet local management interface (LMI) do not match those that are configured on the user network interface (UNI).","Verify that the configuration of VLANs on the UNI match those assigned."
"ETHERNET_LACP","1","ISSU_NOMEMORY","Unit [dec], no memory for [chars]","The requested operation could not be accomplished because of a low memory condition.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"ETHERNET_LACP","3","ISSU_SENDFAILED","LACP ISSU: send message failed, rc = [dec]","The sending of a message has failed. This is an informational message only.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"ETHERNET_LACP","4","ISSU_INCOMPATIBLE","lacp-issu-compat: returned FALSE","The ISSU compatibility matrix check has failed. This is an informational message only.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"ETHERNET_LACP","4","ISSU_XFORM","[chars]: failed, rc=[chars]","The ISSU transform has failed. This is an informational message only.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"ETHERNET_LACP","4","RF_CLIENT_BUNDLE","LACP HA: Unable initiate checkpoint bundle mode.","LACP is unable to initialize checkpoint bundle mode. This is an informational message only.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"ETHERNET_LACP","4","RF_CLIENT_INIT","LACP HA: Unable to initiate RF client.","LACP is unable to initialize as a RF client. This is an informational message only.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"ETHERNET_MLACP","3","PEER_ICCP_VERSION_INCOMPATIBLE","Peer ICCP version [dec] is incompatible with local ICCP version [dec].","mLACP peer is running with a different version of ICCP. Incompatible ICCP would prevent mLACP from working properly.","Reboot peer with identical IOS version would correct the issue. Compatible ICCP version between different IOS images can still be achieved by doing show lacp multichassis group on the both devices to check if ICCP versions are compatible. If ICCP versions are incompatible, repeat IOS image loading and CLI above until a compatible image is loaded."
"ETHERNET_MLACP","3","SYS_CFG_DUPL_ID","Remote mLACP peer has duplicate mLACP node-id [dec]","A remote mLACP peer is configured with the same mLACP node-id as this device.","Reconfigure the mLACP node-id to be unique between the two devices with the mlacp node-id configuration command. Refer to the mLACP configuration section of the Cisco IOS documentation for more information on configuring mLACP."
"ETHERNET_MLACP","3","SYS_CFG_INVALID_ID","Received invalid mLACP node-id [dec] from peer","A remote mLACP peer is configured with an invalid mLACP node-id.","Reconfigure the peer to send a valid mLACP node-id with the mlacp node-id configuration command. Refer to the mLACP configuration section of the Cisco IOS documentation for more information on configuring mLACP."
"ETHERNET_MLACP","4","CORE_CONNECTED","mLACP has recovered from a core isolation failure. Attempting to recover [dec] LAGs in redundancy group [int]","mLACP has recovered from core isolation and has attempted to recover the LAGs in the redundancy group.","This message may not require any action. However the show lacp multi-chassis group and show lacp multi-chassis port-channel commands may be used to verify the state of the mLACP port-channels. Reference the mLACP section of the IOS documentation for details on core isolation failures and related configuration commands."
"ETHERNET_MLACP","4","CORE_ISOLATION","mLACP Core isolation failure: Attempting to failover [dec] LAGs in redundancy group [int]","mLACP has detected isolation from the core and has attempted to failover.","Use the show redundancy interchassis command to determine which core facing interface has triggered the isolation failure. Correct the failure for the given interface, this will clear the mLACP core isolation failure. Reference the mLACP section of the IOS documentation for more information on core isolation failures and related configuration commands."
"ETHERNET_MLACP","4","ICRM_CLIENT_RECV_BAD_LEN","Received an mLACP TLV with bad length [dec], total message length [dec]","The mLACP TLV length is longer than the total message length.","Issue the show version command on the local and remote devices to get the versions of IOS that are running. Reference the mLACP section of the IOS documentation to verify that mLACP is compatible between the IOS versions on the two devices. If the versions are compatible and the message still appears then please contact your Cisco technical support representative. Provide the representative with the exact message being seen as well as the output of the following commands, show version, show run, show lacp multi-chassis group, and show lacp multi-chassis port-channel."
"ETHERNET_MLACP","4","ICRM_CLIENT_RECV_NO_TYPELEN","Received an mLACP TLV without a type and/or length field ([dec])","mLACP received an improperly formatted TLV from the peer. As a result the local and peer devices may have mismatched state data.","Issue the show version command on the local and remote devices to get the versions of IOS that are running. Reference the mLACP section of the IOS documentation to verify that mLACP is compatible between the IOS versions on the two devices. If the versions are compatible and the message still appears then please contact your Cisco technical support representative and provide the representative with the exact error message being seen as well as the versions of IOS from both devices."
"ETHERNET_MLACP","4","ICRM_CLIENT_RECV_REJ","Received rejected mLACP TLV from peer with message ID [dec]","A remote mLACP peer has rejected an mLACP TLV.","Issue the show version command on the local and remote devices to get the versions of IOS that are running. Reference the mLACP section of the IOS documentation to verify that mLACP is compatible between the IOS versions on the two devices. If the versions are compatible and the message still appears then please contact your Cisco technical support representative and provide the representative with the exact error message being seen as well as the versions of IOS from both devices."
"ETHERNET_MLACP","4","PEER_DISCONNECT","An mLACP peer has disconnected from redundancy group [int], attempting to reconnect","mLACP has detected that a peer device from the specified redundancy group has disconnected. mLACP will attempt to reconnect to the device until successful.","This message is typically caused by a configuration event on the peer router, and so no action may be necessary. However if this message is unexpected then issue the show redundancy interchassis command on both the local and peer mLACP devices to determine which peer member IP has lost communication. Use this information to further debug the network communication issue, and re-enable communication with the peer. Reference the mLACP section of the IOS documentation for more information on peer down failures."
"ETHERNET_MLACP","4","PEER_DOWN","mLACP Peer down failure: Attempting to make [dec] local LAGs active in redundancy group [int]","mLACP has detected a peer down failure and has attempted to make the local port-channels become active.","The peer down failure should be corrected by re-enabling communication with the peer mLACP device. Use the show redundancy interchassis command on both the local and peer mLACP devices to determine which peer member IP has lost communication. Use this information to further debug the network communication issue, and re-enable communication with the peer. Reference the mLACP section of the IOS documentation for more information on peer down failures."
"ETHERNET_MLACP","4","PEER_RECONNECT_FAILED","The attempt to reconnect to the peer in redundancy group [int] has failed","After an mLACP peer device disconnected, an attempt was made to reconnect, however that attempt has failed.","To reinitialize the connection, unconfigure mlacp interchassis group from the port-channel, and then reconfigure it. After doing that, issue show redundancy interchassis to get the peer member IP connection status and the mLACP connection state. If the peer member IP connection status is not CONNECTED then there is a more basic communication issue that needs to be fixed. Otherwise if the peer member IP is CONNECTED but the mLACP state is not CONNECTED, then there could be a software issue. In that case collect the output of show redundancy interchassis, show lacp multi-chassis group, and show lacp multi-chassis port-channel. Then please contact your Cisco technical support representative and provide the collected information."
"ETHERNET_MLACP","4","PEER_UP","mLACP has recovered from a peer down failure in redundancy group [int]","mLACP is now in communication with the peer device, and has recovered from a previous peer down failure.","This message may not require any action. However the show lacp multi-chassis group and show lacp multi-chassis port-channel commands may be used to verify the state of the mLACP port-channels. Reference the mLACP section of the IOS documentation for details on peer down failures and related configuration commands."
"ETHERNET_MLACP","6","PEER_CONNECT","mLACP peer is now connected in redundancy group [int]","This message indicates that the local mLACP device is now connected to a peer device in the specified redundancy group.","No action is required. To view the peer information the command show lacp multi-chassis port-channel or show lacp multi-chassis group may be issued."
"ETHERNET_OAM","2","CRIT_ERR","The Ethernet OAM protocol has encountered the critical error: [chars].","The protocol has encountered a critical error as specified in the message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ETHERNET_OAM","3","LOOPBACK_ERROR","Loopback operation on interface [chars] has encountered an error([chars]).","Because of the specified error, the loopback operation has ended abnormally.","No action is required."
"ETHERNET_OAM","5","EVENTTLV","[chars] is received from the remote client on interface [chars].","An event TLV is received from the remote OAM client, which detected errors in receiving frames from this local interface.","No action is required."
"ETHERNET_OAM","5","LINK_MONITOR","[chars] detected over the last [chars] on interface [chars].","A monitored error has been detected to have crossed the user-specified threshold.","No action is required."
"ETHERNET_OAM","5","LINK_MONITOR_HT_CROSS","High threshold was crossed on Port Channel [chars]'s last operational member port [chars]. Interface [chars] is kept online.","A monitored error has been detected to have crossed the user-specified threshold.","No action is required."
"ETHERNET_OAM","6","ENTER_SESSION","The client on interface [chars] has entered the OAM session.","Ethernet OAM client on the specified interface has detected a remote client and has entered the OAM session.","No action is required."
"ETHERNET_OAM","6","EXIT_SESSION","The client on interface [chars] has left the OAM session.","Ethernet OAM client on the specified interface has experienced some state change.","No action is required."
"ETHERNET_OAM","6","LINK_TIMEOUT","The client on interface [chars] has timed out and exited the OAM session.","The Ethernet OAM client on the specified interface has not received any OAMPDUs in the number of seconds for timeout that were configured by the user. The client has exited the OAM session.","No action is required."
"ETHERNET_OAM","6","LOOPBACK","Interface [chars] has [chars] the [chars] loopback mode.","The specified interface has entered or exited loopback mode because of protocol control or an external event, such as the interface link going down.","No action is required."
"ETHERNET_OAM","6","RFI","The client on interface [chars] has received a remote failure indication from its remote peer(failure reason = [chars])","The remote client indicates a Link Fault, or a Dying Gasp (an unrecoverable local failure), or a Critical Event in the OAMPDU. In the event of Link Fault, the Fnetwork administrator may consider shutting down the link.","In the event of a link fault, consider shutting down the link."
"ETHERNET_OAM","6","RFI_CLEAR","The client on interface %s has received a clear of remote failure indication from its remote peer(failure reason = %s action = %s)","The remote client received a message to clear a link fault, or a dying gasp (an unrecoverable local failure), or a critical event in the operations, administration, and maintenance Protocol Data Unit (OAMPDU). The error-disable state can only be cleared by entering the shutdown command followed by the no shutdown command on the interface.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ETHER_SERVICE","6","EVC_STATUS_CHANGED","status of %s changed to %s","The Ethernet virtual connection (EVC) status has changed.","No action is required."
"ETHER_SERVICE","6","EVC_VLAN_NOT_CONFIGURED","VLANs %s not configured at %s but is in a CEVLAN/EVC map","The specified VLANs are part of the CEVLAN/EVC map for an EVC associated with the specified interface, but the VLANs are not configured on that interface.","Verify the configurations of VLANs on the interface."
"ETSEC","1","INITFAIL","PQ3/FE([dec]), Init failed, CSR[dec]=[hex]","The software failed to initialize/restart an Ethernet/Fast Ethernet interface.","Clear the interface. If the message recurs, call your technical support representative for assistance."
"ETSEC","1","INITFAILP","PQ3/FE([dec]), Init failed at [chars]","The FEC could not allocate a I/O buffer pool.","Clear the interface. If the message recurs, call your technical support representative for assistance."
"ETSEC","1","MEMERR","PQ3/FE([dec]), Memory error, CSR[dec]=[hex]","The interface could not access system resources for a long time. This problem may occur under very heavy loads.","The system should recover. No action is required. If the message recurs, call your technical support representative for assistance."
"ETSEC","1","SHOWFAIL","PQ3/FE([dec]), Memory error at [chars] Recommended Action    Clear the interface. If the message recurs, call your technical support representative for assistance.ETSEC-2Error Message    %ETSEC-2-EXCEPTION: Fatal Error, Interface [chars] not transmitting","The software detected critical error and recovery failed, resulting in system crash.","Collect crashinfo files, syslogs and console dumps."
"ETSEC","2","NOISL","Interface [chars] does not support ISL","The interface cannot be configured as an ISL trunk.","Check the configuration."
"ETSEC","3","CREATE_IBC_FAILED","Creation of etsec ibc idb failed","etsec ibc idb creation has failed","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"ETSEC","3","INIT_IBC_FAILED","Initialization of etsec ibc failed","etsec ibc initialization has failed","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"ETSEC","3","INIT_ICDM_FAILED","Initialization of icdm driver failed","icdm driver initialized failed for etsec ibc","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"ETSEC","3","INIT_MAC_DRIVER_FAILED","Initialization of ethernet mac driver failed","ethernet mac driver initialized failed for etsec ibc","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"ETSEC","3","MASKED_RCV_INTR","etsec_ibc_rcv_interrupt called while masked: [int]","etsec_ibc_rcv_interrupt called while already masked","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"ETSEC","3","NO_BUFFER_POOLS","Initialization of private buffer pools failed","Private buffer pools were not created for etsec ibc.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"ETSEC","3","NO_PARTICLE","no particle available to populate the ethernet dma ring","No particle available to populate the ethernet dma ring.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"ETSEC","3","OVERFLO","PQ3/FE([dec]), Receive overflow","While receiving a frame, the controller chip's local buffer transmitted insufficient data because data could not be transferred to DRAM fast enough to keep pace with its input rate. Normally, such a problem is temporary, depending on transient peak loads within the system.","The system should recover. No action is required."
"ETSEC","3","OWNERR","PQ3/FE([dec]), Buffer ownership error, pak=[hex]","The software detected an error in descriptor ownership.","Try a later version of the software. If the message recurs, call your technical support representative for assistance."
"ETSEC","3","RECOVER_TX","Interface [chars] TX workaround invoked","The software detected the interface was not transmittingpackets. The workaround patch has been invoked.","The system should recover. No action is required."
"ETSEC","3","RESTART","Interface [chars] Restarted Due to [chars] Error","The software detected critical error and etsec driver was restarted to restore EoBC traffic flow.","The system should recover. No action is required."
"ETSEC","3","RX_ADD_BUFFER_FAILED","particle not added to the ethernet dma ring","Particle not added to the Ethernet dma ring.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"ETSEC","3","UNDERFLO","PQ3/FE([dec]), Transmit underflow","While transmitting a frame, the controller chip's local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.","The system should recover. No action is required."
"ETSEC","4","BABBLE","PQ3/FE([dec]), Babble error, CSR[dec]=[hex]","The transmitter has been on the channel longer than the time taken to transmit the largest frame.","The system should recover. No action is required."
"ETSEC","5","COLL","PQ3/FE([dec]), Excessive collisions, TDR=[dec], TRC=[dec].","Ethernet/Fast Ethernet is seeing multiple collisions. This may occur under heavy loads.","The system should recover. No action is required."
"ETSEC","5","EXCESSCOLL","PQ3/FE([dec]), Excessive collision","Ethernet/Fast Ethernet is seeing multiple collisions. This may occur under heavy loads.","The system should recover. No action is required."
"ETSEC","5","FIFO_RECOVER","[chars] ([dec]) detected freeze, last([dec]) new([dec]) tx cntr. tx_pending ([dec]). applying patch","The interface is used for IPC/SCP communication between RP and SP. In a rare situation when fifo tx engine is stuck and requires a toggle there is no data loss when the recovery patch is executed. Patch is applicable to MPC8548 version 2.0 silicons only.","None - software patch will be executed."
"ETSEC","5","LATECOLL","PQ3/FE([dec]), Late collision","Late collisions occurred on the Ethernet/Fast Ethernet interface.","If the interface is Fast Ethernet, verify that both peers are in the same duplex mode. For regular Ethernet, the system should recover. No action is required."
"ETSEC","5","LOSTCARR","PQ3/FE([dec]), Lost carrier. Transceiver problem?","The cable is not connected to the port.","Connect the cable to the port."
"EVENT_TRACE","3","GROUP_ID","Duplicate registration of group-id [dec]","Software subsystem is trying to register a group ID for an event trace that has already been used by another subsystem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EXFREE","2","EXMEMFREE","Free a non allocated ptr [hex] size [dec].","The system is trying to free a memory. Not all of it is marked as allocated.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EXFREE","2","EXMEMINIT","EXMEM [dec]: [chars]","The requested external memory allocator failed to be initialized. The reasons are not clear.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EXFREE","2","EXMEMLOCK","[chars] detected error ptr [hex] size [dec].","The system is attempting to lock or unlock a memory location that was either already locked or unlocked.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EXFREE","2","EXMEMPARAM","Bad parameter ([dec]) when calling to the allocator utility","An illegal parameter was used when a call to the allocator utility was made. This condition may indicate data corruption.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EXFREE","2","EXMEMRESET","EXMEM [dec]: [chars]","The requested external memory allocator failed to be reset. The reasons are not clear.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EXFREE","4","EXMALLOCFAIL","External memory allocation of [int] bytes failed from EXMEM [dec]","The requested memory allocation is not available from the specified memory pool. The current system configuration, network environment, or possibly a software error might have exhausted or fragmented the router's memory.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EXPRESS_SETUP","3","UNABLE_TO_RESET_CONFIG","[chars]","The system is unable to reset the configuration.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EXPRESS_SETUP","6","CONFIG_IS_RESET","[chars]","The configuration is reset and the system will now reboot.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"EXPRESS_SETUP","6","MODE_ENTERED",',"Express setup mode is now active.","No action is required."
"EXPRESS_SETUP","6","MODE_EXITED",',"Express setup mode is no longer active.","No action is required."
"FABRIC","3","DISABLE_FAB","The fabric manager disabled active fabric in slot [dec] due to the error ([dec]) on this channel (FPOE [dec]) connected to slot [dec]","The firmware detected a severe fabric error and reported the error to the fabric manager. The manager has disabled the active fabric.","The Fabric Manager will automatically resynchronize the fabric channel to recover from the error. The problem may occur when the fabric card or the line card does not have good contact with backplane. You should insert the fabric and line cards firmly into the chassis."
"FABRIC","3","EM_RECOVERY_ISSU_NEGO_FAILED","Attempting EM recovery for EM type %d, but ISSU negotiation was unsuccessful/incomplete.","On a switchover, the fabric manager is trying to recover for events that were opened on the peer before the switchover, but not closed. These events are maintained by the event manager (EM). The fabric manager found that ISSU negotiation was either unsuccessful or incomplete. Because the data may not have been synchronized correctly between the active and standby devices, this is an error condition.","No action is required."
"FABRIC","3","ERRORS_DDRSYNC","Line card DDR channels sync error fpoe/slot [dec]/[dec].","A transmit FIFO overrun or underrun in the DDR channels has occurred. The error indicates a clock mismatch. If this condition is persistent, the hardware is faulty.","The system will attempt to resynchronize the DDR channel and the fabric channel."
"FABRIC","3","LOST_SYNC","[chars] endpoint of fpoe:[dec] lost Sync. to [chars] fabric,#[dec] times recovered success, trying to recover now!","The endpoint has lost synchronization with the fabric and is trying to recover.","No action is required."
"FABRIC","4","DISABLE_FAB","Please disable fabric service: active sup [dec] (error [dec])","All supervisor engine fabric channels have errors.","Disable fabric services for the switch. Disable power for external switch fabric modules. Disable fabric service for internal switch fabric modules, but keep the supervisor engines powered on."
"FABRIC","4","LINECARDMODE_CFG_MISMATCH","Service module in the slot [dec] cannot pass traffic to the distributed etherchannel configured.","Because of the hardware limitation of the service module in the slot specified, traffic from these modules cannot pass through the distributed EtherChannel as configured.","Force the service modules switching mode to bus mode by entering the fabric switching-mode force busmode command, or change the channel configuration so that the affected modules do not need to pass traffic through the EtherChannel."
"FABRIC","4","SERVICEMOD_CHANGE_BUSMODE","The switching mode of service module in slot [dec] can be changed to its default as the distributed etherchannel config is removed.","The switching mode of the service modules can be reverted to the default by entering the no fabric switching-mode force busmode command.","Restore the default by entering the no fabric switching-mode force busmode command."
"FABRIC","4","SUP_SWITCHOVER","Supervisor switchover from slot [dec] (error [dec])","The active supervisor engine fabric channel has errors.","A switchover to the redundant supervisor engine occurs automatically."
"FABRIC","5","CANNOT_CLEAR_BLOCK","The fabric in slot [dec] cannot support clear-block feature.","A user enabled the clear-block mechanism, but the fabric in the specified slot cannot support the feature.","No action is required."
"FABRIC","5","CANNOT_SUPPORT_FP_INVERSION","The module you have installed in slot [dec] is running an older revision of firmware/software which may cause inconsistent system behavior. Please refer to the release notes for a minimum recommended software release for mentioned module.","The specified module can not support FP bit inversion with the current software release. The fabric clear block will disregard the COS setting for this module.","No action is required."
"FABRIC","5","CLEAR_BLOCK","Clear block option is [chars] for the fabric in slot [dec].","The fabric manager has changed the status of the clear-block mechanism for all fabric channels. The status (on or off) is indicated in the message.","No action is required."
"FABRIC","5","ERRORS_BUFFER","In fabric slot [dec], memory buffer for fpoe/slot [dec]/[dec] is full.","Either the buffer size is less than the packet size or the uplink buffer cannot respond to flow control from the fabric.","Examine the fabric memory configuration."
"FABRIC","5","ERRORS_TIMEOUT","Time out for input from fpoe/slot [dec]/[dec] to slot [dec].","A timeout in the fabric input buffer occurred because of a problem from the destination slot. The transient error is observed when the module is removed. If the error is persistent, the module local bus might be locked.","Reset the module in the destination slot if the error is persistent."
"FABRIC","5","FABRIC_FAILOVER","The fabric in slot [dec] has failed over due to fabric errors on slot [dec]. Fabric in slot [dec] is now the current active fabric.","The Switch Fabric Module in the specified slot failed over and active supervisor switch to former standby supervisor.Error Message    No action is required.%FABRIC-5-LINECARDMODE_BUS_FORCED: The switching mode of module in slot [dec] is forced to bus-mode. Explanation    The fabric switching-mode force busmode command has been applied.","No action is required."
"FABRIC","5","NOT_ALLOWED","Power not allowed to module [dec] : [chars] .","Certain types of linecards is not given power for some reaon. Detailed reason is given in the message body.","No action is required."
"FABRIC","6","TIMEOUT_ERR","Fabric in slot [dec] reported timeout error for channel [dec] (Module [dec], fabric connection [dec])","Firmware code on the fabric detected that the input or output buffer was not moving. To recover from this condition, the system will automatically resynchronize the fabric channel.","The system automatically recovers from this condition by doing a fabric channel resynchronization. If the system experiences this condition persistently, directly connect to the console of the fabric and the module to determine if any errors are being reported by the firmware. Also, reseat and reset the module."
"FABRIC_INTF_ASIC","4","DEV_CONFIG_FAIL","The Switch Fabric interface ASIC configuration failed","The switch fabric interface ASIC could not be configured.","If the switch fabric is inactive (down), this message can be expected. If the module comes online and traffic processing resumes, ignore this message. Otherwise, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. On the Route Processor, capture the show logging and show version commands."
"FABRIC_INTF_ASIC","4","FABRICCRCERRS","[dec] Fabric CRC error events in 100ms period","The switch fabric interface encountered more CRC error events than the supervisor engine CRC error threshold allows.","The line card has notified the supervisor engine and the error has been logged. No action is required from the user."
"FABRIC_INTF_ASIC","5","CHAN_LINK_SPEED_OOB","Array access bounds violated, channel_num=[int], link_num=[int], speed=[int]","Cisco IOS code has attempted to access an internal array with an invalid index for SSA channel number or link number or speed.","No action is required if there is no system impact. If traffic stops or linecard fails, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FABRIC_INTF_ASIC","5","DEV_INIT_FAILURE","The Switch Fabric interface ASIC initialization failed","The switch fabric interface ASIC was not successfully initialized. As a result, this device is not operational and has been disabled.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FABRIC_INTF_ASIC","5","FABRICDOWN_CRCERRS","[dec] Fabric CRC error events in 100ms period","The switch fabric interface encountered more CRC errors than the maximum configured threshold. However, the reason for this error is that the switch fabric is inactive (down). The line card has notified the supervisor engine of this condition and the error has been logged.","This message indicates normal system operation. No action is required."
"FABRIC_INTF_ASIC","5","FABRICDOWN_SYNCERRS","[dec] Fabric sync error events in 100ms period","The switch fabric interface encountered more synchronization errors than the maximum configured threshold. However, the reason for this error is that the switch fabric is inactive (down).","This message indicates normal system operation. No action is required."
"FABRIC_INTF_ASIC","5","FABRICSYNC_DONE","Fabric sync on [chars] channel done.","The switch fabric interface ASIC was resynchronized.","No action is required."
"FABRIC_INTF_ASIC","5","FABRICSYNC_REQ","Fabric sync requested on [chars] channel ([dec])","The line card has requested that the supervisor engine resynchronize its fabric interface ASIC.","No action is required."
"FABRIC_INTF_ASIC","5","NOFABRICPROCESS","The Switch Fabric interface fabric process could not be created","The switch fabric interface does not have a link process running: the system failed to create this process. This module will not support the fabric interface.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FABRIC_INTF_ASIC","5","NULL_DEV_OBJECT","The Switch Fabric interface device object pointer is set to NULL","The memory location of the switch fabric interface device object is invalid. The switch fabric interface ASIC operation is disabled and the device interrupt is now masked.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FABRIC_INTF_ASIC","5","SMB_ACCESSERROR","The Module Switch Fabric interface ASIC cannot be accessed","The switch fabric interface ASIC access (read or write) failed. The serial bus that connected to the switch fabric interface ASIC on this module is not functioning correctly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FABRIC-SP","5","CLEAR_BLOCK","Clear block option is [chars] for the fabric in slot [dec].","The fabric manager has changed the status of the clear-block mechanism for all fabric channels. The status (on or off) is indicated in the message.","No action is required."
"FABRIC-SP","5","FABRIC_MODULE_ACTIVE","The Switch Fabric Module in slot [dec] became active","The Switch Fabric Module in the specified slot is active as the switching fabric.","No action is required."
"FIB","2","FIBFEATSESINIT","Error initializing CEF repop feature session queue","Initialization of a CEF feature session queue could not be accomplished because of a low-memory condition.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"FIB","2","FIBRETRY_EXCEEDED","CEF table download to slot [dec] not performed as IPC port did not come up","The FIB could not be fully downloaded. As a result of this condition, hardware switching might not be functional on the module.","Reset the module to overcome this condition."
"FIB","2","HW_IF_INDEX_ILLEGAL","Attempt to create CEF interface for [chars] with illegal index: [dec]","An internal software error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FIB","2","IF_NUMBER_ILLEGAL","Attempt to create CEF interface for [chars] with illegal if_number: [dec]","An internal software error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FIB","3","FIBSBNOFN","Missing [chars] subblock [chars] function for [chars]","Functions for distributing this subblock are missing from the image.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FIB","3","MAC_ACCT","[chars]: [chars]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FIB","3","PREC_ACCT","[chars]: [chars]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FIB","3","FIB_STATS_ERROR","Internal Error - type [dec], slot [dec], total_len [dec], msg_len [dec], seg_len [dec]","An internal software error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FIB","4","FIBNULLHWIDB","Missing hwidb for fibhwidb [chars] (ifindex [dec])","An internal software error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FIB","4","FIBNULLIDB","Missing idb for fibidb [chars] (if_number [dec]).","An internal software error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FIB","4","FIBRETRY_WARNING","IPC port for slot [dec] to become available for CEF table download (retried [dec] times)","The FIB table failed to download for the number of times specified in the message.","If the FIB table is successfully downloaded in a subsequent retry, no action is required. If the operation is not successful, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FIB","6","FIBLCTUNDELSEQ","Update received on a linecard for a deleted tunnel([chars]) - ignored.","An update was received on a line card for a tunnel that has already been deleted. The update was ignored.","No action is required."
"FILESYS","3","RUNNING_SYNC_FAILED","The active is unable to synchronize the running configuration to standby, so standby will be reloaded","The active supervisor engine cannot access its running configuration to synchronize the configuration to the standby supervisor engine. This can be caused by temporary resource issues such as high CPU.","No action is required. This message is for informational purposes only."
"FILESYS","4","CLPDINT","Management interrupts are [chars] for pcmcia device in socket [dec]. [chars]","A faulty PCMCIA flash device might be generating spurious insert or remove interrupts continuously. The PCMCIA controller's interrupt generation will be disabled temporarily, and will be reenabled after a few seconds. If an alternate PCMCIA device is inserted while the interrupts are disabled, the alternate device may not be readable. In this case, you must remove and reinsert the PCMCIA device.","Replace the PCMCIA flash device."
"FILESYS","5","CFLASH","Compact flash card [chars] [chars]","A file system's status has changed.","Follow any instructions provided with the message."
"FM","2","ACL_MERGE_EXCEPTION","ACL merge internal error due to features configured on interface [chars] in [chars] direction, traffic may be switched in software","The configured features for this interface caused the merge to abort because of an internal error. The traffic on this interface and the interfaces sharing TCAM label with this interface will be sent to the software.","Redefine and reapply or unconfigure one or more features on the interface."
"FM","2","ACL_MERGE_NUM_ACES","ACL merge aborted due to number of ACEs threshold for features on interface [chars] in [chars] direction, traffic may be switched in software","The configured features for this interface may have caused the merge to abort because of hitting the 64000 ACE merge threshold. The traffic on this interface and the interfaces sharing the TCAM label with this interface will be sent to the software.","Redefine and reapply or unconfigure one or more features on the interface."
"FM","2","FIE_EXCEPTION","Feature interaction internal error due to features configured on interface [chars] in [chars] direction, traffic may be switched in software","The configured features for this interface caused an internal error in the feature interaction. The traffic on this interface and the interfaces sharing the TCAM label with this interface will be sent to the software.","Redefine and reapply or unconfigure one or more features on the interface."
"FM","2","FLOWMASK_CONFLICT","Features configured on interface [chars] have conflicting flowmask requirements, traffic may be switched in software","The configured features for this interface have a flow mask conflict. The traffic on this interface and the interfaces sharing the TCAM label with this interface may not comply with the features under this condition. The traffic on these interfaces will be sent to the software.","Redefine and reapply or unconfigure one or more features to avoid the conflict."
"FM","2","TCAM_ERROR","TCAM programming error %d","A software error caused a failure in programming ACLs into the TCAM.","Choose the Order Dependent Merge (ODM) algorithm for merging the ACL. Shut down the VLAN interface and reenable the interface after ten minutes. If the error message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FM","2","TCAM_MEMORY","ACL merge abandoned when merging Interface [chars] [chars] ACLs due to insufficient memory. Interface traffic handled in Software.","The capacity of the hardware TCAM has been exceeded and the packets will be now process-switched. The first [chars] value indicates the VLAN interface for which the ACL merge fails, and the second [chars] indicates whether the ACL is ingress or egress.","Choose the Order Dependent Merge (ODM) algorithm for merging the ACL. Shut down the VLAN interface and reenable the interface after ten minutes. If the error message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FM","2","TCP_FLAG_HW_EXCEPTION","No VLOUs available for TCP FLAGs for interface [chars] in [chars] direction: all features on the interface for the specified direction will be NOT effective","No VLOUs are available for TCP flags. This condition cannot be handled in the software for all the features configured on the interface. A message is printed on the console to notify the user of this error condition. Because there are no features that the software can handle, the system will program an entry to permit all traffic.","The hardware TCAM can handle up to 9 logical operations per interface and up to 64 logical operations in total. To recover from this error, recompute the ACLs for the features that cannot be handled in the software (for example, VACLs) to move entries using TCP flags before others entries are moved and to minimize the usage of TCP flags."
"FM","2","TCP_FLAG_SW_EXCEPTION","No VLOUs available for TCP FLAGs on interface [chars] in [chars] direction: traffic will be software switched, features which are NOT processable in software will be NOT effective","No VLOUs are available for TCP flags. This condition cannot be handled in the software for some features configured on the interface. A message is printed on the console to notify the user of this error condition. Because there are some features that can be handled in the software (for example, VACLs and RACLs), an exception entry and traffic on this interface will be sent to the software.","The hardware TCAM can handle up to 9 logical operations per interface and up to 64 logical operations in total. To recover from this error, recompute the ACLs for the features that cannot be handled in the software (for example, VACLs) to move entries using TCP flags before others entries are moved and to minimize the usage of TCP flags."
"FM","3","LABELERROR","Incorrect label to [chars] vlan label attribute copy callback srclabel [dec], dstlabel [dec]","The Feature Manager attribute copy callback was called with an incorrect source or destination label.","Enter the show running-config command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FM","3","NOTEMPTY","Illegal copy of attribute to non empty [chars] vlan label [dec]","The Feature Manager attribute copy callback was called with a destination label already being used by a VLAN or routed port.","Enter the show running-config command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FM","3","UNKNOWNACTION","Unknown VMR access group action [hex]","An internal software error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FM","4","EXCESSSECONDARY","More than [dec] secondary IP addresses configured on interface [chars]","When secondary IP addresses are configured on an interface, the hardware is usually programmed so that the ICMP redirect functionality on the CPU is not notified of packets sent between two subnets configured on the same interface. If many secondary IP addresses are configured on the same interface it becomes impractical to program the hardware in this manner. This message is logged, and the CPU will be notified of every packet sent between two subnets on this interface. No ICMP redirects will be sent in error, but the CPU usage may increase because of the additional notifications.","Enter the no ip redirects command on the interface to reduce the CPU load on the system."
"FM","4","MPLS_RSVD_VLAN_ERROR","Failed attempt to remove the default feature from MPLS reserved vlan [chars]","MPLS reserved vlan's have a default 'permit ip any any' ACL configured. In some corner cases an event is generated to unconfigure this default feature. Such instances should be blocked.","No functional impact. Contact TAC with the traceback and also with the configuration steps that lead to the error message."
"FM","4","FLOWMASK_REDUCED","Features configured on interface [chars] have conflicting flowmask requirements, some features may work in software","The configured features for this interface have a flow mask conflict. The traffic on this interface and the interfaces sharing the TCAM label with this interface will be sent to the software.","Redefine and reapply or unconfigure one or more features to avoid the conflict."
"FM","4","IPSG_VACL","VACL Capture & IPSG conflict on i/f [chars]","Because VACL capture and IPSG is not supported on the same VLAN port, VACL capture will be inactive. To activate VACL capture, reconfigure the feature after removing IPSG.","Remove either IPSG or VACL capture on this interface."
"FM","4","L2_DYN_TCAM_EXCEPTION","Failed to install Dynamic TCAM entry to filter Layer 2 traffic, error status: [dec], host IP address: [IP_address], interface: [chars]","There is an error in installing the per-user policies in the Dynamic TCAM region to filter Layer 2 traffic. The TCAM might be full. As a result, host ingress traffic will be subjected to the default interface ACL.","Attempt to free up TCAM resources."
"FM","4","L2EOU_INSP","INSPECION & L2EOU conflict on i/f [chars]","The inspection feature and the Layer 2 EAP over UDP (L2EOU) feature are not supported on the same VLAN. The inspection feature will be inactive. To activate the inspection feature, reconfigure it after removing the L2EOU feature.","Remove either the Layer 2 EAP over UDP (L2EOU) feature or the inspection feature from the interface."
"FM","4","L2EOU_VACL","VACL Capture & L2EOU conflict on i/f [chars]","Because VACL capture and the Layer 2 EAP over UDP (EOU) feature are not supported on the same VLAN port, VACL capture will be inactive. To activate VACL capture, reconfigure the feature after removing the L2EOU feature.","Remove either the Layer 2 EAP over UDP (EOU) feature or VACL capture on this interface."
"FM","4","TCAM_ADJ","Hardware ACL adjacency capacity exceeded","The hardware does not have the capacity to handle all of the configured adjacencies.","The configured policies have too many adjacencies to fit in the hardware. Use the mls tcam priority command to prioritize interfaces for hardware switching. Reduce the number of adjacencies in the policies."
"FM","4","TCAM_DYN_ENTRY_EXCEPTION","Failed to install Dynamic TCAM entry in TCAM for Interface:[chars]","Dynamic installation of an ACE failed because of TCAM resource exhaustion. Layer 3 traffic will be handled by the software.","Attempt to free up TCAM resources."
"FM","4","TCAM_MASK","Hardware TCAM MASK entry capacity exceeded","The hardware TCAM has exhausted its available storage and does not have the capacity to store all configured ACLs.","If the ACL merge algorithm is currently binary decision diagrams (BDD), space could be freed by changing the merge algorithm to order dependent merge (ODM). Enter the show fm summary command to determine the current merge algorithm. Enter the mls aclmerge algorithm odm command to change the merge algorithm from BDD to ODM. Enter the mls tcam priority command to prioritize interfaces for hardware switching. Attempt to share the same ACLs across multiple interfaces in order to reduce TCAM resource contention. If server load balancing is configured, enter the mls ip slb search wildcard rp command to reduce the amount of TCAM space used by server load balancing. After you enter the command, server load balancing will increase its utilization of the route processor."
"FMCORE","2","ACL_FAILURE","Interface [chars] traffic will not comply with ACLs in [chars] direction(s)","ACLs will not be applied on traffic for the specified interface because of a TCAM resource contention.","The configured ACLs are too large for all of them to fit in the hardware TCAM. Use the mls tcam priority command to prioritize interfaces for hardware switching. Try to share the same ACLs across multiple interfaces to reduce TCAM resource contention."
"FMCORE","4","RACL_REDUCED","Interface [chars] routed traffic will be software switched in [chars] direction","TCAM resource contention prevents ACLs from being applied in the TCAM for this interface. The traffic on this interface will be sent to software so that the ACLs can be applied.","The configured ACLs are too large to all fit in the hardware TCAM. Enter the mls tcam priority command to prioritize the interfaces for hardware switching. Try to share the same ACLs across multiple interfaces to reduce TCAM resource contention."
"FMCORE","2","VACL_FAILURE","Interface [chars] traffic will not comply with VACLs in [chars] direction(s)","VACLs will not be applied on traffic for this interface because of a TCAM resource contention.","The configured ACLs are too large for all of them to fit in the hardware TCAM. Use the mls tcam priority command to prioritize interfaces for hardware switching. Try to share the same ACLs across multiple interfaces to reduce TCAM resource contention."
"FMCORE","4","RACL_REDUCED","Interface [chars] routed traffic will be software switched in [chars] direction","A TCAM resource contention prevents ACLs from being applied in the TCAM for the specified interface. The traffic on the interface will be sent to software so that the ACLs can be applied.","The configured ACLs are too large for all of them to fit in the hardware TCAM. Use the mls tcam priority command to prioritize interfaces for hardware switching. Try to share the same ACLs across multiple interfaces to reduce TCAM resource contention."
"FMCORE","6","RACL_ENABLED","Interface [chars] routed traffic is hardware switched in [chars] direction","Earlier TCAM resource contention may have prevented ACLs from being applied in the TCAM for this interface. It has been enabled and traffic on this interface is hardware switched.","No need to take an action for this as it is an informational message not an error message."
"FM_EARL6","4","RACL_REDUCED_MCAST_RATELIM_WARN","Enabling acl [chars] rate-limiter will cause Multicast traffic to be dropped in hardware on interface [chars] in [chars] direction","A TCAM resource contention prevents routed ACLs from being programmed in the TCAM for the specified interface in the specified direction. All Layer 3 traffic will be sent to CPU to have RACLs enforced in software. Due to a lack of resources, multicast special VMRs cannot be programmed. In this condition, rate limiting for traffic bridged to the CPU by the ACL is incompatible with the status of the multicast interface and will cause multicast traffic to be dropped in the hardware.","Do not enter the mls unicast acl {input | output} command."
"FM_EARL6","4","VACL_PVLAN","Vacl config is NOT supported on secondary Vlan: [chars] and will be removed","Current implementation of the FM does not support the configuration of VACLs on secondary VLANs. The VACL configuration is removed from the VLAN interface once it becomes a secondary private VLAN. Both the hardware and the software will be updated accordingly.","Make the VLAN a primary VLAN or a regular (nonprivate) VLAN. Reapply the VLAN filter."
"FM_EARL7","2","IPV6_PORT_QOS_MCAST_FLOWMASK_CONFLICT","QoS configuration on port [chars] conflicts for flowmask with IPv6 multicast forwarding on SVI interface [chars]","The port-based QoS microflow policing configuration for this interface has a flow mask conflict with IPv6 multicast forwarding. The traffic on the SVI interface will be sent to the software under this condition.","Unconfigure the latest configuration change, modify the conflicting QoS configuration, and reapply."
"FM_EARL7","2","IPV6_QOS_MCAST_FLOWMASK_CONFLICT","QoS configuration on interface [chars] conflicts for flowmask with IPv6 multicast forwarding, traffic may be switched in software","The QoS microflow policing configuration for this interface has a flow mask conflict with IPv6 multicast forwarding. The traffic on this interface will be sent to the software under this condition.","Unconfigure the latest configuration change, modify the conflicting QoS configuration, and reapply."
"FM_EARL7","2","SWITCH_PORT_QOS_FLOWMASK_CONFLICT","QoS configuration on switch port [chars] conflicts for flowmask with feature configuration on SVI interface [chars]","The QoS configuration on the specified port has a conflict with a feature configuration on an SVI interface. QoS or other features might not function correctly under these circumstances.","Unconfigure the latest configuration change, modify the conflicting configuration, and reapply the features."
"FM_EARL7","4","FEAT_CONFLICT_ON_IDB","IP ADMISSSION feature conflicts with other features on interface [chars], feature will work in software","The IP admission feature conflicts with other features on this interface.","Unconfigure any conflicting features and reapply the IP admission feature."
"FM_EARL7","4","FEAT_FLOWMASK_REQ_CONFLICT","Feature [chars] requested flowmask [chars] conflicts with other features on interface [chars], flowmask request Unsuccessful for the feature","The flow mask requested by the specified feature conflicts with other features. The requested flow mask cannot be programmed for the feature.","Redefine and reapply the feature, or unconfigure one or more features and reapply the specified feature to avoid the conflict."
"FM_EARL7","4","FEAT_FLOWMASK_REQ_CONFLICT_ON_SP","Flowmask requested on interface [chars] conflicts with other features on interface for Protocol [chars], flowmask request Unsuccessful for the feature","The flow mask requested by the feature conflicts with other features. The requested flow mask cannot be programmed for the feature.","Redefine and reapply the feature, or reconfigure one or more features and reapply the feature to avoid the conflict."
"FM_EARL7","4","FLOW_FEAT_FLOWMASK_REQ_FAIL","Flowmask request for the flow based feature [chars] for protocol [chars] is unsuccessful, hardware acceleration may be disabled for the feature","The flow mask request for the flow-based feature is unsuccessful. This condition might occur because of a TCAM resource exception, a flow mask registers resource exception, or an unresolvable flow mask conflict with other NetFlow-based features. The NetFlow shortcut installation and hardware acceleration for the feature might be disabled under this condition, and the feature might be applied in the software.","Determine the netflow shortcut installation enable/disable status for the feature by entering the show fm fie flowmask command. If the NetFlow shortcut installation and hardware acceleration is disabled for the feature, reconfigure or unconfigure some of the other features to remove the TCAM resource exception or the flow mask conflict/flow mask resource exception condition. Reapply the feature for the flow mask request to succeed, and reenable the NetFlow shortcut installation for the feature."
"FM_EARL7","4","FEAT_QOS_FLOWMASK_CONFLICT","Features configured on interface [chars] conflict for flowmask with QoS configuration on switch port [chars], traffic may be switched in software","The configured features for the specified interface have flow mask conflicts with the QoS configuration on the switch port. The traffic on this interface will be sent to software.","Undo the latest configuration change, modify the conflicting QoS configuration on the switch port, and reapply the features."
"FM_EARL7","4","FLOW_FEAT_FLOWMASK_REQ_FAIL","Flowmask request for the flow based feature [chars] for protocol [chars] is unsuccessful, hardware acceleration may be disabled for the feature","The flow mask request for the flow-based feature is unsuccessful. This may happen due to TCAM resource exception or flow mask registers resource exception or due to unresolvable flow mask conflict with other NetFlow-based features. NetFlow shortcut installation and hardware acceleration for the feature may be disabled under this condition and the feature may be applied in software.","Check the NetFlow shortcut installation enable/disable status for the feature by entering the show fm fie flowmask command. If NetFlow shortcut installation/hardware acceleration is disabled for the feature, reconfigure or unconfigure some of the other features to remove the TCAM resource exception or the flow mask conflict/flow mask resource exception condition. Reapply the feature for the flow mask request to succeed and reenable the NetFlow shortcut installation for the feature."
"FM_EARL7","4","MLS_FLOWMASK_CONFLICT","mls flowmask may not be honored on interface [chars] due to flowmask conflict","The configured MLS flow mask conflicts with other features or with the QoS configuration. The traffic on the specified interface will be sent to the software. NDE might not function correctly for the specified interface under this condition.","Remove the conflicting configuration, and reconfigure the MLS flow mask."
"FM_EARL7","4","MLS_FLOWMASK_NO_TCAM_RESOURCES","mls flowmask may not be honored on interface [chars] due to TCAM resource shortage","The requirements for the configured features exceed the TCAM resources. The flow mask may not be programmed in the hardware. Under this condition, the traffic on the specified interface is sent to the software. NDE may not function correctly for this interface.","Redefine and reapply some of the features, or unconfigure one or more features."
"FM_EARL7","4","MLS_IPV6_FORCED_COMPRESS_MODE","Use IPv6 mask values of 88 or lower in forced compress mode for consistent processing of incompressible IPv6 addresses in both hardware and software.","IPv6 compress mode is a hardware feature. If compress mode is force-enabled and IPv6 ACLs are built with mask values 89 or greater, inconsistent behavior in IPv6 ACL processing could result with incompressible addresses. Using IPv6 mask values of 88 and lower while forcing compress mode ensures proper hardware processing of IPv6 ACL entries.","Use IPv6 mask values of 88 or lower in forced compress mode for consistent processing of incompressible IPv6 addresses in both hardware and software."
"FM_EARL7","4","NO_FLOWMASK_REGISTERS","Feature configuration on interface [chars] could not allocate required flowmask registers, traffic may be switched in software","The flow mask requirements for configured features on the specified interface cannot be met because there are no available flow mask registers. The traffic on this interface will be sent to software.","Remove one or more NetFlow-based features or QoS microflow policing from the configuration, and reapply the features."
"FM_EARL7","4","RACL_REDUCED_MCAST_RATELIM_WARN","Enabling acl [chars] rate-limiter will cause Multicast traffic to be dropped in hardware on interface [chars] in [chars] direction","A TCAM resource contention prevents routed ACLs from being programmed in TCAM for the specified interface in the specified direction. All Layer 3 traffic will be sent to CPU to have RACLs enforced in software. Due to a lack of resources, multicast special VMRs cannot be programmed. In this condition, rate limiting for traffic bridged to CPU by the ACL is incompatible with the status of the multicast interface and will cause multicast traffic to be dropped in hardware.","Do not enter the mls unicast acl {input | output} command."
"FM_EARL7","4","VACL_PVLAN","Vacl config is NOT supported on secondary Vlan: [chars] and will be removed","The current implementation of the Feature Manager does not support the configuration of VACLs on secondary VLANs. The VACL configuration is removed from the VLAN interface once it becomes a secondary private VLAN. Both the hardware and the software will then be updated accordingly.","Change the VLAN to be a primary VLAN or a regular (nonprivate) VLAN and reapply the VLAN filter."
"FPD_MGMT","2","CREATE_FAIL","Couldn't create [chars].","The system does not have enough free main memory to create the specified resource.","Make sure that the system main memory size meets the minimum requirement that is specified in the Cisco IOS software release note. If the system meets the minimum requirement for this Cisco IOS software release, make sure that the amount of free main memory in the system also meets the minimum memory required to use this software feature. Enter the show memory command to find out this information and add more main memory if it is necessary. If the system meets all the memory requirements, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","BNDL_CARD_TYPE_MISMATCH","The [chars] file does not contain the card type ([hex]) in the image bundle to indicate the support of the target card. Please make sure that this is a valid FPD image [chars] file for card in [chars].","The image bundle in the specified file does not contain a correct card type value for the target card.","Ensure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the correct one from the Cisco Software Center website. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show hw-module subslot fpd, the show upgrade fpd table, and the show upgrade fpd file fpd-pkg-url commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","BNDL_CRC_CHECK_FAIL","The [chars] file contains a corrupted image bundle - CRC mismatch: current value [hex], expected value [hex]. Please make sure that this is a valid FPD image [chars] file for card in [chars].","The file failed the CRC checking process. This failure indicates a corrupt FPD image bundle or package file.","Try to download again the required package from the Cisco Software Center website as the specified one might be corrupted. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the Enter the show hw-module subslot fpd, the show upgrade fpd table, and the show upgrade fpd file fpd-pkg-url commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","BNDL_NAME_PREFIX_MISMATCH","The [chars] file contains a bundle name prefix ([chars]) that does not match with the expected value of '[chars]' for the image bundle. Please make sure that this is a valid FPD image [chars] file for card in [chars].","The content of the selected FPD image bundle does not match its filename.","Ensure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the correct one from the Cisco Software Center website. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show hw-module subslot fpd, the show upgrade fpd table, and the show upgrade fpd file fpd-pkg-url commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","BNDL_WRONG_HDR_LEN","The [chars] file contains wrong header length for the image bundle: [int] bytes (expected [int] bytes). Please make sure that this is a valid FPD image [chars] file for card in [chars].","The specified file might not be a valid FPD image bundle or package file for the target card.","Ensure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the correct one from the Cisco Software Center website. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show hw-module subslot fpd, the show upgrade fpd table, and the show upgrade fpd file fpd-pkg-url commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","BNDL_WRONG_MAGIC_NUM","The [chars] file contains a wrong magic number for the image bundle: [hex] (expected [hex]). Please make sure that this is a valid FPD image [chars] file for card in [chars].","The specified file might not be a valid FPD image bundle or package file for the target card or the file could be corrupted.","Ensure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the correct one from the Cisco Software Center website. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show hw-module subslot fpd, the show upgrade fpd table, and the show upgrade fpd file fpd-pkg-url commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","BNDL_WRONG_SIZE","The [chars] file contains incorrect image bundle size: [int] bytes (expected [int] bytes). Please make sure that this is a valid FPD image [chars] file for card in [chars].","The specified file might not be a valid FPD image bundle or package file for the target card.","Ensure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the correct one from the Cisco Software Center website. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show hw-module subslot fpd, the show upgrade fpd table, and the show upgrade fpd file fpd-pkg-url commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","BUNDLE_EXTRACT_ERROR","Cannot extract the [chars] bundle from [chars] - [chars]","There has been a bundle file-extraction error. The cause of the failure is specified in the message. The specified file might not be a valid FPD image package file.","Ensure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the correct one from the Cisco Software Center website. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show hw-module subslot fpd, the show upgrade fpd table, and the show upgrade fpd file fpd-pkg-url commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","CLOSE_FAILED","Failed to close [chars] file.","There is a problem in the internal software coding. This message should not be seen under normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","DUPLICATE_UPGRADE_RESULT","Upgrade result already received for the FPD image upgrade of FPD ID [int] for [chars] card in [chars].","There is a problem in the internal software coding. This message should not be seen under normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","FPD_UPGRADE_FAILED","[chars] (FPD ID=[int]) image upgrade for [chars] card in [chars] has FAILED.","The FPD image upgrade process has failed for the specified device.","Retry the upgrade operation again. If the affected card remains disabled by the system after attempts to retry the upgrade, copy the message exactly as it appears on the console or in the system log. Enter the show hw-module subslot fpd command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","IMG_CRC_CHECK_FAILED","The FPD image for [chars] (FPD ID [int]) in [chars] file is corrupted - CRC mismatch: current value [hex], expected value [hex]. Please make sure that this is a valid FPD image bundle or package file for card in [chars].","The image failed the CRC checking process, this indicates a corrupt FPD image bundle or package file.","Ensure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the correct one from the Cisco Software Center website. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show hw-module subslot fpd, the show upgrade fpd table, and the show upgrade fpd file fpd-pkg-url commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","IMG_DATA_UNCOMPRESS_ERROR","Could not uncompress [chars] FPD image for [chars] in [chars].","An error has been detected during the uncompress operation of the compressed FPD image data.","Ensure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the correct one from the Cisco Software Center website. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show hw-module subslot fpd, the show upgrade fpd table, and the show upgrade fpd file fpd-pkg-url commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","IMG_VER_NOT_FOUND","FPD image version information is not available for [chars] card in [chars]. All the FPD images will be upgraded to recover from this error.","The FPD image version information for the specified card is not available because the system was not able to extract this information for all the FPDs in the card. This could be the result of a corrupted FPD image from a power failure.","If the automatic upgrade feature is not enabled, then the affected card will be disabled. If this happens, follow the recommended action described for the FPD_MGMT-5-CARD_DISABLED message."
"FPD_MGMT","3","INCOMP_BNDL_VER","The selected [chars] file contain an image bundle that has a version number that is incompatible for this IOS release - [chars]. Selected version = [int].[int], minimum compatible version = [int].[int]. Please make sure that this is a valid FPD image [chars] file for card in [chars].","The version of the selected FPD image bundle does not contain a valid version number that is compatible for the Cisco IOS release. The major version number should be the same and the minor version number should be at least equal to the minimal required version.","Ensure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the correct one from the Cisco Software Center website. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show hw-module subslot fpd, the show upgrade fpd table, and the show upgrade fpd file fpd-pkg-url commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","INCOMP_IMG_VER","Incompatible [chars] (FPD ID=[int]) image version detected for [chars] card in [chars]. Detected version = [int].[int], minimum required version = [int].[int]. Current HW version = [int].[int].","An incompatible FPD image version has been detected. The FPD image must be upgraded either automatically or manually to make the card operational. If the automatic upgrade feature is not enabled, or if the system cannot find the necessary FPD image package file, the card will be disabled.","If the automatic upgrade feature is not enabled, then the affected card will be disabled. If this happens, follow the recommended action described for the FPD_MGMT-5-CARD_DISABLED message."
"FPD_MGMT","3","INVALID_IMAGE_SIZE","The [chars] FPD image from [chars] file does not have a valid image size: expected size = [dec] bytes, actual size = [dec] bytes.","The size of the specified FPD image does not have the expected size. The FPD image bundle or package might not be a valid file.","Ensure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the correct one from the Cisco Software Center website. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show hw-module subslot fpd, the show upgrade fpd table, and the show upgrade fpd file fpd-pkg-url commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","INVALID_IMG_VER","Invalid [chars] (FPD ID=[int]) image version detected for [chars] card in [chars].","The specified field programmable device contains an invalid version for the FPD image, because the system was not able to extract this information from the specified card. A failed upgrade attempt might have corrupted the FPD image identification on the device.","If the automatic upgrade feature is not enabled, the affected card will be disabled. If this happens, follow the recommended action described for the FPD_MGMT-5-CARD_DISABLED message."
"FPD_MGMT","3","INVALID_PKG_FILE","The indicated file ([chars]) is not a valid FPD image package file - [chars]","The file format does not appear to be a valid FPD image package.","Ensure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the correct one from the Cisco Software Center website. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show hw-module subslot fpd, the show upgrade fpd table, and the show upgrade fpd file fpd-pkg-url commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","INVALID_PKG_FILE_SIZE","The indicated file ([chars]) does not have a valid FPD image package file size, minimum size = [dec] bytes.","The file size of the specified FPD image package does not meet the required minimum size. The file is too small to be a valid FPD image package file.","Ensure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the correct one from the Cisco Software Center website. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show hw-module subslot fpd, the show upgrade fpd table, and the show upgrade fpd file fpd-pkg-url commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","INVALID_UPGRADE_RESULT","Invalid upgrade result '[int]' received for the FPD image upgrade of [chars] (FPD ID=[int]) for [chars] card in [chars].","There is a problem in the internal software coding. This message should not be seen under normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","IPC_FAILED","Failed to send IPC message to [chars] in [chars] - [chars]","The system failed to send a message via IPC to the specified card. The cause of the specific IPC failure is specified in the message text.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","MISSING_BUNDLE_ENTRY","Failed to find a matching entry in the programmable device bundle information table.","There is a problem in the internal software coding. This message should not be seen under normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","MISSING_DEV_INFO","Could not find [chars] (FPD ID=[int]) information for [chars] card in [chars].","There is a problem in the internal software coding. This message should not be seen under normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","MISSING_IMAGE","Could not find the required [chars] image (FPD ID=[int] and FPD version=[int].[int] compatible with HW version=[int].[int]) from the [chars]-fpd.bndl bundle in [chars] file. Please make sure that this is a valid FPD image [chars] file for [chars] card in [chars].","The specified FPD image bundle or package file might not be the correct one. If this is an FPD image package file, then an incompatible package file might have been renamed with a filename that matched the one that the system is expecting for this Cisco IOS software release. You should never rename an FPD image package file name.","Ensure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the correct one from the Cisco Software Center website. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show hw-module subslot fpd, the show upgrade fpd table, and the show upgrade fpd file fpd-pkg-url commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","OPEN_FAILED","Failed to open [chars] ([chars]). Please make sure that the required file is in a valid path.","The system cannot access the required file from the specified URL.","Ensure that the specified URL is a valid path and the system has access to the file system where the file has been placed."
"FPD_MGMT","3","OUT_OF_MEMORY","Could not allocate the required [dec] bytes of memory.","The system does not have enough free main memory to download the bundle file.","Make sure that the system main memory size meets the minimum requirement that is specified in the Cisco IOS software release note. If the system meets the minimum requirement for this Cisco IOS software release, make sure that the amount of free main memory in the system also meets the minimum memory required to use this software feature. Enter the show memory command to find out this information and add more main memory if it is necessary. If the system meets all the memory requirements, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","PKG_FILE_SEARCH_FAILED","FPD image package ([chars]) cannot be found in system's flash card or disk to do FPD upgrade.","By default, if the upgrade fpd path fpd-pkg-url global configuration command is not configured, then the system will try to locate the required FPD image package file from removable flash cards or disks that are accessible by the system for an FPD upgrade. This message indicates that the system could not find the package file.","Make sure that the specified FPD image package file is copied into a flash card or disk that is accessible by the system, then restart the FPD upgrade by reinserting the target card or entering a system command to reload or power-cycle the target card."
"FPD_MGMT","3","PKG_VER_FILE_EXTRACT_ERROR","Cannot extract the [chars] version file from [chars] - [chars]","There is a package version file extraction error. The cause of the failure is specified in the message. The specified file might not be a valid FPD image package file.","Ensure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the correct one from the Cisco Software Center website. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show hw-module subslot fpd, the show upgrade fpd table, and the show upgrade fpd file fpd-pkg-url commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","READ_BNDL_HDR_ERROR","Failed to read the FPD bundle header from [chars] file.","The specified file might not be a valid FPD image bundle or package file.","Ensure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the correct one from the Cisco Software Center website. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show hw-module subslot fpd, the show upgrade fpd table, and the show upgrade fpd file fpd-pkg-url commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","READ_ERROR","Could not read the [chars] file.","The system cannot read the required file from the specified URL.","Make sure that the specified URL is a valid path and that the system has access to the file system where the file has been placed."
"FPD_MGMT","3","SEND_IMG_FAILED","[chars] (FPD ID=[int]) image for [chars] card in [chars] has failed to be sent for upgrade operation - [chars]","The FPD image was not able to be sent for the upgrade operation. The system might be too busy to handle this operation. The affected card will be disabled by this failure.","Wait until the system load is lower to try again with the manual upgrade procedure by using the upgrade hw-module privileged EXEC command. If the symptom persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","SW_ERROR","NULL","There is a problem in the internal software coding. This message should not be seen under normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","TOO_MANY_FPD_ENTRIES","Too many FPD entries for the FPD Bundle Info Table. Required number of entries = [int], maximum number of entries allowed = [int].","There is a problem in the internal software coding. This message should not be seen under normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","UNKNOWN_BNDL_HDR_FORMAT","Unknown header format version: [hex]","There is a problem in the internal software coding. This message should not be seen under normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","UPGRADE_LIST_FULL","Could not add a new entry in the FPD Management Upgrade List. No upgrade will be performed for the [chars] card in [chars].","There is a problem in the internal software coding. This message should not be seen under normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","WRONG_IMG_DATA_LEN","The FPD image for [chars] (FPD ID [int]) in [chars] file contains wrong data length: total data length (with padding) = [int] bytes, data length = [int] bytes. Please make sure that this is a valid FPD image bundle or package file for card in [chars].","The specified file might not be a valid FPD image bundle or package file for the card.","Ensure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the correct one from the Cisco Software Center website. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show hw-module subslot fpd, the show upgrade fpd table, and the show upgrade fpd file fpd-pkg-url commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","WRONG_IMG_HDR_LEN","The FPD image for [chars] (FPD ID [int]) in [chars] file contains wrong header length: [int] bytes (expected [int] bytes). Please make sure that this is a valid FPD image bundle or package file for card in [chars].","The specified file might not be a valid FPD image bundle or package file for the card.","Ensure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the correct one from the Cisco Software Center website. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show hw-module subslot fpd, the show upgrade fpd table, and the show upgrade fpd file fpd-pkg-url commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","WRONG_IMG_MAGIC_NUM","The FPD image for [chars] (FPD ID [int]) in [chars] file contains wrong magic number: [hex] (expected [hex]). Please make sure that this is a valid FPD image bundle or package file for card in [chars].","The specified file might not be a valid FPD image bundle or package file for the card.","Ensure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the correct one from the Cisco Software Center website. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show hw-module subslot fpd, the show upgrade fpd table, and the show upgrade fpd file fpd-pkg-url commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","3","WRONG_IMG_MAJOR_VER","The selected FPD image for upgrade contains wrong FPD image major version number = '[int]' (expected number = '[int]') for [chars] (FPD ID [int]). Please make sure that the file being used for upgrade is a valid FPD image [chars] for card in [chars].","The file used for upgrade might not be a valid FPD image bundle or package file for the card.","Ensure that the version of the FPD image package, which is stated in the package filename, matches or is compatible with the Cisco IOS software release that the system is running. If the version is not the correct one, try to obtain the correct one from the Cisco Software Center website. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show hw-module subslot fpd, the show upgrade fpd table, and the show upgrade fpd file fpd-pkg-url commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FPD_MGMT","4","BYPASS_AUTO_UPGRADE","The automatic FPD image upgrade feature is not enabled, bypassing the image upgrade for [chars] card in [chars].","The automatic FPD image upgrade feature is not enabled. The incompatible image will not be automatically upgraded. The card will be disabled until the image is upgraded to a compatible version.","Enable the automatic FPD image upgrade by entering the upgrade fpd auto global configuration command, or enter the upgrade hw-module privileged EXEC command for a manual upgrade operation. For more information about these commands, refer to the FPD image upgrade feature document for the target card. (This documentation can be found in the software configuration guide for the target card.)"
"FPD_MGMT","4","CFG_NOT_SYNCED","Failed to sync '[chars]' command to standby: [chars]","A FPD configuration command failed to get synced to standby RP due to the indicated error condition. Usually this can happen if the standby RP hardware doesn't support the type of filesystem supported on the active one.","Configure again the command with a filesystem that is supported on both standby and active RP. To find out if a specific filesystem is also supported on standby RP, the dir ? command can be used to display a list of filesytem supported on both standby and active RP."
"FPD_MGMT","4","UPGRADE_EXIT","Unexpected exit of FPD image upgrade operation for [chars] card in [chars].","The FPD image upgrade operation was interrupted by the physical removal of the card from the system or by the use of other commands that have interrupted the normal operation of the target card. The partial upgrade operation might have left the card unusable because of corrupted FPD images.","If the card does not come up after reinserting into the system, perform the recovery upgrade operation by entering the upgrade hw-module privileged EXEC command. With this command, the system will attempt to reprogram the image to recover from the previous partial upgrade operation. For more information about performing a recovery upgrade operation, refer to the FPD image upgrade feature document for the target card (this documentation can be found in the software configuration guide for the target card)."
"FPD_MGMT","4","VERSION_CHECK_ABORTED","FPD image version check operation has been aborted for [chars] card in [chars] because manual upgrade has already being started.","The FPD image version check operation required for the automatic upgrade feature is not being performed for the specified card because the upgrade hw-module privileged EXEC command has already being executed. These two operations cannot be performed at the same time.","If an automatic upgrade operation is required, do not enter the upgrade hw-module privileged EXEC command for the manual upgrade while the target card is initializing. Enter the show hw-module subslot fpd command and ensure that the target card is displayed in the command output before proceeding with the manual upgrade."
"FPD_MGMT","5","CARD_DISABLED","[chars] card in [chars] is being disabled because of an incompatible FPD image version. Note that the [chars] package will be required if you want to perform the upgrade operation.","The specified card contains an incompatible FPD image version, and is being disabled to avoid operational problems with the existing Cisco IOS software. This can happen if the automatic upgrade feature has not been enabled with the upgrade fpd auto global configuration command, if the automatic upgrade operation failed to perform the required upgrade, or because it could not find the necessary FPD image package file. Upgrade the incompatible image so that the system can enable the card.","The FPD image upgrade can be performed automatically by making sure that the automatic upgrade feature is enabled with the upgrade fpd auto global configuration command and the necessary FPD image package file is located in the system's default file system (for instance, disk0:) or in a location specified by the upgrade fpd path directory-url global configuration command. When the automatic upgrade feature is enabled, the upgrade is triggered by the reinsertion of the card into the system or the use of a system command to reload or power-cycle the target card. nother way to perform the upgrade is through the use of the upgrade hw-module privileged EXEC command. For more information about these commands, refer to the FPD image upgrade feature document for the target card (this documentation can be found in the software configuration guide for the target card)."
"FPD_MGMT","5","POST_UPGRADE_REMINDER","[chars] card in [chars] will require a [chars] for the FPD image upgrade to take effect.","The indicated card will require manual intervention after the FPD image upgrade. The specified operation is required for the upgraded FPD image to take effect.Error Message    No action is required.%FPD_MGMT-5-CARD_POWER_CYCLE: [chars] card in [chars] is being power cycled for the FPD image upgrade to take effect. Explanation    The specified card is being power cycled after the FPD image upgrade. This action allows the target card to be operational with the new upgraded FPD image or images.","This is an informational message only. No action is required."
"FPD_MGMT","5","UPGRADE_ATTEMPT","Attempting to automatically upgrade the FPD image(s) for [chars] card in [chars]. Use 'show upgrade fpd progress' command to view the upgrade progress ...","The automatic FPD image upgrade feature is enabled with the upgrade fpd auto global configuration command. The system is currently upgrading an incompatible image version automatically.","The upgrade process can take a long time. The FPD_MGMT-6-UPGRADE_TIME message gives an estimate of the total upgrade time. No action is required."
"FPD_MGMT","6","BUNDLE_DOWNLOAD","Downloading FPD image bundle for [chars] card in [chars] ...","The system is downloading the field programmable device image bundle to the system main memory.","This is an informational message only. No action is required."
"FPD_MGMT","6","OVERALL_UPGRADE","All the attempts to upgrade the required FPD images have been completed for [chars] card in [chars]. Number of successful/failure upgrade(s): [int]/[int].","All the FPD image upgrades have completed for the specified card.","This is an informational message only. No action is required."
"FPD_MGMT","6","PENDING_UPGRADE","[int] more FPD image upgrade operation will be required on [chars] in [chars] after additional power-cycle operation on the target card.","All upgrade operations have not completed, and additional power-cycle operations are required before the upgraded or new FPD image will be applied to the system configuration. The message text specifies the number of pending upgrade operations that will be performed. More than one power-cycle operation might be required to complete the overall upgrade process.","This is an informational message only. No action is required."
"FPD_MGMT","6","UPGRADE_PASSED","[chars] (FPD ID=[int]) image in the [chars] card in [chars] has been successfully updated from version [chars] to version [int].[int]. Upgrading time = [time-stamp]","The FPD image upgrade process has completed successfully for the specified device.","This is an informational message only. No action is required."
"FPD_MGMT","6","UPGRADE_RETRY","Attempting to recover from the failed upgrades ...","Because of an image upgrade failure, the system will attempt another upgrade operation for the same FPD image.","This is an informational message only. No action is required."
"FPD_MGMT","6","UPGRADE_START","[chars] (FPD ID=[int]) image upgrade in progress for [chars] card in [chars]. Updating to version [int].[int]. PLEASE DO NOT INTERRUPT DURING THE UPGRADE PROCESS (estimated upgrade completion time = [time-stamp]) ...","The FPD image upgrade process has started. Do not interrupt the upgrade operation because any interruption could render the target card unusable. Avoid actions such as removing the target card from the system, powering off the system, or using commands that can power-cycle the target card during the upgrade process.","This is an informational message only. No action is required."
"FPD_MGMT","6","UPGRADE_TIME","Estimated total FPD image upgrade time for [chars] card in [chars] = [time-stamp].","The estimated total time for all FPD images to be upgraded is displayed for the specified card.","This is an informational message only. No action is required."
"FR","3","FR_PVC_STATUS_Q_CREATE_ERROR","FR PVC status event queue error: failed to create queue","Unable to create FR PVC status event queue","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FR","3","SVC_SETUP","[chars]: interface [chars]: DLCI [dec]","An error occurred while attempting to set up a Frame Relay SVC. There may have been an attempt to set up an SVC using a DLCI that is already in use.","Check if the DLCI is already in use. For example, a PVC may be configured to use the same DLCI by entering the show frame-relay pvc command. If so, remove the configuration."
"FR","5","CONVERT_ROUTE","Converting route pair to connect","A pair of Frame Relay routes is being converted to connections.","No action is required."
"FR_ADJ","3","ADD_MEMBER","Unable to add adjacency for vc-bundle [chars] member [dec]","An error occurred while adding an adjacency for a VC-bundle member.","Delete the VC bundle and reconfigure on the same interface."
"FR_ADJ","3","ARRAY_FULL","Unable to setup adjacencies for vc-bundle [chars]","An error occurred while setting up VC-bundle adjacencies.","Try shutting down the subinterface on which the VC bundle is configured. After a minute or so, verify that the adjacencies on the subinterface have been deleted. Reconfigure the VC bundle."
"FR_ADJ","3","ARRAY_INDEX_ERROR","Adjacency array index is incorrect for vc-bundle [chars] member [dec]","An error occurred while setting up VC-bundle adjacencies.","Try shutting down the subinterface on which the VC bundle is configured. After a minute or so, verify that the adjacencies on the subinterface have been deleted. Reconfigure the VC bundle."
"FR_HA","3","ISSU","[chars]: [chars]","A Frame Relay ISSU error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FR_HA","3","SYNC","[chars]: code [dec]","An error occurred when synchronizing the Frame Relay state to the standby route processor. This may affect nonstop forwarding capability on Frame Relay interfaces during and after switchover until the state is recovered through normal protocol operation.","Reset the standby processor to attempt the synchronization again. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FRR_OCE","3","GENERAL","[chars]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FRR_OCE","3","INVALIDPAR","[chars]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FRR_OCE","3","NULLPOINTER","[chars]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FR_VCB","3","BUMPING","Bumping error - vcb [chars] - [chars]","An error occurred while bumping traffic in a VC bundle.","As a workaround, reconfigure the VC bundle to avoid bumping."
"FR_VCB","3","CONFIG","Configuration error - vcb [chars] - [chars]","An error occurred while interpreting the VC bundle configuration.","Try reconfiguring the VC bundle."
"FR_VCB","3","FIBSW_MISSING_TABLE_ENTRY","FIB switching error - vc-bundle [chars]","An error occurred while FIB switching packet(s) across a VC bundle.","As a workaround, delete the VC bundle and use a PVC to substitute for the VC bundle."
"FR_VCB","3","PROCESS_SWITCHING","Switching error - vcb [chars] - [chars]","An error occurred while switching packets across a VC bundle.","As a workaround, delete the VC bundle and employ a PVC to substitute for the VC bundle."
"FR_VCB","5","UPDOWN","FR VC-Bundle [chars] changed state to [chars]","The state of a Frame Relay VC bundle changed to up/down.","This is an informational message only. No action is required."
"FR_VIP","3","INCONSISTENT","Invalid state on VIP: DLCI [dec]: Slot [dec]: Error code [dec]","An error occurred while the Frame Relay state of the VIP was being processed.","Enter the shutdown and no shutdown commands to disable and enable the Frame Relay-encapsulated interface for the specified slot."
"FR_VIP","3","MISSING_STATE","Missing state on VIP: DLCI [dec]: Slot [dec]","An error occurred while an IPC statistics unit was being prepared.","Enter the shutdown and no shutdown commands to disable and enable the Frame Relay-encapsulated interface for the specified slot."
"FR_VIP","3","SWITCHING","[chars] DLCI [dec]: [chars]","An error was detected while a packet was being switched on the VIP.","Enter the shutdown and no shutdown commands to disable and enable the Frame Relay-encapsulated interface for the specified slot, or unconfigure then reconfigure the interface. If this does not solve the problem, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FR_VIP","5","FLUSH","Flushing frame relay state","The Frame Relay state of the VIP card is being cleared.","No action is required."
"FS_IPHC","2","LC_IPHC_SETUP_FAIL","Failed to initialise or allocate memory for IP Compression database.","The IP compression main database could not be created because of a lack of memory resources. The line card cannot allocate memory for an IP compression database.","If possible, add more memory to the VIP. Obtain more free memory on the VIP by reducing the features that are used or buffer allocations. Enter the ip rtp compression-connections command in interface configuration mode to reduce the number of contexts configured on all interfaces on the affected line card."
"FS_IPHC","4","LC_IPCSENDFAIL","LC unable to send IPHC msg to RP ([int])","The IP compression main database could not be created because of a lack of memory resources. The line card cannot allocate memory for an IP compression database.","If possible, add more memory to the VIP. Obtain more free memory on the VIP by reducing the features that are used or buffer allocations. Enter the ip rtp compression-connections command in interface configuration mode to reduce the number of contexts configured on all interfaces on the affected line card."
"FS_IPHC","4","RP_NOIPCBUFFER","Unable to malloc IPC msg buffer ([int]) on RP","The line card was unable to send IPHC information to the route processor because of a lack of memory in its private memory pool.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FTTM","3","ERROR","[chars]","An FTTM manager error has occurred. The cause of the error is given in the message itself.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FW","3","SMTP_INVALID_COMMAND","Invalid SMTP command (%s)(total %d chars) from initiator (%i:%d)","The CBAC code detected an invalid SMTP command in the inspected SMTP connection. This message indicates that a suspicious violation was detetected that may be an attack to the mail server system. The command is rejected and the connection is reset by the firewall immediately.","This message is for informational purposes only, but may indicate a security problem."
"FW","4","ALERT_OFF","%s, count (%d/%d) current 1-min rate: %d","Either the number of half-open connections or the new connection initiation rate has gone below the max-incomplete low threshold. This message indicates that the rate of incoming new connections has slowed down and is issued only when the max-incomplete low threshold is crossed.","This message is for informational purposes only, but may indicate that an attack has stopped."
"FW","4","ALERT_ON","%s, count (%d/%d) current 1-min rate: %d","Either the max-incomplete high threshold of half-open connections or the new connection initiation rate has been exceeded. This error message indicates that an unusually high rate of new connections is coming through the firewall, and a DOS attack may be in progress. This message is issued only when the max-incomplete high threshold is crossed.","This message is for informational purposes only, but may indicate a security problem."
"FW","4","HOST_TCP_ALERT_ON","Max tcp half-open connections (%d) exceeded for host %i.","The max-incomplete host limit of half-open TCP connections has been exceeded. This message indicates that a high number of half-open connections is coming to the protected server, and may indicate that a SYN flood attack is in progress and is targeted to the specified server host.","This message is for informational purposes only, but may indicate that a SYN flood attack was attempted. If this alert is issued frequently and identified to be mostly false alarms, then the max-incomplete host threshold value is probably set too low, and there is a lot of legitimate traffic coming in to that server. In this case, the max-incomplete host parameter should be set to a higher number to avoid false alarms."
"FW","4","TCP_MAJORDOMO_EXEC_BUG","Majordomo Execute Attack - from %i to %i","A bug in the Majordomo program will allow remote users to execute arbitrary commands at the privilege level of the server.","For security reasons users should not be allowed to execute programs via e-mail servers. This is a very serious indication that your network may be under attack and the source should be shunned immediately."
"FW","4","TCP_SENDMAIL_BAD_FROM_SIG","Sendmail Invalid Sender - from %i to %i","Triggers on any mail message with a ''pipe'' (|) symbol in the ''From:'' field.","For security reasons users should not be allowed to execute programs via e-mail servers. This is a very serious indication that your network may be under attack and the source should be shunned immediately."
"FW","4","TCP_SENDMAIL_BAD_FROM_SIG","Sendmail Invalid Sender - from %i to %i","Triggers on any mail message with a ''pipe'' (|) symbol in the ''From:'' field.","For security reasons users should not be allowed to execute programs via e-mail servers. This is a very serious indication that your network may be under attack and the source should be shunned immediately."
"FW","4","TCP_SENDMAIL_BAD_TO_SIG","Sendmail Invalid Recipient - from %i to %i","Triggers on any mail message with a ' 'pipe'' (|) symbol in the recipient field.","For security reasons users should not be allowed to execute programs via e-mail servers. This is a very serious indication that your network may be under attack and the source should be shunned immediately."
"FW","4","TCP_SENDMAIL_DECODE","Sendmail Decode Alias - from %i to %i","Triggers on any mail message with '': decode@'' in the header. The decode alias is used to uudecode files and is primarily implemented as a convenience for system administration.","For security reasons users should not be allowed to execute programs via e-mail servers. This is a very serious indication that your network may be under attack and the source should be shunned immediately."
"FW","4","TCP_SENDMAIL_INVALID_COMMAND","Invalid SMTP command - %i to %i","Triggers on an invalid SMTP command in the SMTP connection. This message indicates that a suspicious violation was detetected that may be an attack to the mail server system.","This is unusual traffic and may warrant investigation."
"FW","4","TCP_SENDMAIL_INVALID_COMMAND","Invalid SMTP command - %i to %i","Triggers on an invalid SMTP command in the SMTP connection. This message indicates that a suspicious violation was detetected that may be an attack to the mail server system.","This is unusual traffic and may warrantinvestigation."
"FW","4","TCP_SENDMAIL_OLD_SIG","Archaic Sendmail Attacks - from %i to %i","Triggers when ''wiz'' or ''debug'' commands are sent to the SMTP port.","For security reasons users should not be allowed to execute programs via e-mail servers. This is a very serious indication that your network may be under attack and the source should be shunned immediately."
"FW","4","UNBLOCK_HOST","New TCP connections to host %i no longer blocked","New TCP connection attempts to the specified host are no longer blocked. This message indicates that the blocking of new TCP attempts to the specified host has been lifted.","This message is for informational purposed only, but may indicate a SYN flood attack was attempted to the host."
"FW","4","UNAVAILABLE","%s, count (%d/%d) current 1-min rate: %d","Either the max-incomplete high threshold of half-open connections or the new connection initiation rate has been exceeded. This error message indicates that an unusually high rate of new connections is coming through the firewall, and a DOS attack may be in progress. This message is issued only when the max-incomplete high threshold is crossed.","This message is for informational purposed only, but may indicate a security problem."
"FW","4","UNAVAILABLE","%s, count (%d/%d) current 1-min rate: %d","Either the number of half-open connections or the new connection initiation rate has gone below the max-incomplete low threshold. This message indicates that the rate of incoming new connections has slowed down and is issued only when the max-incomplete low threshold is crossed.","This message is for informational purposed only, but may indicate that an attack has stopped."
"FW","4","UNAVAILABLE","Archaic Sendmail Attacks - from %i to %i","Triggers when ''wiz'' or ''debug'' commands are sent to the SMTP port.","For security reasons users should not be allowed to execute programs via e-mail servers. This is a very serious indication that your network may be under attack and the source should be shunned immediately."
"FW","4","UNAVAILABLE","Invalid SMTP command - %i to %i","Triggers on an invalid SMTP command in the SMTP connection. This message indicates that a suspicious violation was detetected that may be an attack to the mail server system.","This is unusual traffic and may warrantinvestigation."
"FW","4","UNAVAILABLE","Majordomo Execute Attack - from %i to %i","A bug in the Majordomo program will allow remote users to execute arbitrary commands at the privilege level of the server.","For security reasons users should not be allowed to execute programs via e-mail servers. This is a very serious indication that your network may be under attack and the source should be shunned immediately."
"FW","4","UNAVAILABLE","Max tcp half-open connections (%d) exceeded for host %i.","The max-incomplete host limit of half-open TCP connections has been exceeded. This message indicates that a high number of half-open connections is coming to the protected server, and may indicate that a SYN flood attack is in progress and is targeted to the specified server host.","This message is for informational purposes only, but may indicate that a SYN flood attack was attempted. If this alert is issued frequently and identified to be mostly false alarms, then the max-incomplete host threshold value is probably set too low, and there is a lot of legitimate traffic coming in to that server. In this case, the max-incomplete host parameter should be set to a higher number to avoid false alarms."
"FW","4","UNAVAILABLE","New TCP connections to host %i no longer blocked","New TCP connection attempts to the specified host are no longer blocked. This message indicates that the blocking of new TCP attempts to the specified host has been lifted.","This message is for informational purposed only, but may indicate a SYN flood attack was attempted to the host."
"FW","4","UNAVAILABLE","Sendmail Decode Alias - from %i to %i","Triggers on any mail message with '': decode@'' in the header. The decode alias is used to uudecode files and is primarily implemented as a convenience for system administration.","For security reasons users should not be allowed to execute programs via e-mail servers. This is a very serious indication that your network may be under attack and the source should be shunned immediately."
"FW","4","UNAVAILABLE","Sendmail Invalid Recipient - from %i to %i","Triggers on any mail message with a ' 'pipe'' (|) symbol in the recipient field.","For security reasons users should not be allowed to execute programs via e-mail servers. This is a very serious indication that your network may be under attack and the source should be shunned immediately."
"FW","4","UNAVAILABLE","Sendmail Invalid Sender - from %i to %i","Triggers on any mail message with a ''pipe'' (|) symbol in the ''From:'' field.","For security reasons users should not be allowed to execute programs via e-mail servers. This is a very serious indication that your network may be under attack and the source should be shunned immediately."
"FW","6","SESS_AUDIT_TRAIL","%s session initiator (%i:%d) sent %u bytes -- responder (%i:%d) sent %u bytes","This message documents the per-session transaction log of network activities. The message is issued at the end of each inspected session and it records the source/destination addresses and ports, as well as the number of bytes transmitted by the client and server.","This message is for informational purposes only, and can be used to collect the basic accounting for the inspected sessions."
"FW","6","UNAVAILABLE","%s session initiator (%i:%d) sent %u bytes -- responder (%i:%d) sent %u bytes","This message documents the per-session transaction log of network activities. The message is issued at the end of each inspected session and it records the source/destination addresses and ports, as well as the number of bytes transmitted by the client and server.","This message is for informational purposed only, and can be used to collect the basic accounting for the inspected sessions."
"FX1000","1","UNAVAILABLE","%s, initialization failed, no buffer memory","The GigabitEthernet port initialization failed due to insufficient memory","Upgrade the GigabitEthernet Interface Processor with larger memory model. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FX1000","1","UNAVAILABLE","Could not initialize structure","The driver failed to initialize a structure","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FX1000","1","UNAVAILABLE","Only found %d interfaces on bay %d, shutting down bay","Possible hardware error resulted in too few GE interfaces discovered","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FX1000","3","UNAVAILABLE","%s, error interrupt, csr_STATUS=%#x","The GigabitEthernet controller has signalled an error condition.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FX1000","3","UNAVAILABLE","%s, packet too big (%d), src %e, dst %e","The interface detects a packet larger than what is defined by mtu","Check the other station's MTU setting LOG_STD_NO_ACTION"
"FX1000","3","UNAVAILABLE","FX1000(%d/%d), packet too big (%d), from %e","The interface detects a packet larger than what is defined by mtu","Check the other station's MTU setting"
"FX1000","3","UNAVAILABLE","FX1000(%d/%d), unknown device (%x)","Somehow the GE PA does not contain a Gigabit controller chip","Could be a mislabeled PA"
"FX1000","3","UNAVAILABLE","PA bay %u, device number %u: unknown device (%#x)","Somehow the GE PA does not contain a Gigabit controller chip","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"FX1000","5","UNAVAILABLE","%s cable/transceiver problem?","The GigabitEthernet port detects link failure, meaning that it is no longer receiving signals from the LAN. This can be caused by disconnected GigabitEthernet cabling, a transceiver (GBIC)failure, or the remote end has shutdown.","Check your GigabitEthernet wiring and port adapter. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GBIC","4","CHECK_SUM_FAILED","GBIC EEPROM data check sum failed for GBIC interface [chars]","The GBIC was identified as a Cisco GBIC, but the system was unable to read vendor-data information to verify its correctness.","Remove and reinsert the GBIC. If it fails again in the same way, the GBIC may be defective."
"GBIC","4","NOREAD_VSDATA","Unable to read vendor-specific data for GBIC interface [chars]","The GBIC was identified as a Cisco GBIC, but the system was unable to read identifying vendor-specific information to verify its authenticity.","Remove and reinsert the GBIC. If it fails again in the same way, the GBIC may be defective."
"GBIC","4","UNRECOGNIZED_EXTTYPE","GBIC interface [chars] has unrecognized extended type","The GBIC was identified as a Cisco GBIC, but the system does not recognize its reported extended type code.","Check the list of supported GBICs for this version of the system software. An upgrade may be required for newer GBICs. Even if unrecognized, the GBIC may still operate properly, perhaps with limited functionality."
"GBIC","6","UNAVAILABLE","Unrecognizable GBIC found in %s (module mask 0x%02x)","The GBIC presented data to the system which did not correctly identify the type of the GBIC. It will be handled as a 'generic' GBIC.","If the GBIC fails to become operational, carefully reinsert it in the slot. If it continues to fail after reinsertion, the GBIC may be defective or incompatible with the switch."
"GBIC","6","UNAVAILABLE","Unrecognizable GBIC found in %s (serial data 0x%02x)","The GBIC presented data to the system which did not correctly identify the type of the GBIC. It will be handled as a 'generic' GBIC.","If the GBIC fails to become operational, carefully reinsert it in the slot. If it continues to fail after reinsertion, the GBIC may be defective or incompatible with the switch."
"GBIC_1000BASET","6","UNAVAILABLE","1000-BaseT GBIC module is detected in %s. Speed and duplex will be autonegotiated","1000-BaseT GBIC modules only support autonegotiation on speed/duplex.Error Message    %GBIC_1000BASET-6-UNAVAILABLE: 1000-BaseT GBIC module is detected in %s. Speed and duplex will be autonegotiated Explanation    1000-BaseT GBIC modules only support autonegotiation on speed/duplex.","LOG_STD_NO_ACTION"
"GBIC_1000BASET","6","UNAVAILABLE","Configuration ignored. 1000-BaseT GBIC modules only support autonegotiation on duplex.","1000-BaseT GBIC modules only support autonegotiation on duplex.Error Message    %GBIC_1000BASET-6-UNAVAILABLE: Configuration ignored. 1000-BaseT GBIC modules only support autonegotiation on duplex. Explanation    1000-BaseT GBIC modules only support autonegotiation on duplex.","LOG_STD_NO_ACTION"
"GBIC_1000BASET","6","UNAVAILABLE","Configuration ignored. 1000-BaseT GBIC modules only support autonegotiation on speed.","1000-BaseT GBIC modules only support autonegotiation on speed.Error Message    %GBIC_1000BASET-6-UNAVAILABLE: Configuration ignored. 1000-BaseT GBIC modules only support autonegotiation on speed. Explanation    1000-BaseT GBIC modules only support autonegotiation on speed.","LOG_STD_NO_ACTION"
"GBIC_1000BASET","6","UNAVAILABLE","Configuration ignored. 1000-BaseT GBIC modules only support autonegotiation.","1000-BaseT GBIC modules only support autonegotiation.Error Message    %GBIC_1000BASET-6-UNAVAILABLE: Configuration ignored. 1000-BaseT GBIC modules only support autonegotiation. Explanation    1000-BaseT GBIC modules only support autonegotiation.","LOG_STD_NO_ACTION"
"GBIC_1000BASET","6","GBIC_1000BASET_NO_CONFIG_NEGOTIATE","Configuration ignored. 1000-BaseT GBIC modules only support autonegotiation.","1000-BaseT GBIC modules only support autonegotiation.","No action is required."
"GBIC_SECURITY","4","UNAVAILABLE","EEPROM checksum error for GBIC in %s","The GBIC in the port specified in the error message has invalid EEPROM data.","Remove the GBIC from the specified port."
"GBIC_SECURITY","4","UNAVAILABLE","Error in reading GBIC serial ID in %s","Error when reading GBIC type from EEPROM","Please remove GBIC from this Port"
"GBIC_SECURITY","4","UNAVAILABLE","GBIC in %s failed security check","The GBIC in the port specified in the error message has invalid EEPROM data.","Remove the GBIC from the specified port."
"GBIC_SECURITY","4","UNAVAILABLE","Internal error occurred in setup for GBIC interface %s","The system could not allocate resources, or had some other problem, in the setup for the specified GBIC interface.","Reload the system. If the problem persists, contact TAC."
"GBIC_SECURITY_CRYPT","4","UNAVAILABLE","GBIC in port %d has bad crc","The GBIC was identified as a Cisco GBIC, but it does not have valid CRC in the EEPROM data.","Check to see if the Cisco IOS software running on the system supports the GBIC. If the GBIC is newer, a system software upgrade might be required. Even if the GBIC is unrecognized by the system, the GBIC may still operate properly, but might have limited functionality."
"GBIC_SECURITY_CRYPT","4","UNAVAILABLE","GBIC in port %d manufactured by an unrecognized vendor","The GBIC was identified as a Cisco GBIC, but the system was unable to match its manufacturer with one on the known list of Cisco GBIC vendors","Check to see if the Cisco IOS software running on the system supports the GBIC. If the GBIC is newer, a system software upgrade might be required."
"GBIC_SECURITY_CRYPT","4","UNAVAILABLE","Identification check failed for GBIC in port %d","The GBIC was identified as a Cisco GBIC, but the system was unable to verify its identity","Check to see if the Cisco IOS software running on the system supports the GBIC. If the GBIC is newer, a system software upgrade might be required. Otherwise, verify that the GBIC was obatined from Cisco or from a supported vendor."
"GBIC_SECURITY_UNIQUE","3","UNAVAILABLE","GBIC interface %d/%d is a duplicate of GBIC interface %d/%d","The GBIC was identified as a Cisco GBIC, but its vendor ID and serial number match that of another interface on the system.","Cisco GBICs are assigned unique serial numbers. Verify that the GBIC was obtained from Cisco or a supported vendor"
"GBIC_SECURITY_UNIQUE","4","DUPLICATE_SN","GBIC interface [dec]/[dec] has the same serial number as another GBIC interface","The GBIC was identified as a Cisco GBIC, but its serial number matches that of another interface on the system.","Cisco GBICs are assigned unique serial numbers. Verify that the GBIC was obtained from Cisco or a supported vendor."
"GDOI","1","GDOI_ACE_DENY","A Group Member ACL policy containing deny was attempted. This is not supported.","A Group Member ACL policy containing deny was attempted. This is not supported.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GDOI","1","GDOI_ACL_NUM","The ACL has too many entries. GDOI will honor only the first 100 ACL entries specified.","The ACL has too many entries. GDOI will honor only the first 100 ACL entries specified.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GDOI","1","KS_NO_RSA_KEYS","RSA Key - [chars] : Not found, Required for group [chars]","RSA keys are required for signing and verifying rekey messages, but no RSA keys were found in the key server.","Ask the administrator of the key server to create the required RSA key pair."
"GDOI","1","UNAUTHORIZED_IDENTITY","Group [chars] received registration from unauthorized identity: [chars]","The registration request was dropped because the requesting device was not authorized to join the group.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GDOI","1","UNAUTHORIZED_IPADDR","Group [chars] received registration from unauthorized ip address: [chars]","The registration request was dropped because the requesting device was not authorized to join the group.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GDOI","1","UNREGISTERED_INTERFACE","Group [chars] received registration from unregistered interface.","Receiving registration from an unregistered interface. Processing has stopped.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GDOI","4","GM_RE_REGISTER","The IPSec SA created for group [chars] may have been expired or cleared. Re-register to KS.","The IPsec SA created for one group may have been expired or cleared. You need to reregister to the key server (KS).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GDOI","5","GM_REGS_COMPL","Registration complete for group [chars] using address [chars]","Registration was completed for the specified group.","No action is required."
"GEFC","3","ACCESS_FAIL","LRC access Failed","An attempt to access the line card redundancy controller (LRC) has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GEFC","3","BDI_E_ALM","End-to-End Backward Defect Indication [chars]","An attempt to access the line card redundancy controller (LRC) has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GEFC","3","FPGA_NOT_SUPPORT","Jamesport FPGA need upgrade. slot:[dec] port:[dec] [chars] function","The FPGA on the Jamesport card requires an upgrade so that it can support JP2 functions.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GEFC","3","GEFC_INTRPEND","Pending unexpected interrupt [addr [hex] = [hex]]","One or more pending unexpected interrupts have occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GEFC","3","GEFC_MAGICFAIL","Magic number read failed [[chars]]","The FPGA has reset.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GEFC","3","GEFC_PTFAILASSERTED","Unexpected portfail asserted","One or more unexpected port failures have been asserted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GEFC","3","GEFC_RDWRFAIL","Read/write failed [[chars]]","A read or write error occurred while the hardware was being accessed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GEFC","3","IDPROM_ACCESS_FAIL","Access to IDPROM Failed","An attempt to access to the IDPROM has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GEFC","3","INT_LPBK_FAIL","Internal CardLoopback Failed","An attempt to perform an internal card loopback operation has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GEFC","3","KPA_TIMEOUT_ALM","Keep-alive timeout [chars]","Either normal packets or CDL idle packets were not received.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GEFC","3","LASER_TX_FAULT_ALM","Optic Laser Transmit Fault [chars]","A transceiver laser transmittal fault has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GEFC","3","LOSS_OF_LIGHT_ALM","Loss of Light [chars]","The cable for the transceiver has been cut or removed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GEFC","3","LOSS_OF_LOCK_ALM","Transceiver CDR Loss of Lock [chars]","The CDR is experiencing problems while attempting to lock onto the signal.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GEFC","3","LOSS_OF_SYNC_ALM","Transceiver Loss of Sync [chars]","A loss of synchronization error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GEFC","3","MIB_HW_LASER_DOWN_ALM","Laser Disabled [chars] [chars] [chars]","The client laser has been disabled.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GEFC","3","MIB_KPA_TIMEOUT_ALM","Keep-alive timeout [chars] [chars] [chars]","Normal packets or CDL idle packets were not received.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GEFC","3","MIB_LASER_TX_FLT_ALM","Laser Transmit Fault [chars] [chars] [chars]","A client laser transmittal fault has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GEFC","3","MIB_LOSS_OF_LIGHT_ALM","Transceiver Loss of Light [chars] [chars] [chars]","No light is being received from the client side.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GEFC","3","MIB_LOSS_OF_LOCK_ALM","Loss of Lock [chars] [chars] [chars]","The GEFC has lost its lock on the signal.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GEFC","3","MIB_LOSS_OF_SYNC_ALM","Loss of Sync [chars] [chars] [chars]","The GEFC has lost its synchronization.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GEFC","3","MIB_SFP_VENDOR_UNKNOWN","Unknown Vendor SFP inserted [chars] [chars] [chars]","The SFP is not qualified to work with Cisco products.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GEFC","3","TX_CRC_ERR_THR_ALM","GEFC TX CRC Error Threshold [chars]","The maximum threshold for transmission CRC errors has been exceeded.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GEFC","3","UNKNOWN_SFP_INSERTED","Unknown SFP inserted [chars]","An unknown SFP has been inserted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GEFC","6","UNAVAILABLE","Flow control become active at slot:%d port:%d","Flow control active","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GEFC","6","UNAVAILABLE","Flow control become inactive at slot:%d port:%d","Flow control deactive","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GENERAL","2","CRITEVENT","[chars]","A critical error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GENERAL","3","EREVENT","[chars]","This is a general error message to be used for sanity tests.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GENERAL","3","WSHALEVENT","[chars]","This message provides general error information to be used for sanity testing.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GENERIC_SUBBLOCK","2","UNAVAILABLE","Failed to build message for GSB: %s","An attempt to build a message for distribution of generic subblock failed","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GENERIC_SUBBLOCK","2","UNAVAILABLE","GSB %s is not ISSU aware. Cannot distribute it to ISSU-aware slots","This GSB is expected to be ISSU aware but it is not. IT cannot be distributed safely to ISSU-aware slots as it may not be correctly interpreted","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GENERIC_SUBBLOCK","2","UNAVAILABLE","Late registration of GSB type %s, with id %d","An attempt to register a new generic subblock type was received after subblocks have already been allocated from the control structure with previously registered types","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GENERIC_SUBBLOCK","2","UNAVAILABLE","Unpacked %d bytes and attempted to consume %d bytes for GSB: %s","A discrepancy was detected between length of message expected versus length of message received","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GIGASTACK","1","UNAVAILABLE","The link neighbor of link %d of Gigastack GBIC in %s did not respond to the loop detection request. If loop topology is deployed, make sure all switches in the stack are running the latest software.","No acknowledgement for Gigastack loop detection request is received from one of the links on a Gigastack GBIC. Either the neighboring switch does not support Gigastack Loop breaking algorithm, or the link between the two Gigastack GBICs is broken. Under this condition, a Gigastack loop topology will not be automatically detected and the connectivity between switches in the stack could be lost.","If loop topology is used in the Gigastack, make sure the latest software is running on all switches in the stack. Check the Gigastack GBICs involved to make sure they are functioning."
"GIGASTACK","3","UNAVAILABLE","Gigastack GBIC in %s initialization failed.","Gigastack GBIC failed POST.","Remove the Gigastack GBIC and re-insert it into the GBIC slot."
"GIGASTACK","6","UNAVAILABLE","Gigastack GBIC in %s is selected as Master Loop Breaker. Link 2 of the Gigastack GBIC is disabled to break the loop.","Loop is detected in the Gigastack and this Gigastack GBIC is selected as the Master Loop Breaker. Link 2 of this Gigastack GBIC is disabled to break the loop.","LOG_STD_NO_ACTION"
"GIGASTACK","6","UNAVAILABLE","Link loss is detected in the Gigastack loop Link 2 of the Gigastack GBIC in %s is re-enabled.","Loop formed by Gigastack modules is broken because of link loss. Link 2 of the Master Loop Breaker is re-enabled to replace the broken link","LOG_STD_NO_ACTION"
"GK","3","SUBNET_NOT_FOUND","Subnet not found under specified IP address [IP_address]/[IP_address].","Not Available","Not Available"
"GK","6","UNAVAILABLE","The IP address which has been changed was the gatekeeper's configured RAS address. Existing RAS clients will no longer be able to reach the gatekeeper.","The IP address being changed at the interface was statically assigned to the gatekeeper for its RAS signaling via the zone local command. This action will automatically replace the gatekeeper's static RAS address with the new IP address. Since the gatekeeper's old RAS address is no longer valid, existing clients which have registered to this gatekeeper via the old RAS address will no longer be able to communicate with this gatekeeper.","It is the user's responsibility to notify existing RAS clients to re-register their systems to the gatekeeper's new RAS address as shown in the show gatekeeper zone status display"
"GK","6","UNAVAILABLE","The IP address which has been removed was the gatekeeper's configured RAS address. The system will automatically assign a new IP address (if available) to be used as the gatekeeper's RAS address. Existing RAS clients will no longer be able to reach the gatekeeper.","The IP address being removed at the interface was statically assigned to the gatekeeper for its RAS signaling via the zone local command. This action will automatically remove the gatekeeper's static RAS address. Since the gatekeeper no longer has a configured RAS address, the router will automatically assign an IP address (if there is any) to the gatekeeper. Existing clients which have registered to this gatekeeper via the old RAS address will no longer be able to communicate with this gatekeeper.","It is the user's responsibility to notify existing RAS clients to re-register their systems to the gatekeeper's new RAS address as shown in the show gatekeeper zone status display"
"GK","6","UNAVAILABLE","The connection to GKTMP server %s(%i) appears to be hung and will be closed.","Messages are being backed up in the gatekeeper's write queue in the connection with the specified server name. The connection is assumed to have gone bad and the gatekeeper is closing the connection. This implies that messages will not be sent to that server for processing until either the gatekeeper or the server re-initiates the connection.","Check with the specified server for possible connection error."
"GK","6","UNAVAILABLE","The gatekeeper's RAS address has been automatically changed by the system. Existing RAS clients may no longer be able to reach the gatekeeper.","The IP address being changed at the interface causes the system to look for a better IP address to be used for the gatekeeper's RAS address. existing clients which have registered to this gatekeeper via the old RAS address may no longer be able to communicate with this gatekeeper.","It is the user's responsibility to notify existing RAS clients to re-register their systems to the gatekeeper's new RAS address as shown in the show gatekeeper zone status display"
"GLBP","3","UNAVAILABLE","Cannot add MAC address %e to interface %s - not supported","A software or hardware error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GLBP","4","BADAUTH","Bad authentication received from %s, group %d","Two routers participating in a Gateway Load Balancing Protocol group disagree on the valid authentication string.","Use the glbp authentication interface command to repair the GLBP authentication discrepancy between the local system and the one whose IP address is reported."
"GLBP","4","DUPADDR","Duplicate address %s on %s, sourced by %e","The IP address in a GLBP message received on the interface is the same as the router's own IP address. This may be because of misconfiugration, or because of a malfunctioning switch","Check the configurations on all the GLBP routers, and make sure that any switches you have are functioning properly."
"GLBP","4","UNAVAILABLE","%s Grp %d active routers virtual IP address %s is different to the locally configured address %s","The GLBP virtual IP address contained in the Hello message from the Active router is different to that configured locally.","Check the configuration on all GLBP routers."
"GLBP","4","UNAVAILABLE","%s Grp %d address %s is already assigned on this interface","The GLBP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to this interface.","Check the configuration on all GLBP routers."
"GLBP","4","UNAVAILABLE","%s Grp %d address %s is already assigned to %s group %d","The GLBP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to a different GLBP group.","Check the configuration on all GLBP routers."
"GLBP","4","UNAVAILABLE","%s Grp %d address %s is already assigned to, or overlaps with, an address on another interface or application","The GLBP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to, or overlaps with, an address on another interface or application.","Check the configuration on all GLBP routers."
"GLBP","4","UNAVAILABLE","%s Grp %d address %s is in the wrong subnet for this interface","The GLBP virtual IP address contained in the Hello message cannot be learnt as it is not within a subnet configured on the interface.","Check the configuration on all GLBP routers and ensure that the virtual IP address is within a configured subnet."
"GLBP","4","UNAVAILABLE","Bad authentication received from %s, group %d","Two routers participating in a Gateway Load Balancing Protocol group disagree on the valid authentication string.","Use the glbp authentication interface command to repair the GLBP authentication discrepancy between the local system and the one whose IP address is reported."
"GLBP","4","UNAVAILABLE","Duplicate address %s on %s, sourced by %e","The IP address in a GLBP message received on the interface is the same as the router's own IP address. This may be because of misconfiugration, or because of a malfunctioning switch","Check the configurations on all the GLBP routers, and make sure that any switches you have are functioning properly."
"GLBP","6","UNAVAILABLE","%s Grp %u Fwd %u state %s - %s","The GLBP forwarder has changed state","LOG_STD_NO_ACTION"
"GLBP","6","UNAVAILABLE","%s Grp %u state %s - %s","The GLBP gateway has changed state","LOG_STD_NO_ACTION"
"GPRSFLTMG","0","UNAVAILABLE","%s","Two reasons for this error message, 1. DHCP Client failed to get started, this could be because of malloc failures. 2. GPRS DHCP Process failed to start","If this error message is seen it is recommended not to use this GGSN for PDP session establishment with SGSN with dynamic IP request. Check the available memory in the box and for the first reason try to get 'debug dhcp detail' before the failure. Contact your technical support representative with the error message you got."
"GPRSFLTMG","0","UNAVAILABLE","%s","A Process could not be started","Please contact your technical support representative with the error message you got and with the output of 'show gprs gtp status'."
"GPRSFLTMG","0","UNAVAILABLE","GSN: %i, TEID: %x, APN: %s, Reason: %d, %s","Available resources exhausted to continue GGSN service because of the following reasons : 1. Number of pending signaling messages reaches limit. 2. Out of Memory - Insuffient in GGSN. 3. System failure - Permenant system failure has occured.","1. Check whether you can increase number of PDP that can be handled by GGSN. If the problem recurs , contact your technical support representative with the error message you got and with the output of 'show gprs gtp status'."
"GPRSFLTMG","0","UNAVAILABLE","GSN: %i, TID: %08x%08x, APN: %s, Reason: %d, %s","Available resources exhausted to continue GGSN service because of the following reasons : 1. Number of PDP reaches Limit. 2. Number of Network Initiated PDP reached percentage - Insuffient in GGSN. 3. Number of IP PDP regenerated PPP reaches limit.","1. Check whether you can increase number of PDP that can be handled by GGSN. If the problem recurs , contact your technical support representative with the error message you got and with the output of 'show gprs gtp status'."
"GPRSFLTMG","0","UNAVAILABLE","GSN: %i, TID: %08x%08x, APN: %s, Reason: %d, %s","You get this error messages because of one of the following reasons : 1. Path fail - No echo message is received from the GSN peer and time out. 3. GGSN service up - GGSN service starts. 4. GGSN service down - GGSN service shutdown. 5. Primary Charging Gateway down - Primary charging gateway is not reachable or unconfigured. 6. Primary Charging Gateway up - Primary Charging gateway is up or its configured . 7. Secondary Charging Gateway up - Secondary Charging Gateway is up or its configured. 8. Secondary Charging Gateway becomes unreachable or unconfigured.","Error messages with reasons 3,6 and 7 are informational. For error messages with the other reasons contact your technical supportrepresentative with the error message you got."
"GPRSFLTMG","0","RESOURCE","GSN: [IP_address], TID: [hex][hex], APN: [chars], Reason: [dec], [chars]","Available resources exhausted to continue GGSN service because of the following reasons : 1. Number of PDP reaches Limit. 2. Number of Network Initiated PDP reached percentage - Insuffient     in GGSN. 3. Number of IP PDP regenerated PPP reaches limit.","Check whether you can increase number of PDP that can be handled by GGSN. If the problem recurs, contact your technical support representative with the error message you got and with the output of the show gprs gtp status command."
"GPRSFLTMG","4","UNAVAILABLE","GSN: %i, TEID: %x, APN: %s, Reason: %d, %s","One of the following Mobility Related problem has occured : 1. MS GPRS Detached. 2. MS GPRS present. 3. MS not GPRS responding for network initiated PDP - MS does not respond for packets initiated by external network. 4. MS Refused for network initiated PDP. 5. IMSI unknown for network initiated PDP.","If the problem recurs , contact your technical support representative with the error message you got"
"GPRSFLTMG","4","UNAVAILABLE","GSN: %i, TEID: %x, APN: %s, Reason: %d, %s","A PDP Activation has been failed because of one of the following reasons: 1. No RADIUS server present for Authentication - No RADIUS server is configured or configured RADIUS server is not reachable. 2. Authentication fail - Authentication failed for invalid username or password. 3. Missing PAP/CHAP in non-transparent mode - PAP/CHAP IE is missing in the packet in non-transparent mode. 4. Missing username - User name field is not present in the PDP activation Request sent.","1. Check whether RADIUS server is configured properly and able to ping it. 2. Check whether RADIUS server is configured properly. For the other reasons copy and save the error message with the output of 'show running' command. and contact your technical support representative."
"GPRSFLTMG","4","UNAVAILABLE","GSN: %i, TEID: %x, APN: %s, Reason: %d, %s","Failed to allocate IP address dynamically because of one of the following reason: 1. a. DHCP/RADIUS server IP address has been wrongly configured in GGSN. b. DHCP/RADIUS server is reachable but the configuration to allocate IP address might be wrong. or c. Properly configured DHCP/RADIUS server is unreachable. 2. Dynamic IP allocation is disabled in the APN configuration . 3. Missing PAP/CHAP information from radius client in transparent mode - Username and Password is missing in the PDP Activation Request.","1.a. Check whether the GGSN is conifugred with the valid DHCP/RADIUS server IP address. b. Check whether DHCP/RADIUS server is configured properly to allocate IP address . c. If the configurations are fine, then check whether the server is reachable from GGSN. 2. Configure IP allocation pool as either DHCP proxy client or RADIUS client in the APN . If you could not solve the problem still contact your technical support representative with the error message you got."
"GPRSFLTMG","4","UNAVAILABLE","GSN: %i, TEID: %x, APN: %s, Reason: %d, %s","PDP activation has failed due to one of the APN related problem : 1. APN not configured - The APN requested in the PDP Request is not configured in the GGSN router. 2. Subscribe mode on APN but selection mode field not verified. 3. Duplicate static IP address to access same APN. 4. Session already exists for a different APN.","Check the APN configuration correspondingly. If that can't solve the problem, get the output of 'sh run' and 'sh gprs access-point all' , copy the error message exactly as it appears, and report to your technical support representative."
"GPRSFLTMG","4","UNAVAILABLE","GSN: %i, TEID: %x, APN: %s, Reason: %d, %s","QoS negotitaion/update has failed since resources not available.","Contact your technical support representative with the error messages and the output of command 'sh gprs gtp status' ."
"GPRSFLTMG","4","UNAVAILABLE","GSN: %i, TID: %08x%08x, APN: %s, Reason: %d, %s","You get this syslog message due to one of the following reasons : 1. Primary/Secondary Charging gateway configured/unconfigured. 2. GSN GTP' Transfer Failure - Failure in sending CDRs to Charging gateway configured. 3. GSN CGF Echo Request Failure/Restored - Failure/Success of Echo messages sent charging gateway to check the connectivity of the Charging gateway configured. 4. GSN CDR Capacity Full/Free - Status of GSN CDR buffer full/free , the subsequent packet might be dropped if the buffer is full. 5. GSN CDR Discard Notification - a status whether the GSN CDRs are getting discard/buffered.","1. This is informational . 2. Check whether the charging gateways are configured correctly and are active with the charging functionality. 3. If the configured charging gateway is up and reachable from the GSN, check whether charging function is enabled in the gateway. 4,5. If you have configured gprs char charging-send-buffer-size with minimum bytes , you may configure maximum bytes. If the problem recurs , contact your technical support representative with the error message you got"
"GPRSFLTMG","4","UNAVAILABLE","GSN: %i, TID: %08x%08x, APN: %s, Reason: %d, %s","A PDP Activation has been failed because of one of the following reasons: 1. No RADIUS server present for Authentication - No RADIUS server is configured or configured RADIUS server is not reachable. 2. Authentication fail - Authentication failed for invalid username or password. 3. Missing PAP/CHAP in non-transparent mode - PAP/CHAP IE is missing in the packet in non-transparent mode. 4. Missing username - User name field is not present in the PDP activation Request sent.","1. Check whether RADIUS server is configured properly and able to ping it. 2. Check whether RADIUS server is configured properly. For the other reasons copy and save the error message with the output of 'show running' command. and contact your technical support representative."
"GPRSFLTMG","4","UNAVAILABLE","GSN: %i, TID: %08x%08x, APN: %s, Reason: %d, %s","Failed to allocate IP address dynamically because of one of the following reason: 1. a. DHCP/RADIUS server IP address has been wrongly configured in GGSN. b. DHCP/RADIUS server is reachable but the configuration to allocate IP address might be wrong. or c. Properly configured DHCP/RADIUS server is unreachable. 2. Dynamic IP allocation is disabled in the APN configuration . 3. Missing PAP/CHAP information from radius client in transparent mode - Username and Password is missing in the PDP Activation Request.","1.a. Check whether the GGSN is conifugred with the valid DHCP/RADIUS server IP address. b. Check whether DHCP/RADIUS server is configured properly to allocate IP address . c. If the configurations are fine, then check whether the server is reachable from GGSN. 2. Configure IP allocation pool as either DHCP proxy client or RADIUS client in the APN . If you could not solve the problem still contact your technical support representative with the error message you got."
"GPRSFLTMG","4","UNAVAILABLE","GSN: %i, TID: %08x%08x, APN: %s, Reason: %d, %s","PDP activation has failed due to one of the APN related problem : 1. APN not configured - The APN requested in the PDP Request is not configured in the GGSN router. 2. Subscribe mode on APN but selection mode field not verified. 3. Duplicate static IP address to access same APN. 4. Session already exists for a different APN.","Check the APN configuration correspondingly. If that can't solve the problem, get the output of 'sh run' and 'sh gprs access-point all' , copy the error message exactly as it appears, and report to your technical support representative."
"GPRSFLTMG","4","UNAVAILABLE","GSN: %i, TID: %08x%08x, APN: %s, Reason: %d, %s","QoS negotitaion/update has failed since resources not available.","Contact your technical support representative with the error messages and the output of command 'sh gprs gtp status' ."
"GPRSFLTMG","4","UNAVAILABLE","GSN: %i, TID: %08x%08x, APN: %s, Username: %s Reason: %d, %s","One of the following Mobility Related problem has occured : 1. MS GPRS Detached. 2. MS GPRS present. 3. MS not GPRS responding for network initiated PDP - MS does not respond for packets initiated by external network. 4. MS Refused for network initiated PDP. 5. IMSI unknown for network initiated PDP.","If the problem recurs , contact your technical support representative with the error message you got."
"GPRSMIB","4","UNAVAILABLE","Invalid GPRSMIB message (msg_type %x) received","An internal software error occurred.","Contact your technical support representative."
"GPRSMIB","4","UNAVAILABLE","fragmentation error (s_uid = %x) received","An internal software error occurred.","contact your technical support representative."
"GRIP","2","UNAVAILABLE","Error %s route - null table","A hardware or software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"GRIP","3","UNAVAILABLE","Invalid number of paths (%d) for %q","An internal inconsistency was detected in the XNS routing table structure.","Note the parameters associated with this message and call your technical support representative for assistance."
"GT64010","1","UNAVAILABLE","DMA interrupt stalled, restarted engine %d","The driver timed out waiting for completion of DMA task. The DMA engine has been restarted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GT64010","3","UNAVAILABLE","Attempt to install already installed timer %d","An attempt was made to initialize a timer element that is already in use.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GT64010","3","UNAVAILABLE","Interrupt error, c=%#x, m=%#x, rc=%#x","An unexpected interrupt was registered from a DMA engine that was not initialized by software.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GT64010","3","UNAVAILABLE","Interrupt error, c=%#x, m=%#x, rc=%#x","An unexpected timer interrupt was received from a timer element that was not initialized by software.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GT64010","3","UNAVAILABLE","Referencing unused DMA channel %d","An access to an uninitialized DMA engine was attempted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GT64120","3","UNAVAILABLE","%d single bit memory errors corrected by the system","The system has seen so many single bit errors.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GT96100","1","UNAVAILABLE","DMA interrupt stalled, restarted engine %d","The driver timed out waiting for completion of DMA task. The DMA engine has been restarted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GT96100","3","UNAVAILABLE","Attempt to install already installed timer %d","An attempt was made to initialize a timer element that is already in use.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GT96100","3","UNAVAILABLE","CPU corrected %d single bit memory errors","The system has seen so many single bit errors.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GT96100","3","UNAVAILABLE","Interrupt error, c=%#x, m=%#x, rc=%#x","An unexpected interrupt was registered from a DMA engine that was not initialized by software.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GT96100","3","UNAVAILABLE","Interrupt error, c=%#x, m=%#x, rc=%#x","An unexpected timer interrupt was received from a timer element that was not initialized by software.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GT96100","3","UNAVAILABLE","Referencing unused DMA channel %d","An access to an uninitialized DMA engine was attempted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GTP","0","UNAVAILABLE","GSN: %i, TEID: %x, APN: %s, Reason: %s","A PDP context activation failed at the packet parsing state for one of the following reasons: 1. Mandatory IE is missing in the PDP . 2. Mandatory IE incorrect - Mandatory IE has invalid range of value. 3. Mandatory IE out of sequence - The Mandatory IEs are not in sequence. 4. Invalid message format. 5. Optional IE incorrect - Optional IE present in the packet has invalid range of value. 6. Version not support - The GGSN Node does not support the GTP version recieved. 7. Non-charging msg in charging path. 8. Charging msg in GTP path. 9. Unknown GTP message. 10.Message too short - GTP message received is too short to contain all expected inform IE. 11.Unexpected message seen.","Copy the error message exactly as it appears, and report to your technical support representative."
"GTP","0","UNAVAILABLE","GSN: %i, TID: %x%x, APN: %s, Reason: %s","A PDP context activation failed at the packet parsing state for one of the following reasons: 1. Mandatory IE is missing in the PDP . 2. Mandatory IE incorrect - Mandatory IE has invalid range of value. 3. Mandatory IE out of sequence - The Mandatory IEs are not in sequence. 4. Invalid message format. 5. Optional IE incorrect - Optional IE present in the packet has invalid range of value. 6. Version not support - The GGSN Node does not support the GTP version recieved. 7. Non-charging msg in charging path. 8. Charging msg in GTP path. 9. Unknown GTP message. 10.Message too short - GTP message received is too short to contain all expected inform IE. 11.Unexpected message seen.","Copy the error message exactly as it appears, and report to your technical support representative."
"GTP","0","UNAVAILABLE","GSN: %i, TID: %x%x, APN: %s, Reason: %s","Available resources exhausted to continue GGSN service because of the following reasons : 1. Number of pending signaling messages reaches limit. 2. Out of Memory - Insuffient in GGSN. 3. System failure - Permenant system failure has occured.","1. Check whether you can increase number of PDP that can be handled by GGSN. If the problem recurs , contact your technical support representative with the error message you got and with the output of 'show gprs gtp status'."
"GTP","2","UNAVAILABLE","GSN service %s changed state to %s","SGSN service starts or shutdown","If this message recurs, contact your technical support representative."
"GTP","2","UNAVAILABLE","GTP PDP activation/update failed, GSN: %i, TEID: %x, Reason: %s","A PDP context activation failed","If this message recurs, contact your technical support representative."
"GTP","2","UNAVAILABLE","GTP PDP activation/update failed, GSN: %i, TID: %x%x, Reason: %s","A PDP context activation failed","If this message recurs, contact your technical support representative."
"GTP","3","UNAVAILABLE","APN: %s, Reason: %s","A required configuration is missing","Please make sure the missing commands are configured"
"GTP","4","UNAVAILABLE","GSN: %i, TID: %x%x, APN: %s, Reason: %s","GGSN has recieved PDP update request with different Recovery Information Element in the same path.","Contact your technical support representative with the error messages you got."
"GTP","6","UNAVAILABLE","GSN: %i, TID: %x%x, APN: %s, Reason: %s","PDP context purged because of PDP context idle timeout","This is purely informational"
"GULF2488","3","UNAVAILABLE","gulf2488 channel provisioning failed (slice:%d ch:%d): %s","required resources unavailable.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GULF2488","3","UNAVAILABLE","gulf2488 channel unprovisioning failed (slice:%d ch:%d): %s","required resources unavailable.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"GULF2488","3","UNAVAILABLE","gulf2488 chip initialization failed (errcode=%d): %s","required resources unavailable.","Reinsert the linecard. If still fails, do 'test cwtlc show seeprom red', swap hardware, and Copy the error message exactly as it appears, and report it to your technical support representative."
"G_QOS_CLASSIFY","3","NOMEM","Memory Allocation Failure - [chars]","Memory required to service one or more Network Processors could not be allocated.","This error may indicate that more memory must be installed on the affected card or platform in order to service all the features and related entities enabled via the configuration. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"G_QOS_CLASSIFY","3","QOS_CONFIG","error detected: [chars]","A QoS policymap classification configuration error was detected.","This configuration error is not considered fatal to the operation of the Network Processors. The software is designed to detect and report the error condition. Change the QOS Policymap Filter configuration to correct the problem."
"G_QOS_CLASSIFY","4","MACACL_CONFIG","[chars]","Only source mac address in extended named MAC ACL is supported on X40G linecard interfaces.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"GT96100","3","ECC","CPU corrected [dec] single bit memory errors","The system has detected and corrected single-bit errors. The number of errors is displayed in the message text.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA","2","UNAVAILABLE","%d linecard(s) not quiesced exceeds limit of %d, all slots will be reloaded.","This is a cutover notice about a High Availability System linecard error condition. The linecard(s) did not quiesce properly. Within the current configuration, the number of errors detected requires the system to do a full reload of all of the linecards.","If you OIR removed the active RSP or have legacy IPs installed in the system this message is normal. Otherwise, copy the notice exactly as it appears. Check both the active system and standby system for messages. Call your technical support representative for assistance."
"HA","2","UNAVAILABLE","%s %s","This is a critical error message about a High Availability System interprocess communication status or condition. A message of this type indicates that an interprocess communication failure occurred between the active system and the standby system.","Copy the notice exactly as it appears. Check both the active system and standby system for messages. Call your technical support representative for assistance."
"HA","2","UNAVAILABLE","%s","This is a critical error message about a High Availability System cutover status or condition. A message of this type indicates that a critical failure occurred during cutover of the standby system to the active system. Messages of this type indicate that the active system relinquished system control that the standby system failed to properly take over as the active.","Copy the notice exactly as it appears. Check both the active system and standby system for messages. Call your technical support representative for assistance."
"HA","2","UNAVAILABLE","%s","This is a critical error message about a High Availability System initilization status or condition. A message of this type indicates that a failure occured during high availability system initialization.","Copy the notice exactly as it appears. Check both the active system and standby system for messages. Call your technical support representative for assistance."
"HA","2","UNAVAILABLE","%s","This is an important High Availability System notice logging the state of a system cutover of the standby system to the active system. Messages of this type indicate that the active system reliquished system control and that the standby system is taking over as active.","If the message is due to a failure condition, copy the notice exactly as it appears. Check both the active system and standby system for messages. Call your technical support representative for assistance. If the message is not due to a failure condition, no action is required."
"HA","2","UNAVAILABLE","CCB playback failed.","This is a critical error message about a High Availability System status or condition.","Copy the notice exactly as it appears. Check both the active system and standby system for messages. Call your technical support representative for assistance."
"HA","2","UNAVAILABLE","CCB record failed.","This is a critical error message about a High Availability System status or condition.","Copy the notice exactly as it appears. Check both the active system and standby system for messages. Call your technical support representative for assistance."
"HA","2","UNAVAILABLE","Slot %d did not quiesce, it will be disabled and then reloaded.","This is a cutover notice about a High Availability System linecard error condition. The linecard did not quiesce properly.","This message is normal if the slot contains a legacy IP. Otherwise, copy the notice exactly as it appears. Check both the active system and standby system for messages. Call your technical support representative for assistance."
"HA","3","UNAVAILABLE","%s","This is a error message about a High Availability System state syncronization error status or condition.","Copy the notice exactly as it appears. Check both the active system and standby system for messages. Call your technical support representative for assistance."
"HA","3","UNAVAILABLE","%s","This is a error message about a High Availability System status or condition.","Copy the notice exactly as it appears. Check both the active system and standby system for messages. Call your technical support representative for assistance."
"HA","3","UNAVAILABLE","RF event not processed till %d milliseconds. Code = %d","The event sent to the redundancy facility was not processed till the specific time delay.","Copy the notice exactly as it appears. Check both the active system and standby system for messages. Call your technical support representative for assistance."
"HA","3","UNAVAILABLE","Tif number %d (Card Type %x, (S)PA Type %x) already allocated in the Standby (Hash Index %llx) - Standby Reloading","An error was encountered in reserving the TIF (Channel ID) number meant for a specifc physical/logical interface in the standby route processor. This occurs if there is a race condition in the synchronization of TIF numbers and the running configuration from the active route processor to the standby route processor. In most situations, this error is self-correcting.","This error affects the standby route processor only. Upon encountering this error, standby route processor reloads itself automatically and reestablishes synchronization with the active route processor. If the standby does not reload itself automatically, reload it from the active route processor console by entering the how-module standby reload command. If this command fails, reload the standby by entering the hw-module standby reset command.If the standby route processor still does not reload or this error is seen again, collect the output from show c7300, show c7300 ha tif entries, show c7300 ha statistics, show c7300 ha registers, show redundancy, show redundancy state, show redundancy switchover history, show redundancy history, and show checkpoint clients. Also, copy the running configuration and the system messages exactly as they appear on the console or in the system log. Contact your Cisco technical support representative and provide the representative with the gathered information."
"HA","3","UNAVAILABLE","Tifkey %llx (Card Type %x, (S)PA Type %x) not present in the Standby Tif table (Hash Slot %d) - Standby Reloading","The standby route processor encountered an error in the reception of the TIF number (channel ID) for the indicated interface from the active route processor. In most situations, this error is self-correcting.","This error affects the standby route processor only. Upon encountering this error, standby route processor reloads itself automatically and reestablishes synchronization with the active route processor. If the standby does not reload itself automatically, reload it from the active route processor console by entering the how-module standby reload command. If this command fails, reload the standby by entering the hw-module standby reset command.If the standby route processor still does not reload or this error is seen again, collect the output from show c7300, show c7300 ha tif entries, show c7300 ha statistics, show c7300 ha registers, show redundancy, show redundancy state, show redundancy switchover history, show redundancy history, and show checkpoint clients. Also, copy the running configuration and the system messages exactly as they appear on the console or in the system log. Contact your Cisco technical support representative and provide the representative with the gathered information."
"HA","4","DATADESCR_DECODE_ERROR","Failed to decode descriptor %d %u %u %u %d","Data descriptors are used to encode an interface index in a compact fashion for transfer to another RP. An interface corresponding to the if_index was not found on the Standby RP. HA synchronization will fail for that interface","If this error recurs, then issue the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information."
"HA","4","UNAVAILABLE","%s (rc %d, event %s)","Failure to send UNIX checkpointing data.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA","4","UNAVAILABLE","%s","An error was encountered in a data sync operation","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA","4","UNAVAILABLE","%s","This is a warning message about a High Availability System status, condition, or event.","Copy the notice exactly as it appears. Check both the active system and standby system for messages. Call your technical support representative for assistance."
"HA","4","UNAVAILABLE","Creation of %s process failed","Creation of a platform high availability process failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA","4","UNAVAILABLE","Data Encode - %s (%s)","Failure to encode 7300 checkpointing data descriptors.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA","4","UNAVAILABLE","Data decode - %s (%d)","Failure to decode 7300 checkpointing data descriptors.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA","4","UNAVAILABLE","Failed to allocate buffer for inter-RP IPC message receive","An error was encountered in the reception of IPC messages from the peer Route Processor because a packet buffer to receive the packet could not be allocated.","The 'show buffers' command can be used to confirm that the IPC buffer pool is suffering misses. Intermittent errors will be handled by the IPC mechanism of retries. However, if this error message is seen with regularity, the system may need to be upgraded to have more memory as the IPC buffer pool is automatically sized in direct proportion to the total amount of memory in the system. Note that there is no configuration command to resize the IPC buffer pool."
"HA","4","UNAVAILABLE","Failed to decode descriptor %d %u %u %u %d","Data descriptors are used to encode an interface index in a compact fashion for transfer to another RP. An interface corresponding to the if_index was not found on the Standby RP. HA synchronization will fail for that interface","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.."
"HA","4","UNAVAILABLE","Incompatible RP (%s) in slot %d - Peer RP being held in reset state","The peer Route Processor (RP) is not compatible with the active RPand so it will be held in reset state.","The peer RP must be removed and replaced with a RP that is the same type as the active RP to have it successfully boot as the standby."
"HA","4","UNAVAILABLE","Initialization of standby Route Processor in slot %d failed","The initialization of the standby route processor failed. This will result in the high availability features not being operational.","If additional error messages indicate that the type of the standby RP is incompatible with the current active RP, then that should be fixed by inserting a compatible standby RP. If the standby RP is of a type that is compatible with the active RP, then an attempt should be made to remove and firmly re-insert the standby RP. If the problem persists, please contact your Cisco technical support representative with this information."
"HA","4","UNAVAILABLE","Platform CF - %s","Failure in some 7300 checkpointing activity.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA","4","UNAVAILABLE","Platform CF - %s","Failure in some UNIX checkpointing activity.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA","4","UNAVAILABLE","Reset of %s RP triggered %s","Reset of the active RP was triggered by the standby RP in response to some event that caused the standby RP to conclude that the active RP was no longer functional.","The crashing route processor (RP) will produce a crashinfo file and a core dump if that was configured. These files provide information about the events that triggered the RP to reset. Contact your Cisco technical support representative with this information."
"HA","4","UNAVAILABLE","Unable to lock the configuration session.","This is a warning message indicating that the configuration session could not be locked. Simultaneous configuration sessions can corrupt the configuration.","Copy the message exactly as it appears. Check both the active system and standby system for messages. Call your technical support representative for assistance."
"HA","5","UNAVAILABLE","%s","This is a notice message about a High Availability System status, condition, or event.","No action required."
"HA","5","UNAVAILABLE","%s","This is a notice message about a High Availability System syncronization status, condition, or event.","No action required."
"HA","5","UNAVAILABLE","%s hw-module slot %d image %s : %s","This is a notice message about a High Availability System hardware module configuration status, condition, or event.","Copy the notice exactly as it appears. Check both the active system and standby system for messages. Call your technical support representative for assistance."
"HA","5","UNAVAILABLE","Active HA version (%u.%u) differs from standby HA version (%u.%u)","This is a notice about High Availablility System version mismatch between the active and standby systems.","No action required."
"HA","5","UNAVAILABLE","Active IOS version differs from standby IOS version","This is a notice about High Availablility System version mismatch between the active and standby systems.","No action required."
"HA","5","UNAVAILABLE","Maximum sync retries exceeded. Reloading standby and cancelling sync.","This is a notice message about a High Availability System syncronization status, condition, or event. The syncronization operation failed.","Copy the notice exactly as it appears. Check both the active system and standby system for messages. Call your technical support representative for assistance."
"HA","5","UNAVAILABLE","Operating mode is %s, %smode is %s.","This is a notice about the High Availablility System mode.","Make sure that both the active system and standby systems are correctly configured and operational."
"HA","5","UNAVAILABLE","Reloading standby and retrying sync operation (retry %d).","This is a notice message about a High Availability System syncronization status, condition, or event. The syncronization operation will be retried.","No action required."
"HA","5","UNAVAILABLE","Unable to reload the standby. %s","The active RSP was unable to reload the standby because of the reason indicated in the message. This may be because the slave is in unplugged state, or because there is a redundancy forced switchover process in progress, or because the reload function is incorrectly called from the standby to the active.","If the message says Standby (slave) is unplugged, verify that the slave is properly seated in the chassis. If the message says Switchover is in progress, it means that currently a switchover is in progress, and no action is necessary. If you are getting the message Standby cannot reload the Active, then run the show logging and show tech-support commands and report the error to your Cisco technical support representative and provide him with the output of the commands."
"HA","6","FALLBACK","[chars] - configured mode([chars]), fallback mode([chars])","The specified route processor redundancy mode has fallen back to the mode specified in the message.","No action is required."
"HA","6","NOCOEXIST","Line card in slot [dec] ([chars]) cannot co-exist in [chars] redundancy mode","The specified line card cannot coexist with the rest of the system in the current redundancy mode configuration of the system.","No action is required."
"HA","6","STANDBY_READY","Standby RP in slot [dec] is operational in [chars]modeThe standby route processor is operational.Recommended Action    No action is required.Error Message    %HA-6-SWITCHOVER: Route Processor switched from being standby to being active","This route processor has switched over to become the active route processor.","No action is required."
"HA","6","TOOBIG","Running config too big, config sync failed","The running configuration was too large to be synchronized.","No action is required."
"HA_CLIENT","3","RF_REG_FAILED","RF registration for the %s HA client failed with return code %u","The specified HA client failed to register properly with the Redundancy Facility (RF). This should not happen and suggests a software problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_CONFIG_SYNC","3","BOOTVAR","Cannot communicate boot variable to standby (%s)","The active supervisor failed to send the specified boot variable to the standby supervisor. As a result, a subsequent reload or a switchover operation will probably result in the standby supervisor booting a wrong image.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_CONFIG_SYNC","3","CONFREG","Cannot communicate config register to standby","The active supervisor failed to send the configuration register to the standby supervisor. As a result, the active and standby supervisors might not have matching configuration registers.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_CONFIG_SYNC","3","FS_BULK_CFGSYNC","%s [%s]","A synchronization of the file system bulk configuration has failed. The reason for the failure is provided in the string.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_CONFIG_SYNC","3","ISSU_MTU","CONFIG SYNC Failed to get MTU Size for session[[dec]] msg_type[[dec]], MTU[[dec]], rc[[dec]]","An ISSU configuration synchronization failed to get the message MTU.","Copy the system's configuration along with any other relevant information. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_CONFIG_SYNC","6","BULK_CFGSYNC_SUCCEED","Bulk Sync succeeded","A bulk synchronization has succeeded.","No action is necessary."
"HA_CONFIG_SYNC","6","LBL_PRC_SUBCODE","CONFIG SYNC : Subcode not matching for command %s Active subcode[0x%x], Standby subcode[0x%x]","The line-by-line synchronization of a command has succeeded. A command entered on the active system was successfully synchronized with the standby system. However, the subcode of parser return code returned by the active system differed from the subcode returned by the standby system.","Normally, no action is required. If any problems with line-by-line synchronization are found, copy the system's configuration along with any other relevant information. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","ACTION_CNS_OPEN_FAIL","[chars]: Unable to open connection to CNS Event Agent: [dec]","The Cisco Network Services (CNS) action process failed to open a CNS handle to the event agent.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMC_CBH_PROCESS_CREATE","[chars]: callback handler process create failed for eid: [dec]","The process create function reported an error while trying to create the callback handler process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMC_FH_INIT","[chars]: fh_init failed : [dec]","The fh_init function reported an error while trying to initialize EEM for a callback process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_ACTION_INFO","[chars]: Error occurred while fetching action information: [dec].","The Embedded Event Manager Policy Director failed to gather action information registered for the event.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_ADJUST_HIST_SIZE","[chars]: Error attempting to adjust event history table size.","The Embedded Event Manager policy director could not adjust the size of the event history table.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_ACTION_NOTRACK","%s: unable to set state for tracking object number %u; object does not exist or is not a stub-object.","The Embedded Event Manager applet attempted to set the state of a tracking object that does not exist.","Only set the state of tracking objects that have already been configured in the system. If the message continues to occur, copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","FMPD_CHECKSUM_MISMATCH","%s: file checksum mismatch","The checksum value of an installed policy does not match the value provided by the installation manager.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMFD_EMPTY_QUEUE","[chars]: The [chars] event detector I/O queue empty.","The I/O queue is unexpectedly empty.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_ERROR","Error executing applet %s statement %s","The Embedded Event Manager policy director found an error when processing an applet.","Check syntax of applet statement. If the message continues to occur, copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","FMPD_EXECUTE_CALLBACK","%s: failed to execute callback","Failed to execute callback routine.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_FH_INIT","%s: could not initialize Embedded Event Manager service: %s","An internal error was detected when initializing Embedded Event Manager service.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_IPC_PORT_CREATE","%s: failed to create an IPC port: %s","Embedded Event Manager failed to create an IPC port.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_IPC_PORT_OPEN","%s: failed to open an IPC port: %s","Embedded Event Manager failed to open an IPC port.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","FMPD_IPC_PORT_REGISTER","%s: failed to register an IPC port: %s","Embedded Event Manager failed to register an IPC port.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_NOEID","%s: No such event id found.","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_NOESID","%s: No such event spec id found.","The Embedded Event Manager Policy Director could not find the event for the event spec. ID.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_NO_PROC","%s: Failed to create process","The process create function reports an error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMFD_OID_UNAVAIL","%s: The following oid has become unavailable: %s","The registered oid is no longer available in the system.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_PROCESS_XML","%s: error processing xml buffer","An error occurred processing the event publish information xml buffer.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_QUEUE_INIT","%s: could not initialize queue","An internal error was detected when initializing Embedded Event Manager queue.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMFD_QUEUE_INIT","[chars]: Unable to initialize queue;","The queue initialization function reported an error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMFD_TTY_NUM","[chars]: Error occurred while fetching TTY number.","An internal software error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_ACTION","[chars]: Error occurred while performing action: [chars].","An internal software error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_CHECKSUM_MISMATCH","[chars]: file checksum mismatch","The checksum value of a an installed policy does not match the value provided by the installation manager.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_CHKPT_INIT","[chars]: could not register the application with the checkpointing server: [chars]","Failed to register an application with the checkpointing server.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_CHKPT_TBL_INFO_READ","[chars]: could not read the existing table information: [chars]","Failed to read the existing table information using the checkpointing API.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_CHKPT_TBL_INIT","[chars]: failed to initialize [chars]: [chars]","Could not initialize a table with the checkpointing server.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_CHKPT_TBL_RECOVER","[chars]: could not recover the checkpointed [chars]: [chars]","Failed to recover a checkpointed table.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_CLI_CONNECT","Unable to establish CLI session: [chars]","Unable to establish a CLI session.","This is an informational message only. No action is required."
"HA_EM","3","FMPD_CLI_DISCONNECT","Error disconnecting from CLI session: [chars]","An error occurred while disconnecting from the CLI session.","This is an informational message only. No action is required."
"HA_EM","3","FMPD_CLI_NOTTY","Error attempting to access an unopened CLI session: [chars]","An error occurred while the system attempted to access the specified unopened CLI session.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_CLI_READ","Unable to read CLI response: [chars]","Unable to read a CLI response.","This is an informational message only. No action is required."
"HA_EM","3","FMPD_CLI_WRITE","Unable to send CLI command: [chars]","Unable to send a CLI command.","This is an informational message only. No action is required."
"HA_EM","3","FMPD_ERROR","Error executing applet [chars] statement [chars]","The Embedded Event Manager policy director found an error when processing an applet.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_EVM_ASYNC_ATTACH","[chars]: could not attach handler for Event Manager asynchronous event: [chars]","An internal error was detected when attaching a handler for an Event Manager asynchronous event.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_EVM_CREATE","[chars]: could not create event manager: [chars]","An internal error was detected when creating Event Manager.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_EVM_EVENT_BLOCK","[chars]: failed to block waiting for Event Manager events: [chars]","An internal error was detected when block-waiting for Event Manager events.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_EVM_INIT_EVENT","[chars]: could not initialize Event Manager event: [chars]","An internal error was detected when initializing an Event Manager event.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_EVM_MSG_ATTACH","[chars]: could not attach handler for Event Manager message event: [chars]","An internal error was detected when attaching a handler for an Event Manager message event.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_EXECUTE_CALLBACK","[chars]: failed to execute callback","Failed to execute a callback routine.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_FH_INIT","[chars]: could not initialize Embedded Event Manager service: [chars]","An internal error was detected when initializing the Embedded Event Manager service.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_GET_PRIO","[chars]: failed to get process priority: [chars]","There has been an internal error. A call to get a process-scheduling priority failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_IPC_PORT_CREATE","[chars]: failed to create an IPC port: [chars]","Embedded Event Manager failed to create an IPC port.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_IPC_PORT_OPEN","[chars]: failed to open an IPC port: [chars]","Embedded Event Manager failed to open an IPC port.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_IPC_PORT_REGISTER","[chars]: failed to register an IPC port: [chars]","Embedded Event Manager failed to register an IPC port.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_NOEID","%s: No such event id found.","The Embedded Event Manager (EEM) policy director could not find a record of the event ID.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_NOESID","[chars]: No such event spec id found.","The Embedded Event Manager policy director could not find the triggered event specification ID.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_NO_PROC","%s: Failed to create process","The Embedded Event Manager (EEM) policy director could not create a process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_OVL_NOTIF_REG","[chars]: could not register for Version Manager notification: [chars]","An internal error was detected when registering for Version Manager notification.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_POLICY_UNREG_ERR","[chars]: could not unregister policy [chars]: [chars]","A registered policy changed or deleted by the last installation update was detected. Because the update used the start option, the old policy was automatically unregistered. This message signaled an unsuccessful unregistration.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_POLICY_UNREGREG_ERR","[chars]: could not replace policy [chars]: [chars]","A registered policy changed by the last installation update was detected. Because the update used the start option, the old policy was automatically replaced by the new policy. This message signaled an unsuccessful replacement of the policy.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_PROCESS_XML","%s: error processing xml buffer","An error occurred in processing the event publishing information XML buffer.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_PTHRD_CREATE","[chars]: failed to create POSIX thread: [chars]","An internal error occurred when trying to create a POSIX thread.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_QUEUE_INIT","[chars]: could not initialize queue","An internal error was detected when initializing the Embedded Event Manager queue.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_REQINFO","[chars]: Error attempting to fetch event information: [chars].","The Embedded Event Manager policy director could not obtain event information.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_SET_INFO","[chars]: Error occurred while fetching variable information: [dec].","An error occurred while attempting to obtain Embedded Event Manager variable information.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_SMTP_CHK_REPLY","Reply code unexpected from SMTP server: [chars]","An unexpected reply code was received from the connected SMTP server.","This is an informational message only. No action is required."
"HA_EM","3","FMPD_SMTP_CONNECT","Unable to connect to SMTP server: [chars]","Unable to connect to the SMTP server socket.","This is an informational message only. No action is required."
"HA_EM","3","FMPD_SMTP_DISCONNECT","Unable to disconnect from SMTP server: [chars]","Unable to disconnect from the connected SMTP server.","This is an informational message only. No action is required."
"HA_EM","3","FMPD_SMTP_READ","Unable to read from SMTP server: [chars]","Unable to read from the connected SMTP server.","This is an informational message only. No action is required."
"HA_EM","3","FMPD_SMTP_WRITE","Unable to write to SMTP server: [chars]","Unable to write to the connected SMTP server.","This is an informational message only. No action is required."
"HA_EM","3","FMPD_SVCEVM_CREATE","[chars]: could not initialize RPC server for event manager: [chars]","Initializing RPC server stub for event manager has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_SVC_REG","[chars]: RPC service registration for Embedded Event Manager Script Director failed","Embedded Event Manager Script Director failed to register with the RPC facility.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_UNKNOWN_ENV","[chars]: could not find environment variable: [chars]","The Embedded Event Manager policy director could not find the environment variable specified in the action message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_UNKNOWNTYPE","[chars]: Unknown event type found in applet.","The Embedded Event Manager applet had an unknown event type.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMPD_UNKNOWN_ENV","%s: could not find environment variable: %s","The Embedded Event Manager policy director could not find the environment variable specified in the action message.","Only use well known Embedded Event Manager environment variables. If the message continues to occur, copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","FMPD_WRONGTYPE","[chars]: Published event type does not match event spec","The Embedded Event Manager policy director event specification does not match the published event.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMS_CNS_FAIL","[chars]: Failed to perform CNS action: [chars]","The Embedded Event Manager failed attempting to send a CNS message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMS_EMPTY_QUEUE","[chars]: The I/O queue empty.","The I/O queue is empty, but it should not be empty.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMS_ENQUEUE_FAIL","[chars]: The Unable to enqueue packet onto queue.","The queue is not in a state to accept packets.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMS_OPEN","%s: Unable to open %s; %s","The open function reported an error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMS_POLICY_CHECKSUM","%s: Checksum error for policy %s - this policy will not be run","The checksum computed for the specified policy does not match the original checksum computed when the policy was registered.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMS_POLICY_HASH","%s: The hash computation routine reported an error; %s","The fh_hash_md5_fd() function reported the specified error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMS_POLICY_LOOKUP_FAIL","[chars]: Failed to look up in the table the registration specification for policy [chars].","A table lookup for the registration specification for the policy has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMS_QUEUE_INIT","[chars]: The Unable to initialize queue.","The queue cannot be initialized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","FMS_SWITCH_NOT_RF_ACTIVE","[chars]: This processor is not in ACTIVE state (state = [dec]). Switchover must be performed on ACTIVE processor.","Switchovers must occur on the active unit, not the standby unit.","Ensure that the switchover occurs on a unit that is designated as an active unit and not a standby unit."
"HA_EM","4","FMPD_EVENT_CREATE","%s: failed to create an event: %s","Failed to create an Embedded Event Manager event.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","4","FMPD_EVENT_REG","%s: failed to register an event: %s","Failed to register an Embedded Event Manager event.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","4","FMPD_IPC_GET_PAK","[chars]: failed to allocate an IPC buffer","Embedded Event Manager failed to allocate a buffer from IPC.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","4","FMPD_IPC_SEND_MSG","[chars]: failed to send an IPC message: [chars]","Embedded Event Manager failed to send a message through IPC.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","4","FMPD_NO_ACTION","No action configured for applet [chars]","No action has been configured for the specified applet.","Configure at least one action for this applet."
"HA_EM","4","FMPD_NO_EVENT","No event configured for applet [chars]","No event has been configured for the specified applet.","Configure an event for this applet."
"HA_EM","4","FMPD_NOTAGNAME","%s: No tag %s found corresponding to this event publish.","The Embedded Event Manager policy director could not associate the tag name with a published event.","In the action info type event reqinfo command, use only tag names that correspond to the published event."
"HA_EM","4","FMPD_NO_TRACK","Use of the 'track' keyword in the correlate statement is not supported in this image. All tracked objects will return the 'unset' state of 0","The Embedded Event Manager Track ED is not supported in this image.","If you require Embedded Event Manager Track ED, upgrade to an image that supports the feature."
"HA_EM","6","FMPD_CONTEXT_RETRIEVE","Failed to retrieve context for key %s: %s","Failed to context retrieve variable information for event.","Ensure context information with the given key is saved. If the message continues to occur, copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","6","FMPD_CONTEXT_SAVE","Failed to save variable context for key %s: %s","Failed to context save variable information for event.","Ensure context information with the same key is not already saved. If the message continues to occur, copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","6","FMPD_DIVIDE_ZERO","Invalid operand in arithmetic division, cannot divide by zero","Arithmetic division does not allow divide by zero.","Ensure denominator provided to division action is non-zero."
"HA_EM","6","FMPD_EEM_CONFIG","Embedded Event Manager configuration: %s","The Embedded Event Manager (EEM) reports an error in the Event Manager (EM) configuration.","Check the EEM applet or policy configuration"
"HA_EM","6","FMPD_OPERAND_INVALID","Invalid operand in action, expected value within range %ld to %ld, received: %s","Arithmetic actions only accept valid long integer values.","Ensure value provided to action is long integer."
"HA_EM","6","FMPD_POLICY_CHANGED","[chars]: registered policy [chars] changed by the last installation update","A registered policy was changed by the last installation update. If the update used the start option, the old policy was automatically unregistered and the new policy registered. Otherwise, the old policy would remain registered and functional until the user unregisters it manually.","This is an informational message only. No action is required."
"HA_EM","6","FMPD_POLICY_DELETED","[chars]: registered policy [chars] deleted by the last installation update","A registered policy was deleted by the last installation update. If the update used the start option, the policy was automatically unregistered. Otherwise, the policy would remain registered and functional until the user unregisters it manually.","This is an informational message only. No action is required."
"HA_EM","6","FMPD_POLICY_UNREGREG_SUCC","[chars]: policy [chars] replaced successfully","A registered policy changed by the last installation update was detected. Because the update used the start option, the old policy was automatically replaced by the new policy. This message signaled a successful replacement of the policy.","This is an informational message only. No action is required."
"HA_EM","6","FMPD_POLICY_UNREG_SUCC","[chars]: policy [chars] unregistered successfully","A registered policy changed or deleted by the last installation update was detected. Because the update used the start option, the old policy was automatically unregistered. This message signaled a successful unregistration.","This is an informational message only. No action is required."
"HA_EM","6","FMPD_REGCOMP","Error compiling regular expression: %s","An error was encountered when compiling the given regular expression.","Check syntax of regular expression pattern. If the message continues to occur, copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","6","FMPD_SWITCH_HARDWARE","%s: Policy has requested a hardware switchover","An Embedded Event Manager policy requested that a hardware switchover occur.","No action is required."
"HA_EM","6","FMPD_UPDATE_POLICY_COPY","Policy update has copied %d bytes from %s to %s","As a result of an event manager update command, an Embedded Event Manager (EEM) policy has been copied.","No action is required."
"HA_EM","6","FMPD_UPDATE_POLICY_REGISTER","Policy update has successfully re-registered policy %s","As a result of an event manager update command, an EEM policy has been successfully reregistered.","No action is required."
"HA_EM","6","FMPD_UPDATE_POLICY_REGISTER_FAIL","Policy update has failed to register policy %s %s","As a result of an event manager update command, an EEM policy could not be registered.","No action is required."
"HA_EM","6","FMPD_UPDATE_POLICY_UNREGISTER_FAIL","Policy update has failed to unregister policy %s %s","As a result of an event manager update command, an EEM policy could not be unregistered.","No action is required."
"HA_EM","6","FMS_MODIFY_POLICY","%s: unable to modify the policy to class %s: scheduling rule unavailable.","There is no scheduler rule configured to service this event class.","Please configure a scheduler rule before modifying the event."
"HA_EM","6","FMS_SWITCH_HARDWARE","[chars]: Policy has requested a hardware switchover","An Embedded Event Manager policy requested that a hardware switchover occur.","This is an informational message only. No action is required."
"HA_EM","7","ACTION_ADD_PARSER","[chars]: Unable to add action [chars] command;","Failed to add the specified action command.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","ACTION_CNS_AGENT_UNAVAIL","[chars]: CNS Event Agent not available: [dec]","The CNS Event Agent is currently not available.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","ACTION_CNS_CLEAR_RESTART","[chars]: Unable to clear restart callback;","The CNS action process failed to clear restart callback.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","ACTION_CNS_SET_RESTART","[chars]: Unable to set restart callback;","The CNS action process failed to set restart callback.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","ACTION_ENQUEUE_FAIL","[chars]: Unable to enqueue [chars];","The enqueueing function reported an error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","ACTION_WB_CREATE","[chars]: create_watched_boolean failed: [chars]","The create_watched_boolean function reported an error trying to create the watched boolean.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","ACTION_WB_DELETE","[chars]: delete_watched_boolean failed: [chars]","The delete_watched_boolean function reported an error trying to delete the watched boolean.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMC_CB_DM_THREADPOOL_CREATE","[chars]: dispatch_manager_threadpool_create failed [chars]","The dispatch manager reported an error trying to create a thread pool.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMC_CB_DM_THREADPOOL_START","[chars]: dispatch_manager_threadpool_start failed [chars]","The dispatch manager reported an error trying to start a thread pool.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMC_ENQUEUE_FAIL","[chars]: Unable to enqueue [chars];","The enqueueing function reported an error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMC_INV_REPLY","[chars]: Application client library unable to handle message receive.","The API received a message reply when it was not in a state to accept such messages.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMC_MALLOC","[chars]: Unable to allocate [chars];","The malloc function reported an error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMC_REG_CBH_PULSE","%s: Unable to locate reg callback entry for pulse code %d","The registration callback handler was unable to validate the pulse code received.","The pthread_create function reported an error."
"HA_EM","7","FMC_REG_CBH_SEND","%s: Unable to send response for FH_MSG_CALLBACK_DONE %s","The registration callback handler was unable to send the FH_MSG_CALLBACK_DONE message to the Embedded Event Manager Server.","The pthread_create function reported an error."
"HA_EM","7","FMFD_ADD_PARSER","[chars]: Unable to add [chars] event detector command;","The event detector failed to add a command.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMPD_CHKPT_ITERATE_END","[chars]: call to chkpt_iterate_end returned unexpected failure.","An attempt to register an application with the checkpointing server has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMPD_CHKPT_NULL_PTR","[chars]: Got a null [chars] but non-null value was expected","An attempt to do further processing has failed because a null value was received when a non-null value was expected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMPD_CHKPT_TBL_ADD","[chars]: could not save a record into a checkpointing table: [chars]","An attempt to save a record into the specified checkpointing table has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMPD_CHKPT_TBL_REMOVE","[chars]: could not delete a record from a checkpointing table: [chars]","An attempt to delete a record from the specified checkpointing table has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMPD_CHKPT_TBL_RESET","[chars]: could not reset a record in a checkpointing table: [chars]","An attempt to reset a record in the specified checkpointing table has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_COND_WAIT","[chars]: conditional wait error: [chars]","Internal error. The event detector has failed to perform a conditional wait.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMPD_COUNTER_SET","[chars]: failed to set a counter: [chars]","An attempt to set an Embedded Event Manager counter has failed.Error Message    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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message    %HA_EM-7-FMFD_DE_FETCH: %s: %s[%d] Explanation    Internal error. The event detector has failed to fetch a data element from the statistics data engine.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_DM_CREATE","[chars]: could not create dispatch manager: [chars]","The event detector has failed to create a dispatch manager.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_ENQUEUE_FAIL","[chars]: Unable to enqueue [chars];","The enqueueing function reported an error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMPD_EVENT_CREATE","[chars]: failed to create an event: [chars]","An attempt to create an Embedded Event Manager event has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMPD_EVENT_REG","[chars]: failed to register an event: [chars]","An attempt to register an Embedded Event Manager event has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMPD_EVENT_TYPE","[chars]: unknown event type [dec]","An unknown Embedded Event Manager event type was detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMPD_FILE_OPEN","[chars]: failed to open file [chars] : [chars]","An attempt to open the specified file has failed due to an internal error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMPD_FORMAT_TIME","[chars]: error attemting to format time string","An attempt to format a time string has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMPD_GET_NODE_NAME","[chars]: failed to get the local node name: [chars]","An attempt to get the local node name has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_HIST_QERR","%s","Internal error. The event detector has failed to get a free history list entry.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_INV_COMPARE_OP","%s: invalid comparison operator: %d","Internal error. The value comparison operator is invalid or not supported.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_INV_STATS_TYPE","%s: invalid statistics value type: %d","Internal error. The statistics data type is invalid or not supported.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_INV_TM","%s: invalid timer: type=%d, timer=%p","Internal error. The timer value is invalid or not as expected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_INV_TM_TYPE","%s: invalid timer type: %d","Internal error. The timer type is invalid or not supported.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMPD_LAST_POLICY","[chars]: invalid last policy name replied [chars]","There has been an internal error. The last policy name that the script director replied to the show event manager policy registered command is an invalid policy name.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMPD_LONG_PATHNAME","[chars]: too long path name","There has been an internal error. A path name could not be formed because it exceeded the maximum length.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_MALLOC","[chars]: Unable to allocate [chars]; [chars]","The malloc function reported an error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_MET_RBLD","%s: %s","Internal error. The event detector has failed to rebuild the metric list from the checkpointed records.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_MSGSEND_RETRY_ERR","%s: %d","The event detector has exceeded its maximum number of retries to send a pulse to the embedded event manager to notify of an event publish.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_NO_CLOCK","[chars]: unable to read clock using clock_gettime: [chars]","The clock reading function reported an error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMPD_NO_MEM","[chars]: not enough memory: [chars]","Memory allocation failed due to a low-memory condition.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"HA_EM","7","FMFD_OE_CREATE","%s: could not create an occurrence entry","Internal error. The event detector has failed to create an entry for the matched occurrence list.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_OE_REMOVE","%s: could not remove an occurrence entry","Internal error. The event detector has failed to remove an entry for the matched occurrence list.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_OID_UNAVAIL","[chars]: The following oid has become unavailable: [chars]","An internal error has occurred. The registered OID is no longer available in the system.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_OPEN_CONF","[chars]: could not open event detector config file: [chars]","The event detector has failed to open the configuration file for event detector information.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMPD_OVL_SETUP_ENV","[chars]: could not update environment variables: [chars]","Updating environment variables of the process according to stored system variables has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_PUB_TM_ALLOC","%s: Unable to allocate memory for event publish timer block","Internal error. The event detector has failed to allocate memory for the event publish timer block.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_READ_CONF","[chars]: could not read event detector config file: [chars]","The event detector has failed to read the configuration file for event detector information.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_RESOURCE_MONITOR_REGISTER_FAIL","%s: resource_monitor_register failed; return code = %d","The resource_monitor_register function reported an error trying to register for RMI notifications.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_SNMP_ADDR_ILLEGAL","%s: Illegal SNMP address type","The SNMP address is illegal.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_SNMP_ADDR_IPV6","%s: SNMP IPV6 address is not supported","The IPV6 address is not supported.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_SNMP_BUILD_PDU_FAILED","%s: SNMP build pdu failed","The SNMP pdu build has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_SNMP_COMM_FAIL","%s: Unable to create SNMP octet community string; string = %s","The community string was not able to build into a SNMP octet string","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_SNMP_ERRCODE","%s: %s","The SNMP error code.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_SNMP_MAKE_PDU_FAILED","%s: SNMP make pdu failed","The SNMP pdu make has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_SNMP_MSG_FAIL","%s: Unable to create a SNMP message; community = %s","The SNMP message failed to be created","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_SNMP_OID_INVALID","%s: Invalid SNMP oid length %d","The SNMP oid has invalid length","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_SNMP_OID_MAKE_FAIL","%s: Unable to build an oid string into a SNMP oid; oid = %s","The oid string was not able to build into a SNMP oid","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_SNMP_REQ_FAILED","%s: SNMP request failed","The SNMP request has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_SNMP_RESP_CANCEL","%s: SNMP response cancelled","The SNMP response has been cancelled.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_SNMP_RESP_ERROR","%s: SNMP response error; error_status = %d","The SNMP response has error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_SNMP_RESP_Q_EMPTY","%s: SNMP proxy exec got event, but queue is empty","The SNMP proxy got event but the queue is empty.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_SNMP_RESP_TIMEOUT","%s: SNMP response has timed out","The SNMP response has timed out.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_SNMP_UNKNOWN_TYPE","%s: Unknown SNMP operation or response type %d","The operation or response type is unknown.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_SNMP_VARBIND_FAIL","%s: Unable to create a SNMP varbind","The oid failed to make into a SNMP varbind","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMPD_SWITCH_FAIL","%s: The system is unable to switch to standby processor. Switchover cancelled.","Switchovers must occur when STANDBY is available and ready.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_THRD_POOL_CREATE","[chars]: could not create thread pool: [chars]","The event detector has failed to create a thread pool.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMPD_TIMER_ARM","[chars]: failed to arm a timer: [chars]","An attempt to arm an Embedded Event Manager timer has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMFD_TM_LEAF_NEW","%s: could not create a leaf timer","Internal error. The event detector has failed to create a managed leaf timer.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMS_ASYNC_ATTACH_CHKPT","[chars]: Failed to attach to handle chkpt asychronous events; [chars]","The event pulse attach event function reported an error trying to attach the checkpoint pulse handler.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMS_CHKPT_ITERATE_END","[chars]: call to chkpt_iterate_end returned unexpected failure.","An attempt to register an application with the checkpointing server has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMS_CHKPT_TBL_UNREG","[chars]: could not unregister the checkpointed table [chars]: [chars]","Failed to unregister a checkpointed table.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMS_FDC_ALLOCATE","%s: Failed to allocate Event Detector context control block; %s","The get_fd function reported an error trying to allocate a Event Detector context control block.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMS_FDC_OPEN","[chars]: Failed to open Event Detector context control block","The open_fd function reported an error trying to open an Event Detector context control block.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMS_GUARD_WORD_VER","%s: %s guard word corrupted; %p","The guard word for the specified control block does not contain what is expected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMS_INV_ARG_STRING","%s: Invalid argument string: %s","An invalid argument string was passed to the specified function.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMS_MALLOC","%s: Unable to allocate %s; %s","The malloc function reported an error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMS_NO_CLOCK","[chars]: unable to read clock using clock_gettime: [chars]","The clock reading function reported an error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMS_NULL_SCRIPT_NAME","%s: The script name is NULL","An invalid script name was passed as an argument into the specified function.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMS_POLICY_EXEC","%s: Policy execution %s","The Embedded Event Manager policy excution state has been changed to the state named in the message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMS_POLICY_MAX_ENTRIES","[chars]: Maximum number of script publish entries exceeded; some events have been discarded","An attempt to publish an event requiring a script failed because there is no more room in the script publish queue.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMS_REALLOC_FAIL","[chars]: Unable to reallocate [chars]; [chars]","The reallocation function reported an error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMS_STRDUP","%s: Failed to duplicate string %s; %s","The strdup function reported an error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMS_SWITCH_FAIL","[chars]: The system is unable to switch to standby processor. Switchover cancelled.","Switchovers must occur when a standby processor is available and ready.","Ensure that a standby processor is available and ready."
"HA_EM","7","FMS_WB_CREATE","[chars]: create_watched_boolean failed; [chars]","The create watched boolean function reported an error trying to create the watched boolean.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","FMS_WQ_CREATE","[chars]: create_watched_queue failed; [chars]","The create watched queue function reported an error trying to create the watched queue.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","PTHREAD_MUTEX_LOCK","[chars]: Error locking mutex [chars]; [chars]","The pthread mutex lock function reported an error while attempting to lock the specified mutex.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","PTHREAD_MUTEX_UNLOCK","[chars]: Error unlocking mutex [chars]; [chars]","The pthread mutex unlock function reported an error while attempting to unlock the specified mutex.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HAL","1","UNAVAILABLE","%s","A HAL Port Adapter was detected which has a revision earlier than rev3. This port adapter pre-dates the router platform it has been installed in, and is not a supported combination.","Upgrade to a HAL Port Adapter which is rev3 or above."
"HAL","1","UNAVAILABLE","%s could not be disabled by %s","The shutdown failed to disable the interface.","Copy the error message exactly as it appears, and report it to your technical support representative."
"HAL","1","UNAVAILABLE","%s could not be enabled by %s","The restart failed to enable the interface.","Copy the error message exactly as it appears, and report it to your technical support representative."
"HAL","1","UNAVAILABLE","%s could not be reset by %s","The restart failed to reset the interface.","Copy the error message exactly as it appears, and report it to your technical support representative."
"HAL","1","UNAVAILABLE","%s init failed at %s","HAL initialization failure.","Copy the error message exactly as it appears, and report it to your technical support representative."
"HAL","1","UNAVAILABLE","Failed to configure %d interfaces in bay %d, shutting down bay","The HAL hardware failed. Some components on the board failed to initialize.","Replace the HAL port adapter."
"HAL","1","UNAVAILABLE","Found %d interfaces in bay %d, shutting down bay","The HAL hardware failed. Some components on the board failed to initialize.","Copy the error message exactly as it appears, and report it to your technical support representative."
"HAL","1","UNAVAILABLE","Microcode to slot %d","Failed to download firmware into the HAL port adapter.","Copy the error message exactly as it appears, and report it to your technical support representative."
"HAL","1","UNAVAILABLE","Slot %d firmware init (%s)","HAL firmware initialization failure.","Copy the error message exactly as it appears, and report it to your technical support representative."
"HAL","1","UNAVAILABLE","Slot %d for microcode download","An error was detected on the communication path between VIP and HAL.","Copy the error message exactly as it appears, and report it to your technical support representative."
"HAL","2","UNAVAILABLE","%#08x %08x %08x %08x","HAL firmware crash information","Copy the error message exactly as it appears, and report it to your technical support representative."
"HAL","2","UNAVAILABLE","%s: packet received for unknown VC %d","The virtual channel encapsulation is corrupted.","Copy the error message exactly as it appears, and report it to your technical support representative."
"HAL","2","UNAVAILABLE","HAL F/W crashed in bay %d: %#x - reset","HAL firmware does not update the software watchdog.","Copy the error message exactly as it appears, and report it to your technical support representative."
"HAL","3","UNAVAILABLE","%s - Accumulator is not available","An invalid TX accumulator is detected.","Copy the error message exactly as it appears, and report it to your technical support representative."
"HAL","3","UNAVAILABLE","%s","General error information.","Copy the error message exactly as it appears, and report it to your technical support representative."
"HAL","3","UNAVAILABLE","%s packet buffer, pak=0x%x","A software or hardware error occurred. The HAL driver detected that the transmit ring is in an inconsistent and unrecoverable state.","Copy the error message exactly as it appears, and report it to your technical support representative."
"HAL","3","UNAVAILABLE","%s: failed to send %s love letter","A love letter was not sent to RSP.","Copy the error message exactly as it appears, and report it to your technical support representative."
"HAL","3","UNAVAILABLE","Failed to receive reply %d from bay %d firmware","A message was not received from HAL firmware.","Copy the error message exactly as it appears, and report it to your technical support representative."
"HAL","3","UNAVAILABLE","Failed to send msg %d to %s driver firmware","A port related message was not sent to HAL firmware.","Copy the error message exactly as it appears, and report it to your technical support representative."
"HAL","3","UNAVAILABLE","Failed to send msg %d to bay %d firmware","A message was not sent to HAL firmware.","Copy the error message exactly as it appears, and report it to your technical support representative."
"HAL","3","UNAVAILABLE","Failed to send msg %s to bay %d firmware","Specified message was not sent to HAL firmware.","Copy the error message exactly as it appears, and report it to your technical support representative."
"HAL","3","UNAVAILABLE","Received unexpected mailbox message (id = %d)","Unexpected message from HAL firmware.","Copy the error message exactly as it appears, and report it to your technical support representative."
"HAL","3","UNAVAILABLE","Slot %d device ID seen as %#x, expected %#x (Mueslix)","Failed to detect the hdlc controller on the HAL.","Replace the HAL port adaptor."
"HAL","3","UNAVAILABLE","Slot %d device ID seen as %#x, expected %#x (PLX9060)","The PLX 9060 was not detected on the HAL.","Replace the HAL port adaptor."
"HA_IFINDEX","2","INIT_ERROR","[chars]","This is a critical error message about a high availability system initilization status or condition. A message of this type indicates that a failure occurred during high availability system initialization.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HARDWARE","3","ASICNUM_ERROR","Port-ASIC number [dec] is invalid","Each port ASIC is identified by an ID. The port ASIC number that is specified in the message text is invalid. This condition indicates an internal error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HARDWARE","3","INDEX_ERROR","Index value [dec] is invalid","An index was attempted to be placed into the hardware table, but that index is out of the configured range.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HARDWARE","3","INTRNUM_ERROR","Port-ASIC Interrupt number [dec] is invalid","An interrupt ID that was used for a port ASIC is invalid.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HARDWARE","3","PORTNUM_ERROR","port number [dec] is invalid","Each interface in a given port ASIC is identified by an index value. The port number used is not within the specified range.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HARDWARE","3","STATS_ERROR","Statistics ID [dec] is invalid","Each statistic that is supported by the port ASIC is identified using an ID. The ID provided by the caller is not within the configured range.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HAWKEYE","1","UNAVAILABLE","HAWKEYE(bay %d), Port adapter requires Rev 2 CPU, shutting down bay","This message is specific to Cisco 7200 series router platforms. It indicates that the device driver has detected an NPE150 CPU version earlier than revision 2. The token ring device driver requires capabilities of a NPE150 revision 2 and later CPU.","Upgrade the 7200 router processor to an NPE150 Revision 2 or later."
"HAWKEYE","1","UNAVAILABLE","Only found %d interfaces on bay %d, shutting down bay","This message may be emitted during IOS initialization or after a token ring port adapter/module is OIR inserted. The message indicates that the token ring device driver was unable to communicate with all of the interfaces expected to be on the port adapter/module. This could mean that one or more of the interfaces is not functioning.","Re-seat the port adapter/module in the slot. Also try installing it in another slot if available. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HAWKEYE","1","UNAVAILABLE","PCI memory unavailable for %s","The device driver for this interface was unable to allocate the necessary amount of shared memory between the driver and the interface hardware. This condition can occur if the system contains less than the recommended minimum amount of SRAM for the current interface combination. Shared memory blocks are required for the interface to function. So, this interface will be inoperable until the memory shortage is corrected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HAWKEYE","3","UNAVAILABLE","%s failed to initialize - %s","The token ring interface encountered an error while attempting to open a connection to the ring. The specific error that occured is described in the last half of the error message as one of the following: 1) 'microcode checksum failed' - the MAC microcode was found to be corrupted inside the interface's local memory. 2) 'failed to build receive descriptor ring' - there was not enough system memory available to allocate receive buffers for packets. 3) 'init failed' - the interface hardware rejected the device driver's request to configure and open the interface.","Reset the interface using the 'clear interface token' exec command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HAWKEYE","3","UNAVAILABLE","Interface %s, adapter check error","The token ring interface encountered an unrecoverable error condition while it was operating and connected to the ring. The interface will automatically shut itself down.","Issue the 'clear interface token' command to restart the interface. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_CONFIG_SYNC","3","UNAVAILABLE","%s","Active and Standby configuration out of sync LBL what was attempted and what went wrong will be printed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_CONFIG_SYNC","3","UNAVAILABLE","%s","Bulk config sync failure, the reason for the failure will be provided in the string","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_CONFIG_SYNC","3","UNAVAILABLE","%s","General Config Sync Problem","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_CONFIG_SYNC","3","UNAVAILABLE","%s","Line by Line sync failure what was attempted and what went wrong will be printed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_CONFIG_SYNC","3","UNAVAILABLE","%s [%s]","Bulk config sync filesys failure, the reason for the failure will be provided in the string","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_CONFIG_SYNC","3","UNAVAILABLE","%s with error code [ %s ]","An ISSU Config Sync Registration Error occurred. The details about what was attempted and what went wrong will be printed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_CONFIG_SYNC","3","UNAVAILABLE","CONFIG SYNC %s msg_type[%d], rc[%d]","An ISSU Config Sync failed to transform messge. The details about what was attempted and what went wrong will be printed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_CONFIG_SYNC","3","UNAVAILABLE","CONFIG SYNC Failed to get MTU Size for session[%d] msg_type[%d], MTU[%d], rc[%d]","An ISSU Config Sync failed to get Messge MTU. The details about what was attempted and what went wrong will be printed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_CONFIG_SYNC","3","UNAVAILABLE","Cannot communicate boot variable to standby (%s)","Active failed to send the boot variable specified to standby. A reload or a switchover operation will likely result in the standby booting a wrong image.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_CONFIG_SYNC","3","UNAVAILABLE","Cannot communicate config register to standby","Active failed to send the config register to standby. The active and standby supervisors won't have the same config registers.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_CONFIG_SYNC","3","UNAVAILABLE","IPC operation failed for [ %s ] with error code [ %s ]","A config sync error occurred. The details about what was attempted and what went wrong will be printed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_CONFIG_SYNC","6","UNAVAILABLE","Bulk Sync succeeded","Bulk Sync has succeeded","No action necessary"
"HA_CONFIG_SYNC","6","UNAVAILABLE","CONFIG SYNC : Subcode not matching for command %s Active subcode[0x%x], Standby subcode[0x%x]","The line by line synchronization of a command has succeeded. A command entered on the active system was successfully synchronized with the standby system. However, the sub code of Parser Return Code, that were returned by the Active and Standby systems were different. However, the sub code of Parser Return Code, that were returned by the Active and Standby systems where different.","Normally, no action is required. If, however, any problems with line by line synchronization are found, copy this message exactly as it appears on the console or in the system log and contact your Cisco technical support representative."
"HA_EM","3","UNAVAILABLE","%s: Checksum error for policy %s - this policy will not be run","The checksum computed for the specified policy does not match the original checksum computed when the policy was registered.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: Error attempting to fetch event information: %s.","The Embedded Event Manager Policy Director failed to receive event info for a callback.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: Error occurred while fetching TTY number.","The Embedded Event Manager failed to fetch a TTY number.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: Error occurred while fetching action information: %d.","The Embedded Event Manager Policy Director failed to gather action information registered for the event.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: Error occurred while fetching variable information: %d.","The Embedded Event Manager Policy Director was unable to set the variable with the requested information.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: Error occurred while performing action: %s.","The Embedded Event Manager Policy Director failed to perform an action for the registered event.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: Failed to create process","The process create function reports an error","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: Failed to look up in the table the registration specification for policy %s.","A table lookup for the registration specification for the policy failed.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: Failed to perform CNS action: %s","The Embedded Event Manager failed attempting to send a CNS message.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: No such event id found.","An internal software error occurred.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: No such event spec id found.","The Embedded Event Manager Policy Director could not find the event for the event spec. ID.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: Published event type does not match event spec.","The Embedded Event Manager Policy Director detected a mis-match in event type between the published event and the event spec.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: The %s event detector I/O queue empty.","The I/O queue is empty at this point, and should not be.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: The I/O queue empty.","The I/O queue is empty at this point, and should not be.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: The Unable to enqueue packet onto queue.","The queue is not in a state to handle enqueues.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: The Unable to initialize queue.","The queue cannot be initialized.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: The following oid has become unavailable: %s","The registered oid is no longer available in the system.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: The hash computation routine reported an error; %s","The fh_hash_md5_fd() function reported the specified error.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: This processor is not in ACTIVE state (state = %d). Switchover must be performed on ACTIVE processor.","Switchovers must occur on ACTIVE unit, not STANDBY unit.Error Message    %HA_EM-3-UNAVAILABLE: %s: Unable to initialize queue; Explanation    The queue initialization function reported an error.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: Unable to open %s; %s","The open function reported an error.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: Unable to open connection to CNS Event Agent: %d","The CNS Action process failed to open CNS handle to Event Agent.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: Unknown event type found in applet.","The Embedded Event Manager applet had an unknown event type.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: callback handler process create failed for eid: %d","The process_create function reported an error trying to create the callback handler process.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: could not find environment variable: %s","The Embedded Event Manager policy director could not find the environment variable specified in the action message.","Only use well known Embedded Event Manager environment variables. If the message continues to occur, copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: could not initialize Embedded Event Manager service: %s","An internal error was detected when initializing Embedded Event Manager service.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: could not initialize queue","An internal error was detected when initializing Embedded Event Manager queue.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: error processing xml buffer","An error occurred processing the event publish information xml buffer.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: failed to create an IPC port: %s","Embedded Event Manager failed to create an IPC port.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: failed to execute callback","Failed to execute callback routine.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: failed to open an IPC port: %s","Embedded Event Manager failed to open an IPC port.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: failed to register an IPC port: %s","Embedded Event Manager failed to register an IPC port.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: fh_init failed : %d","The fh_init function reported an error trying to initialize EEM for a callback process.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: file checksum mismatch","The checksum value of an installed policy does not match the value provided by the installation manager.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","%s: unable to set state for tracking object number %u; object does not exist or is not a stub-object.","The Embedded Event Manager applet attempted to set the state of a tracking object that does not exist.","Only set the state of tracking objects that have already been configured in the system. If the message continues to occur, copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","Error attempting to access an unopened CLI session: %s","An error occurred attempting to access an unopened CLI session: %s","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","UNAVAILABLE","Error disconnecting from CLI session: %s","An error occurred while disconnecting from the CLI session.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","UNAVAILABLE","Error executing applet %s statement %s","The Embedded Event Manager policy director found an error when processing an applet.","Check syntax of applet statement. If the message continues to occur, copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","3","UNAVAILABLE","Error occurred when sending mail to SMTP server: %s : %s","An unexpected error occurred when sending mail to SMTP server.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","UNAVAILABLE","Unable to establish CLI session: %s","Unable to establish CLI session.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","UNAVAILABLE","Unable to read CLI response: %s","Unable to read CLI response.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","UNAVAILABLE","Unable to send CLI command: %s","Unable to send CLI command.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","UNAVAILABLE","Unable to send notification using all SMTP servers","An unexpected error occurred when sending mail to all SMTP servers.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","3","UNAVAILABLE","Use of the 	rack keyword in the correlate statement is not supported in this image.","The Embedded Event Manager Track ED is not supported in this image.","Track ED is not available in this image"
"HA_EM","4","UNAVAILABLE","%s: No tag %s found corresponding to this event publish.","The Embedded Event Manager policy director could not associate the tagname with a published event.","Only use tagnames in the action info type event reqinfo command which correspond to the published event."
"HA_EM","4","UNAVAILABLE","%s: failed to allocate an IPC buffer","Embedded Event Manager failed to allocate a buffer from IPC.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","4","UNAVAILABLE","%s: failed to create an event: %s","Failed to create an Embedded Event Manager event.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","4","UNAVAILABLE","%s: failed to register an event: %s","Failed to register an Embedded Event Manager event.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","4","UNAVAILABLE","%s: failed to send an IPC message: %s","Embedded Event Manager failed to send a message through IPC.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","4","UNAVAILABLE","Cisco Signature not found or invalid. %s has been registered as a user policy.","Cisco Signature not found or invalid.","Sign with Cisco signature."
"HA_EM","4","UNAVAILABLE","No action configured for applet %s","No action has been configured for this applet.","Configure at least one action for this applet."
"HA_EM","4","UNAVAILABLE","No event configured for applet %s","No event has been configured for this applet.","Configure an event for this applet."
"HA_EM","4","UNAVAILABLE","No threads are configured to service event class %s","The Embedded Event Manager has no scheduler threads to service this event class.","Configure threads for the event class using the 'event manager scheduler' command."
"HA_EM","6","UNAVAILABLE","%s: %s","The Embedded Event Manager reports an error on Event Manager configuration","Check the EEM applet or policy configuration"
"HA_EM","6","UNAVAILABLE","%s: Cannot change a class %s %s to priority LAST. LAST is for default policies only","Embedded Event Manager Scheduler Command can only change a default policy to priority LAST.","The command is applicable to default policies only."
"HA_EM","6","UNAVAILABLE","%s: Cannot modify a LAST policy to class %s. LAST policies are for class default only.","Embedded Event Manager LAST policy is for default class only.","The command is applicable to default policies only."
"HA_EM","6","UNAVAILABLE","%s: Error adding trapvar to queue %s","The trap variable was not added to the queue.","Check the EEM applet or policy configuration"
"HA_EM","6","UNAVAILABLE","%s: No variable %s","The variable is not defined.","Check the EEM applet or policy configuration"
"HA_EM","6","UNAVAILABLE","%s: Policy has requested a hardware switchover","An Embedded Event Manager policy requested that a hardware switchover occur.Error Message    %HA_EM-6-UNAVAILABLE: %s: Policy has requested a hardware switchover Explanation    An Embedded Event Manager policy requested that a hardware switchover occur.","None"
"HA_EM","6","UNAVAILABLE","%s: Policy has requested a system reload;","An Embedded Event Manager policy requested that the system be reloaded.Error Message    %HA_EM-6-UNAVAILABLE: %s: cannot %s a running policy with jobid %d. Explanation    Embedded Event Manager Scheduler Command cannot change a running policy.","The command is not applicable to a running policy."
"HA_EM","6","UNAVAILABLE","%s: duplicate oid","The oid is a duplicate","Check the EEM applet or policy configuration"
"HA_EM","6","UNAVAILABLE","%s: number of values exceeded %d","The number of values per variable exceeded the maximum","Check the EEM applet or policy configuration"
"HA_EM","6","UNAVAILABLE","%s: unable to modify the policy to class %s: scheduling rule unavailable.","There is no scheduler rule configured to service this event class.","Please configure a scheduler rule before modifying the event."
"HA_EM","6","UNAVAILABLE","Error compiling regular expression: %s","An error was encountered when compiling the given regular expression.","Check syntax of regular expression pattern. If the message continues to occur, copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","6","UNAVAILABLE","Failed to retrieve context for key %s: %s","Failed to context retrieve variable information for event.","Ensure context information with the given key is saved. If the message continues to occur, copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","6","UNAVAILABLE","Failed to save variable context for key %s: %s","Failed to context save variable information for event.","Ensure context information with the same key is not already saved. If the message continues to occur, copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","6","UNAVAILABLE","Invalid operand in action, expected value within range %ld to %ld, received: %s","Arithmetic actions only accept valid long integer values.","Ensure value provided to action is long integer."
"HA_EM","6","UNAVAILABLE","Invalid operand in arithmetic division, cannot divide by zero","Arithmetic division does not allow divide by zero.","Ensure denominator provided to division action is non-zero."
"HA_EM","6","UNAVAILABLE","Policy update has copied %d bytes from %s to %s","An EEM policy has been copied as a result of an event manager update command","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","6","UNAVAILABLE","Policy update has failed to register policy %s %s","An EEM policy has failed to be registered as a result of an event manager update command","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","6","UNAVAILABLE","Policy update has failed to unregister policy %s %s","An EEM policy has failed to be unregistered as a result of an event manager update command","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","6","UNAVAILABLE","Policy update has successfully re-registered policy %s","An EEM policy has been successfully re-registered as a result of an event manager update command","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_EM","7","UNAVAILABLE","%s","Internal error. The event detector has failed to get a free history list entry.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: %d","The event detector has exceeded its maximum number of retries to send a pulse to the embedded event manager to notify of an event publish.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: %s","Internal error. The event detector has failed to rebuild the metric list from the checkpointed records.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: %s","The SNMP error code.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: %s guard word corrupted; %p","The guard word for the specified control block does not contain what is expected.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: %s[%d]","Internal error. The event detector has failed to fetch a data element from the statistics data engine.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: Application client library unable to handle message receive.","The API received a msg reply when it was not in a state to accept such messages.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: CNS Event Agent not available: %d","The CNS Event Agent is currently not available.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: Class %s: Maximum number of %d %s publish entries exceeded; some events have been discarded","An attempt to publish an event failed because there is no more room in the publish queue.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: Failed to allocate Event Detector context control block; %s","The get_fd function reported an error trying to allocate a Event Detector context control block.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: Failed to duplicate string %s; %s","The strdup function reported an error.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: Failed to open Event Detector context control block","The open_fd function reported an error trying to open a Event Detector context control block.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: Illegal SNMP address type","The SNMP address is illegal.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: Invalid SNMP oid length %d","The SNMP oid has invalid length","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: Invalid argument string: %s","An invalid argument string was passed to the specified function.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: Policy execution %s","The Embedded Event Manager policy excution state has been changed to the state named in the message.Error Message    %HA_EM-7-UNAVAILABLE: %s: SNMP IPV6 address is not supported Explanation    The IPV6 address is not supported.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: SNMP build pdu failed","The SNMP pdu build has failed.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: SNMP make pdu failed","The SNMP pdu make has failed.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: SNMP proxy exec got event, but queue is empty","The SNMP proxy got event but the queue is empty.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: SNMP request failed","The SNMP request has failed.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: SNMP response cancelled","The SNMP response has been cancelled.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: SNMP response error; error_status = %d","The SNMP response has error.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: SNMP response has timed out","The SNMP response has timed out.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: The script name is NULL","An invalid script name was passed as an argument into the specified function.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: The system is unable to switch to standby processor. Switchover cancelled.","Switchovers must occur when STANDBY is available and ready.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: Unable to add %s event detector command;","The Event detector failed to add command.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: Unable to add action %s command;","Failed to add action command.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: Unable to allocate %s; %s","The malloc function reported an error.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: Unable to allocate %s;","The malloc function reported an error.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: Unable to allocate memory for event publish timer block","Internal error. The event detector has failed to allocate memory for the event publish timer block.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: Unable to build an oid string into a SNMP oid; oid = %s","The oid string was not able to build into a SNMP oid","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: Unable to clear restart callback;","The CNS Action process failed to clear restart callback.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: Unable to create SNMP octet community string; string = %s","The community string was not able to build into a SNMP octet string","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: Unable to create a SNMP message; community = %s","The SNMP message failed to be created","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: Unable to create a SNMP varbind","The oid failed to make into a SNMP varbind","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: Unable to enqueue %s;","The enqueue function reported an error.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: Unable to locate reg callback entry for pulse code %d","The registration callback handler was unable to validate the pulse code received.","The pthread_create function reported an error."
"HA_EM","7","UNAVAILABLE","%s: Unable to reallocate %s; %s","The realloc function reported an error.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: Unable to send response for FH_MSG_CALLBACK_DONE %s","The registration callback handler was unable to send the FH_MSG_CALLBACK_DONE message to the Embedded Event Manager Server.","The pthread_create function reported an error."
"HA_EM","7","UNAVAILABLE","%s: Unable to set restart callback;","The CNS Action process failed to set the restart callback.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: Unknown SNMP operation or response type %d","The operation or response type is unknown.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: could not create a leaf timer","Internal error. The event detector has failed to create a managed leaf timer.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: could not create an occurrence entry","Internal error. The event detector has failed to create an entry for the matched occurrence list.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: could not remove an occurrence entry","Internal error. The event detector has failed to remove an entry for the matched occurrence list.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: create_watched_boolean failed: %s","The create_watched_boolean function reported an error trying to create the watched boolean.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: create_watched_boolean failed; %s","The create_watched_boolean function reported an error trying to create the watched boolean.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: create_watched_queue failed; %s","The create_watched_queue function reported an error trying to create the watched queue.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: delete_watched_boolean failed: %s","The delete_watched_boolean function reported an error trying to delete the watched boolean.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: error attemting to format time string","Format time failure.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: invalid comparison operator: %d","Internal error. The value comparison operator is invalid or not supported.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: invalid last policy name replied %s","Internal error. The last policy name the script director replied to show fm policy registered command is an invalid policy name.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: invalid statistics value type: %d","Internal error. The statistics data type is invalid or not supported.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: invalid timer type: %d","Internal error. The timer type is invalid or not supported.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: invalid timer: type=%d, timer=%p","Internal error. The timer value is invalid or not as expected.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: not enough memory: %s","Allocating memory failed due to a low-memory condition.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: resource_monitor_register failed; return code = %d","The resource_monitor_register function reported an error trying to register for RMI notifications.","Copy the message exactly as it appears, and report it your technical support representative."
"HA_EM","7","UNAVAILABLE","%s: unknown event type %d","An unknown Embedded Event Manager even type was detected.","Copy the message exactly as it appears, and report it your technical support representative."
"HD","1","UNAVAILABLE","4T Port Adapter fault on port %d in slot %d","A hardware or software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"HD","1","UNAVAILABLE","Loopback not supported for a 4T DTE/X.21, port %d in slot %d","Loopback mode is not allowed when using an X.21 DTE cable on a Quad serial NIM port.","Do not enable loopback, or use a different cable type."
"HD","1","UNAVAILABLE","msgtxt_badringsize","An internal software error occurred.","If message recurs, call your technical support representative for assistance."
"HD","5","UNAVAILABLE","Unit %d excessive modem control changes","Too many modem control interrupts have been received. The port was disabled to prevent excessive use of the CPU.","Check the cable on the serial port."
"HA_WD","3","DM_SEND_PULSE","[chars]: could not send priority pulse to receiver: [chars]","An attempt to send a priority pulse to the receiver has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_WD","3","PROCFS_PASS","[chars]: procfs pass ended in error after five consecutive passes","A call to the wd_procfs_per_process() function ended in error after five consecutive passes.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_WD","3","PTHRD_SETDETACHSTATE","[chars]: could not set detach state of a POSIX thread: [chars]","An internal error was detected when trying to set the detach state of a POSIX thread.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_WD","3","PTHRD_SETSCHEDPARAM","[chars]: could not set scheduler param of a POSIX thread: [chars]","An internal error was detected when trying to set the scheduler parameter of a POSIX thread.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_WD","3","RESTART_WDSYSMON","[chars]: Error returned from sysmgr_restart_self() [chars]","An error was returned from the sysmgr_restart_self API.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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.HA_WD-6Error Message    %HA_WD-6-BLOCKED_THREAD: A default priority thread CPU starvation condition was detected Explanation    Some higher priority threads are blocking the CPU.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_WD","6","CPU","[chars]","The CPU is blocked by one or more high priority threads.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_WD","6","DLK","[chars]","An unresolved process or Cisco IOS scheduler deadlock was detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HA_WD","7","GUARD_WORD_CORRUPTED","[chars]: [chars] guard word corrupted [hex]","The named control block guard word was corrupted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HDLC","1","ISSU_NOMEMORY","Unit [dec], no memory for [chars]","The requested operation could not be accomplished because of a low-memory condition.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"HSRP","4","BADAUTH","Bad authentication from %s, group %d, remote state %s","Two routers participating in HSRP disagree on the valid authentication string.","Use the standby authentication command to repair the HSRP authentication discrepancy between the local system and the one whose IP address is reported."
"HDLC","4","ISSU_INCOMPATIBLE","hdlc-issu-compat: returned FALSE","The compatibility checking has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HDLC","4","ISSU_SENDFAILED","HDLC ISSU: send message failed, rc = [dec]","An attempt to send a message has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HDLC","4","ISSU_XFORM","[chars]: failed, rc=[chars]","The transform has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HDV","1","UNAVAILABLE","HDV in slot %d: No PCI memory available.","The system is experiencing memory exhaustion in the PCI/packet memory. This is probably due to heavy traffic congestion but could also be a software error.","Review the configuration for performance bottlenecks. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HDV","1","UNAVAILABLE","HDV in slot %d: VIC daughter card (%s/0x%x) is unsupported","The VIC card plugged into the HDV is not of a supported type","Replace this VIC with a type that is supported by this version of IOS, or change the version of IOS to support this VIC type."
"HDV","1","UNAVAILABLE","HDV in slot %d: VIC daughter card has an unknown id of 0x%x","The software did not recognize the type of VIC card plugged into the HDV Port Module.","Check the part number on the VIC card to see if it is supported in the version of IOS operational on the router or contact your technical support representative."
"HDV","1","UNAVAILABLE","HDV in slot %d: no VIC card is inserted in the HDV.","The software did not detect the presence of a VIC card inserted in the HDV Port Module.","Check that there is a VIC card inserted properly into the HDV. If so, then check the part number on the VIC card to see if it is supported in the version of IOS operational on the router or contact your technical support representative."
"HDV","1","UNAVAILABLE","HDV in slot %d: packet size (%d) too big.","A packet greater than the 256 bytes received on this interface.","The system should recover. No action is required. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HDV","2","UNAVAILABLE","HDV in slot %d: An unrecoverable error occurred.","The HDV card experienced an internal unrecoverable error. This may be due to a internal firmware error or bad HDV hardware.","Power down, reinsert the network module and reboot. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HDV","3","UNAVAILABLE","HDV in slot %d: Incorrect %d PM-ID device not supported.","A interface controller device did not have the correct PM-ID.","Check that the HDV is inserted properly. If necessary, turn off the router and reinsert the HDV Port Module. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HDV","3","UNAVAILABLE","HDV in slot %d: reports an invalid device id of %#x.","The HDV port module hardware may be bad or improperly seated.","Power down, reinsert the network module and reboot. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HDV","3","UNAVAILABLE","HDV in slot %d: the HDV failed to initialize properly.","An initialization action failed for the HDV. This can be caused by a lack of system resources, improper or no VIC installed in the port module, or it may be bad HDV hardware.","Power down. Check that a supported VIC module is properly installed in the HDV module. Reinsert the VIC module. Then reinsert the Port Module and reboot the router. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HDV","3","UNAVAILABLE","HDV in slot %d: the firmware on the port module did start properly.","The firmware on the card did not start after a reset. This is usually caused by a bad HDV module or improperly seated HDV module.","Power down. Reinsert the HDV port module and reboot the router. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HDV","3","UNAVAILABLE","HDV in slot %d: the port module did not reset and start up properly.","The hardware on the card did not start after a reset. This is usually caused by a bad HDV module or improperly seated HDV module.","Power down. Reinsert the HDV port module and reboot the router. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HDX","3","UNAVAILABLE","On int %d/%d, unexpected state %d, event %d","A bad state, event pair is detected in the rx/tx half duplex state machine.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HLFM","3","MACFREE_ERROR","MAC address [enet], vlad [dec] is still referenced; cannot free","An attempt was made to free a MAC address before all references to it had been released.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HLFM","3","MAP_ERROR","IP address [IP_address] not in mac tables, mac-address [enet], vlan [dec]","The IP address and MAC address tables have lost their synchronization.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HLFM","3","MOD_SD","Failed to modify Station Descriptor with index [dec], vlan [dec], di [dec], error [dec], mad [dec], ref-count [dec]","The forwarding manager is attempting to modify a station descriptor that is no longer in use or is invalid.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HMM_ASYNC","3","UNAVAILABLE","Digital modem %d/%d on Simm %d failed power on diagnostics.","Digital modem failed to pass power on diagnostics. It will not be used.","If remaining Simm(s) passed diagnostics, remove or replace this problem Simm before continuing. Copy the error message exactly as it appears, and report it to your technical support representative."
"HMM_ASYNC","3","UNAVAILABLE","HMM Digital Modem Card %d experienced a TDM Synthesis Error.","Digital Modem Card failed to send or receive PCM data in time to avoid data loss. This may cause the modems to speed shift, retrain, or hangup.","Verify that the DS1 interface(s) share a common clock source. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HMM_ASYNC","3","UNAVAILABLE","HMM Modem %d/%d Mailbox is Full, command %#x not sent.","Error delivering commands to Modem Module. This may be a transient failure. If this message repeats every 30 seconds it may indicate a failed Modem Module.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HMM_ASYNC","3","UNAVAILABLE","HMM Modem %d/%d failed to accept a new command.","Modem failed to accept a new command. This may be a transient failure or the modem may remain unusable until a system reset.","You may try to reset the modem by issuing the clear modem slot/port command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HMM_ASYNC","3","UNAVAILABLE","HMM: Digital Modem Card %d hardware exception : %s","This may be an intermittent or permanent hardware failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HMM_ASYNC","3","UNAVAILABLE","No memory for %s of unit %d","The router does not have enough memory to perform the function","Consider adding more shared memory. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HMM_ASYNC","3","UNAVAILABLE","Received unknown message 0x%x at mail offset %d from modem %d/%d.","Received unidentifed message from modem. This is symtomatic of running with an incompatible version of modem firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HMM_ASYNC","3","UNAVAILABLE","Simm %d in slot %d has halted due to a Runtime Error.","The Portware running on the Simm was halted due a runtime error. The six modems contained on the Simm have been marked Bad and are no longer usable until the system is reloaded.","Copy the error message exactly as it appears, along with show modem and show modem log output, and report it to your technical support representative."
"HMM_ASYNC","3","UNAVAILABLE","Unable to creaet pool %d raw Tx mode buffers","The router does not have enough I/O memory for buffers","Consider adding more shared memory. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HMM_ASYNC","3","UNAVAILABLE","Unable to create TTY structure for line %d","Unable to create tty line control block for the specified line This may be due to not having enough memory in the router","Consider adding more shared memory. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HMM_ASYNC","3","UNAVAILABLE","Unable to create pool for %d raw Rx mode buffers","The router does not have enough I/O memory for buffers","Consider adding more shared memory. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HMM_ASYNC","3","UNAVAILABLE","Unable to download firmware image to digital modem card in slot %d.","Failed to bring up the processor on the digital modem card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HMM_ASYNC","3","UNAVAILABLE","Unable to download modem firmware image to Simm %d in slot %d.","Failed to load modem firmware into the Simm.","If firmware successfully loaded into remaining Simm(s), remove or replace this problem Simm before continuing. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HMM_ASYNC","3","UNAVAILABLE","Unknown Platform type to support HMM Network Module","The Network Module is not compatible with the current platform that it is plugged into.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HMM_ASYNC","4","UNAVAILABLE","HMM Digital Modem Card %d contains no active modems.","There are no modems installed on the network module.","Make sure the network module contains properly installed MICA-6DM Simm(s)."
"HOOD","3","UNAVAILABLE","msgtxt_badunit","An internal software error occurred.","If the message recurs, call your technical support representative for assistance."
"HOOD","5","UNAVAILABLE","Unit %d, HP100VG, cable error. Training failed","A 100VG cable or hub is faulty.","If the message recurs, and either the cable or hub appears to be good, repair or replace the router module."
"HOOD","5","UNAVAILABLE","Unit %d, HP100VG, no tone detected. Check cable, hub","A 100VG cable is faulty.","If the message recurs, and either the cable or hub appears to be good, repair or replace the router module."
"HOOD","5","UNAVAILABLE","Unit %d, excessive collisions","An Ethernet cable is broken or unterminated, or the transceiver is unplugged.","If the transceiver appears to be properly terminated, repair or replace the router."
"HOOD","5","UNAVAILABLE","Unit %d, lost carrier. Transceiver problem?","An Ethernet transceiver is unplugged or faulty.","Repair or replace the controller."
"HP100VG","1","UNAVAILABLE","%s access to network denied","Access to the network is denied because of incompatible configuration.","Check the configuration of the hub for Frame Format, Promiscuous, and Repeater bit to indicate proper configuration."
"HP100VG","1","UNAVAILABLE","%s configuration not compatible with the network","Configuration of the router module is not compatible to the network","Check the configuration of the hub for Frame Format, Promiscuous, and Repeater bit to indicate proper configuration"
"HP100VG","1","UNAVAILABLE","%s unable to login to the hub","Unable to login to the hub.","Take action based on the following error messages."
"HP100VG","1","UNAVAILABLE","On %s LAN segment","Two VG devices on the same LAN segment have the same MAC address.","Check router configuration to make sure that no duplicate MAC address is configured."
"HP100VG","1","UNAVAILABLE","Only found %d interfaces on bay %d, shutting down bay","No VG interface detected.","Make sure 100VG PA is properly seated in the slot. Otherwise repair or replace the 100VG PA interface module."
"HP100VG","3","UNAVAILABLE","%s hardware CAM device not found","Could not find Hardware CAM on the PA module","Repair or replace the 100VG PA interface module."
"HP100VG","3","UNAVAILABLE","%s packet buffer, pak=0x%x","A software or hardware error occurred. The HP100VG driver detected that the buffer ring is in an inconsistent and unrecoverable state.","Copy the error message exactly as it appears, and report it to your technical support representative."
"HP100VG","3","UNAVAILABLE","Bay %d device ID seen as %#x, expected %#x","Could not find 100VG PCI device","Make sure 100VG PA is properly seated in the slot. Otherwise repair or replace the 100VG PA interface module."
"HP100VG","5","UNAVAILABLE","%s cable fault; tone not detected","An 100VG cable is faulty.","Repair or replace the cable. If either the cable appears to be good, repair or replace the VG PA interface module."
"HP100VG","5","UNAVAILABLE","%s cable/hub problem?","The VG controller detects link to the hub is down due to cable, hub or vg controller problem.","Repair or replace the cable or hub. If either the cable or hub appears to be good, repair or replace the VG PA interface module."
"HP100VG","5","UNAVAILABLE","%s training failed","An 100VG cable or hub is faulty.","Repair or replace the cable or hub. If the cable or hub appears to be good, repair or replace the VG PA interface module."
"HSRP","3","MISCONFIG","Attempt to change [chars] MAC address to [enet] when DECNET already running","An HSRP group attempted to become active on an interface that can only support a single MAC address and that is running DECnet. If the standby use-bia command has not been entered on the interface, HSRP would normally set the interface MAC address to the HSRP virtual MAC address, but this configuration is not allowed if DECnet is running.","Enter the standby use-bia command on the interface."
"HSRP","3","NOSOCKET","Unable to open socket","The system was unable to initialize an IP connection for the Hot Standby protocol.","Make sure that there is at least one interface configured to run IP."
"HSRP","4","BADAUTH","Bad authentication from [IP_address], group [dec], remote state [chars]","Two routers participating in HSRP disagree on the valid authentication string.","Use the standby authentication command to repair the HSRP authentication discrepancy between the local system and the one whose IP address is reported."
"HSRP","4","BADAUTH2","Bad authentication from [IP_address]","Two routers participating in HSRP disagree on the valid authentication string.","Use the standby authentication command to repair the HSRP authentication discrepancy between the local system and the one whose IP address is reported."
"HSRP","4","BADVIP","[chars] Grp [dec] address [IP_address] is in the wrong subnet for this interface","The HSRP virtual IP address contained in the Hello message cannot be learned as it is not within a subnet configured on the interface.","Check the configuration on all HSRP routers and ensure that the virtual IP address is within a configured subnet."
"HSRP","4","DIFFVIP1","[chars] Grp [dec] active routers virtual IP address [IP_address] is different to the locally configured address [IP_address]","The HSRP virtual IP address contained in the Hello message from the active router is different from the virtual IP address configured locally.","Check the configuration on all HSRP routers in the group and ensure they are all configured with the same virtual IP address."
"HSRP","4","DUPADDR","Duplicate address [IP_address] on [chars], sourced by [enet]","The IP address in an HSRP message received on the specified interface is the same as the IP address of the router. Another router might be configured with the same IP address. The most likely cause is a network loop or a misconfigured switch that is causing the router to see its own HSRP Hello messages.","Check the configurations on all the HSRP routers to ensure that the interface IP addresses are unique. Check that no network loops exist. If port channels are configured, check that the switch is correctly configured for port channels. Enter the standby use-bia command so that the error message displays the interface MAC address of the sending router, which can be used to determine if the error message is caused by a misconfigured router or a network loop."
"HSRP","4","DUPVIP1","[chars] Grp [dec] address [IP_address] is already assigned to [chars] group [dec]","The HSRP virtual IP address contained in the Hello message cannot be learned as it is already assigned to a different HSRP group.","Check the configuration on all HSRP routers and ensure that the virtual IP address of each HSRP group is unique."
"HSRP","4","DUPVIP2","[chars] Grp [dec] address [IP_address] is already assigned on this interface","The HSRP virtual IP address contained in the Hello message cannot be learned as it is already assigned to this interface.","Check the configuration on all HSRP routers and ensure that the virtual IP address of each HSRP group is unique."
"HSRP","4","DUPVIP3","[chars] Grp [dec] address [IP_address] is already assigned to, or overlaps with, an address on another interface or application","The HSRP virtual IP address contained in the Hello message cannot be learned as it is already assigned to, or overlaps with, an address on another interface or application.","Check the configuration on all HSRP routers and ensure that the virtual IP address of each HSRP group is unique."
"HSRP","5","STATECHANGE","[chars] Grp [dec] state [chars] -> [chars]","The router has changed state.","No action is required."
"HTSP","3","UNAVAILABLE","no free event structure available from %s for DSP message","There were no event structures remaining in the system pools to alert the router of a voice or signaling event.","Check that the voice port for which the event was reported is still operational. If not, clear the voice port."
"HTSP","3","UNAVAILABLE","voice port %s: Ground Start trunking not supported","This voice port does not support the 'connection trunk' command when ground start signaling is configured. Trunking mode on this voice is supported when using loop start signaling.","Shut down the voice port, remove the 'connection trunk' and/or 'signal groundStart' command from the voice port configuration, and unshut the voice port."
"HTSP","3","UNAVAILABLE","voice port %s: call connection id [0x%x 0x%x 0x%x 0x%x]","There was a capabilities mismatch between the two call legs. capabilities are negotiated between call legs for CODEC, VAD and FAX rate.","Check that the dial peer configuration is appropriate for the interface in question. Also check that and configuration on the interface is correct."
"HTSP","3","UNAVAILABLE","voice port %s: status=0x%x message=0x%x text=%s","The DSP reported a fatal error. All calls on the DSP were dropped and a DSP reload was attempted.","Verify that the DSP reloaded properly by attempting to place a call on the affected voice port. Contact your technical support representative, include the full text of the error message."
"HTSP","5","UNAVAILABLE","Trunk port(channel) [%s] is %s","Trunk port:channel changed state.","LOG_STD_NO_ACTION"
"HTTP","3","INIT_FAIL","HTTP Process Init failed.","Initialization of the HTTP subsystem has failed.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"HTTP","3","OUTOF_MEM","HTTP out of memory.","An error occurred during initialization of the HTTP process. The HTTP process could not create crucial internal data structures that are required for operation of the HTTP subsystem. The most likely reason for this condition is an exhaustion of system memory.","Reduce other system activity to ease memory demands. if conditions warrant, upgrade to a larger memory configuration."
"HTTP","3","PROC_NOCREAT","Unable to create HTTP process.","An error occurred during initialization of the HTTP process. The HTTP process that processes all HTTP requests and responses could not be created.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"HTTP","3","SERVER_RESTART_FAILED","Server restart failed. Disabling HTTP server.","TCP process was restarted affecting the HTTP server. Attempts to restart HTTP server failed.","Check status of TCP process. Enable the HTTP server after TCP process has started."
"HTTP","6","SERVER_SETUP_FAILED","Server setup failed","Setup of the HTTP or HTTPS server to listen on the specified port number has failed.","Disable the server, verify that port number is correct and enable the server. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"HUB","1","UNAVAILABLE","Bad port number %d","An internal software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"HUB","1","UNAVAILABLE","Invalid hub type %d and number %d","An internal software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"HUB","1","UNAVAILABLE","Read op %d not allowed","An internal software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"HUB","1","UNAVAILABLE","Write op %d not allowed","An internal software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"HUB","1","UNAVAILABLE","msgtxt_nomemory","The system detected that there is not enough memory for the hub initialization.","If conditions warrant, upgrade to larger memory configuration."
"HUJR","3","UNAVAILABLE","Read/write failed [%s]","A read/write error occurred when accessing the hardware","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HW","2","OBSOLETE_HW_VER","Module Version in [chars] is obsolete ********************************************************************* * IMPORTANT !!! * * The module in [chars] is obsolete and must be returned * * via RMA to Cisco Manufacturing. If it is a lab unit, * * it must be returned to Proto Services for upgrade. * *********************************************************************","The specified hardware is obsolete and needs to be replaced.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HWMATM_MOD","3","UNAVAILABLE","Unexpected null pointer in %s at %d","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HW_API","3","BACKWALK_REQUEST","Backwalk request failed, [chars]","A request to walk internal data structures has failed. Depending on the criticality of the data, the accuracy of forwarding may be affected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HW_API","3","BACKWALK_REQUEST_VALUE","Backwalk request failed, [chars] ([hex])","A request to walk internal data structures has failed. Depending on the criticality of the data, the accuracy of forwarding may be affected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HW_API","3","INVALID_CONTEXT","Invalid context [hex]","An internal API error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HW_API","3","INVALID_OBJ","Invalid object [hex]","An internal API error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HW_API","3","INVALID_TYPE","Invalid type [dec]","An internal API error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HW_API","3","INVALID_WALK_SPEC","Invalid walk spec [hex]","An internal API error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HW_API","3","NO_OBJ_TYPE_LIST_ENTRY","Invalid sw_obj_type ([dec]) used with obj_type_list","An internal API error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HW_API","3","NO_OBJ_TYPE_LIST_ENTRY2","Invalid sw_obj_link_type ([dec]) used with obj_type_list","An internal API error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HW_API","3","RESILIENCE_NO_HANDLER","No handlers in place for [chars] sw object creation failure.","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HW_API","3","VECTOR","Failed to set [chars] vector for [chars], [chars]","An internal API error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HW_API","3","WALK_MODE_UNSUPPORTED","Walk mode '[chars]' unsupported","An internal API error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HW_VPN","1","UNAVAILABLE","%s: Command 0x%x failed with status 0x%x","A command was sent to the Encryption AIM, and it responded that the command had an error. The details of the failure depend upon the circumstances, but in all likelihood the Encryption AIM is faulty and should be replaced.","Make a note of the error message and contact a Cisco representative. The EAIM will most likely need to be replaced."
"HW_VPN","1","UNAVAILABLE","%s: EAIM responded incorrectly to hello: received 0x%x expected 0x%x","A command was sent to the Encryption AIM, and it was expected to echo back the data that was sent to it. Instead of receiving the expected data, the indicated data was received instead.","Make a note of the error message and contact a Cisco representative. The EAIM will most likely need to be replaced."
"HW_VPN","1","UNAVAILABLE","%s: Invalid Amount of RAM for PA ID, memsize = 0x%x","The Power On Self Test (POST) reported an incorrect memory size.","The EAIM must be replaced."
"HW_VPN","1","UNAVAILABLE","%s: Invalid command reply: expected 0x%x received 0x%s","A command was sent to the Encryption AIM, and it's replay contained an unexpected reply code. The details of the failure depend upon the circumstances, but in all likelihood the Encryption AIM is faulty and should be replaced.","Make a note of the error message and contact a Cisco representative. The EAIM will most likely need to be replaced."
"HW_VPN","1","UNAVAILABLE","%s: Key management error, cmd=0x%x status=0x%x","An unexpected error occurred during the execution of a key management command by the EAIM.","Make a note of the status value and contact a Cisco representative. The EAIM will most likely need to be replaced."
"HW_VPN","1","UNAVAILABLE","%s: Packet Encryption/Decryption error, status=%u","An unexpected error occurred during the encryption and/or decryption of a packet.","This message can occur occasionally during normal operation of the system. It may occur during the transition to a new session key for a Security Association. In such cases, it may be ignored. However, if it happens frequently, or is associated with traffic disruption, then make a note of the status value and contact a Cisco representative. The EAIM will most likely need to be replaced."
"HW_VPN","1","UNAVAILABLE","%s: Power On Self Test failed, alert status = 0x%x","The Power On Self Test (POST) for the EAIM failed.","The EAIM must be replaced."
"HW_VPN","1","UNAVAILABLE","%s: Timeout on reply to command to Encryption AIM","A command has been sent to the Encryption AIM, and there has not been a reply to the command in a reasonable amount of time. The Encryption AIM is faulty and should be replaced.","Make a note of the error message and contact a Cisco representative. The EAIM will most likely need to be replaced."
"HW_VPN","1","UNAVAILABLE","AIM in slot %u not supported by this HW revision.","The revision level of the C2600 'Elmer' PLD does not support encryption AIM. The PLD needs to be reprogrammed.","The C2600 'Elmer' PLD needs to be reprogrammed to a later revision. Refer to CCO Release Notes for the C2600 and Encryption AIM for an explanation of how to reprogram the PLD."
"HW_VPN","1","UNAVAILABLE","EAIM: Device Initialization failure","The EAIM failed to respond properly to attempts at initialization.","The EAIM must be replaced."
"HW_VPN","1","UNAVAILABLE","EAIM: Initialization failed at %s","The EAIM device would not reset properly. Indicative of a hardware failure.","Copy the error message exactly as it appears, and report it to your technical support representative. The EAIM will need to be replaced."
"HW_VPN","1","UNAVAILABLE","EAIM: Invalid PCI device ID: %u","The EAIM device has improperly identified itself on the router bus","Copy the error message exactly as it appears, and report it to your technical support representative. The EAIM will need to be replaced."
"HW_VPN","1","UNAVAILABLE","Encryption AIM busy","You have entered a command which involves an Encryption AIM, but the Encryption AIM is busy executing another command.","Wait until the present command has completed. If the present command doesn't seem to complete in a reasonable amount of time, then the Encryption AIM is defective and must be replaced."
"HW_VPN","1","UNAVAILABLE","Encryption AIM not present in system","You have entered a command which involves an Encryption AIM, but no encryption AIM is present in the system.","Don't enter encryption AIM commands unless an Encryption AIM is present. If an encryption AIM is installed, then it is defective and must be replaced."
"HW_VPN","1","UNAVAILABLE","This Encryption AIM type not supported on this router platform","You have installed an encryption AIM designed for one particular type of router platform (e.g. C2600) on another router platform (e.g. C3620). Different Encryption AIMs are supported by each router platform.","The Encryption AIM must be removed and one compatible with your router must be installed in its place."
"HW_VPN","6","UNAVAILABLE","%s: disabled","The EAIM has been disabled","The EAIM will need to be replaced."
"HW_VPN","6","UNAVAILABLE","%s: starting up","The specified EAIM has initialized successfully.","This is an informational message only. It occurs in normal operation."
"HW_VPN","6","UNAVAILABLE","Cannot support more than one Encryption AIMs","A second Encryption AIM was discovered present in the system. The Encryption AIM software only supports a single Encryption AIM. All other Encryption AIMs installed will be ignored.","Remove one of the Encryption AIMs installed in your system."
"HWIF_QOS","6","EOM_FORCE_TRUSTED","EoMPLS on [chars] caused install of 'trust cos' state","If EoMPLS is configured on the interface or any of its subinterfaces, the no trust state is automatically replaced by trust cos.","Remove all EoMPLS configurations from the interface to restore the no trust state."
"HWIF_QOS","6","EOM_RESTORE_UNTRUSTED","The 'no trust' state is restored on EoMPLS removal from [chars]","If EoMPLS is unconfigured on the interface and all its subinterfaces, the configured no trust state is restored.","This is an informational message only. No action is required."
"HWIF_QOS","6","EOM_TRUST_NOT_INSTALLED","'no trust' command is not installed on [chars] in presence of EoMPLS","If EoMPLS is configured on the interface or any of its subinterfaces, the no trust command is not installed.","Remove all EoMPLS configurations from the interface."
"HYPERION","3","FAILURE_INTR_CFG","Failure to setup the Hyperion device interrupts.","The internal ASIC on a line card could not be initialized. The device is not operational and has been disabled. The data path is not operational.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HYPERION","4","EARL_BUS_SYNC_ERR","Failed to sync Earl bus, Hyperion version [dec]","The HYPERION ASIC in the line card failed to synchronize with the Earl bus.","If traffic recovers, no action is required. Otherwise, copy the message exactly as it appears on the console or in the system log. Enter the show platform hardware hyperion all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HYPERION","4","HYP_RESET","Hyperion Error Interrupt. Resetting ASIC.","The Hyperion ASIC in the SPA or Enhanced FlexWAN module has received a fatal error. The ASIC is automatically reset, and the SPA or Enhanced FlexWAN module attempts to continue normal operation.","No action is required if traffic recovers. If traffic does not recover, copy the error message exactly as it appears on the console or in the system log. Enter the show platform hardware hyperion all command to gather data that may help identify the cause of the error. If you cannot determine the cause of the error from the error message text or from the show platform hardware hyperion all output, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HYPERION","4","HYP_RESET","Hyperion ASIC reset, interrupt [chars]","The Hyperion ASIC in the SPA or Enhanced FlexWAN module has received a fatal error. The ASIC is automatically reset, and the SPA or Enhanced FlexWAN module attempts to continue normal operation.","No action is required if traffic recovers. If traffic does not recover, copy the error message exactly as it appears on the console or in the system log. Enter the show platform hardware hyperion all command to gather data that may help identify the cause of the error. If you cannot determine the cause of the error from the error message text or from the show platform hardware hyperion all output, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HYPERION","4","UNEXPECTED_VERSION","Unexpected Hyperion version.","The line card is unable to recognize the version of the Hyperion ASIC.","No action is required if traffic passes through the line card. If traffic does not pass through the line card, check the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl to determine in which version this problem is fixed and upgrade accordingly. If traffic does not pass after the upgrade, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HYPERION","5","BUS_MODE_CHANGE","The System Switching Bus Mode changed to [chars] mode","The system switching bus interface device mode changed switching bus modes. The mode is specified in the system message.","The supervisor engine instructed the module to change the mode on the switching bus. No action is required."
"HYPERION","5","BUS_SEQ_ERR","Constellation bus Sequence Error. Resetting Hyperion ASIC.","The switch processor has detected a sequence error on the backplane bus. A reset sequence from the EARL has been called to recover from this error. System traffic should recover and continue normally.","If traffic recovers, no action is required. If traffic does not recover, copy the error message exactly as it appears on the console or in the system log. Enter the show platform hardware hyperion all command to gather data that may help identify the cause of the error. If you cannot determine the cause of the error from the error message text or from the show platform hardware hyperion all output, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HYPERION","5","HYP_INIT_FAILURE","The Hyperion ASIC initialization failed","The Hyperion ASIC initialization was not successful. The Hyperion ASIC is not operational and is disabled.","If traffic recovers, no action is required. If traffic does not recover, copy the error message exactly as it appears on the console or in the system log. Enter the show platform hardware hyperion all command to gather data that may help identify the cause of the error. If you cannot determine the cause of the error from the error message text or from the show platform hardware hyperion all output, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HYPERION","5","HYP_INTR_INFO","[chars]","This message provides more information about the interrupts from the backplane bus ASIC to the line card CPU.","If traffic recovers, no action is required . Otherwise, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HYPERION","5","HYP_RESET_INFO","[chars]","This message provides more information about the interrupts leading to the reset of the backplane bus ASIC.","If traffic recovers, no action is required . Otherwise, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"HYPERION","5","NULL_HYP_OBJECT","The Hyperion device object pointer is set to NULL","The memory location of the Hyperion ASIC device object is invalid. The Hyperion ASIC operation is disabled, and the device interrupt is now masked.","If traffic recovers, no action is required. If traffic does not recover, copy the error message exactly as it appears on the console or in the system log. Enter the show platform hardware hyperion all command to gather data that may help identify the cause of the error. If you cannot determine the cause of the error from the error message text or from the show platform hardware hyperion all output, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC","2","NOMEM","No memory available for %s","The ICC subsystem could not obtain the memory it needed.","If this error recurs, then issue the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information."
"ICC","3","MAST_BAD_FREE","ICC multicast memory already freed","One of the ICC multicast request's memory was found to be free when response arrived","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC","4","BAD_ACCOUNTING","ICC received a bad class %d","The intercard communication (ICC) process received an invalid class and therefore cannot account for the message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC","4","COMM","Communication failure occurred while %s","A communication failure has occurred between this card and another card in the system.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC","4","CONSISTENCY","Internal consistency check: %s","An internal inconsistency was found in some ICC data structures.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC","4","HEARTBEAT","Card %d failed to respond to heartbeat","A communication failure has occurred between the primary and the specified line card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC","5","REQ_WATERMARK","[dec] pkts for class [chars] request [dec] are waiting to be processed","The processor has received packets for the class request and the packets are waiting to be processed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC","6","INFO","[chars] [hex] [hex] [hex]","This message provides ICC subsystem generic information or error information.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC","6","MCAST_TIMEOUT","ICC multicast request timed out","One of the ICC multicast request timed out without response.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"I82543","1","UNAVAILABLE","%s - Cannot create IDB subblock due to insufficient memory","There was insufficent system memory to create the subblock.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"I82543","1","UNAVAILABLE","%s - Could not install or use i82543 IDB subblock","An internal IOS error prevented the IDB subblock from being installed or used.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"I82543","1","UNAVAILABLE","%s, initialization failed, no buffer memory","The Ethernet port initialization failed due to insufficient memory","The router requires more packet memory - consider upgrade. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"I82543","1","UNAVAILABLE","Could not init buffer pools","The driver failed to get a pool of buffers from IOS","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"I82543","1","UNAVAILABLE","Could not initialize structure","The driver failed to initialize a structure","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"I82543","1","UNAVAILABLE","Invalid Interface Descriptor Block","The driver tried to fetch the interface's IDB and failed","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"I82543","1","UNAVAILABLE","MAC Still in Reset","An attempt was made to access the MAC while it was in reset","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"I82543","1","UNAVAILABLE","Only found %d interfaces on bay %d, shutting down bay","Possible hardware error resulted in too few interfaces discovered","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"I82543","1","UNAVAILABLE","Plugin function table incomplete or missing","The driver could not access the PA's specific function table","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"I82543","1","UNAVAILABLE","Problem getting particle size","The driver was unable to get the particle size for this interface","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"I82543","1","UNAVAILABLE","Unknown IDBTYPE while starting i82543","The IDBTYPE in the interface's instance structure is undefined for this driver","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"I82543","1","UNAVAILABLE","Unknown media-type in subblock","The media-type specified in the driver subblock is invalid","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"I82543","1","UNAVAILABLE","Unknown or invalid chip mode (MII/TBI)","The driver subblock contains an invalid or undefined chip operating mode (MII or TBI mode)","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"I82543","2","UNAVAILABLE","Interface %s does not support ISL","ISL is not supported on the specified interface's hardware.","LOG_STD_NO_ACTION"
"I82543","3","UNAVAILABLE","%s, error interrupt, csr_STATUS=%#x","The i82543 controller has signalled an error condition.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"I82543","3","UNAVAILABLE","%s, packet too big (%d), src %e, dst %e","The interface detects a packet larger than what is defined by MTU","Check the other station's MTU setting LOG_STD_NO_ACTION"
"I82543","3","UNAVAILABLE","Bay %u, device number %u: unknown device (%#x)","Somehow the PA does not contain an Intel 82543 controller chip","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"I82543","3","UNAVAILABLE","Interface %s has an unsupported PHY","The specified interface has an unsupported PHY chip on the board","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IBM2692","1","UNAVAILABLE","%s %s creation failed","The router or access server could not allocate memory for the descriptors.","Copy the error message exactly as it appears, and report it to your technical support representative."
"IBM2692","1","UNAVAILABLE","Bay %d port adapter requires Rev 2 CPU","The Token Ring PCI Port Adapter driver depends on capabilities of the Revision 2 processor.","Upgrade the processor to Revision 2."
"IBM2692","1","UNAVAILABLE","IBM2692 (%d/%d), LL queue overflow.","A packet buffer queue overflowed. This message indicates a packet was lost, probably due to traffic congestion.","A small number of queue overflows might not be a cause for concern. Reducing the load on the router or installing a higher-performance router should alleviate this problem."
"IBM2692","1","UNAVAILABLE","Only found %d interfaces on bay %d, shutting down bay","One of the interface controller devices on the module did not initialize properly.","Power down, reinsert the network module, and reboot. If the message recurs, call your technical support representative for assistance."
"ICE","3","UNAVAILABLE","%s","Error Messages","try debug command"
"ICC_ISSU_NEGO","3","CLIENT_EVENT_QUEUE_CREATE","Failed to create ICC nego client queue (client %d, endpoint 0x%x)","The intercard communication (ICC) ISSU negotiation process failed to create a client watched queue.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","CLIENT_FREE_EVENTS_ALLOCATION","Failed to allocate ICC Nego free events (client %d, endpoint 0x%x)","The ICC negotiation process failed to allocate ICC negotiation free events.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","CLIENT_FREE_EVENT_ENQUEUE","Failed to enqueue event to free event queue (type %d, client %d, endpoint 0x%x)","The ICC negotiation process failed to enqueue an event to the free event queue.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","CLIENT_FREE_EVENT_QUEUE_CREATE","Failed to create ICC nego client queue (client %d, endpoint 0x%x)","The ICC negotiation process failed to create a client free events queue.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","CLIENT_PROCESS_CREATE","Failed to create ICC nego client process (client %d, endpoint 0x%x)","The ICC negotiation process failed to create a client process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","DROPPING_MSG","Dropping message (client %d)","The ICC negotiation process dropped a client message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","ICC_INIT_SEND","Failed to send the ICC Nego Init message (endpoint 0x%x)","The ICC negotiation process failed to send the negotiation initialization message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","INCONSISTENT_MEDMAN_DATA","Inconsistent MEDMan data (unique key %d)","The ICC negotiation process Multiple Endpoint Data Manager (MEDMan) data is inconsistent.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","INTERNAL_ICC_PAK","Failed to get an ICC pak (internal message %d, size %d","The ICC negotiation process failed to get an ICC packet for an internal message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","INVALID_CLIENT","Invalid client %d","The ICC negotiation client is invalid.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","INVALID_CLIENT_PID_GENERIC","Invalid client process pid, can't be the generic process (client %d, endpoint 0x%x, pid %d)","An attempt was made to send a client process message to the ICC negotiation generic process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","INVALID_DS","Invalid ICC Nego data structure","The internal ICC negotiation data structure is invalid.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","INVALID_DS_CLIENT","Invalid ICC Nego data structure (client %d)","The internal ICC negotiation data structure is invalid.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","INVALID_MSG","Invalid message (type %d)","The ICC negotiation message is invalid.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","INVALID_PCOL_DS","Invalid ICC Nego process collector data structure (client %d, endpoint 0x%x)","The ICC negotiation process collector data structure is invalid.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","INVALID_QUEUE","Invalid ICC Nego client queue (client %d)","The internal ICC negotiation watched queue is invalid.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","INVALID_STATUS","Invalid client negotiation status (client %d, status %s)","The ICC negotiation client negotiation status is invalid.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","MEDMAN_DS_CREATION","Failed to create the client data structure in MEDMan (client %d, endpoint 0x%x, error %s)","The ICC negotiation process could not create the client data structure in the Multiple Endpoint Data Manager (MEDMan).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","MEDMAN_REGISTRATION","Failed to register with MEDMan","The ICC negotiation process failed to register with the Multiple Endpoint Data Manager (MEDMan).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","MSG_ENQUEUING","Failed to enqueue msg to the ICC Nego generic process (client %d)","The ICC negotiation process failed to enqueue a process message to the ICC negotiation generic process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","MSG_ENQUEUING_CLIENT","Failed to enqueue msg to the ICC Nego generic process (client %d, e_id 0x%x, type %d)","The ICC negotiation process failed to enqueue a process message to an ICC negotiation client process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","NEGO_CANNOT_COMPLETE","Negotiation cannot complete (endpoint 0x%x)","The ICC negotiation cannot complete.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","NOTIFY_CLIENT","Failed to notify client %d (e_id 0x%x)","The ICC negotiation process failed to notify a client.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","NO_FREE_EVENT","Couldn't get a free event (type %d, client %d, e_id 0x%x)","The ICC negotiation process failed to get a free event for a client.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","NO_INTERNAL_CB","No callback for internal message %d","No ICC negotiation callback has been defined for this internal message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","NO_QUEUE","Couldn't get an event queue (type %d, client %d, e_id 0x%x)","The ICC negotiation process failed to get an event queue for a client.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","NO_UK","Couldn't retreive the unique key","The ICC negotiation process failed to retrieve the unique key for a client endpoint pair.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","NVI_EMPTY_MSG","Received an empty NVI ICC message","The ICC negotiation process received an empty NVI ICC message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","NVI_ICC_SEND","Failed to send the ICC Nego NVI ICC message (endpoint 0x%x)","The ICC negotiation process failed to send the NVI ICC message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","NVI_REQ_PAK","Failed to get an ICC req pak for the ICC Nego NVI message","The ICC negotiation process failed to get an ICC request packet for the NVI internal message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","NVI_RESP_PAK","Failed to get an ICC resp pak for the ICC Nego NVI message","The ICC negotiation process failed to get an ICC response packet for the NVI internal message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","OPEN_PORT_RELIABLE","Can't open reliable port (endpoint 0x%x, client %s - %d)","The ICC negotiation process cannot open a reliable port to the endpoint for the ISSU client. The ISSU client might not be able to negotiate.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","OPEN_PORT_UNRELIABLE","Can't open unreliable port (endpoint 0x%x, client %d)","The ICC negotiation process cannot open an unreliable port to the endpoint for the ISSU client. The ISSU client might not be able to negotiate.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","OUT_OF_MEMORY","System is running out of memory","There is not enough available memory in the system.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","PCOL_INCONSISTENT_PID","Inconsistent ICC Nego process collector process id (client %d, endpoint 0x%x)","The ICC negotiation process collector process ID is inconsistent.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","PROCESS_CREATE","Failed to create ICC nego process","The ICC negotiation failed to create a process to handle the messages.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","PROCESS_KILL_INTERNAL","Internal process kill failed (pid %d, process collector pid %d)","The ICC negotiation process failed to terminate an internal process due to an inconsistent process ID.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","PROC_LEVEL_MSG_GENERIC","Invalid process level message in the generic process (client %d, level %d)","The level of messages for the ICC negotiation process is invalid in the generic process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","PROC_LEVEL_MSG_INTERRUPT","Invalid process level message in the ICC interrupt (client %d, level %d)","The level of messages for the ICC negotiation process is invalid in the ICC interrupt.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","SEND_UK","Failed to send unique key to process (client %d, endpoint 0x%x","The ICC negotiation process failed to send the unique key to the new client process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","TIMER_NOT_AWAKE","ICC Nego pcol timer was not awake when getting a timer event","The ICC negotiation process collector timer was not awake when receiving a timer event.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","TIMER_NOT_RUNNING","ICC Nego pcol timer was not running when getting a timer event","The ICC negotiation process collector timer was not running when getting a timer event.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_NEGO","3","WATCHED_QUEUE_CREATION","Failed to create the watched queue","The ICC negotiation process could not create the watched queue.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICC_ISSU_TAGGING","3","NOT_XFORM","Untransformed message detected (class:%d, request:%d, sender:%x)","During runtime, the intercard communication (ICC) ISSU tagging process detected an untransformed ICC message. This message must be transformed or suspended to support ISSU.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ICPM","3","ALLOC","Cannot alloc %s","An attempt to allocate an ICPM data structure failed because of a low memory condition.","Reduce other system activitiy to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"IDBINDEX_SYNC","3","IDBINDEX_ASSIGN","Failed to assign an index to IDB type %d, for interface","An interface index cannot be allocated for this interface due to an internal software error. This is an unrecoverable error that results in this interface not being usable for traffic.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBINDEX_SYNC","3","IDBINDEX_ENTRY_MISMATCH","An interface index mismatched its active table entry:","An interface index was found which did not match the active interface descriptor block (IDB) index table entry with the corresponding synchronization key. This condition is due to an internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBINDEX_SYNC","3","IDBINDEX_LINK","Driver for IDB type '%d' changed the Identity of interface","The interface index table cannot be updated with the new identity provided for this interface due to an internal software error. The driver might not have deleted the old identity first, or the driver might have accidentally changed the identity.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBINDEX_SYNC","3","IDBINDEX_RETRIEVE","Cannot retrieve if-index for this interface:","The interface index number was not found in the interface index table for the interface specified in the error message. This condition might have been caused by the interface index number not being properly synchronized by the primary processor card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBINDEX_SYNC","3","INIT_ERR","%s","The interface index synchronization ISSU client has an initialization error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBINDEX_SYNC","3","IPC_ERR","%s: %s.","The interface index synchronization interprocess communication (IPC) session has an error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBINDEX_SYNC","3","ISSU_ERR","%s%s, rc=%d","The interface index synchronization ISSU client has an error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBINDEX_SYNC","3","RF_ERR","%s %d.","An error occurred in the interface index synchronization of the redundancy facility (RF) client.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBINDEX_SYNC","3","TRANSFORM","Require IF-Index ISSU transformation function %s %s","The interface index synchronization process has identified a missing ISSU transformation function. This condition may lead to misoperation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBINDEX_SYNC","3","VALIDATE","Cannot validate if-index for this interface:","The identity of this interface could not be validated against the stored identity within the interface descriptor block (IDB) index table. This condition probably occurred due to the identity of the IDB changing without first explicitly unlinking the previous identity.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBINDEX_SYNC","4","RESERVE","Failed to lookup existing ifindex for an interface on the Standby, allocating a new ifindex from the Active (ifindex=%d, idbtype=%s)","A lookup failure occurred for an interface on the standby unit. An attempt was made to resolve the issue by reserving a new interface index on the active unit. If this failure was caused by a defect in the key encoding, then traffic may stop on this interface if the system switches over.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBINDEX_SYNC","4","TRUNCATE","Overflow in %s when encoding interface sync key, got %d maximum is %d","During the creation of a unique synchronization key to represent an interface, one of the attributes making up the key was truncated to fit in the allocated space in the key. This condition might lead to overlapping key allocations, which would cause an error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBINDEX_SYNC_KEY","3","UNKNOWN_TYPE","Interface type is unknown and cannot be synced:","An internal software error has occurred related to the interface descriptor block (IDB) key synchronization.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBMAN","3","AGGPORTMISMATCH","%s: %s(%d / %d) does match internal slot/port state %s(%d / %d)","There is an internal error that caused an invalid aggregate port to be used by the software.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBMAN","3","DELETEDAGGPORT","%s(%d / %d) Group %d has been deleted, but is being reused.","There is an internal error that caused an interface that has been deleted to be reused for a new aggregate port.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBMAN","3","INVALIDAGGPORTBANDWIDTH","%s(%d / %d) has an invalid bandwidth value of %d","There is an internal error that caused an invalid bandwidth to be used for an aggregate port.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBMAN","3","INVALIDPORT","%s: trying to use invalid port number %d ( Max %d )","There is an internal error that caused an invalid port numer to be used by the software.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBMAN","3","INVALIDVLAN","%s: trying to use invalid Vlan %d","There is an internal error that caused an invalid Vlan to be used by the software.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBMAN","3","NOTANAGGPORT","%s( %d / %d ) is not an aggregate port","There is an internal error that caused an interface that is not an aggregate port to be used for aggregate port operations","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBMAN","3","PORTNOTINAGGPORT","%s(%d / %d) is not present in Aggport %s(%d / %d)","There is an internal error that caused an invalid port to be referred to be part of an aggregate port.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBMAN","3","UNAVAILABLE","%s( %d / %d ) is not an aggregate port","There is an internal error that caused an interface that is not an aggregate port to be used for aggregate port operations","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBMAN","3","UNAVAILABLE","%s(%d / %d) Group %d has been deleted, but is being reused.","There is an internal error that caused an interface that has been deleted to be reused for a new aggregate port.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBMAN","3","UNAVAILABLE","%s(%d / %d) has an invalid bandwidth value of %d","There is an internal error that caused an invalid bandwidth to be used for an aggregate port.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBMAN","3","UNAVAILABLE","%s(%d / %d) is not present in Aggport %s(%d / %d)","There is an internal error that caused an invalid port to be referred to be part of an aggregate port.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBMAN","3","UNAVAILABLE","%s: %s(%d / %d) does match internal slot/port state %s(%d / %d)","There is an internal error that caused an invalid aggregate port to be used by the software.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBMAN","3","UNAVAILABLE","%s: Vlan %d is in use by %s","Each L3 interface has a Vlan associated with it. This message indicates that the Vlan associated with the interface is being used by some other L3 Interface, which is not anticipated to happen","This is an informational message only, no action is required."
"IDBMAN","3","UNAVAILABLE","%s: Vlan %d not set since it already has Vlan %d","There is an internal error that caused an interface to not have its Vlan set to the requested value","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBMAN","3","UNAVAILABLE","%s: trying to use invalid Vlan %d","There is an internal error that caused an invalid Vlan to be used by the software.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBMAN","3","UNAVAILABLE","%s: trying to use invalid port number %d ( Max %d )","There is an internal error that caused an invalid port numer to be used by the software.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBMAN","3","VLANINUSE","%s: Vlan %d is in use by %s","Each L3 interface has a Vlan associated with it. This message indicates that the Vlan associated with the interface is being used by some other L3 Interface, which is not anticipated to happen","The standby supervisor engine is reloaded automatically to recover from the problem. If the standby supervisor engine does not recover, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBMAN","3","VLANNOTSET","%s: Vlan %d not set since it already has Vlan %d","There is an internal error that caused an interface to not have its Vlan set to the requested value","The standby supervisor engine is reloaded automatically to recover from the problem. If the standby supervisor engine does not recover, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBMAN","4","ACTIVEPORTSINAGGPORT","%s( %d / %d ) has %d active ports, but is being removed","There is an internal error that caused an aggregate port with active ports to be removed","The standby supervisor engine is reloaded automatically to recover from the problem. If the standby supervisor engine does not recover, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBMAN","4","CONFIG_WRITE_FAIL","FFailed to generate configuration for interface [chars]","The system failed to generate a configuration for the specified interface because of a problem with the file system. The active and standby supervisor engines will have configurations that do not match.","The standby supervisor engine is reloaded automatically to recover from the problem. If the standby supervisor engine does not recover, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBMAN","4","IDB_LIMIT","Maxinum interface count reached the limit of [dec]([dec]+[dec]). Module is disabled.","The number of interfaces has reached the maximum limit and the module has been disabled.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDBMAN","6","UNAVAILABLE","Vlan %d is mapped to %s","Informational message indicating that the given Vlan is mapped to the given interface","No action is required."
"IDBMAN","6","VLANMAPPED","Vlan %d is mapped to %s","Informational message indicating that the given Vlan is mapped to the given interface","No action is required."
"IDB_IDENTITY","3","UNAVAILABLE","Memory allocation failure for HWIDB type %d","A memory allocation failure occured when trying to allocate the identity for this HWIDB. This HWIDB will not be allocated an IF Index which will prevent it from being used for forwarding data.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDMGR","3","UNAVAILABLE","%s","A malloc failure occured in ID Manager.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDMGR","3","UNAVAILABLE","%s","An id_get attempted at interrupt level.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDMGR","3","UNAVAILABLE","bad id in %s (id: 0x%llX)","An ID Manager error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDMGR","3","UNAVAILABLE","bad new ID table size","A bad new table request to ID Manager occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IDPROM","3","UNAVAILABLE","Corrupt or missing IDPROM Checksum","This message indicates the IDPROM of this unit could not be accessed or was found to be corrupt, either due to a hardware problem or manufacturing problem.","Report this error to your technical support representative."
"IDPROM","4","UNAVAILABLE","Corrupt or missing IDPROM Magic number","This message indicates the IDPROM of this unit could not be accessed or was found to be corrupt, either due to a hardware problem or manufacturing problem.","Report this error to your technical support representative."
"IDS","4","ICMP_ECHO_REPLY_SIG","Sig:2000:ICMP Echo Reply - from %i to %i","Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 0 (Echo Reply).","This is extremely common network traffic. Suspicion should be "
"IDS","4","ICMP_ECHO_REPLY_SIG","Sig:2000:ICMP Echo Reply - from %i to %i","Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 0 (Echo Reply).","This is extremely common network traffic. Suspicion should beraised when a large number of these packets are found on the network. If nolegitimate reason for this traffic can be identified, prudent securitypractices would suggest that the source be shunned."
"IDS","4","ICMP_ECHO_SIG","Sig:2004:ICMP Echo Request - from %i to %i","Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 8 (Echo Request). Commonly used to perform reconnaissance sweeps. Suspicion should be raised when a large number of these packets are found on the network.","The ICMP Echo Request is issued by the source to determine if the destination is ''alive''. When the destination receives the request it will reply with an ICMP Echo Reply. This request/reply pair is most commonly implemented via the ''ping'' utility. Many network management tools use this utility or some derivative. This is extremely common network raffic. Suspicion should be raised when a large number of these packets are found on the network. If no legitimate reason for this traffic can be identified, prudent security practices would suggest that the source be shunned."
"IDS","4","ICMP_FRAGMENT_SIG","Sig:2150:Fragmented ICMP Traffic - from %i to %i","Triggers when a IP datagram is received with the protocol field of the IP header set to 1 (ICMP) and either the more fragments flag is set to 1 (ICMP) or there is an offset indicated in the offset field.","IP datagrams may be fragmented normally as they are ransported across the network, but ICMP is rarely fragmented. The traffic should be investigated. If no legitimate reason for the fragmentation can be found and especially if the packets seem to be originating from a single source, prudent security practices would suggest that the host be shunned."
"IDS","4","ICMP_INFO_REPLY_SIG","Sig:2010:ICMP Information Reply - from %i to %i","Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 16 (ICMP Information Reply). No known exploit exists.","This datagram type is obsolete and should not be encountered. When non-specific network traffic of this type is encountered, he most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate the user will then identify "
"IDS","4","ICMP_INFO_REPLY_SIG","Sig:2010:ICMP Information Reply - from %i to %i","Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 16 (ICMP Information Reply). No known exploit exists.","This datagram type is obsolete and should not beencountered. When non-specific network traffic of this type is encountered,the most prudent action from a security perspective is to shun or disallowit. If the source of this traffic is legitimate the user will then identifyhim or herself."
"IDS","4","ICMP_INFO_SIG","Sig:2009:ICMP Information Request - from %i to %i","Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 15 (Information Request).","This datagram type is obsolete and should not be encountered. When non-specific network traffic of this type is encountered, he most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate the user will then identify "
"IDS","4","ICMP_INFO_SIG","Sig:2009:ICMP Information Request - from %i to %i","Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 15 (Information Request).","This datagram type is obsolete and should not beencountered. When non-specific network traffic of this type is encountered,the most prudent action from a security perspective is to shun or disallowit. If the source of this traffic is legitimate the user will then identifyhim or herself."
"IDS","4","ICMP_MASK_REPLY_SIG","Sig:2012:ICMP Address Mask Reply - from %i to %i","Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 18 (Address Mask Reply). No known exploits incorporate this option.","The ICMP Address Mask Request/Reply pair can be used to determine the sublet mask used on the network. The requesting system issues he Address Mask Request bound for a destination, the destination system "
"IDS","4","ICMP_MASK_REPLY_SIG","Sig:2012:ICMP Address Mask Reply - from %i to %i","Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 18 (Address Mask Reply). No known exploits incorporate this option.","The ICMP Address Mask Request/Reply pair can be used todetermine the sublet mask used on the network. The requesting system issuesthe Address Mask Request bound for a destination, the destination systemresponds with an Address Mask Reply message. This is normal network traffic,but is uncommon on most networks. Suspicion should be raised when a largenumber of these packets are found on the network. If no legitimate reasonfor this traffic can be identified prudent security practices would suggestthat the source be shunned."
"IDS","4","ICMP_MASK_SIG","Sig:2011:ICMP Address Mask Request - from %i to %i","Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 17 (Address Mask Request). ICMP Address Mask Requests could be used to perform reconnaissance sweeps of networks.","The ICMP Address Mask Request/Reply pair can be used to determine the subnet mask used on the network. The requesting system issues he Address Mask Request bound for a destination, the destination system "
"IDS","4","ICMP_MASK_SIG","Sig:2011:ICMP Address Mask Request - from %i to %i","Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 17 (Address Mask Request). ICMP Address Mask Requests could be used to perform reconnaissance sweeps of networks.","The ICMP Address Mask Request/Reply pair can be used todetermine the subnet mask used on the network. The requesting system issuesthe Address Mask Request bound for a destination, the destination systemresponds with an Address Mask Reply message. This is normal network traffic,but is uncommon on most networks. Suspicion should be raised when a largenumber of these packets are found on the network. If no legitimate reasonfor this traffic can be identified prudent security practices would suggestthat the source be shunned."
"IDS","4","ICMP_PARAMPROB_SIG","Sig:2006:ICMP Parameter Problem on Datagram - from %i to %i","Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 12 (Parameter Problem on Datagram). No known exploits incorporate this option.","ICMP Parameter Problem datagrams are issued when a router "
"IDS","4","ICMP_PARAMPROB_SIG","Sig:2006:ICMP Parameter Problem on Datagram - from %i to %i","Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 12 (Parameter Problem on Datagram). No known exploits incorporate this option.","ICMP Parameter Problem datagrams are issued when a routerhas had to drop a datagram because it was malformed. This is a normal andnecessary type of network traffic. Large numbers of this datagram type onthe network are indicative of network difficulties or may be indicative ofhostile actions. If no network problems can be identified to account for thetraffic prudent security practices would suggest that the source be shunned."
"IDS","4","ICMP_PING_OF_DEATH_SIG","Sig:2154:ICMP Ping of Death Attack - from %i to %i","Triggers when a IP datagram is received with the protocol field of the IP header set to 1(ICMP), the Last Fragment bit is set, and ( IP offset * 8 ) + ( IP data length) 65535 that is to say, the IP offset (which represents the starting position of this fragment in the original packet, and which is in 8 byte units) plus the rest of the packet is greater than the maximum size for an IP packet. This indicates a denial of service attack.","This indicates a denial of service attack. It is likely that the source address has been spoofed making shunning ineffective"
"IDS","4","ICMP_PING_OF_DEATH_SIG","Sig:2154:ICMP Ping of Death Attack - from %i to %i","Triggers when a IP datagram is received with the protocol field of the IP header set to 1(ICMP), the Last Fragment bit is set, and ( IP offset * 8 ) + ( IP data length) 65535 that is to say, the IP offset (which represents the starting position of this fragment in the original packet, and which is in 8 byte units) plus the rest of the packet isgreater than the maximum size for an IP packet. This indicates a denial of service attack.","This indicates a denial of service attack. It is likely that the sourceaddress has been spoofed making shunning ineffective"
"IDS","4","ICMP_REDIRECT_SIG","Sig:2003:ICMP Redirect - from %i to %i","Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 5 (Redirect).","The redirect message may be issued from a router to inform a host of a better route to a requested destination. The host then updates its routing table to include this route. This method of updating routing ables is an uncommon practice today. When non-specific network traffic of his type is encountered, the most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate the user will then identify him or herself."
"IDS","4","ICMP_REDIRECT_SIG","Sig:2003:ICMP Redirect - from %i to %i","Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 5 (Redirect).","The redirect message may be issued from a router to informa host of a better route to a requested destination. The host then updatesits routing table to include this route. This method of updating routingtables is an uncommon practice today. When non-specific network traffic ofthis type is encountered, the most prudent action from a securityperspective is to shun or disallow it. If the source of this traffic islegitimate the user will then identify him or herself."
"IDS","4","ICMP_SOURCEQUENCH_SIG","Sig:2002:ICMP Source Quench - from %i to %i","Triggers when an IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 4 (Source Quench). This datagram may be used in network management to provide congestion control. Large numbers of this datagram type on the network are indicative of network difficulties or may be indicative of hostile actions.","This datagram may be used in network management to provide congestion control. A source quench packet will be issued when a router is beginning to lose packets due to the transmission rate of a source. The source quench is a request to the source to reduce the rate of datagram ransmission. This datagram type is rarely if ever seen on networks and some systems do not even support it. Large numbers of this datagram type on the etwork are indicative of network difficulties or may be indicative of "
"IDS","4","ICMP_SOURCEQUENCH_SIG","Sig:2002:ICMP Source Quench - from %i to %i","Triggers when an IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 4 (Source Quench). This datagram may be used in network management to provide congestion control. Large numbers of this datagram type on the network are indicative of network difficulties or may be indicative of hostile actions.","This datagram may be used in network management to providecongestion control. A source quench packet will be issued when a router isbeginning to lose packets due to the transmission rate of a source. Thesource quench is a request to the source to reduce the rate of datagramtransmission. This datagram type is rarely if ever seen on networks and somesystems do not even support it. Large numbers of this datagram type on thenetwork are indicative of network difficulties or may be indicative ofhostile actions. If no network problems can be identified to account for thetraffic prudent security practices would suggest that the source be shunned."
"IDS","4","ICMP_TIME_REPLY_SIG","Sig:2008:ICMP Timestamp Reply - from %i to %i","Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the type field in the ICMP header set to 14 (Timestamp Reply). No known exploits incorporate this option.","The ICMP Timestamp Request/Reply pair can be used to synchronize system clocks on the network. The requesting system issues the Timestamp Request bound for a destination, the destination system responds with a Timestamp Reply message. This is normal network traffic, but is uncommon on most networks. Suspicion should be raised when a large number of hese packets are found on the network. If no legitimate reason for this raffic can be identified prudent security practices would suggest that the source be shunned."
"IDS","4","ICMP_TIME_SIG","Sig:2007:ICMP Timestamp Request - from %i to %i","Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 13 (Timestamp Request). ICMP Timestamp Requests could be used to perform reconnaissance sweeps of networks. No known exploits incorporate this option.","The ICMP Timestamp Request/Reply pair can be used to synchronize system clocks on the network. The requesting system issues the Timestamp Request bound for a destination, the destination system responds with a Timestamp Reply message. This is normal network traffic, but is uncommon on most networks. Suspicion should be raised when a large number of hese packets are found on the network. If no legitimate reason for this raffic can be identified prudent security practices would suggest that the source be shunned."
"IDS","4","ICMP_TIMXCEED_SIG","Sig:2005:ICMP Time Exceeded for a Datagram - from %i to %i","Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 11(Time Exceeded for a Datagram). No known exploits incorporate this option.","ICMP Time Exceeded datagrams are issued when a router has "
"IDS","4","ICMP_TIMXCEED_SIG","Sig:2005:ICMP Time Exceeded for a Datagram - from %i to %i","Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 11(Time Exceeded for a Datagram). No known exploits incorporate this option.","ICMP Time Exceeded datagrams are issued when a router hashad to drop a datagram whose Time to Live (TTL) flag has expired. This is anormal and necessary type of network traffic. Large numbers of this datagramtype on the network are indicative of network difficulties or may beindicative of hostile actions. If no network problems can be identified toaccount for the traffic prudent security practices would suggest that thesource be shunned."
"IDS","4","ICMP_TOOLARGE_SIG","Sig:2151:Large ICMP Traffic - from %i to %i","While it is possible to receive ICMP datagrams that have a size greater than 1024 bytes, this is a highly unusual occurrence that warrants investigation.","While it is possible to receive ICMP datagrams that have a size greater than 1024 bytes, this is a highly unusual occurrence that warrants investigation. If no legitimate reason for the large packet size can be found and especially if the packets seem to be originating from a single source, prudent security practices would suggest that the host be shunned."
"IDS","4","ICMP_TOOLARGE_SIG","Sig:2151:Large ICMP Traffic - from %i to %i","While it is possible to receive ICMP datagrams that have a size greater than 1024 bytes, this is a highly unusual occurrence that warrants investigation.","While it is possible to receive ICMP datagrams that have asize greater than 1024 bytes, this is a highly unusual occurrence thatwarrants investigation. If no legitimate reason for the large packet sizecan be found and especially if the packets seem to be originating from asingle source, prudent security practices would suggest that the host beshunned."
"IDS","4","ICMP_UNREACH_SIG","Sig:2001:ICMP Host Unreachable - from %i to %i","Triggers when an IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 3 (Host Unreachable). This is the common responseLarge numbers of this datagram type on the network are indicative of network difficulties or may be indicative of hostile actions.","This is the common response provided to a client when there is no path available to the requested host. This is a very common type of etwork traffic. Large numbers of this datagram type on the network are indicative of network difficulties or may be indicative of hostile actions. If no network problems can be identified to account for the traffic prudent security practices would suggest that the source be shunned."
"IDS","4","IPFRAG_ATTACK_SIG","Sig:1100:IP Fragment Attack - from %i to %i","Triggers when any IP datagram is received with the 'more fragments' flag set to 1 or if there is an offset indicated in the offset field.","IP datagrams may be fragmented normally as they are transported across the network. This is not uncommon, but is unusual enough that the traffic should be investigated. This is especially important if the network is protected by a packet filtering firewall."
"IDS","4","IPOPTS_BAD_SIG","Sig:1000:Bad IP Option List - from %i to %i","Triggers on receipt of an IP datagram where the list of IP options in the IP datagram header is incomplete or malformed. No known exploits purposely incorporate this option.","There is no legitimate use for malformed datagrams. This may be indicative of systems that are experiencing problems with their kernel or NIC cards. This is unusual traffic and warrants investigation. When non-specific network traffic of this ype is encountered, the most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate he user will then identify him or herself."
"IDS","4","IPOPT_LSRR_SIG","Sig:1004:IP options-Loose Source Route - from %i to %i","Triggers on receipt of an IP datagram where the IP option list for the datagram includes option 3 (Loose Source Route). This option may be misused to defeat authentication mechanisms that rely on IP addresses as their basis for trust relationships.","While network troubleshooting may require the legitimate use of this feature, this type of traffic is rarely if ever oted and should comprise much less than 1% of network traffic. Small amounts of source routed traffic most probably indicates that a etwork problem is being investigated. Large amounts of source "
"IDS","4","IPOPT_RR_SIG","Sig:1001:IP options-Record Packet Route - from %i to %i","The IP options list contains one or more options that perform various network management or debugging tasks. This alarm may indicate a reconnaissance attack is in progress against your network.","While network troubleshooting may require he legitimate use of this feature, this is unusual traffic that warrants investigation. When non-specific network traffic of this type is encountered, the most prudent action from a security perspective is o shun or disallow it. If the source of this traffic is legitimate he user will then identify him or herself."
"IDS","4","IPOPT_RR_SIG","Sig:1001:IP options-Record Packet Route - from %i to %i","The IP options list contains one or more options that perform various network management or debugging tasks. This alarm may indicate a reconnaissance attack is in progress against your network.","While network troubleshooting may require the legitimate use of this feature, this is unusual traffic that warrantsinvestigation. When non-specific network traffic of this type is encountered, the most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate the user will then identify him or herself."
"IDS","4","IPOPT_SATID_SIG","Sig:1005:IP options-SATNET ID - from %i to %i","Triggers on receipt of an IP datagram where the IP option list for the datagram includes option 8 (SATNET stream identifier). No known exploit exists.","This option is obsolete and should not be encountered. When on-specific network traffic of this type is encountered, the most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate the user will then identify him or herself."
"IDS","4","IPOPT_SECURITY_SIG","Sig:1003:IP options-Provide s,c,h,tcc - from %i to %i","Triggers on receipt of an IP datagram where the IP option list for the datagram includes option 2. No known exploit exists.","This signature will trigger if you have implemented IP security options on your network However, this is "
"IDS","4","IPOPT_SSRR_SIG","Sig:1006:IP options-Strict Source Route - from %i to %i","Triggers on receipt of an IP datagram in which the IP option list for the datagram includes option 2 (Strict Source Routing). This option may be misused to defeat authentication mechanisms that rely on IP addresses as their basis for trust relationships.","While network troubleshooting may require the legitimate use of this feature, this type of traffic is rarely if ever noted and should comprise much less than 1% of network traffic. Small amounts of source "
"IDS","4","IPOPT_SSRR_SIG","Sig:1006:IP options-Strict Source Route - from %i to %i","Triggers on receipt of an IP datagram in which the IP option list for the datagram includes option 2 (Strict Source Routing). This option may be misused to defeat authentication mechanisms that rely on IP addresses as their basis for trust relationships.","While network troubleshooting may require the legitimate use of thisfeature, this type of traffic is rarely if ever noted and should comprise much less than 1% of network traffic. Small amounts of source routed traffic most probably indicates that a network problem is being investigated. Large amounts of source routed traffic is more suspicious and a thorough investigation of the source and reason is indicated."
"IDS","4","IPOPT_TS_SIG","Sig:1002:IP options-TimeStamp - from %i to %i","Triggers on receipt of an IP datagram where the IP option list for the datagram includes option 4 (Timestamp). This alarm indicates that a reconnaissance attack may be in progress against your network.","While network troubleshooting may require he legitimate use of this feature, this is unusual traffic that warrants investigation. When non-specific network traffic of this type is encountered, the most prudent action from a security perspective is o shun or disallow it. If the source of this traffic is legitimate he user will then identify him or herself."
"IDS","4","IP_IMPOSSIBLE_SIG","Sig:1102:Impossible IP Packet - from %i to %i","This triggers when an IP packet arrives with source equal to destination address. This signature will catch the so-called Land Attack.","This should never occur in legitimate traffic."
"IDS","4","IP_UNKNOWN_PROTO_SIG","Sig:1101:Unknown IP Protocol - from %i to %i","Triggers when an IP datagram is received with the protocol field set to 101 or greater. The use of these protocol types is highly unusual and should be investigated.","Locally developed protocols that may use hese protocol types will trigger the signature. The use of these protocol types is highly unusual and should be investigated. When on-specific network traffic of this type is encountered, the most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate the user will then identify him or herself."
"IDS","4","LOST_CONNECT","Connection to HostID:%u OrgID:%u","Triggers when a connection drops and there is no previous connection.","This message indicates that the IDS cannot communicate with the Director. Check connectivity to the Director and check Postoffice configuration on both the router and the Director."
"IDS","4","RPC_CALLIT_REQUEST","Sig:6103:Proxied RPC Request - from %i to %i","Triggers when a proxied RPC request is sent to the portmapper of a target host.","If this procedure is allowed on your network those users hat employ it will trigger the signature. This may be a serious attempt at gaining unauthorized access and if the source of the attempt is not within your network they should be shunned."
"IDS","4","RPC_DUMP_REQUEST","Sig:6102:RPC Dump - from %i to %i","Triggers when an RPC dump request isissued to a target host.","This is a common procedure performed by many system administrators and wary users to determine which RPC services are being offered. Executing this procedure is most likely due to curiosity on the part of a novice user or a system administrator performing system maintenance. If upon investigation no valid user can be associated with this event, prudent security practices would suggest shunning the source."
"IDS","4","RPC_DUMP_REQUEST","Sig:6102:RPC Dump - from %i to %i","Triggers when an RPC dump request isissued to a target host.","This is a common procedure performed by many systemadministrators and wary users to determine which RPC services are beingoffered. Executing this procedure is most likely due to curiosity on thepart of a novice user or a system administrator performing systemmaintenance. If upon investigation no valid user can be associated with thisevent, prudent security practices would suggest shunning the source."
"IDS","4","RPC_PORTREQ_MOUNTD","Sig:6155:RPC mountd Portmap Request - from %i to %i","Triggers when a request is made to the portmapper for the mount daemon (mountd) port.","If this procedure is allowed on your network those users hat employ it will trigger the signature. This may be a serious attempt at gaining unauthorized access and if the source of the attempt is not within your network they should be shunned."
"IDS","4","RPC_PORTREQ_REXD","Sig:6175: RPC rexd Portmap Request - from %i to %i","Triggers when a request is made to the portmapper for the remote execution daemon (rexd) port. The remote execution daemon is the server esponsible for remote program execution. This may be indicative of an attempt o gain unauthorized access to system resources.","If this procedure is allowed on your network, those users who employ it will trigger the signature. This may be a serious attempt at gaining unauthorized access and if the source of the attempt is not within your network, it should be shunned."
"IDS","4","RPC_PORTREQ_REXD","Sig:6175: RPC rexd Portmap Request - from %i to %i","Triggers when a request is made to the portmapper for the remote execution daemon (rexd) port. The remote execution daemon is the serverresponsible for remote program execution. This may be indicative of an attempt to gain unauthorized access to system resources.","If this procedure is allowed on your network, those userswho employ it will trigger the signature. This may be a serious attempt atgaining unauthorized access and if the source of the attempt is not withinyour network, it should be shunned."
"IDS","4","RPC_PORTREQ_YPBIND","Sig:6151:RPC ypbind Portmap Request - from %i to %i","Triggers when a request is made to the portmapper for the YP bind daemon (ypbind) port.","If this procedure is allowed on your network those users hat employ it will trigger the signature. This may be a serious attempt at gaining unauthorized access and if the source of the attempt is not within your network they should be shunned."
"IDS","4","RPC_PORTREQ_YPPASSWDD","Sig:6152:RPC ypbind yppasswdd Portmap Request - from %i to %i","Triggers when a request is made to the portmapper for the YP password daemon (yppasswdd) port.","If this procedure is allowed on your network those users hat employ it will trigger the signature. This may be a serious attempt at gaining unauthorized access and if the source of the attempt is not within your network they should be shunned."
"IDS","4","RPC_PORTREQ_YPPASSWDD","Sig:6152:RPC ypbind yppasswdd Portmap Request - from %i to %i","Triggers when a request is made to the portmapper for the YP password daemon (yppasswdd) port.","If this procedure is allowed on your network those usersthat employ it will trigger the signature. This may be a serious attempt atgaining unauthorized access and if the source of the attempt is not withinyour network they should be shunned."
"IDS","4","RPC_PORTREQ_YPSERV","Sig:6150:RPC ypserv Portmap Request - from %i to %i","Triggers when a request is made to the portmapper for the YP server daemon (ypserv) port.","If this procedure is allowed on your network those users hat employ it will trigger the signature. This may be a serious attempt at gaining unauthorized access and if the source of the attempt is not within your network they should be shunned."
"IDS","4","RPC_PORTREQ_YPUPDATED","Sig:6153:RPC ypupdated Portmap Request - from %i to %i","Triggers when a request is made to the portmapper for the YP update daemon (ypupdated) port.","If this procedure is allowed on your network those users hat employ it will trigger the signature. This may be a serious attempt at gaining unauthorized access and if the source of the attempt is not within your network they should be shunned."
"IDS","4","RPC_PORTREQ_YPXFRD","Sig:6154:RPC ypxfrd Portmap Request - from %i to %i","Triggers when a request is made to the portmapper for the YP transfer daemon (ypxfrd) port.","If this procedure is allowed on your network those users hat employ it will trigger the signature. This may be a serious attempt at gaining unauthorized access and if the source of the attempt is not within your network they should be shunned."
"IDS","4","RPC_REXD_REQUEST","Sig:6180:RPC rexd Attempt - from %i to %i","Triggers when a call to the rexd program is made. The remote execution daemon is the server responsible for remote program execution. This may be indicative of an attempt to gain unauthorized access to system esources.","If this service is being used legitimately, this alarm will fire. For security purposes, this service really should not be used."
"IDS","4","RPC_REXD_REQUEST","Sig:6180:RPC rexd Attempt - from %i to %i","Triggers when a call to the rexd program is made. The remote execution daemon is the server responsible for remote program execution. Thismay be indicative of an attempt to gain unauthorized access to system resources.","If this service is being used legitimately, this alarm willfire. For security purposes, this service really should not be used."
"IDS","4","RPC_SET_REQUEST","Sig:6100:RPC Port Registration - from %i to %i","Triggers when attempts are made to register new RPC services on a target host.","No benign triggers exist for this signature. Prudent security practices suggest that the source of this attempt should be shunned."
"IDS","4","UNAVAILABLE","Connection to HostID:%u OrgID:%u","Triggers when a connection drops and there is no previous connection.","This message indicates that the IDS cannot communicate with the Director. Check connectivity to the Director and check Postofficeconfiguration on both the router and the Director."
"IDS","4","UNAVAILABLE","Invalid SMTP command - from %i to %i","Triggers on an invalid SMTP command in the SMTP connection. This message indicates that a suspicious violation was detetected that may be an attack to the mail server system.","This is unusual traffic and may warrant investigation."
"IDS","4","UNAVAILABLE","Sig:1000:Bad IP Option List - from %i to %i","Triggers on receipt of an IP datagram where the list of IP options in the IP datagram header is incomplete or malformed. No known exploits purposely incorporate this option.","There is no legitimate use for malformed datagrams. This may be indicative of systems that are experiencing problems with their kernel or NIC cards. This is unusual traffic and warrants investigation. When non-specific network traffic of this type is encountered, the most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate the user will then identify him or herself."
"IDS","4","UNAVAILABLE","Sig:1001:IP options-Record Packet Route - from %i to %i","The IP options list contains one or more options that perform various network management or debugging tasks. This alarm may indicate a reconnaissance attack is in progress against your network.","While network troubleshooting may require the legitimate use of this feature, this is unusual traffic that warrantsinvestigation. When non-specific network traffic of this type is encountered, the most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate the user will then identify him or herself."
"IDS","4","UNAVAILABLE","Sig:1002:IP options-TimeStamp - from %i to %i","Triggers on receipt of an IP datagram where the IP option list for the datagram includes option 4 (Timestamp). This alarm indicates that a reconnaissance attack may be in progress against your network.","While network troubleshooting may require the legitimate use of this feature, this is unusual traffic that warrantsinvestigation. When non-specific network traffic of this type is encountered, the most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate the user will then identify him or herself."
"IDS","4","UNAVAILABLE","Sig:1003:IP options-Provide s,c,h,tcc - from %i to %i","Triggers on receipt of an IP datagram where the IP option list for the datagram includes option 2. No known exploit exists.","This signature will trigger if you have implemented IP security options on your network However, this is rarely, if ever, implemented . When non-specific network traffic of this type is encountered, the most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate the user will then identify him or herself."
"IDS","4","UNAVAILABLE","Sig:1004:IP options-Loose Source Route - from %i to %i","Triggers on receipt of an IP datagram where the IP option list for the datagram includes option 3 (Loose Source Route). This option may be misused to defeat authentication mechanisms that rely on IP addresses as their basis for trust relationships.","While network troubleshooting may require the legitimate use of this feature, this type of traffic is rarely if ever noted and should comprise much less than 1% of network traffic. Small amounts of source routed traffic most probably indicates that a network problem is being investigated. Large amounts of source routed traffic is more suspicious and a thorough investigation of the source and reason is indicated."
"IDS","4","UNAVAILABLE","Sig:1005:IP options-SATNET ID - from %i to %i","Triggers on receipt of an IP datagram where the IP option list for the datagram includes option 8 (SATNET stream identifier). No known exploit exists.","This option is obsolete and should not be encountered. Whennon-specific network traffic of this type is encountered, the most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate the user will then identify him or herself."
"IDS","4","UNAVAILABLE","Sig:1006:IP options-Strict Source Route - from %i to %i","Triggers on receipt of an IP datagram in which the IP option list for the datagram includes option 2 (Strict Source Routing). This option may be misused to defeat authentication mechanisms that rely on IP addresses as their basis for trust relationships.","While network troubleshooting may require the legitimate use of thisfeature, this type of traffic is rarely if ever noted and should comprise much less than 1% of network traffic. Small amounts of source routed traffic most probably indicates that a network problem is being investigated. Large amounts of source routed traffic is more suspicious and a thorough investigation of the source and reason is indicated."
"IDS","4","UNAVAILABLE","Sig:1100:IP Fragment Attack - from %i to %i","Triggers when any IP datagram is received with the 'more fragments' flag set to 1 or if there is an offset indicated in the offset field.","IP datagrams may be fragmented normally as theyare transported across the network. This is not uncommon, but is unusual enough that the traffic should be investigated. This is especially important if the network is protected by a packet filtering firewall."
"IDS","4","UNAVAILABLE","Sig:1101:Unknown IP Protocol - from %i to %i","Triggers when an IP datagram is received with the protocol field set to 101 or greater. The use of these protocol types is highly unusual and should be investigated.","Locally developed protocols that may use these protocol types will trigger the signature. The use of these protocol types is highly unusual and should be investigated. When non-specific network traffic of this type is encountered, the most prudent action from a security perspective is to shun or disallow it.If the source of this traffic is legitimate the user will then identify him or herself."
"IDS","4","UNAVAILABLE","Sig:1102:Impossible IP Packet - from %i to %i","This triggers when an IP packet arrives with source equal to destination address. This signature will catch the so-called Land Attack.","This should never occur in legitimate traffic."
"IDS","4","UNAVAILABLE","Sig:2000:ICMP Echo Reply - from %i to %i","Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 0 (Echo Reply).","This is extremely common network traffic. Suspicion should beraised when a large number of these packets are found on the network. If nolegitimate reason for this traffic can be identified, prudent securitypractices would suggest that the source be shunned."
"IDS","4","UNAVAILABLE","Sig:2001:ICMP Host Unreachable - from %i to %i","Triggers when an IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 3 (Host Unreachable). This is the common responseLarge numbers of this datagram type on the network are indicative of network difficulties or may be indicative of hostile actions.","This is the common response provided to a client when thereis no path available to the requested host. This is a very common type ofnetwork traffic. Large numbers of this datagram type on the network areindicative of network difficulties or may be indicative of hostile actions.If no network problems can be identified to account for the traffic prudentsecurity practices would suggest that the source be shunned."
"IDS","4","UNAVAILABLE","Sig:2002:ICMP Source Quench - from %i to %i","Triggers when an IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 4 (Source Quench). This datagram may be used in network management to provide congestion control. Large numbers of this datagram type on the network are indicative of network difficulties or may be indicative of hostile actions.","This datagram may be used in network management to providecongestion control. A source quench packet will be issued when a router isbeginning to lose packets due to the transmission rate of a source. Thesource quench is a request to the source to reduce the rate of datagramtransmission. This datagram type is rarely if ever seen on networks and somesystems do not even support it. Large numbers of this datagram type on thenetwork are indicative of network difficulties or may be indicative ofhostile actions. If no network problems can be identified to account for thetraffic prudent security practices would suggest that the source be shunned."
"IDS","4","UNAVAILABLE","Sig:2003:ICMP Redirect - from %i to %i","Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 5 (Redirect).","The redirect message may be issued from a router to informa host of a better route to a requested destination. The host then updatesits routing table to include this route. This method of updating routingtables is an uncommon practice today. When non-specific network traffic ofthis type is encountered, the most prudent action from a securityperspective is to shun or disallow it. If the source of this traffic islegitimate the user will then identify him or herself."
"IDS","4","UNAVAILABLE","Sig:2004:ICMP Echo Request - from %i to %i","Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 8 (Echo Request). Commonly used to perform reconnaissance sweeps. Suspicion should be raised when a large number of these packets are found on the network.","The ICMP Echo Request is issued by the source to determineif the destination is ''alive''. When the destination receives the requestit will reply with an ICMP Echo Reply. This request/reply pair is mostcommonly implemented via the ''ping'' utility. Many network management toolsuse this utility or some derivative. This is extremely common networktraffic. Suspicion should be raised when a large number of these packets arefound on the network. If no legitimate reason for this traffic can beidentified, prudent security practices would suggest that the source beshunned."
"IDS","4","UNAVAILABLE","Sig:2005:ICMP Time Exceeded for a Datagram - from %i to %i","Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 11(Time Exceeded for a Datagram). No known exploits incorporate this option.","ICMP Time Exceeded datagrams are issued when a router hashad to drop a datagram whose Time to Live (TTL) flag has expired. This is anormal and necessary type of network traffic. Large numbers of this datagramtype on the network are indicative of network difficulties or may beindicative of hostile actions. If no network problems can be identified toaccount for the traffic prudent security practices would suggest that thesource be shunned."
"IDS","4","UNAVAILABLE","Sig:2006:ICMP Parameter Problem on Datagram - from %i to %i","Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 12 (Parameter Problem on Datagram). No known exploits incorporate this option.","ICMP Parameter Problem datagrams are issued when a routerhas had to drop a datagram because it was malformed. This is a normal andnecessary type of network traffic. Large numbers of this datagram type onthe network are indicative of network difficulties or may be indicative ofhostile actions. If no network problems can be identified to account for thetraffic prudent security practices would suggest that the source be shunned."
"IDS","4","UNAVAILABLE","Sig:2007:ICMP Timestamp Request - from %i to %i","Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 13 (Timestamp Request). ICMP Timestamp Requests could be used to perform reconnaissance sweeps of networks. No known exploits incorporate this option.","The ICMP Timestamp Request/Reply pair can be used tosynchronize system clocks on the network. The requesting system issues theTimestamp Request bound for a destination, the destination system respondswith a Timestamp Reply message. This is normal network traffic, but isuncommon on most networks. Suspicion should be raised when a large number ofthese packets are found on the network. If no legitimate reason for thistraffic can be identified prudent security practices would suggest that thesource be shunned."
"IDS","4","UNAVAILABLE","Sig:2008:ICMP Timestamp Reply - from %i to %i","Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the type field in the ICMP header set to 14 (Timestamp Reply). No known exploits incorporate this option.","The ICMP Timestamp Request/Reply pair can be used tosynchronize system clocks on the network. The requesting system issues theTimestamp Request bound for a destination, the destination system respondswith a Timestamp Reply message. This is normal network traffic, but isuncommon on most networks. Suspicion should be raised when a large number ofthese packets are found on the network. If no legitimate reason for thistraffic can be identified prudent security practices would suggest that thesource be shunned."
"IDS","4","UNAVAILABLE","Sig:2009:ICMP Information Request - from %i to %i","Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 15 (Information Request).","This datagram type is obsolete and should not beencountered. When non-specific network traffic of this type is encountered,the most prudent action from a security perspective is to shun or disallowit. If the source of this traffic is legitimate the user will then identifyhim or herself."
"IDS","4","UNAVAILABLE","Sig:2010:ICMP Information Reply - from %i to %i","Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 16 (ICMP Information Reply). No known exploit exists.","This datagram type is obsolete and should not beencountered. When non-specific network traffic of this type is encountered,the most prudent action from a security perspective is to shun or disallowit. If the source of this traffic is legitimate the user will then identifyhim or herself."
"IDS","4","UNAVAILABLE","Sig:2011:ICMP Address Mask Request - from %i to %i","Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 17 (Address Mask Request). ICMP Address Mask Requests could be used to perform reconnaissance sweeps of networks.","The ICMP Address Mask Request/Reply pair can be used todetermine the subnet mask used on the network. The requesting system issuesthe Address Mask Request bound for a destination, the destination systemresponds with an Address Mask Reply message. This is normal network traffic,but is uncommon on most networks. Suspicion should be raised when a largenumber of these packets are found on the network. If no legitimate reasonfor this traffic can be identified prudent security practices would suggestthat the source be shunned."
"IDS","4","UNAVAILABLE","Sig:2012:ICMP Address Mask Reply - from %i to %i","Triggers when a IP datagram is received with the ''protocol'' field of the IP header set to 1 (ICMP) and the ''type'' field in the ICMP header set to 18 (Address Mask Reply). No known exploits incorporate this option.","The ICMP Address Mask Request/Reply pair can be used todetermine the sublet mask used on the network. The requesting system issuesthe Address Mask Request bound for a destination, the destination systemresponds with an Address Mask Reply message. This is normal network traffic,but is uncommon on most networks. Suspicion should be raised when a largenumber of these packets are found on the network. If no legitimate reasonfor this traffic can be identified prudent security practices would suggestthat the source be shunned."
"IDS","4","UNAVAILABLE","Sig:2150:Fragmented ICMP Traffic - from %i to %i","Triggers when a IP datagram is received with the protocol field of the IP header set to 1 (ICMP) and either the more fragments flag is set to 1 (ICMP) or there is an offset indicated in the offset field.","IP datagrams may be fragmented normally as they aretransported across the network, but ICMP is rarely fragmented. The trafficshould be investigated. If no legitimate reason for the fragmentation can befound and especially if the packets seem to be originating from a singlesource, prudent security practices would suggest that the host be shunned."
"IDS","4","UNAVAILABLE","Sig:2151:Large ICMP Traffic - from %i to %i","While it is possible to receive ICMP datagrams that have a size greater than 1024 bytes, this is a highly unusual occurrence that warrants investigation.","While it is possible to receive ICMP datagrams that have asize greater than 1024 bytes, this is a highly unusual occurrence thatwarrants investigation. If no legitimate reason for the large packet sizecan be found and especially if the packets seem to be originating from asingle source, prudent security practices would suggest that the host beshunned."
"IDS","4","UNAVAILABLE","Sig:2154:ICMP Ping of Death Attack - from %i to %i","Triggers when a IP datagram is received with the protocol field of the IP header set to 1(ICMP), the Last Fragment bit is set, and ( IP offset * 8 ) + ( IP data length) 65535 that is to say, the IP offset (which represents the starting position of this fragment in the original packet, and which is in 8 byte units) plus the rest of the packet isgreater than the maximum size for an IP packet. This indicates a denial of service attack.","This indicates a denial of service attack. It is likely that the sourceaddress has been spoofed making shunning ineffective"
"IDS","4","UNAVAILABLE","Sig:3040:TCP - No bits set in flags - from %i to %i","Triggers when a TCP packet is received with no bits set in the flags field.","There is no legitimate use for malformed TCP datagrams. This is unusual traffic and warrants investigation. Hacker tools will generateTCP packets with no bits set in the flags field in an attempt to eludeintrusion dection. When non-specific network traffic of thistype is encountered, the most prudent action from a security perspectiveis to shun or disallow it. If the source of this traffic is legitimatethe user will then identify him or herself."
"IDS","4","UNAVAILABLE","Sig:3041:TCP - SYN and FIN bits set - from %i to %i","Triggers when a TCP packet is received with both the SYN and FIN bits set in the flags field.","There is no legitimate use for malformed TCP datagrams. This is unusual traffic and warrants investigation. Hacker tools will generateTCP packets with the SYN and FIN bits set in the flags field in an attempt to eludeintrusion dection. When non-specific network traffic of thistype is encountered, the most prudent action from a security perspectiveis to shun or disallow it. If the source of this traffic is legitimatethe user will then identify him or herself."
"IDS","4","UNAVAILABLE","Sig:3042:TCP - FIN bit with no ACK bit in flags - from %i to %i","Triggers when a TCP packet is received with the FIN bit set but with no ACK bit set in the flags field.","There is no legitimate use for malformed TCP datagrams. This is unusual traffic and warrants investigation. Hacker tools will generateTCP packets with the FIN bit set but with no ACK bit set in the flags field in an attempt to elude intrusion dection. When non-specific network traffic of this type is encountered, the most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate the user will then identify him or herself."
"IDS","4","UNAVAILABLE","Sig:3050:Half-Open Syn Flood - from %i to %i","Triggers when the number of half-open TCP connections exceeds the high-water mark or the one minute high rate mark","There are no known sources that would legitimately generatethis traffic pattern. This may be indicative of some type of network problemand should be investigated. To avoid depletion of your network resources itis recommended that the source be shunned during the course of theinvestigation. If no network problems are discovered prudent securitypractices would suggest that the source be shunned permanently."
"IDS","4","UNAVAILABLE","Sig:3100:Smail Attack - from %i to %i","Triggers on the very common ''smail'' attack against e-mail servers. This attack attempts to cause e-mail servers to execute programs on the attacker's behalf.","For security reasons users should not be allowed to executeprograms via e-mail servers. This is a very serious indication that yournetwork may be under attack and the source should be shunned immediately."
"IDS","4","UNAVAILABLE","Sig:3101:Sendmail Invalid Recipient - from %i to %i","Triggers on any mail message with a ' 'pipe'' (|) symbol in the recipient field.","For security reasons users should not be allowed to executeprograms via e-mail servers. This is a very serious indication that yournetwork may be under attack and the source should be shunned immediately."
"IDS","4","UNAVAILABLE","Sig:3102:Sendmail Invalid Sender - from %i to %i","Triggers on any mail message with a ''pipe'' (|) symbol in the ''From:'' field.","For security reasons users should not be allowed to executeprograms via e-mail servers. This is a very serious indication that yournetwork may be under attack and the source should be shunned immediately."
"IDS","4","UNAVAILABLE","Sig:3103:Sendmail Reconnaissance - from %i to %i","Triggers when ''expn'' or ''vrfy'' commands are issued to the SMTP port.","These commands are commonly used to verify that a user mailaccount exists on the server or to expand an alias to determine who theactual recipients of a message may be. Users that use the EXPN and VRFYfunctions for legitimate purposes will trigger this signature. Theinformation that can be obtained is useful, but not dangerous on its own.Monitoring of future traffic for patterns of misuse is recommended."
"IDS","4","UNAVAILABLE","Sig:3104:Archaic Sendmail Attacks - from %i to %i","Triggers when ''wiz'' or ''debug'' commands are sent to the SMTP port.","There is no reason for this type of traffic to be seen onmodern networks. There is little chance that there will be any adverseeffects from someone attempting these ''old'' hacks. Prudent securitypractices would suggest that the source of this attempt be shunned."
"IDS","4","UNAVAILABLE","Sig:3105:Sendmail Decode Alias - from %i to %i","Triggers on any mail message with '': decode@'' in the header. The decode alias is used to uudecode files and is primarily implemented as a convenience for system administration.","The decode alias is used to uudecode files and is primarilyimplemented as a convenience for system administration. For securitypurposes this should not be allowed and the service should be disabled. Ifallowed, users that mail to the alias will trigger this signature. Recommendshunning of hosts that attempt to mail to this alias especially if they areoutside of your network."
"IDS","4","UNAVAILABLE","Sig:3106:Excessive Rcpt to: (SPAM) - from %i to %i","Parse for RCPT TO: in header. Alarm on threshold.","Some mailing list software may trigger this signature."
"IDS","4","UNAVAILABLE","Sig:3107:Majordomo Execute Attack - from %i to %i","A bug in the Majordomo program will allow remote users to execute arbitrary commands at the privilege level of the server.","Prudent security practices would suggest that the source of this attempt be shunned."
"IDS","4","UNAVAILABLE","Sig:3150:FTP Remote Command Execution - from %i to %i","Triggers when someone tries to execute the FTP SITE command.","The FTP Site command allows a user to execute a limitednumber of commands via the FTP server on the host machine. No authenticationis required to execute the command. The commands that may be executed varyfrom system to system and on many systems the SITE command is notimplemented. Recommend that the SITE command be disabled on FTP servers ifpossible. If this signature is triggered from a source outside of yournetwork prudent security practices would suggest that the source be shunned."
"IDS","4","UNAVAILABLE","Sig:3151:FTP SYST Command Attempt - from %i to %i","Triggers when someone tries to execute the FTP SYST command.","The FTP SYST command returns the type of operating systemthat the FTP server is running. Authentication is not required to executethis command. SYST provides information that may be used to refine attackmethods. FTP from Linux causes SYST signature to fire. Some proxies, such asthe TIS Toolkit, issue the SYST command as a matter of course. Running anFTP version with SYST disabled."
"IDS","4","UNAVAILABLE","Sig:3152:FTP CWD ~root - from %i to %i","Triggers when someone tries to execute the CWD ~root command.","There is no known reason that this command should ever beexecuted. If this signature is triggered from a source outside of yournetwork prudent security practices would suggest that the source be shunned."
"IDS","4","UNAVAILABLE","Sig:3153:FTP Improper Address Specified - from %i to %i","Triggers if a port command is issued with an address that is not the same as the requesting host.","Triggers if a port command is issued with an address that isnot the same as the requesting host."
"IDS","4","UNAVAILABLE","Sig:3154:FTP Improper Port Specified - from %i to %i","Triggers if a port command is issued with a data port specified that is 65535.","Triggers if a port command is issued with a data port specifiedthat is 65535."
"IDS","4","UNAVAILABLE","Sig:4050:UDP Bomb - from %i to %i","Triggers when the UDP length specified is less than the IP length specified. This malformed packet type is associated with a denial of service attempt.","There is no legitimate use for malformed datagrams. Thismay be indicative of systems that are experiencing problems with theirkernel or NIC cards. This is unusual traffic and warrants investigation.When non-specific network traffic of this type is encountered, the mostprudent action from a security perspective is to shun or disallow it. If thesource of this traffic is legitimate the user will then identify him orherself."
"IDS","4","UNAVAILABLE","Sig:4100:Tftp Passwd File - from %i to %i","Triggered when someone tries to tftp a password file.","System administrators might use this service to updatesystem files. It is a high security risk if this is normal practice andshould be avoided. No other benign triggers exist for this signature. Ifafter investigation the alarm was not generated by a system administrator,prudent security practices would suggest that the source be shunned."
"IDS","4","UNAVAILABLE","Sig:6100:RPC Port Registration - from %i to %i","Triggers when attempts are made to register new RPC services on a target host.","No benign triggers exist for this signature. Prudentsecurity practices suggest that the source of this attempt should beshunned."
"IDS","4","UNAVAILABLE","Sig:6101:RPC Port Unregistration - from %i to %i","Triggers when attempts are made to unregister new RPC services on a target host.","No benign triggers exist for this signature. Prudentsecurity practices suggest that the source of this attempt should beshunned."
"IDS","4","UNAVAILABLE","Sig:6102:RPC Dump - from %i to %i","Triggers when an RPC dump request isissued to a target host.","This is a common procedure performed by many systemadministrators and wary users to determine which RPC services are beingoffered. Executing this procedure is most likely due to curiosity on thepart of a novice user or a system administrator performing systemmaintenance. If upon investigation no valid user can be associated with thisevent, prudent security practices would suggest shunning the source."
"IDS","4","UNAVAILABLE","Sig:6103:Proxied RPC Request - from %i to %i","Triggers when a proxied RPC request is sent to the portmapper of a target host.","If this procedure is allowed on your network those usersthat employ it will trigger the signature. This may be a serious attempt atgaining unauthorized access and if the source of the attempt is not withinyour network they should be shunned."
"IDS","4","UNAVAILABLE","Sig:6150:RPC ypserv Portmap Request - from %i to %i","Triggers when a request is made to the portmapper for the YP server daemon (ypserv) port.","If this procedure is allowed on your network those usersthat employ it will trigger the signature. This may be a serious attempt atgaining unauthorized access and if the source of the attempt is not withinyour network they should be shunned."
"IDS","4","UNAVAILABLE","Sig:6151:RPC ypbind Portmap Request - from %i to %i","Triggers when a request is made to the portmapper for the YP bind daemon (ypbind) port.","If this procedure is allowed on your network those usersthat employ it will trigger the signature. This may be a serious attempt atgaining unauthorized access and if the source of the attempt is not withinyour network they should be shunned."
"IDS","4","UNAVAILABLE","Sig:6152:RPC ypbind yppasswdd Portmap Request - from %i to %i","Triggers when a request is made to the portmapper for the YP password daemon (yppasswdd) port.","If this procedure is allowed on your network those usersthat employ it will trigger the signature. This may be a serious attempt atgaining unauthorized access and if the source of the attempt is not withinyour network they should be shunned."
"IDS","4","UNAVAILABLE","Sig:6153:RPC ypupdated Portmap Request - from %i to %i","Triggers when a request is made to the portmapper for the YP update daemon (ypupdated) port.","If this procedure is allowed on your network those usersthat employ it will trigger the signature. This may be a serious attempt atgaining unauthorized access and if the source of the attempt is not withinyour network they should be shunned."
"IDS","4","UNAVAILABLE","Sig:6154:RPC ypxfrd Portmap Request - from %i to %i","Triggers when a request is made to the portmapper for the YP transfer daemon (ypxfrd) port.","If this procedure is allowed on your network those usersthat employ it will trigger the signature. This may be a serious attempt atgaining unauthorized access and if the source of the attempt is not withinyour network they should be shunned."
"IDS","4","UNAVAILABLE","Sig:6155:RPC mountd Portmap Request - from %i to %i","Triggers when a request is made to the portmapper for the mount daemon (mountd) port.","If this procedure is allowed on your network those usersthat employ it will trigger the signature. This may be a serious attempt atgaining unauthorized access and if the source of the attempt is not withinyour network they should be shunned."
"IDS","4","UNAVAILABLE","Sig:6175: RPC rexd Portmap Request - from %i to %i","Triggers when a request is made to the portmapper for the remote execution daemon (rexd) port. The remote execution daemon is the serverresponsible for remote program execution. This may be indicative of an attempt to gain unauthorized access to system resources.","If this procedure is allowed on your network, those userswho employ it will trigger the signature. This may be a serious attempt atgaining unauthorized access and if the source of the attempt is not withinyour network, it should be shunned."
"IDS","4","UNAVAILABLE","Sig:6180:RPC rexd Attempt - from %i to %i","Triggers when a call to the rexd program is made. The remote execution daemon is the server responsible for remote program execution. Thismay be indicative of an attempt to gain unauthorized access to system resources.","If this service is being used legitimately, this alarm willfire. For security purposes, this service really should not be used."
"IDS","4","UNAVAILABLE","Sig:6190:statd Buffer Overflow - from %i to %i","Triggers when a large statd request is sent.","You should not see this in legitimate traffic."
"IDS","4","UNAVAILABLE","Sig:8000:FTP Retrieve Password File - from %i to %i","Triggers on string ''passwd'' issued during an FTP session.","System administrators might use this service to updatesystem files. It is a high security risk if this is normal practice andshould be avoided. No other benign triggers exist for this signature. Ifafter investigation the alarm was not generated by a system administrator,prudent security practices would suggest that the source be shunned."
"IDS","4","RPC_UNSET_REQUEST","Sig:6101:RPC Port Unregistration - from %i to %i","Triggers when attempts are made to unregister new RPC services on a target host.","No benign triggers exist for this signature. Prudent security practices suggest that the source of this attempt should be shunned."
"IDS","4","RPC_UNSET_REQUEST","Sig:6101:RPC Port Unregistration - from %i to %i","Triggers when attempts are made to unregister new RPC services on a target host.","No benign triggers exist for this signature. Prudentsecurity practices suggest that the source of this attempt should beshunned."
"IDS","4","STR_MATCH_SIG","Sig:8000:FTP Retrieve Password File - from %i to %i","Triggers on string ''passwd'' issued during an FTP session.","System administrators might use this service to update system files. It is a high security risk if this is normal practice and should be avoided. No other benign triggers exist for this signature. If after investigation the alarm was not generated by a system administrator, prudent security practices would suggest that the source be shunned."
"IDS","4","TCP_FIN_ONLY_SIG","Sig:3042:TCP - FIN bit with no ACK bit in flags - from %i to %i","Triggers when a TCP packet is received with the FIN bit set but with no ACK bit set in the flags field.","There is no legitimate use for malformed TCP datagrams. This is unusual traffic and warrants investigation. Hacker tools will generateTCP packets with the FIN bit set but with no ACK bit set in the flags field in an attempt to elude intrusion dection. When non-specific network traffic of this type is encountered, the most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate the user will then identify him or herself."
"IDS","4","TCP_FTP_CWDROOT_SIG","Sig:3152:FTP CWD ~root - from %i to %i","Triggers when someone tries to execute the CWD ~root command.","There is no known reason that this command should ever be executed. If this signature is triggered from a source outside of your etwork prudent security practices would suggest that the source be shunned."
"IDS","4","TCP_FTP_PORT_BADADDR_SIG","Sig:3153:FTP Improper Address Specified - from %i to %i","Triggers if a port command is issued with an address that is not the same as the requesting host.","Triggers if a port command is issued with an address that is ot the same as the requesting host."
"IDS","4","TCP_FTP_PORT_BADPORT_SIG","Sig:3154:FTP Improper Port Specified - from %i to %i","Triggers if a port command is issued with a data port specified that is <1024 or 65535.","Triggers if a port command is issued with a data port specified hat is 65535."
"IDS","4","TCP_FTP_SITE_SIG","Sig:3150:FTP Remote Command Execution - from %i to %i","Triggers when someone tries to execute the FTP SITE command.","The FTP Site command allows a user to execute a limited umber of commands via the FTP server on the host machine. No authentication is required to execute the command. The commands that may be executed vary from system to system and on many systems the SITE command is not implemented. Recommend that the SITE command be disabled on FTP servers if possible. If this signature is triggered from a source outside of your etwork prudent security practices would suggest that the source be shunned."
"IDS","4","TCP_FTP_SITE_SIG","Sig:3150:FTP Remote Command Execution - from %i to %i","Triggers when someone tries to execute the FTP SITE command.","The FTP Site command allows a user to execute a limitednumber of commands via the FTP server on the host machine. No authenticationis required to execute the command. The commands that may be executed varyfrom system to system and on many systems the SITE command is notimplemented. Recommend that the SITE command be disabled on FTP servers ifpossible. If this signature is triggered from a source outside of yournetwork prudent security practices would suggest that the source be shunned."
"IDS","4","TCP_FTP_SYST_SIG","Sig:3151:FTP SYST Command Attempt - from %i to %i","Triggers when someone tries to execute the FTP SYST command.","The FTP SYST command returns the type of operating system hat the FTP server is running. Authentication is not required to execute his command. SYST provides information that may be used to refine attack methods. FTP from Linux causes SYST signature to fire. Some proxies, such as he TIS Toolkit, issue the SYST command as a matter of course. Running an FTP version with SYST disabled."
"IDS","4","TCP_MAJORDOMO_EXEC_BUG","Sig:3107:Majordomo Execute Attack - from %i to %i","A bug in the Majordomo program will allow remote users to execute arbitrary commands at the privilege level of the server.","Prudent security practices would suggest that the source of this attempt be shunned."
"IDS","4","TCP_NO_FLAGS_SIG","Sig:3040:TCP - No bits set in flags - from %i to %i","Triggers when a TCP packet is received with no bits set in the flags field.","There is no legitimate use for malformed TCP datagrams. This is unusual traffic and warrants investigation. Hacker tools will generate TCP packets with no bits set in the flags field in an attempt to elude intrusion dection. When non-specific network traffic of this ype is encountered, the most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate he user will then identify him or herself."
"IDS","4","TCP_SENDMAIL_BAD_FROM_SIG","Sig:3102:Sendmail Invalid Sender - from %i to %i","Triggers on any mail message with a ''pipe'' (|) symbol in the ''From:'' field.","For security reasons users should not be allowed to executeprograms via e-mail servers. This is a very serious indication that yournetwork may be under attack and the source should be shunned immediately."
"IDS","4","TCP_SENDMAIL_BAD_TO_SIG","Sig:3101:Sendmail Invalid Recipient - from %i to %i","Triggers on any mail message with a ' 'pipe'' (|) symbol in the recipient field.","For security reasons users should not be allowed to execute programs via e-mail servers. This is a very serious indication that your etwork may be under attack and the source should be shunned immediately."
"IDS","4","TCP_SENDMAIL_BOUNCE_SIG","Sig:3100:Smail Attack - from %i to %i","Triggers on the very common ''smail'' attack against e-mail servers. This attack attempts to cause e-mail servers to execute programs on the attacker's behalf.","For security reasons users should not be allowed to executeprograms via e-mail servers. This is a very serious indication that yournetwork may be under attack and the source should be shunned immediately."
"IDS","4","TCP_SENDMAIL_DECODE","Sig:3105:Sendmail Decode Alias - from %i to %i","Triggers on any mail message with '': decode@'' in the header. The decode alias is used to uudecode files and is primarily implemented as a convenience for system administration.","The decode alias is used to uudecode files and is primarily implemented as a convenience for system administration. For security purposes this should not be allowed and the service should be disabled. If allowed, users that mail to the alias will trigger this signature. Recommend shunning of hosts that attempt to mail to this alias especially if they are outside of your network."
"IDS","4","TCP_SENDMAIL_INVALID_COMMAND","Invalid SMTP command - from %i to %i","Triggers on an invalid SMTP command in the SMTP connection. This message indicates that a suspicious violation was detetected that may be an attack to the mail server system.","This is unusual traffic and may warrant investigation."
"IDS","4","TCP_SENDMAIL_OLD_SIG","Sig:3104:Archaic Sendmail Attacks - from %i to %i","Triggers when ''wiz'' or ''debug'' commands are sent to the SMTP port.","There is no reason for this type of traffic to be seen on modern networks. There is little chance that there will be any adverse effects from someone attempting these ''old'' hacks. Prudent security practices would suggest that the source of this attempt be shunned."
"IDS","4","TCP_SENDMAIL_VRFY_SIG","Sig:3103:Sendmail Reconnaissance - from %i to %i","Triggers when ''expn'' or ''vrfy'' commands are issued to the SMTP port.","These commands are commonly used to verify that a user mailaccount exists on the server or to expand an alias to determine who theactual recipients of a message may be. Users that use the EXPN and VRFYfunctions for legitimate purposes will trigger this signature. Theinformation that can be obtained is useful, but not dangerous on its own.Monitoring of future traffic for patterns of misuse is recommended."
"IDS","4","TCP_SYN_ATTACK_SIG","Sig:3050:Half-Open Syn Flood - from %i to %i","Triggers when the number of half-open TCP connections exceeds the high-water mark or the one minute high rate mark","There are no known sources that would legitimately generate his traffic pattern. This may be indicative of some type of network problem and should be investigated. To avoid depletion of your network resources it is recommended that the source be shunned during the course of the investigation. If no network problems are discovered prudent security practices would suggest that the source be shunned permanently."
"IDS","4","TCP_SYN_FIN_SIG","Sig:3041:TCP - SYN and FIN bits set - from %i to %i","Triggers when a TCP packet is received with both the SYN and FIN bits set in the flags field.","There is no legitimate use for malformed TCP datagrams. This is unusual traffic and warrants investigation. Hacker tools will generateTCP packets with the SYN and FIN bits set in the flags field in an attempt to eludeintrusion dection. When non-specific network traffic of thistype is encountered, the most prudent action from a security perspectiveis to shun or disallow it. If the source of this traffic is legitimatethe user will then identify him or herself."
"IDS","4","UDP_BOMB_SIG","Sig:4050:UDP Bomb - from %i to %i","Triggers when the UDP length specified is less than the IP length specified. This malformed packet type is associated with a denial of service attempt.","There is no legitimate use for malformed datagrams. This may be indicative of systems that are experiencing problems with their kernel or NIC cards. This is unusual traffic and warrants investigation. When non-specific network traffic of this type is encountered, the most prudent action from a security perspective is to shun or disallow it. If the source of this traffic is legitimate the user will then identify him or "
"IDS","4","UDP_TFTP_PASSWD_SIG","Sig:4100:Tftp Passwd File - from %i to %i","Triggered when someone tries to tftp a password file.","System administrators might use this service to updatesystem files. It is a high security risk if this is normal practice andshould be avoided. No other benign triggers exist for this signature. Ifafter investigation the alarm was not generated by a system administrator,prudent security practices would suggest that the source be shunned."
"IDTATM25","1","UNAVAILABLE","IDTATM25(%d/%d), Init failed at %s.","The ATM25 network module hardware may be bad","Copy the error message exactly as it appears, and report it to your technical support representative."
"IDTATM25","1","UNAVAILABLE","IDTATM25(%d/%d), Init failed, CSR%d=0x%04x.","The ATM25 network module hardware may be bad","Copy the error message exactly as it appears, and report it to your technical support representative."
"IDTATM25","1","UNAVAILABLE","Only found %d interfaces on bay %d, shutting down bay","The ATM25 network module hardware may be bad","Copy the error message exactly as it appears, and report it to your technical support representative."
"IDTATM25","3","UNAVAILABLE","Device reported %#x","The ATM25 network module hardware may be bad","Copy the error message exactly as it appears, and report it to your technical support representative."
"IDTATM25","3","UNAVAILABLE","IDB= %s, RX lost sync, Interface reset","RX hang","Copy the error message exactly as it appears, and report it to your technical support representative."
"IDTATM25","3","UNAVAILABLE","IDB= %s, TX hang, Interface reset","TX hang","Copy the error message exactly as it appears, and report it to your technical support representative."
"IDTATM25","3","UNAVAILABLE","Interface %s, %s not supported","The ATM25 network module hardware may be bad","Copy the error message exactly as it appears, and report it to your technical support representative."
"IDTATM25","3","UNAVAILABLE","Interface %s, Failed to down vc %d (Cause: %s)","The ATM25 network module hardware may be bad","Copy the error message exactly as it appears, and report it to your technical support representative."
"IDTATM25","3","UNAVAILABLE","Interface %s, Failed to setup vc %d (Cause: %s)","The ATM25 network module hardware may be bad","Copy the error message exactly as it appears, and report it to your technical support representative."
"IDTATM25","6","UNAVAILABLE","ATM transmit bandwidth is limited to smallest shaped value.","Any PVC configured with traffic shaping will limit the entire ATM interface to not exceed the bandwidth of any traffic shaped pvc.IF MessagesThis section contains interface messages.IF-2Error Message    %IF-2-IDB_TABLE_INIT: Malloc failed while initializing idb table Explanation    A memory allocation failure occurred while an IDB table was being initialized.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"IF","3","BADMACADDRTYPE","illegal mac address type, [dec]","This is an internal error that was recovered gracefully.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IF","4","BACKWARD_COUNTERS","Corrected for backward [chars] counters ([int] -> [int]) on [chars]","The interface specified in the message has a packet counter that has decreased in number. This condition can occur if a packet is counted and then dropped. This event was detected and corrected.","If this condition persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IF","4","NOBGPROCESS","Network background process not running. [chars]","A process which manages network interface background processing is not yet running, but another system process has tried to send the process a message. An interface on the router may have missed a request to bring itself up.","Reset the interface by entering a shutdown command followed by a no shutdown command."
"IFDAMP","5","ZERODELAY","dampening reuse timer is updated with 0 delay time","An inconsistency was detected in the dampening reuse timer wheel.","No action is required."
"IFMGR","3","BADIFINDEXTABLE","The file nvram:ifIndex-table is corrupt.","The file is not in the expected format.","If possible, delete the file. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IFMGR","3","DUP_IFINDEX","Duplicate ifIndex (%d) found for ifDescr","Two interfaces have the same interface index in the interface manager assigned list. The second interface registered with the interface manager will be assigned a new index.","If interface index persistence is not required, then no action is required. Otherwise, reload the router with the proper interface index table and image. If the error message only appears from the standby route processor (RP), reload the standby RP."
"IFMGR","3","IFDB","IF manager interface database [chars] failure- [dec]","An internal software error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IFMGR","3","IFINDEX_PERSIST_ENTRY_CORRUPT","[chars] seems to be corrupted. Trying to read [dec] size","The ifIndex table is corrupted.","Delete the ifindex table."
"IFMGR","3","INVALID_PERSISTENT_DATA","Invalid persistent data","An attempt was made to write invalid persistent data.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IFMGR","3","NOIMACP","IF manager control process failed to start","An internal software error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IFMGR","3","NOVECTOR","Interface manager failed to allocate IF vector. size %d","The interface vector could not be allocated with the number of elements required, either initially or by a resize operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IFMGR","3","VECTOREXD","IF manager attempted to use interface [dec] outside vector range.","An internal software error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IFMGR","3","VECTORIFSUSPECT","IF manager added interface %d which is unexpectedly large.","The ifIndex allocation scheme is trying to add an ifIndex value much larger than the former greatest ifIndex value in the DB. It should assign sequential ifIndex values.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IFMGR","3","VECTORPOSUSED","IF manager attempted to add interface [dec] which was already added.","An internal software error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IFMGR","4","NOIFINDEX","All SNMP if indices are exhausted","All SNMP MIB indexes have been exhausted. Interfaces will not be able to obtain an interface index that they can use to register with the interface MIB.","Attempt a system reload. If the problem persists after the system reload, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IFMGR","4","NOSYNC","ifIndex not being synced between active and standby","When the standby module comes up, the tuple of ifIndex and ifDescr is synchronized so that interfaces get the same ifIndex when they come up. This error happens when the interface does not get the ifIndex for the given ifDescr.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IFMGR","4","STACK_RELATIONSHIP_ADD_ERROR","[chars]: Request for creating invalid stack relationship [dec], [dec]","The IF MGR received the call to add invalid stack relationship. The higher and lower ifIndex are shown in the message. The module of the IF MGR from which this message is generated is also shown in the message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IFMGR","4","VECTORIFSUSPECT","IF manager added interface [dec] which is unexpectedly large.","The ifIndex allocation scheme gives out sequential ifIndex values. This message comes from the IF-MGR DB when it is trying to add an ifIndex value much larger than the former greatest ifIndex value in the DB.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IFMGR","7","NO_IFINDEX_FILE","Unable to open [chars] [chars]","This is a informational message. This means system found no saved ifIndex information, and ifIndex is not persisted across reboots. The ifIndices will be reassigned.","1. No Action, if 'snmp-server ifIndex persist' is not configured. 2. If 'snmp-server ifindex persist' is configured then copy the error message exactly as it appears, and report it to your technical support representative."
"IFS","3","UNAVAILABLE","'%s' file system missing required functions, not created","Some file systems require a certain set of function to be present in order to be usable. This file sustem does not support all the mandatory functionality.","Call your technical support representative for assistance."
"IFS","3","UNAVAILABLE","Data does not match expected internal representation","A mismatch exists between the representation of data extracted from the filesystem and the expectation of its formatting. This may occur when running in a dual-RP environment, with different IOS versions running on the two RPs.","Ensure both RPs are running the IOS same version, if running in a dual-RP environment. If not, call your technical support representative for assistance."
"IFS","3","UNAVAILABLE","Failed to add %s, filesystem prefix exists","A file system cound not be added because another file system exists with the same name.","Contact your technical support representative."
"IFS","3","UNAVAILABLE","Failed to add %s, maximum filesystems %d","The router has reached the maximum number of file systems that can be supported at one time.","Contact your technical support representative."
"IFS","3","UNAVAILABLE","Failed to create %s file system, %s","An internal software error occurred.","Call your technical support representative for assistance."
"IFS","3","UNAVAILABLE","Failed to create %s simple file system, %s","An internal software error occurred.","Call your technical support representative for assistance."
"IFS","4","UNAVAILABLE","Failed to open %s, maximum open files %d)","The router has reached the maximum number of files that may be open at one time.","Close some files and try again. If this messages recurs, contact your technical support representative."
"IGMP","3","NO_DNS_SERVER","No DNS server is configured. DNS-based SSM mapping should be disabled if no DNS server is configured.","No domain name service (DNS) server is present. Processing of Internet Group Management Protocol (IGMP) packets may be delayed if the DNS lookup is done continuously.","Disable DNS-based source specific multicast (SSM) mapping if no DNS server is present in the network."
"IGMP","3","QUERY_INT_MISMATCH","Received a non-matching query interval %d, from querier address %i","An IGMP version mismatch was detected between routers.","Configure both interfaces with the same IGMP version."
"IGMP","6","IGMP_CHANNEL_LIMIT","IGMP limit exceeded for channel (%i, %i) on %s by host %i","The allowed number of IGMP joiners reached the configured limit. New joiners cannot be allowed unless the configuration is changed.","Enter the global or interface ip igmp limit command to adjust the allowed number of IGMP joiners. If the exceeding of current limits was unexpected, find the IP address of the denied host in the system log."
"IGMP","6","IGMP_GROUP_LIMIT","IGMP limit exceeded for group (*, %i) on %s by host %i","The allowed number of IGMP joiners has exceeded the configured limit. New joiners cannot be allowed unless the configuration is changed.","Enter the global or interface ip igmp limit command to adjust the allowed number of IGMP joiners. If the exceeding of current limits was unexpected, find the IP address of the denied host in the system log."
"ILACC","1","UNAVAILABLE","msgtxt_initfail","The hardware failed to initialize correctly.","Repair or replace the controller."
"ILACC","1","UNAVAILABLE","msgtxt_memoryerror","An Ethernet interface detected a hardware problem.","Repair or replace the controller."
"ILACC","3","UNAVAILABLE","Unit %d, spurious IDON interrupt, csr%d=0x%04x","An Ethernet interface generated a spurious Initialization Done interrupt.","Repair or replace the controller."
"ILACC","3","UNAVAILABLE","Unit %d, underflow error","The Ethernet hardware is requesting data faster than the system can supply it. This condition might indicate that the system is at the limit of its performance.","A small number of underflows might not be a cause for concern. You can monitor underflows with the show interface command. Reducing the load on the router or installing a higher-performance router should alleviate this problem."
"ILACC","3","UNAVAILABLE","msgtxt_badunit","An internal software error occurred.","If this message recurs, contact your technical support representative."
"ILACC","3","UNAVAILABLE","msgtxt_ownerror","An Ethernet interface is malfunctioning, or an internal software error occurred.","Repair or replace the controller."
"ILACC","4","UNAVAILABLE","Unit %d, babble error, csr0 = 0x%x","An Ethernet interface is malfunctioning.","Determine whether the malfunction stems from a software or hardware error by turning off all fast switching. Error messages showing that the packet is too large for the link indicate a software error at a high level. Copy the error message exactly as it appears, and report it to your technical support representative. Receiving no error messages indicates a hardware error. Repair or replace the controller."
"ILACC","5","UNAVAILABLE","Unit %d, excessive collisions. TDR=%d","An Ethernet cable is broken or unterminated, or the transceiver is unplugged. The time delay reflectometer (TDR) counter is an internal ILACC counter that counts the time (in ticks of 100 ns each) from the start of a transmission to the occurrence of a collision. Because a transmission travels about 35 feet per tick, this value is useful to determine the approximate distance to a cable fault.","If the transceiver appears to be properly terminated, repair or replace the Ethernet interface card."
"ILACC","5","UNAVAILABLE","Unit %d, late collision error","An Ethernet transceiver is malfunctioning, the Ethernet is overloaded, or the Ethernet cable is too long.","Repair or replace the controller."
"ILACC","5","UNAVAILABLE","Unit %d, lost carrier. Transceiver problem?","An Ethernet transceiver is unplugged or faulty.","Repair or replace the controller."
"ILPOWER","3","CONTROLLER_ERR","Controller error, Controller number [dec]: [chars]","An error involving the inline power controller has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ILPOWER","3","CONTROLLER_IF_ERR","Controller interface error, [chars]: [chars]","An interface error has been detected between the inline power controller and the system.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ILPOWER","3","CONTROLLER_PORT_ERR","Controller port error, Interface [chars]: [chars]","A port error has been reported by the inline power controller.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ILPOWER","3","ILPOWER_INTERNAL_IF_ERROR","Inline Power internal error, interface %s: %s","A software sanity check failed in the course of Inline Power processing.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ILPOWER","5","AC_DISCONNECT","Interface [chars]: AC disconnect","The AC power has been disconnected.","No action is required."
"ILPOWER","5","DC_DISCONNECT","Interface [chars]: DC disconnect","The DC power has been disconnected.","No action is required."
"ILPOWER","5","ILPOWER_MISCONFIG","Interface [chars] is denied power as it requires more power than configured maximum wattage([dec]).","The interface is denied power as it requires more power than the configured maximum wattage.","No action is required."
"ILPOWER","5","ILPOWER_NOPOWER_AVAIL","Interface [chars] is denied power because either the system ran out of power or module limit reached.","There is not enough power left in the system to supply to the interface specified in the error message.","No action is required."
"ILPOWER","5","ILPOWER_POWEROVERDRAWN","Interface [chars] is shutdown as it is consuming more power ([dec]) than the configured maximum value ([dec]).","The specified interface is shut down because it is consuming more power than the configured maximum value.","No action is required."
"ILPOWER","5","LINKDOWN_DISCONNECT","Interface [chars]: Link down disconnect","A link has been disconnected.","No action is required."
"ILPOWER","5","POWER_GRANTED","Interface [chars]: Power granted","Power has been granted for the interface specified.","No action is required."
"ILPOWER","7","DETECT","Interface [chars]: Power Device detected: [chars]","A power device has been detected.","No action is required."
"ILPOWER_RF","3","CREATE_PROCESS","Inline power RF client failed to create %s process","The inline power redundancy facility (RF) client could not create a process. This condition will cause bulk synchronization to fail.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IMA","1","UNAVAILABLE","Command opcode %#x on channel %d on slot %d was rejected.","The IMA firmware has rejected the command because of the current protocol state of the interface, or the opcode is undefined.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IMA","1","UNAVAILABLE","Delaying activation of %s until a currently active interface is shutdown.","The IMA network module cannot only support up to 4 activate interfaces at one time. Once more that 4 are no shutdown, each interface will wait for an existing interface to be shutdown before becoming activated.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IMA","1","UNAVAILABLE","Download of %s to failed to at %#x on IMA Network Module in slot %d.","An error occured during the download of firmware to the IMA NM.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IMA","1","UNAVAILABLE","FPGA Download on module in slot %d failed.","An error occured during the download of the FPGA on the IMA NM.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IMA","1","UNAVAILABLE","Module in slot %d had a shared memory error.","Memory on the NM failed power-on diagnostic check.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IMA","1","UNAVAILABLE","Network processor on module in slot %d failed to come up.","An error occured during reset of the IMA NM.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IMA","1","UNAVAILABLE","Previous process %d never received mail response from slot %d.","The previous requesting process was terminated before receiving a mail reply.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IMA","1","UNAVAILABLE","The IMA Network Module in slot %d is incompatible with the PCMCIA controller in the router.","The PCMCIA controller is down level.","Copy the error message exactly as it appears, and contact your technical support representative for upgrade information."
"IMA","1","UNAVAILABLE","The Network Module in slot %d did not initialize.","The Network Module has failed its initialization.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IMA","1","UNAVAILABLE","The Network Module in slot %d reports an invalid %s device id of %#x.","The IMA network module hardware may be bad.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IMA","1","UNAVAILABLE","The mailbox for channel %d on IMA Network Module in slot %d is completely full. Message %d was dropped.","The IMA NM mailboxes are full and cannot accept any more requests.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IMA","1","UNAVAILABLE","Timed out waiting for a response to command %#x from slot %d.","The IMA NM failed to respond with the requested information. Information to be displayed by requesting exec command or SNMP manager is incomplete. This is an extremely rare event and should only happen under severe system load.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IMA","4","UNAVAILABLE","Link %d will become the common transmit clock once it is added to group %s","The link configured as the common transmit clock is not a member of the group, so it cannot provide the clock. The group will use a common transmit clock that is automatically chosen from one of the other active links.","LOG_STD_NO_ACTION"
"IMA","4","UNAVAILABLE","Link %d will initiate the test pattern procedure once its added to group %s.","The link chosen to transmit the test pattern is not a member of the group, thereby preventing the transmission of the test pattern.","LOG_STD_NO_ACTION"
"IMA","4","UNAVAILABLE","Stopping test pattern procedure on group %s.","The link transmitting the test pattern has been removed from the group, thereby stopping the transmission of the test pattern.","LOG_STD_NO_ACTION"
"IMA","5","UNAVAILABLE","%s is using channel %d but has no configured links.","The IMA interface has been configured Up but has no link members. It cannot become active until active links are added to the group.","LOG_STD_NO_ACTION"
"IMA","5","UNAVAILABLE","IMA Group %s now has %d active links, active link bitmap is %#x.","Active Links were added or removed from the Group, changing its bandwidth.","LOG_STD_NO_ACTION"
"IMAGEMGR","6","AUTO_ADVISE_SW","[chars]","A line of output from the auto-advise-software process is being displayed.","No action is required."
"IMAGEMGR","6","AUTO_ADVISE_SW_INITIATED","Auto-advise-software process initiated for switch number(s) [chars]","Systems with incompatible software have been detected in the stack. The stack will now determine whether or not software is available to be copied to the incompatible systems, and if so, advise the user how to copy it. Otherwise, the system lets the user know that the software on the stack needs to be updated.","No action is required."
"IMAGEMGR","6","AUTO_COPY_SW","[chars]","A line of output from the auto-copy-software process is being displayed.","No action is required."
"IMAGEMGR","6","AUTO_COPY_SW_INITIATED","Auto-copy-software process initiated for switch number(s) [chars]","Systems with incompatible software have been detected in the stack. The stack determines whether or not software is available to be copied to the incompatible systems, and whether or not it is appropriate to copy the software automatically.","No action is required."
"IMAGEMGR","6","AUTO_DOWNLOAD_SW","[chars]","A line of output from the automatic software download process is being displayed.","No action is required."
"IMAGEMGR","6","AUTO_DOWNLOAD_SW_INITIATED","Auto-download-software process initiated for switch number(s) [chars]","Systems with incompatible software have been detected in the stack. The stack attempts to download software from a previously configured location, and install it to make the systems compatible.","No action is required."
"IMAGE_SIMFS","3","NOPROCESS","Failure spawning Memory Reclaim process","The creation of an Cisco IOS process to compact memory previously held by in-memory image files has failed, probably due to a software defect.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IMAGE_VFS","3","UNAVAILABLE","%s image checksum mismatch.","The checksum of the image in memory is different from the expected checksum","Check whether the image file is complete and uncorrupted"
"IMAGE_VFS","3","UNAVAILABLE","Failed to locate all the Image files,on bootup","The relevant image file is missing or it couldn't be extracted(due to corruption), or the router has insufficient memory to load the entire image","If the TAR file is part of a system image, enter the show image contents file archive-name, where archive-name is the name of the archive. Enter the show region and show version commands. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"IMAGE_VFS","3","UNAVAILABLE","Failed to open %s, which was loaded from archive %s","The relevant image file is missing or it could'nt be extracted(due to corruption), or the Archive itself is missing(In case of Flash based access)","If the file is not in memory, check the archive file. If the file is a TAR archive file and not part of a system software image, enter the archive tar table archive-name command, where archive-name is the name of the TAR archive. If the TAR file is part of a system image, enter the show image contents file archive-name, where archive-name is the name of the archive. Enter the dir all and show version commands. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"IMAGE_VFS","3","UNAVAILABLE","Failure spawning No Cache process","The creation of an IOS process to delete in-memory Image files failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IMAGE_VFS","3","UNAVAILABLE","archive verification failed for file %s & archive %s.","The archive in the local device is different from the version whose image file has been loaded into memory. This can happen if the archive was deleted from the local device &/or replaced by another file of the same name","Check whether the archive file is complete and uncorrupted.Also check if the size of the archive & the last modification time (if available) is what you expect it to be. Enter the dir all and show version commands."
"INBAND","3","BAD_PAK","Possibly un-encapsulated packet passed to Mistral: int [chars] type [int] stat [hex] flags [hex] size [dec] offset [dec] requeue_token [int] r1 [int] r2 [int] total detected [int]","There is a badly encapsulated packet from the process level.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"INBAND","3","INVALID_SEND","Invalid send operation (packet on [chars])","An internal error caused illegal call to device driver: normal operation continues.","If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"INBAND","3","NO_BUFFER_POOLS","Initialization of private buffer pools failed","Private buffer pools were not created for etsec ibc.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"INBAND","3","TOOBIG","An attempt made to send giant packet on [chars] ([dec] bytes from [hex], max allowed [dec])","An attempt was made to send an oversized packet.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"INBAND","6","UNAVAILABLE","Bad idb for vector %s: %s vlan %d total %d","Bad idb returned from get_l3_swidb","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"INBAND_or_EOBC","3","UNAVAILABLE","Invalid send operation (packet on %s)","Internal error caused illegal call to device driver:normal operation continues","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"INDXOBJ","3","UNAVAILABLE","index object routine %s called from interrupt context","inappropriate index object routine called from interrupt routine.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"INTERFACE_API","1","NOMOREHWIDBNUMBERS","No more hardware IDB numbers can be issued. The maximum allowed numbers, [dec], has been reached for this platform.","No more hardware IDB numbers can be issued. The maximum allowed number has been reached for this platform.","In addition to the following, copy the information from the show idb command output. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"INTERFACE_API","1","NOMORESWIDBNUMBERS","No more software IDB numbers can be issued. The maximum allowed numbers, [dec], has been reached for this platform.","No more software IDB numbers can be issued. The maximum allowed number has been reached for this platform.","In addition to the following, copy the information from the show idb command output. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"INTERFACE_API","3","CANNOTGETMTU","Error [dec] received while getting MTU: [chars]. Using default [int]","A software error has occurred while attempting to retrieve the MTU value from the interface.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"INTERFACE_API","3","IFNUMTOIDBERROR","Error occurred while using the ifnum to idb table for interface [chars], if number [dec], during [chars]","A software error has occurred. An operation on the interface number to the IDB mapping table could not be performed successfully.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"INTERFACE_API","3","INVALIDSUBBLOCKPARAMETERS","Invalid subblock parameters for [chars] were supplied.","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"INTERFACE_API","3","NOADDSUBBLOCK","The [chars] subblock named [chars] was not added to [chars]","A software error has occurred. IDB subblocks could not be added.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"INTERFACE_API","3","SUBNUMDBERR","subnum [hex] error in [chars]","A software error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"INTERFACE_API","4","UNAVAILABLE","%s may not be referencing the correct swidb","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"INTERFACE_API","4","UNAVAILABLE","A error occurred while using the Index Table utility for %s.","A software error has occurred; this message is displayed when an Index table feature could not be used successfully.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"INTERFACE_API","4","UNAVAILABLE","Function %s detected an invalid %s pointer of %08lX, ignoring","A software error has occurred, this message is displayed when an invalid pointer is detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"INTERFACE_API","4","UNAVAILABLE","pak-if_input is not initialized","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"INTERFACE_API","4","UNAVAILABLE","pak-if_output is not initialized","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"INTF_SYNC","2","UNAVAILABLE","%s","A software error occurred during initialization of the Interface Sync RF subsystem","Check for sufficient processor memory. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"INTF_SYNC","3","UNAVAILABLE","Incorrectly formatted message (0x%x, 0x%x) received by %s","Inconsistent message data was received from the peer CPU, possibly due to an incompatible image version.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"INTF_SYNC","3","UNAVAILABLE","Unable to transmit message type %d from %s","A transmit error occurred while sending msg to other CPU, due to msg translation","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"INTF_SYNC","3","UNAVAILABLE","Unable to transmit message type %d from %s","A transmit error occurred while sending msg to other CPU, due to non-availability of buffer","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"INTF_SYNC","3","UNAVAILABLE","Unknown message type 0x%x received by %s","An unknown message type was received from the peer CPU, possibly due to an incompatible image version.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"INTF_SYNC","5","UNAVAILABLE","Msgtype %s sent by %s unsupported by peer.","Peer responded that it didn't recognize a message sent by this CPU, possibly due to a different image version.","May require a software upgrade on the Standby CPU. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"INTR_MGR","3","BURST","[chars] [chars] [[dec]]","A burst of hardware interrupts of the specified type has occurred.","The message text on the console or in the system log provides more information on the specific cause of the error. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"INTR_MGR","3","INTR","[chars] [chars]","The specified interrupt event has been detected.","The message text on the console or in the system log provides more information on the specific cause of the error. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"INTR_MGR","3","MAXBURST","[chars] [chars] [[dec]]","The specified hardware interrupt has exceeded the maximum allowed number of bursts.","The message text on the console or in the system log provides more information on the specific cause of the error. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IOCARD","3","UNAVAILABLE","%s in slot%d is not supported on %s chassis","The software identified and disabled the FE on the I/O card","No action required."
"IOCARD","3","UNAVAILABLE","IO card discovered in non-zero slot %d","An IO card was detected in a non-zero slot.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IOS_LICENSE","2","UNAVAILABLE","No memory available for %s","The Ios licensing subsystem could not obtain the memory it needed.","If this error message recurs, attempt to reduce memory usage by reducing the number of router features, or interfaces, enabled. Alternatively, add more memory. To display total memory usage for a router enter show memory summary at the privileged command line prompt. To display buffer usage enter show buffers at the prompt."
"IOS_LICENSE","2","UNAVAILABLE","No valid license avaiable to run any feature","The Ios licensing subsystem could not get a valid license to run any feature on the box, please purchase a license.","Purchase a valid license to run the features you requier on the box. You should contact the cisco portal or a TAC engineer to get a license. You can do a show license at the privileged command line prompt to get the list of availabe feature in the box"
"IOS_LICENSE","3","UNAVAILABLE","%s","The ios licensing subsystem failed to create a process/watched boolean etc to watch request from the remote show subsys license commands","please capture the error msg and forward it to the appropriate licensing component"
"IOS_LICENSE","3","UNAVAILABLE","%s failed","The rttys calls in the Ios licensing subsystem failed for some reason, please capture the error msg and forward it to the appropriate licensing component","please capture the error msg and forward it to the appropriate licensing component"
"IOS_LICENSE","3","UNAVAILABLE","%s failed with an error = %s","The ipc calls in the Ios licensing subsystem failed for some reason, please capture the error msg and forward it to the appropriate licensing component","please capture the error msg and forward it to the appropriate licensing component"
"IOS_LICENSE","3","UNAVAILABLE","an unknown message type was received, dropping it, msg_type = %d","Ios licensing subsystem received a msg type which it does not recognizes or support","please capture the error msg and forward it to the appropriate licensing component."
"IOS_LICENSE_IMAGE_APPLICATION","3","UNAVAILABLE","%s","The ios image licensing subsystem received an event for an unknown version of a feature","please capture the error msg and forward it to the appropriate licensing component"
"IOS_LICENSE_IMAGE_APPLICATION","3","UNAVAILABLE","%s","The ios image licensing subsystem received an event which it does not understand or recognizes","please capture the error msg and forward it to the appropriate licensing component"
"IOS_LICENSE_IMAGE_APPLICATION","3","UNAVAILABLE","%s","The ios licensing subsystem failed to create a process/watched boolean etc to watch request from the remote show subsys license commands","please capture the error msg and forward it to the appropriate licensing component"
"IOS_LICENSE_IMAGE_APPLICATION","6","UNAVAILABLE","%s %s.","There is no valid license available on the box and we are running on a default feature","please purchase a license to activate required features"
"IOS_LICENSE_IMAGE_APPLICATION","6","UNAVAILABLE","EULA must be accepted for license level = %s","This is an informational message to inform user that the user needs to reissue the command from an interactive terminal","This is an informational message, no action is required"
"IOS_LICENSE_IMAGE_APPLICATION","6","UNAVAILABLE","Module name = %s Next reboot level = %s and License = %s","This is an informational message to display the change in the next reboot license level","This is an informational message, no action is required"
"IOS_LICENSE_IMAGE_APPLICATION","6","UNAVAILABLE","Please issue 'license boot' config command to make extension license (%s) available for use.","This is an informational message to info user that to make extension license available to support image level, licensing image level needs to be configured","This is an informational message, no action is required"
"IP","3","LOOPPAK","Looping packet detected and dropped src=[IP_address], dst=[IP_address],hl=[int], tl=[int], prot=[int], port=[int], dport=[int] in=[chars], nexthop=[IP_address], out=[chars] options=[chars]","A looping packet was detected. A common cause is a misconfiguration of an IP helper address. The helper address should be the same address as that of the server of the intended service. Putting the address of the router in the helper address causes a routing loop to be created.","To resolve this issue, analyze the source and destination address of the looped packets. Verify that the configuration of IP helper addresses in the switch correctly point to the right device (for example the DHCP server, the DNS server, or WINS server)."
"IP","3","MAXIRDP","Attempt to send IRDP to proxies exceeding configurable limit: [dec], interface: [chars], secondary = [dec], proxy = [dec]","The sum of configured secondary addresses and configured proxy addresses exceeds the number of total addresses that the IRDP can support in its implementation.","Reduce the number of either the secondary IP addresses or proxy addresses configured for the interface."
"IP","3","NOOUTINTF","Output interface not available. source address: [IP_address], destination address: [IP_address], routing type: [int]","The output interface for this packet is not set.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IP","4","UNAVAILABLE","Bad IP address and mask %i%m in class_resolve()","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IP","4","UNAVAILABLE","Duplicate address %i on %s, sourced by %e","Another system is using your IP address.","Change the IP address of one of the two systems."
"IP","4","UNAVAILABLE","IP unicast reverse-path check disabled on %s","The IP verify unicast reverse-path feature was disabled because CEF was disabled (either through configuration or due to an internal error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IP","4","UNAVAILABLE","Zero MAC address for %i in ARP cache","An entry in the ARP cache have a NULL MAC address","If this message recurs, call your technical support representative for assistance."
"IP","5","UNAVAILABLE","%s","Error occured in IP access checks.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IP","5","UNAVAILABLE","%s","Error occured in intialisation of TURBOACL.","Show process. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IP","5","UNAVAILABLE","Attempting web install from host %i","A hardware or software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"IP","5","UNAVAILABLE","Selected IP address %i","A hardware or software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IP","5","UNAVAILABLE","Sending DNS response to %i (request was for %i)","A hardware or software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IP","5","UNAVAILABLE","Terminating DNS process","A hardware or software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IP","6","L2MCASTDROP","Layer 2 Multicast packet detected and dropped, src=[IP_address], dst=[IP_address]","Layer 2 Multicast packet with Layer3 Unicast Destination was dropped.","No action is required."
"IP","6","PHYBCASTDROP","Physical broadcast packet detected and dropped, src=[IP_address], dst=[IP_address]","Layer 2 Broadcast packet with Layer3 Unicast Destination was dropped.","No action is required."
"IPA","3","UNAVAILABLE","%s: invalid mailbox command: %02X","A subsytem attempted to register a mailbox command that is out of range.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPA","3","UNAVAILABLE","%s: unknown mailbox command: %02X %02X %02X %02X","The channel port adapter sent a mailbox command that the driver did not expect. This may occur if there is a version mismatch between the system image and the microcode.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPA","3","UNAVAILABLE","Port IO %s process terminating.","Unexpected termination of a port io process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPA","3","UNAVAILABLE","bay [%s] mailbox response timed out after (%u + %u) usecs, mbx=%08X","A mailbox command sent from driver to the channel port adapter never completed within the expected time limit. As a result of this error, the channel port adapter driver will reset the port adapter and reload microcode to it.","The reset and reload rectified the problem. If that did not occur, then try the microcode reload operation again. If the error still occurs, record the output from the following commands:"
"IPA","3","UNAVAILABLE","bay [%u] failed to establish %s connection (%04X)","An attempt to establish the console or debugger connection with the channel port adapter failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPACCESS","2","NOMEMORY","Alloc fail for acl-config buffer. Disabling distributed mode on lc","Unable to malloc a buffer to send access-list configuration down to linecards.","Enter a show chunks command and report the output, along with this error message, to your technical support representative."
"IPACCESS","2","UNAVAILABLE","Alloc fail for acl-config buffer. Disabling distributed mode on lc","Unable to malloc a buffer to send access-list configuration down to linecards.","Enter a show chunks command and report the output, along with this error message, to your technical support representative."
"IPACCESS","2","UNAVAILABLE","Incorrect length acl ipc xdr of type=%s len=%d received","Received an acl message of the wrong size for that type","Report this error message, to your tech support representative."
"IPACCESS","2","UNAVAILABLE","Invalid request to allocate chunk of size %d","We only allow acl chunks of max size IPACCESS_LARGE_CHUNK_SZ","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPACCESS","4","INVALIDACL","Invalid ACL field: [chars] is [dec]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPC","2","UNAVAILABLE","%s: Cannot send IPC message from 0x%x to 0x%x: info 0x%x","An error occurred when sending IPC message","Show tech-support ipc. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPC","2","UNAVAILABLE","Bad refcount in %s, ptr=%x, count=%d","A reference count is used to track the usage of IPC messages.A function increments the count when it begins to use a message and decrements it when it finishes. When the count becomes zero, the data structure is freed. This message indicates that when the count was accessed, it was found to be zero or negative.","Show tech-support ipc. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPC","2","UNAVAILABLE","Boolean NULL in IPC message: %x.","A watched boolean that was allocated while sending the message is found to be NULL, when an ACK arrived.","Show tech-support ipc. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPC","2","UNAVAILABLE","IPC port pre-closure overflow : 0x%x : 0x%x","An application attempts to close an ipc port when there are messages pending in retransmit queue and ipc defer table overflows.","Show ipc ports open. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPC","2","UNAVAILABLE","IPC test: %s","The IPC test routines.","IPC test only - no action required."
"IPC","2","UNAVAILABLE","Invalid IPC Zone 0x%x.","Some operation is attempted on a zone ID not known to IPC","Show tech-support ipc. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPC","2","UNAVAILABLE","Invalid operation at interrupt level: %s %x","Debug Message. An IPC application has attempted an IPC action which has been prohibited from being performed at the interrupt level.","Show ipc ports. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPC","2","UNAVAILABLE","Lock done a deleted element 0x%x","An internal inconsistency was found in some IPC data structures.","Show tech-support ipc. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPC","2","UNAVAILABLE","Message for %x.%x has no receive queue or dispatch routine","The IPC user failed to provide any means of handling the received message.","Show ipc ports. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPC","2","UNAVAILABLE","No handler for ACK with data for port %x.","The IPC receiver appended data to an ACK. But at the sender, there is no corresponding ACK handler.","Show tech-support ipc. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPC","2","UNAVAILABLE","No memory available for %s","The IPC protocol subsystem could not obtain the memory it needed.","If this error message recurs, attempt to reduce memory usage by reducing the number of router features, or interfaces, enabled. Alternatively, add more memory. To display total memory usage for a router enter show memory summary at the privileged command line prompt. To display buffer usage enter show buffers at the prompt. To display IPC usage enter show ipc queue at the prompt"
"IPC","2","UNAVAILABLE","Unlock done on already unlocked element 0x%x","An internal inconsistency was found in some IPC data structures.","Show tech-support ipc. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPC","3","INVALID_PORT_INFO","Invalid port_info in the retry queue message - SRC_PORT = [hex], DEST_PORT = [hex], MSG_TYPE = [hex]","The IPC protocol subsystem detected that the port information is inconsistent. The port information is probably already freed by the application.","Copy the message exactly as it appears on the console or in the system log. Enter the show tech ipc command from the master and the slave, to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPC","3","ISSU_API_ERR","[chars] failed with error code [dec]","An ISSU API could not perform an operation for the IPC layer. The message text includes the error code from ISSU library.","Enter the show issu client command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPC","3","ISSU_ERROR","[chars] failed with error code [dec] for seat [hex]","An ISSU API could not perform an operation for the IPC layer. The message text includes the error code from ISSU library.","Enter the show issu fsm command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPC","4","MSGMAXTIMEOUT","Invalid maximum timeout value [dec] seconds; Period - [dec]; Retries - [dec]","The maximum message timeout for an IPC message exceeds 2 minutes.","Enter the show version command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPC","4","NOPORT","Port Not Found. [hex] --> [hex], Index:[hex], Seq: [dec], flags: [hex], size: [dec]","IPC received a message which is destined for a port that cannot be found by IPC.","Copy the message exactly as it appears on the console or in the system log. Enter the show ipc status, show ipc ports, and debug ipc errors commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPC","4","UNAVAILABLE","Failed for message size %d","System unable to allocate IPC message of required size.","If this error message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative with the gathered information. To display total memory usage for a router enter show memory summary at the privileged command line prompt. To display buffer usage enter show buffers at the prompt. To display IPC usage enter show ipc queue at the prompt"
"IPC","4","UNAVAILABLE","Invalid maximum timeout value %d seconds; Period - %d; Retries - %d","The maximum message timeout for an IPC message exceeds 2 minutes","Capture 'sh version' and contact TAC"
"IPC","4","UNAVAILABLE","Port Not Found. %x -- %x, Index:%x, Seq: %d, flags: %x, size: %d","IPC Received a message which is destined for a port that cannot be found by IPC","Capture 'sh ipc status', 'sh ipc ports' and 'deb ipc errors' outputs and contact TAC"
"IPC","5","UNAVAILABLE","%d messages pending in %s for the port %s(%x.%x) seat %x","Several IPC messages are pending to be processed. If the number increases, it may result in the IPC header cache or buffers being exhausted.","Show tech-support ipc. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPC","5","UNAVAILABLE","%s %s=0x%x %s=0x%x","IPC failed to register the control port","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPC","5","UNAVAILABLE","%s %s=0x%x, %s 0x%x","IPC module could not find an IPC entity that is expected to be existing always","Show tech-support ipc. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPC","5","UNAVAILABLE","%s","IPC API is called with invalid argument.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPC","5","UNAVAILABLE","%s","IPC message returned is Null","Show tech-support ipc. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPC","5","UNAVAILABLE","%s Dest Port 0x%x Session 0x%x Source 0x%x","While processing an incoming message, IPC encountered invalid data in its internal data structures.","Show tech-support ipc. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPC","5","UNAVAILABLE","%s: Flow control callback function is not provided by IPC Client %s","An IPC application cannot be controlled if flow need to be slowed down. This might result in drop of IPC packets","Show ipc ports. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPC","5","UNAVAILABLE","Cannot hold RPC message port: %#x, index: %d, type: %#x","An RPC request for an application could not be added to the RPC request table because pending requests have filled the RPC request table.","Show tech-support ipc. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPC","5","UNAVAILABLE","Failed to intialize IPC client","An IPC application cannot be initialized because its initialization function does not appear in the IPC initialization list.","Show tech-support ipc. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPC","5","UNAVAILABLE","Invalid registration","An IPC application has attempted to register NULL function in the IPC initialization list.","Show tech-support ipc. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPC","5","UNAVAILABLE","Passed Null backpressure handler","IPC cannot register application's NULL function in the IPC Backpressure handler list.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPC","5","UNAVAILABLE","Q=0x%x %s %d","IPC queue is full.Error Message    OUTPUT_INTERPRETER%IPC-5-UNAVAILABLE: Send message to peer for %s failed. Reason: %s Explanation    Client using IPC App Port has not been able to send message","If the reason is 'no such port', then this may be caused because of the difference in the versions of IOS running on Active and the standby. Any other reason, please collect 'sh ipc stat' 'sh ipc rpc', 'sh ipc port' on active and standby RPs and contact tac"
"IPC","5","UNAVAILABLE","VIP-%s","The Cisco IOS software, running on a Versatile Interface Processor (VIP) card, generated this message. The error message has been passed to the Route Processor (RP) or Route Switch Processor (RSP) for display. This message appears only if the user has configured the service slavelog command.","This is actually a Cisco IOS error message from a VIP. Handle it as indicated by the text after the 'VIP-' string in the error message."
"IPC","6","MAXRPCTIMEOUT","Maximum RPC timeout value [dec] seconds set for port [hex]","The maximum RPC timeout for an IPC message exceeds the maximum expected value of 10 minutes.","Enter the show techsupport ipc command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPC","6","STATEFUL","%s","A stateful interprocess communication (IPC) event occurred.","No action is required."
"IPCGRP","3","UNAVAILABLE","%s %s","Failed to create IPC port on RP.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPCGRP","3","UNAVAILABLE","%s (%u)","The ID associated with an IPC card is either missing, duplicated, or cannot be created.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPCGRP","3","UNAVAILABLE","%s (%u)","The IPC application tried to send a message that was larger than IPC could handle. The message was not transmitted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPCGRP","3","UNAVAILABLE","%s (%u)","The slave IPC cannot register with master.It cannot exchange messages with the master.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPCGRP","3","UNAVAILABLE","%s","An IPC card has registered itself to the IPC master twice. The card malfunctioned and its IPC is not active.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPCGRP","3","UNAVAILABLE","%s","Nonblocking IPC command queue initialization failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPCGRP","3","UNAVAILABLE","%s","REXEC-On IPC command failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPCGRP","3","UNAVAILABLE","%s: %s","An IPC error was detected","Copy the error message exactly as it appears, and report it to your technical support representative."
"IPCGRP","3","UNAVAILABLE","Cannot find hwidb for interface(%u/%u)","Interface identifier does not exist for the interface addressed by the corresponding IPC message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPCGRP","3","UNAVAILABLE","Event %u from slot%u/%u: %s","IPC event processing operational errors.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPCGRP","3","UNAVAILABLE","IPC command %u (slot%u/%u): %s","IPC command processing operational errors.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPCGRP","3","UNAVAILABLE","Incorrect msg size (size=%u)","Wrong size of a REXEC-On IPC command.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPCGRP","3","UNAVAILABLE","Invalid interface(%u/%u/%u)","Invalid interface addressed by the corresponding IPC message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPCGRP","3","UNAVAILABLE","Null %s ipc message","An empty IPC message, which is not expected to be received.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPCGRP","3","UNAVAILABLE","Received empty ipc rexec cmd message","REXEC-On IPC command failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPCGRP","3","UNAVAILABLE","System call for command %u (slot%u/%u) : %s (Cause: %s)","IPC kernel system call error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPCOIR","3","UNAVAILABLE","Card in slot %d/%d has an invalid card type in IDPROM","The linecard IDPROM is unprogrammed or has failed.","Contact customer support."
"IPCOIR","3","UNAVAILABLE","Couldn't load %s...","The indicated image is inaccessible","Check the filename."
"IPCOIR","3","UNAVAILABLE","IPC failed (%s) %s slot %u/%u","The IOS IPC protocol reported an unexpected error.","Make sure the indicated card is still plugged in."
"IPCOIR","3","UNAVAILABLE","Image version stamp missing","The loaded image did not contain a recognizable version stamp","Replace the image with known-good bits, and try again."
"IPCOIR","3","UNAVAILABLE","Incorrect API message version 0x%x","The linecard and IOS images are badly out of phase.","Contact customer support."
"IPCOIR","3","UNAVAILABLE","Incorrect message version obj 0x%x op 0x%x version 0x%x","The linecard and IOS images are badly out of phase.","Contact customer support."
"IPCOIR","3","UNAVAILABLE","Remote server refused to load slot %u/%u Error Message    %IPCOIR-3-UNAVAILABLE: TFTP of %s from %s failed...","The indicated image is inaccessible","Check file permissions, network connectivity."
"IPCOIR","3","UNAVAILABLE","Unable to create driver plugin in slot %d/%d.","A valid linecard driver plugin create failed.","Perhaps a memory allocation failure, should not happen."
"IPCOIR","3","UNAVAILABLE","Unable to get an IPC msg buffer in %d tries: slot %u/%u","The IOS IPC buffer pool was empty for a sustained period of time.","Install more processor SDRAM in the PRE."
"IPCOIR","3","UNAVAILABLE","Unable to initialize PRE ports.","The PRE plugin init sequence failed.","Determine and fix cause."
"IPCOIR","3","UNAVAILABLE","Unable to preanalyze driver plugin in slot %d/%d.","A valid linecard driver preanalyze failed.","Possibly incompatible card types"
"IPCOIR","3","UNAVAILABLE","Unsupported card type (0x%x) in slot %d/%d.","The linecard is not supported by this version of IOS","Contact customer support."
"IPCOIR","4","UNAVAILABLE","Get IPC msg buf failed %d time(s): slot %u/%u - retry in %d sec","The IOS IPC buffer pool was temporarily empty.","Consider installing more processor SDRAM in the PRE."
"IPC_RPM","3","UNAVAILABLE","%s %s","The ID associated with an IPC card is either missing, duplicated, or cannot be created.","Copy the error message exactly as it appears, and report it to your technical support representative."
"IPC_RPM","3","UNAVAILABLE","%s (%d)","An invalid IPC message was received during cc command exection","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPC_RPM","3","UNAVAILABLE","%s (%d)","The IPC application tried to send a message that was larger than IPC could handle. The message was not transmitted.","Copy the error message exactly as it appears, and report it to your technical support representative."
"IPC_RPM","3","UNAVAILABLE","%s","IPC card registered itself to the IPC master twice.","Copy the error message exactly as it appears, and report it to your technical support representative."
"IPC_RPM","3","UNAVAILABLE","%s","The IPC ran out of memory buffers.","Reduce the number of applications currently running on the IPC. Copy the error message exactly as it appears, and report it to your technical support representative."
"IPC_RPM","3","UNAVAILABLE","WARNING: ECC Single Bit Error Correction","A ECC Single Bit Error was detected and corrected.","Use the command 'debug rpm ecc' to look at the total number of ECC errors since the system was booted. 'debug rpm ecc count' will set the number of ECC errors that will cause a Switch Over."
"IPC_RSP_CBUS","3","UNAVAILABLE","%s (%d)","System controller Bengal has reported an error/event","Read error reports. SBE are generally not fatal. Most others are"
"IPC_RSP_CBUS","3","UNAVAILABLE","%s (%d)","The ID associated with an IPC card is either missing, duplicated, or cannot be created.","Copy the error message exactly as it appears, and report it to your technical support representative."
"IPC_RSP_CBUS","3","UNAVAILABLE","%s (%d)","The IPC application tried to send a message that was larger than IPC could handle. The message was not transmitted.","Copy the error message exactly as it appears, and report it to your technical support representative."
"IPC_RSP_CBUS","3","UNAVAILABLE","%s","An IPC card has registered itself to the IPC master twice. The card malfunctioned and its IPC is not active.","Copy the error message exactly as it appears, and report it to your technical support representative."
"IPC_RSP_CBUS","3","UNAVAILABLE","%s","The IPC ran out of memory device (MEMD) buffers.","Reduce the number of applications currently running on the IPC. Copy the error message exactly as it appears, and report it to your technical support representative."
"IPC_RSP_CBUS","3","UNAVAILABLE","Hardware queue for card at slot %d not found","IPC messages cannot be transmitted due to a missing hardware queue. The messages were discarded, and subsequent messages will not be transmitted to that card.","Copy the error message exactly as it appears, and report it to your technical support representative."
"IP_DEVICE_TRACKING","4","TABLE_LOCK_FAILED","Table already locked by process-id [dec]([chars])","The IP device tracking table could not be updated because of another process holds a lock on the table.","No action is required."
"IP_DEVICE_TRACKING_HA","4","ENTRY_OUT_OF_SYNC","Host mac-address [enet] ip-address [IP_address] interface [chars]","An inconsistency has been detected between the active supervisor engine IP device tracking table and the standby supervisor engine IP device tracking table for this host.","No action is required."
"IP_DEVICE_TRACKING_HA","3","UNAVAILABLE","%s","A run-time module could not obtain the resources that are required to complete a task. The failure most likely occurred because of a software error or a lack of system memory. Additional details on the nature of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IP_DEVICE_TRACKING_HA","3","UNAVAILABLE","Failed to send %s message to active for %s, %s","The specified synchronization message, which is an internal IPC message, could not be sent to the active unit in the specified run-time module. The failure most likely occurred because of a software error. Additional details on the nature of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IP_DEVICE_TRACKING_HA","4","UNAVAILABLE","Host mac-address %e ip-address %i interface %s","An inconsistency has been detected in the IP device tracking table for this host between active and standby","LOG_STD_NO_ACTION"
"IPFAST","2","FAILOPENIPCPORT","Could not open the IPC ports. [chars]","The IPFAST process could not open the IPC port to communicate to the line card or route processor.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPFAST","2","FASTPORTCREATEERR","Attempt to create [chars] failed after [dec] retries (last error:[chars])","The line card attempted to create a port to the route processor but has failed after a few retries. This condition might result in the CEF becoming disabled on the line card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPFAST","2","FASTPORTOPEN","Requested to open [chars], id [int] when already open. Attempting to re-open.","The line card is attempting to open a port to the route processor when one is already open. This behavior could be transient but might result in multiple ports opened for the same purpose.","The router should be able to recover from this situation. If CEF problems develop for this line card, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPFAST","2","FASTPORTOPENERR","Attempt to open [chars] failed after [dec] retries (last error:[chars])","The line card attempted to open a port to the route processor but has failed after a few retries. This condition might result in the CEF becoming disabled on the line card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPFAST","2","FASTPORTREGISTERERR","Attempt to register [chars] failed after [dec] retries (last error:[chars])","The line card attempted to register a port to the route processor but has failed after a few retries. This condition might result in the CEF becoming disabled on the line card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPFAST","2","INVALSIZE","The IP fast path received an IPC message with an invalid size(size/type - [dec]/[dec])","The IP fast path switching module has received an IPC message with an invalid size.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPFAST","2","MSGDROP","IPC queue limit is reached and message is dropped. queue limit = [dec] cumulative drops = [dec]","The IPC raw queue limit for IP fast path has been reached.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPFAST","3","UNAVAILABLE","Cache update request at interrupt level: %i(%s)-%i(%s)","A programming error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPFAST","3","UNAVAILABLE","Found existing %s specific entry %i%m..%m-%i (%s) when attempting to create %i%d..%d-%i (%s)","Problems related to the IP route cache triggered this debugging message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPFAST","3","UNAVAILABLE","Invalid cache destination %i/%d","The system attempted to add a cache entry for an invalid address.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPFAST","4","UNAVAILABLE","Attempt to create %s failed. Will be retried %d times (last error:%s)","The Linecard is attempting to create a port to the Route processor but has failed. This could be a transient behavior and hence retries will be attempted","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPFAST","4","UNAVAILABLE","Attempt to open %s failed. Will be retried %d times (last error:%s)","The Linecard is attempting to open a port to the Route processor but has failed. This could be a transient behavior and hence retries will be attempted","The router should be able to recover from this situation. If CEF gets disabled for this line card 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPFAST","4","UNAVAILABLE","Attempt to register %s failed. Will be retried %d times (last error:%s)","The Linecard is attempting to register a port to the Route processor but has failed. This could be a transient behavior and hence retries will be attempted","The router should be able to recover from this situation. If CEF gets disabled for this line card, copy the error message exactly as it appears and report it to your Cisco technical support representative"
"IPFAST","4","UNAVAILABLE","Error invalidating IP fast cache due to memory shortage","Running short of memory triggered this debugging message. This could result in wrong switching decisions.","The router memory should be upgraded and if the problem persists copy the error exactly as it appears and report it to your technical support representative."
"IPFAST","4","UNAVAILABLE","Error trying to delete prefix entry for %i/%d (expected %#x, got %#x)","Problems related to the IP route cache triggered this debugging message.","The router should correct for this error. If the router cannot forward packets properly or is experiencing other problems, copy the error message exactly as it appears and report it to your Cisco technical support representative."
"IPFAST","4","UNAVAILABLE","Error trying to insert prefix entry for %i/%d (expected %#x, got %#x)","Problems related to the IP route cache triggered this debugging message.","The router should correct for this error. If the router cannot forward packets properly or is experiencing other problems, copy the error message exactly as it appears and report it to your Cisco technical support representative."
"IPFAST","5","SUCCEEDOPENIPCPORT","Attempt to open the IPC ports succeeded. [chars]","The IP fast switching has succeeded in an attempt to open the IPC port to communicate with the line card or route processor.","No action is required."
"IPFAST","6","UNAVAILABLE","Cache invalidation request for %s","The system is invalidating all cache requests for a given interface.","LOG_STD_NO_ACTION"
"IPFAST","6","UNAVAILABLE","Packet too short from %i, datagram size %d, tl %d","An IP packet which is too short was received","LOG_STD_NO_ACTION"
"IPFLOW","2","UNAVAILABLE","Error initializing Flow Export Template Table","Initialization of the Flow export template table could not be accomplished because of a low memory condition.","Reduce other system activitiy to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"IPFLOW","2","UNAVAILABLE","Error initializing Flow Export queue","Initialization of the Flow export queue could not be accomplished because of a low memory condition.","Reduce other system activitiy to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"IPFLOW","2","UNAVAILABLE","Error initializing Flow background process","Initialization of the Flow background process could not be accomplished because of a low memory condition.","Reduce other system activitiy to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"IPFLOW","2","UNAVAILABLE","Error initializing Flow feature queue","Initialization of the Flow feature queue could not be accomplished because of a low memory condition.","Reduce other system activitiy to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"IPFLOW","2","UNAVAILABLE","Error initializing IP flow cache","Initialization of the Flow cache could not be accomplished because of a low memory condition.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPFLOW","3","UNAVAILABLE","NULL","Flow export is disabled because export destination address matches with one of the interface's IP addresses","IP addresses of all the interfaces must be checked to make sure none of them matches with flow export destination IP address."
"IPFLOW","4","UNAVAILABLE","Error creating %s","Version 9 export template length is zero","LOG_STD_DBG_ACTION"
"IPMCAST_LIB","3","UNAVAILABLE","Failed to sync multicast limit state to the standby RP","An internal failure prevented sending of multicast limit information to the standby RP. Some multicast traffic disruption is possible following a route processor failover.","LOG_STD_NO_ACTION"
"IPMCAST_LIB","4","UNAVAILABLE","Adding %s interface '%s' denied for (%s,%s)","The maximum number of times the given interface appears as incoming or outgoing for some multicast state is reached.","LOG_STD_NO_ACTION"
"IP_HOST_ISSU","2","GET_BUFFER","IP Host ISSU client failed to get buffer for message. Error: %d (%s)","The IP host ISSU client failed to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"IP_HOST_ISSU","2","INIT","IP Host ISSU client initialization failed to %s. Error: %d (%s)","The IP host ISSU client could not be initialized. This initialization failure must be addressed before an in-service software upgrade or downgrade can be performed successfully. Otherwise, a software upgrade or downgrade will result in downtime.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IP_HOST_ISSU","2","SEND_NEGO_FAILED","IP Host ISSU client failed to send negotiation message. Error: %d (%s)","The IP host ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"IP_HOST_ISSU","2","SESSION_NEGO","IP Host ISSU client encountered unexpected client nego_done. Error: %d (%s)","The IP host ISSU client encountered a client negotiation done state that was unexpected. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"IP_HOST_ISSU","2","SESSION_REGISTRY","IP Host ISSU client failed to register session information. Error: %d (%s)","The IP host ISSU client failed to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"IP_HOST_ISSU","3","CAP_INVALID_SIZE","IP_HOST ISSU client capability list is empty.","The IP host ISSU client capability exchange list is empty, which is an invalid condition.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu capability entries commands and your pertinent troubleshooting logs."
"IP_HOST_ISSU","3","CAP_NOT_COMPATIBLE","IP Host ISSU client capability exchange result incompatible.","Based on the results of the capability exchange, the IP host ISSU client is not compatible with the peer.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"IP_HOST_ISSU","3","INVALID_SESSION","IP Host ISSU client does not have a valid registered session.","The IP host ISSU client does not have a valid registered session.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"IP_HOST_ISSU","3","MSG_NOT_OK","IP Host ISSU client 'Message Type %d' is not compatible","The IP host ISSU client received an incompatible message from the peer device. The message cannot be processed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, show issu message group, and show issu negotiated version commands and your pertinent troubleshooting logs."
"IP_HOST_ISSU","3","MSG_SIZE","IP Host ISSU client failed to get the MTU for Message Type %d. Error: %d (%s)","The IP host ISSU client was unable to calculate the MTU for the specified message. As a result, the client is not able to send the message to the standby device.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, show issu message group, and show issu negotiated version commands and your pertinent troubleshooting logs."
"IP_HOST_ISSU","3","SESSION_UNREGISTRY","IP Host ISSU client failed to unregister session information. Error: %d (%s)","The IP host ISSU client failed to unregister session information.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"IP_HOST_ISSU","3","TRANSFORM_FAIL","IP Host ISSU client %s transform failed for 'Message Type %d'. Error: %d (%s)","The IP host ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In either case, the IP host state between the active device and the standby device is not identical.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"IPMCAST_LIB","4","RPF_DEPTH_ERR","Depth for rpf lookup greater than [dec] for [chars]","The number of recursions for resolution of a given route has exceeded the allowed maximum. This is usually due to misconfiguration.","Review and fix the router configuration. If you require further assistance, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPMCAST_LIB","4","RPF_STATIC_ERR","No match for RIB static route [ipv6_addr]/[dec] in static table for root [ipv6_addr]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPMCAST_LIB","6","TIMER_BUSY","Timer drift is accumulating, [dec] msecs","There is large amount of processing load and the timers are accumulating delay.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPMCAST_LIB_RPF","3","INTERNAL_ERROR","An internal error has occured while obtaining RPF information (%s)","RPF handling Internal error","If this error recurs, then issue the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information."
"IPMCAST_LIB_RPF","3","RIB_REGISTER_FAIL","Failed to register with RIB, multicast RPF lookups will notfunction","Multicast could not register with RIB to obtain RPF information later. This will cause severe problem when there is multicast traffic flow, since it will not be possible to obtain RPF information","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPMCAST_LIB_RPF","3","RW_INIT_FAIL","Failed to START/STOP Route-watch debugging for '%s'","Multicast could not START or STOP Route-watch debugging for the specific Address-family (IPv4/IPv6), listed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPMCAST_LIB_RPF","3","RW_START_FAIL","Error trying to start RPF route watch for prefix %s in table %u (%s), RPF information will not be obtained","An internal error has occured while trying to obtain RPF information for a prefix. As a result, subsequent changes in RPF information for the prefix will also not be obtained. This will impact the multicast traffic flow for this prefix","If this error recurs, then issue the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information."
"IPMCAST_LIB_RPF","3","STOP_FAIL","Error trying to stop RPF watch for a prefix","Internal error has occured while trying to stop obtaining RPF change information","If this error recurs, then issue the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information."
"IPMCAST_LIB_RPF","4","RIB_UNREGISTER_FAIL","Multicast failed to unregister with RIB","Multicast could not unregister with RIB when multicast is disabled. There will not be any existing traffic flow since multicast is already disabled. However if enabled again, and if problem is seen with multicast traffic flow, it should be reported","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPMCAST_LIB_RPF","4","RTMGR_TOPO_ERR","Unexpected error accessing topology specific information","An internal error has occured while accessing topology specific information. The RPF information may not be obtained, resulting in problems with multicast flows","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPMCAST_RPF","3","INTERNAL_ERROR","An internal error has occured while obtaining RPF information (%s)","RPF handling Internal error","If this error recurs, then issue the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information."
"IPMCAST_RPF","4","FOREIGN_VRF","RPF for %i (VRF %s) resolves in a foreign VRF (%s)","RPF resolves in a foreign VRF without specifing any encapsulation OR non-IP transport, multicast cannot handle this, hence a tree will no be built. This could be a temporary condition, but if the error persist, check your routing configuration","If this error recurs, then issue the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information."
"IPMCAST_RPF","4","RPF_LOOKUP_LOOP","RPF route lookup loop for %i","A routing loop occurred during the recursive resolution of an RPF address","Check routing tables used for RPF."
"IPMOBILE","2","UNAVAILABLE","IPMOBILE assertion failed: %s","The software detected an inconsistency. This is considered a serious error. The router attempts to continue, but IP Mobility processing may be impaired.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPMOBILE","3","UNAVAILABLE","Unable to open socket","The requested operation could not be accomplished because of a low memory condition.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"IPM_C54X","1","UNAVAILABLE","DSP %d, packet(size %d) too big.","A packet greater than the 256 bytes received on this interface.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPM_C54X","1","UNAVAILABLE","No more ring descriptors available on %d slot.","The DSP driver cannot queue messages up to the dma engine for transmit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. Reset the DSP's on this port module."
"IPM_C54X","1","UNAVAILABLE","dsp %d NOT RESPONDING.","The DSP driver cannot queue messages up to the dma engine for transmit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. Reset the DSP's on this port module."
"IPM_C54X","3","UNAVAILABLE","%d SPMM Modules to support this configuration","Certain configurations require more than 1 SPMM module","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPM_C54X","3","UNAVAILABLE","%s Unable to download the Application overlay firmware. Status returned 0x%x","Error initializing the DSP with the application/overlay firmware.","Power down, reinsert the Port Module and reboot. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPM_C54X","3","UNAVAILABLE","Can't get dsp resources","There are not enough DSP's for all the VIC's in the router.","There are more VIC's in the router than the DSP's can support. You need to upgrade your DSP module to get more DSP's. You can run 'show diag' to figure out how many DSP's the router has."
"IPM_C54X","3","UNAVAILABLE","DSP %d Sending alarm indication","The dsp is indicating and unexpected event has occurred and may not continue to process calls.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPM_C54X","3","UNAVAILABLE","DSP %d Sending alarm indication","The dsp is indicating that it is not able to properly initialize the port(s) it services.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPM_C54X","3","UNAVAILABLE","DSP %d Unable to download the Boot loader firmware, ret = 0x%x","Error initializing the DSP with the bootloader firmware.","Power down, reinsert the Port Module and reboot. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPM_C54X","3","UNAVAILABLE","Epic TDM Switch failure","The EPIC TDM switch failed to acknowledge a command","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPM_C54X","3","UNAVAILABLE","Host is unable to transmit packets to DSP %d","IOS is unable to communicate with one of the DSPs","Reload the IOS image running on the host and Copy the error message exactly as it appears, and ."
"IPM_C54X","3","UNAVAILABLE","No buffers available for DSP buffer pool","Unable to allocate buffers to DSP receive buffer pool.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPM_C54X","3","UNAVAILABLE","Unable to allocate IDB","Unable to allocate DSP Interface IDB.","Copy the error message exactly as it appears, and report it to your technical support representative."
"IPM_C54X","4","UNAVAILABLE","Unsupported or Bad PVDM in SPMM slot %x","The type of Packet Voice DSP Module present is not supported.","You may need to replace the unsupported Packet Voice DSP Module, or upgrade to a version of IOS that supports the PVDM you have. Please refer to documentation to find out what type of PVDMs are supported with which versions on this router."
"IPM_DSPRM","3","UNAVAILABLE","ALARM indication received from dsp %d in dsp group %d","DSP has failed and indicated an alarm.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPM_DSPRM","3","UNAVAILABLE","BAD init config response received from dsp %d in dsp group %d","Initial configuration failed in dsp firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPM_DSPRM","3","UNAVAILABLE","BAD restart indication received from dsp %d in dsp group %d","DSP firmware download is not successful.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPM_DSPRM","3","UNAVAILABLE","Boot loader download failed for dsp %d in dsp group %d","DSP boot loader firmware download is not successful.","Remove/put back DSP module or replace it"
"IPM_DSPRM","3","UNAVAILABLE","Could not bring DSP %d in DSP group %d in service","DSP did not come up after repeated attempts to downloadfirmware.","Check if the dsp is not bad and reload the trunk. Ifproblem persists call support"
"IPM_DSPRM","3","UNAVAILABLE","Insufficient DSP resources %s","DSP resources are not availabe to open a voice channel or to run a voice codec.","Check dsp resource usage and see if number of active calls exceede the limits."
"IPM_DSPRM","3","UNAVAILABLE","Port %d/%d not found in any DSP group","T1 port is not added to any dsp group.","Check if tdm-clock has been configured for this port."
"IPM_NV_EEPROM","3","UNAVAILABLE","Detected invalid NVRAM size: %d bytes","The detected size of NVRAM is not one of the supported sizes.The NVRAM may be bad.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPM_NV_EEPROM","3","UNAVAILABLE","Failed to erase config due to internal error","Password protection feature failed to erase config due to internal error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPNAT","4","ADDR_ALLOC_FAILURE","Address allocation failed for [IP_address], pool [chars] might be exhausted","An address could not be allocated from the IP NAT pool. This condition can cause a translation failure and might result in packets being dropped. The counter for missed packets will be incremented.","Determine if the NAT pool has been exhausted. To reuse any existing addresses in the NAT pool for new packet flows, clear the current NAT entries using the clear ip nat translation command."
"IPNAT","6","CREATED","[chars]","A NAT flow entry was created.","No action is required."
"IPNAT","6","DELETED","[chars]","A NAT flow entry was deleted.","No action is required."
"IPRT","2","UNAVAILABLE","Bad route_compress() call, sdb= %x","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPRT","3","UNAVAILABLE","Bad path pointer of %x for %i, %d max","A software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPRT","3","UNAVAILABLE","Community list check with bad list %d","A user specified an invalid BGP community list number.","Check the system configuration to make sure that the community list specified falls within the valid range."
"IPRT","3","UNAVAILABLE","IP routing table creation failure - %s","An internal software error occurred preventing the creation of new IP routing table.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPRT","3","UNAVAILABLE","IP routing table limit exceeded - %s, %i%m","The number of routes in the named IP routing table has reached the configured limit. No further routes will be added to the table","Reduce the number of routes in the table, or reconfigure the limit"
"IPRT","3","UNAVAILABLE","IP routing table limit warning - %s","The number of routes in the named IP routing table has reached the configured warning limit.","Reduce the number of routes in the table, or reconfigure the limit"
"IPRT","3","UNAVAILABLE","No memory available for %s","The requested operation failed because of a low memory condition.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"IPRT","3","UNAVAILABLE","Un-installing static route %i%m from %s routing table with outgoing interface %s","Restricting the access of static routes that point across vrfs","Remove the static routes that are pointing accross VRF interfaces"
"IPRT","3","UNAVAILABLE","Unable to register IP Routing as a client of RF.","This is a severe error as far as IP routing NSF is concerned","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPRT","4","ROUTECOUNTNEGATIVE","IP route counter negative - %s, %i Attempt: %d","Attempt to decrement IP route counter into negative value","Use clear ip route * command to reset the route counter. If the message still comes out consistently, copy the messages exactly as they appear, and report it to your technical support representative."
"IPRT","4","TRACKOBJECTNONE","Illegal tracking number 0 on static route %i%m [%d/0] via %i, table %d, client %d","The tracking number 0 was assigned to a static route, but 0 is not a legal value.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPRT","4","UNAVAILABLE","Redistribution prefix limit has been reached %s - %d prefixes","We have reached the maximum number of redistributed prefixes","Check if redistribution of large number of prefixes is desired and has not been configured by mistake"
"IPRT","4","UNAVAILABLE","Redistribution prefix threshold has been reached %s - %d prefixes","We have reached the threshold level of number of redistributed prefixes","Check if redistribution of large number of prefixes is desired and has not been configured by mistake"
"IPRT","4","UNAVAILABLE","can't track this type of object","Route maps only support STATE type track objects.This object is not a STATE object","Reconfigure the track object to make it a STATE object."
"IPSECV6","4","UNAVAILABLE","IP protocol in packet mismatched with tunnel mode, packet from %s to %s dropped by %s","We tried to send an IPv4 packet into an IPSec-IPv6 tunnel, or an IPv6 packet into an IPSec-IPv4 tunnel. The tunnel cannot handle this type of packet, and so the packet is dropped.","Modify the tunnel configuration, either by removing the incorrect IP address type from the tunnel interface, or by changing the tunnel mode to match the IP address type."
"IPSECV6","4","UNAVAILABLE","Rec'd packet not an IPSEC packet. 	(ip) dest_addr= %P, src_addr= %P, prot= %d","Rec'd packet matched crypto map ACL, but is not IPSEC-encapsulated. IPSEC Peer is sending unencapsulated packets. There may simply be a policy setup error on the peer. Some might consider this a hostile event.","Contact the peer's administrator to compare policy settings."
"IPSECV6","4","UNAVAILABLE","decaps: rec'd IPSEC packet has invalid spi for 	destaddr=%P, prot=%d, spi=0x%x(%d), srcaddr=%P","Rec'd IPSEC packet specifies SPI that doesn't exist in SADB. This may be a temporary condition due to slight differences in aging of SAs between the IPSEC peers, or it may be because the local SAs have been cleared. It may also be because of bogus packets sent by the IPSEC peer. Some might consider this a hostile event.","If the local SAs have been cleared, the peer may not know this. In this case, if a new connection is established from the local router, the two peers may reestablish successfully. Otherwise if the problem occurs for more than a brief period, either attempt to establish a new connection or contact the peer's administrator."
"IPSECV6","4","UNAVAILABLE","decapsulate: packet has bad %s length destadr=%P, prot=%d, len=%d","Rec'd IPSEC packet is malformed: possibly encapsulation error? The peer is sending malformed packets. It may be due to a decryption error. Some might consider this a hostile event.","Contact the peer's administrator."
"IPSECV6","4","UNAVAILABLE","decapsulate: packet missing %s, destadr=%P, actual prot=%d","Rec'd IPSEC packet missing an expected AH or ESP header The peer is sending packets that don't match the negotiated security policy. Some might consider this a hostile event.","Contact the peer's administrator."
"IPV6FIB","3","UNAVAILABLE","Inconsistent global state '%s' %s","IPV6FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPV6FIB","4","UNAVAILABLE","Invalid XDR length. Type/event %d/%s. XDR %d, buffer %d","IPV6FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPV6FIB","4","UNAVAILABLE","Invalid format. %s","IPV6FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPV6FIB","4","UNAVAILABLE","Missing cef idb for %s during %s","IPV6FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPV6FIB","4","UNAVAILABLE","Missing cef table for tableid %lu during %s event","IPV6FIB_INTERNAL_ERROR","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IP_SNMP","4","UNAVAILABLE","Oversize message from %i, datagram size %u, udp length %u","An incoming SNMP packet had a length field so large that the system had to assume it was in error. This system made a correct reaction to bad external data. Since SNMP packets should originate from systems under the same administration, this may indicate that the network host used to originate the SNMP request had a problem in its networking layer. Alternatively, if the SNMP packet originated from outside the local administrative domain, it could indicate an failed attempt at security penetration and that site should be watched more closely.","If the origin is local, no action is required. If the origin is determined to be malicious, either contact the administrator of the originating site or install filters to prevent access by that site, as circumstances warrant."
"IP_SNMP","4","UNAVAILABLE","SNMP trap source %s has no ip address","The user entered an snmp-server trap-source command. The interface requested for use as the source address has no ipv4 address associated with it. The SNMP trap is being sent anyway, but without the source address that the user intended.","There are two possible solutions. Either enter a no snmp-server trap-source command to disable the request for a specific source IP address, or add an IP address to the interface referenced in the snmp-server trap-source configuration command."
"IP_SNMP","4","UNAVAILABLE","SNMP trap source %s has no ipv6 address","The user entered an snmp-server trap-source command. The interface requested for use as the source address has no ipv6 address associated with it. The SNMP trap is being sent anyway, but without the source address that the user intended.","There are two possible solutions. Either enter a no snmp-server trap-source command to disable the request for a specific source IP address, or add an IPV6 address to the interface referenced in the snmp-server trap-source configuration command."
"IPV6","3","(-1)","Cannot start the IPv6 process; router will not process IPv6 packets.","The IPv6 process could not be started. This machine will not be able to process any IPv6 packets.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"IPV6","3","INTERNAL","Internal error, [chars]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPV6","3","INTERNAL_PAK","Internal error ([chars]): [hex] [hex] [chars]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPV6","3","NO_UNIQUE_IDENTIFIER","Cannot determine an unique IPv6 identifier for the system.IPv6 will not be started.","An unique IPv6 Identifier could not be determined for the system. Therefore the IPv6 process will not be started.This machine will not be able to process any IPv6 packets.","Verify that there is at least one interface in this machine that supports IEEE-style addresses."
"IPV6","3","RIB","[chars]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPV6","3","UNFRAGMENTABLE","Cannot fragment packet: unfragmentable part length [dec], MTU of [dec]","An internal software error occurred. A single packet originated by this system could not be fragmented and has been dropped. Normal system operation continues.","This is a transient error. However, this condition indicates other errors in the software that will require further examination by your Cisco technical support representative. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPV6","4","DUPLICATE_OPTIMISTIC","Duplicate address %P on %s","You have elected not to run duplicate address detection (DAD), but another system is using your IPv6 address.","Change the IPv6 address of one of the two systems."
"IPV6","4","LLA_CONFLICT","LLA conflict for static neighbor on [chars] : [chars]","A neighborhood discovery (ND) message from the specified neighbor carries a link-layer address (LLA) other than the configured address.","Reconfigure the static neighbor with the correct link-layer address."
"IPV6","4","MAXPDB","Exceeded maximum supported IPv6 Routing Protocol instances","Configuration of a routing protocol has failed because it would exceed the maximum supported number of routing protocols.","Reduce the number of IPv6 routing protocol instances configured."
"IPV6","6","ACCESSLOGSP","list [chars]/[dec] [chars] [chars] [chars]->, [dec] packet[chars]","A packet matching the log criteria for the given access list was detected.","No action is required."
"IPV6","4","MULTICAST","Application does not support multicast destination address , packet dropped.","An internal software error occurred. A multicast destination address was used in an local application which does not yet handle IPv6 multicast.","Use a unicast address in commands on the router. If the problem persists, or you feel the command should support multicast, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPV6_ACL","6","ACCESSLOGSP","list %s/%d %s %s %P %s- %P, %d packet%s","A packet matching the log criteria for the given access list was detected.","Informational only. No action required."
"IPV6_ACL","6","UNAVAILABLE","list %s/%d %s %d %P %s- %P, %d packet%s","A packet matching the log criteria for the given access list was detected.","Informational only. No action required."
"IPV6_ACL","6","UNAVAILABLE","list %s/%d %s %s %P %s- %P (%d/%d), %d packet%s","A packet matching the log criteria for the given access list was detected.","Informational only. No action required."
"IPV6_ACL","6","UNAVAILABLE","list %s/%d %s %s %P %s- %P, %d packet%s","A packet matching the log criteria for the given access list was detected.","Informational only. No action required."
"IPV6_ACL","6","UNAVAILABLE","list %s/%d %s %s %P(%d) %s- %P(%d), %d packet%s","A packet matching the log criteria for the given access list was detected.","Informational only. No action required."
"IPV6_ADDRESS","3","UNAVAILABLE","%P/%d can not be configured on %s, %s","An error was encountered while configuring an IPv6 address","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPV6_ADDRESS","3","UNAVAILABLE","Cannot determine an unique IPv6 identifier for the system.IPv6 will not be started.","An unique IPv6 Identifier could not be determined for the system.Therefore the IPv6 process will not be started.This machine will not be able to process any IPv6 packets.","Verify that there is at least one interface in this machine that supports IEEE-style addresses."
"IPV6_ADDRESS","3","UNAVAILABLE","Cannot start an IPv6 process; router will not process IPv6 packets.","An IPv6 process could not be started. This machine will not be able to process any IPv6 packets.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"IPV6_ADDRESS","3","UNAVAILABLE","Internal error, %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPV6_ADDRESS","3","UNAVAILABLE","Uninitialized interface pointer - %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPV6_ADDRMGR","3","UNAVAILABLE","Internal error, %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPV6_FORWARDING","3","UNAVAILABLE","Cannot fragment packet: unfragmentable part length %d, MTU of %d","An internal software error occurred. A single packet originated by this system could not be fragmented and has been dropped. Normal system operation continues.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPV6_FORWARDING","3","UNAVAILABLE","Cannot start an IPv6 forwarding process; router will not process IPv6 packets.","An IPv6 process could not be started. This machine will not be able to process any IPv6 packets.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"IPV6_FORWARDING","3","UNAVAILABLE","Uninitialized buffer pointer - %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPV6_FORWARDING","3","UNAVAILABLE","Uninitialized interface pointer - %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPV6_FORWARDING","4","UNAVAILABLE","Application does not support multicast destination address (%P), packet dropped.","An internal software error occurred. A multicast destination address was used in an local application which does not yet handle IPv6 multicast.","Use a unicast address in commands on the router, if the problem persists, or you feel the command should support multicast, then please contact the TAC with the failing command line."
"IPV6_ICMP","3","UNAVAILABLE","Uninitialized buffer pointer - %s","An internal software error occurred.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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.IPV6_INTF-3Error Message    %IPV6_INTF-3-UNAVAILABLE: Cannot start IPv6 Interface Process. Explanation    The IPv6 Interface Process could not be started. Interfaces will not be enabed for IPv6 Processing. This machine will not be able to process any IPv6 packets.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"IPV6_INTF","3","UNAVAILABLE","Internal error, %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPV6_INTF","3","UNAVAILABLE","The link MTU of %s is below the %u-byte minimum IPv6 link MTU.","As specified in the standard, IPv6 requires that every link has an MTU of at least 1280. Since this link's MTU is below that, IPv6 is held down on this interface.","LOG_STD_NO_ACTION"
"IPV6_INTF","3","UNAVAILABLE","The link MTU of %s is below the %u-byte user set IPv6 link MTU.","The interface link MTU is below the user set IPv6 link MTU. IPv6 is held down on this interface.","LOG_STD_NO_ACTION"
"IPV6_INTF","4","UNAVAILABLE","High load on interface events (%s), auto-recovery complete.","The router has automatically recovered from a condition normally brought about by high load. If this occurs frequently, please contact the TAC.","LOG_STD_NO_ACTION"
"IPV6_ND","3","UNAVAILABLE","Cannot start an IPv6 Neighbor Discovery process; router will not process IPv6 packets.","An IPv6 process could not be started. This machine will not be able to process any IPv6 packets.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"IPV6_ND","3","UNAVAILABLE","Internal error, %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPV6_ND","3","UNAVAILABLE","Router %P on %s conflicting ND setting %s","Another router on the link sent router advertisements with conflicting parameters to ours.","Verify that all IPv6 routers on the link have the same parameters in the router advertisement for hop-limit, managed-config-flag, other-config-flag, reachable-time and ns-interval, and that preferred and valid lifetimes for the same prefix, advertised by several routers are the same. Use the command show ipv6 interface to list the parameters per interface."
"IPV6_ND","3","UNAVAILABLE","Uninitialized data - %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPV6_ND","4","UNAVAILABLE","Duplicate address %P on %s","Another system is using your IPv6 address.","Change the IPv6 address of one of the two systems."
"IPV6_ND","4","UNAVAILABLE","Duplicate address %P on %s","You have elected not to run DAD, but another system is using your IPv6 address.","Change the IPv6 address of one of the two systems."
"IPV6_ND","4","UNAVAILABLE","LLA conflict for static neighbor %P on %s : %s","This error indicates that an ND message from the specified neighbor carries a Link Layer Address other than that configured via static neighbor","Reconfigure the static neighbor with correct LLA"
"IPV6_ND","4","UNAVAILABLE","Prefix %P/%d advertised in RA on %s has been previously configured on another interface","This warning indicates that an on-link prefix advertised in an IPv6 ND RA on the specified interface has previously been configured on another interface. The prefix will be ignored on the current prefix","Learning an on-link prefix via IPv6 ND RA when the same prefix has previously been configured on another interface indicates a likely configuration error, either on the current router or on the neighbor router advertising the ND RA. Review network topology, current router and adjacent router configuration, and correct as appropriate"
"IPV6_ND","4","UNAVAILABLE","Prefix %P/%d advertised in RA on %s was previously learnt on another interface","This warning indicates that an on-link prefix advertised in an IPv6 ND RA on the specified interface has previously been learnt from an RA on another interface. The prefix will be ignored on the current interface","Learning the same on-link prefix via IPv6 ND RA on multiple interfaces indicates a likely configuration error on adjacent routers. Review network topology and adjacent router configuration and correct as appropriate."
"IPV6_ND","6","UNAVAILABLE","%P/%d can not generate auto-configured address on %s, %s%s","IPv6 address could not be auto-configured.","NOG_STD_NO_ACTION."
"IPV6_RIP","3","UNAVAILABLE","Uninitialized interface pointer - RIPv6","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPV6_ROUTING","3","UNAVAILABLE","%s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPV6_ROUTING","3","UNAVAILABLE","IPv6 routing table limit exceeded - %s","The number of routes in the named IPv6 routing table has reached the configured limit. No further routes will be added to the table","Reduce the number of routes in the table, or reconfigure the limit."
"IPV6_ROUTING","3","UNAVAILABLE","IPv6 routing table limit warning - %s","The number of routes in the named IPv6 routing table has reached the configured warning limit.","Reduce the number of routes in the table, or reconfigure the limit."
"IPV6_ROUTING","3","UNAVAILABLE","Internal error, %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPV6_ROUTING","4","UNAVAILABLE","Exceeded maximum supported IPv6 Routing Protocol instances","This error indicates that configuration of a Routing Protocol has failed because it would exceed the maximum supported number of Routing Protocols","Reduce the number of IPv6 Routing Protocol instances configured"
"IPV6_ROUTING","6","UNAVAILABLE","IPv6 routing table limit recovered - %s","The number of routes in the named IPv6 routing table has fallen below the configured limit. The routing table has recovered","LOG_STD_NO_ACTION"
"IPX","3","NOVNOSTART","IPX Failed to Start due to insufficient memory","The Novell IPX routing subsystem failed to initialize properly due to memory allocation errors, usually due to insufficient amount of available memory.","Free up memory, look for a possible memory leak, or upgrade the system to have more memory."
"IPX","3","UNAVAILABLE","Bad IPX server count. %s %d, %s %d","The internal SAP service count does not match the number of services currently present and displayed by the show ipx servers command.","If this message recurs, report the problem to your echnical support representative, along with the output of the show ipx servers command taken before the message appeared and again after the message appeared."
"IPX","3","UNAVAILABLE","Cannot send incremental SAP update to peer on %s. 	Increasing output-sap-delay may help","An incremental SAP update could not be sent, because this might cause the SAP tables between peers to become out of synch.","Increase the output SAP delay on the listed interface to reduce buffer usage. If, after changing the delay the message remains, copy the error message exactly as it appearsand 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IPX","3","UNAVAILABLE","Consistency check failed for SAP table %d.","An internal SAP table consistency check failed.","Copy the error message exactly as it appears, and report it to your technical support representative."
"IPX","3","UNAVAILABLE","Duplicate SAP entry insert attempted. %s%s %s0x%x %s0x%x %s%d %s0x%x %s0x%x %s0x%x","An IPX SAP service entry, which is being added currently, already exists in he current internal table.","Report the error messages and the tracebacks following them to your technical support representative."
"IPX","3","UNAVAILABLE","IPX Failed to Start due to insufficient memory","The Novell IPX routing subsystem failed to initialize properly due to memory allocation errors, usually due to insufficient amount of available memory.","Free up memory, look for a possible memory leak, or upgrade the system to have more memory."
"IPX","3","UNAVAILABLE","Inconsistency in the %s LSP Linkage data structure detected.","An internal inconsistency was detected in the RDB or SRDB internal routing table structure. Specifically, a data area used by NLSP to link LSPs.","Copy and save this message. If NLSP is not running this could mean there is a software or hardware problem which is corrupting memory. If the message recurs, copy and save the messages, and call your technical support representative for assistance."
"IPX","3","UNAVAILABLE","Invalid number of paths (%d) for %q","An internal inconsistency was detected in the IPX routing table structure.","Copy and save this message. If possible, clear the IPX routing table by issuing the clear ipx route command. (This will result in lost connectivity until the routing table is rebuilt.) If the message recurs, copy and save the message, along with the output from the show ipx route, and call your technical support representative for assistance."
"IPX","3","UNAVAILABLE","Too many networks. The number of directly connected IPX networks cannot exceed %d","The limit of connected IPX networks has been reached. Additional IPX interfaces cannot be configured.","Do not configure IPX on additional interfaces. Remove IPX configuration commands from inactive interfaces."
"IPX","3","UNAVAILABLE","Unsupported SAP type for EIGRP being %s - type %x","There are two types of service access points (SAPs)-general queries and general responses. This message is sent when you receive or attempt to send an SAP with a type code which is not a general query or a general response. It is also sent when you receive a general query not addressed to the broadcast address.","Copy the error message exactly as it appears, and report it to your technical support representative. If possible, also provide the output of the debug ipx sap activity and debug ipx sap event commands for the period during which this message appeared."
"IPX","6","UNAVAILABLE","%s %s %s %s %x.%e %s %x.%e %d pkt%s","If IPX access violation logging is enabled, these messages are displayed when an access list logging event has occurred.","Verify that the host system is permitted or denied as defined in the access list."
"IPX","7","UNAVAILABLE","%s: %08x %08x %08x %08x %08x","Internal use only","Should not be seen in the field"
"IP_VRF","3","UNAVAILABLE","%s","Caching of Interface List update for VRF failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IP_VRF","3","UNAVAILABLE","%s","IP VRF creation failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IP_VRF","3","UNAVAILABLE","%s","Invalid parameter.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IP_VRF","3","UNAVAILABLE","%s","VRF infrastructure failure for Platform VRFs.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IP_VRF","3","UNAVAILABLE","%s","VRF tableid already allocated.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IP_VRF","3","UNAVAILABLE","%s","VRF tableid inconsistent between two RPs.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IP_VRF","3","UNAVAILABLE","%s","VRF tableid invalid","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IP_VRF","3","UNAVAILABLE","%s","cached vrf entry creation failed","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IP_VRF","3","UNAVAILABLE","%s","cached vrf initialization failed","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IP_VRF","3","UNAVAILABLE","Invalid VRF id 0x%x in %s","VRF ID Invalid","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IP_VRF","3","UNAVAILABLE","Memory allocation failure","VRF MALLOC failure","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IP_VRF","3","UNAVAILABLE","VRF %d name record is null %s","VRF name record is null","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IP_VRF","3","UNAVAILABLE","VRF %s iflist is not empty in %s","VRF iflist is not empty","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IP_VRF","4","VRF_DELETE_WAIT","The VRF [chars] is getting deleted after a wait","There are routes remaining in the deleted VRF routing table. To ensure reusablity of the same VRF, the system forcibly clears the routes in the VRF routing table, which causes the VRF to be deleted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISA","1","ALIGN","Alignment failure on packet buffer: [hex]","A software error has occurred. The ISA driver detected that the buffer is not aligned correctly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISA","1","ERROR","[chars]","An error occurred in the application using ISA.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISA","6","INFO","[chars]","This is an informational message from ISA.","This is an informational message only and occurs in normal operation. No action is required."
"ISA","1","INITDESCRING","Slot [dec]: The ISA driver failed to allocate 'descriptor offsets' write_offsets: [hex], read_offsets: [hex], stored_offsets: [hex]","The ISA driver failed to initialize at the specified point.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISA","1","INITFAIL","Slot [dec]: [chars]","The ISA driver failed to initialize at the specified point.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISA","1","NOMEMORY","[chars] creation failed for slot [dec]","The ISA driver, in its initialization phase, could not allocate memory for the specified data structure.","Consider adding more shared memory. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISA","1","OWNER","[chars] packet buffer, pak=[hex]","A software or hardware error has occurred. The ISA driver detected that the buffer ring is in an inconsistent and unrecoverable state.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISA","6","SHUTDOWN","[chars] shutting down","The specified ISA is shutting down. It may have been physically removed.","This is an informational message only and occurs in normal operation. No action is required."
"ISA","1","TOOBIG","[chars] received a packet with size [dec].","The system has received a packet that is larger than the allowed size.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISA","6","UNAVAILABLE","%s","This is informational message from ISA","This is informational message from ISA. This occurs in normal operation."
"ISA","6","UNAVAILABLE","%s shutting down","The specified ISA is shutting down. It may have been physically removed.","This is an informational message only. It occurs in normal operation."
"ISDN","1","UNAVAILABLE","msgtxt_nomemory","The requested operation could not be accomplished because of a low memory condition.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"ISDN","2","UNAVAILABLE","%s:%d","A debug - traceback condition has occurred","LOG_STD_NO_ACTION"
"ISDN","3","UNAVAILABLE","%s: Resource not available, at %s:%d","Hardware resource could not be allocated","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISDN","4","UNAVAILABLE","%s: Bad Event Received For Current State","The State Transition for the ISDN L2 Socket Process failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISDN","4","UNAVAILABLE","%s: Failed to Open Required Temporary Socket%s","The (Re)Open attempt for a required temporary socket failed, without this socket the L2 socket process will fail","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISDN","4","UNAVAILABLE","%s: Occurred at %s:%d","An unexpected event of significance has occurred","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISDN","4","UNAVAILABLE","%s: Spurious Connection Accepted and Closed on port %u","An unknown TCP connection was accepted and refused.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISDN","4","UNAVAILABLE","%s: isdn_create_delete_signalling_channel: Unknown DSL %u for %s","The Creation/Deletion service for the L2 Signalling handler for the given DSL is missing","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISDN","4","UNAVAILABLE","%s: isdn_get_status_state: Unknown DSL %u","An attempt to retrieve the status of a DSL that is not currently configured.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISDN","4","UNAVAILABLE","%s: isdn_to_L2: Unknown DSL %u for command %s","The ISDN Stack has not registered its L2 Message Handler","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISDN","4","UNAVAILABLE","ISDN SC %s: Status Changed to: %s.","ISDN has been notified by the RLM component of a status change in the RLM link","LOG_STD_NO_ACTION"
"ISDN","4","UNAVAILABLE","Interface %s, Ignoring call, EndPoint Identifier (EID) mismatch","The incoming ISDN call is ignored because the EID delivered in the incoming setup message cannot be matched.","If EID is delivered in the setup message, use the isdn debugs and show isdn status commands to determine the current EID values. You may need to contact the service provider."
"ISDN","4","UNAVAILABLE","Interface %s, Ignoring call, LDN and Called Party Number mismatch","The incoming ISDN call is ignored because the Called Party Number does not match the LDN numbers configured in the router.","Correct the LDN in the router to match the Called Party Number delivered in the incoming setup message."
"ISDN","4","UNAVAILABLE","Interface %s, Spid%d was rejected","The SPID configured in the router has been rejected by the switch.","Determine the correct SPID, reenter the SPID and clear the BRI interface."
"ISDN","6","UNAVAILABLE","%s %s %s %s","The NFAS D-channel status has changed.","Informational only. No action required."
"ISDN","6","UNAVAILABLE","%s: Invalid Timer Handle, caller 0x%x handle %3d","This could be an indication of low memory. It is sent when an invalid ISDN timer handle is passed on for timer operations","Capture the show isdn mem, show isdn status output for possible debugging information. Reduce other system activity to ease the memory demands in the system."
"ISDN","6","UNAVAILABLE","Interface %s Call Cid 0x%x Cref 0x%x collision on Channel %d in_use_cid 0x%x cref 0x%x, Channel awarded to the received call","This is an informational message. It is sent when a Call is received that collides with an existing call on the same channel.","Informational only. No action required."
"ISDN","6","UNAVAILABLE","Interface %s Requested Channel %d is not available","This is an informational message. It is sent when the requested channel is not available.","Informational only. No action required."
"ISDN","6","UNAVAILABLE","Interface %s disconnected from %s %s, call lasted %u seconds","This is an informational message sent when a call is disconnected. The message displays the remote name and number, which it receives from the Point-to-Point Protocol (PPP) authentication or from where the dialer placed the call to. It also shows how long the call lasted.","Informational only. No action required."
"ISDN","6","UNAVAILABLE","Interface %s is now connected to %s %s","This is an informational message sent when a call is connected. The message displays the remote name and number, which it receives from the Point-to-Point Protocol (PPP) authentication or from where the dialer placed the call to.","Informational only. No action required."
"ISDN","6","UNAVAILABLE","Layer 2 for Interface %s, TEI %u changed to down","This is an informational message. It is sent when an ISDN Layer2 logical link is down. It also shows the TEI associated with this logical link.","Informational only. No action required."
"ISDN","6","UNAVAILABLE","Layer 2 for Interface %s, TEI %u changed to up","This is an informational message. It is sent when an ISDN Layer2 logical link is up. It also shows the TEI associated with this logical link.","Informational only. No action required."
"ISDN","6","UNAVAILABLE","No Free Timer Entry, caller 0x%x, timers used %d","This could be an indication of low memory. It is sent when the ISDN protocol cannot start new timers for it's operation.","capture the show isdn mem, show isdn status output for possible debugging information. Reduce other system activity to ease the memory demands in the system."
"ISISL2","3","MCAST_EVENT_UPD_FAILURE","%s-RIBInfo%s: %s client failed to send Multicast event (%u, %d) update request with error %s","ISISL2 client failed to send out Multicast event notification","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISISL2","3","MCAST_RT_UPD_REP_FAILURE","%s-RIBInfo%s: %s client receives the response of Multicast RT %s message with code:%d topoid:%u","ISISL2 client receives the response of Multicast RT update failure","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISISL2","3","MCAST_RT_UPD_REQ_FAILURE","%s-RIBInfo%s: Multicast RT (%u, %s, %s): Failed to send the route update request to MLMRIB with error %s","ISISL2 client failed to send the Multicast route update request to MLMRIB","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISISL2","3","UNICAST_EVENT_UPD_FAILURE","%s-RIBInfo%s: %s client failed to send Unicast event (%u, %d) update request with error %s","ISISL2 client failed to send out Unicast event notification","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISISL2","3","UNICAST_RT_UPD_REP_FAILURE","%s-RIBInfo%s: %s client receives the response of Unicast RT %s message with code:%d topoid:%u","ISISL2 client receives the response of Unicast RT update failure","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISISL2","3","UNICAST_RT_UPD_REQ_FAILURE","%s-RIBInfo%s: Unicast RT (%u, %s): Failed to send the route update request to MLURIB with error %s","ISISL2 client failed to send Unicast route update request to MLURIB","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","BAD_PARAMS","%s","Bad parameters were detected in the ISSU process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","BASE_CLIENT_CHECK_COMPATIBILITY","%s","An error was found during checking of the ISSU base client compatibility.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","CLIENT_OR_ENTITY_NOT_REG","Client([dec]) or entity([dec]) is not registered [chars].","The specified client or entity is not registered.","Enter the show issu client | grep client id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","CLIENT_REG_DIST","Failed to %s distributed client %d","A distributed client reservation or unreservation failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","DEBUG_ERROR","[chars]","An error occurred when turning on ISSU debug.","Enter the show issu client | grep client id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","DUMY_ENTRY_NOT_LAST","Dumy cap entry is not last one for cap group([dec]) registration under client([dec]) and entity([dec])","The dummy cap entry is not the last one for the cap group registration.","Enter the show issu client | grep client id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","DUMMY_VERSION_OUT_OF_RANGE","Dummy msg version (%d) is out of range for msg(%d) under client %s(%d) and entity(%d).","The dummy message version is out of range.","Enter the show issu client | grep client id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","DUP_ENTITY_REG","Entity(%d) is registered already under client %s(%d)","Entity is duplicated under client.","Enter the show issu client | grep client id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","DUP_DUMMY_VERSION_REG","%s is already registered under client %s(%d), entity(%d), and msgtype(%d)","The specified item is registered already under that message type.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu message type | include commands and your pertinent troubleshooting logs."
"ISSU","3","DUP_ENTITY_REG","Entity([dec]) is registered already under client([dec])","The entity is duplicated under the client.","Enter the show issu client | grep client id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","DUP_ITEM_IN_REG_UNDER_ENTITY","[chars] is duplicated [chars] under client([dec]) and entity([dec])","Item is duplicated under the client and entity.","Enter the show issu client | grep client id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","DUP_REG_ENDPOINT","Endpoint is registered already.","The endpoint is already registered.","Enter the show issu endpoint command to check if the ISSU subsystem was initialized twice."
"ISSU","3","DUP_REG_UNDER_ENDPOINT","[chars]([dec]) is registered already under endpoint.","The item is already registered under the endpoint.","Enter the show issu client | grep client id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","DUP_REG_UNDER_ENTITY","[chars]([dec]) is registered already under client([dec]) and entity([dec])","The item is already registered under the client and entity.","Enter the show issu client | grep client id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","EMPTY_DUMMY_VERSION","%s is empty under client %s(%d), entity(%d).","The dummy version is empty.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","EMPTY_UNDER_CLIENT","[chars] is empty under client([dec]).","The item is empty in the client.","Enter the show issu client | grep client id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","EMPTY_UNDER_ENDPOINT","[chars] is empty under endpoint.","The item is empty under the endpoint.","Enter the show issu client | grep client id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","EMPTY_UNDER_ENTITY","[chars] is empty [chars] under client([dec]) and entity([dec]).","The item is empty in the client and entity.","Enter the show issu client | grep client id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","ENDPOINT_NOT_REG","Endpoint is not registered yet.","The endpoint is not registered yet.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","ERP_AGENT","[chars]","One of the primary functions for the ERP agent failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","ERP_AGENT_SEND_MSG","[chars]; error code is [chars]","The send message function call failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","ERP_CLIENT","[chars]","One of the primary functions for the ERP client failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","ERP_CLIENT_EVENT","Unknown [chars] event - [dec]","An unknown event was received.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","EXTERNAL_MATRIX_FILE_ERR","Line %u: %s","An error was found in the external matrix data file.","Open a case with TAC, and attach the output of the more ivfs:/matrix_cm_file command, where matrix_cm_file is the output of the dir system:image command."
"ISSU","3","FAILED_TO_ALLOC_CHUNK_MEMORY","[chars] type chunk allocation failed.","A memory allocation has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","FAILED_TO_ALLOC_DUMMY_VERSION","Can not allocate %s under client %s(%d) and entity(%d)","The ISSU process could not allocate a dummy version under the client and entity.","Enter the show proc mem or show buffs command to determine whether the memory or buffer is full, indicating a possible memory leak. To recover, shut down any unused tasks and reset the cards. If these actions do not help, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","FAILED_TO_ALLOC_ENTITY","Can not allocate entity([dec]) under client([dec])","Cannot allocate an entity control block under the client.","Enter the show proc mem or show buffs command to check if memory or buffer is full. Shuting down unused tasks or resetting cards usually can recover a memory leak problem. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","FAILED_TO_ALLOC_FUNCT_UNDER_ENDPOINT","Can not allocate [chars].","Cannot allocate the function callback.","Enter the show proc mem or show buffs command to check if memory or buffer is full. Shutingt down unused tasks or resetting cards usually can recover those memory leak problem. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","FAILED_TO_ALLOC_FUNCT_UNDER_ENTITY","Can not allocate [chars] under client([dec]) and entity([dec])","Cannot allocate control block under the client and entity.","Enter the show proc mem or show buffs command to check if memory or buffer is full. Shuting down unused tasks or resetting cards usually can recover a memory leak problem. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","FAILED_TO_ALLOC_MEMORY","memory allocation for %s failed.","The ISSU process could not allocate memory.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","FAILED_TO_ALLOC_UNDER_ENDPOINT","Can not allocate [chars]([dec]) control block.","Cannot allocate a control block.","Enter the show proc mem or show buffs command to check if memory or buffer is full. Shuting down unused tasks or resetting cards usually can recover a memory leak problem. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","FAILED_TO_ALLOC_UNDER_ENTITY","Can not allocate [chars]([dec]) under client([dec]) and entity([dec])","Cannot allocate a control block under the client and entity.","Enter the show proc mem or show buffs command to check if memory or buffer is full. Shuting down unused tasks or resetting cards usually can recover a memory leak problem. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","FAILED_TO_ALLOC_UNDER_GROUP","Can not allocate [chars]([dec]) for [chars]([dec]) registration under client([dec]) and entity([dec])","Cannot allocate an item for group registration under the client and entity.","Enter the show proc mem or show buffs command to check if memory or buffer is full. Shuting down unused tasks or resetting cards usually can recover a memory leak problem. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","FAILED_TO_ALLOC_UNDER_MSG","Can not allocate [chars] for msg ([dec]) registration under client([dec]) and entity([dec])","Cannot allocate a control block for message registration.","Enter the show proc mem or show buffs command to check if memory or buffer is full. Shuting down unused tasks or resetting cards usually can recover a memory leak problem. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","FAILED_TO_ALLOC_UNDER_MSG_SES","Can not allocate [chars] for msg session([dec]) registration under client([dec]) and entity([dec])","Cannot allocate a control block for message session registration.","Enter the show proc mem or show buffs command to check if memory or buffer is full. Shuting down unused tasks or resetting cards usually can recover a memory leak problem. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","FAILED_TO_CREATE_ID32_SPACE","Failed to create ID32 space.","Failed to create ID32 space.","Enter the show proc mem or show buffs command to check if memory or buffer is full. Shuting down unused tasks or resetting cards usually can recover a memory leak problem. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","FAILED_TO_INIT_ISSU_PROTO","Failed to initialize ISSU proto.","Failed to initialize the ISSU protocol.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","FAILED_TO_UNREG_SES","Failed to unregister [chars] session under client([dec]) and entity([dec])","Failed to unregister the session.","Enter the show proc mem or show buffs command to check if memory or buffer is full. Shuting down unused tasks or resetting cards usually can recover a memory leak problem. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","FOREIGN_OWNED_FIELDS","%s; err code [%s]","The transformation of a foreign owned field (FOF) has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","FSM_BADMSG","Peer session [dec] while receiving message [chars] is wrong.","Sessions on peers are mismatched or were not found.","Enter the show issu session | grep session id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","FSM_DUP_UID","Duplicate unique_id on session [dec]: my_uid [dec], peer_uid [dec].","The requirement that each endpoint must have distinctive identifier has been violated.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","FSM_INIT","Fail to create process during FSM init.","Creation of an FSM timer process has failed.","Check what system resources are available during bootup."
"ISSU","3","FSM_MISMATCH_MTU","ISSU nego failed for client %s(%d) entity_id %d session %d due to mismatch of mtu size %d & %d.","The ISSU negotiation failed due to a mismatch in the negotiation version MTU size.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message types, and show issu fsm | include commands and your pertinent troubleshooting logs."
"ISSU","3","FSM_NEGO_SEND_ERR","Client '%s' with ID %d encountered '%s' in session %d.","The ISSU negotiation message could not be sent.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session | include, and show issu fsm commands and your pertinent troubleshooting logs."
"ISSU","3","FSM_RUNTIME_ERR","[chars] occurs during FSM negotiation in session [dec].","Runtime error occurs during FSM negotiation.","Enter the show issu session | grep session id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","HANDLE_SIZE","Handle buffer size is %d, should be %d","A statically defined handle buffer size is incorrect.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","INCOMPATIBLE_BASE_CLIENTS","%s","This message displays a list of ISSU base clients found to be incompatible.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","INCOMPATIBLE_PEER_UID","Setting image (%s), version (%s) on peer uid (%d) as incompatible","The peer client is incompatible.","Synchronize the configurations and reload the standby supervisor."
"ISSU","3","INCONSISTENT_MSG_TYPE","%s","A runtime registration error has occurred. Message types passed for foreign owned fields (FOFs) are inconsistent.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","IN_USE_UNDER_ENDPOINT","[chars]([dec]) is in use under endpoint","Item is in use under the endpoint.","Enter the show issu session | grep session id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","IN_USE_UNDER_ENTITY","[chars]([dec]) is in use under client([dec]) and entity([dec])","Item is in use under the client and entity.","Enter the show issu session | grep session id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","INVALID_ITEM_UNDER_ENDPOINT","Invalid [chars] under endpoint","Invalid item under the endpoint.","Enter the show issu session | grep session id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","INVALID_ITEM_UNDER_ENTITY","Invalid [chars] under client([dec]) and entity([dec])","Invalid item under the client and entity.","Enter the show issu session | grep session id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","INVALID_PARAM_UNDER_SES","Invalid params %s under session(%d)","Invalid parameters were detected under the session.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu session | include commands and your pertinent troubleshooting logs."
"ISSU","3","INVALID_VERSION_LOWHIGH","Invalid low([dec]) and high([dec]) value for msg([dec]) under client([dec]) and entity([dec]).","Invalid low and high value for group registration.","Enter the show issu session | grep session id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","IN_USE_UNDER_ENDPOINT","%s(%d) is in use under endpoint","Item is in use under endpoint.","Enter the show issu session | grep session id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","IN_USE_UNDER_ENTITY","%s(%d) is in use under client %s(%d) and entity(%d)","Item is in use under client and entity.","Enter the show issu session | grep session id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","IPC_PORT","Port name '[chars]' failure; reason is '[chars]'.","Creation or removal of the named port failed for IPC.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","ISSU_INIT_NOT_COMPLETE","%s","ISSU initialization has not been completed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","JID","Failed to get the local process JID with err %d","The system manager call to collect the job ID has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","MISSING_ITEM_IN_REG","[chars]([dec]) is not available [chars] under client([dec]) and entity([dec])","Item is not available for registration.","Enter the show issu session | grep session id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","MSG_NEGO_RESULT_CHUNK","Failed to %s element %x","The message negotiation result element could not be locked or freed, indicating an invalid element or corrupted memory.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","MSG_SES_IN_MSG_NOT_FOUND","The intended session %d specified in received %s for client %s(%d) is not found.","No session could be found with the session ID specified in the received message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu session | include commands and your pertinent troubleshooting logs."
"ISSU","3","NON_ISSU_ID_UNDER_ENDPOINT","Non ISSU [chars]","Peer endpoint does not support ISSU.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","NO_PEER_UID","No peer uid found at [chars]","No peer UID with this value was found registered in the ISSU database.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","NO_UID","No uid (%d) registered with ISSU at %s","No uid with this value found registered in ISSU Database","Copy the error and send it to TAC who can contact ISSU infrastructure team to check why no uid with this value found registered in ISSU Database"
"ISSU","3","NOT_DUMY_CAP_TYPE","Cap type([dec]) is not dumy one.","Cap type is not dummy.","Enter the show issu cap type | grep cap type command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","NOT_FIND_ENTITY","Can not find entity([dec]) under client([dec]).","Cannot find entity under the client.","Enter the show issu session | grep session id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","NOT_FIND_FUNCT_UNDER_SESSION","Can not find [chars] under [chars] session([dec]).","Cannot find function under the session.","Enter the show issu session | grep session id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","NOT_FIND_MSG_SES","Can not find message session([dec]) [chars].","Cannot find message session.","Enter the show issu session | grep session id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","NOT_FIND_UNDER_ENDPOINT","Can not find [chars]([dec]) control block under endpoint.","Cannot find a control block under the endpoint.","Enter the show issu client | grep client id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","NOT_FIND_UNDER_ENTITY","Can not find [chars]([dec]) control block under client([dec]) and entity([dec]).","Cannot find a control block under the client and entity.","Enter the show issu client | grep client id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","NOT_FIND_UNDER_SESSION","Can not find [chars]([dec]) under [chars] session([dec]).","Cannot find item under the session.","Enter the show issu session | grep session id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","NOT_REG_UNDER_ENDPOINT","[chars]([dec]) is not registered under endpoint.","Item is not registered under the endpoint.","Enter the show issu client | grep client id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","NOT_REG_UNDER_ENTITY","[chars]([dec]) is not registered under client([dec]) and entity([dec])","Item is not registered under the client and entity.","Enter the show issu client | grep client id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","NO_UID","No uid ([dec]) registered with ISSU at [chars]","No UID with this value was found registered in the ISSU database.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","NULL_CALLBACK_UNDER_ENDPOINT","[chars] callback is NULL for registration.","Callback is NULL for registration.","Enter the show issu client | grep client id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","NULL_CALLBACK_UNDER_ENTITY","[chars] callback is NULL for msg session registration under client([dec]) and entity([dec])","Callback is NULL for message session registration.","Enter the show issu client | grep client id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","NULL_CALLBACK_UNDER_SESSION","Can not register null [chars] callback in [chars] session([dec]).","Cannot register NULL callback in the session.","Enter the show issu session | grep session id and show issu fsm | grep session id commands. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","PEER_IMAGE_INCOMPATIBLE","Peer image (%s), version (%s) on peer uid (%d) is incompatible","The peer client is incompatible.","Synchronize the configurations and reload the standby supervisor."
"ISSU","3","PEER_IMAGE_NOT_IN_INCOMP_LIST","Peer image (%s), version (%s) on peer uid (%d) is not in the incompatible images list","The peer client is incompatible.","Synchronize the configurations and reload the standby supervisor."
"ISSU","3","PEER_IMAGE_REM_FROM_INCOMP_LIST","Peer image (%s), version (%s) on peer uid (%d) being removed from the incompatibility list","The peer client is incompatible.","Synchronize the configurations and reload the standby supervisor."
"ISSU","3","PEER_INCOMP_SET","Peer incompatibility set for image (%s), version (%s) on peer uid (%d)","The peer client is incompatible.","Synchronize the configurations and reload the standby supervisor."
"ISSU","3","PEER_UID_CB_IS_NULL","Peer uid control block is NULL","The peer client is incompatible.","Synchronize the configurations and reload the standby supervisor."
"ISSU","3","PROTO_CLIENT_ENTITY_UNREG","Proto Client entity unreg for [chars] has failed","A protocol client has failed to unregister its entity with ISSU.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","PROTO_CLIENT_REG","Proto Client registration for [chars] has failed","Protocol client has failed to register with ISSU.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","REF_TREE","%s reference tree %s failed","The AVL-based ISSU reference tree operation failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","SESSION_ID_ERROR","Failed to %s session id %d for %s","A session ID related operation failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","SESSION_RENEGOTIATE","Client Attemptiong to renegotiate on session [dec]","A client is attempting to renegotiate a session without unregistering it and doing the negotiation over again. This is not allowed.","Unregister the message session first, and then reregister and attempt the negotiation."
"ISSU","3","SET_UNKNOWN_UID","Unknown unique_id is set.","Platform team should provide distinctive identifier for the endpoint.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","TRANSPORT_ERP_UID_CB_IS_NULL","Transport ERP uid control block is NULL","The peer client is incompatible.","Synchronize the configurations and reload the standby supervisor."
"ISSU","3","UNKNOWN_ENTITY_ID","Unknown entity id under client([dec])","There is an unknown entity ID under the specified client.","Enter the show issu client | grep client id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","UNKNOWN_ID_UNDER_ENDPOINT","Can not use unknown [chars].","Cannot use the specified unknown ID.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","UNKNOWN_ID_UNDER_ENTITY","Unknown [chars] under client([dec]) and entity([dec])","Unknown ID under the specified client and entity.","Enter the show issu client | grep client id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","VERSION_LOWHIGH_NOT_MATCH_TABLE_SIZE","Version low([dec]) and high([dec]) value for msg([dec]) does not match table size([dec]) under client([dec]) and entity([dec]).","Version low and high values for the specified message do not match the specified table size.","Enter the show issu client | grep client id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","VERSION_OUT_OF_ORDER","Msg version([dec],[dec]) is out of order for msg([dec]) under client([dec]) and entity([dec]).","The specified message version is out of order for the specified group registration.","Enter the show issu client | grep client id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","3","VERSION_OUT_OF_RANGE","Msg version([dec],[dec]) is out of range for msg([dec]) under client([dec]) and entity([dec]).","The specified message version is out of range for the specified group registration.","Enter the show issu client | grep client id command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","4","FSM_INCOMP","Version of local ISSU client [dec] in session [dec] is incompatible with remote side.","The protocol versions of the local and remote clients are incompatible. These clients cannot communicate with each other.","Use the show version and show issu clients commands to help verify that the software images are incompatible. Upgrade the software images on each unit to versions that are compatible. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","4","MSG_INCOMP","Message([dec]) is incompatible under msg session([dec]).","The specified message is incompatible under the specified message session.","Enter the show issu session | grep session id and show issu fsm | grep session id commands. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU","4","NEGO_NOT_FINISHED","Negotiation is not finished for client [dec], msg session([dec]).","Negotiation is not finished for the specified client and message session.","Enter the show issu session | grep session id and show issu fsm | grep session id commands. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_CS","3","BULK_CONFIG_TR","[chars] [chars]","ISSU bulk configuration synchronization transformation failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_CS","3","DL","[chars] [chars]","The ISSU configuration synchronization difference list is displayed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_CS","3","DL_STATS","[chars][dec][chars]","ISSU configuration synchronization difference list statistics are displayed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_CS","3","LBL_CONFIG_TR","[chars] [chars]","ISSU line-by-line configuration synchronization transformation failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_CS","3","SKL","[chars] [chars]","An ISSU configuration synchronization SKL operation failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_CS_DL_MESSAGES","3","DL_CLI_DUMP","[chars][dec][chars][dec][chars]","ISSU configuration synchronization difference list CLI generation statistics are displayed.","No action is required."
"ISSU_ERROR","2","CLIENT_INCOMPATIBLE","%s(%d): ISSU Client not compatible","The ISSU client is incompatible with the current version.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_ERROR","2","NEGO_NOT_DONE","%s(%d): ISSU Negotiation not complete","The ISSU client was unable to complete ISSU negotiation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_ERROR","2","NTI_EP_TYPE_REG","%s(%d): Failed to register EP type (%d) with NTI: %s (%d)","The ISSU client could not register the endpoint (EP) type with the Negotiation Trigger Infrastructure (NTI).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_ERROR","2","NTI_EP_TYPE_UNREG","%s(%d): Failed to unregister EP type (%d) with NTI: %s (%d)","The ISSU client could not unregister the endpoint type with NTI.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_ERROR","2","NTI_REG","%s(%d): Failed to register with NTI: %s (%d)","The ISSU client could not register with NTI.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_ERROR","2","NTI_UNREG","%s(%d): Failed to unregister with NTI: %s (%d)","The ISSU client could not be unregistered with NTI.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_ERROR","3","CAPENTRY_REG","%s(%d): failed to register a capability entry (%s)","The ISSU client failed to register a capability entry.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_ERROR","3","CAPGROUP_REG","%s(%d): failed to register a capability group (%s)","The ISSU client failed to register a capability group.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_ERROR","3","CAPTYPE_REG","%s(%d): failed to register capability type (%s)","The ISSU client failed to register a capability type.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_ERROR","3","CAP_EXCHANGE","%s(%d): Capability exchange failed with error (%s)","The capability exchange failed and the ISSU client is unable to process the received capability.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_ERROR","3","CAP_REG","%s(%d): failed to register its capabilities (%s)","The capabilities of the ISSU client could not be registered.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_ERROR","3","CF_SEND","%s(%d): Client failed to send message (%d)","The ISSU client cannot send a negotiation message to a peer.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_ERROR","3","CLIENT_REG","%s(%d): Client failed to register (%s)","The ISSU client could not be registered.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_ERROR","3","CLIENT_REG_FAILED","%s(%d): Client is not initialized","The ISSU client is not initialized. The negotiation for this client is not yet done.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_ERROR","3","ENTITY_REG","%s(%d): failed to register the entity (%s)","The ISSU entity could not be registered.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_ERROR","3","ENTITY_UNREG","%s(%d): failed to unregister the entity (%s)","The ISSU entity could not be unregistered.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_ERROR","3","ICC_SEND","%s(%d): Client failed to send message","The ISSU client cannot send a negotiation message to a peer.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_ERROR","3","MSGGROUP_REG","%s(%d): failed to register a message group (%s)","The ISSU client cannot register a message group.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_ERROR","3","MSGTYPE_REG","%s(%d): failed to register a message type (%s)","The ISSU client cannot register a message type.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_ERROR","3","MSG_MTU","%s(%d): Client failed to get mtu for message %d (%s)","The ISSU client cannot get the MTU for the message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_ERROR","3","MSG_NOT_OK","%s(%d): ISSU message type (%d) is not compatible","The ISSU process received a message not compatible with the running version.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show message type commands and your pertinent troubleshooting logs."
"ISSU_ERROR","3","MSG_POLICY","%s(%d): Client failed to negotiate version for message type (%d), error (%s)","The ISSU client cannot negotiate the message type with a peer.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_ERROR","3","MSG_REG","%s(%d): failed to register its messages (%s)","Messages for the ISSU client could not be registered.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_ERROR","3","MTU_NOT_ENOUGH","%s(%d): Requested buffer size (%d) is greater than the max MTU size (%d)","The checkpoint buffer size requested is greater than the maximum MTU size supported by the checkpoint feature.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_ERROR","3","NEGO_PROCESS","%s(%d): Cannot create process: %s","The process to negotiate the session for the specified ISSU client cannot be created.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_ERROR","3","REG_ARBITRATE_CALLBACK","%s(%d): Failed to register first speaker arbitration callback - %s)","The ISSU client could not register the first speaker arbitration callback.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_ERROR","3","SESSION_REG","%s(%d): session failed to register (%s)","The client's ISSU session could not be registered.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_ERROR","3","SESSION_UNREG","%s(%d): session (%d) failed to unregister (%s)","The client's ISSU session could not be unregistered.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_ERROR","3","START_NEGO_FAILED","%s(%d): failed to start negotiation (%s)","The ISSU client cannot start its negotiation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_ERROR","3","TRANSFORM_FAILED","%s(%d): %s transformation failed (%s)","The transformation operation for the ISSU message has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_ERROR","3","TRANSFORM_FAILED_DETAILED","%s(%d): %s transformation failed for message %d, endpoint %d (%s)","The transformation operation for the ISSU message has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_PROCESS","3","UNAVAILABLE","%s (%s)","Return code failure from calling UAM API.","Got unexpected rc from calling UAM API."
"ISSU_PROCESS","3","UNAVAILABLE","%s (%s) parameters are wrong","The system could not be configured for ISSU","Fix the error and try the command again"
"ISSU_PROCESS","3","UNAVAILABLE","%s","NVRAM variables are not set properly.","The issu commands or the hw-module command did not set the variables properly."
"ISSU_PROCESS","3","UNAVAILABLE","%s","Persistent variables are not set properly.","The issu commands or the hw-module command did not set the variables properly."
"ISSU_PROCESS","3","UNAVAILABLE","%s","The ISSU configuration failed due to an IPC problem, a platform problem, or a rommon problem.","Copy the error and send it to TAC."
"ISSU_PROCESS","3","UNAVAILABLE","%s","The ISSU loadversion command did not fulfill the necessary criteria. This can happen due to the following conditions not being met. 1. Standby is not HOT yet. 2. Active and/or Standby unit ID are wrong. 3. ISSU process is not in the INIT state. 4. Active and/or Standby image doesnt exist in flash. 5. Image names are not the same. 6. The configuration register value is not 0x2102","Fix the error and try the command again"
"ISSU_PROCESS","3","UNAVAILABLE","%s","The ISSU process IPC MSG Queue Setup encountered an error.","Copy the error and send it to TAC."
"ISSU_PROCESS","3","UNAVAILABLE","%s","The ISSU process cannot continue with negotiation as it can't verify the peer's state.","Make sure the peer is present and try again. If the problem persists, send the output of 'show issu state' and 'show version' to TAC."
"ISSU_PROCESS","3","UNAVAILABLE","%s","The rollback timer could not be configured","Fix the error and try the command again"
"ISSU_PROCESS","3","UNAVAILABLE","%s [ %s ]","The ISSU process IPC agent had an error.","Copy the error and send it to TAC."
"ISSU_PROCESS","3","UNAVAILABLE","%s [ %s ]","The ISSU process RF client had an error.","Copy the error and send it to TAC."
"ISSU_PROCESS","3","UNAVAILABLE","%s [ %s ]","The ISSU process transform utility had an error.","Send the output of 'show version' from the Active and the Standby and send it to TAC."
"ISSU_PROCESS","3","UNAVAILABLE","%s is loading the wrong image [ %s ], expected image [ %s ]","Wrong image is being loaded during ISSU process.Check the detail state of ISSU process, make sure the right images are loaded on Active and on Standby.Error Message    %ISSU_PROCESS-3-UNAVAILABLE: '%s' filesystem does not exist Explanation    Verification of the filesystem failed","The file needs to be downloaded to the flash disk"
"ISSU_PROCESS","3","UNAVAILABLE","ISSU process is in progress; Changing configuration register might disrupt the upgrade process","The configuration register value should not be changed while the ISSU process is in progress","The low order byte of the configuration register should be 0x02 during the upgrade process"
"ISSU_PROCESS","3","UNAVAILABLE","issu acceptversion; %s","The ISSU acceptversion command did not fulfill the necessary criteria. This can happen due to the following conditions not being met. 1. ISSU state in Active is not RunVersion. 2. Current Version doesn't exist in Active's rommon. 3. Primary Version doesn't exist in Active's rommon. 4. Primary Version and Current Version are not the same due to some error 5. Current Version doesn't exist on Standby 6. The image names on Standby's Primary Version and Current Version are different 7. Secondary Version doesn't exist on Active 7. Active Secondary Version and Standby Current Version are different","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_PROCESS","3","UNAVAILABLE","issu commitversion; %s","The ISSU commitversion command did not fulfill the necessary criteria. This can happen due to the following conditions not being met. 1. Current ISSU state is not RunVersion 2. Secondary Version doesn't exist on Standby 3. Standby BOOT variable doesn't exist 4. The new image is not the first in BOOT on Standby 5. Active BOOT variable is not set 6. Primary Version on Active doesn't exist 7. New image is not the first in Active BOOT 8. Configuration register is not 0x2102","Fix the error and try the command again"
"ISSU_PROCESS","3","UNAVAILABLE","issu loadversion; %s","The ISSU abortversion command can be run only from the LoadVersion or RunVersion state","Please proceed to reinitializing the ISSU process"
"ISSU_PROCESS","3","UNAVAILABLE","issu runversion; %s","The ISSU runversion command did not fulfill the necessary criteria. This can happen due to the following conditions not being met. 1. Standby is not in RF STANDBY HOT state. 2. The ISSU system state is not LoadVersion. 3. Primary Version doesn't exist in Active's rommon. 4. Configuration register value is not 0x2102. 5. The ISSU state could not be set to RunVersion","Fix the error and try the command again"
"ISSU_PROCESS","4","UNAVAILABLE","%s","The peer has been determined to be incompatible and hence is being reloaded.","Send the output of 'show redundancy history' from the Active to TAC."
"ISSU_PROCESS","7","UNAVAILABLE","%s","Debug commands for the ISSU process. The system is attempting to recover from an unknown error.","Send the output of 'show logging' to TAC for debugging purposes."
"ISSU_PROCESS","3","ABORTVERSION","issu loadversion; %s","The ISSU abortversion command can be run only from the LoadVersion or RunVersion ISSU state.","Reinitialize the ISSU process."
"ISSU_PROCESS","3","ACCEPTVERSION","issu acceptversion; %s","The ISSU acceptversion command did not execute because one of the following conditions was not met:- The active supervisor was not in the RunVersion ISSU state. - The active supervisor's ROMMON does not contain the current version.- The active supervisor's ROMMON does not contain the primary version.- The primary and current versions are not the same.- The standby supervisor's ROMMON does not contain the current version.- The standby supervisor's current and primary image names are different.- The active supervisor does not have the secondary version.- The active's secondary version and the standby's current version are different.","Correct the condition and retry the command."
"ISSU_PROCESS","3","COMMITVERSION","issu commitversion; %s","The ISSU commitversion command did not execute because one of the following conditions was not met:- The current ISSU state is not RunVersion. - The secondary version does not exist on the standby supervisor. - The standby BOOT variable does not exist. - The new image is not the first in BOOT on the standby supervisor. - The active BOOT variable is not set. - The primary version does not exist on the active supervisor. - The new image is not the first in the active BOOT. - The configuration register is not 0x2102.","Correct the error condition and retry the command."
"ISSU_PROCESS","3","CONFIGREG","ISSU process is in progress; Changing configuration register might disrupt the upgrade process","The configuration register value should not be changed while the ISSU process is in progress.","The low-order byte of the configuration register should be 0x02 during the upgrade process."
"ISSU_PROCESS","3","FILESYS","'[chars]' filesystem does not exist","Verification of the file system failed.","Download the file to the flash disk."
"ISSU_PROCESS","3","IMAGE","%s is loading the wrong image [ %s ], expected image [ %s ]","The wrong image is being loaded during the ISSU process.","Check the detail state of the ISSU process and make sure that the correct images are loaded on the active and standby supervisors."
"ISSU_PROCESS","3","IPC_AGENT","[chars] [ [chars] ]","The ISSU process IPC agent had an error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_PROCESS","3","IPC_MSG","%s","An error occurred in the setup of the interprocess communication (IPC) message queue.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_PROCESS","3","LOADVERSION","%s","The ISSU loadversion command did not execute because one of the following conditions was not met: - The standby device is not yet in the HOT state. - The active or standby device's unit ID is wrong. - The ISSU process is not in the INIT state. - The active or standby image does not exist in flash memory. - The active and standby image names are not the same. - The configuration register value is not 0x2102.","Correct the error condition and retry the command."
"ISSU_PROCESS","3","NVRAM","[chars]","NVRAM variables are not set properly.","The ISSU commands or the hardware module command did not set the variables properly. Fix the error and retry the command."
"ISSU_PROCESS","3","PARAMETERS","[chars] ([chars]) parameters are wrong","The system could not be configured for ISSU.","Fix the error and retry the command."
"ISSU_PROCESS","3","PEER","%s","The ISSU process cannot continue with negotiation because it cannot verify the peer's state.","Make sure the peer is present and try again. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show version, and show issu state commands and your pertinent troubleshooting logs."
"ISSU_PROCESS","3","PRST","%s","The specified persistent variables are not set properly.","Check the ISSU commands and the hw-module command to determine whether the specified variables are set properly."
"ISSU_PROCESS","3","RF","[chars] [ [chars] ]","The ISSU process RF client had an error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_PROCESS","3","ROLLBACK_TIMER","[chars]","The rollback timer could not be configured.","Fix the error and retry the command."
"ISSU_PROCESS","3","RUNVERSION","issu runversion; %s","The ISSU runversion command did not execute because one of the following conditions was not met: - The standby device is not in the RF STANDBY HOT state. - The current ISSU state is not LoadVersion. - The primary version image does not exist in the active supervisor's ROMMON. - The configuration register value is not 0x2102. - The ISSU state could not be set to RunVersion.","Correct the error condition and retry the command."
"ISSU_PROCESS","3","SYSTEM","[chars]","The system could not be configured for ISSU.","Correct the error condition and retry the command."
"ISSU_PROCESS","3","TRANSFORM","[chars] [ [chars] ]","The ISSU process transform utility had an error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_PROCESS","3","UAM","%s","An unexpected return code failure was received from the Upgrade Analysis Module (UAM).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ISSU_PROCESS","7","DEBUG","%s","This message displays debug commands for the ISSU process. The system is attempting to recover from an unknown error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show logging commands and your pertinent troubleshooting logs."
"ISSU_PROXY","3","ISSU_PROXY_TIMEOUT","ICC Timed Out after waiting for %dsecs.","The ISSU proxy on the route processor initiated an asynchronous intercard communication (ICC) call to the switch processor to perform an ISSU command. This call did not return within the wait period.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IVR","3","UNAVAILABLE","%s: Failed to create pool_group %x buffer_pool %x platform_mc_buf_pool_count %d","No IO memory to create IVR private pak pool","Check to see if there is enough IO memory."
"IVR","3","UNAVAILABLE","%s: This version of IOS does not support prompt playout for IVR applications.","This error will be displayed if an IVR application is used on a gateway that does ot support IVR prompt playout.","Ensure that this platform and IOS version support the IVR feature set."
"IVR","3","UNAVAILABLE","Could not create IVR prompt %s errno=%d=%s","Could not read in the IVR prompt","Check that prompt exists on the server, and is readable."
"IVR","3","UNAVAILABLE","Could not load IVR script %s errno=%d=%s","Could not read in the IVR script","Check that script exists on the server, and is readable."
"IVR","3","UNAVAILABLE","IVR: Sytem running on low memory. Free memory: %l bytes. Call is rejected.","System does not have enough memory to accept calls","Check to see what is causing low system memory."
"IVR","3","UNAVAILABLE","Script requires version %d.%d, image supports %d.%d","IVR Script requires a higher IVR infrastructure version","Upgrade IOS, or use a different script"
"IVR","3","UNAVAILABLE","TCL IVR Process PANIC: %s, CallID %d, Event %s","TCL IVR Call process panic and exited abnormally","Contact your technical support representative, include the full text of the error message."
"IVR","3","UNAVAILABLE","Unable to create internal interface descriptor","There are insufficient resources to create a necessary data structure.","Verify that there is sufficient main memory."
"IXP_MAP","3","ATOM","[chars] error detected: [chars] [chars] [hex] [hex]","A software programming error for the ATOM ESF network processor client mapper was detected.","This software programming error is not considered fatal to the operation of the ESF network processors. The software is designed to detect and report the error condition. If the error persists, reset the affected device. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IXP_MAP","3","DROP_BLOCK","[chars] error detected - [hex] [hex] [dec] [dec]","An error was detected during the processing of ESF network processor drop block allocations.","This is a software programming error. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IXP_MAP","3","EXMEM","[chars] [chars] error detected - [chars] ([dec])","An error was detected managing the external memory of a network processor.","This is a software programming error. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IXP_MAP","3","HQF","[chars] error detected: [chars] [chars] [hex] [hex]","A software programming error for the HQF ESF network processor client mapper was detected.","This software programming error is not considered fatal to the operation of the ESF network processors. The software is designed to detect and report the error condition. If the error persists, reset the affected device. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IXP_MAP","3","INITFAIL","Initialization Failed - [chars]: [chars] [chars]","Memory needed to service one or more network processors could not be initialized.","Try to reload the Cisco IOS image on the affected card or platform. If the error persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IXP_MAP","3","INTF","[chars] error detected: [chars] [chars] [hex] [hex]","A software programming error for the interface ESF network processor client mapper was detected.","This software programming error is not considered fatal to the operation of the ESF network processors. The software is designed to detect and report the error condition. If the error persists, reset the affected device. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IXP_MAP","3","LOCK_BLOCK","[chars] error detected - [hex] [dec] [dec] [dec]","An error was detected during the processing of ESF network processor lock bit allocations.","This is a software programming error. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IXP_MAP","3","LOCK_LIST","[chars] error detected - [hex] [dec] [dec] [dec]","An error was detected during the processing of ESF network processor lock bit allocations.","This is a software programming error. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IXP_MAP","3","MAXEXCEED","ESF NP Mapper Max Services Exceeded - [chars]: [chars] [dec] Recommended Action    Change the configuration to reduce the number of services configured. If the error persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message    %IXP_MAP-3-MPLSOGRE: [chars] error detected: [chars] [chars] [hex] [hex]","A software programming error for the MPLSOGRE ESF network processor client mapper was detected.","This software programming error is not considered fatal to the operation of the ESF network processors. The software is designed to detect and report the error condition. If the error persists, reset the affected device. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IXP_MAP","3","NOMEM","Memory Allocation Failure - [chars] : [chars]([hex])","Memory required to service one or more network processors could not be allocated.","This error may indicate that more memory must be installed on the affected card or platform to service all the features and related entities enabled by the configuration. Attempt to reload the Cisco IOS image on the affected card or platform. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IXP_MAP","3","NOMEM_S","Memory Allocation Failure - [chars]: [chars] [chars]","Memory required to service one or more network processors could not be allocated.","This error may indicate that more memory must be installed on the affected card or platform to service all the features and related entities enabled by the configuration. Attempt to reload the Cisco IOS image on the affected card or platform. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IXP_MAP","3","NOTFOUND","ESF NP Client Mapper - [chars]: [chars] [hex]","The ESF network processor client mapper could not locate a required software element.","Try to reload the Cisco IOS image on the affected card or platform. If the error persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IXP_MAP","3","NPUNKNOWN","Unsupported NP - [chars]: [chars] [chars]","An unsupported network processor has been detected.","Verify that the correct Cisco IOS image is loaded on the affected card or platform for the configured features. If the error persists,"
"IXP_MAP","3","QOS","[chars] error detected: [chars] [chars] [hex] [hex]","A software programming error for the QOS ESF network processor client mapper was detected.","This software programming error is not considered fatal to the operation of the ESF network processors. The software is designed to detect and report the error condition. If the error persists, reset the affected device. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IXP_MAP","3","QOS_CONFIG","[chars] error detected: [chars] [chars] [hex] [hex]","A configuration error for the QoS ESF network processor client mapper was detected. This configuration error is not considered fatal to the operation of the ESF network processors. The software is designed to detect and report the error condition.","Change the configuration to correct the QoS ACL configuration problem. If the condition persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IXP_MAP","3","STATS_BLOCK","[chars] error detected - [hex] [hex] [dec] [dec] [dec]","An error was detected during the processing of ESF network processor statistics block allocations.","This is a software programming error. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IXP_MAP","4","STUCK","Client ID([hex], [hex]) not ready on [chars]","During reset of the ESF network processor, one or more network processor clients had not completed stop processing.","The system should still operate normally, however, statistics or state collected before the ESF network processor was reset may have been lost. If the error persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IXP_MAP","3","TTFIB","[chars] error detected: [chars] [chars] [hex] [hex]","A software programming error for the VPLS ESF network processor client mapper was detected.","This software programming error is not considered fatal to the operation of the ESF network processors. The software is designed to detect and report the error condition. If the error persists, reset the affected device. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IXP_MAP","3","VPLS","[chars] error detected: [chars] [chars] [hex] [hex]","A software programming error for the VPLS ESF network processor client mapper was detected.","This software programming error is not considered fatal to the operation of the ESF network processors. The software is designed to detect and report the error condition. If the error persists, reset the affected device. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IXP_MAP","3","WRED","[chars] error detected: [chars] [chars] [hex] [hex]","A software programming error for the WRED ESF network processor client mapper was detected.","This software programming error is not considered fatal to the operation of the ESF network processors. The software is designed to detect and report the error condition. If the error persists, reset the affected device. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IXP_MAP","4","IPC_FAIL","ESF IPC Command failed - [chars] NP=[chars] (cmd=[dec] me=[dec] rc=[dec])","An IPC command sent to the ESF network processor has failed.","This error indicates a possible problem with the network processor hardware or microcode. Reload the affected hardware to clear the condition. If the error persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IXP_MAP","4","QUEUE_LIMIT_EXCEED","Warning: Line card default queue-limit exceeds the maximum transmit packet buffers ([dec]). To ensure high priority traffic is not dropped, apply a QOS policy on each interface and adjust the queue-limit so that the total of the queue-limits on this line card is less than the maximum transmit packet buffers.","An error for the HQF ESF network processor client mapper was detected. The total of the default queue imits exceeds the maximum transmit packet buffers for this line card. Under high-traffic conditions, the line card may run out of packet buffers and drop high-priority traffic.","This configuration error is not considered fatal to the operation of the ESF network processors. The software is designed to detect and report the error condition. Apply the QoS policy configuration in the output direction of each interface. Adjust the queue limit so that the total of the queue limits on this line card is less than the maximum transmit packet buffers. (policy-map qlimit; class class-default; queue-limit 100000; interface Gig1/0/0; service policy output qlimit). If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show policy-map interface command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"IXP_MAP","4","STUCK","Client ID(0x%x, 0x%08X) not ready on %s","During reset of the ESF Network Processor, one or more Network Processor Clients had not completed stop processing.","The system should still operate normally, however, statistics or state collected before the ESF Network Processor was reset may have been lost. If the error persists, record the output from the show log and show tech commands. Provide this information to your technical support representative."
"KERBEROS","3","UNAVAILABLE","Failed to fork process for %s.","Quite likely, we ran out of memory. Other explanations are possible.","If this message recurs, call your technical support representative for assistance."
"KEYMAN","4","KEYSTR_BAD_CRYPTO","Bad encrypted keystring for key id [dec].","The system could not successfully decrypt an encrypted key string. The key string may have been corrupted during system configuration.","Reenter the key string command, and reconfigure the key string."
"KEYMAN","4","KEYSTR_CRYPTO_TYPE","Type [dec] encryption unknown. Interpreting keystring as literal","The system does not recognize the format type. A key string format type value of 0 (unencrypted key string) or 7 (hidden key string), followed by a space, can precede the actual key string to indicate its format. An unknown type value will be accepted, but the system will consider the key string as being unencrypted.","Use the correct format for the value type or remove the space following the value type."
"KINEPAK","3","UNAVAILABLE","Cannot create message buffer","A software error occurred resulting in failure to create a message buffer to send messages among processes.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"KINEPAK","3","UNAVAILABLE","Cannot create particle pool","A software error occurred resulting in failure to create a particle pool to receive packets from DSP.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"KINEPAK","3","UNAVAILABLE","Cannot find dspware %s component","A software error occurred resulting in failure to download a dspware component.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"KINEPAK","3","UNAVAILABLE","Contiguous packet sent for transmit","A software error occurred resulting in an unexpected packet being set up for transmission and the packet was dropped.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"KINEPAK","3","UNAVAILABLE","No dsp entry in dsp list","The software structure that is used to maintain the DSP instance is missing.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"KINEPAK","3","UNAVAILABLE","No particle available for ingress packet","A software error occurred resulting in failure to obtain a particle to hold an ingress packet from DSP.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"KINEPAK","3","UNAVAILABLE","Static receive paktype unavailable","A software structure was found in an unexpected state during run-time for the indicated DSP.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"KINEPAK","3","UNAVAILABLE","dsp%d cannot download dspware %s","A software error occurred resulting in failure to download a dspware component.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"KEYSTORE_SP","3","HW_BAD_EEPROM_ERR","Bad EEPROM cell reported in hardware keystore.","A cell in the keystore EEPROM has failed. Write operations are not producing correct results.","Report this error to your Cisco technical support representative and arrange to have the hardware keystore on the supervisor card replaced."
"LANMGR","4","BADRNGNUM","Ring number mismatch on [chars], shutting down the interface","The router detected a conflict in assigned ring numbers for the specified Token Ring. The Ring Parameter Server (RPS) function was shut down to prevent potentially incorrect information from being sourced onto the ring.","Check all bridges connected to this Token Ring and ensure that they are using the same assigned ring number."
"L2_AGING","2","DEC_EN_FAIL","Failed to initialize Distributed EtherChannel","One or more resources that are required for the distributed EtherChannel operation are in use.","Remove the monitor session reserved for service modules by entering the no monitor session service module command, and then try to reinitialize the operation."
"L2_AGING","2","MALLOC_FAIL","[chars]: Failed to allocate memory for bitlist","There was no memory available to create the bit list.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L2_AGING","2","SIG_INST_FAIL","[chars]: Failed to install signal handler","A signal handler could not be installed for a process that involves Layer 2 aging.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L2_APPL","0","TASK_SPAWN_FAIL","Failed to spawn task '[chars]'","The specified initializing task failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L2_APPL","4","MAC_MOVE","Host [enet] is flapping between port [chars] and port [chars]","A host is going up and down between ports.","Examine the network for possible loops."
"L2_APPL","4","MAC_USAGE","MAC usage is currently [dec]%","MAC usage is exceeded for the Layer 2 monitoring feature.","No action is required."
"L2_APPL","4","UNKMESG","Unknown received message [dec]","An internal error occurred. There might be a mismatch between image versions.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L2_ASIC","0","FATAL_INTR","L2 Forwarding Engine: fatal interrupt: int status [hex],  int mask [hex]","Critical interrupts indicate that EARL may no longer be functioning.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L2_ASIC","1","SCP_Q_CREATE_FAIL","Failed to create L2 Forwarding Engine SCP queue","SCP queue creation has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L2_ASIC","1","TASK_CREATE_FAIL","Failed to create L2 Forwarding Engine fatal interrupt patch task","A task creation failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L2_ASIC","1","THRO_RES_ALLOC_FAIL","Failed to allocate throttle resource","Throttle resource allocation has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L2_ASIC","2","L2L3_SEQ_ERR","L2 Seq #[hex], L3 Seq #[hex], L2L3 Mismatch seq #[hex]","A Layer 2 forwarding engine Layer 2-to-Layer 3 sequence error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L2_ASIC","2","PARITY_ERR","L2 Forwarding Engine: parity intr #[dec]: address [hex], Data: [hex], [hex], [hex], [hex]","A parity error was detected while accessing the forwarding table.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L2_ASIC","2","RESET_LC","Resetting the linecard [dec]. Error code [dec]","Failed to receive an SCP response or received a response with a status of not-ok.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L2_ASIC","2","SEQ_ERR","[chars] seq. error: Seq #[hex], Intr. status #[hex], Cntrl1 #[hex], Cntrl2 #[hex]","A Layer 2 forwarding engine sequence error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L2_ASIC","4","INV_MSG","Received [chars] message from slot [dec]","A message was received from an invalid line card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L2_ASIC","4","INV_REG","L2 Forwarding Engine: Attempt to [chars] invalid register","An internal error has occurred. An attempt was made to read or write to an invalid Layer 2 forwarding engine register.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L2TP","3","CRITICAL","%s","An critical event was processed by the Layer 2 Tunneling Protocol (L2TP) subsystem.","No action is required."
"L2TP","3","ILLEGAL","%s: %s","An illegal event was processed by the Layer 2 Tunneling Protocol (L2TP) subsystem.","No action is required."
"L2TP","5","IGNOREICMPMTU","Ignoring received ICMP Type 3 Code 4, due to pmtu min or max setting","An ICMP Type 3 Code 4 packet has been received, indicating that fragmentation is needed, but the 'don't fragment' (DF) bit is set. This packet has specified a next-hop MTU that is smaller or greater than the current minimum or maximum path MTU discovery MTU value. The ICMP packet was ignored and the MTU has not been changed.","To allow the ICMP packet to be accepted and used to decrease or increase the MTU, enter the vpdn pmtu min command to decrease the minimum MTU allowed and enter the vpdn pmtu max command to increase the maximum MTU that is allowed. The minimum value specified is the minimum MTU that is allowed, and the maximum value specified is the maximum MTU that is allowed."
"L2TUN","3","ILLEGAL","%s","An illegal event was processed by the Layer 2 Tunneling (L2TUN) subsystem.","No action is required."
"L2_MMC","3","TASK_SPAWN_FAIL","L2 MMC process cannot be created","The Layer 2 MAC move counters (MMC) process cannot be created.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L2_MMC","4","MMC_FIRST","MAC Move(s) are detected","The feature is enabled and the first MAC move(s) have been detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L2_MMC","4","MMC_MAX","Maximum limit for MAC move counters exceeded for vlan %d","The maximum limit has been exceeded for MAC move counters (MMC) on the specified VLAN.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L3_ASIC","1","ERR_NF_PARITY","Netflow table parity error can't be fixed by software.","NetFlow table parity errors are too many to be fixed by software.","Reload the system. If the messages continue for the same module after a reload, contact your Cisco technical support representative and provide the output of the show module command to obtain a replacement for that module."
"L3_ASIC","4","ERR_INTRPT","Interrupt [chars] occurring in L3 CEF Engine.","An error interrupt is occurring for the Layer 3 CEF engine.","Copy the message exactly as it appears on the console or in the system log. Enter the show earl status command on the consoles of the switch supervisor and any DFC-enabled line cards to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L3_COMMON","3","ERROR","%s","An error has occurred in the Layer 3 in-service software upgrade (ISSU) process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L2CTRL","3","UNAVAILABLE","Subsystem %s fails to add callback function %s","Other subsystem must have mistakenly add its own callback functions. This syslog is for debugging purpose.","LOG_STD_NO_ACTION"
"L2MCAST_SNOOP","4","FORCE_MAC_FORWARDING","Force to do MAC-based forwarding becuase an IP multicast DMAC is configured while IP-based forwarding is enabled on this VLAN %d. Suggest to configure static multicast group instead.","Configuring multicast group address can avoid ddress aliasing problem","Either change to MAC-based forwarding using command 'multicast snooping lookup mac' or configure group ip address using command 'ip/ipv6 igmp/mld snooping static interface '"
"L2MCAST_SNOOP","4","UNAVAILABLE","Failed creation of GIP/SIP entry, exceeded VLAN (%d) limit (%d) of IPv%d state entries.","Maximum state entry limit is exceeded and thus no new (*,G)/(S,G) state entries can be created by L2 multicast snooping. Receivers for these GIP/SIP entries may not be able to receive traffic","Reduce the number of (*,G)/(S,G) entries in this VLAN or increase the state limit. Another alternative is to configure static entries for those groups that should not be subjected to the state limit"
"L2MCAST_SNOOP","4","UNAVAILABLE","Force to do MAC-based forwarding becuase an IP multicast DMAC is configured while IP-based forwarding is enabled on this VLAN %d. Suggest to configure static multicast group instead.","Configuring multicast group address can avoid ddress aliasing problem","Either change to MAC-based forwarding using command 'multicast snooping lookup mac' or configure group ip address using command 'ip/ipv6 igmp/mld snooping static interface '"
"L2MCAST_SNOOP","4","UNAVAILABLE","VLAN (%d) limit is already exceeded after decreasing the limit.L2 multicast snooping must be disabled and enabled for lowerlimit to take effect.","After the maximum state entry limit is decreased, the number of L2 multicast snooping states is now greater than the limit.In order to make the smaller limit take effect, snooping must be disabled on the VLAN and then re-enabled.","Disable and re-enable L2 multicast snooping on the VLAN."
"L2MCAST_SNOOP","6","ETRACK_LIMIT_EXCEEDED","%s snooping on VLAN %d was trying to allocate more explicit-tracking entries than what allowed global limit (%d) or the limit on the VLAN (%d). Potential multicast traffic disruption may occur. Increase limit if not intended so.","The allocation of explicit-tracking entries is bounded to avoid the IGMP/MLD snooping hogs the system resources","Reduce the number of (s,g) channelds or number of receivers. When explicit- tracking database is overflow, new membership for any channel will not be tracked and it may cause high leave latency when those members leave a channel. Another alternative is to increase the limit from the config mode through the CLI 'ip/ipv6 igmp/mld snooping explicit-tracking-limit ' globally and on the VLAN. But note increasing the value of max-entries could create crash due to high use of system resources"
"L2MCAST_SNOOP","6","UNAVAILABLE","%s snooping on VLAN %d was trying to allocate more explicit-tracking entries than what allowed global limit (%d) or the limit on the VLAN (%d). Potential multicast traffic disruption may occur. Increase limit if not intended so.","The allocation of explicit-tracking entries is bounded to avoid the IGMP/MLD snooping hogs the system resources","Reduce the number of (s,g) channelds or number of receivers. When explicit- tracking database is overflow, new membership for any channel will not be tracked and it may cause high leave latency when those members leave a channel. Another alternative is to increase the limit from the config mode through the CLI 'ip/ipv6 igmp/mld snooping explicit-tracking-limit ' globally and on the VLAN. But note increasing the value of max-entries could create crash due to high use of system resources"
"L2MCAST_SNOOP","6","UNAVAILABLE","IP-based forwarding is restored on VLAN %d","The static multicast MAC are all removed. Restore IP-based forwarding","The message is for information only"
"L2MC_QUERIER","4","UNAVAILABLE","The %s querier cannot send out General Query messages in VLAN %d because there is no IP address configured on the system.","An IP address should be specified for the IGMP/MLD querier either at the global or per VLAN level.","Configure a source IP address for the IGMP/MLD querier."
"L2MC_QUERIER","4","UNAVAILABLE","The %s querier is operationally disabled in VLAN %d because %s snooping has been disabled in this VLAN.","IGMP/MLD snooping has been detected as being disabled on this VLAN. The IGMP/MLD querier function should not be operationally enabled when IGMP/MLD snooping is disabled.","Ensure that IGMP/MLD snooping is enabled globally and on the VLAN reported."
"L2MC_QUERIER","4","UNAVAILABLE","The %s querier is operationally disabled in VLAN %d because PIM has been enabled on the SVI.","PIM has been detected on the SVI. The IGMP/MLD querier function should not be operationally enabled when PIM is enabled on the SVI.","Ensure that PIM is disabled on the SVI."
"L2MC_QUERIER","6","UNAVAILABLE","The %s querier is now operationally enabled in VLAN %d because %s snooping is no longer disabled.","IGMP/MLD snooping has now been enabled and, as a result, the IGMP/MLD querier function has now been enabled.","LOG_STD_NO_ACTION"
"L2MC_QUERIER","6","UNAVAILABLE","The %s querier is now operationally enabled in VLAN %d because PIM is no longer enabled on the SVI.","PIM has been disabled on the SVI and, as a result, the IGMP/MLD querier function has now been enabled.","LOG_STD_NO_ACTION"
"L2_MMC","4","MMC_FIRST","MAC Move(s) are detected","After the feature is enabled, the first Mac Move(s) are happening","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L2R","4","UNAVAILABLE","Invalid L2R message (msg_type %x) received from UID %d at line %d","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L2R","4","UNAVAILABLE","fragmentation error (s_uid = %x) received","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L2R","4","UNAVAILABLE","l2r uid %d drop packet (type %x) from/to uid %d when %s","drop packet.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L2TM","3","UNAVAILABLE","Tcam access failed while %s","Failed to read/write from/to tcam.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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.L2TM-7Error Message    %L2TM-7-UNAVAILABLE: Internal error: %s Explanation    An internal error occured.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L3_MGR","3","ERROR","%s: %s","An error has occurred in the Layer 3 in-service software upgrade (ISSU) process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L3_MGR_ISSU","3","ERROR","%s: %s","An error has occurred in the Layer 3 ISSU manager process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L3MM","4","AP_DB_ADD","Failed to add AP to DB { AP: [enet], [IP_address]}","The L3MM failed to add the entry for the specified access point (AP) into the AP database.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L3MM","4","AP_DB_DEL","Failed to delete AP from DB { AP: [enet], [IP_address]}","The L3MM failed to delete the entry for the specified AP from the AP database.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L3MM","4","DUP_AP_IPADDR","AP [enet] is requesting ip [IP_address] which is being used by another AP","The L3MM detected that an access point requested an IP address that is being used by another access point in the network.","Change the IP address of one of the two access points."
"L3MM","4","DUP_IPADDR","MN [enet] is requesting ip [IP_address] which is being used by MN [enet]","The L3MM detected that a mobile node requested an IP address that is being used by another mobile node in the network.","Change the IP address of one of the two mobile nodes."
"L3MM","4","INIT_FAIL","Initialization failure; reason: [chars]","The L3MM failed to initialize due to the specified reason.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L3MM","4","MALLOC_FAIL","Memory allocation failure [chars]","The L3MM failed to allocate memory that was needed to perform an operation or to respond to an event.","Increase the memory on the router processor of the supervisor engine."
"L3MM","4","MN_IPDB_ADD","Failed to add MN to MN DB { MN: [enet], [IP_address]}","The L3MM failed to add the entry for the specified mobile node into the mobile node IP database.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L3MM","4","MN_IPDB_DEL","Failed to delete MN from IP DB { MN: [enet], [IP_address]}","The L3MM failed to delete the entry for the specified mobile node from the mobile node IP database.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L3MM","4","MN_MACDB_ADD","Failed to add MN to MAC DB { MN: [enet], AP: [IP_address] }","The L3MM failed to add the entry for the specified mobile node into the mobile node MAC database.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L3MM","4","MN_MACDB_DEL","Failed to delete MN from MAC DB { MN: [enet], [IP_address], AP: [IP_address], WNID: [dec] }","The L3MM failed to delete the entry for the specified mobile node from the mobile node MAC database.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"L3MM","5","WLAN","Wireless LAN Module in slot [dec] is [chars]","The L3MM detected a change in the state of the wireless LAN module in the specified slot. If the module is now on line, the L3MM starts accepting access-point and mobile-node registrations from the WDS on the module. If the module is now off line, the L3MM purges all access points and mobile nodes received from the module.","No action is required."
"L3MM","5","WLAN_COMM_ABORT","Communication with Wireless LAN Module in slot [dec] aborted ([chars])","The L3MM detected a communication failure with the wireless LAN module specified in the error message above. The L3MM will respond by purging its access point and mobile node databases as if the module went offline. However, the module will not be reset by the L3MM.","No action is required."
"L3MM","5","WLAN_PWR_DN","Wireless LAN Module in slot [dec] will be powered down, another module is already active","The L3MM detected a wireless LAN module trying to come online, while another module was already functional as the active wireless LAN module. The L3MM does not support more than one wireless LAN module on line in the chassis at a given time, which is why this module will be powered down.","No action is required."
"L3TCAM","3","SIZE_CONFLICT","[chars] requires enabling extended routing","The TCAM entry has not been configured to enable extended routing. In order to support this feature, it is required that the TCAM entry be configured to enable extended routing.","Modify the Switch Database Management template so that the switch is enabled to support the 144-bit Layer 3 TCAM. Enter the sdm prefer extended-match, sdm prefer access extended-match, or sdm prefer routing extended-match global configuration command, then reload the switch by entering the reload privileged EXEC command."
"L3TCAM","3","TOO_MANY_VRF","Exceed the maximum number of VRF allowed","The number of VPNs has exceeded the maximum number of VPNs that are allowed in the VPN routing and forwarding table on this hardware platform.","Reconfigure your switch to limit the number of VRFs. Do not define more than seven VRFs when you are entering the ip vrf vrf-name command, with vrf-name being the name of the VRF instance, in global configuration mode."
"LACP","4","MULTIPLE_NEIGHBORS","Multiple neighbors detected on %s","The Link Aggregation Control Protocol (LACP) detected multiple neighbors on the specified interface.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LANCE","1","UNAVAILABLE","msgtxt_initfail","The hardware failed to initialize correctly.","Repair or replace the controller."
"LANCE","1","UNAVAILABLE","msgtxt_memoryerror","An Ethernet interface detected a hardware problem.","Repair or replace the controller."
"LANCE","3","UNAVAILABLE","Unit %d, spurious IDON interrupt, csr%d=0x%04x","An Ethernet interface generated a spurious Initialization Done interrupt.","Repair or replace the controller."
"LANCE","3","UNAVAILABLE","Unit %d, underflow error","The Ethernet hardware is requesting data faster than the system can supply it. This condition might indicate that the system is at the limit of its performance.","A small number of underflows might not be a cause for concern. You can monitor underflows with the show interface command. Reducing the load on the router or installing a higher-performance router should alleviate this problem."
"LANCE","3","UNAVAILABLE","msgtxt_badcable","Ethernet cable is not connected.","Check Ethernet cable connection."
"LANCE","3","UNAVAILABLE","msgtxt_badunit","An internal software error occurred.","If either message recurs, call your technical support representative for assistance."
"LANCE","3","UNAVAILABLE","msgtxt_ownerror","An Ethernet interface is malfunctioning, or an internal software error occurred.","Repair or replace the controller."
"LANCE","4","UNAVAILABLE","Unit %d, babble error, csr0 = 0x%x","An Ethernet interface is malfunctioning.","Determine whether the malfunction stems from a software or hardware error by turning off all fastswitching. Error messages showing that the packet is too large for the link indicate a software error at a high level. Copy the error message exactly as it appears, and report it to your technical support representative. Receiving no error messages indicates a hardware error. Repair or replace the controller."
"LANCE","5","UNAVAILABLE","Unit %d, excessive collisions. TDR=%d","An Ethernet cable is broken or unterminated, or the transceiver is unplugged. The time delay reflectometer (TDR) counter is an internal LANCE counter that counts the time (in ticks of 100 ns each) from the start of a transmission to the occurrence of a collision. Because a transmission travels about 35 feet per tick, this value is useful to determine the approximate distance to a cable fault.","If the transceiver appears to be properly terminated, repair or replace the Ethernet interface card."
"LANCE","5","UNAVAILABLE","Unit %d, late collision error","An Ethernet transceiver is malfunctioning, the Ethernet is overloaded, or the Ethernet cable is too long.","Repair or replace the controller."
"LANCE","5","UNAVAILABLE","Unit %d, lost carrier. Transceiver problem?","An Ethernet transceiver is unplugged or faulty.","Repair or replace the controller."
"LANE","3","UNAVAILABLE","%s %s cannot register %Cj with ILMI","An attempt to register the given ATM address with the ATM switch failed. This failure can occur because the ATM switch is down or misconfigured. The registration will be retried.","If the situation persists after a number of attempts, and the switch is up, the configuration of the switch and router should be examined. A likely cause is that the ATM address being registered is not compatible with the parameters configured in the switch. Correct the configuration."
"LANE","3","UNAVAILABLE","%s","A LANE client software or hardware error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"LANE","3","UNAVAILABLE","%s","A serious internal occured with LES/BUS.","This error should not occur. Download the system error log, then call your technical support representative and provide the log, the error message, and the router configuration."
"LANE","3","UNAVAILABLE","%s","An internal consistency error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"LANE","3","UNAVAILABLE","%s","An internal error has occured, which reflects an inconsistency in the system and needs attention.","Copy the error message exactly as it appears, and report it to your technical support representative."
"LANE","3","UNAVAILABLE","%s","An internal error occurred while system routines were handling ATM signaling messages for LANE.","Copy the error message exactly as it appears, and report it to your technical support representative."
"LANE","3","UNAVAILABLE","%s CFG_REQ failed, %s (LECS returned %d)","The master LECS refused the LEC's configuration request.","Check your LECS configurations."
"LANE","3","UNAVAILABLE","%s CTL DIST blli type wrong","Wrong BLLI value specified on the incoming circuit.","The originator of the circuit is not using the correct BLLI value for this type of circuit. LANE standard defines these values, and the originator is violating the standard."
"LANE","3","UNAVAILABLE","%s JOIN failed, %s (LES returned %d)","LANE client was rejected the Join request to join its elan.","This is usually because of user configuration errors: LANE client attempting to join an incorrect elan, or elan not configured in the LES, or validation failures with the LECS, etc..."
"LANE","3","UNAVAILABLE","%s LEC unable to compute ATM address","The client cannot obtain an ATM address from the given configuration, or auto-assignment failed to get an ATM prefix from the switch.","If you expect the switch to assign the prefix to the router, check that the Interim Local Management Interface (ILMI) is functional and the switch has a prefix configured. Otherwise, confirm that the client has an address in the NVRAM configuration."
"LANE","3","UNAVAILABLE","%s RD REGISTER failed for Route Descriptor %x","A software or hardware error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"LANE","3","UNAVAILABLE","%s REGISTER failed, %s (LES returned %d)","attempt to register a mac-atm address binding with LES failed.","The LES has already registered the requested mac addr - atm addr binding."
"LANE","3","UNAVAILABLE","%s elan %s unable to compute %s ATM address","Software was unable to compute an ATM address based on the ATM address template given. The characters in chars (see above display) will be either BUS (broadcast-and-unknown), server, or config server in the actual error message.","Enter a correct ATM address template for the LANE component (BUS, server, or config server) named in the error message."
"LANE","3","UNAVAILABLE","%s elan %s unrecoverable error %s","A very serious LES/BUS internal error occurred.","This error should not occur. Download the system error log, then call your technical support representative and provide the log, the error message, and the router configuration."
"LANE","3","UNAVAILABLE","%s listen failed on %s","The LANE client could not register its address with ATM signalling to be able to accepts calls on that address.","Reconfigure the client ATM address. It may be conflicting with another component with the same ATM address."
"LANE","3","UNAVAILABLE","%s still destroying old sub-interface","An attempt was made to create a new subinterface while a previous version of the subinterface was still being destroyed.","Wait a minute and try again. If failure still occurs, try shutting down the main interface. Rebooting may be required to recover in extreme cases."
"LANE","3","UNAVAILABLE","%s: elan id mismatch: LECS indicates %u, LES indicates %u","The elan-id returned by LES does not match the value given by LECS or via the CLI","Check configuration of elan ids specified in the LECS database and the LES. The mismatch must be occuring as a result of misconfiguration."
"LANE","3","UNAVAILABLE","A LANE Client is already running here using another elan name","Both the LANE client and the LANE server/BUS may have an emulated LAN name specified in the configuration via the lane server-bus and lane client commands. If both specify the emulated LAN name, then the name cannot be changed by re-entering just one of the commands.","Use the no lane server-bus command to delete the server-bus or the no lane client command to delete the client. Then, the other of the two commands can be re-entered with another emulated LAN name. Finally, re-enter the deleted command with the new emulated LAN name."
"LANE","3","UNAVAILABLE","A LANE Client is already running here using another elan type","Both the LANE client and the LANE Server/BUS may have an ELAN type specified in the configuration via the lane server-bus and lane client commands as either Ethernet or Token Ring. If both, specify the type; the type cannot be changed by re-entering just one of the commands.","Use the no lane server-bus command to delete the server-bus or the no lane client command to delete the client. Then, the other of the two commands can be re-entered with a new type. Finally, re-enter the deleted command with the new type."
"LANE","3","UNAVAILABLE","ELAN name must be 1-32 characters long","A name which is longer than 32 characters identifying a LANE component has been entered by the user.","Re-enter a shorter name."
"LANE","3","UNAVAILABLE","ILMI service registration failed","The Interim Local Management Interface (ILMI) feature is either not included in the software image running on the router, or is having other problems.","This error should not occur. Download the system error log, then call your technical support representative and provide the log, the error message, and the router configuration."
"LANE","3","UNAVAILABLE","Inappropriate LAN type","An unexpected LAN type has been specified for a LANE component. Only ethernet and token-ring elans are supported.","Specify a valid LAN type."
"LANE","3","UNAVAILABLE","Received bad control message on interface %s","The LANE client received an unexpected or inappropriate control message over one of its vc's.","Copy the error message exactly as it appears, and report it to your technical support representative."
"LANE","3","UNAVAILABLE","Unexpected ILMI event %d","An internal error occurred.","This error should not occur. Download the system error log, then call your technical support representative and provide the log, the error message, and the router configuration."
"LANE","3","UNAVAILABLE","Unexpected SigAPI event %d","ATM signaling sent the LANE client an unexpected message type.","Copy the error message exactly as it appears, and report it to your technical support representative."
"LANE","4","UNAVAILABLE","%s","The LANE Configuration Server address could not be registered with or de-registered from the switch, using Interim Local Management Interface (ILMI). Possible causes: The switch prefix is not available. The address is not acceptable to the switch (the prefix does not conform). The interface over which this operation should take place is down. The ILMI subsystem on the router is not completely initialized.","Copy the error message exactly as it appears, and report it to your technical support representative."
"LANE","4","UNAVAILABLE","%s elan %s LECIDs exhausted","The LANE server specified has 65279 clients. No more can be added.","Change the configurations to avoid trying to have more than 65279 LANE clients on this server."
"LANE","4","UNAVAILABLE","%s elan %s unable to register LES/BUS ATM addr","LANE Server or BUS could not register its address with ILMI.","Try and investigate why. Some of the reasons are: user defined override address does not conform to the switch prefix, or that there is a problem with the ATM switch with whom the entity is registering."
"LANE","5","UNAVAILABLE","%s %s %s: %s changed state to %s","A LANE component changed state to up/down.","If this event is expected, then take no action. Otherwise, please contact a technical support representative."
"LANE","6","UNAVAILABLE","%s","LANE client informational messages.","None."
"LANE","6","UNAVAILABLE","%s","LANE subsystem simple informational messages.","None."
"LANE","6","UNAVAILABLE","%s","Simple informational LECS messages.","None."
"LANE","6","UNAVAILABLE","%s","Simple informational LES messages.","None."
"LANMGR","2","UNAVAILABLE","No memory available: %s","The requested operation failed because of a low memory condition.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"LANMGR","4","UNAVAILABLE","Cannot run RPS on %s, Old TRAMON code.","The software on this interface cannot support the functions required for LAN Network Manager.","Call your Cisco technical support representative about a firmware upgrade for this interface card."
"LANMGR","4","UNAVAILABLE","No ring info for %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LANMGR","4","UNAVAILABLE","Ring number mismatch on %s, shutting down the interface","The router detected a conflict in assigned ring numbers for the specified Token Ring. The Ring Parameter Server (RPS) function was shut down to prevent potentially incorrect information from being sourced onto the ring.","Check all bridges connected to this Token Ring and ensure that they are using the same assigned ring number."
"LANMGR","4","UNAVAILABLE","Unexpected call (%s) from LLC2 for Bridge %03x-%x-%03x","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LAPB","2","NOBUF","Interface [chars], no buffer available to [chars]","There was insufficient memory for the LAPB protocol engine to send a message.","This message is acceptable if it occurs infrequently, because the LAPBprotocol is designed to handle loss of frames. Frequent occurrences can cause disruption of service. The system can be configured to ease memory demands or, if conditions warrant, the system can be upgraded to a larger memory configuration."
"LAPB","3","UNAVAILABLE","%s: %s","An internal software error occurred.","If either of these messages recur, call your technical support representative for assistance."
"LAPB","3","UNAVAILABLE","Input idb not set","An internal software error occurred.","If either of these messages recur, call your technical support representative for assistance."
"LAPB","3","UNAVAILABLE","Interface %s, Invalid payload value: %s","An internal software error occurred.","If either of these messages recur, call your technical support representative for assistance."
"LAPB","3","UNAVAILABLE","Interface %s, NULL packet ptr, rvr %d, vs %d, vr %d","An internal software error occurred.","If either of these messages recur, call your technical support representative for assistance."
"LAPB","3","UNAVAILABLE","LAPB timer task cannot be created","An internal software error occurred.","If either of these messages recur, call your technical support representative for assistance."
"LAPB","4","UNAVAILABLE","Interface %s, Frame error: CF %#x, VS %d %c VR %d, Reason %#x","A FRMR frame was received, indicating that a protocol violation was detected. The Reason field will be interpreted by generating INFOBAD, CTRLBAD, N1TOOBIG, or INVNR messages immediately after this message; refer to the explanations for these messages for more information.","The protocol will recover by resetting the service. This will disrupt any network service on top of LAPB (for example, X.25 virtual circuits will be cleared). Follow the recommended action for any error message following the FRMR reports; if service becomes unacceptable, check the serial line and its attached devices."
"LAPB","4","UNAVAILABLE","Interface %s, Info field not permitted","A received FRMR frame reported that an information field was present in a frame where no information field is allowed.","Check the serial line and the device attached to the line."
"LAPB","4","UNAVAILABLE","Interface %s, Invalid NR value","A received FRMR reported a frame with an invalid N(R) value.","Verify that the equipment attached to the serial line is configured with the same K value (maximum number of outstanding I frames)."
"LAPB","4","UNAVAILABLE","Interface %s, Invalid control field","A received FRMR reported a frame with an invalid control code.","Check the serial line and the devices attached to the line."
"LAPB","4","UNAVAILABLE","Interface %s, N1 too large","A received FRMR reported an information frame that was too long.","Verify that the equipment attached to the serial line is configured with the same N1 value. N1 is in bits and includes the entire frame plus 16 bits of CRC. However, some equipment may require configuration in octets, the omission of the two CRC octets, or the omission of the three octets of LAPB control information."
"LAPP_OFF","1","UNAVAILABLE","msgtxt_nomemory","The requested operation could not be accomplished because of a low memory condition.Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.LAPP_OFF-2Error Message    %LAPP_OFF-2-UNAVAILABLE: Internal software error, %s Explanation    An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LAPP_OFF","2","UNAVAILABLE","Internal software error, %s, cid=%d","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LAPP_OFF","4","UNAVAILABLE","FAXMAIL- Could notsend data to the SMTP server","A connection was made to the SMTP server, but no data can be sent.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LAPP_OFF","4","UNAVAILABLE","LAPP_OFF- Bad message received","An unexpected message was received.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LAPP_OFF","4","UNAVAILABLE","SMTP- failed %s, %d","A connection attempt to a remote mail server was not successful. This unexpected behavior.","LOG_STD_NO_ACTION"
"LAPP_OFF","4","UNAVAILABLE","mmsp- Can't connect to the SMTP server","No connection was created to the specified SMTP server.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LAT","3","UNAVAILABLE","Null IDB pointer with destination %e","An internal software error occurred.","If this message recurs, contact your technical support representative."
"LAT","3","UNAVAILABLE","Queue block at %x not found for HI connection","An internal software error occurred.","If this message recurs, contact your technical support representative."
"LAT","3","UNAVAILABLE","Tty%t, Attempt to re-use slot array, empty = %d, fill = %d","An internal software error occurred.","If this message recurs, contact your technical support representative."
"LAT","3","UNAVAILABLE","Tty%t, Data pointer does not correspond to current packet","An internal software error occurred.","If this message recurs, contact your technical support representative."
"LAT","3","UNAVAILABLE","Tty%t, Output data ptrs out of sync with byte count","An internal software error occurred.","If this message recurs, contact your technical support representative."
"LAT","3","UNAVAILABLE","Tty%t, data buffer full with count %d","An internal software error occurred.","If this message recurs, contact your technical support representative."
"LB","3","UNAVAILABLE","%s %s","There was a subinterfce error for the given interface.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LB","3","UNAVAILABLE","%schannel: failed to create chunk","An internal data structure, called a chunk, and used for channel route processor - line card interprocess communications, failed to be created. Such interprocss communication may be impeded.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LB","3","UNAVAILABLE","Bundle creation feature callback failed for %s","For the given link bundle interface, failed to create its feature callback.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LB","3","UNAVAILABLE","Channel %d, error in MAC address allocation, configured MAC address %e, actual MAC address %d","For the given channel number, addition of the first member caused a failure in changing the MAC address of the channel to that of this first member.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LB","3","UNAVAILABLE","Empty link bundling function vector(s)","One or more function vectors used in generic etherchannel and poschannel code was null i.e. not initialized. This is a severe error resulting from a coding error. Crash will happen because this error prevents the proper functioning of the ether or pos channel features.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LB","3","UNAVAILABLE","Failed to apply ACL %d to interface %s. Removing new ACL config, reapplying old ACL %d.","For the given member interface or subinterface, failed to apply the given ACL. This new ACL configuration is removed from the bundle and the old ACL configuration, if any, is reapplied to the bundle. The new ACL that failed to be applied is removed in order to maintain consistent state for the whole bundle.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LB","3","UNAVAILABLE","Failed to create Link Bundle Feature ListQ","In initializing link bundling feature support, an internal list queue failed to be created.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LB","3","UNAVAILABLE","Failed to create Link Bundle Subinterface ClientQ","In initializing link bundling subinterface feature support, an internal subinterface client queue failed to be created.","Copy the error message exactly as it appears, and report it to your technical support representative."
"LB","3","UNAVAILABLE","Failed to register ACL control block with Link Bundle subinterface module","For the given interface, failed to register the ACL feature control block. This happened during install ACL support for link bundling. ACL support installation for link bundling is aborted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LB","3","UNAVAILABLE","Failed to register bundle interface %s for Command Replay service","For the given link bundle interface, failed to register it for the Command Replay service.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LB","3","UNAVAILABLE","Failed to registered Link Bundle ACL feature control block","For the given interface, failed to register the ACL feature control block.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LB","3","UNAVAILABLE","Failed to registered Link Bundle subinterface control block","In initializing link bundling subinterface feature support, could not register for notifications from the common link bundle infrastructure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LB","3","UNAVAILABLE","NULL notification callback","In registering a client for service from the Link Bundling subinterface module, the callback notification callback function was NULL.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LB","3","UNAVAILABLE","One or more NULL feature callbacks in the passed in Feature Control Block","In registering a feature for services from link bundling feature support, there were one or more NULL function pointers used as function callbacks. Aborted the feature registration as a result.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LB","3","UNAVAILABLE","One or more NULL feature control block members","In installing link bundling feature support, there were one or more NULL function pointers used in a feature control block. Installation of the feature support is aborted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LB","5","UNAVAILABLE","%s added as member-%d to %schannel%d","The given channel member interface was added to the given channel number.","Informational only, No action required."
"LB","5","UNAVAILABLE","%s added as passive member to %schannel%d","The given interface was added as a passive member in the given channel number.","Informational only, No action required."
"LB","5","UNAVAILABLE","%s moved to active state as member-%d in %schannel%d","The given etherchannel member interface became an active member in the given channel number.","Informational only, No action required."
"LB","5","UNAVAILABLE","%s moved to passive state in %schannel%d","The given channel member interface became a passive member in the given channel number.","Informational only, No action required."
"LB","5","UNAVAILABLE","%s taken out of %schannel%d","The given channel member interface was taken out of the given channel number.","Informational only, No action required."
"LC","2","UNAVAILABLE","LC interface idb incorrect, %#x","The line card control block (LCCB) data structure indicates a zero interface descriptor block (IDB).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC","2","UNAVAILABLE","LC interface lccb incorrect, %#x","The line card control block (LCCB) data structure was incorrectly set in the command data structure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC","2","UNAVAILABLE","Line Card type %d in slot %d serial link sync failed.","LC serial link sync failed in the specified slot.","Check that the card is properly seated properly. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC","2","UNAVAILABLE","Line Card type %d in slot %d wedged.","LC initializaion failed in the specified slot.","Check that the card is properly seated properly. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC","2","UNAVAILABLE","Out of range Line Card interface, %d on bay %d","The software specified an out-of-range line card interface.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC","2","UNAVAILABLE","Out of range Line Card slot %d","The software specified an out-of-range line card slot.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC","2","UNAVAILABLE","Out of range Line Card slot %d Sub Module slot %d","The software specified an out-of-range sub module slot.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC","2","UNAVAILABLE","Recursive loop while getting the daughtercard info for LC type %d","While getting the daughter card info for the chassismib the platform snmp code goes into an infinite loop.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC","2","UNAVAILABLE","Undefined Line Card type %d in slot %d","The software does not have a driver for the line card type in the specified slot.","Make sure the image you are running is supposed to support this card.Check that the card is properly seated. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC","3","UNAVAILABLE","%s Linecard I2C bus access failed at slot %d, status = 0x%x","The line card in the specified slot experienced an I2C access failure. This problem often occurs when the I2C failed to gracefully terminate the previous transaction and could be the result of a hardware or software caveat. The line card is automatically deactivated.","Reactivate the line card using hw-module slot slot-number start. If this command fails to reactivate the line card, copy the error message exactly as it appears on the console and collect the show diag slot-number output. Remove the line card and place it in a different slot. If the line card fails to initialize in the new slot, call your Cisco technical support representative and provide the representative with the gathered information."
"LC","3","UNAVAILABLE","%s(%d) Line card fpga requires min h/w revision of (%d.%d)","A newer hardware revision of the line card is required for current fpga to function properly on this chassis.","Upgrade your hw version, or downgrade fpga version"
"LC","3","UNAVAILABLE","%s(%d) Line card requires fpga revision of (%d).Current fpga revision is (%d)","A newer fpga revision of the line card is required for functional operation on this chassis.","Upgrade you fpga version"
"LC","3","UNAVAILABLE","CI-MUX: Serial Link 0x%x, Status 0x%x, %s","Cluster interconnect multiplexer FPGA on RP detected an error at the specified line card serial link. This error could be the result of line card fpga logical errors or the result of an incorrect line card serial link bringup by the line card software driver. The line card is automatically deactivated and recovered.","If line card recovery fails 5 times within an hour, line card is deactivated without further attempts at recovery. Reactivate the line card using hw-module slot slot-number start. If this command fails to reactivate the line card, copy the error message exactly as it appears on the console and collect the show diag slot-number output. Remove the line card and place it in a different slot. If the line card fails to initialize in the new slot, call your Cisco technical support representative and provide the representative with the gathered information."
"LC","3","UNAVAILABLE","Errors seen on the line card (slot %d) exceeds the error threshold","The software is attempting to recover the line card from certain fatal errors such as (1) line card serial link error, (2) line card FPGA or device error, (3) excessive interrupts, (4) local processor firmware crash, (5) loss of keepalive from card local processor,and (6) card local processor firmware IPC initialization failure. The line card will automatically reinitialize after this error, unless the error occurs five times in one hour. If a line card encounters five such error in one hour, the line card will be deactivated without further attempts at recovery.","Try and reactivate the line card manually by entering the hw-module slot slot-number start command. The line card can also be reactived by removing and reinserting the line card; if you take this approach, however, copy the error message as it appears on the console and collect the output from the show diag slot-number command before removing and reinserting the line card. If the error recurs, contact your Cisco technical support representative and provide the representative with the error message and the show diag slot-number output."
"LC","3","UNAVAILABLE","LC in slot%d (%s) is not supported on this %s","This line card is not supported on this chassis/cpucard.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC","3","UNAVAILABLE","LC in slot%d with hw version (%d.%d) is old. Requires base h/w revision of (%d.%d) for this line card","The hardware revision of the line card is old. Required a newer hardware revision for this line card to work properly with corrent IOS image.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC","3","UNAVAILABLE","Line card (slot %d) recovery in progress","This information message indicates that a line card is recovering from a fatal error. This error could be: (1) line card serial link error, (2) line card FPGA or device error, (3) excessive interrupts, (4) card local processor firmware crash, (5) loss of keepalive from card local processor, and (6) card local processor firmware IPC initialization failure.","Copy the error message exactly as it appears on the console or in the system log. Enter the show diag slot-number command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative, and provide the representative with the gathered information."
"LC","3","UNAVAILABLE","Line card common logic fpga (slot %d) error: %s","The line card common logic fpga in the specified slot encountered an error. This error could be result of a line card fpga caveat or a result of incorrect line card reset sequence by the line card software driver. Based on the fatality of the error, the line card is automatically deactivated and recovered.","If line card recovery fails 5 times within an hour, line card is deactivated without further attempts at recovery. Reactivate the line card using hw-module slot slot-number start. If this command fails to reactivate the line card, copy the error message exactly as it appears on the console and collect the show diag slot-number output. Remove the line card and place it in a different slot. If the line card fails to initialize in the new slot, call your Cisco technical support representative and provide the representative with the gathered information."
"LC","3","UNAVAILABLE","No line card in slot [%d].","There is no line card in the slot.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC","3","UNAVAILABLE","RP CI-MUX FPGA read timeout (Slot %d, Serial Channel %d)","Cluster interconnect multiplexer FPGA on RP could not complete line card I/O read transaction. This error could be the result of a timing error inside line card fpga or the result of an incorrect line card I/O access by the line card software driver. The line card is automatically deactivated and recovered.","If line card recovery fails 5 times within an hour, line card is deactivated without further attempts at recovery. Reactivate the line card using hw-module slot slot-number start. If this command fails to reactivate the line card, copy the error message exactly as it appears on the console and collect the show diag slot-number output. Remove the line card and place it in a different slot. If the line card fails to initialize in the new slot, call your Cisco technical support representative and provide the representative with the gathered information."
"LC","3","UNAVAILABLE","Recommended line card configuration exceeded","The aggregate throughput of the line cards exceed the rated capacity of this system.","Refer to the configuration guidelines for the maximum allowed aggregate throughput of the line cards for the system."
"LC","3","UNAVAILABLE","Santa Ana Asic: %s %d, Serial Channel %c (slot %d), Error Status 0x%x %s%s%s","Santa Ana asic on the RP or the indicated line card detected an error at the associated serial link. This error could be because of the line card fpga timing errors or because of an incorrect line card serial link bring up by the line card software driver. The line card is automatically deactivated and recovered.","If line card recovery fails 5 times within an hour, line card is deactivated without further attempts at recovery. Reactivate the line card using hw-module slot slot-number start. If this command fails to reactivate the line card, copy the error message exactly as it appears on the console and collect the show diag slot-number output. Remove the line card and place it in a different slot. If the line card fails to initialize in the new slot, call your Cisco technical support representative and provide the representative with the gathered information."
"LC","3","UNAVAILABLE","Unable to %s for Linecard Slot %d","Possible memory shortage","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC","3","UNAVAILABLE","Unable to create driver for Line Card type %d in slot %d","Possible memory shortage or line card hardware error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC","3","UNAVAILABLE","line card in slot [%d] deactivated.","The line card is being deactivated.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC","3","UNAVAILABLE","line card in slot [%d] failed to reset.","An attempt to reset and initialize the line card timed out.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCB","3","UNAVAILABLE","LCB process unable to create event queue","Unable to create LCB event queue. LCB process quit. The operating system was unable to allocate RAM space for the queue","Try executing the command again after a few minutes. If the problem persists it indicates a lack of RAM space. Most likely, the router image requires more system memory (RAM) than the router contains."
"LCB","3","UNAVAILABLE","Multiple LCB event processes scheduled","This message occurs when LCB event process fails to lock the semaphore which is used to prevent multiple LCB processes from running. This implies that multiple LCB processes have been scheduled to run which should not happen","Try executing the command again after a few minutes. If the problem persists contact Cisco Technical support"
"LC_10G","3","ACCESS_FAIL","[chars] Access Fail","A read or write operation to the line card redundancy controller (LRC) scratch pad register has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_10G","3","AFOVR_ERR","Autofailover Error [chars]","The optical switch has encountered an error during an autofailover operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_10G","3","AFOVR_EVNT","Autofailover event occured [chars]","An autofailover event has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_10G","3","CDL_HEC_ERR_THR","CDL HEC Errors threshold [chars]","The threshold of allowable converged data link (CDL) header error control (HEC) errors has been exceeded.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_10G","3","CRC_ERR_THR","CRC Errors threshold [chars]","The threshold of allowable cyclic redundancy check (CRC) errors has been exceeded.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_10G","3","ETH_DCC_LPBK_FAIL","EthernetDcc loopback Fail","A loopback operation through the Ethernet backplane has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_10G","3","IDPROM_ACCESS_FAIL","Idprom Access Fail","The IDPROM could not be read or checked.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_10G","3","INTERNAL_CRITICAL","[chars]","A critical internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_10G","3","INTERNAL_ERROR","[chars]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_10G","3","INT_LPBK_FAIL","Internal Card loopback Fail","A loopback attempt that was internal to the card has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_10G","3","LASER_AUTO_SHUTDOWN","Auto Laser Shutdown [chars]","The laser has been automatically shut down.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_10G","3","LASER_BIAS_ALARM","Optic Laser Bias Alarm [chars]","An error involving laser bias has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_10G","3","LASER_TEMP_ALARM","Optic Laser Temperature Alarm [chars]","An error involving the temperature of the optics laser has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_10G","3","LASER_TX_FAULT","Optic Laser Transmit Fault [chars]","An error involving optics laser transmission has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_10G","3","LOSS_OF_LOCK","Transceiver Loss of Lock [chars]","The transceiver has lost the lock onto the incoming signal.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_10G","3","LOSS_OF_SYNC","Transceiver Loss of Sync [chars]","The transceiver has lost its frame synchronization.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_10G","3","LPBK_THRU_PSC_FAIL","loopback through PSC Fail","A internal card loopback attempt through the processor and switch card (PSC) has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_10G","3","MIB_AFOVR_ERR_ALM","Optical Switch Error [chars] [chars] [chars]","An optical switch error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_10G","3","MIB_AFOVR_EVNT_ALM","AutoFailover Event [chars] [chars] [chars]","An autofailover event has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_10G","3","MIB_AUTO_LASER_SHUTDOWN","Auto Laser Shutdown [chars] [chars] [chars]","The laser has been shut down.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_10G","3","MIB_LASER_BIAS_ALM","Laser Bias Alarm [chars] [chars] [chars]","An error involving trunk laser bias has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_10G","3","MIB_LASER_TEMP_ALM","Laser Temperature Alarm [chars] [chars] [chars]","An error involving the temperature of the trunk laser has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_10G","3","MIB_LASER_TX_FLT_ALM","Laser Transmit Fault [chars] [chars] [chars]","An error involving trunk laser transmission has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_10G","3","MIB_LOSS_OF_LOCK_ALM","Loss of Lock [chars] [chars] [chars]","A loss-of-lock event has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_10G","3","MIB_LOSS_OF_SYNC_ALM","Loss of Sync [chars] [chars] [chars]","A loss-of-synchronization event has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_10G","3","SYML_ERR_THR","Symbol Errors threshold [chars]","The threshold of allowable symbol errors has been exceeded.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_2P5G","3","ACCESS_FAIL","Access Fail [chars]","A read or write operation to the LRC scratch pad register has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_2P5G","3","AFOVR_ERR","Autofailover Error [chars]","The optical switch failed to perform an autofailover operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_2P5G","5","AFOVR_EVNT","Autofailover event occured [chars]","An autofailover event has occurred.","No action is required."
"LC_2P5G","3","CDL_HEC_ERR_THR","CDL HEC Errors threshold [chars]","The threshold of allowable converged data link (CDL) header error control (HEC) errors has been exceeded.","Check that the cables connected to the Rx transciever are plugged in, are not bent or twisted, and are in good condition. Check the physical state (transmit laser power level) and configuration of the remote end connected to the port associated. If the error message persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_2P5G","3","CRC_ERR_THR","CRC Errors threshold [chars]","The threshold of allowable CRC errors has been exceeded.","Check that the cables connected to the Rx transciever are plugged in, are not bent or twisted, and are in good condition. Check the physical state (transmit laser power level) and configuration of the remote end connected to the port associated. If the error message persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_2P5G","3","ETH_DCC_LPBK_FAIL","EthernetDcc loopback Fail [chars]","A loopback operation through the Ethernet backplane has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_2P5G","3","IDPROM_ACCESS_FAIL","Idprom Access Fail [chars]","The IDPROM could not be read or checked.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_2P5G","2","INTERNAL_CRITICAL","[chars]","An internal critical error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_2P5G","3","INTERNAL_ERROR","[chars]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_2P5G","3","INT_LPBK_FAIL","Internal Card loopback Fail [chars]","A loopback operation that was internal to the card has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_2P5G","5","LASER_AUTO_SHUTDOWN","Auto Laser Shutdown [chars]","The laser has been automatically shut down.","No action is required."
"LC_2P5G","3","LASER_DEGRADATION_ALARM","Optic Laser Degradation Alarm [chars]","The transmission power of the optics laser module is degrading.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_2P5G","3","LASER_NO_LIGHT_ALARM","Optic Laser Loss of Light Alarm [chars]","The optics laser has experienced a loss of light.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_2P5G","3","LASER_TX_FAULT","Optic Laser Transmit Fault [chars]","An optics laser transmission fault has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_2P5G","3","LASER_WAVE_LN_DEV_ALARM","Optic Laser Wavelength Deviation Alarm [chars]","The wavelength of the optics laser module has deviated.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_2P5G","3","LOSS_OF_LOCK","Transceiver Loss of Lock [chars]","The receiver has lost the lock on the incoming signal.","Check that the cables connected to the Rx transciever are plugged in, are not bent or twisted, and are in good condition. Check the physical state (transmit laser power level) and configuration of the remote end connected to the port associated. If the error message persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_2P5G","3","LOSS_OF_SYNC","Transceiver Loss of Sync [chars]","The decoder has lost its frame synchronization.","Check that the cables connected to the Rx transciever are plugged in, are not bent or twisted, and are in good condition. Check the physical state (transmit laser power level) and configuration of the remote end connected to the port associated. If the error message persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_2P5G","3","LPBK_THRU_PSC_FAIL","loopback through PSC Fail [chars]","An internal card loopback operation through the processor and switch card (PSC) has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_2P5G","3","MIB_AFOVR_ERR_ALM","Optical Switch Error [chars] [chars] [chars]","An autofailover operation for the optical switch has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_2P5G","5","MIB_AFOVR_EVNT_ALM","AutoFailover Event [chars] [chars] [chars]","An autofailover event has occurred.","No action is required."
"LC_2P5G","5","MIB_AUTO_LASER_SHUTDOWN","Auto Laser Shutdown [chars] [chars] [chars]","The laser has been automatically shut down.","No action is required."
"LC_2P5G","3","MIB_CVRD_ERR_THR","CVRD Error Threshold Exceeded [chars] [chars] [chars]","The threshold of allowable symbol errors has been exceeded.","Check that the cables connected to the Rx transciever are plugged in, are not bent or twisted, and are in good condition. Check the physical state (transmit laser power level) and configuration of the remote end connected to the port associated. If the error message persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_2P5G","3","MIB_LASER_DEG_ALM","Laser Degradation Alarm [chars] [chars] [chars]","The transmission power of the optics laser module is degrading.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_2P5G","3","MIB_LASER_TX_FLT_ALM","Laser Transmit Fault [chars] [chars] [chars]","An optics laser transmission fault has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_2P5G","3","MIB_LASER_WV_DEV_ALM","Laser Wavelength Deviation Alarm [chars] [chars] [chars]","The wavelength of the optics laser module has deviated.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_2P5G","3","MIB_LOSS_OF_LOCK_ALM","Loss of Lock [chars] [chars] [chars]","The receiver has lost its lock on the incoming signal.","Check that the cables connected to the Rx transciever are plugged in, are not bent or twisted, and are in good condition. Check the physical state (transmit laser power level) and configuration of the remote end connected to the port associated. If the error message persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_2P5G","3","MIB_LOSS_OF_SYNC_ALM","Loss of Sync [chars] [chars] [chars]","The decoder has lost its frame synchronization.","Check that the cables connected to the Rx transciever are plugged in, are not bent or twisted, and are in good condition. Check the physical state (transmit laser power level) and configuration of the remote end connected to the port associated. If the error message persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.."
"LC_2P5G","3","MIB_NO_LIGHT_ALM","Laser Loss of Light Alarm [chars] [chars] [chars]","An error involving a loss of light for the optics laser has occurred.","Check that the cables connected to the Rx transciever are plugged in, are not bent or twisted, and are in good condition. Check the physical state (transmit laser power level) and configuration of the remote end connected to the port associated. If the error message persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LC_2P5G","3","SYML_ERR_THR","Symbol Errors threshold [chars]","The threshold of allowable symbol errors has been exceeded.","Check that the cables connected to the Rx transciever are plugged in, are not bent or twisted, and are in good condition. Check the physical state (transmit laser power level) and configuration of the remote end connected to the port associated. If the error message persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Egress FC/ESCON Loss of Sync %s %s %s","Fiber Channel/ESCON Syncronization error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Egress GE Loss of Sync %s %s %s","GE Loss of Syncronization error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Alarm: %s, %s, %s, %s, %s","Submit An alarm - Prints out descriptive message","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","CDL Drop FIFO OvrFL %s %s %s","CDL Drop FIFO Overflow Prealarm","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","CDL Drop FIFO OvrFL; %s","CDL Drop FIFO Overflow Prealarm","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","CDL HEC Err count %s %s %s","CDL HEC error count threshold exceeded","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","CDL HEC Err count; %s","CDL HEC error count threshold exceeded","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Card [slot %d] present but not ready","Card is present but can not talk to it, perhaps card in reset","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Egress CDR Locking error %s %s %s","CDR is having trouble locking onto the signal.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Egress CDR Locking error; %s","CDR is having trouble locking onto the signal.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Egress FC/ESCON Loss of Sync; %s","Fiber Channel/ESCON Syncronization error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Egress Fiber Channel/ESCON Line Err %s %s %s","Fiber Channel/ESCON Line code error count exceeded threshold","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Egress Fiber Channel/ESCON Line Err; %s","Fiber Channel/ESCON Line code error count exceeded threshold","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Egress GE Line Code Err count %s %s %s","GE Line Code error count exceeded threshold","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Egress GE Line Code Err count; %s","GE Line Code error count exceeded threshold","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Egress GE Loss of Sync; %s","GE Loss of Syncronization error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Egress Loss of Light %s %s %s","Egress side No Light","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Egress Loss of Light Prealarm %s %s %s","Egress side No Light; switched over to other side","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Egress Loss of Light Prealarm: %s","Egress side No Light; switched over to other side","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Egress Loss of Light: %s","Egress side No Light","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Egress SONET BIP Err count %s %s %s","SONET BIP Err count exceeded threshold","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Egress SONET BIP Err count; %s","SONET BIP Err count exceeded threshold","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Egress SONET Loss of Frame %s %s %s","SONET Loss of Frame error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Egress SONET Loss of Frame; %s","SONET Loss of Frame error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Egress SONET SEF Prealarm %s %s %s","Egress SONET Severely Errored Frame threshold exceeded","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Egress SONET SEF; %s","Egress SONET Severely Errored Frame threshold exceeded","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Egress Serdes Locking error %s %s %s","Serdes has trouble locking onto the signal","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Egress Serdes Locking error; %s","Serdes has trouble locking onto the signal","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Egress Serdes Phase Error %s %s %s","Serdes has a phase error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Egress Serdes Phase Error; %s","Serdes has a phase error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Egress Trunk Switch Mech. Failure %s %s %s","Egress side switch failed to switch position during auto-failover","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Egress Trunk Switch Mech. Failure; %s","Egress side switch failed to switch position during auto-failover","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","IDPROM CRC check failed [%s]","CRC check failed for IDPROM","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","IDPROM mismatch read failed [%s]","check with catched value fail","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","IDPROM read failed [%s]. 	The card may not be inserted correctly. Please ensure that card is 	inserted completely and then please fasten the screws completely.","The read error occurred when accessing the IDPROM","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Ingress CDR Locking error %s %s %s","Ingress CDR failed to lock onto signal","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Ingress CDR Locking error; %s","Ingress CDR failed to lock onto signal","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Ingress FC/ESCON Line Code err %s %s %s","Ingress FC/ESCON Line code error count threshold exceeded","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Ingress FC/ESCON Line Code err; %s","Ingress FC/ESCON Line code error count threshold exceeded","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Ingress FC/ESCON Loss of Sync %s %s %s","Ingress Fiber Channel/ESCON Loss of Syncronization","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Ingress FC/ESCON Loss of Sync; %s","Ingress Fiber Channel/ESCON Loss of Syncronization","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Ingress GE Line Code Err %s %s %s","Ingress Line Code error count threshold exceeded","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Ingress GE Line Code Err; %s","Ingress Line Code error count threshold exceeded","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Ingress GE Loss of Sync %s %s %s","Ingress GE Loss of the Syncronization","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Ingress GE Loss of Sync; %s","Ingress GE Loss of the Syncronization","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Ingress Loss of Light %s %s %s","Loss of Light","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Ingress Loss of Light; %s","Ingress side Loss of Light","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Ingress SONET BIP error %s %s %s","Ingress SONET BIP error count threshold exceeded","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Ingress SONET BIP error; %s","Ingress SONET BIP error count threshold exceeded","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Ingress SONET Loss of Frame %s %s %s","Ingress SONET Loss of frame","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Ingress SONET Loss of Frame; %s","Ingress SONET Loss of frame","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Ingress SONET SEF %s %s %s","Ingress SONET Severely Errored Frame threshold exceeded","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Ingress SONET SEF; %s","Ingress SONET Severely Errored Frame threshold exceeded","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Ingress Serdes Locking Error %s %s %s","Ingress Serdes signal lock error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Ingress Serdes Locking Error; %s","Ingress Serdes signal lock error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Ingress Serdes Phase error %s %s %s","Ingress Serdes out of Phase error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Ingress Serdes Phase error; %s","Ingress Serdes out of Phase error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Interface Create Failed [%s]","Interface data structure creation/initialization failed","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Interface Delete Failed [%s]","Interface data structure deletion failed","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Laser Degrade Trunk side %s %s %s","Laser Degrade failure on the transmit side","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Laser Degrade Trunk side; %s","Laser Degrade failure on the transmit side","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Line Laser Failure %s %s %s","Laser failure","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Line Laser Failure; %s","Laser failure","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Line OFC IND %s %s %s","Ingress OFC Indication","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Line OFC IND; %s","Ingress OFC Indication","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Loss of Light on Standby: %s","No Light on Standby","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Magic Register Reset Slot %d","Magic Register Reset for Linecard in slot","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Non supported clock rate %d Khz","The entered clock rate in Khz is not supported","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Non supported signal rate %d","The entered enum signal rate is invalid","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Pending unexpected interrupt [addr %#x = %#x]","One or more pending unexpected interrupts","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Port Creation Failed [%s]","Port data structure creation/initialization failed","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Read/write failed [%s]","A read/write error occurred when accessing the hardware","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Transceiver OIR; %s","OIR of the pluggable transceiver","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Transmit Failure %s %s %s","Transmit failure","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Transmit Failure; %s","Transmit failure","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Transparent Interface Creation Failed for slot [%d]","Interface data structure creation/initialization failed","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Trunk Laser wavelength deviation: %s %s %s","Trunk laser wavelength deviation","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Trunk Laser wavelength deviation: %s","Trunk laser wavelength deviation","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Trunk OFC IND %s %s %s","Egress OFC Indication","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Trunk OFC IND; %s","Egress OFC Indication","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Trunk laser degrade: %s %s %s","Trunk laser wavelength degrade","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Trunk laser degrade: %s","Trunk laser wavelength degrade","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Unexpected portfail asserted","One or more unexpected portfails asserted","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Unexpected trunk laser wavelength: %s","Trunk laser wavelength is incorrect","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Wavelength Deviation %s %s %s","Wavelength deviation error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","3","UNAVAILABLE","Wavelength Deviation; %s","Wavelength deviation error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","4","UNAVAILABLE","Encap rate mismatched: %s","The entered encap rate is not matched with xcvr type","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCMDC","5","UNAVAILABLE","Default wavelength selected: %s","The inserted transponder can not support cached hwsb-itu_num so the default wavelength is used instead","LOG_STD_NO_ACTION"
"LCMDC","6","TX_ALARM_SOAK","[chars]","An alarm has occurred. The message text provides additional details on the cause of the error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LCR","6","FAILED","Failed to send exported registry request %d; eobc_addr %x","There was a communication failure while sending an exported registry request.","No action is required."
"LCR","6","FAILED_MCAST","Failed to send exported registry request %d to mcast group","A communication failure occurred while attempting to send an exported registry request to a multicast group.","No action is required."
"LCR","6","FAILEDRCV","Failed to process registry request [dec]","A request received on a receiver could not be processed successfully.","No action is required."
"LCR","6","FAILED_RCV_ON_ACTIVE","Failed to process registry request [dec] - on active supervisor SP","A request received on the active supervisor engine could not be processed successfully.","No action is required."
"LDP","3","ISSU_XFORM","ISSU [chars] transformation failed for msg type ([dec])[chars].","The LDP could not upgrade or downgrade a checkpointing message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LDP","3","RECONNECT","[chars]","An error occurred while parsing the incoming LDP initialization message. The FT reconnect timer value received was greater than the locally-configured forwarding state holding timer value.","Reconfigure the forwarding state holding timer value."
"LDP","4","MAXMSGSIZE","Maximum implementation message size exceeded, actual %u, maximum %u","This is an informational message that appears when LDP receives a request to allocate memory resources for an LDP message with a size exceeding the current implemented maximum.","No action is required unless a larger message size is deemed to be required to support a new application. In this case the actual application should be identified and component owners contacted to increase the implemented maximum message size."
"LDP","5","CLEAR_CHKPT","Clear LDP bindings checkpoint state ([chars]) by [chars]","The checkpoint state for one or more LDP bindings has been reset.","No action is required."
"LDP","5","CLEAR_NBRS","Clear LDP neighbors ([chars]) by [chars]","One or more LDP neighbor sessions has been reset.","No action is required."
"LDP","5","GR","[chars]","An informational LDP notice was generated for a graceful restart event.","No action is required."
"LDP","5","SP","[chars]","An informational LDP notice was generated for a session protection event.","No action is required."
"LFD","2","AVL","[chars] [hex]","An error involving an Adelson-Velskii and Landis (AVL) tree operation has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","2","FPIHANDLER3","[chars] [hex] [hex] [hex]","An error has been detected in the forwarding path identifier (FPI) handler.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","BADEXEC","Unexpected Code Execution: [chars] [dec]","An error involving unexpected execution of code has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","BADFRRTYPE","illegal frr type: [dec]","An error involving an Fast ReRoute (FRR) request type has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","BADLABELADD","Cannot add label - [chars].","Unable to create label due to reason given.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","BADSHORTLABELADD","Cannot add short label: path_idx [dec], moi_type [dec]","Unable to create MFI feature space in FIB entry, so unable to store short path extension information there.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information."
"LFD","3","BROKERINITFAIL","Failed to initialise lte RP broker facility","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","CHUNKMGR","chunk mgr: [chars] [hex]","An error involving the memory manager has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","CHUNKMGRALLOC","failed chunk alloc: [chars]","An error involving memory allocation has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","CHUNKMGRDEALLOC","failed chunk dealloc: [chars]","An error involving the freeing of memory has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","EVTLOGBADSOURCE","Illegal log event source: [dec]","An illegal event in the log buffer has been detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","FIB_SRC","Lable [[dec]/[dec]] [chars] [chars] [chars]","The FIB entry could not be sourced for label in question.","Enter the show mpls forwarding-table internal and show ip route [vrf name] prefix commands and capture the error message traceback. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","FPIHANDLER","LFD SSS Handler: [chars]","An error has been detected in the FPI handler.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","FPITYPEWRONG","Require fpi type [chars], get fpi type [chars]","An error involving unmatched FPI types has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","INTFDB","intf db: [chars] [hex]","An interface DB error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","INTFDB2","intf db: [chars] [hex] [hex]","An interface DB error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","INVINSTALLER","Wrong installer [dec] for [chars] [dec]/[dec] update (was [dec])","The rewrite ID is invalid for non-IP label table entry.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","INVIPLABELTYPE","Wrong label type [dec] for IP Label [dec], table [dec] prefix [chars], vrf [chars]","The label type is invalid for the indicated label table entry.","Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show running-config commands and your pertinent troubleshooting logs."
"LFD","3","INVLABELTYPE","Wrong label type [dec] for non-ip LTE [dec]/[dec]","The label type is invalid for the non-IP label table entry.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","INVLABELUPDTYPE","Wrong label type [dec] for label [dec] table [dec] [chars] [chars]","An invalid label type was encountered during the specified operation.","Enter the show mpls forwarding-table label label internal command and capture the error message traceback. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","INVPATHLBL","[chars] [chars]","An invalid outgoing label is attached to the prefix.","Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show running-config commands and your pertinent troubleshooting logs."
"LFD","3","INVPLIST","Wrong path list type [dec] for label [dec]/[dec] [chars]","The path list type is set incorrectly for the label in question.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","INVRWID","Wrong rwid [dec] for non-ip LTE [dec]/[dec]","The rewrite ID is invalid for non-IP label table entry.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","INVXDRLEN","Length [int] for [chars] field in LTE msg for [chars]","An error occurred when encoding the MPLS label information for the FEC in question. This could result in line cards having stale labels for this FEC.","Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show running-config commands and your pertinent troubleshooting logs."
"LFD","3","KEY_DB_INSERTFAIL","[chars], entry [hex], existing [hex]","The element could not be inserted into the LFD's key database.","Enter the show mpls forwarding-table label label internal command and capture the error message traceback. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","LCXDRCLIENT","LTE distribution client: [chars]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","LTABLEMEM","Cannot allocate new mpls table [dec] of size [dec] needed for entry [dec]","There is not enough contiguous memory for the MPLS forwarding table.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"LFD","3","NONIPINFO","Non-ip info: [chars]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","NOOCE","Attempt to get labels from OCE failed - [chars].","The calling function has provided insufficient information to get labels.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","NORESOURCE","[chars] [dec]","A resource failure occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","NULLADJACENCY","NULL Adjacency","A NULL adjacency was encountered.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","NULLFIBIDB","NULL FIB IDB: [chars] [dec]","A NULL FIB IDB was encountered.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","ORPHANLTE","Label [dec]/[dec], plist [dec], LDM: [hex]","The LTE for the label was supposed to be deleted, but is still present.","Collect the running configuration and the output of the show mpls forwarding-table labels label-num command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","REWMGR","Rewrite Manager: [chars] [hex]","An error involving the rewrite manager has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","REWMGR2","[chars] [hex] [hex]","A rewrite lookup attempt has failed becuase of an inconsistency in the FPI.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","RPXDRCLIENT","Invalid XDR Client: %s","An internal software error occurred. The XDR client is invalid.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","RUNNING_TIMER","[chars] [dec] [chars] [dec]","The MPLS forwarding entry for the specified label was deleted prior to the expiry of its associated timer.","Enter the show mpls forwarding-table label label internal command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","SM","[chars] [dec]","An error involving the state machine has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","SMBADEVENT","Unexpected event [chars] for state [chars]","The LFD received an unexpected event for its state. The state of the LFD, and the unexpected event, are specified in the message text.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","UNSUPPORTED_XDR","[chars]","Decoding of an XDR message revealed data or a format that is unsupported in the current release.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","UPDATEHANDLER2","[chars] [hex] [hex]","An error involving the update handler has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","UPDATEHANDLER3","[chars] [hex] [hex] [hex]","An error involving the update handler has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","UPDATEHANDLERFPI","No handler installed: fpi=[dec] handler type=[chars]","No handler has been installed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","3","XDRBADMAGIC","xdr message for [chars] spilled out of allocated static storage","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","4","NOFIBIDB","[chars] - ifnum [dec]","The FIB IDB is missing on the line card.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","4","OWNCHANGED","Owner changed for [chars] [dec]/[dec] from [dec] to [dec]","A label was previously installed by a different installer.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","4","UNSUPPORTEDRW","Unexpected rewrites seen where MPLS is not supported by platform for this slot","MPLS is either not needed or not handled by the platform for this card and should not handle rewrites.","No action is required."
"LFD","5","FRRISSULOG","FRR is not ISSU compatible, notified by %s","The ISSU negotiation results for Fast Reroute (FRR) are not compatible.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LFD","6","RESOURCE","[chars]","MPLS is not supported by the platform.","No action is required."
"LIBT2F","2","UNAVAILABLE","A new text2fax context could not be created","An internal error occurred in the initialization of thetext2fax engine. The fax transmission will be aborted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LIBT2F","3","UNAVAILABLE","A text buffer is NULL","An internal error occurred in the text buffer processing. Thefax tranmission be aborted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LIBT2F","3","UNAVAILABLE","Cannot allocate a packetfrom shared memory","The system is running low on packet memory. The fax cannot besent correctly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LIBT2F","3","UNAVAILABLE","The text2fax engine failed","This occcurred most likely due to a memory limitation orillegal data being passed into the text2fax engine. The faxtransmission will be aborted","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LIBTIFF","3","UNAVAILABLE","A new tiff context could not be created","An internal error occurred in the initialization of thetiff engine. The fax transmission will be aborted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LIBTIFF","3","UNAVAILABLE","A tiff buffer is NULL","An internal error occurred in the tiff bufferprocessing. The fax tranmission will be aborted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LIBTIFF","3","UNAVAILABLE","A tiff buffer is invalid","An internal error occurred in the tiff bufferprocessing. The fax tranmission will be aborted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LIBTIFF","3","UNAVAILABLE","Cannot allocate a packetfrom shared memory","The system is running low on packet memory. Thefax cannot be sent correctlyError Message    %LIBTIFF-3-UNAVAILABLE: Invalid dial peer tag %d Explanation    Invalid mmoip dial peer tag","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LIBTIFF","3","UNAVAILABLE","The tiff engine failed","This occcurred most likely due to a memory limitation orillegal data being passed into the tiff engine. The fax transmission will be aborted","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LIBTIFF","4","UNAVAILABLE","Bad copy quality on tty%d","Noisy phone lines or a bad modem caused this error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LIC_AGENT","3","MEMORY","%s","License Agent subsystem has experienced a problem gettting the required memory to complete this operation.","Check system memory for other memory allocation errors and contact Technical support for problem resolution. In the absence of IOS errors upgrading the memory in the network device may be required."
"LICENSE","1","UNAVAILABLE","Feature %s %s running without a License in this device, UDI=%s","Your system is running a feature that is licensed. Running a feature without a license will create support and legal issues.","Please buy and install the license for the feature immediately. If you are seeing this message afterinstallation, contact TAC with show license file and show license detail output"
"LICENSE","1","UNAVAILABLE","Feature %s %s running without a License. UDI=%s","Your system is running a feature that is licensed. Running a feature without a license will create support and legal issues.","Please buy and install the license for the feature immediately. If you are seeing this message afterinstallation, contact TAC with show license file and show license detail output"
"LICENSE","1","UNAVAILABLE","Feature %s %s will expire on %s. UDI=%s Error Message    %LICENSE-1-UNAVAILABLE: License for feature %s %s has expired %s. UDI=%s","License for the feature specified has expired","If this message recurs, customer should buy the license from Cisco since feature will not run"
"LICENSE","1","UNAVAILABLE","License for feature %s %s will expire in %s. UDI=%s","License for the feature specified will expire in the specified time.","If this message recurs, customer should buy license for the feature from Cisco since feature will not run after license expiry"
"LICENSE","1","UNAVAILABLE","License request for feature %s %s failed in this device, UDI=%s","Your system is trying to run a feature without a license.","Please buy and install the license for the feature immediately"
"LICENSE","1","UNAVAILABLE","License request for feature %s %s failed. UDI=%s","Your system is trying to run a feature without a license.","Please buy and install the license for the feature immediately"
"LICENSE","2","UNAVAILABLE","%s","The IOS licensing subsystem does not have a primary storage","If this error message recurs, please copy the message and and contact the customer service"
"LICENSE","2","UNAVAILABLE","%s","The ios licensing subsystem detected corrupted storage","If this error message occurs, please reinstall all the licenses.If you do not have the licenses, please contact Cisco with the correctUDI to get all the licenses issued for this particular device"
"LICENSE","2","UNAVAILABLE","%s","The ios licensing subsystem does not have a primary storage","If this error message recurs, please copy the message and and contact the customer service"
"LICENSE","2","UNAVAILABLE","%s UDI=%s","The IOS licensing subsystem detected corrupted storage","If this error message occurs, please reinstall all the licenses.If you do not have the licenses, please contact Cisco with the correctUDI to get all the licenses issued for this particular device"
"LICENSE","2","UNAVAILABLE","'%s' failed with an error - rc = %d - '%s'","The IOS licensing subsystem encountered an error with the VLS api","If this error message recurs, please copy the message and and contact the customer service"
"LICENSE","2","UNAVAILABLE","'%s' failed with an error - rc = %d - '%s'","The ios licensing subsystem encountered an error with the VLS api","If this error message recurs, please copy the message and and contact the customer service"
"LICENSE","2","UNAVAILABLE","License IPC subsystem could not be initialized: %s","License IPC subsystem could not be initialized. The reason for failureis displayed after :","If this error message recurs, please copy the message and and contact the customer service, See whether the system resourcesare available"
"LICENSE","2","UNAVAILABLE","License for feature %s %s has expired %s, UDI=%s","License for the feature specified has expired","If this message recurs, customer should buy the license from Cisco since feature will not run"
"LICENSE","2","UNAVAILABLE","No memory available for %s","The IOS licensing subsystem could not obtain the memory it needed.","If this error message recurs, attempt to reduce memory usage by reducing the number of router features, or interfaces, enabled. Alternatively, add more memory. To display total memory usage for a router enter show memory summary at the privileged command line prompt. To display buffer usage enter show buffers at the prompt."
"LICENSE","2","UNAVAILABLE","No memory available for %s","The ios licensing subsystem could not obtain the memory it needed.","If this error message recurs, attempt to reduce memory usage by reducing the number of router features, or interfaces, enabled. Alternatively, add more memory. To display total memory usage for a router enter show memory summary at the privileged command line prompt. To display buffer usage enter show buffers at the prompt."
"LICENSE","2","UNAVAILABLE","The IOS license storage on this device was not recovered in this device, UDI=%s","The IOS license storage on this device was not recovered","If this error message occurs, please reinstall all the licenses."
"LICENSE","2","UNAVAILABLE","The IOS license storage on this device was not recovered. UDI=%s","The IOS license storage on this device was not recovered","If this error message occurs, please reinstall all the licenses."
"LICENSE","3","FEATURE_INCONSISTENT","License mismatch for feature %s %s: Active has %s and standby has %s","HAWKEYE log message.","No action required."
"LICENSE","3","UNAVAILABLE","%s","The IOS licensing subsystem encountered an error while initializing/handling the implicit licenses","If this error message recurs, please copy the message and and contact the customer service"
"LICENSE","3","UNAVAILABLE","%s","The IOS licensing subsystem was unable to create a process","If this error message recurs, please copy the message and and contact the customer service, See whether the system resourcesare available"
"LICENSE","3","UNAVAILABLE","%s","The ios licensing subsystem encountered an error while initializing/handling the implicit licenses","If this error message recurs, please copy the message and and contact the customer service"
"LICENSE","3","UNAVAILABLE","%s","The ios licensing subsystem was unable to create a process","If this error message recurs, please copy the message and and contact the customer service, See whether the system resourcesare available"
"LICENSE","3","UNAVAILABLE","%s%s %x rc:%s","Licensing is experiencing errors when communicating to Line Cards using IPC","Show ipc ports. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LICENSE","3","UNAVAILABLE","%s, error:%d","Licensing is experiencing ISSU Errors","Show ipc ports. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LICENSE","3","UNAVAILABLE","Client id:%d MTU failed, error:%d","Licensing is experiencing Errors when performing ISSU GET MTU during a transmit operation","Show issu negotiations. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LICENSE","3","UNAVAILABLE","Client id:%d type = %d receive failed, error:%d","Licensing is experiencing Errors when performing ISSU Transformation during a receive operation","Show ipc ports. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LICENSE","3","UNAVAILABLE","Client id:%d, type = %d xmit failed, error:%d","Licensing is experiencing errors when performing ISSU Transformation during a transmit operation","Show ipc ports. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LICENSE","3","UNAVAILABLE","License %s IPC port %s failed: %s","License IPC port could not be created. The reason for failureis displayed after :","If this error message recurs, please copy the message and and contact the customer service, See whether the system resourcesare available"
"LICENSE","3","UNAVAILABLE","License Slave device registration failed : %s","License Slave registration failed. The reason for failureis displayed after :","If this error message recurs, please copy the message and and contact the customer service, See whether the system resourcesare available"
"LICENSE","3","UNAVAILABLE","License Slave device registration failed : %s","License Slave registration failed. The reason for failureis displayed after :","If this error message recurs, please copy the message and and contact the customer service, See whether the system resourcesare available."
"LICENSE","4","UNAVAILABLE","Expired license is loaded for feature: %s %s in this device, UDI=%s, StoreIndex=%s","An expired license is loaded or installed in the system","If you are seeing this message,please buy and install a license for this featureif you plan to use the feature."
"LICENSE","4","UNAVAILABLE","Expired license is loaded for feature: %s %s. UDI=%s; StoreIndex=%s","An expired license is loaded or installed in the system","If you are seeing this message,please buy and install a license for this featureif you plan to use the feature."
"LICENSE","4","UNAVAILABLE","License Agent is turned off. UDI=%s","The License Agent on this device is not running","Please check the device configuration if you need to enable it."
"LICENSE","4","UNAVAILABLE","License for feature %s %s will expire in %s UDI=%s","License for the feature specified will expire in the specified time.","If this message recurs, customer should buy license for the feature from Cisco since feature will not run after license expiry"
"LICENSE","4","UNAVAILABLE","Setting precedence for feature %s failed with error : %d","Setting precedence for a grace period license failed. This will causecustomer to use wrong license for the same feature","If this error message recurs, please copy the message and and contact the customer service"
"LICENSE","4","UNAVAILABLE","The source license udi(%s:%s) differs from the platform udi(%s:%s), please save the running config.","The source license udi mismatches with the platform udi","Please save running-config."
"LICENSE","6","UNAVAILABLE","EULA for feature %s %s has been accepted in this device, UDI=%s, StoreIndex=%s","End User License Agreement was accepted on this device","none"
"LICENSE","6","UNAVAILABLE","EULA for feature %s %s has been accepted. UDI=%s; StoreIndex=%s","End User License Agreement was accepted on this device","none"
"LICENSE","6","UNAVAILABLE","Feature %s %s count violation - count = %d, usage count = %d.","The feature's count is less than the current usage count","This is just an informational message todenote count change for particular feature"
"LICENSE","6","UNAVAILABLE","Feature %s %s license count changed from %d to %d.","The feature's maximum licensable count has changed","This is just an informational message todenote count change for particular feature"
"LICENSE","6","UNAVAILABLE","Feature %s %s was installed in this device, UDI=%s, StoreIndex=%s","Feature was installed on this device","none"
"LICENSE","6","UNAVAILABLE","Feature %s %s was installed in this device. UDI=%s; StoreIndex=%s","Feature was installed on this device","none"
"LICENSE","6","UNAVAILABLE","Feature %s %s was removed from this device, UDI=%s, StoreIndex=%s","Feature was removed from this device","none"
"LICENSE","6","UNAVAILABLE","Feature %s %s was removed from this device. UDI=%s; StoreIndex=%s","Feature was removed from this device","none"
"LICENSE","6","UNAVAILABLE","License for feature %s %s has been annotated, UDI=%s, StoreIndex=%s, Comment=%s","Feature was annotated on this device","none"
"LICENSE","6","UNAVAILABLE","License for feature %s %s has been annotated. UDI=%s; StoreIndex=%s; Comment=%s","Feature was annotated on this device","none"
"LICENSE","6","UNAVAILABLE","License for feature %s %s has been revoked in this device, UDI=%s, StoreIndex=%s","A license is revoked from the system","This is just an informational message to log a message when a license has been revoked"
"LICENSE","6","UNAVAILABLE","License for feature %s %s has been revoked. UDI=%s; StoreIndex=%s","A license is revoked from the system","This is just an informational message to log a message when a license has been revoked"
"LICENSE","6","UNAVAILABLE","The IOS license storage on this device was recovered in this device, UDI=%s","The IOS license storage on this device was recovered","none"
"LICENSE","6","UNAVAILABLE","The IOS license storage on this device was recovered. UDI=%s","The IOS license storage on this device was recovered","none"
"LIC_AGENT","3","MEMORY","%s","License Agent subsystem has experienced a problem gettting the required memory to complete this operation.","Check system memory for other memory allocation errors and contact Technical support for problem resolution. In the absence of IOS errors upgrading the memory in the network device may be required."
"LIC_AGENT","3","UNAVAILABLE","event %d, %s","License Agent tried to execute an unknown event.","Contact technical support for problem resolution."
"LINEPROTO-SP","5","UPDOWN","Line protocol on Interface %s, changed state to %s","The data link level line protocol changed state.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LINK","0","UNAVAILABLE","Fatal reentrancy, level=%d, intfc=%s","An internal software error occurred. The system code tried to access a critical data structure which was already in use.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LINK","2","UNAVAILABLE","In critical region with interrupt level=%d, intfc=%s","An internal software error occurred. The high-level system code tried to call this routine with interrupts enabled.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LINK","2","UNAVAILABLE","Interface %s, undefined entry point","An internal software error occurred. The high-level system code tried to use an unimplemented entry point with the virtual interface descriptor block (IDB) driver.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LINK","2","UNAVAILABLE","No linestate vector for %s","An internal software inconsistency occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LINK","2","UNAVAILABLE","Source idb not set","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LINK","3","BOGUSENCAP","Interface [chars], bad encapsulation in idb-enctype = [hex]","A serial interface has been configured with an unknown encapsulation.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"LINK","3","FCS_ERROR","[chars] [chars] [chars] [chars]","The FCS error rate exceeds the configured threshold.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LINK","3","LINK_FAULT","[chars] [chars] [chars] [chars]","The link state for the port is down.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LINK","3","TOOSMALL","Interface [chars], Output runt packet of [dec] bytes","An output packet was detected that was smaller than the minimum allowable datagram size. An error in another driver or an error in the system software probably triggered this error message.","This is an informational message only. No action is required."
"LINK","3","UPDOWN","Interface [chars], changed state to [chars]","The interface hardware has gone either up or down.","If the state change was unexpected, confirm the configuration settings for the interface."
"LINK","4","UNAVAILABLE","A random default MAC address of %e has been chosen. Ensure that this address is unique, or specify MAC addresses for commands (such as 'novell routing') that allow the use of this address as a default.","An addressing inconsistency occurred.","Make sure that this address is unique, or specify MAC addresses for commands such as novell routing that allow the use of this address as a default."
"LINK","4","UNAVAILABLE","Interface %s, FDDI state %s detected","There was a state change on the FDDI ring.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LINK","4","UNAVAILABLE","Interface %s, Output packet size of %d bytes too big","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LINK","4","UNAVAILABLE","Interface %s, bad output queue ID specified (%d). Packet dropped","This message indicates an internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LINK","4","UNAVAILABLE","Interface %s, encapsulated BPDU recvd from %e","An FCIT running in nonencapsulating transparent mode detected an FDDI bridge running in encapsulation mode on the same fiber. This is an unstable situation and should be corrected. The incoming interface is displayed, along with the FDDI MAC address in standard form.","Upgrade the errant interface to full transparent mode. Copy the error message exactly as it appears, and report it to your Cisco technical support representative."
"LINK","4","UNAVAILABLE","SSB deleted with timer running","An internal software error occurred. Problem has been corrected, and router operation has not been impaired.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LINK","5","UNAVAILABLE","%s address %i, resolved by %i","An interface's IP address was successfully learned dynamically through BootP. The first address is the learned IP address. The second IP address is the IP address of the BootP server that provided the information.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LINK","5","UNAVAILABLE","%s address %i, resolved by %i","The Reverse Address Resolution Protocol (RARP) resolved an IP address.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LINK","5","UNAVAILABLE","%s address %i, resolved by %i","The Serial Line Address Resolution Protocol (SLARP) resolved an IP address.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LINK","5","UNAVAILABLE","Interface %s, %s","The interface entered or exited loopback.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LINK","5","UNAVAILABLE","Interface %s, changed state to %s","The interface hardware changed state.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LINK","5","UNAVAILABLE","Interface %s, remote loop %s %s","The interface entered or exited a remote loopback.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LINK","6","UNAVAILABLE","%s","BERT related information messages.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LINK","6","UNAVAILABLE","Interface %s, %s","BERT is completed for this interface.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LLC","2","UNAVAILABLE","LLC2: %s UNEXPECTED EVENT","An internal software error was found. A software component is trying to use LLC2 structures that do not exist.","Record the configuration and any information that would be useful in recreating the error and call your technical support representative."
"LINK-SP","3","UPDOWN","Interface %s, changed state to %s","The interface hardware went either up or down.","If the state change was unexpected, confirm the configuration settings for the interface."
"LISP","3","NO_MAP_REQUEST_SOURCE","Local map request source address not available for %s%s.","No map request source address is available, meaning the router cannot send any map requests.","Contact your Cisco service representative to diagnose the root cause. In the mean time adding the following command under router lisp will likely provide a workaround. {ipv4|ipv6} map-request-source ."
"LISP","4","ASSERT","Internal LISP error (%s)%s","LISP control plane code execution encountered an unexpected condition.","Issue the show {ip | ipv6} lisp database command and look for routing locators marked as missing. Configure the missing routing locators for the remaining local EID prefixes. If a routing locatormust not be used for inbound traffic to a local EID prefix then a priority of 255 can be specified."
"LISP","4","CEF_DISABLED","Disabling %s CEF will impact configured LISP functionality.","CEF has been disabled whilst LISP has configuration which depends on CEF being enabled.","Re-enable CEF using the command {ip|ipv6} cef [distributed]."
"LISP","4","LOCAL_EID_NO_ROUTE","No route to local EID database prefix %s.","There is no RIB route that covers or is a more specific of the configured local EID database prefix. This means that the ETR will not be able to forward decapsulated packets to their destination.","Check the network connectivity and routing configuration within the LISP site and re-establish a route to destinations covered by the configured EID prefix."
"LISP","4","LOCAL_EID_RLOC_INCONSISTENCY","Inconsistent LISP routing locator configuration detected in the local EID database for instance-ID %u %s address family.","All the LISP local EID prefixes for an address family must be configured with the same set of routing locators. LISP detected that there are routing locators configured on some local EID prefixes and not on other local EID prefixes of the same address family.","Issue the show {ip | ipv6} lisp database command and look for routing locators marked as missing. Configure the missing routing locators for the remaining local EID prefixes. If a routing locatormust not be used for inbound traffic to a local EID prefix then a priority of 255 can be specified."
"LISP","4","SITE_XTR_RLOC_INCONSISTENCY","%s RLOC %s in EID database configuration in record for %s from %s.","While probing other xTRs in our own site we received a map reply mapping record listing a different set of locators than those we have configured in database commands.","Issue the show {ip | ipv6} lisp database command on both this xTR and the other site xTR that sent us the map reply to locate the mis-configuration. Add or remove locators in the config of one or both xTRs to make them have the same list of configured locators."
"LISP","4","UNSUPPORTED_LOCAL_RLOC","This platform does not support local %s RLOCs, %s will be marked as down.","The platform has indicated it does not support local RLOCs of this address family.","Deconfigure the RLOC, or move it to another xTR at the site which does not have this platform limitation."
"LLDP","4","LLDP_NEW_ENTRY","Neighbor record not committed - malloc failure","An LLDP entry creation failed due to a memory allocation failure.","Run memory diagnostics."
"LLIST","3","UNAVAILABLE","%s from 0x%x, 0x%x not on list","An internal inconsistency was detected when an attempt was made to remove an item from a list not on the list.","Copy the message exactly as it appears and report it to your technical service representative."
"LLIST","3","UNAVAILABLE","%s to 0x%x, 0x%x on list","An internal inconsistency was detected when an attempt was made to add an item to a list already on the list.","Copy the message exactly as it appears and report it to your technical service representative."
"LNMC","3","UNAVAILABLE","%s Bad clsi SAP id = %x %s","A LAN network manager system error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LNMC","3","UNAVAILABLE","%s Bad data len = %d %s","A LAN network manager system error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LNMC","3","UNAVAILABLE","%s Bad header len = 0x%x %s","A LAN network manager system error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LNMC","3","UNAVAILABLE","%s Invalid ID type = 0x%x %s","A LAN network manager system error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs._ERR"
"LNMC","3","UNAVAILABLE","%s Invalid confirm %s %s","A LAN network manager system error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LNMC","3","UNAVAILABLE","%s Invalid indication %s, %s","A LAN network manager system error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LNMC","3","UNAVAILABLE","%s Invalid primitive type = 0x%x %s","A LAN network manager system error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LNMC","3","UNAVAILABLE","%s Invalid ret code (0x%x) %s, %s","A LAN network manager system error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LNMC","3","UNAVAILABLE","%s primitive not valid for lnm %s %s","A LAN network manager system error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LOGIN","3","UNAVAILABLE","Too many Login Authentication failures have occurred in the last one minute on the line %d.","A large number of authentication failures (greater than the configured limit) have occurred in the last one minute interval. It might indicate an attempt to gain unauthorized access to the device.","Make sure it is not by any malicious attempt to gain access to the device."
"LPD","3","UNAVAILABLE","Line %t, packet has too many newlines to convert","An internal buffer did not have enough room to add all the necessary carriage returns to a packet of LPD data destined for a printer configured with a newline-convert command. This message is unlikely to occur with a file containing valid data.","Check the file being printed to see whether it contains valid, printable data."
"LRE_CPE","3","INVALIDMODE","CPE on interface [chars] is in invalid mode [chars].","The CPE is in an inconsistent mode; for example, the model number may imply a MAC mode while the CPE is in a PHY mode.","Enter the show controllers lre cpe mfg command to verify that the CPE model number string is correct. Enter the hw-module slot slot lre upgrade remote command to ensure that the CPE has the latest supported firmware. If the CPE's model number and firmware are correct, enter the interface configuration shutdown command followed by the no shutdown command to force the switch to read the CPE information again. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LRE_CPE","3","INVALIDPATCH","CPE on interface [chars] has invalid LRE firmware.","The LRE firmware header does not have a valid signature, or the header information on the specified firmware is inconsistent with the contents of the firmware","Upgrade the firmware on the CPE to the latest supported one by using the hw-module slot slot lre upgrade remote command."
"LRE_CPE","3","INVALIDPHY","CPE on interface [chars] has an unsupported Ethernet PHY.","The Ethernet PHY device on the CPE attached to the specified interface is not supported. This error occurs when the switch cannot recognize the PHY identifier of the PHY device(s) on the CPE. The reason could be one of the following: The Cisco IOS version running on the switch is not compatible with this CPE, the CPE is not supported by Cisco, or the switch did not correctly read the PHY identifier from the CPE.","Verify that the CPE is supported by Cisco. Enter the command show controllers lre cpe mfg to verify that the CPE model number string is correctly set. If the Cisco IOS version and CPE model number look correct, enter the interface configuration shutdown command followed by the no shutdown command to force the switch to read the PHY identifer again. As a last resort, power cycle the CPE. If the error persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LRE_CPE","3","NOVERCKSUM","Could not fetch CPE firmware version and checksum on interface [chars].","The system could not obtain the CPE firmware version and checksum. If the CPE has the latest firmware, and the CPE model number is correct, the most likely cause for this error is that the LRE link between the switch and the CPE is of poor quality.","Enter the command show controllers lre cpe mfg to verify that the CPE model number string is correctly set for this CPE. Enter the hw-module slot slot lre upgrade remote command to ensure that the CPE has the latest supported firmware. Enter the interface configuration shutdown command followed by the no shutdown command to force the switch to read the CPE firmware version and checksum. As a last resort, power cycle the CPE. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LRE_CPE","3","UNKNOWNMODEL","CPE has unrecognizable model number [chars] on interface [chars]","The model number string in the CPE does not match a known CPE model number.","Enter the command show controllers lre cpe mfg to examine the model number of the CPE. Verify that the model number is supported by Cisco. Enter the interface configuration shutdown command followed by the no shutdown command to force the switch to read the CPE model number again. If the error message persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LRE_CPE","3","WRONGAPPVER","CPE on interface [chars] reported unsupported version of application firmware [chars]. Minimum application firmware version needed [chars]","Each CPE requires a currently supported application firmware version for it to function correctly. This CPE has a application firmware version that predates the earliest supported version.","Application firmware is not currently used on the CPE. This error message is for future use."
"LRE_CPE","3","WRONGBOOTVER","CPE on interface [chars] reported unsupported version of bootloader firmware [chars]. Minimum bootloader firmware version needed [chars]","Each CPE requires a currently supported bootloader firmware version for it to function correctly. This CPE has a bootloader firmware version that predates the earliest supported version.","Enter the hw-module slot slot lre upgrade remote command to upgrade the bootloader firmware on the CPE to a recent version that supports the current requirements. If the CPE firmware upgrade does not solve the problem, enter the interface configuration shutdown command followed by the no shutdown command to force the switch to read the bootloader firmware version again. As a last resort power cycle the CPE. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LRE_CPE","3","WRONGPATCH","CPE on interface [chars] has wrong patch version [hex]. Patch version [hex] or higher is needed for this CPE.","Each CPE requires a currently supported patch version for it to function. This CPE has a patch version that predates the earliest supported version. This condition might occur because the switch was upgraded with the latest Cisco IOS software image, but the CPE firmware has not been upgraded.","Enter the hw-module slot slot lre upgrade remote command to upgrade the patch on the CPE to the latest supported version."
"LRE_CPE","5","SSNCHANGED","CPE unit on interface [chars] changed.","The CPE system serial number has changed. This condition usually means that the CPE unit on this interface was replaced.","No action is required."
"LRE_LINK","3","PROFILE_FAILURE","Interface [chars], profile [chars] failure","The interface specified in the error message did not achieve link with the attached profile.","If the link failure was unexpected, confirm the profile settings for the interface."
"LRE_LINK","3","UPDOWN","Interface [chars], changed state to [chars]","The interface hardware has either become active (came up) or become inactive (gone down).","If the state change was unexpected, confirm the configuration settings for the interface."
"LRE_LINK","4","HEALTH_MON","Interface [chars], had crossed certain monitored thresholds","The link status monitor for the specified interface has detected conditions that have crossed the configured thresholds.","Enter the show controllers lre link monitor command "
"LRE_LOG","7","LRE_LOGGING","LRE Log:Interface [chars]: State: [chars], Event: [chars], Data: [chars].","The system has changed its state. The error message text provides more information on the cause of the change.","No action is required."
"LRE_UPGRADE","2","LOCAL_LOAD_FAILURE","The system failed to load the firmware for local PHY controller:[dec]","An internal system error has occurred while loading the firmware for a local PHY controller.","Power cycle the switch. If this message persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LRE_UPGRADE","3","INIT_SYSTEM","Upgrade module failed to initialize","The LRE upgrade module failed to initialize.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LRE_UPGRADE","3","LOCAL_FAILURE","Upgrade of local controller [chars] failed","The LRE upgrade is unable to download firmware to a local controller.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LRE_UPGRADE","4","INIT_RESOURCE","[chars]","The LRE upgrade module cannot locate a required resource.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LRE_UPGRADE","4","TERMINATE","Upgrade on [chars] terminated","The customer equipment was disconnected or changed in the middle of an upgrade.","No action is required."
"LS1010_CCM","2","UNAVAILABLE","%s","The LS1010 TSCAM S/W subsystem encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter OUTPUT_INTERPRETER . Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit BUG_TOOLKIT . If you still require assistance, open a case with the Technical Assistance Center via the Internet TAC_CASE_OPEN , or contact your Cisco technical support representative and provide the representative with the gathered information. on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter OUTPUT_INTERPRETER . Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit BUG_TOOLKIT . If you still require assistance, open a case with the Technical Assistance Center via the Internet TAC_CASE_OPEN , or contact your Cisco technical support representative and provide the representative with the gathered information. error using the Output Interpreter OUTPUT_INTERPRETER . Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit BUG_TOOLKIT . If you still require assistance, open a case with the Technical Assistance Center via the Internet TAC_CASE_OPEN , or contact your Cisco technical support representative and provide the representative with the gathered information."
"LS1010_CCM","3","UNAVAILABLE","%s","The LS1010 TSCAM S/W subsystem encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter OUTPUT_INTERPRETER . Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit BUG_TOOLKIT . If you still require assistance, open a case with the Technical Assistance Center via the Internet TAC_CASE_OPEN , or contact your Cisco technical support representative and provide the representative with the gathered information. on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter OUTPUT_INTERPRETER . Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit BUG_TOOLKIT . If you still require assistance, open a case with the Technical Assistance Center via the Internet TAC_CASE_OPEN , or contact your Cisco technical support representative and provide the representative with the gathered information. error using the Output Interpreter OUTPUT_INTERPRETER . Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit BUG_TOOLKIT . If you still require assistance, open a case with the Technical Assistance Center via the Internet TAC_CASE_OPEN , or contact your Cisco technical support representative and provide the representative with the gathered information."
"LS1010_CCM","4","UNAVAILABLE","%s","The LS1010 TSCAM S/W subsystem encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter OUTPUT_INTERPRETER . Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit BUG_TOOLKIT . If you still require assistance, open a case with the Technical Assistance Center via the Internet TAC_CASE_OPEN , or contact your Cisco technical support representative and provide the representative with the gathered information. on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter OUTPUT_INTERPRETER . Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit BUG_TOOLKIT . If you still require assistance, open a case with the Technical Assistance Center via the Internet TAC_CASE_OPEN , or contact your Cisco technical support representative and provide the representative with the gathered information. error using the Output Interpreter OUTPUT_INTERPRETER . Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit BUG_TOOLKIT . If you still require assistance, open a case with the Technical Assistance Center via the Internet TAC_CASE_OPEN , or contact your Cisco technical support representative and provide the representative with the gathered information."
"LSD","2","APP_NOTSUPP","[chars] interface does not support app [chars]","The interface does not support the application that is specified in the message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSD","2","AVL","[chars] [hex]","An error involving an Adelson-Velskii and Landis (AVL) tree operation has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSD","2","FPIHANDLER","[chars] [hex]","An error involving the FPI handler has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSD","2","INVALID_VAR","[chars]","The function has received invalid parameters.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSD","2","INVALID_VAR2","[chars] [hex] [hex]","The function has received invalid parameters.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSD","2","RESOURCE","[chars]","A system resource error has occurred.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"LSD","2","TESTAPP2","Test app error: [chars]: [hex] [hex]","A test application error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSD","3","APPMGR","[chars] [hex]","An error involving the application manager has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSD","3","BADEXEC","Unexpected Code Execution: [chars] [dec]","An error involving unexpected execution of code has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSD","3","CHUNKMGR","chunk mgr: [chars] [hex]","A memory manager error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSD","3","CLIENT_CONN","[chars]","A client connection error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSD","3","CLIENT_CONN2","[chars] [hex] [hex]","A client connection error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSD","3","EVTLOGBADSOURCE","Illegal log event source: [dec]","An illegal event was found in the log buffer.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSD","3","INTF_DB","[chars]","An interface database error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSD","3","INTF_DB2","[chars] [hex] [hex]","An interface database error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSD","3","INVALID_PROC_EVT","Unexpected process event [dec] for pid [dec]","The LSD component received an unexpected process event notification for the process with the specified ID.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSD","3","LABEL","[chars][dec]","A label operation error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSD","3","LABEL2","[chars] [hex] [hex]","A label operation error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSD","3","MULTISERVICEREQ","Multiple outstanding service requests: [dec] [dec]","A service request was submitted, but one service request is already outstanding.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSD","3","OS_NOTIFY","Process id [dec] [chars], error code [dec]","The LSD was unable to notify the operating system about (un)registration of the specified process.","Enter the show version, show running-config, show mpls infrastructure lsd apps commands. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSD","3","REWMGR","Rewrite Manager: [chars] [hex]","An error involving the rewrite manager has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSD","3","REWMGR2","[chars] [hex] [hex]","An attempt to look up a rewrite has failed because of an inconsistency in a forwarding path identifier.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSD","3","UPDATELISTMGR2","[chars] [dec] [dec]","A general error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSD","3","UPDATELISTMGREXEC","Illegal exec: [chars] [hex]","An error involving illegal execution of code has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSD","4","BADAPI","[chars] from [chars]","The LSD has received a message with invalid parameters.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSD","4","LABELFREETO","requested free timeout ([int] ms) by [chars] limited to: [int] ms","The timeout period for the MPLS application label has exceeded the maximum configured time.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSD","4","LABEL_RESOURCE","label range [dec]-[dec] exhausted","The MPLS application is attempting to allocate more labels than the system configuration will allow.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSD_CLIENT","2","MSGHANDLERERR","Client=[dec] Msg type=[dec] Error=[chars]","An error involving the message handler has occurred.","Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show running-config commands and your pertinent troubleshooting logs."
"LSD_CLIENT","2","XDREXEC","[chars] [dec]","Illegal code has been executed in the XDR path.","Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show running-config commands and your pertinent troubleshooting logs."
"LSD_CLIENT","2","XDREXEC2","[chars] [hex] [hex]","llegal code has been executed in the XDR path.","Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show running-config commands and your pertinent troubleshooting logs."
"LSD_CLIENT","3","CLIENTAPI","Client API error: [chars] [dec]","An unexpected client API error has occurred.","Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show running-config commands and your pertinent troubleshooting logs."
"LSD_CLIENT","3","INVALID_VAR","[chars]","A function has received parameters that are invalid.","Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show running-config commands and your pertinent troubleshooting logs."
"LSD_CLIENT","3","ISSU_MSG_CONV","[chars] [dec] [dec]","Could not convert received message type to a known message.","Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show running-config commands and your pertinent troubleshooting logs."
"LSD_CLIENT","3","PCHUNK2","[chars]: [chars] [hex] [hex]","An error involving memory parameters has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show version, show running-config and show process memory commands and your pertinent troubleshooting logs."
"LSD_CLIENT","3","UTIL2","[chars]: [hex] [hex]","An error involving utilities has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show version and show running-config commands and your pertinent troubleshooting logs."
"LSD_HA","2","CF","[chars][dec]","A CF-related error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSD_HA","2","RESOURCE","[chars]","A system resource error has occurred.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"LSD_HA","2","RF","[chars][dec]","An RF-related error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSD_HA","3","GENERAL","[chars]","A function has received invalid parameters.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSD_HA","3","INVALID_VAR","[chars]","A function has received invalid parameters.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSD_HA","3","LABEL_RANGE_DB","[chars]","An error has occurred in the label range database.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSD_HA","3","UNSENT_MSG_DB","[chars]","An error has occurred in the unsent message database.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSPV","3","COMM","[chars]: [hex] [hex]","An unexpected RP/LC XDR condition has been encountered in the communications module.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSPV","3","COMM_UNKNOWN_RC","Unexpected oce return code","An unexpected OCE return code was encountered in the communications module.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"LSS","1","UNAVAILABLE","%s %s","LSS SDM Alert - protocol region reached limit. Cannot accept anymore entries. Need to reconfigure protocol regions, and reload","Reconfigure SDM region sizes and reload."
"LSS","3","UNAVAILABLE","Conn empty detected %s. This port has had conn empty problems %d times since last boot","Informational","If portstuck reload is not enabled, manually reload the interface or OIR the card."
"LSS","3","UNAVAILABLE","Interface %s is portstuck This port has stuck %d times since last boot.","Informational","If portstuck reload is not enabled, manually reload the interface or OIR the card"
"LSS","4","UNAVAILABLE","******************************************************** ATM Router Module(ARM) not supported with ASP hardware version less than 6.0. Please upgrade ASP hardware version to atleast 6.0 with FC-PFQ feature card. ATM Router Module(ARM) in slot %d is not operational . ********************************************************","Cat8510 ASP hardware with version less than 6.0 doesnot support ATM Router Modules(ARM)","Upgrade ASP hardware version to atleast 6.0 with FC-PFQ card."
"LSS","4","UNAVAILABLE","%s %d","LSIPC warning - LSIPC is timing out. uCode on that interface may not be responding","Possibly E-PAM is not responding"
"LSS","4","UNAVAILABLE","%s %d","MAC Learn/Age IPC warning - MAC Learn or Age IPC dropped. The IOS bridge table and the L2 Cam entries are inconsistant","Do clear bridge"
"LTL","2","LTL_PARITY_CHECK","LTL parity check request for 0x%x.","The local target logic (LTL) parity check found a parity error on the index.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MAB","5","FAIL","Authentication failed for client (%s) on Interface %s","Authentication was unsuccessful.","No action is required."
"MAB","5","SUCCESS","Authentication successful for client (%s) on Interface %s","Authentication was successful.","No action is required."
"MACDB","3","ERROR","Internal error, %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MACDB","4","WARN","Internal warning, %s","An internal software warning occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MACDB","6","INFO","Internal info, %s","An internal software information message occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MAC_LIMIT","4","DROP","Vlan [dec] with Configured limit = [dec] has currently [dec] Entries","The number of entries for a VLAN has gone below or is equal to the allowed number.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MAC_LIMIT","4","ENFORCE","Enforcing limit on Vlan [dec] with Configured limit = [dec]","The number of entries for a VLAN has exceeded the allowed number. The action that enforces the limit is configured.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MAC_LIMIT","4","EXCEED","Vlan [dec] with Configured limit = [dec] has currently [dec] Entries","The number of entries for a VLAN has exceeded the allowed number.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MAC_LIMIT","4","PORT_DROP","[chars] with Configured limit [dec] has currently [dec] entries","The number of entries for the specified port has gone below or is equal to the permitted number.","This message is for reporting purposes only. No action is required."
"MAC_LIMIT","4","PORT_ENFORCE","Enforcing limit on [chars] with Configured limit [dec]","The number of entries for the specified port has exceeded the permitted number. The action to enforce the limit is configured.","This message is for reporting purposes only. No action is required."
"MAC_LIMIT","4","PORT_EXCEED","[chars] with configured limit [dec] has currently [dec] entries","The number of entries for the specified port has exceeded the permitted number.","This message is for reporting purposes only. No action is required."
"MAC_LIMIT","4","VLAN_DROP","Vlan [dec] with configured limit [dec] has currently [dec] entries","The number of entries for the specified VLAN has gone below or is equal to the permitted number.","This message is for reporting purposes only. No action is required."
"MAC_LIMIT","4","VLAN_ENFORCE","Enforcing limit on Vlan [dec] with configured limit [dec]","The number of entries for the specified VLAN has exceeded the permitted number. The action to enforce the limit is configured.","This message is for reporting purposes only. No action is required."
"MAC_LIMIT","4","VLAN_EXCEED","Vlan [dec] with configured limit [dec] has currently [dec] entries","The number of entries for the specified VLAN has exceeded the permitted number.","This message is for reporting purposes only. No action is required."
"MAC_MOVE","4","NOTIF","Host [enet] in vlan [dec] is flapping between port [chars] and port [chars]","The system found the specified host moving between the specified ports.","Examine the network for possible loops."
"MAILBOX","3","UNAVAILABLE","%s mailbox is offline. Interrupt ignored.","This message is generated when an attempt is made by the management module to communicate with an offline mailbox. When it appears, it indicates a problem exists between the perceived state of the mailbox from the router's side versus the management module's side.","Issue a system-wide reset on the management module. If the error persists, call your technical support representative for assistance."
"MAILBOX","3","UNAVAILABLE","Checksum failed. Expected = 0x%02x, calculated = 0x%02x. Ignoring PDU.","A hardware or software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"MAILBOX","3","UNAVAILABLE","Echo-request timed out. No response received. Mailbox offline.","An ECHO_RESPONSE was not received in the appropriate time after the generation of an ECHO_REQUEST. This failure only occurs during mailbox initialization, and indicates a problem between the communication path of the router module and its carrier card.","Confirm the router module installation. Make sure the software revision on the management module and the router module carrier card is up-to-date. If the error persists, call your technical support representative for assistance."
"MAILBOX","3","UNAVAILABLE","Echo-response did not match echo-request!","The data received from an ECHO_RESPONSE protocol data unit (PDU) did not match the original data provided in the ECHO_REQUEST. Usually, this message is seen during initialization, and indicates a catastrophic failure of the mailbox interface. See MAILBOX-3-INITFAIL for more information.","Confirm the router module installation. Make sure the software revision on the management module and the router module carrier card is up-to-date. If the error persists, call your technical support representative for assistance."
"MAILBOX","3","UNAVAILABLE","Intra-PDU timeout occurred on %s mailbox data.","A timeout occurred while sending or receiving the characters of a protocol data unit (PDU). The entire PDU will be ignored.","Informational message only. No action required"
"MAILBOX","3","UNAVAILABLE","Mailbox initialization failure. %s Mailbox offline.","A catastrophic failure involving the initialization of the administrative mailbox occurred. The mailbox will be taken offline and remain in that state until a router module reset, or a system reload, occurs At that time, initialization will again be attempted. Note that the functionality of the router, that is, it's ability to receive and forward packets, is not affected by this error.","Confirm the router module installation. Make sure the software revision on the management module and the router module carrier card is up-to-date. If the error persists, call your technicalsupport representative for assistance."
"MAILBOX","3","UNAVAILABLE","PDU of type %s received. Invalid or unsupported. Ignoring.","The protocol data unit (PDU) received was valid, but the type is not supported in the current software implementation. It will be ignored.","Informational message only. No action required."
"MAILBOX","6","UNAVAILABLE","Mailbox initialization successful.","This message is generated after a router reload to indicate the mailbox was successfully initialized.","Informational message only. No action required."
"MAILBOX","7","UNAVAILABLE","%s","This message header is paired with general debugging messages used to provide information about the functionality of the mailbox. To enable mailbox debugging, issue the command debug mailbox.","Advisory message only. No action required."
"MAILBOX","7","UNAVAILABLE","%s mailbox coming online.","This message is generated only when mailbox debugging is enabled. It provides information about the state of each incoming or outgoing mailbox.","Advisory message only. No action required."
"MAILBOX","7","UNAVAILABLE","Reading 0x%02x from carrier.","This message is generated only when mailbox debugging is enabled. It provides very low-level information about the incoming mailbox data stream.","Advisory message only. No action required."
"MAILBOX","7","UNAVAILABLE","Writing 0x%02x to carrier.","This message is generated only when mailbox debugging is enabled. It provides very low-level information about the outgoing mailbox data stream.","Advisory message only. No action required."
"MARINA","4","UNAVAILABLE","Unsupported flash type in the bootflash - %s.","The flash chips in the Flash SIMM is not supported by the platform.","Contact technical support to update your system."
"MBRI","1","UNAVAILABLE","%s %s failed","The MBRI network module failed to complete initialization.","Please make sure there is sufficient memory available in the router. If you continue to get this message, copy the error message exactly as it appears, and report it to your technical support representative."
"MBRI","1","UNAVAILABLE","%s could not get timer element","The requested operation could not be accomplished because a global pool of timer elements was empty. This may be due to a transient condition of certain system activity.","Copy the error message exactly as it appears, and report it to your technical support representative."
"MBRI","1","UNAVAILABLE","Port Adapter in bay %d, shutting down PA","The MBRI network module failed to complete initialization.","Please make sure there is sufficient memory available in the router. If you continue to get this message, copy the error message exactly as it appears, and report it to your technical support representative."
"MBRI","3","UNAVAILABLE","%s layer1 state is %d","The MBRI driver detected an invalid Layer 1 condition","Copy the error message exactly as it appears, and report it to your technical support representative."
"MBRI","3","UNAVAILABLE","Bay %d device ID seen as %#x, expected %#x","The network module hardware reports that a non-MBRI port module was detected","Copy the error message exactly as it appears, and report it to your technical support representative."
"MBUS","2","UNAVAILABLE","From %s agent in slot %d. %s","The interface to the MBUS agent firmware has gone deaf. This is a software bug.","Submit a bug with as much information as possible including the console output at the time of the error"
"MBUS","2","UNAVAILABLE","RAM version download to slot %d failed","The RAM version of the MBUS agent firmware could not be downloaded to specified slot. This may be a software or hardware bug.","Submit a bug with as much information as possible including the console output at the time of the error"
"MBUS","3","UNAVAILABLE","Message type %u to %u has length %u (exceeds %u)","Software called send_mbus_msg with a length greater than 254. This is a software bug.","Submit a bug with as much information as possible including the console output at the time of the error"
"MBUS","3","UNAVAILABLE","Status change message for register %x in slot %d, value = %x","The MBUS agent for the specified slot reported a status change for a register that is no longer being monitored.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MBUS","6","UNAVAILABLE","New state is '%s'","This is an informational message. The DSI changed state with respect to MBUS control and became either a master or a slave. In a dial shelf with just one DSI, it must always be a master.","None"
"MBUS_SYS","0","UNAVAILABLE","Failed to create registry %s %s","The specified registry could not be created. This is a catastrophic error for this feature. This needs a developer's intervention for a solution.","Copy the error message exactly as it appears, and report it to your technical support representative."
"MBUS_SYS","3","UNAVAILABLE","Error slot %d, stream %d %s","A reassembly error was detected for the given slot/stream combination. Either the slot/stream combination was incorrect (so it gave an invalid reassembly buffer index) or the first/last (or last few) packet(s) was/were lost. The message will be dropped which may cause errors for the application running over MBUS.","This condition should correct itself. No action is required."
"MBUS_SYS","3","UNAVAILABLE","Failed to allocate MBUS channel for over 10 secs","No MBUS channel could be allocated for sending messages. There is either very heavy MBUS traffic or there is a hardware problem. If there is temporary heavy traffic, the condition will clear itself. In case of hardware errors either the mbus agent has died or the hardware interface to the mailbox is not draining messages. Resetting the processor (including agent) may clear the problem. If the problem persists the card probably has hardware problems and needs diagnosis.","Power cycle the card. If problem persists the card probably has a hardware problem."
"MBUS_SYS","3","UNAVAILABLE","Failed to queue message from slot %d stream %d","Failed to enqueue a message from the interrupt for process level software. The message will be dropped. This points to a potential problem in the mbus process level message handling. This can occur if there are problems with the mbus process specifically or there maybe general IOS process related issues. This may also happen if the mbus process is not scheduled for extended periods of time and there is heavy MBUS traffic.","If this is a persistent problem, either the mbus process is dead or there are other IOS related problems. Consider rebooting the GRP if possible."
"MBUS_SYS","3","UNAVAILABLE","Failed to transmit MBUS message for over 10 secs","Message could not be transmitted since all the transmit buffers are full for ever 10 seconds. This may be a temporary problem if there is heavy MBUS traffic. Otherwise it is probably a hardware problem. Either the mbus agent is not responding or the hardware interface is not generating interrupts.","If this is a persistent problem power cycle the card. If the problem still continues it is likely to be a hardware problem and needs diagnosis."
"MBUS_SYS","3","UNAVAILABLE","MBUS invalid channel selected (dev=%u,type=%u,channel=%d,len=%u)","Software tried to send a message on a invalid MBUS channel.","Submit a bug with as much information as possible including the console output at the time of the error."
"MBUS_SYS","3","UNAVAILABLE","MBUS message length too big (dev=%u,type=%u,len=%u)","Software tried to send a message with a length greater than 254.","Submit a bug with as much information as possible including the console output at the time of the error."
"MBUS_SYS","3","UNAVAILABLE","Message from slot %d in stream %d dropped","Message from the slot was dropped as there were no MBUS buffers available. Either the messages are coming too fast or the process level message handling is not draining messages quickly enough.","This condition should correct itself. Check if the GRP is being inundated by messages from the chassis. If the condition persists, consider rebooting the GRP."
"MBUS_SYS","3","UNAVAILABLE","Message from slot %d stream %d of length %d  max message size %d","Message from a slot exceeded maximum message size and hence will be dropped. This should not happen during normal operations.","Verify health of MBUS using show mbus counters and the show mbus can-error commands. If any particular card shows errors and this condition persists, try reloading the card if possible. The error counts in the show mbus commands can be cleared using clear mbus-statistics."
"MBUS_SYS","3","UNAVAILABLE","Sequencing error (slot %d, stream %d): expected %d, received %d","An incorrect sequence number was detected in a multi packet message. This could happen if the source packetized the message incorrectly (unlikely) or one/more packets got dropped.","Check if there is excessive MBUS activity, copious printing from a line card etc. The command show mbus counters can provide lost message count."
"MBUS_SYS","3","UNAVAILABLE","Timeout on mbus request. Dest = %u, type = %u, addr = 0x%x","Failed to receive a response from a mbus request. This could be either a request for a eeprom field or a register read.","Copy the error message exactly as it appears, and report it to your technical support representative."
"MBUS_SYS","3","UNAVAILABLE","Unexpected response key = %u, current key = %u","Received an unexpected response to a read register or read eeprom.","Copy the error message exactly as it appears, and report it to your technical support representative."
"MC3810_DSX1","3","UNAVAILABLE","NULL","This message can take many forms. It provides information about a software error.","Copy the error message exactly as it appears, and report it to your technical support representative."
"MC3810_DSX1","5","UNAVAILABLE","NULL","Notification message.","LOG_STD_NO_ACTION"
"MCAST","2","IGMP_ADDRAL:IGMP","Address Aliasing for [chars]","The network management processor (NMP) detected a multicast data stream being directed to a special multicast address. Several special class D addresses are used exclusively for control purposes by the multicast protocols IGMP, DVMRP, MOSPF, and PIM. The sending of noncontrol packets to these addresses is considered address aliasing.","From the displayed MAC and IP address information, determine which device's IP address is being aliased. Change its IP address to an address outside of the special multicast address group, or do not use it for the multicast data feed."
"MCAST","2","IGMP_ADDRALDETAILS:IGMP","Multicast address aliasing: From [chars] ([IP_address]) on [dec]/[dec] to [chars]","The network management processor (NMP) detected a multicast data stream being directed to a special multicast address. Several special class D addresses are used exclusively for control purposes by the multicast protocols IGMP, DVMRP, MOSPF, and PIM. The sending of noncontrol packets to these addresses is considered address aliasing.","From the displayed group, port, and IP address information, determine which device's IP address is being aliased; [dec]/[dec] is the module number/port number. Change its IP address to an address outside of the special multicast address group, or do not use it for the multicast data feed."
"MCAST","2","IGMP_FALLBACK:IGMP","Running in FALL BACK mode","The network management processor (NMP) has detected excessive multicast traffic being directed to a special multicast address that should be used exclusively for control purposes. As a result, the NMP has entered fallback mode, in which it stops snooping packets with the specified destination MAC address. After 5 minutes the NMP will attempt to listen to these groups again. If it fails 3 times, the switch will move to fallback mode permanently. In fallback mode, only IGMP-based packets will be directed to the NMP, and router ports will be learned only from IGMP general query messages.","From the group and IP address information displayed by related system messages, determine which device's IP address is being aliased. Change its IP address to an address outside of the special multicast address group, or do not use it for the multicast data feed."
"MCAST","2","IGMP_SNOOP_DISABLE",',"IGMP snooping is disabled, but the system is receiving multicast traffic. This situation will force multicast packets to be directed to the route processor, possibly flooding it. IGMP snooping may have been disabled automatically due to excessive multicast traffic.","By capturing packets on the management VLAN (using a sniffer or SPAN), determine the source of the excessive multicast traffic and remove it."
"MCAST","3","GROUP_IP_INVALID","MCAST: Invalid group_ip in SSO sync msg for LTL type=[dec], index [hex]","A system error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCAST","3","IGMP_PKT_DROPPED:IGMP","IGMP Queue full (high packet rate/CPU busy), dropped [dec] packet(s) in last 5 minutes","The IGMP queue dropped one or more packets during the past five minutes either because the queue was full due to a high packet rate or because the CPU was too busy.","If the packet drops are few and infrequent, the drops may be caused by a transient condition, and no action is required. If many packets are being dropped, a multicast server might be flooding the switch, or some other process might be using excessive CPU resources."
"MCAST","3","PIMV2_PTCAM_LTL_ALL","PIMv2 PT_CAM LTL change to %s failed on all %s","While the system was executing an MPLS, router-guard, or PIM rate-limiter configuration command, communication with all line cards failed. As a result, the PIMv2 protocol redirection feature might not work properly.","Enter the MPLS, router-guard, or PIM rate-limiter command ([no] mpls ip or [no] router-guard ip multicast switchports or [no] mls rate-limit multicast ipv4 pim) again to cause the PIMv2 redirection local target logic (LTL) to be reprogrammed."
"MCAST","3","PIMV2_PTCAM_LTL_LC","PIMv2 PT_CAM LTL change to %s failed on linecard %d","While the system was executing an MPLS, router-guard or PIM rate-limiter configuration command, communication with one of the line cards failed. As a result, the PIMv2 protocol redirection feature might not work properly.","Enter the MPLS, router-guard, or PIM rate-limiter command ([no] mpls ip or [no] router-guard ip multicast switchports or [no] mls rate-limit multicast ipv4 pim) again to cause the PIMv2 redirection local target logic (LTL) to be reprogrammed."
"MCAST","3","PROT_RED_ALL","%s of %s redirection failed on all %s","While IGMP or PIMv2 snooping was being globally enabled or disabled, communication with all line cards failed. As a result, the protocol redirection feature might not work properly.","Disable and then enable IGMP or PIMv2 snooping globally, or vice versa, depending on whether the enable or disable form of the [no] ip [igmp | pim] snooping command was executed."
"MCAST","3","PROT_RED_LC","%s of %s redirection failed on linecard %d","While IGMP or PIMv2 snooping was being globally enabled or disabled, communication with one of the line cards failed. As a result, the protocol redirection feature might not work properly.","Disable and then enable IGMP or PIMv2 snooping globally, or vice versa, %MCASTRED-3-BAD_SYNC_TYPE depending on whether the enable or disable form of the [no] ip [igmp | pim] snooping command was executed."
"MCAST","3","QUERY_INT_MISMATCH","Snooping Querier received a non-matching query interval ([dec] msec), from querier address ([IP_address]) on VLAN([dec]).Configured query-interval ([dec] msec)","Mismatch of snooping query interval found between routers which can lead to querier flapping issues","Configure the same snooping query interval across all the active and redundat queriers in the VLAN."
"MCAST","4","LTL_FULL_VDB_CREATE_FAILED","Multicast Multi-Layer Switching: Failed to create VLAN ([dec]), hardware resource unavailable","The number of multicast MAC entries has exceeded the hardware limit. As a result, the VLAN will be software switched. This error also occurs when a larger number of VLANs are configured on a virtual switch.","Check the number of multicast MAC entries using the show mac-address-table multicast count command. Consider rearranging the network topology to reduce the multicast MAC count. Once multicast MAC entries fall below the hardware limit, unconfigure the VLAN using the no vlan command and reconfigure it."
"MCAST","4","RX_LVRANGE:IGMP","Rcvd Leave in the range [chars]","The switch received an IGMP leave message from a host for the group address in the specified range. This range is normally used for control packets and should not be used for general multicast data traffic.","No action is required if the frequency of the message is not affecting the operation of the switch. This message may indicate a malfunction of the multicast host device that sent it. To determine the identity of the multicast device, check for related system messages reporting details of the IGMP leave. Using the port information displayed by the related system messages, capture port traffic to determine the source of the IGMP leave message."
"MCAST","5","RX_IGMPLV:IGMP","Rcvd IGMP Leave [chars] on [dec]/[dec]","The switch has received an IGMP leave message for the group number on module number/port number; [chars] is the group number, and [dec]/[dec] is the module number/port number.","No action is required."
"MCAST","5","RX_IGMPREPORT:IGMP","Rcvd IGMP Report [chars] on [dec]/[dec]","The switch has received an IGMP report message for the group number on module number/port number; [chars] is the group number, and [dec]/[dec] is the module number/port number.","No action is required."
"MCAST","6","ADDRESS_ALIASING_FALLBACK","Address Aliasing detected for group %e on vlan %d from possible source ip %i source mac %e","Multicast packets with destination that aliases a special L2 entry can represent a possible denial of service attack and overwhelm the CPU, we need to take care of them","Remove from the L2 table the entry for which address aliasing was detected."
"MCAST","6","ADDRESS_ALIASING_NORMALMODE","Address Aliasing timer expired reinstalling entry for group %e on vlan %d","After a certain time dependent on the group we detected address aliasing for, we reinstall the corrispondent L2 entry","Reinstall in the L2 table the entry for which address aliasing was detected."
"MCAST","6","CGMP_JOININFO","CGMP: GDA %e USA %e","The system has received from the router a Cisco Group Management Protocol (CGMP) join message for the group destination address (GDA) for the host whose unicast source address (USA) is shown.","No action is required."
"MCAST","6","DELGDA","Deleting a GDA %e in vlan %d","A multicast entry in the specified VLAN is being deleted because an IGMP leave from the last host for this group destination address (GDA) was received.","No action is required."
"MCAST","6","ETRACK_LIMIT_EXCEEDED","[chars] snooping was trying to allocate more explicit-tracking entries than what allowed ([dec]","The allocation of explicit-tracking entries is limited to avoid the monopolizing of system resources by IGMP and MLD snooping.","Reduce the number of (s,g) channels or the number of receivers. When the explicit-tracking database has gone beyond its limit, new membership for any channels will not be tracked. This condition might cause high-leave latency when those members leave a channel. Another alternative is to increase the limit from configuration mode by entering the ip igmp snooping limit track max-entries command. It is important to note that increasing the value of max-entries could cause the system to fail because of high use of system resources."
"MCAST","6","ETRACK_STATS_LIMIT_EXCEEDED","Number of entries in %s snooping explicit-tracking statistics has exceeded the %s (%d)","The number of explicit-tracking statistics entries is bounded to avoid monopolizing of system resources by IGMP/MLD snooping. The explicit-tracking statistics database maximum size is set to the same as that of explicit-tracking limit. The statistics are split into two banks: permanent and volatile. The statistics entries will be stored permanently (volatile) until the permanent entries threshold is reached, after which the statistics will be stored temporarily up to the database maximum size. When the size of the database exceeds the permanent threshold, a group will be removed on receiving an IGMP/MLD leave. Groups can be removed whether they were installed above or below the permanent threshold. If the number of statistics entries grows beyond the maximum size of the database, then no statistics will be stored for any newly formed groups.","If the number of groups being used in the network exceeds the recommended value of the explicit-tracking database, you can increase the size of the database using the ip {igmp | mld} snooping limit track {0-128000} command. If the number of groups being used by hosts exceeds the recommended value of the explicit-tracking database, but the number of groups currently active is less than the database size and you require complete statistics, you can set the explicit-tracking limit to the maximum using the ip {igmp | mld} snooping limit track {0-128000} command. If you are interested only in statistics of the groups currently active in the system, you can clear the IGMP/MLD snooping statistics to free up space in the database. The following command can be used to clear snooping statistics: clear ip {igmp | mld} snooping statistics [interface [type slot/port | vlan x]]."
"MCAST","6","GC_LIMIT_EXCEEDED","%s snooping was trying to allocate more Layer 2 entries than what allowed (%lu)","The allocation of layer 2 entries is bounded to avoid the IGMP snooping hogs the system resources","Fewer IP groups must be sent, even because the groups that goes beyond the limit aren't learned from IGMP snooping. Another alternative is to set the limit from the config mode through the CLI 'ip igmp snooping l2-entry-limit '. Increasing the value of max-entries could create crash due to high use of system resources."
"MCAST","6","GLOBAL_CGMP_REDIRECT_NOT_INSTALLED","Global IGMP Snooping CGMP MAC Redirection not Installed, System cannot operate in IGMP_CGMP mode automatically","The global IGMP Snooping feature was unable to install the CGMP-MAC redirection. As a result, the system cannot automatically function in IGMP_CGMP mode when the CGMP-capable devices are in the network.","Enter the per-VLAN ip igmp snooping cgmp present command in all the VLANs that have one or more receivers through a CGMP-capable Layer 2 switch connected to this system."
"MCAST","6","IGMP_BADPKT","IGMP: No of Packets received with %s in last 5 minutes = %d","This message indicates that the switch received n IGMP packets with bad checksums in last 5 minutes","This message is provided for information only."
"MCAST","6","IGMP_CGMP_MODE","IGMP snooping now is running in IGMP_CGMP mode on vlan [dec]","The specified VLAN is running in IGMP/CGMP mode.","No action is required."
"MCAST","6","IGMP_ONLY_MODE","IGMP snooping now is running in IGMP_ONLY mode on vlan [dec]","The specified VLAN is running in IGMP mode.","No action is required."
"MCAST","6","IGMP_PKT_DROPPED","IGMP: IGMP Queue full (high packet rate/CPU busy), dropped [dec] packet(s) in last 5 minutes","The IGMP packet queue is not able to accommodate additional packets. Any additional packets will be dropped without processing.","Reduce the IGMP packet rate to prevent packets from being dropped."
"MCAST","6","IGMP_RATE_LIMIT_DISABLE","IGMP: enabling Snooping on Vlan([dec]), IGMP messages will not be rate limited","After throttling the IGMP messages on the VLAN for a certain period, snooping is reenabled after the user manually fixes the rate on the offending VLAN and reduces the CPU load.","No action is required."
"MCAST","6","IGMP_RATE_LIMIT_ENABLE","IGMP: Incoming IGMP message rate exceeded max threshold([dec] pps), disabling Snooping on Vlan([dec]) with Rate([dec] pps)","The incoming rate of IGMP messages exceeded the maximum configured threshold. Snooping will be disabled on all high-rate VLANs to lower the aggregate rate below the threshold on all remaining VLANs.","Ease the CPU load by reducing the rate of IGMP messages on all high-rate VLANs."
"MCAST","6","IGMPV3_BADPKT","IGMPV3: No of bad packets received (%s) = %d","The switch received the specified number of bad IGMP packets.","No action is required."
"MCAST","6","IGMPV3_EXCLUDE_RECORD","Received %d IGMP-V3 EXCLUDE Group Records with zero sources. Last received from","This message indicates the number of IGMPv3 EXCLUDE 0 reports that were received for groups in the source specific multicast (SSM) range.","No action is required."
"MCAST","3","IGMPV3_V1V2PKT","No of IGMP (%s) messages received in SSM Range = %d","The specified number of IGMP messages was received for groups in the source specific multicast (SSM) range.","No action is required."
"MCAST","6","IGMP_BADPKT","IGMP: No of Packets received with %s in last 5 minutes = %d","The switch received the specified number of IGMP packets with bad checksums during the previous five minutes.","No action is required."
"MCAST","3","IGMP_VLAN_SNOOP_ALL","%s of protocol redirection for vlan %d failed on all %s","While enabling or disabling IGMP snooping on the VLAN, communication with all line cards failed. As a result, the protocol redirection feature might not work properly for the VLAN.","Disable and then enable IGMP snooping on the VLAN, or vice versa, depending on whether the enable or disable form of the [no] ip igmp snooping command was executed."
"MCAST","3","IGMP_VLAN_SNOOP_LC","%s of protocol redirection for vlan %d failed on linecard %d","While enabling or disabling IGMP snooping on the VLAN, communication with one of the line cards failed. As a result, the protocol redirection feature might not work properly for the VLAN.","Disable and then enable IGMP snooping on the VLAN, or vice versa, depending on whether the enable or disable form of the [no] ip igmp snooping command was executed."
"MCAST","6","L2_HASH_BUCKET_COLLISION","Failure installing (G,C)->index: ([enet],[dec])->[hex] Protocol :[dec] Error:[dec]","A Layer 2 entry could not be installed in the hardware because there is not enough space in the hash bucket. Multicast packets will be flooded on the incoming VLAN because the Layer 2 entry installation failed.","No action is required."
"MCAST","6","LTL_HIGH_WATER_MARK","Number of free LTL indices in the system has reached above the low threshold ([dec])","The number of indices available in the system has increased above the low threshold. Snooping on the VLANs will resume.","No action is required."
"MCAST","6","LTL_LOW_WATER_MARK","Number of free LTL indices in the system has reached below the low threshold ([dec])","The number of indices available in the system has fallen below the low threshold. As a result, the multicast traffic on the VLANs will be flooded and snooping will be discontinued.","Check whether the system has many source-only entries. Use the remote command switch show mmls verbose gc gce,, Enforce a limit on the number of source only entries by using the command ip igmp snooping source-only-learning limit. This however would cause remaining source only entries to flood in the VLAN."
"MCAST","6","LTL_WATER_MARK","Number of free LTL indices in the system has reached above the low threshold (%d)","The number of local target logic (LTL) indices available in the system has exceeded the lower threshold, and snooping on the VLANs will resume.","No action is required, but you can enter the remote command switch show mmls mltl command to check multicast LTL resource usage."
"MCAST","6","MCAST_PROT_STATUS","%s Feature is %sabled","This message displays whether the Layer 2 multicast feature is enabled or disabled.","No action is required."
"MCAST","6","MCAST_RTRADD_PIM","Adding Router Port %d/%d in vlan %d - PIM message","The CGMP/IGMP has learned a new router port through a PIM message.","No action is required."
"MCAST","6","MCAST_RTRADD_PROT","Adding Router Port %d/%d in vlan %d","The CGMP/IGMP/MLD has learned a new router port.","No action is required."
"MCAST","6","MCAST_RTRADD_USERCFG","Adding Router Port %d/%d in vlan %d - User Configured","A user-configured multicast router port was added using the CLI.","No action is required."
"MCAST","6","MCAST_TOPOCHG","Recvd Topology Change Notification in vlan %d","The network management processor (NMP) received a topology change notification in a VLAN.","No action is required."
"MCAST","6","MLD_ADDRESS_ALIASING_FALLBACK","Address Aliasing detected for [enet] on vlan [dec] from possible src-ip[ipv6_addr] dst-ip[ipv6_addr] src-mac [enet]","Multicast packets with destinations that alias a special Layer 2 entry can indicate a possible denial-of-service attack and overwhelm the CPU.","Remove from the Layer 2 table the entry for which address aliasing was detected."
"MCAST","6","MLD_ADDRESS_ALIASING_NORMALMODE","Address Aliasing timer expired reinstalling entry for group [enet] on vlan [dec]","After a certain time (dependent on the group for which address aliasing was detected) the corresponding Layer 2 entry is reinstalled.","Reinstall in the Layer 2 table the entry for which address aliasing was detected"
"MCAST","6","MLD_RATE_LIMIT_DISABLE","MLD: enabling Snooping on Vlan([dec]), MLD messages will not be rate limited","After throttling the IGMP messages on the VLAN for a certain period, snooping is reenabled after the user manually fixes the rate on the offending VLAN and reduces the CPU load.","No action is required."
"MCAST","6","MLD_RATE_LIMIT_ENABLE","MLD: Incoming MLD message rate ([dec] pps) exceeded max threshold([dec] pps), disabling Snooping on Vlan([dec]) for [dec] secs","The incoming rate of MLD messages has exceeded the maximum configured threshold. Snooping will be disabled on all high rate VLANs to reduce the aggregate rate on all remaining VLAN to below the threshold.","Ease the CPU load by reducing the rate of MLD messages on all high-rate VLANs."
"MCAST","6","RGMP_JOIN","Rcvd RGMP Join Mesg %d/%d vlan %d for Group %i","The router has joined a multicast group.","No action is required."
"MCAST","6","RGMP_JOINRANGE","Rcvd RGMP Join Message in the range 01-00-5e-00-00-xx","The router sent a message for an invalid (reserved) address. The address 01-00-5e-00-00-xx cannot be used by the Router Port Group Management Protocol (RGMP).","No action is required."
"MCAST","6","RGMP_LEAVE","Rcvd RGMP Leave Mesg %d/%d vlan %d for Group %i","The router has left a multicast group.","No action is required."
"MCAST","6","RGMP_LVRANGE","Rcvd RGMP Leave Mesg in the range 01-00-5e-00-00-xx","The router sent a message for an invalid (reserved) address. The address 01-00-5e-00-00-xx cannot be used by RGMP.","No action is required."
"MCAST","6","RTRDEL_TIMEOUT","Deleting Router Port %d/%d in vlan %d - Timeout","The router port timer has timed out and the router port entry has been removed.","Determine whether a router is connected to the indicated port, and verify that IGMP is enabled."
"MCAST","6","RTRRGMP_BYE","Router Port %d/%d in vlan %d has become nonRGMP-capable","An RGMP router port has changed to a non-RGMP router port.","No action is required."
"MCAST","6","RTRRGMP_HELLO","Router Port %d/%d in vlan %d has become RGMP-capable","A router port has changed to a RGMP-capable port.","No action is required."
"MCAST","6","RTRRGMP_TIMEOUT","Router Port %d/%d in vlan %d has become RGMP-capable","The RGMP router has timed out and the port is no longer RGMP-capable.","No action is required."
"MCAST","6","RX_CGMPJN","Rcvd CGMP Join Mesg in vlan %d","A CGMP join message was received by a VLAN.","No action is required."
"MCAST","6","RX_CGMPLV","Rcvd CGMP Leave Mesg %d/%d vlan %d","A CGMP leave message was received on a VLAN port.","No action is required."
"MCAST","6","RX_IGMPLV","IGMP: Rcvd IGMP Leave %e on %d/%d","The switch received an IGMP leave message for the group number on module number/port number.","No action is required."
"MCAST","6","RX_IGMPREPORT","IGMP: Rcvd IGMP Report %e on %d/%d","The switch received an IGMP report message for the group number on module number/port number.","No action is required."
"MCAST","6","RX_JNRANGE","IGMP: Rcvd Report in the range of 01-00-5e-00-00-xx","The switch received an IGMP report from a host for the group address in the range of 01-00-5e-00-00-xx. This range is reserved for control packets and should not be used for general multicast data traffic.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCAST","6","RX_LVRANGE","IGMP: Rcvd Leave in the range of 01-00-5e-00-00-xx","The switch received an IGMP leave from a host for the group address in the range of 01-00-5e-00-00-xx. This range is reserved for control packets and should not be used for general multicast data traffic.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCAST","6","SOURCE_ONLY_LIMIT_EXCEEDED","[chars] snooping was trying to allocate more source only entries than allowed ([int])","Attempts by the IGMP snooping module to allocate source-only entries has exceeded the limit. This limit prevents the IGMP snooping module from consuming all of the system resources. Any IP groups sent in excess of the limit will not be learned by IGMP snooping.","Either reduce the number of IP groups sent or increase the limit by entering the ip igmp snooping source-only-learning limit max-entries command. Increasing the value of max-entries could cause a system failure due to the overuse of system resources."
"MCAST_MQC","3","CMAP_SDB_REGISTER","Error initialising class-map of type multicast-flows.","The system could not register the component related to the class map of type \n multicast-flows to the string database.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","ACKQMSG","Failed attempt to enqueue sync message type %u in confirmation queue","An attempt to link a new synchronization message into the synchronization message confirmation queue failed. This failure indicates corruption of the linkage within the queue. It is not possible to track message confirmation or to initiate a recovery action if confirmation is not received.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","ACKUNQMSG","Failed to remove sync request type %u from pending ACK queue","An attempt failed to unlink a completed synchronization request from the queue for requests awaiting confirmation of receipt from the standby route processor (RP). This failure indicates corruption of the linkage within the pending acknowledgement queue. False timeout error messages and memory leakage are likely. Loss of standby RP synchronization is possible.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","ALCSYNCTYP","Attempt to allocate sync request for invalid sync type %u","A function attempting to perform a synchronization operation has specified an invalid synchronization data type. No synchronization operation can be performed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","ALLOCMSG","Sync message buffer allocation failed for sync info type %u","An attempt to allocate a buffer for synchronization message transmission failed. Loss of synchronization on the standby route processor (RP) is likely.","Attempt standby RP synchronization by reloading the standby RP. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","ALLOC_CAP_TLV","Failed attempt to allocate memory for %s client capability TLV","The callback function responsible for creating an ISSU capability type length value (TLV) list was unable to allocate memory to hold the TLV list. Capability negotiation cannot proceed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","BAD_EVENT_TYPE","Defrd sync event type [dec] is invalid.","An invalid value was specified in a call to handle events which deferred sync elements are waiting for. The value is greater than PIM_SYNC_WAIT_FOR_EVENT_MAX.","This is a transient error. However, this condition indicates other errors in the software that will require further examination by your Cisco technical support representative. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","BAD_SYNC_TYPE","PIM sync type %d is invalid or too large.","In a call to modify an array indexed by the Protocol Independent Multicast (PIM) synchronization type, an out-of-bounds value was specified. The specified value exceeds either PIM_SYNC_TYPE_MAX or the length of the array.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","BLKNOBOOL","Failed to create %s watched boolean for bulk sync","An attempt to create a watched boolean to monitor bulk synchronization of state information to the standby route processor (RP) has failed. It is not possible to verify successful completion of the bulk synchronization operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","BLKNOFUNC","No bulk sync function defined for sync type %u","No function is defined for bulk synchronization of database information of this type. Some required information might not be synchronized to the standby RP.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","BULKRQTIME","Timeout sending bulk sync requests to standby","The maximum wait time has expired for transmission of enqueued bulk synchronization messages to the standby RP. Some required synchronization messages might not have been sent successfully.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","BULK_COMPLETE_INCOMPATIBLE","Skipping sending of bulk sync completion message to peer: Incompatible message type.","The message code designated for peer RP confirmation of bulk synchronization completion was not recognized by the ISSU infrastructure as a compatible PIM HA message type. Although PIM bulk synchronization may have succeeded, bulk synchronization confirmation is not possible.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","BULK_COMPLETE_XFORM_FAIL","ISSU xmit transform failed for bulk send complete message.","An ISSU transformation failed on the message used for peer RP confirmation of bulk synchronization completion. Although PIM bulk synchronization may have succeeded, bulk synchronization confirmation is not possible.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","CAP_PROC_NULL_CTX","NULL client context for ISSU capability TLV processing.","The callback function responsible for processing a capability type length value (TLV) was invoked by the ISSU infrastructure with a NULL client context. Capability negotiation cannot proceed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","CAP_PROP_NULL_CTX","NULL client context for ISSU capability TLV setup.","The callback function responsible for creating a capability type TLV was invoked by the ISSU infrastructure with a NULL client context. Capability negotiation cannot proceed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","DDE_REPLAY_FAILSAFE","PIM NSF Data Driven Event failsafe timer expired. First waiting VRF is","Multicast Forwarding Information Base (MFIB) replay of data driven events and subsequent Multicast Routing Information Base (MRIB) update processing has not completed within the maximum allowed time interval. Protocol Independent Multicast (PIM) is forcing termination of the Data Driven Event (DDE) replay monitoring period but some multicast routing information might not have been restored.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","DDE_REPLAY_NULL_MVRF","NULL MVRF specified for DDE replay.","An invalid (NULL) value was specified in a call to initiate MFIB data driven event replay following a route processor failover. Some previously existing multicast state might not be preserved through the route processor failover.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","DECODEFUNC","No decode function exists for sync data type %u","No function is defined for handling synchronization data of the specified type. No synchronization action is possible on the standby RP for the synchronization message that specified this data type.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","DECODENULL","No message buffer specified for standby sync of database type %u","A function was invoked to perform a database synchronization operation on the standby RP, but the caller did not specify the address of the synchronization message containing the information required for performing the synchronization operation. The synchronization operation for this database entity type cannot proceed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","DEFER_SYNC_FAILURE","Sync failure in standby defer sync operation.","An element which was scheduled to be synched later has failed to sync either upon arrival of the event it was waiting for or it has waited in the deferred sync queue for more than 1 minute.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"MCASTRED","3","DELNULLREQ","No sync request specified in sync request deletion attempt.","In a call to delete a synchronization request entry, the caller failed to specify the location of the synchronization request to be deleted. A memory leak is likely.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","DELSYNCTYP","Attempt to delete sync request for invalid sync type %u","A function attempting to delete a synchronization request has specified an invalid synchronization data type. The synchronization request cannot be deleted. A memory leak is likely.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","EMPTY_CAP_GROUP","Empty capability group for %s ISSU client capability TLV setup.","The callback function responsible for creating an ISSU capability type length value (TLV) found that the count of capability entries in its client context table was zero. Capability negotiation cannot proceed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","EMPTY_CAP_PROPOSE_TABLE","Empty capability table for ISSU capability TLV setup.","The callback function responsible for creating a capability type TLV was invoked by the ISSU infrastructure with a capability table containing no capability types. Capability negotiation cannot proceed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","EOXBADRC","Invalid completion code %u for sync message transmission type %u","An undefined completion code was specified for end of synchronization message transmission handling. Memory leakage, false timeouts, and other subsequent errors may result.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","EOXNOREQ","End of sync message transmission: no sync request specified","End of synchronization message transmission handling was invoked with no synchronization request specified. Cleanup for successful transmission cannot proceed. Retry for unsuccessful transmission cannot proceed. Memory leakage is likely and loss of synchronization on the standby RP is possible.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","FINDNULLENT","No target specified for sync entity search.","In a call to invoke a search for a database entity requiring synchronization to the standby RP, the caller failed to specify a descriptor for the entity to be synchronized. The synchronization operation entity cannot proceed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","FMTFUNC","No sync message format function defined for sync type %u","No function is defined to create a synchronization message for this type of database information. Loss of synchronization on the standby RP is likely.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","FMTGENNOBF","No message buffer specified for generic sync message info","A function was invoked to store generic synchronization message information into an outgoing message buffer, but the caller did not specify the outgoing message buffer address. The synchronization operation for this database entity type cannot proceed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","FMTMSG","Failed to format a sync message for sync type %u","An attempt to format (create) a synchronization message has failed. The synchronization message cannot be sent. Loss of synchronization on the standby RP is likely.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","FMTNULLPRM","Missing parameters in sync message format request for data type %u","A function was invoked to store synchronization message information into an outgoing message buffer, but the caller failed to specify either the location of the search key for the database entity to be synchronized or the address of the outgoing message buffer. The synchronization operation for this database entity type cannot proceed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","HASHNQ","Failed attempt to enqueue sync request type %u in hash table","An attempt to link a new synchronization request into the synchronization request hash table failed. This failure indicates corruption of the linkage within the hash table. The synchronization operation cannot proceed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","HLD_RLS_NO_MVRF","No MVRF for tableid 0x%x specified for multicast NSF holdoff release.","A table ID for which no MVRF exists was specified as an input to a function registered for releasing of a multicast NSF holdoff lock. If the calling client has a real holdoff extension request pending for some MVRF, the lock will not be released until the holdoff failsafe timer expires. This condition could delay completion of multicast reconvergence following an RP failover.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","HOLDOFF_FAILSAFE","PIM NSF failsafe timer expired. Holding client mask = 0x%x","One or more clients requested extension of the PIM NSF holdoff period, but did not release the holdoff within the maximum allowed time interval. PIM is forcing termination of the NSF holdoff period and resumption of normal flow of multicast routing information, but one or more clients may not be ready to resume normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","INITNOBOOL","Failed to create %s watched boolean during multicast redundancy initialization","An attempt to create a watched boolean during multicast (PIM) redundancy process initialization has failed. The PIM redundancy process cannot be initialized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","INITNOQUEUE","Failed to create %s watched queue during multicast redundancy initialization","An attempt to create a watched queue during multicast (PIM) redundancy process initialization has failed. The PIM redundancy process cannot be initialized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","INVALID_CAP_PROPOSE_TABLE","Invalid capability table for %s client ISSU capability TLV setup.","The callback function responsible for creating a capability type length value (TLV) was invoked by the ISSU infrastructure with a capability table that did not match any of the registered entries for this client. Capability negotiation cannot proceed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","INVSYNCTYP","Attempt to initiate sync request for invalid sync type","The synchronization data type specified by the function attempting to initiate a synchronization operation is not a valid type. No synchronization operation can be performed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","INV_CKPT_MSG","Received invalid CF message. client = %u, entity = %u, type = %u","An invalid checkpoint facility (CF) message was received by the PIM HA checkpoint client. The message cannot be processed. This condition might cause a loss of database synchronization between the primary and standby RPs.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","INV_PORT_TYPE","Invalid communication port identifier %u specified for ISSU port up/down handling","An undefined communication port identifier was specified for PIM ISSU transport up or down handling. PIM ISSU communication port up or down handling cannot proceed. PIM ISSU functionality might be impaired or lost.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","ISSU_EMPTY_TLV","Empty TLV list received for ISSU %s client capability processing","The callback function responsible for processing an ISSU capability type length value (TLV) list received an empty TLV list. Capability negotiation cannot proceed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","ISSU_PROC_CAP_TYPE","Invalid capability type found in %s client capability entry.","The callback function responsible for processing an ISSU capability type TLV list encountered a capability type for which no handling is available. Capability negotiation cannot proceed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","ISSU_TLV_INSERT","Failed to insert entry in ISSU capability TLV list for %s client","The callback function responsible for creating an ISSU capability type TLV list encountered a failure when attempting to insert an entry into a TLV list. Capability negotiation cannot proceed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","LOCFUNC","No database entity search function defined for sync type %u","A function was invoked to store synchronization message information into an outgoing message buffer, but no function exists for locating a database entry of the specified type. The synchronization operation for this database entity type cannot proceed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","LOCNULLENT","No destination specified in search for sync entity of type %u","A function was invoked to search for a database entity of the specified type, but the caller failed to specify a destination for storing the search result. The synchronization operation for this database entity type cannot proceed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","LOCNULLHND","No search handle specified in search for sync entity of type %u","A function was invoked to search for a database entity of the specified type, but the caller failed to specify a search handle (key) for finding the database entity to be synchronized. The synchronization operation for this database entity type cannot proceed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","MRIB_UPD_NULL_MVRF","NULL MVRF pointer specified for MRIB update notification.","A NULL MVRF address was specified in a function call to notify the PIM HA process that all pending updates have been read for a specified MVRF. The process will attempt to continue with RP switchover handling despite this error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","MSGNOREQ","Could not find sync request for completed sync message type %u","The synchronization request corresponding to a completed synchronization message could not be determined. This condition may result in memory leakage, false timeouts, and other subsequent errors.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","MSGSEQNUM","Out of order sequence number in received sync message for sync data type %u, received epoch/seq %u/%u, expected %u/%u","The sequence number specified in a synchronization message received by the standby RP is not the expected sequence number for the next received synchronization message. Some synchronization messages may have been lost.","Attempt to synchronize the standby RP by reloading it. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","MVRF_NAME","MVRF lookup for VRF %s failed.","An MVRF lookup failed for a VRF name known to be associated with an existing MVRF table, indicating an incorrect setup of search parameters. A PIM data synchronization operation has been aborted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","MVRF_TABLEID","MVRF lookup for tableid %u failed.","An MVRF lookup failed for a table ID known to be associated with an existing MVRF table, indicating an incorrect setup of search parameters. A PIM data synchronization operation has been aborted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","NEGOMSGINV","Invalid negotiation status for %s client message","The ISSU infrastructure evaluated a message for this client but failed to identify the message as a negotiation message or a user message. The message cannot be processed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","NOSYNCARG","NULL argument pointer specified for PIM data sync type %u.","A function was invoked to synchronize PIM information, but the caller did not provide a valid data pointer. The synchronization operation for this database entity type cannot proceed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","PRM_LOOKUP","PIM RP mapping range lookup for VRF %s group %i mask %i failed.","A PIM RP mapping range lookup failed for a range that is known to exist, indicating an incorrect setup of search parameters. A PIM data synchronization operation has been aborted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","RCVNODATA","No data pointer returned for received checkpoint message","On reception of a checkpoint message at the standby RP, an attempt to obtain the location of the data for the message returned a NULL pointer. No message contents are available for this message.","Attempt to synchronize the standby RP by reloading it. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","RPDF_NO_IDB","No IDB for if_number %u in Bidir RP DF sync attempt for RP address %i.","In a function call to trigger synchronization of bidirectional RP designated forwarder (DF) information, the interface descriptor block (IDB) if_number specified does not map to any existing IDB. The synchronization operation cannot proceed. The DF information might no longer be correct following an RP failover.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","RPDF_NULL_IDB","NULL IDB pointer in Bidir RP DF sync attempt for RP address %i.","In a function call to trigger synchronization of bidirectional RP DF information, a NULL IDB address was specified. The DF information might no longer be correct following an RP failover.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","RTRYLIMIT","Retry limit reached for sync type %u","The maximum allowable number of transmission retries has failed for a database entity of this type. No further retries can be executed. The standby RP might no longer be synchronized with the active RP.","Attempt to synchronize the standby RP by reloading it. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","RTRYNOREQ","Sync retry requested with no sync request specified","A retry was requested for transmission of a synchronization message, but no synchronization request information was specified. The retry cannot be executed. The standby RP might no longer be synchronized with the active RP.","Attempt to synchronize the standby RP by reloading it. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","SNDMSG","Failed to send a sync message for sync type %u","An attempt to send a synchronization message has failed. The message transmission will be automatically retried.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","SNDNODATA","No data pointer provided in checkpoint message to be sent.","After allocation of a checkpoint message buffer in the primary RP, an attempt to obtain the location of the data for the message returned a NULL pointer. The checkpoint message cannot be sent. Loss of standby synchronization is likely.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","SPURIOUS_MGD_TIMER_EXP","Managed timer wakeup received by the PIM HA process with no expired timers.","The PIM HA process received a wakeup for managed timer expiration, but no expired timer was reported. The timer expiration cannot be handled. The standby RP might no longer be synchronized with the active RP.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","SYNC_REQ_ORPHAN","Orphaned queue links found in sync request hash table search for sync type %u","An attempt to find a matching entry for a new synchronization request in the synchronization request hash table failed because of corruption of the linkage within the hash table. The synchronization operation cannot proceed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","TABLE_INVALID_CAP_TYPE","Invalid capability type found in %s client capability entry.","The callback function responsible for creating an ISSU capability type length value (TLV) list encountered a capability type for which no handling is available. Capability negotiation cannot proceed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","TUNSYNCMSG","Received invalid termination message for mvrf(%u) while waiting for mvrf(%u) mdt tunnel sync","Confirmation has failed for standby RP reception of a multicast distribution tree (MDT) tunnel message. As a result, the standby RP might not be able to create the MDT tunnel.","Attempt to synchronize the standby RP by reloading it. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","TUNSYNCRCV","%s failure in reception of MDT tunnel sync information for mvrf %s on the standby RP.","Confirmation has failed for standby RP reception of a multicast distribution tree (MDT) tunnel message. As a result, the standby RP might not be able to create the MDT tunnel.","Attempt to synchronize the standby RP by reloading it. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","TUNSYNCTIME","Timeout waiting for confirmation of mdt tunnel sync for mvrf(%u) (%s)","Confirmation has failed for standby RP reception of a multicast distribution tree (MDT) tunnel message. As a result, the standby RP might not be able to create the MDT tunnel.","Attempt to synchronize the standby RP by reloading it. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","TUNSYNCXMIT","Failed to transmit sync MDT tunnel information for mvrf %s to the standby RP.","An interprocess communication (IPC) transmission attempt has failed to send an IPC message to the standby RP with multicast distribution tree (MDT) tunnel synchronization information. As a result, the standby RP will not be able to create the MDT tunnel.","Attempt to synchronize the standby RP by reloading it. If the error recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","UCAST_CONV_STBY","Spurious unicast convergence notification received on standby RP for mvrf %s.","Unicast convergence notification was erroneously signalled on the standby RP for the specified multicast VRF. This convergence notification is being ignored.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCASTRED","3","WAITQ_ORPHAN","Orphaned queue links found in the %x MVRF wait queue.","An attempt to perform state transition handling for multicast VRFs (MVRFs) in this queue failed. The failure occurred because the queue was corrupted or because one or more queue link entries did not specify the address of the corresponding MVRF. Multicast route convergence following an RP failover may be delayed or impaired.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCAST_RP","4","MPLS_PIM_RATE_LIMIT","[chars] when [chars] will reprogram hardware setting for PIM. Please reapply PIM rate-limiter.","The Router Guard or PIM Snooping features require the switch hardware to be programmed in a manner different from MPLS. These two features are incompatible with MPLS. When either Router Guard or PIM snooping is enabled while MPLS is enabled, the PIM rate limiter will not work properly.","Unconfigure and reconfigure the PIM rate limiter using the show mls rate-limit multicast ipv4 pim command. The same solution applies to the situation when both Router Guard and PIM snooping are disabled and MPLS is being enabled."
"MCAST_RP","4","MPLS_PIM_SNOOPING","The MPLS and PIM Snooping features do not work together. Please disable either one.","The PIM Snooping feature requires the switch hardware to be programmed in such a way that PIM register messages with MPLS tags might be lost.","Disable either MPLS or PIM Snooping."
"MCAST_RP","4","MPLS_ROUTER_GUARD","The MPLS and Router Guard features do not work together. Please disable either one.","The Router Guard feature requires the switch hardware to be programmed in such a way that PIM register messages with MPLS tags might be lost.","Disable either MPLS or Router Guard."
"MCAST_RP","4","RGUARD_PIM_RATE_LIMIT","Router Guard feature if enabled or disabled while PIM rate-limiter is ON will not work properly. Please reapply the PIM rate-limiter.","The PIM rate limiter floods the rate-limited PIM control packets to all the ports in the VLAN. Because of this, the Router Guard feature will not work properly if enabled while the PIM rate limiter is enabled.","Unconfigure and reconfigure the PIM rate limiter using the show mls rate-limit multicast ipv4 pim command."
"MCM","3","DEQUEUE_FAIL","Unable to get a free event (%s) from the free event queue (slot: %d, mode %d)","During runtime, the minimal disruption routing (MDR) card manager is unable to retrieve a free event to communicate between its different processes. MDR operation will probably result in the resetting of all line cards.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCM","3","GET_MTU_FAIL","Unable to get the MTU for message %d to seat %s (%d) (valid:%d)","During runtime, the MDR card manager is unable to get the MTU of a message to be sent between its different processes.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCM","3","NEGO_INCOMPATIBLE","MDR Card manager ISSU negotiation with standby is incompatible","An error occurred during MDR card manager initialization. As a result, the MDR card manager is unable to synchronize its data between the active and standby supervisors. An MDR operation will probably result in the resetting of all line cards.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCT1E1","2","CMD_DROP","[chars], cmd: [dec], arg0: [dec], arg1: [dec] arg2: [dec], arg3: [dec], vc: [dec] reason: [chars]","The SPA driver dropped a configuration command. One or more interfaces or controllers associated with the SPA might not be configured correctly.","Check the configuration of the interfaces and controllers and correct the configuration if necessary. If the condition persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCT1E1","2","EV_DROP","[chars], cmd: [dec], arg0: [dec], arg1: [dec] arg2: [dec] reason [chars]","The SPA driver dropped an event notification command. Counters or line protocols for one or more interfaces or controllers may be incorrect.","Restart any interfaces or controllers that are down. If the condition persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCT1E1","3","AUTODNR","%s failed for slot %d bay %d err %d","The Auto-Do-Not-Resequence (AUTODNR)/USNDNR process has failed. The SPA and line card are out of synchronization. This condition indicates a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCT1E1","3","BAD_SIZE_ERR","SPA [dec]/[dec]: [dec] [chars] events on HDLC Controller were encountered. The SPA is being Restarted.","The SPA driver detected an error event on the HDLC controller.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCT1E1","3","BATCH_CMD_INVALID_TAG","SPA [dec]/[dec]: Invalid tag value [dec] at index [dec].","The SPA driver detected an invalid tag value in a batch command from the RP.","If the ports on the SPA are not operating as expected, power down and reseat the specified SPA card. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCT1E1","3","CMD_FAILED","SPA [dec]/[dec]: f/w send command failed err [dec] reason [chars]","The SPA driver could not successfully send a command to the firmware.","If the ports on the SPA are not operating as expected, power down and reseat the specified SPA card. If this message persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCT1E1","3","COR_MEM_ERR","SPA [dec]/[dec]: [dec] correctable [chars] memory error(s) encountered.The error has been corrected and normal processing should continue.The memory address of most the recent error is: [hex]","The SPA driver detected a correctable memory error on the SPA card. The error has been corrected and normal processing should continue. The hexadecimal memory address of the most recent error is specified in the message text on the console or in the system log.","If the condition persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCT1E1","3","FPGA_CNTR_ERR","[chars]: [dec] [chars] error(s) encountered.","The SPA driver detected an FPGA error condition on the SPA card. Interface packet error counter corruption may result.","The SPA should continue to function normally. If the error condition recurs, reset the SPA by doing a physical online insertion and removal (OIR). If the condition persists, copy the error message exactly as it appears. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCT1E1","3","FRMR_CLKFAIL","SPA [dec]/[dec]: Framer input clock failure detected, CTCLK = [chars]CTIVE, LREFCLK = [chars]CTIVE, SREFCLK = [chars]CTIVE, ctclk count [int] lrefclk count [int] srefclk count [int]","The SPA driver detected failure of one or more input clocks to the framer chip. The T1/E1 ports may not operate as expected.","If the ports on the SPA are not operating as expected, power down and reseat the specified SPA card. If this message persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCT1E1","3","HDLC_CTRL_ERR","SPA [dec]/[dec]: [dec] [chars] events on HDLC Controller were encountered.","The SPA driver detected an error event on the HDLC controller.","If the condition persists, c opy 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCT1E1","3","INITFAIL","MCT1E1 (bay [dec]), Init Failed at [chars] - line [dec] arg [hex]","The SPA failed to complete hardware initialization.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCT1E1","3","PERIODIC_PROCESS","SPA [dec]/[dec]: periodic process error [chars].","The SPA driver detected an error with the periodic processing routine.","If the ports on the SPA are not operating as expected, power down and reseat the specified SPA card. If this message persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCT1E1","3","QUEUE_HALT_FAIL","[chars]: Could not suspend message ([dec]) or command ([dec]) queue","The message or command queue could not be stopped prior to the OIR removal of the SPA.","If the ports on the SPA are not operating as expected, power down and reseat the specified SPA card. If this message persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCT1E1","3","SPI4_HW_ERR","SPA [dec]/[dec]: [chars] Hardware error was encountered.","The SPA driver detected a hardware error condition on the SPA card's SPI4 bus. This condition might result in improper operation.","Power down and reseat the specified SPA card. If the condition persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCT1E1","3","TIMEOUT","%s: %s failed: %d, state: %d, ml_id: %d progress: %d","Linkrec is stuck at non-ready. This condition indicates a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCT1E1","3","UNCOR_MEM_ERR","SPA [dec]/[dec]: [dec] uncorrectable [chars] memory error(s) encountered. The memory address of the most recent error is: [hex]The SPA is being restarted.","The SPA driver detected an uncorrectable memory error condition on the SPA card. Packet corruption may result. The hexadecimal memory address of the most recent error is specified in the message text on the console or in the system log.","Power down and reseat the specified SPA card. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCT1E1","3","UNCOR_PARITY_ERR","SPA [dec]/[dec]: [dec] [chars] parity error(s) encountered.","The SPA driver detected an uncorrectable parity error condition on the SPA card. Packet corruption may result.","Power down and reseat the specified SPA card. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MCX","3","FREEDMFATAL","Bay [dec]: freedm reset, command-status register [hex]","CHOPIN experienced fatal freedm related problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MDEBUG","2","ACCESSBEYONDSIZE","[hex] access beyond allocated size; ptr = [hex]; size = [dec]; actual size = [dec]; allocator_pc = [hex]; Traceback - [chars]","The software attempted to access memory beyond the allocated size.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MDR_SM","3","INIT_FAIL","Initialisation error '%s'","An error occurred during initialization of the minimum disruption restart (MDR) state machine (SM). As a result, the MDR SM is inoperable. An MDR operation will probably result in the resetting of all line cards.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM","3","SLOT_CLIENT_ID_ERROR","Can not find the data associated to client ID (%d) for slot (%d)","The MDR state machine cannot find the data registered for the client ID. The client ID is invalid.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM","3","SLOT_CONTINUE_INVALID","Client (%d) returned an invalid status code on slot %d","The MDR state machine client returned a status code that is invalid when returned on the standby device.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM","3","SLOT_EVENT_TIMEOUT","MDR slot state machine %d did not receive the SLOT_UP event from the linecard","The MDR slot state machine (SM) did not receive an expected event from the line card. As a result, the state machine is inoperable for this slot.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM","3","SLOT_ID_MISMATCH","Client ID mismatch for slot %d during progression %s on client: %d, expecting %d","The MDR state machine client returned a client ID that does not match the current client ID. As a result, the MDR state machine will abort.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM","3","SLOT_INVALID_ARG","Process is unable to get his slot number","The MDR state machine process is unable to get the slot number of a slot supporting MDR.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM","3","SLOT_INVALID_EVENT","Slot (%d) received an unexpected event (%s) in state (%s)","The MDR state machine received an unexpected event for the current state.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM","3","SLOT_NOTIFY_STANDBY_FAILED","Failed to notify Standby for MDR slot state machine (%d) Client %s (%d) in state %s","The MDR state machine failed to notify the standby device. As a result, the MDR state machine will abort.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM","3","SLOT_NOTIFY_TIMEOUT","Notification timeout on MDR slot state machine %d for the local client %s (%d) in state %s","The MDR state machine (SM) did not receive a response from the MDR SM client. As a result, the state machine is inoperable. An MDR operation will probably result in the resetting of all line cards.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM","3","SLOT_NO_FREE_EVENT_IN_QUEUE","The event queue is full for MDR Slot SM %d, MDR Slot SM %d will abort","The MDR state machine (SM) was unable to get a free event from the event queue. As a result, the state machine is inoperable. An MDR operation will probably result in the resetting of all the line cards.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM","3","SLOT_STATUS_INVALID","Client %s (%d) on slot %d returned an unexpected status code (%d)","The MDR state machine client returned an unexpected status code. An MDR operation will probably result in the reset of all line cards.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM","3","SYS_CLIENT_ID_ERROR","Can not find the data associated to client ID (%d)","The MDR state machine cannot find the data registered for the client ID. The client ID is invalid.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM","3","SYS_CONTINUE_INVALID","Client (%d) returned an invalid status code","The MDR state machine client returned a status code that is invalid when returned on the standby device.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM","3","SYS_ID_MISMATCH","Client ID mismatch during progression %s on client: %d, expecting %d","The MDR state machine client returned a client ID that does not match the current client ID. As a result, the MDR state machine will abort.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM","3","SYS_INVALID_EVENT","Received an unexpected event (%s) in state (%s)","The MDR state machine received an unexpected event for the current state.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM","3","SYS_NOTIFY_STANDBY_FAILED","Failed to notify Standby for MDR system state machine Client %s (%d) in state %s","The MDR state machine failed to notify the standby device. As a result, the MDR state machine will abort.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM","3","SYS_NOTIFY_TIMEOUT","Notification timeout on MDR system state machine for the local client %s (%d) in state %s","The MDR state machine (SM) did not receive a response from the MDR SM client. As a result, the state machine is inoperable. An MDR operation will probably result in the resetting of all line cards.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM","3","SYS_NO_FREE_EVENT_IN_QUEUE","The event queue is full for MDR System SM, MDR SM will abort","The MDR state machine (SM) was unable to get a free event from the event queue. As a result, the MDR SM is inoperable. An MDR operation will probably result in the resetting of all the line cards.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM","3","SYS_STATUS_INVALID","Client %s (%d) returned an unexpected status code (%d)","The MDR state machine client returned an unexpected status code. An MDR operation will probably result in the reset of all line cards.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM","4","QUIESCE_FAIL","Quiesce watchdog timer expired, continuing with MDR","At the start of a switchover, the minimum disruption restart state machine (MDR SM) on the old active RP enters the quiesce state. Because this state blocks the reload of the old active, the switchover is blocked during this state. To prevent a loss of service due to a bug in the MDR SM or one of its clients, a watchdog timer limits the duration of this state.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM","4","SLOT_CALLBACK_TOO_MUCH_TIME","MDR SM Slot %d client %s (%d) spent too much time (%d msecs) in state (%s)","The MDR state machine has detected that one of its clients spent too much time in its callback function. This is a warning message; the MDR state machine will continue.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM","4","SYS_CALLBACK_TOO_MUCH_TIME","MDR SM SYS client %s (%d) spent too much time (%d msecs) in state (%s)","The MDR state machine detected that one of its clients spent too much time in its callback function. This is a warning message; the MDR state machine will continue.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM","4","UNBLOCK_RF","MDR SM aborted, continuing RF Progression (%d)","The MDR state machine (SM) aborted due to an error in the MDR state machine or one of its clients. The redundancy facility (RF) progression was blocked, but it will be unblocked to allow the standby device to boot.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM_LC","3","ABORT","MDR state machine is aborted due to '%s'","The minimum disruption restart (MDR) state machine (SM) aborted due to an unrecoverable error. Any MDR operation will probably result in the resetting of this line card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM_LC","3","ID_MISMATCH","Client ID mismatch during progression on client: %d, expecting %d","The MDR state machine client returned a client ID that does not match the current client ID. As a result, the MDR state machine will abort.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM_LC","3","INIT_FAIL","Initialisation error '%s'","During the MDR state machine (SM) initialization, an error occurred that has caused the MDR SM to be inoperable. Any MDR operation will probably result in the resetting of this line card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM_LC","3","INVALID_EVENT","MDR SM LC received an unexpected event (%s) in state (%s)","The MDR state machine (SM) received an unexpected event for the current state.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM_LC","3","NOTIFY_TIMEOUT","Notification timeout for client %s(%d) in state %s","During an MDR state machine (SM) state transition, the notification timer expired for the client. Any MDR operation will probably result in the resetting of this line card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM_LC","3","NO_FREE_EVENT_IN_QUEUE","The event queue is full for MDR SM, MDR SM will abort","The MDR state machine (SM) was unable to get a free event from the event queue. This error has rendered the MDR SM inoperable. An MDR operation will probably result in the resetting of all the line cards.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM_LC","3","SEMWAIT","MDR state machine waiting for semaphore(%s) acquired by pid(%d)","The MDR state machine encountered a problem in acquiring a semaphore. Any MDR operation will probably result in the resetting of this line card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM_LC","3","STATUS_INVALID","Client %s (%d) returned an unexpected status code (%d)","The MDR state machine client returned an unexpected status code. An MDR operation will probably result in the reset of all line cards.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM_LC","4","CALLBACK_TOO_MUCH_TIME","MDR SM LC client %s (%d) spent too much time (%d msecs) in state (%s)","The minimum disruption restart (MDR) state machine (SM) has detected that one of its clients spent too much time in its callback function. This is a warning message; the MDR state machine will continue.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM_PROXY","3","NOTIFY_TIMEOUT","Notification timeout on MDR %s state machine for the remote client '%s'","The minimum disruption restart (MDR) state machine (SM) proxy master did not receive any response to the notification on its slave, and is now unable to communicate with the slave. As a result, the MDR SM is inoperable. An MDR operation will likely result in the resetting of all line cards.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MDR_SM_PROXY","4","SLOT_CALLBACK_TOO_MUCH_TIME","MDR SM Slot %d client (%d) spent too much time (%d msecs) in state (%s)","The MDR state machine has detected that one of its clients spent too much time in its callback function. This is a warning message; the MDR state machine will continue.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDR_SM_PROXY","4","SYS_CALLBACK_TOO_MUCH_TIME","MDR SM SYS client (%d) spent too much time (%d msecs) in state (%s)","The MDR state machine has detected that one of its clients spent too much time in its callback function. This is a warning message; the MDR state machine will continue.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show monitor event-trace mdr_sm all commands and your pertinent troubleshooting logs."
"MDS","2","LC_INVALID_HWIDB_INDEX","Invalid if_index for HWIDB [chars]","The if_index parameter for the hardware IDB was invalid.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MDS","2","LC_INVALID_HWIDBQ_SIZE","Invalid Q count value","The Q count parameter was invalid.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MDS","2","LC_INVALID_SWIDB_IFNUM","Invalid if_num for SWIDB [chars]","The if_index parameter for the software IDB was invalid.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MDS","2","LC_INVALID_SWIDBQ_SIZE","Invalid Q count value","The Q count parameter was invalid.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MDS","2","LC_SWIDB_UPDATE_NULL_MVRF","LC received swidb update for if_number [hex] ([chars]) tableid [hex].mvrf pointer for this tableid is NULL.","The line card received a software IDB update from the route processor specifying a multicast VRF table ID for which no multicast VRF exists in the linecard.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MDS","4","ROUTELIMIT_ATTEMPT","Attempt to exceed multicast route-limit of [dec]","The number of multicast routes equals the configured maximum allowed. New routes cannot be added unless the configuration is changed.","If multicast traffic is of any priority among the traffic carried by this router, then use the ip multicast route-limit command to increase the number of multicast routes. Otherwise, no action is required."
"MDT","4","LBSRC","MDT %s uses source address %i from a non-loopback interface","The local peering interface used to set up an MDT tunnel is not a loopback interface. This may cause black holes if the interface is in the outgoing list of the MDT group.","Change the configuration of the bgp update-source command and use a loopback interface as the local peering interface."
"MDT","4","NO_GROUP_LINK","MDT entry [chars]:([IP_address],[IP_address]) linked by source but not linked by group","The entry for the affected MDT group was not properly linked into the MDT database. The inconsistency has been repaired. [chars] is the MDT entry and the [IP_address],[IP_address] are the linked IP addresses.","No action is required."
"MDT","4","RD_CONFLICT","MDT entry [chars]:([IP_address],[IP_address]) received an update for RD [chars]","A previously existing MDT entry should have been withdrawn by BGP before sending this conflicting update. [chars] is the MDT entry, the [IP_address],[IP_address] are the linked IP addresses, and the second [chars] is the redirect name.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MDT","4","UPDATED_RD_CONFLICT","MDT entry %s:(%i,%i) received an update for RD %s","The previously existing entry should have been withdrawn by BGP before sending this conflicting update.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MDT","4","VRFSRC","The source interface of the MDT tunnels, %s, is not in the global table","The local peering interface must not be an interface in a VRF.","Change the configuration of the bgp update-source command and use a loopback interface in the global table."
"MDT","5","DATA_MDT_REUSED","Data MDT %i is reused","If all pre-defined data MDT groups are used, a data MDT group can be reused by a particular host that sources user traffic in an VPN.","No action is required."
"MDX","1","DAEMSGSNDFAILED","FAILED to send IPC message of TYPE [chars] to slot [dec] on the DAE, FAIL REASON = [chars]","An IPC message could not be sent. Retries to send the message were attempted and failed. This condition does not affect system operation.","No action is required."
"MDX","1","DAENODPENTRY","MDX framework could not find an entry for the DP with dp_id = [dec] on slot = [dec], on DAE","IPC messages that were sent to the line card have been lost as the line card buffers were being reassigned. As a result of this condition, the MDX DP failed to register. This condition does not affect system operation.","Disable the SNMP query of the MIBs depending on the value of dp_id as follows:"
"MDX","1","DAEPORTCREATEFAIL","Could not create IPC port for MDX framework on DAE, FAIL REASON = [chars]","The IPC port for MDX framework on the Data Aggregator End (DAE) failed for the reason specified in the message text. This condition does not affect system operation, except that the MDX framework will not be able to obtain the requested data from the MIBs.","Enter one or more of the following CLI commands to obtain the required information: show processes memory, show processes cpu, show controller optics, show controller fia, show controller xbar or show controller sca."
"MDX","1","DAEPORTOPENFAIL","UNABLE to open port to primary RP FAIL REASON = [chars]","The MDX Data Aggregator End (DAE) IPC port could not be opened, even after three retry attempts. This condition does not affect system operation, except that the MDX framework will not be able to obtain the requested data from the MIBs.","Enter one or more of the following CLI commands to obtain the required information: show processes memory, show processes cpu, show controller optics, show controller fia, show controller xbar or show controller sca."
"MDX","1","DAEPORTOPENFAILRETRY","UNABLE to open port to primary RP try number = [dec], FAIL REASON = [chars], Will retry again","The MDX Data Aggregator End (DAE) IPC port could not be opened. The system will attempt to retry the operation a maximum of three times. This condition does not affect system operation.","No action is required."
"MDX","1","DPENTRYEXISTS","An entry already exists for the DP with dp_id [dec] on the DPE, could not create a new entry","The DP entry that is attempting to be added already exists on the DPE. The new entry could not be created.","No action is required."
"MDX","1","DPEPORTOPENFAIL","UNABLE to open port to MDX framework on slot = [dec] from DAE, FAIL REASON = [chars]","The MDX DPE (Data Provider End) IPC port could not be opened because of the reason specified in the message text. This condition does not affect system operation.","No action is required."
"MDX","1","DPREGFAILED","DP Registration with MDX framework failed on DPE","The DP could not be registered with the MDX framework on the Data Provider End (DPE). This condition does not affect system operation, except that the MDX framework will not be able to obtain the requested data from the MIBs.","Enter one or more of the following CLI commands to obtain the required information: show processes memory, show processes cpu, show controller optics, show controller fia, show controller xbar or show controller sca."
"MDX","1","IPCMSGSNDFAILED","FAILED to send IPC message of TYPE [chars] to DAE, FAIL REASON = [chars]","The MDX component could not send the IPC message because of the reason specified in the message text. This condition does not affect system operation.","No action is required."
"MDX","1","IPCMSGUNAVAIL","Request for IPC buffer failed for size = [int]","An IPC buffer request returned a null value. The IPC has exhausted its buffer space. This condition does not affect system operation.","Enter the ipc cache size command to increase the IPC buffer size."
"MDX","1","MSG","[chars]","An internal error regarding the MDX facility has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MDX","1","NODPENTRY","MDX framework could not find an entry for the DP with dp_id = [dec]","The entry for the DP does not exist in the MDX framework. A possible reason for this error is that the DP has not registered with the framework. This condition does not affect system operation, except that the MDX framework will not be able to obtain the requested data from the MIBs.","Enter one or more of the following CLI commands to obtain the required information: show processes memory, show processes cpu, show controller optics, show controller fia, show controller xbar or show controller sca."
"MDX","1","NOMGDTIMERCNTXT","The expired timer does not have a timer context","MDX framework found a managed timer that does not have a context. This condition does not affect system operation.","No action is required."
"MDX","1","PORTCREATEFAIL","Could not create IPC port for MDX Framework, FAIL REASON = [chars]","An IPC port could not be opened for the MDX framework even after three retry attempts. This condition does not affect system operation.","No action is required."
"MDX","1","PORTCREATEFAILRETRY","Could not create IPC port for MDX framework try number = [dec], FAIL REASON = [chars], Will retry again","An IPC port could not be created. The system will attempt to retry the operation a maximum of three times.","This condition has no effect on system operation. No action is required."
"MDX","1","PORTREGFAIL","Could not Register IPC port for MDX framework FAIL REASON = [chars]","The IPC port could not be registered with the IPC master, even after three retry attempts. This condition does not affect system operation.","No action is required."
"MDX","1","PORTREGFAILRETRY","Could not Register IPC port for MDX framework try number = [dec], on slot = [dec], FAIL REASON = [chars], Will retry again","The IPC port could not be registered with the IPC master. The system will attempt to retry the operation a maximum of three times.","This condition has no effect on system operation. No action is required."
"MDX","1","SIZEMISMATCH","Recieved an IPC message with inconsistent size compared to the MDX TU in its data region","The size of the IPC message that was received by the MDX framework is not consistent when it is compared to the MDX TU. This condition does not affect system operation.","No action is required."
"MDX","1","UNKNOWNMSGTYPE","The rcvd msg-type is not supported, msg-type [chars]","The message type that was received is not supported by the MDX framework. This condition does not affect system operation.","No action is required."
"MEM_ECC","2","MALLOC","Attempt to malloc [dec] bytes for the ECC error log failed. ECC errors will only be reported and not recorded.","Memory could not be allocated for the ECC error log. If the system has only 32 MB of memory, an upgrade is recommended.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MEM_ECC","2","MBE","Multiple bit error detected at [hex]","A multi-bit error that could not be corrected was detected on a CPU that was read from DRAM.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MEM_ECC","2","MBE_RMW","Multiple bit error detectedat [hex] on a read-modify-write cycle","A multi-bit error that could not be corrected was detected during a read-modify-write cycle on a CPU that was read from DRAM for a non-8-byte access.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MEM_ECC","2","PARITY","Parity error on CPU write to address: [hex]","A data parity error was detected by the ECC Ctrl facility during a CPU write operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MEM_ECC","2","PARITY_INFO","Parity error was detected on the following byte(s) of a double word: [chars] [chars] [chars]","This message specifies the bytes of a 64-bit word that contained invalid parity, and caused the ECC Ctrl facility to generate an interrupt operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MEM_ECC","3","BADADDR_MBE","Invalid MBE dram address: [hex] latched by ECC Ctrl","The address that was found by the ECC control register while an MBE was being detected is not a valid DRAM address. This condition probably indicates a malfunctioning ECC control register that requires replacement.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MEM_ECC","3","BADADDR_MBE_RMW","Invalid MBE dram address: [hex] latched by ECC Ctrl during a RMW cycle","The address that was found by the ECC control register while an MBE was being detected during a read-modify-write cycle is not a valid DRAM address. This condition probably indicates a malfunctioning ECC control register that requires replacement.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MEM_ECC","3","BADADDR_SBE","Invalid SBE dram address: [hex] latched by ECC Ctrl","The address that was found by the ECC control register while an SBE was being detected is not a valid DRAM address. This condition probably indicates a malfunctioning ECC control register that requires replacement.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MEM_ECC","3","BADADDR_SBE_RMW","Invalid SBE dram address: [hex] latched by ECC Ctrl during a RMW cycle","The address that was found by the ECC control register while an SBE was being detected during a read-modify-write cycle is not a valid DRAM address. This condition probably indicates a malfunctioning ECC control register that requires replacement.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MEM_ECC","3","SBE","Single bit error detected and corrected at [hex]","A single-bit correctable error was detected on a read from DRAM.","Enter the show ecc command to display the single-bit errors that have been logged. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MEM_ECC","3","SBE_HARD","Single bit *hard* error detected at [hex]","A single-bit error that could not be corrected (a hard error) was detected on a CPU that was read from DRAM.","Enter the show ecc command to display the single-bit errors that have been logged and display the hard error address locations. Monitor the system by periodically entering the show ecc command and replace the DRAM if too many errors are encountered."
"MEM_ECC","3","SBE_LIMIT","Single bit error detected and corrected at [hex]","A single-bit correctable error was detected on a CPU that was read from DRAM.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MEM_ECC","3","SBE_RMW","Single bit error detected and corrected at [hex] on a read-modify-write cycle","A single-bit correctable error was detected on during a read-modify-write cycle on a CPU read from DRAM for a non-8-byte access.","Enter the show ecc command to display the single-bit errors that have been logged. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MEM_ECC","3","SBE_RMW_HARD","Single bit *hard* error detected at [hex] on a read-modify-write cycle","A single-bit uncorrectable hard error was detected during a read-modify-write cycle on a CPU read from DRAM for a non-8-byte access. The show ecc command can be used to dump single-bit errors currently logged.","Enter the show ecc command to display the single-bit errors that have been logged and display the hard error address locations. Monitor the system by periodically entering the show ecc command and replace the DRAM if too many errors are encountered."
"MEM_ECC","3","SBE_RMW_LIMIT","Single bit error detected and corrected at [hex] on a read-modify-write cycle","A single-bit correctable error was detected on during a read-modify-write cycle on a CPU read from DRAM for a non eight-byte access.","Enter the show ecc command to display the single-bit errors that have been logged. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MEM_ECC","3","SYNDROME_MBE","8-bit Syndrome for the detected Multi-bit error: [hex]","A multi-bit error has been detected for the 8-bit syndrome. This value does not indicate the exact positions of the bits in error, but can be used to approximate their positions.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MEM_ECC","3","SYNDROME_SBE","8-bit Syndrome for the detected Single-bit error: [hex]","A single-bit error has been detected for the 8-bit syndrome. This value does not indicate the exact positions of the bits in error, but can be used to approximate their positions.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MEM_ECC","3","SYNDROME_SBE_LIMIT","8-bit Syndrome for the detected Single-bit error: [hex]","A single-bit error has been detected for the 8-bit syndrome. This value does not indicate the exact positions of the bits in error, but can be used to approximate their positions.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MEM_MGR","3","MEM_MGR_EXCEED_MAX","memory pool exceeds maximum (%d bytes) allowed.","An attempt was made to allocate a buffer from a memory pool that has reached its maximum limit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MEM_MGR","3","MEM_MGR_INVALID","The Memory Management code encounters an invalid parameter.","The memory manager has received an invalid parameter from its caller.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MEM_MGR","3","MEM_MGR_NOMEM","Out of memory","The memory manager is out of memory.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MEMPOOL","3","IPC","[chars] [chars]","An IPC error has occurred on polling the Enhanced Mempool MIB.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"METOPT","2","UNAVAILABLE","No memory available for %s","An attempt at memory allocation failed.","Try these actions to remedy the problem: Add memory. Disable some features. Apply filtering to decrease the size of system data structures - the routing table, for example. In general, reduce other system activities to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"METOPT","2","UNAVAILABLE","No packet buffer available for %s interface to send this packet to higher layer","An attempt to allocate packet buffer failed.","Try these actions to remedy the problem: Reload the system. Perform a CPU switchover if you have a redundant CPU system"
"METOPT","2","UNAVAILABLE","Port Fail event received from %s switch card on fabric port associated with interface %s","Fabric Port Failed due to some problem","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"METOPT","2","UNAVAILABLE","Zero length while %s linecard. Datalen %d","Due to some internal error a zero length transaction is being made from/to the Line card","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"METOPT","3","UNAVAILABLE","Access to %s temperature sensor failed","Accesses to chassis temperature sensor failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"METOPT","3","UNAVAILABLE","Interrupt %s not expected, masking off","An interrupt of a certain type was signalled, but the interrupt handler for this type of interrupt is not yet installed.","This problem should be self-correcting but indicates either a hardware or a software defect. If it's a hardware defect, further problems are to be expected. If it's a software problem, certain types of error and alarm conditions may be left undetected. Copy the error message exactly as it appears, and report it to your technical support representative."
"METOPT","3","UNAVAILABLE","Mismatch in backplane IDPROM, %s: Active-side=%d, Sby-side=%d","There are two backplane IDPROMS. Each is readable by one of the two redundant CPUs. Most IDPROM fields should be programmed by manufacturing to contain identical information. Only the first mismatched field is shown. Use a CLI show command to see additional mismatches.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"METOPT","3","UNAVAILABLE","Mismatch in backplane IDPROM, %s: Active-side=%s, Sby-side=%s","There are two backplane IDPROMS. Each is readable by one of the two redundant CPUs. Most IDPROM fields should be programmed by manufacturing to contain identical information. Only the first mismatched string is shown. Use a CLI show command to see additional mismatches.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"METOPT","4","UNAVAILABLE","Invalid CPU ID, assuming revision 1","The CPU ID could not be read from EEPROM. This is probably due to a hardware failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"METOPT","6","DI_ASSERTED","CDL Defect Indication: [chars] Asserted on interface [chars]","Some CDL Defect Indication bits were asserted on this interface.","Closely monitor CDL Defect Indication Status if Defect Indication was asserted."
"METOPT","6","DI_CLEARED","CDL Defect Indication: [chars] cleared on interface [chars]","CDL Defect Indication Status changed.","No action is required."
"METOPT_DRV","3","REPROGRAM_ERROR","[chars]","The Metro Optical Reprogram driver encountered an error. The error message contains text useful to identify the cause of the problem.","Retry the reprogramming of the card. If the reprogramming fails again, remove the card and reinsert it. If the card does not come up, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"METS","2","UNAVAILABLE","Can't start analysis","The requested operation failed due to lack of resource, maybe temporarily","Reduce system resource/memory usage, and retry for the commands."
"METS","3","BADMETHOD","Cannot process %s method %u","A method list function encountered a method list that was unknown, or could not be handled.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"METS","3","UNAVAILABLE","Can't process null pool: %s","Resource failure: Null pool in the region","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"METS","3","UNAVAILABLE","Cannot process %s method %u","A method list function encountered a method list that was unknown, or could not be handled.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"METS","3","UNAVAILABLE","No region found: %s","Resource failure: No region found.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"METOPT_DI","1","UNAVAILABLE","%s:%s","The specified alarm has occured or cleared","The recommeded action is to repair the source of the alarm."
"METOPT_DI","3","UNAVAILABLE","%s(%d):%s","The Metro Optical CDL defect indiation subsystem encountered an internal software error. The error message contains text useful to identify the nature of the problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFI","3","BADREADUPDATESIZE","Read update reply message from RP has bad size: [dec]","A read update message does not match the parsed result of the read message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFI","3","EVTLOGCAPTURE","Event Logger Capture Error [dec] [dec]","A failure occurred during an event logger capture operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFI","3","EVTLOGCLIENT","Invalid client [dec]","An invalid client has accessed the event logger.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFI","3","EVTLOGCONTROL","[chars]: [dec]","A general event logger controller error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFI","3","EVTLOGREGISTER","Event Logger Registration Error [dec] [dec] [dec]","A failure occurred during an event logger client registration operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFI","3","LCPULSE","LC pulse failed: [chars] [dec]","A line card pulse request operation has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFI","3","MFICOMM","[chars]","An error involving the communications module has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFI","3","MFICOMM2","[chars]: [hex] [hex]","An error involving the communications module has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFI","3","MFICOMM3","[chars]: [hex] [hex] [hex]","An error involving the communications module has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFI","3","MPLS_MTU_SET","[chars] [dec] [chars] [chars] [chars] [dec][chars]","Most drivers will be able to support baby giants and will gracefully drop packets that are too large. Certain drivers will have packet forwarding problems including data corruption.","Increase the interface MTU on all routers connected to this interface to the needed MTU size by entering the mtu bytes command."
"MFI","3","NOCLIENTREQ","[chars] [chars]: [dec] [dec] [dec]","The client reply component could not find an outstanding request.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFI","3","PNDMSGMGR","[chars] [chars] [dec] [dec] [dec]","Only one outstanding request is allowed from a process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFI","3","REDISTMGR","Redistribution Manager: [chars] [hex]","An error involving the redistribution manager has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFI","3","REDISTMGR2","Redistribution Manager: [chars] [hex] [hex]","An error involving the redistribution manager has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFI","3","REDISTMGR3","Redistribution Manager: [chars] [hex]","An error involving the redistribution manager has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFI","3","REPLYMSGSIZE","Reply message is too large: [chars]: [dec]","A read update message is too large to fit into the XDR buffer.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFI","4","UNAVAILABLE","%s %s: %d %d %d","Client reply could not find an outstanding request","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFI","4","UNAVAILABLE","%s: %x %x","MFI General Communication Module","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB","2","UNAVAILABLE","Out of memory for IP multicast MFIB. Used: %lu, Free: %lu","Insufficient memory for the IP multicast forwarding information base. Multicast packets may not be properly routed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB","3","NETWORK_GET_FAIL","MFIB can not get network offset: datagram [hex]; network [hex]","The MFIB failed to find a suitable packet network offset.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB","3","NETWORK_SET_FAIL","MFIB can not set network offset: datagram [hex]; length [dec]; offset [dec]","The MFIB failed to set the offset within a packet.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB","3","NO_SBCTRLFUNC","A[chars] function is required for the MFIB sub-block, but none was provided","The MFIB could not distribute interface information to a line card due to an internal error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB","3","SWITCHOVER_FAIL","Error creating [chars]. MFIB will not work with switchover","Sufficient memory is not available to create structures needed to enable switchover for IPv6 multicast.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"MFIB","6","UNAVAILABLE","%d at %s","MFIB attempted to exceed maximum number of replicated packet header buffers","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB","6","UNAVAILABLE","Packet too short from %s, datagram size %d, tl %d","An IP/IPv6 packet which is too short was received","No action is required."
"MFIB_CONST_RP","6","REPLICATION_MODE_CHANGE","Replication Mode Change Detected. Current system replication mode is %s","When auto detection of replication mode is enabled the system will transition to ingress mode when an egress incapable linecard is inserted. The system will transition back to egress mode when the last egress incapable linecard is removed","Transition between ingress and egress mode will cause temporary loss of traffic, to prevent this use the command ipv6 mfib hardware-switching replication-mode ingress"
"MFIB_DB","3","UNAVAILABLE","%p (%lx) due to discard failure","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_DB","3","UNAVAILABLE","%p (%lx/%s) as %lu entries, %lu ioitems","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_IPC","2","UNAVAILABLE","An IPC message was received with an error status: %s.","An IPC message was received but could not be processed due to an IPC error condition.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_IPC","2","UNAVAILABLE","An IPC message was received with an incorrect type (%d).","An IPC message was received with a type value that does not match that used by the MFIB.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_IPC","2","UNAVAILABLE","An IPC message was received with and unrecognised subtype (%d)","An IPC message was received by the MFIB but could not be processed because the subtype was not recognised.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_IPC","2","UNAVAILABLE","Failed to create local IPC port, error = %s","An IPC port could not be created. This may prevent MFIB statistics being gathered from one or more linecards.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_IPC","2","UNAVAILABLE","IPC message for stats or rates failed, code = %d","Sending of IPC message for stats or rates failed, possibly because of congestion. Stats or rates values may be temporarily affected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_IPC","2","UNAVAILABLE","LC did not receive Ack for IPC message of size = %d, type = %d, error = %s.","The linecard did not receive an acknowledgement for an IPC message it sent to the Route Processor.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_IPC","2","UNAVAILABLE","LC failed to register IPC port: %s","The route processor could not register its IPC port. No MFIB statistics will be gathered from linecards.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_IPC","2","UNAVAILABLE","LC in slot %d failed to open IPC port to RP, error = %s.","The linecard has failed to open IPC port towards the Route Processor. No MFIB statistics will be collected from this line card as a result.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_IPC","2","UNAVAILABLE","LC in slot %d failed to send LC Ready MSG to RP, error = %s.","The linecard has failed to send a Ready message to the Route Processor. No MFIB statistics will be collected from this linecard.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_IPC","2","UNAVAILABLE","RP did not receive Ack for IPC message of type = %d, error = %s","The Route Processor did not receive and acknowledgement for an IPC message that was sent to a linecard.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_IPC","2","UNAVAILABLE","RP failed to create linecard IPC port info structure, slot = %d","The Route Processor has failed to create an IPC port for distributed statistics collection","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_IPC","2","UNAVAILABLE","RP failed to open an IPC port for communication with the linecard in slot %d.","The Route Processor has failed to open an IPC port for distributed statistics collection.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_IPC","2","UNAVAILABLE","RP failed to register IPC port: %s","The route processor could not register its IPC port. No MFIB statistics will be gathered from linecards.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_IPC","2","UNAVAILABLE","RP failed to send IPC message to linecard in slot %d.","The Route Processor could not send an IPC message to a linecard because the slot number is incorrect.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_IPC","2","UNAVAILABLE","The LC failed to create a required process.","The linecard failed to create a process required tomanage linecard IPC connections to the RP. No MFIB statistics will be collected from this linecards","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_IPC","2","UNAVAILABLE","The RP failed to allocate an internal data structure.","The Route Processor failed to allocate memory required to managed linecard IPC connections. No MFIB statistics will be collected from linecards.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_IPC","2","UNAVAILABLE","The RP failed to create a required process.","The Route Processor failed to create a process requiredto manage linecard IPC connections. No MFIB statistics will be collected from linecards.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_MRIB","3","UNAVAILABLE","For %s %s in table %p (%lx/%s) with %s(%lx)","The MFIB attempt to update an MRIB IOitem failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_MRIB","3","UNAVAILABLE","For %s in table %p (%lx/%s) with %s(%lx)","The MFIB attempt to update an MRIB Entry failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_MRIB","3","UNAVAILABLE","In table %p (%lx/%s) : %s","MFIB has encountered an error while processing a message sent by MRIB.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_MRIB","3","UNAVAILABLE","In table %p (%lx/%s) : %s","MFIB has encountered an error while processing an MRIB database update.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_MRIB","3","UNAVAILABLE","In table %p (%lx/%s) with %s(%lx)","An MFIB table failed to connect to the MRIB","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_MRIB","3","UNAVAILABLE","In table %p (%lx/%s) with %s(%lx)","An MFIB table failed to disconnect from the MRIB","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_MRIB","3","UNAVAILABLE","In table %p (%lx/%s) with %s(%lx)","An MFIB table failed to register with the MRIB","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_MRIB","3","UNAVAILABLE","In table %p (%lx/%s) with %s(%lx)","The MFIB failed to configure an MRIB connection.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_PLTF","3","UNAVAILABLE","%s %p","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_PLTF","3","UNAVAILABLE","%s entry %s [%p (%lx/%s)]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_PLTF","3","UNAVAILABLE","%s ioitem %s %s [%p (%lx/%s)]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_PLTF","3","UNAVAILABLE","%s. %p","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_PLTF","3","UNAVAILABLE","%s. %s entry %p %s [%p (%lx/%s)]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_PLTF","3","UNAVAILABLE","%s. %s ioitem %p %s %s [%p (%lx/%s)]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_PLTF","3","UNAVAILABLE","%s. %s table %p %p (%lx/%s)","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFI_LABEL_BROKER","3","UNAVAILABLE",',"The MFI Label Broker received a null key pointer","Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative."
"MFI_LABEL_BROKER","3","UNAVAILABLE","%d","The MFI Label Broker received a (un)registration request from an invalid MPLS application.","Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative."
"MFI_LABEL_BROKER","3","UNAVAILABLE","%d","The MFI Label Broker received a request to allocate an invalid label.","Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative."
"MFI_LABEL_BROKER","3","UNAVAILABLE","%s","An MPLS application is registering multiple times with the label broker.","Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative."
"MFI_LABEL_BROKER","3","UNAVAILABLE","%s","An MPLS application requested label broker services without registering first.","Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative."
"MFI_LABEL_BROKER","3","UNAVAILABLE","%s","The MFI Label Broker received an invalid parameter in a request to allocate or free a local label.","Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative."
"MFI_LABEL_BROKER","3","UNAVAILABLE","%s Label %d in table %d, %s 0x%x","The MFI Label Broker encountered a situation where there is no currently active label for applications to use for the FEC indicated.","Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version, show running-config, show mpls forwarding-table internal and contact your Cisco technical support representative."
"MFI_LABEL_BROKER","3","UNAVAILABLE","%s%d%s%d","The MFI Label Broker received an invalid process event from the IOS-on-Neutrino infrastructure.","Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative."
"MFI_LABEL_BROKER","3","UNAVAILABLE","LDM(%d), PID(%d)","The MFI Label Broker received a registration request with invalid PID.","Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative."
"MFI_LABEL_BROKER","3","UNAVAILABLE","Label %d in table %d, %s, %s","The MFI Label Broker could not honor a request to immediately handle the process restart of the application indicated. It will try to handle it in the background","Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version, show running-config and show mpls infrastructure label-broker ldm (this latter command is present only when service internal is enabled) and contact your Cisco technical support representative."
"MFI_LABEL_BROKER","3","UNAVAILABLE","Label %d in table %d, %s, %s [p/i/o/bm %d/%d/%d/0x%x]","The MFI Label Broker received a request to bind the label to a prefix, but the label is already bound to another prefix.","Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version, show running-config and show mpls forwarding-table and contact your Cisco technical support representative."
"MFI_LABEL_BROKER","3","UNAVAILABLE","Label %d in table %d, for %s","The MFI Label Broker was unable to program the label in question for the mentioned FEC.","Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version, show running-config, show mpls forwarding-table internal and contact your Cisco technical support representative."
"MFI_LABEL_BROKER","3","UNAVAILABLE","Process id %d %s, error code %d","The MFI Label Broker was unable to notify the operating system about (un)registration of the specified process.","Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version, show running-config, show mpls infrastructure label-broker ldm and contact your Cisco technical support representative."
"MFI_LABEL_BROKER","3","UNAVAILABLE","application %s Recommended Action    Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config and contact your Cisco technical support representative.MGCP-2Error Message    %MGCP-2-UNAVAILABLE: %s 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.MGCP-3Error Message    %MGCP-3-UNAVAILABLE: %s 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.MGCP-4Error Message    %MGCP-4-UNAVAILABLE: %s 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.MFIB_CONST_LC MessagesThis section contains MFIB Constellation platform messages.Error Message    %MFIB_CONST_LC-6-ADJ_V6MCAST_ALLOC_FAILURE: Failed to allocate Adjacency for IPv6 multicast entry (S[ipv6_addr], G[ipv6_addr])","The system was unable to allocate an adjacency for this particular flow. The affected flow will be retried and will be software switched until it is successfully installed in the hardware.","The adjacency table utilization could be very high and need to be brought down. Removing some hardware switched flows would help solve the problem"
"MFIB_CONST_LC","6","FIB_V6MCAST_INSTALL_FAILURE","Failed to install FIB IPv6 multicast entry (S[ipv6_addr], G[ipv6_addr])","The FIB entry limit has been exceeded so FIB entries cannot be allocated by the MFIB_CONST_LC.","The FIB table utilization is too high and needs to be reduced. The total number of multicast shortcuts is too large to fit in the FIB table. As a result, subsequent shortcuts will be software switched. Reducing the FIB utilization by other protocols would help solve the problem."
"MFIB_CONST_LC","6","MET_V6MCAST_ALLOC_FAILURE","Failed to allocate MET entries for IPv6 multicast entry (S[ipv6_addr], G[ipv6_addr])","The system is unable to allocate MET entries for this particular flow. The affected flow will be retried and will be software switched until it is successfully installed in the hardware.","The MET utilization could be very high and must be reduced. Removing some hardware switched flows would help solve the problem"
"MFIB_CONST_LC","6","NF_V6MCAST_INSTALL_FAILURE","Failed to install Netflow IPv6 multicast entry (S[ipv6_addr], G[ipv6_addr])","A multicast entry could not be installed due to a NetFlow full condition or a Hash collision.","The NetFlow table utilization is too high and needs to be reduced. The total number of multicast shortcuts are too large to fit in the NetFlow table. As a result, these shortcuts will be software switched. Removing dynamically created NetFlow IPv6 entries or disabling dynamic NetFlow entry creation would help solve the problem."
"MFIB_CONST_LC","6","SW_V6MCAST_INSTALL_FAILURE","Failed to install IPv6 multicast entry, due to [chars] (S[ipv6_addr], G[ipv6_addr], C:[dec])","The system is unable to install an IPv6 multicast entry due to unrecoverable software failures.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MGCP_APP","6","UNAVAILABLE","Cannot create MGCP application process","Failed to create the MGCP application process.","Check the size of free memory to make sure there is enough memory."
"MGCP_APP","6","UNAVAILABLE","Failed to allocate memory for event node","Failed to allocate memory for event node.","Check the size of free memory to make sure there is enough memory."
"MGCP_APP","6","UNAVAILABLE","Failed to create DNS message watched queue","Failed to create DNS message watched queue.","Check the size of free memory to make sure there is enough memory."
"MGCP_APP","6","UNAVAILABLE","Failed to create MGCP system message watched queue","Failed to create MGCP system message watched queue.","Check the size of free memory to make sure there is enough memory."
"MGCP_APP","6","UNAVAILABLE","Failed to create TFTP message watched queue","Failed to create TFTP message watched queue.","Check the size of free memory to make sure there is enough memory."
"MGCP_APP","6","UNAVAILABLE","Failed to create call record database","Failed to create call record database.","Check the size of free memory to make sure there is enough memory."
"MGCP_APP","6","UNAVAILABLE","Failed to create endpoint database","Failed to create endpoint database.","Check the size of free memory to make sure there is enough memory."
"MGCP_APP","6","UNAVAILABLE","Failed to initialize MGCP services","Failed to initialize MGCP services.","Check the size of free memory to make sure there is enough memory."
"MGCP_APP","6","UNAVAILABLE","Failed to open UDP port for MGCP","Failed to open UDP port for the MGCP process.","Check if any other application use the same UDP port number (2427)."
"MGCP_APP","6","UNAVAILABLE","Failed to register MGCP Application with CCAPI","Failed to register MGCP Application with CCAPI.","Check the size of free memory to make sure there is enough memory."
"MGCP_APP","6","UNAVAILABLE","Failed to start VOIP call leg","Failed to start VOIP call leg.","Check the size of free memory to make sure there is enough memory."
"MGCP_APP","6","UNAVAILABLE","Suspended initialization of MGCP services. No IP interface up yet","Suspended initialization of MGCP services. No IP interface up yet","Make sure there is atleast one interface configured with an IP Address."
"MIC","2","UNAVAILABLE","Failed to register with RF, status %u.","The MIC failed to register with RF.","LOG_STD_NO_ACTION"
"MIC","3","UNAVAILABLE","Caller specified invalid MIC client type, %u.","The MIC client type is out of range.","LOG_STD_NO_ACTION"
"MICA","1","UNAVAILABLE","%s","MICA modem FIRMWARE download file is not found in BOOTFLASH.","Record the reason at the end of the message, and report the problem."
"MICA","1","UNAVAILABLE","Slot %d MICA Board Crashed, Going to Recover","A MICA modem board has crashed. The router will automatically restart and reload it.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","1","UNAVAILABLE","Slot %d MICA Board Init Failed : %s","A MICA modem board has failed to reset and initialize.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","Attempting restart of modem module %d","The indicated modem module suffered a run-time error and had to be reset and an attempt is now being made to restart the modem module.","LOG_STD_NO_ACTION"
"MICA","3","UNAVAILABLE","Bad count from modem %d: count = %d","A message was received from the indicated modem which had an illegal count .","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","Bad mail message opcode from modem %d: opcode = 0x%x","A message was received from the indicated modem which had an illegal opcode.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","Bad msg from modem(%d/%d): opcode/arg = 0x%x/0x%x","A message received from the modem was not expected by the driver. If the hardware is newer than the software, this could mean a new response cannot be handled. Otherwise, it is possible that data corruption has occurred in the hardware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","Bad tx mail message opcode = 0x%x","A message was attempted to be transmitted to the indicated modem which had an illegal opcode.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","Bad vendor id from PLX 9060SD -- value was 0x%x","A hardware error occurred involving the PCI interface chip.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","Bad version %s portware: %s","Modem firmware of the indicated version, bundled into the modem card image, did not pass the sanity tests done to verify a firmware image.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","Boardware is not bundled in this IOS image","This image does not contain on-board software (boardware) necessary for MICA modems.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","Cannot download version %s on module %d","The block information that is necessary to download modem firmware was missing for the indicated firmware version.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","Contiguous packet sent for transmit","A software error occurred resulting in an unexpected packet being set up for transmission and the packet was dropped.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","Error: Trying to access an invalid modem %d","The requested operation could not be accomplished because of a bad modem number. Call your technical support representative for assistance","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","Exhausted %s DMA entries for module %d","The software structures that are used to drive the DMA engines were temporarily exhausted while attempting the task indicated in the error message; the task was aborted as a result.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","Exhausted free mail elements for modem_num %d. Current use: %d","The software structures that are used to receive and transmit messages from the MICA modems were temporarily exhausted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","Failed To Allocate Memory for MICA modem mgmt","The requested operation could not be accomplished because of a low memory condition.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"MICA","3","UNAVAILABLE","Inband NAK from modem %d -- payload 0x%x 0x%x 0x%x 0x%x 0x%x 0x%x 0x%x 0x%x","A inband message sent to the indicated modem was rejected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","Inband NAK from modem (%d/%d): opcode = 0x%x","A inband message sent to the indicated modem was rejected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","Inband message with unknown opcode received from modem %d -- payload 0x%x 0x%x 0x%x 0x%x 0x%x 0x%x 0x%x 0x%x","An inband message with unknown opcode was received from the indicated modem","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","Mica sent invalid stack address or length, MICA module %d, addr 0x%x, length %d","Runtime error occured on MICA, MICA sent invalid stack address or length.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","Modem %d went bad","Run-time checks for modem health determined that the indicated modem was no longer functional due to a hardware or software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","Modem %d: %s while handling %s.","The modem state machine received a bad parameter as indicated by the error message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","Modem number %d/%d is bad, Error code is %x","Message from the MICA modem driver indicates that the modem is bad.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","Modem(%d/%d) Unexpected Event: %s in %s","An error was reported from the modem hardware which was not expected by the driver.","The seriousness of this problem has not been determined. If the determination is not obvious from the error message provided from the device, follow these instructions: 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","Module in socket %d (board-id=%d) is %s module; card is not %s card","The modem module in the socket indicated by the message is inappropriate for the modem card it is on.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","Module in socket %d is of unknown type (board-id=%d)","The modem module in the socket indicated by the message is bad, possibly because the serial EEPROM on the module is misprogrammed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","NAK from modem %d in state %d -- payload 0x%x","A message sent to the indicated modem was rejected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","No IDB structure for modem %d","A software structure was found in an unexpected state during run-time for the indicated modem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","No PPP context structure for modem %d","A software structure was found in an unexpected state during run-time for the indicated modem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","No TTY structure for modem %d","A software structure was found in an unexpected state during run-time for the indicated modem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","No msg buffer for Modem(%d/%d) in %s:%d","The MICA software was unable to allocate a packet buffer. The system may be out of memory.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","Packet descriptor count (%d) exceeds transmit ring size","The packet to be transmitted needed more descriptors than are available on the transmit ring, and the packet was dropped.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","Portware download timed out for module %d","The diagnostic message that is expected back from a MICA modem after successful download and initialization of the modem firmware was never received.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","Runtime error on MICA module %d Hex %d","A software error occurred on the modem firmware executing on the indicated modem module.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","Slot %d Boardware download failed because of %s, all modems are marked bad","A MICA modem failed to download its on-board software (boardware.) This was probably caused by a communication error between the router and the MICA hardware.","Try powercycling the router. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","Slot %d Looking for %x, but reading %x","The MICA driver timed out waiting for a specific response.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","Static receive paktype unavailable","A software structure was found in an unexpected state during run-time for the indicated modem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","3","UNAVAILABLE","Unknown inband msg from modem (%d/%d): opcode = 0x%x","An unknown inband message is received from the indicated modem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MICA","4","UNAVAILABLE","OOB comand in Slot(%d) took too long to complete. Reseting port","The OOB port was locked because a command took too long to complete. The port was recovered by reseting internal datastructures.","If there are frequent occurances of this event, turn on debug modem oob for the slot and report the problem with these logs"
"MICA","4","UNAVAILABLE","Slot %d Module numbers %s are running default IOS image, file %s not found in flash","The MICA modem on-board software (boardware) was provided from the running Cisco IOS Software image because the boardware could not be found in flash memory.","LOG_STD_NO_ACTION"
"MICA","5","UNAVAILABLE","Modem (%d/%d) is being recovered by %s","Modem is consecutively failing to Connect, so being recovered","None"
"MICA","5","UNAVAILABLE","Modem (%d/%d) recovery failed: %s","Modem recovery failed","None"
"MICA","5","UNAVAILABLE","Slot %d is running boardware version %c.%c.%c.%c","This is a status message to indicate the successful start-up of the on-board software (boardware) on one MICA modem port.","LOG_STD_NO_ACTION"
"MICA","5","UNAVAILABLE","Unknown modem module in Slot %d - Modem Module %d","A MICA modem module has an uninitialized cookie. This can be due to a manufacturing error or more likely it is due to a problem on the modem module itself.","Please seek a replacement for this modem module. For some reason this module no longer is able to identify itself LOG_STD_NO_ACTION"
"MICA","6","UNAVAILABLE","Modem module %d initialized","The indicated modem module was successfully initialized.","LOG_STD_NO_ACTION"
"MIF68840","1","UNAVAILABLE","Only found %d interfaces on bay %d, shutting down bay","The number of interfaces found was not what was expected. This possibly indicates a hardware failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MIF68840","3","UNAVAILABLE","%s packet buffer, pak=0x%x","This indicates an internal software inconsistency.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MIF68840","3","UNAVAILABLE","Bay %d device ID seen as %#x, expected %#x","The FDDI driver failed to initialize.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MIF68840","5","UNAVAILABLE","'%s' command on %s","The requested device or port is not supported as a FDDI interface","LOG_STD_NO_ACTION"
"MIMIC","3","UNAVAILABLE","No memory for %s of unit %d","The router does not have enough memory to perform the function","Please make sure there is sufficient memory available in the router. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MIMIC","3","UNAVAILABLE","The %s firmware download for the network module in slot %d failed.","The integrated modem network module hardware may be bad.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MIMIC","3","UNAVAILABLE","The MCOM integrated modem network module controller in slot %d %s.","The integrated modem network module hardware may be bad.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MIMIC","3","UNAVAILABLE","The MCOM integrated modem network module in slot %d failed to configure. %s","The integrated modem network module hardware may be bad.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MIMIC","3","UNAVAILABLE","The MCOM integrated modem network module in slot %d failed to initialize properly.","The integrated modem network module hardware may be bad.","Power down, reinsert the network module and reboot. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MIMIC","3","UNAVAILABLE","The modem in slot %d port %d failed to reset (status = 0x%x).","The integrated modem hardware may be bad.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MIMIC","3","UNAVAILABLE","The network module hardware reports an invalid %s device id of %#x.","The integrated modem network module hardware may be bad.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MIMIC","3","UNAVAILABLE","Unable to reset MCOM integrated modem %d/%d.","A critical error occurred and the device driver unsuccessfully attempted to reset the modem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MIMIC","4","UNAVAILABLE","The MCOM integrated modem subsystem is not compatible with this router.","The network module is not compatible with the current platform that it is plugged into.","Power down, remove the network module and reboot."
"MFIB_CONST_RP","6","REPLICATION_MODE_CHANGE","Replication Mode Change Detected. Current system replication mode is [chars]","When automatic detection of the replication mode is enabled, the system will transition to ingress mode when an egress-incapable line card is inserted. The system will transition back to egress mode when the last egress-incapable line card is removed. The transition between ingress and egress modes will cause temporary loss of traffic.","To prevent traffic loss, enter the ipv6 mfib hardware-switching replication-mode ingress command."
"MFIB_STATS","2","MFIB_STATS_LC_FAILED_GET_COUNTERS","Linecard failed in getting counters due to null table. af = [int], v6 def tbl [hex], v4 def tbl [hex]","The line card has failed to get entry counters due to a null table.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_STATS","2","MFIB_STATS_LC_FAILED_GET_IPC_MSG","Linecard failed allocating ipc message buffer","The line card failed to allocate a buffer for sending statistics.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_STATS","2","MFIB_STATS_LC_FAILED_SEND_MSG","Linecard failed in sending msg to the Route Processor error = [chars]","The line card has failed to send a statistics message to the route processor.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_STATS","2","MFIB_STATS_LC_MSG_TOO_BIG","Linecard failed to return counters, message buffer too small.","The line card has failed to return counters because the minimum message size exceeds the maximum IPC buffer size.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_STATS","2","MFIB_STATS_RP_FAILED_GET_IPC_MSG","RP failed allocating ipc message buffer for linecard, slot = [dec]","The route processor failed to allocate a buffer for getting line card statistics.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_STATS","2","MFIB_STATS_RP_FAILED_REPLY_MSG","RP received reply with error status from linecard, slot = [dec]","The route processor has received a reply with error in statistics message from a line card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MFIB_STATS","2","MFIB_STATS_RP_SEQ_ERROR","The RP ignored out of sequence per-interface statistics returned by the linecard in slot [dec].","A line card returned per-interface statistics in the wrong order and the RP has ignored them.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MISA","1","ERROR","[chars]","An error occurred in the application using ISA.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MISA","6","INFO","[chars]","This is an informational message from ISA.","This is an informational message only and occurs in normal operation. No action is required."
"MK5","1","UNAVAILABLE","Unit %d, initialization CSR1_UERR failure, csr1=0x%04x","The hardware failed to initialize correctly.","Repair or replace the controller."
"MK5","1","UNAVAILABLE","Unit %d, initialization failure - No CSR1_PPRIM_INIT_CONF, csr1 = 0x%04x","The hardware failed to initialize correctly.","Repair or replace the controller."
"MK5","1","UNAVAILABLE","msgtxt_badringsize","An internal software error occurred.","If either of these messages recur, call your technical support representative for assistance."
"MK5","1","UNAVAILABLE","msgtxt_initfail","The hardware failed to initialize correctly.","Repair or replace the controller."
"MK5","1","UNAVAILABLE","msgtxt_memoryerror","A network serial interface detected a hardware problem.","Repair or replace the controller."
"MK5","1","UNAVAILABLE","msgtxt_nomemory","The requested operation could not be accomplished because of a low memory condition.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"MK5","3","UNAVAILABLE","Unit %d, bad output packet encapsulation: 0x%x","An internal software error occurred.","If either of these messages recur, call your technical support representative for assistance."
"MK5","3","UNAVAILABLE","Unit %d, provider primitive lost, csr0=0x%04x, csr1=0x%04x","A network serial interface detected a hardware problem.","Repair or replace the controller."
"MK5","3","UNAVAILABLE","Unit %d, spurious provider primitive interrupt, csr0=0x%04x, csr1=0x%04x","A network serial interface detected a hardware problem.","Repair or replace the controller."
"MK5","3","UNAVAILABLE","Unit %d, unexpected provider primitive, csr0=0x%04x, csr1=0x%04x","A network serial interface detected a hardware problem.","Repair or replace the controller."
"MK5","3","UNAVAILABLE","Unit %d, user primitive error, csr0=0x%04x, csr1=0x%04x","A network serial interface detected a hardware problem.","Repair or replace the controller."
"MK5","5","UNAVAILABLE","Unit %d excessive modem control changes","Too many modem control interrupts have been received. The port was disabled to prevent excessive use of the CPU.","Check the cable on the serial port."
"MISTRAL","3","BAD_PAK","Possibly un-encapsulated packet passed to Mistral: int [chars] type [int] stat [hex] flags [hex] size [dec] encsize [dec] offset [dec] requeue_token [int] r1 [int] r2 [int] total detected [int]","A badly encapsulated packet from the process level was passed to the Mistral ASIC.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MISTRAL","3","NOEOBCBUF","No EOBC buffer available. Dropping the packet.","The Ethernet out-of-band channel pool of receive buffers for the Mistral ASIC has been exhausted. No additional input packets can be handled until some buffers are returned to the pool.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MLD_PROT","6","IDB_ENABLE","Interface [chars] does not support multicast, not enabled","IGMP/MLD is not enabled on the specified interface that does not support multicast.","This is an informational message only. No action is required."
"MLI","3","NOT_ENOUGH_SPACE","There is not enough space in Memory Layout Information area to store the tuple","Insufficient memory is reserved in the Memory Layout Information (MLI) area to store the given MLI tuple data.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show mli commands and your pertinent troubleshooting logs."
"MLS_ACL_COMMON","3","MLS_ACL_CONSIST_FIX","ACL TCAM inconsistency seen at index [dec] and could not be fixed","The ACL TCAM inconsistency checker found an inconsistency between software and hardware TCAM entries and could not fix it. [dec] is the index where the inconsistency was found.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MLS_ACL_COMMON","4","LOG_UPDATE_NO_RL","ACL TCAM update ([chars] direction) occured on interface [chars]; [chars] action taken [chars] msec","An update of the ACL TCAM occurred on the specified interface. When the ACL TCAM is updated, the specified security action is taken for the specified time interval.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MLS_ACL_COMMON","4","LOG_UPDATE_RL","ACL TCAM update ([chars] direction) occured on interface [chars]; [chars] action taken [chars] msec","An update of the ACL TCAM occurred on the specified interface. When the ACL TCAM is updated, the specified security action is taken for the specified time interval.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MLS_ACL_COMMON","4","MLS_ACL_CONSIST","ACL TCAM inconsistency seen at index [dec]","The ACL TCAM inconsistency checker found an inconsistency between software and hardware TCAM entries and has fixed it. [dec] is the index where the inconsistency was found.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MLSCEF","2","EXCESSIVE_FIB_CORR_SSRAM_ERRORS","Too many fib correctable ecc error interrupts.","The number of correctable error interrupts has exceeded the threshold of 1000 correctable ECC errors in 30 minutes. All errors were corrected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show mls cef hardware, show mls cef log, and show ver commands and your pertinent troubleshooting logs."
"MLSCEF","2","EXCESSIVE_FIB_SSRAM_ERRORS","Too many fib ecc error interrupts.","The number of error interruptions exceeded the threshold. As a result of this condition, the system will fail.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MLSCEF","2","FIB_SSRAM_WRITE_INCONSISTENCY","FIB SSRAM Mismatch for Index: [dec] Expected: [hex], Hardware: [hex]","A problem occurred when the system attempted to write the FIB SSRAM.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MLSCEF","2","FIB_TCAM_WRITE_INCONSISTENCY","FIB TCAM Mismatch for [chars]: Index: [dec] Exprected:Entry: [hex]-[hex]-[hex] Hardware: Entry: [hex]-[hex]-[hex]","A problem occurred when the system attempted to write the FIB TCAM.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MLSCEF","2","RELOAD","maximum routes config mismatch. Reloading with correct config","The system detected a mismatch between the user configuration route allocation and the current route allocation. A system reload is required to correct this condition.","If the message does not appear continuously and the mls cef maximum-routes command has been entered, no action is required. If this message appears continuously on the same module and the mls cef maximum-routes command has not been entered, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MLSCEF","2","SANITY_FAIL","Sanity Check of MLS FIB s/w structures failed","The verification process encountered inconsistent MLS FIB data structures.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MLSCEF","2","UNCORRECTABLE_SSRAM_ERROR","Bank [dec] Index: [dec], Expected: [hex], Hardware: [hex]. Affected TCAM [hex]-[hex]-[hex]","A faulty FIB SSRAM location was detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MLSCEF","4","FIB_EXCEPTION_THRESHOLD","Hardware CEF entry usage is at 95% capacity for [chars] protocol.","The number of route entries that are installed is about to reach the hardware FIB capacity, or the maximum routes limit set for the specified protocol. If the limit is reached, some prefixes will be software switched.","Enter the mls cef maximum-routes [protocol] global configuration command to increase the maximum number of routes for the protocol. Refer to the configuration manuals for the differing capacity limitations of XL versus non-XL systems, as well as for impacts to other protocols when changing maximum routes of one protocol. Enter the show mls cef summary command to see the current usage summary."
"MLSCEF","4","INCORRECT_CONFIG","A max-routes configuration mismatch or an invalid max-routes configuration has been detected. Reverting to default configuration.","The system has detected a configuration mismatch or an invalid configuration for the mls cef maximum-routes command, and is reverting to the system default configuration.","Reconfigure your maximum routes using the mls cef maximum-routes command. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MLSCEF","7","FIB_MASK_MISMATCH","Attempt to delete an entry not matching block mask - class = [dec], [dec]/[dec], mask [dec]/[dec]","The passed mask does not match the stored block mask.","This is a debug message only. No action is required."
"MLS_CEF_ISSU","2","MLS_CEF_RETRY_FAIL","Unable to get maximum routes config from Active RP.","The ISSU process was unable to get the maximum route configuration from the active RP. The system will configure to default values.","Reload the system. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MLSM","2","IPC_ERROR","MMLS: IPC failure detected between RP and SP","This can happen when EOBC channel is too busy or NMP is too busy so that draco side does not get response even after few retries by IPC layer.","Under some stressful condition, when communication between RP and SP side can not be maintained this message will be printed. MMLS will keep trying to recover from situation by sending message to SP. The restart message to SP has exponential back off upto 160 second"
"MLSM","4","CC_ERROR","(Type of CC: [chars]): [chars] ([IP_address],[IP_address]), Auto-repair is [chars]","Either the RP-SP or MROUTE-MLSM consistency checker has detected an error.","If enabled, the autorepair feature will automatically correct the error."
"MLSM","4","MLSM_LTL_FULL_VDB_CREATE_FAILED","Multi-Layer Switching for Multicast: Disabling Multicast Hardware Switching for VLAN ([dec]), VLAN not found on Switch Processor","The switch processor is unable to create VLANs due to a Layer 2 hardware limitation. Because no VLAN information is available, the switch processor is unable to install shortcuts. Multicast hardware switching for this VLAN interface will be disabled to avoid installation of shortcuts. All flows using this VLAN as the outgoing interface will be affected.","Modify the network configuration to increase the hardware resources for creating VLANs on the switch processor."
"MLSM","6","BIDIR_SC_INSTALL_FAILURE","Bi-dir multicast flows will not be installed in hardware in the presence of tunnel interfaces for RP [IP_address]","Bidirectional multicast flows will not be installed in hardware in the presence of tunnel interfaces. The bidirectional flows will be software-switched until the tunnel interfaces are unconfigured.","Unconfiguring the tunnel interfaces will allow the bidirectional flows to be hardware-switched."
"MLSM","6","CONFIG_MISMATCH","Multicast hardware switching config mis-match between RP and NMP.It is likely to be disabled on the NMP","MLS multicast hardware switching has been enabled on the RP but likely disabled on the NMP","Correct the mis-config by enabling IGMP snooping and MMLS on the NMP"
"MLSM","6","CONFIG_MISMATCH_RECOVERED","Multicast hardware switching mismatch recovered from earlier config mis-match","MMLS Config mismatch between RP and SP recovered from mismatch. The MLS multicast hardware switching is likely to be enabled on the NMP","Note the difference between the time the error occurred to the current message. It indicates the time when no HW switched entries existed in the switch"
"MLSM","6","ERROR_RECOVERED","MMLS: Communication channel between RP and SP recovered from failure","Communication between RP and SP recovered from earlier IPC / SCP failure. MMLS will install HW switched entries on backoff timer expiration. The backoff time is min(10 sec * (# of times error occurred)^2, 160)","Note the difference between the time the error occurred to the current message. It indicates the time when no HW switched entries existed in the switch"
"MLSM","6","LC_SCP_FAILURE","NMP encountered internal communication failure for (%i,%i,%d), flow will be software switched","This message happens SP was not able to update CEF tables on atleast one of the EARLs on Linecards.","Under some condition SP was not able to communicate with Linecard to update the multicast-CEF table. And this causes inconsistency in the CEF table among different line cards. This shortcut is deleted, so that inconsistent state is purged. And this flow will get software forwarded."
"MLSM","6","MFD_COUNT_ERR","MFD Count error : (%i,%i,%d) first mfd: %dvlan extra RPF-MFD in HW state: %dvlan","This message happens when there are multiple MFD in hardware switched state.","Under some stressful condition, RP tends to think that there are two MFDs install for a particular flow. This should not happen, if it happens, it is harmless. This message is added, just to help debugging this problem."
"MLSM","6","MIN_MTU_SUPPORTED","MMLS flows being re-started as the MTU of all the interfaces (oifs) is not equal. Packets greater than the minimum MTU of all oifs will be software switched","This message happens when all the earl in the system are now having polaris rev1.1. In this system configuration, earl will bridge the packet in the incoming interface to draco if incoming packet size is larger then mtu programmed in fib. Software will forward the packet out in all the interfaces. In this configuration WAN (incoming) - LAN (outgoing) flows can be hardware switched upto min-mtu of oif sizes.","This is just a informative message. If there are to many packets going to CPU, the MTU on the interfaces should be changed appropriately to take advantage of hardware replication."
"MLSM","6","MIN_MTU_UNSUPPORTED","Outgoing interfaces with MTU less than the RPF interface will be multicast replicated to in software","This message happens when atleast one earl in the system is now having polaris rev1.0. In this system configuration, earl will not be able to bridge the packet in the incoming interface to draco, if incoming packet size is larger then mtu programmed in fib. So, OIFs having MTU LAN (outgoing) flows will be completely software forwarded.","This is just a informative message. If there are to many packets going to CPU, the MTU on the interfaces should be changed appropriately to take advantage of hardware replication."
"MLSM","6","MLSM_PMS","MMLS: MLSM is suspending the caller process [chars]","MLSM is suspending the caller process. This message appears when the MLSM routines are called from the PIM/Mwheel context and MLSM routines suspend a process. When MLSM suspends the caller process, data corruption might occur for the data that is handled by the caller process.","This message is informational. No action is required."
"MLSM","6","MMLS_EGRESS_INFO","MMLS: Please make sure no multicast traffic is going through egress incapable line cards when system is operating in egress mode","There should be no multicast traffic going through egress-incapable line cards while the system is operating in egress replication mode.","Determine if there are any egress-incapable line cards in the system. If there are egress-incapable line cards, verify that there is no multicast traffic going through them."
"MLSM","6","MMLS_LEGACY_INSERTED","MMLS: Legacy Linecard Inserted, Egress Replication Mode will be disabled","Egress replication is not supported with legacy modules. The system will transition to ingress mode and will cause a temporary loss of traffic.","If the system is required to operate in egress replication mode, remove the legacy module."
"MLSM","6","MMLS_MDT_TUNNEL_UP","MMLS: MDT tunnel is up, Egress Replication Mode will be disabled","Egress replication is not supported when MDT is configured and an MDT tunnel is up. The system will transition to ingress mode if required, and the transition will cause a temporary loss of traffic.","This message is informational. No action is required."
"MLSM","6","MMLS_MODE_CHANGE","MMLS: Replication Mode Change Detected","When automatic detection of the replication mode is enabled, the system will transition to ingress mode when an egress-incapable module is inserted. The system will transition back to egress mode when the last egress-incapable module is removed.","Transitioning between ingress and egress mode causes a temporary loss of traffic. To prevent this temporary loss of traffic, enter the mls ip replication-mode ingress command."
"MLSM","6","MMLS_NO_EGRESS_LOCAL_IN_INGRESS","MMLS: Egress Local feature is NOT applicable in Ingress mode","When the system transitions from egress replication mode to ingress mode, the egress local feature will not be applied, even if the egress local feature is enabled.","If the egress local feature is required, restore the system replication mode to egress."
"MLSM","6","PVLAN_INSTALL_FAILURE","Unable to locate secondary-vlan for (%i,%i,%d), Flow will be software switched","This message happens when RP was not able to determine the secondary vlan for the source in secondary vlan. After finite retries RP gives up installing the shortcut in hardware. This can happen when a new flow is installed or when there is a RPF change. In such situations, flow will be software switched.","Make sure ARP table is populated for sources in secondary vlan by explicity 'ping'ing the source and the ARP table should contain the primary as well as secondary vlan information. To enable creation of hardware shortcut, do a 'clear ip mroute ' for the specific flow."
"MLSM","6","SCP_ERROR","MMLS: SCP failure detected between RP and SP","This can happen when EOBC channel is too busy or NMP is too busy so that draco side does not get response even after few retries by ICC layer.","Under some stressful condition, when communication between RP and SP side can not be maintained this message will be printed. MMLS will keep trying to recover from situation by sending message to SP. The restart message to SP has exponential back off upto 160 second"
"MLSM","6","SM_INSTALL_FAILURE","interface/mask entry installation failed on %i/%d, vlan%d","This message happens when Interface/mask entry to punt directly connected sources to the router could not be installed in HW-CEF table. This happens, system is running out of available CEF entries. In this situation, there might be blackholing of traffic for the directly connected sources on this interface","Modify the network config such that, hardware resource limitation is not hit and ensure that interface/mask entry is installed."
"MLSM","7","SC_TCAM_FULL_ERROR","TCAM space not available to install the (%i,%i) entry in the Hardware","This message is printed when a (s,g) or (*,g) entry could not be installed in HW-CEF table. This happens when the system is running out of available CEF entries.","Modify the network config such that, hardware resource limitation is not hit and ensure that (s,g) or (*,g) entry is installed."
"MLS_RATE","4","CPP_DISABLED_IN_HW","Control Plane Policing NOT performed in hardware, due to the presence of egress QoS.","CPP cannot be performed in the hardware when the system is running in PFC3A mode and egress QoS is configured on any other interface. Under these circumstances, CPP is performed only in the software until egress QoS is removed from the running configuration.","Remove any egress QoS from the running configuration, or upgrade to a PFC3B or PFC3-BXL. We strongly recommend the upgrade."
"MLS_RATE","4","CPP_RE_ENABLED_IN_HW","Control Plane Policing will now be performed in hardware.","CPP cannot be performed in the hardware when the system is running in PFC3A mode and egress QoS is configured on any other interface. Egress QoS has been removed from the running configuration.","Because egress QoS has been removed, no action is required. To prevent this condition from occurring again, we strongly recommend that you upgrade to a PFC3B or PFC3BXL."
"MLS_RATE","4","DISABLING","The Layer2 Rate Limiters have been disabled.","The Layer 2 rate limiters are turned off with the current hardware configuration because they are not supported with this combination of modules.","Refer to the feature usage guidelines for more details."
"MLS_RATE","4","LIMITING_DOWN","MLS HARDWARE RATE-LIMITING functionality is not active","Memory resources are insufficient to support the rate-limiting functionality.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MLS_RATE","4","NO_DHCP_RESOURCE","DHCP Snooping requires 2 Rate Limiters","There are not enough hardware rate limiters to enable DHCP snooping.","DHCP snooping requires two hardware rate limiters. All may be used. To display the features that use these hardware rate limiters, enter the show mls rate-limit usage command. Unconfigure enough rate limiters to configure DHCP snooping."
"MLS_RATE","4","NO_RESOURCE","The hardware Rate Limiters are fully used","There are no more hardware rate limiters available.","EARL supports a limited number of hardware rate limiters. All may be used. To display the features that use these hardware rate limiters, enter the show mls rate-limit usage command. To program a rate limiter for the new feature, unconfigure one of the configured rate limiters."
"MLS_RATE","4","NOT_SUPPORTED","This functionality is not configurable.","The rate limit functionality is not active with the current hardware configuration.","Refer to the feature usage guidelines for more details."
"MLS_RATE","4","OVERWRITING_PORTSEC_DEFAULT","Port security rate limiter was set to non-default value.","Overwriting the default port security rate value.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"MLS_RATE","4","OVERWRITING_VALUE","Overwriting the rate value for: [chars] case","Some rate limiters share the same hardware register. This message appears if programming a new rate limiter causes a previously configured one to be overwritten.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MLS_STAT","4","IP_CSUM_ERR","IP checksum errors","Packets with IP checksum errors have been received.","No action is necessary. This message is for informational purposes only."
"MLS_STAT","4","IP_LEN_ERR","MAC/IP length inconsistencies","Packets with an IP length that does not match their physical length have been received.","No action is necessary. This message is for informational purposes only."
"MLS_STAT","4","IP_TOO_SHRT","Too short IP packets received","Packets with IP minimum length check errors have been received.","No action is necessary. This message is for informational purposes only."
"MLS_STAT","4","IPX_LEN_ERR","MAC/IPX length inconsistencies","Packets with an IPX length that does not match their physical length have been received.","No action is necessary. This message is for informational purposes only."
"MLS_STAT","4","IPX_TOO_SHRT","Too short IPX packets received","Packets with IPX minimum length check errors have been received.","No action is necessary. This message is for informational purposes only."
"M32X","1","UNAVAILABLE","%s: Channel disable failed","A software or hardware error occurred. The M32X trunk card failed to respond to a request to disable an interface.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"M32X","1","UNAVAILABLE","%s: Channel enable failed","A software or hardware error occurred. The M32X trunk card is not responding to commands used to initialize it.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"M32X","1","UNAVAILABLE","M32X controller %d, channel 0x%x: No Reponse from device. Action Request Timeout","The Action Request for a particular has failed after retry.","LOG_STD_NO_ACTION"
"M32X","1","UNAVAILABLE","M32X down load failed.","The M32X trunk card failed. It could not download its operational microcode.","Perform a power cycle. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"M32X","1","UNAVAILABLE","M32X download failed to complete.","The M32X trunk card has failed. It could not download its operational microcode.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"M32X","1","UNAVAILABLE","M32X slot %d: Init Failed at %s","The M32x trunk card failed to complete hardware initialization.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"M32X","1","UNAVAILABLE","M32X: Download checksum error (sent = 0x%x, received = 0x%x","The download of the internal microcode to the M32X failed to checksum correctly. This usually indicates a hardware failure of the M32X.","Perform a power cycle. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"M32X","1","UNAVAILABLE","Not ready for download.","The M32X trunk card did not respond when commanded to download its operational microcode.Perform a power cycle. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.M32X-3Error Message    %M32X-3-UNAVAILABLE: Device reported %#x Explanation    A hardware error occurred involving the PCI interface for an M32X trunk card.","If it is an M32X trunk card then this is due to a malfunction. Or another PCI device may have been mistaken for an M32X. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"M32X","3","UNAVAILABLE","M32X: %s - packet was less than two bytes","An output packet was detected that was smaller than the minimum allowable datagram size. An error in another driver or an error in the system software probably triggered this error message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"M32X","3","UNAVAILABLE","M32X: Exception %d, trace %d","A software or hardware error has occurred in the M32X trunk card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"M32X","3","UNAVAILABLE","M32X: Stale msg in %s - mbx0:%lx mbx1:%lx mbx2:%lx","The M32X has not responded to a message within a specified time.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"M32X","5","UNAVAILABLE","M32X controller %d, channel %d: remote loopback %s, %s","The interface entered or exited a remote loopback.","No action required."
"MAB","5","UNAVAILABLE","Authentication failed for client (%s) on Interface %s","Authentication was unsuccessful","LOG_STD_NO_ACTION"
"MAB","5","UNAVAILABLE","Authentication successful for client (%s) on Interface %s","Authentication was successful","LOG_STD_NO_ACTION"
"MACSEC","3","UNAVAILABLE","Attempt to learn %e on %s caused configured service instance limit (%u) to be exceeded. Service instance will be shutdown.","The ethernet service instance specified in the system message has been configured for shutdown-mode MAC Security, and is not allowed to learn addresses beyond the limit specified in the system message. This service instance received a frame with unknown source MAC address, and if this address is learnt it would cause the limit to be exceeded. The address has not been learnt, and additionally the service instance has been shutdown.","If the MAC address has to be permitted to be learnt, either increase the MAC Security limit configured on the service instance, or clear the MAC address table for the affected bridge-domain to give this address a chance to be learnt. If this is a genuine violation, no action is needed on the device; instead, locate the cause for the violation and remove it. Once the violation cause has been identified and resolved, re-enable the service instance."
"MACSEC","3","UNAVAILABLE","Attempt to learn denied address %e on %s. Service instance will be shutdown.","The ethernet service instance specified in the system message has been configured for shutdown-mode MAC Security, and has been configured to deny the MAC address specified in the system message. A frame was received from this denied MAC address. The address has not been learnt, and additionally the service instance has been shutdown.","If the MAC address has to be permitted to be learnt, remove the address from the list of denied addresses on the service instance. Otherwise, this is a genuine violation and no action is needed on the device; instead, locate the cause for the violation and remove it. Once the violation cause has been identified and resolved, re-enable the service instance."
"MACSEC","3","UNAVAILABLE","Attempt to move %e from [%s] to [%s]","The MAC address specified in the system message is currently learned on the first ethernet service instance specified in the system message. An ethernet frame with the same MAC address has now been encountered on the second ethernet service instance. This is a violation of MAC Security policy.","If the MAC address has to be permitted to be re-learnt on the second service instance, remove the address from the list of addresses permitted on the first service instance (if applicable), and clear the address from the MAC Address Table. If this is a genuine violation, no action is needed on the device; instead, locate the cause for the violation and remove it."
"MACSEC","3","UNAVAILABLE","Attempt to move %e from [%s] to [%s], shutting down the latter","The MAC address specified in the system message is currently learned on the first ethernet service instance specified in the system message. An ethernet frame with the same MAC address has now been encountered on the second ethernet service instance. This is a violation of MAC Security policy, and as a result the second service instance will be shut down.","If the MAC address has to be permitted to be re-learnt on the second service instance, remove the address from the list of addresses permitted on the first service instance (if applicable), and clear the address from the MAC Address Table. If this is a genuine violation, no action is needed on the device; instead, locate the cause for the violation and remove it. Once the violation cause has been identified and resolved, re-enable the service instance."
"MACSEC","4","UNAVAILABLE","Attempt to learn %e on %s caused configured bridge-domain limit (%u) to be exceeded.","The bridge-domain specified in the system message is not allowed to learn addresses beyond the limit specified in the system message. A service instance belonging to this bridge-domain received a frame with unknown source MAC address, and if this address is learnt it would cause the bridge-domain limit to be exceeded. The address has not been learnt.","If the MAC address has to be permitted to be learnt, either increase the MAC Security limit configured on the bridge-domain, or clear the MAC address table for the affected bridge-domain to give this address a chance to be learnt. If this is a genuine violation, no action is needed on the device; instead, locate the cause for the violation and remove it."
"MACSEC","4","UNAVAILABLE","Attempt to learn %e on %s caused configured service instance limit (%u) to be exceeded.","The ethernet service instance specified in the system message has been configured for restrict-mode MAC Security, and is not allowed to learn addresses beyond the limit specified in the system message. This service instance received a frame with unknown source MAC address, and if this address is learnt it would cause the limit to be exceeded. The address has not been learnt.","If the MAC address has to be permitted to be learnt, either increase the MAC Security limit configured on the service instance, or clear the MAC address table for the affected bridge-domain to give this address a chance to be learnt. If this is a genuine violation, no action is needed on the device; instead, locate the cause for the violation and remove it."
"MACSEC","4","UNAVAILABLE","Attempt to learn denied address %e on %s.","The ethernet service instance specified in the system message has been configured for restrict-mode MAC Security, and has been configured to deny the MAC address specified in the system message. A frame was received from this denied MAC address. The address has not been learnt.","If the MAC address has to be permitted to be learnt, remove the address from the list of denied addresses on the service instance. Otherwise, this is a genuine violation and no action is needed on the device; instead, locate the cause for the violation and remove it."
"MMLS","3","ICROIF_BLOCK_ALLOC_FAILED","Allocation of %s block of indices for egress distribution over fabric failed","The allocation of the block of indices used for egress distribution over the fabric has failed. As a result, the system will not be able to work in egress replication mode. This condition could be caused by a shortage of hardware resources during boot up or at the time when the first block of indices is completely consumed. A shortage of hardware resources might be caused by having too many VLANs configured.","Reduce the number of VLANs in the system by entering the no vlan {vlan_id} command and reloading the system, or configure ingress replication mode by entering the mls ip multicast replication-mode ingress command. Ingress replication mode does not use egress distribution indices."
"MMLS","4","ICROIF_INDICES_EXHAUSTED","Unable to allocate index for egress distribution over fabric","The indices used for egress distribution over the fabric are exhausted and the system is currently unable to allocate an index. An index is allocated for each unique combination of flow over the fabric and is not freed upon removal of all shortcuts using it. An index-freeing mechanism operates when a threshold for freeing up unused indices is reached. If the number of used indices stays above the threshold after collection of unused indices, another block (up to a maximum of two blocks) of 256 indices is allocated.","You may not be required to take any action, as the index-freeing mechanism should take care of freeing up unused indices. If the problem remains, try reducing the number of unique combination of flows over the fabric created by the presence of multicast sources and receivers on different line cards."
"MMLS","4","VLAN_2K_SR_TR_INSTALL_FAILED","Multicast Multi-Layer Switching: Failed to install service reflect translation, hardware resource unavailable","The Multicast Service Reflect translation cannot be installed in hardware as a required hardware resource is unavailable.","Removing tunnel interfaces or reducing the number of service reflect translations would help solve the problem."
"MMLS","6","ADJ_ALLOC_FAILURE","Failed to allocate Adjacency for the multicast flow ([IP_address], [IP_address])","The system is unable to allocate an adjacency for this particular flow. The affected flow will be retried and will be software switched until it is successfully installed in the hardware.","The adjacency table utilization could be very high and needs to be reduced. Removing some hardware switched flows would help solve the problem."
"MMLS","6","BIDIR_ADJ_LIMIT_EXCEEDED","Failed to allocate Adjacency for Bidir Multicast shortcuts, exceeded limit of ([dec]), subsequent flows will be software switched.","The system limit of maximum adjacencies for bidirectional shortcuts has been exceeded. As a result, any new multicast flows will be switched by the software.","The number of bidirectional multicast flows is too large to fit in the hardware. There is no workaround."
"MMLS","6","FIB_LIMIT_EXCEEDED","Failed to allocate FIB entry, exceeded system limit of ([dec]) entries.","The maximum FIB entry limit has been exceeded, so FIB entries cannot be allocated by the MMLS.","The total number of multicast shortcuts is too large to fit in the FIB table and as a result subsequent shortcuts will be software switched. There is no workaround."
"MMLS","6","MCAST_L3FLOW","%s from the Route Processor for Source %i Group %i vlan %d","A multicast flow has been installed or deleted.","No action is required."
"MMLS","6","MCAST_STATUS","IP Multicast Multilayer Switching is %sabled","This message indicates whether the multicast Layer 3 multicast feature is enabled or disabled.","No action is required."
"MMLS","6","MET_LIMIT_EXCEEDED","Failed to allocate MET entry, exceeded system limit of ([dec]) entries. Number of times MET limit is exceeded in the last 1 min : [dec]","The maximum MET entry limit has been exceeded, so MET entries cannot be allocated by the MMLS.","The total number of OIFs is too large to fit in the MET table. Subsequent shortcuts or OIFs will be switched by the software. There is no workaround."
"MMLS","6","MMLS_EGRESS_INCAPABLE_LC_INSERTED","MMLS: Egress incapable line card ([dec]) inserted in forced egress replication mode","An egress-incapable line card is inserted while the system is operating in forced egress replication mode. The user must not source any multicast traffic on this egress-incapable line card.","Verify that there is no multicast traffic going through this egress-incapable line card."
"MMLS","6","MMLS_EGRESS_INCAPABLE_LC_PRESENT","MMLS: Egress incapable line card present while forcing replication mode to egress","There is at least one line card that is egress incapable in the system, but forced egress replication mode is configured on the system. Multicast traffic must not be sourced on the egress-incapable line card.","Verify that there is no multicast traffic going through this egress-incapable line card."
"MMLS","6","MMLS_FSTATS_MAX_PENDING_MSGS","Flow stats enqueued messages count([dec]) has reached the maximum and would be reset to [dec]","This message indicates that flow stats pending messages count has reached the maximum. To avoid further flow stats messages from being dropped, the counter would be reset to match the current pending messages count of the ICCQ.","This message is provided for information only."
"MMLS","6","MMLS_HALF_MET","MMLS: IPv6 multicast enabled on supervisor uplinks. Available MET space on supervisors is halved","The MET space is being halved to enable IPv6 on supervisor engine uplinks.","No action is required."
"MMLS","6","MMLS_LEGACY_LC_PRESENT","MMLS: Legacy line card present, system cannot operate in egress replication mode","There is at least one legacy line card in the system. Therefore, the system cannot operate in egress replication mode when the system is configured for forced egress replication mode.","Remove the legacy line card(s) if you want the system to operate in forced egress replication mode."
"MMLS","6","RPF_ADJ_LIMIT_EXCEEDED","Failed to allocate Adjacency for multicast shortcuts with RPF-vlan: ([dec]), exceeded limit of ([dec]), subsequent flows will be software switched","The system limit of maximum adjacencies for multicast shortcuts with the same RPF has been exceeded. As a result, any new multicast flows will be software switched.","The number of multicast flows with the same RPF interface are too large to fit in the hardware. There is no workaround."
"MMLS","6","RP_LIMIT_EXCEEDED","Failed to allocate DF index for Bidir-RP, exceeded limit of ([dec]) RPs for VPN: ([dec]). Shortcuts for RP: ([IP_address]) will be software switched.","The system limit of four RPs per VPN has been exceeded. As a result, the multicast flows for the groups served by this RP will be software-switched.","The configured RPs are too large to fit in the DF table for one VPN. Attempt to configure the groups among existing RPs in hardware, or configure the RP in another VPN."
"MMLS","6","VLAN_ADD_FAILURE_ON_MET_FULL","Error adding vlan [dec] to the MET table of some shortcuts","The MET table is full and the system is unable to add the VLAN to some shortcuts. The affected shortcuts will not switch traffic for that VLAN.","The MET utilization is very high and must be reduced. Removing some VLANs or switching to ingress replication mode will solve the problem."
"MPLS_ADJ_SB","4","NO_BACKUP_INTF","[chars] - ifnum [dec]","Backup interface cannot be programmed.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"MPLS_COMMON","3","L3_CONFIG_NOT_RECOMMENDED","LAN interfaces have MPLS configured. Do not configure xconnect on interface vlans.","An attempt was made to configure a xconnect on an interface VLAN. The current network configuration has MPLS configured on a LAN interface.","Do not configure xconnects on an interface VLAN if the network has MPLS configured on a LAN interface."
"MPLS_COMMON","3","VPLS_CONFIG_EXCEEDED","The number of EoMPLS/VPLS VCs exceeded the maximum supported on %i/%u.","The number of destination routers or the global number of virtual circuits exceeded the maximum supported by the box.","Refer to network configuration guidelines for the maximum limits"
"MPLS_COMMON","4","ATOM_ON_MPLS_TE_ONLY","AToM traffic supported only on MPLS TE tunnels currently AToM traffic uses interface %s","AToM traffic is supported only on MPLS TE tunnels and not on any other type of tunnels like GRE tunnels. Right now AToM traffic is using the mentioned tunnel interface.","Please make sure AToM traffic does not use non-MPLS TE tunnels."
"MPLS_IPRM","3","DB","[chars]","There is an inconsistency in the information required to request labels from or to process labels received from an IP label distribution module.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_IPRM","3","DB_PATH","[chars]","There is an inconsistency in the information about a prefix path required to request labels from or to process labels received from an IP label distribution module.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_IPRM","3","DB_PNDG_DISC","[chars]","There is an inconsistency in the information about a temporarily deferred action required to populate MPLS forwarding data structures for a prefix.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_IPRM","3","DB_TABLE","[chars]","There is an inconsistency in the information about a (VRF) table ID required to request labels from or to process labels received from an IP label distribution module.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_IPRM","3","DB_TRANS","[chars]","There is an inconsistency in the information about an ongoing transaction required to populate MPLS forwarding data structures for a prefix.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_IPRM","3","INTERNAL","[chars]","An operation required for proper operation of the IP rewrite manager has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_IPRM","3","PATH_LABEL_DEL","[chars]","An attempt to delete MPLS forwarding information for the specified prefix has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_IPRM","3","PATH_LABEL_GET","[chars]","An attempt to access MPLS forwarding information for the specified prefix has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_IPRM","3","PATH_LABEL_UPD","[chars]","An attempt to update MPLS forwarding information for the specified prefix has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_IPRM","3","WALK","[chars]","A request by an IP label distribution module (for example, LDP, BGP) to walk a CEF table cannot be handled.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MMLS_RATE","3","MMLS_PARTIAL_SC_ERROR","Error installing Multicast Partial-sc rate-limiter.Operation failed.","The multicast partial SC rate limiter could not be configured because of an error that was returned from the switch processor.","The LTL index for the partial SC rate limiter might not have initialized yet. Wait several minutes, and try to configure the rate limiter again."
"MPLSOAM","3","XDR_COMM","%s:0x%x 0x%x","The XDR communication module reports an unexpected RP/LC XDR condition encountered in the MPLS OAM software. This condition may result in MPLS OAM FIB subblocks becoming out of synchronization between the RP and the line card. This condition should not affect overall system operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_PACKET","3","FWDDISABLE","MPLS [chars] forwarding path disabled","The MPLS forwarding plane has been disabled.","This log entry is informational only. No action is required."
"MPLS_PACKET","3","FWDREENABLE","MPLS [chars] forwarding path reenabled","The MPLS forwarding plane has been reenabled.","This log entry is informational only. No action is required."
"MPLS_PACKET","3","LABELCACHE","[chars] [dec]/[dec]","An MPLS label cache error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_PACKET","4","NOLFDSB","MPLS packet received on non MPLS enabled interface [chars] L3 type [hex] label {[dec] [dec] [dec] [dec]}","MPLS packets received on an interface are being dropped as the interface is not setup to handle MPLS. This message may appear when an MPLS application is disabled on a interface, and should disappear when the upstream neighbor has reprogrammed its CEF and MPLS entries.","If an MPLS application has just been disabled and traffic is flowing, this message is expected and should be ignored. If the message recurs in steady state, the operator should monitor the network for attacks and report the occurrence to Cisco."
"MPLS_TE","2","ADJ_WALK_ERR","[chars]","An error occurred during a bundle adjacency walk.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_TE","2","BUNDLE_INSERT","[chars][chars]","A request for inserting a traffic engineering tunnel bundle failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_TE","2","UNSUPPORTED_LINK_TYPE","[chars]","An unsupported link type was detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_TE","3","LSDERROR","[chars]: [chars] [chars]","A traffic engineering request to the label switching database encountered an unexpected condition.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_TE_AUTOMESH","5","AUTOTEMPLATE_HWIDB_DELETE","Failed to delete hwidb for Auto-Template %d index %d","The deletion of a hardware interface descriptor block (HWIDB) for an auto-template interface failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_TE_AUTO_TUN","3","UNAVAILABLE","Unexpected data structure access. %s unlocks with count %u, but expected %u (%u failure%s). MPLS_TE_AUTO_TUN_STD_CONFIRM","MPLS_TE_AUTO_TUN_STD_LOCK_EXPLANATION","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_TE_AUTO_TUN","3","UNAVAILABLE","Unexpected data structure access. %s unlocks with count %u, but not locked (%u failure%s). MPLS_TE_AUTO_TUN_STD_CONFIRM","MPLS_TE_AUTO_TUN_STD_LOCK_EXPLANATION","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_TE_AUTO_TUN","3","UNAVAILABLE","Unexpected data structure access. Non-zero lock count %u when %s locks (%u failure%s). MPLS_TE_AUTO_TUN_STD_CONFIRM","MPLS_TE_AUTO_TUN_STD_LOCK_EXPLANATION","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_TE_AUTO_TUN","4","UNAVAILABLE","Removing existing auto tunnels may have failed.%s%s MPLS_TE_AUTO_TUN_STD_CONFIRM Use show running-config to confirm expected configuration. Repeat CLI configuration as needed.","The MPLS Traffic Engineering Auto-Tunnel software detected a possible problem removing existing automatic tunnels. It may be necessary to repeat the CLI action that caused the removal and reconfiguration of automatic tunnels.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_TE_LM","3","LSP_BAD_ENCODING_TYPE","LSP [chars] requesting Encoding Type [[chars]] that is unsupported on interface [chars].","The indicated TE LSP, routed on the indicated interface, requested an encoding type that is unsupported on the interface. The requested value appears in the Generalized Label Request.","Verify that the head end originating the TE LSP has a Generalized Label Request that is specifying an encoding type acceptable to the interface in question. If not, alter the head end configuration to request an LSP with an appropriate value, or cause the LSP to be routed on a different interface. If this problem still persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. Also provide a topology diagram showing the hops in the LSP, marking each hop with the vendor and software, and identify which hop is the Cisco IOS device issuing the error message."
"MPLS_TE_LM","3","LSP_BAD_GPID","LSP [chars] requesting G-PID [[chars]] that is unsupported on interface [chars][chars].","The indicated TE LSP, routed on the indicated interface, requested a (Generalized) Payload Identifier unsupported on the interface. The requested value appears in the Label Request and Generalized Label Request.","Verify that the head end originating the TE LSP has a Label Request that is specifying a PID acceptable to the interface in question. If not, one possibility is to alter the head end configuration to request an LSP with an appropriate value. Alternatively, if this error is generated at the penultimate hop of an LSP where the endpoint is advertising an implicit-null label (penultimate hop popping is in use), alter the endpoint to advertise an explicit-null label. If this problem still persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. Also provide a topology diagram showing the hops in the LSP, marking each hop with the vendor and software, and identify which hop is the Cisco IOS device issuing the error message."
"MPLS_TE_LM","3","LSP_BAD_SWITCHING_TYPE","LSP [chars] requesting Switching Type [[chars]] that is unsupported on interface [chars].","The indicated TE LSP, routed on the indicated interface, requested a Switching Type that is unsupported on the interface. The requested value appears in the Generalized Label Request.","Verify that the head end originating the TE LSP has a Generalized Label Request that is specifying a Switching Type acceptable to the interface in question. If not, alter the head end configuration to request an LSP with an appropriate value, or cause the LSP to be routed on a different interface. If this problem still persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. Also provide a topology diagram showing the hops in the LSP, marking each hop with the vendor and software, and identify which hop is the Cisco IOS device issuing the error message."
"MPLS_TE_LM","5","UNAVAILABLE","Clear MPLS TE Link Management counters by %s","The MPLS TE Link Management counters have been cleared","LOG_STD_NO_ACTION"
"MPLS_TE_PCALC","2","UNAVAILABLE","%s %d","A failure at an attempt to alloc memory was detected","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_TE_PCALC","2","UNAVAILABLE","%s %i %s","Two nodes have the same stable ip address","Find the system that has the duplicate ip address and configure a different one"
"MPLS_TE_PCALC","2","UNAVAILABLE","%s %i %s","Two nodes have the same stable router id","Find the system that has the duplicate router id and configure a different one"
"MPLS_TE_PCALC","2","UNAVAILABLE","Invalid router id (%i) received from %s in fragment %lu","Received an Invalid Router LSA. LSA should not contain a Router id of zero. The cause of this problem may be misconfiguration, memory corruption or unexpected behaviour on a router","Locate the problem router and check the configuration. To determine what is causing this problem, call your Cisco technical support representative for assistance."
"MPLS_TE_PCALC","2","UNAVAILABLE","Router id (%i) received from %s in fragment %lu, previously received in fragment %lu","Received Router ID in multiple fragments","Locate the problem router and contact your Cisco technical support representative for assistance."
"MPLS_TE_PCALC","3","UNAVAILABLE","%s %s","An internal inconsistency was detected when an attempt was made to establish handle received lsa for MPLS TE topology database.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_TE_PCALC","3","UNAVAILABLE","%s","An internal inconsistency was detected when an attempt was made to establish an MPLS TE tunnel using the MPLS TE path calculation subsystem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_TE_PCALC","3","UNAVAILABLE","pcalc_system_id_size == 0","An internal inconsistency was detected when an attempt was made to initialize the MPLS TE path calculation system id before the system_id size is known.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_VPN_HA","3","CF_GEN_ERROR","[chars]","A general error occurred related to the MPLS VPN HA client CF.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_VPN_HA","3","CLIENTREG","[chars]","The MPLS VPN HA failed to register to CF.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_VPN_HA","3","DBOPERATION","[chars] RD [chars], [IP_address]/[dec], label [dec]","An error occurred related to an MPLS VPN HA checkpoint database operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_VPN_HA","3","SIZEMISMATCH","Label table size ([dec]) mismatch, get label tableid failed.","A mismatch has been detected in the table size of the MPLS VPN HA facility.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_VPN_HA","7","LABELFREE","[chars] [dec]","The MPLS VPN label manager failed to free a label.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_VPN_HA","7","MALLOCFAIL","[chars]","The MPLS VPN HA facility failed to allocate memory.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_VPN_HA","7","XMITFAIL","[chars], message seq no [dec], current seq no [dec]","The MPLS VPN label manager has failed to deliver a message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_VPN_ISSU","3","CF_ERR","[chars] [hex]","An error occurred related to the MPLS VPN ISSU client CF.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_VPN_ISSU","3","GENERR","[chars]","An error occurred related to the MPLS VPN ISSU client.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPLS_VPN_ISSU","3","ISSU_RC_ERR","[chars] [chars]","An error occurred related to the MPLS VPN ISSU client.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPOA","3","UNAVAILABLE","%s","A software error has occurred in the multiprotocol-over-ATM server (MPS) software.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPOA","3","UNAVAILABLE","%s","A software error has occurred in the multiprotocol-over-ATM client (MPC) software.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPOA","3","UNAVAILABLE","%s","A software error has occurred in the multiprotocol-over-ATM subsystem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPOA","4","UNAVAILABLE","%s","This is a non-fatal warning from the multiprotocol-over-ATM client (MPC) software, probably the result of an incorrect configuration or operator command. Details about the warning are included in the message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPOA","4","UNAVAILABLE","%s","This is a non-fatal warning from the multiprotocol-over-ATM server (MPS) software, probably the result of an incorrect configuration or operator command. Another possible but less likely cause could be an internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MPOA","5","UNAVAILABLE","%s","A multiprotocol-over-ATM entity was brought up or down. This is only a status message.","LOG_STD_NO_ACTION"
"MPOA","6","UNAVAILABLE","%s","This is a multiprotocol-over-ATM client (MPC) status/information message","LOG_STD_NO_ACTION"
"MPOA","6","UNAVAILABLE","%s","This is a multiprotocol-over-ATM server (MPS) status/information message","LOG_STD_NO_ACTION"
"MRIB_PROXY","2","MRIB_LC_CREPRC_FAILED","LC in slot [dec] failed to create a required process.","The line card could not create a process to perform delayed IPC initialization. The MFIB will not be started on this line card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MRIB_PROXY","2","MRIB_LC_FAILED_GET_IPC","LC failed allocating IPC buffer which may lead to data loss or inconsistent MFIB states, slot = [dec]","The line card has failed in allocating an interprocessor communication buffer.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"MRIB_PROXY","2","MRIB_LC_FAILED_IDB_MAP","LC failed in mapping interface number [dec]","The line card failed in mapping an interface from the global representation to the local one.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MRIB_PROXY","2","MRIB_LC_FAILED_IPC_ACK","RP failed in getting Ack for IPC message of type = [dec], status = [dec], error = [chars]","The route processor has failed to get IPC acknowledgement.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MRIB_PROXY","2","MRIB_LC_FAILED_IPC_OPEN","LC in slot [dec] failed to open IPC port to RP, error = [chars]","The line card has failed to open an IPC port towards the route processor.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MRIB_PROXY","2","MRIB_LC_FAILED_SEND_LC_READY","LC in slot [dec] failed to send LC ready to RP, error = [chars]","The line card has failed to send a ready message to the route processor.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MRIB_PROXY","2","MRIB_LC_FETCH_FAIL","LC in slot [dec] failed to send an RPC fetch request to the RP: [chars]","The line card attempted to read mroute updates from the route processor but the RPC request failed. The line card MFIB state may now be inconsistent or frozen.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MRIB_PROXY","2","MRIB_LC_READY_NOIPC","LC failed allocating IPC buffer to send LC ready, slot = [dec]","The line card has failed to allocate an interprocessor communication buffer to send the ready message.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"MRIB_PROXY","2","MRIB_LC_UPDATE_IGNORED","LC in slot [dec] ignored one or more mroute updates","The line card ignored one or more mroute updates because the buffer containing them failed a sanity check. The line card MFIB state may now be inconsistent.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MRIB_PROXY","2","MRIB_RP_FAILED_GET_IPC","RP failed allocating IPC buffer which may lead to data loss or inconsistent MFIB states","The route processor has failed to allocate an interprocessor communication buffer.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MRIB_PROXY","2","MRIB_RP_FAILED_IDB_MAP","RP failed in mapping interface","The route processor failed to map an interface from the global representation to the local one, or vice versa.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MRIB_PROXY","2","MRIB_RP_FAILED_IPC_ACK","LC failed in getting Ack for IPC message of type = [dec], status = [dec], error = [chars]","The line card has failed to get an IPC acknowledgement.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MRIB_PROXY","2","MRIB_RP_FAILED_IPC_CREATE","RP failed in creating IPC port, error = [chars]","The route processor failed to create an MFIB interprocess communications port.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MRIB_PROXY","2","MRIB_RP_FAILED_LC_DIST_MODE_INIT_PROC","RP failed in creating distribute mode init process for a linecard, slot = [dec]","The route processor failed to create a distribute mode initialization process for a line card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MRIB_PROXY","2","MRIB_RP_FAILED_LC_PORT_INFO","RP failed in creating linecard port info for distributed mode, slot = [dec]","The route processor failed to create line card port information for distributed mode.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MRIB_PROXY","2","MRIB_RP_FAILED_LC_PORT_OPEN","RP failed in opening linecard port info for distributed mode, slot = [dec]","The route processor failed to open line card port information for distributed mode.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MRIB_PROXY","2","MRIB_RP_FAILED_RPC_REPLY","RP failed in sending [chars] reply to a linecard in slot = [dec], IPC error = [chars]. This is normal after linecard removal or reset. At other times, data loss or mroute state inconsistency may result.","The route processor has failed in sending a remote procedure call reply to a line card. This is normal after line card removal or reset. At other times, data loss or mroute state inconsistency may result.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MROUTE","2","RADIXINIT","Error initializing IP multicast radix for %i","Insufficient memory is available to initialize the IP multicast routing table.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MROUTE","3","IGMP_LATE_PROCESS_ERR","IGMP process is not up yet","An error occured accessing IGMP process watched queue","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MROUTE","3","IGMP_NOT_FOUND","IGMP group [IP address] to delete from interface [chars] not found in VRF [chars]","An inconsistency in maintaining the IGMP cache occurred. The group to be deleted from the interface could not be found in the IGMP cache for the VRF. [IP address] is the IP address in the IGMP group, the first [chars] is the interface, and the second [chars] is the VRF.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MROUTE","3","IGMP_TWHEEL_INIT_ERR","Error trying to initialize the IGMP timer wheel","An error occurred during the initialization of a timer wheel.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MROUTE","3","IGMP_WAVL_ERROR","IGMP wavl [chars] failed for group [IP_address] in interface [chars]","The addition/deletion of igmp group in wavl tree failed.","Collect show tech ipmulticast command output. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"MROUTE","3","MIDB_QUEUE_ERR","Interface %s not in (%i, %i)","The MIDB has the highest expiration timer but was not in the MDB->MIDB.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MROUTE","3","NO_PIM_NBR","There is no PIM neighbor on this IDB: [chars]","There is no PIM neighbor on the specified IDB. The most probable cause of this error is that PIM is not configured correctly on this interface or on interfaces of the next-hop routers.","Check PIM configurations on local and neighbor routers. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MROUTE","3","RECUR_ROUTE_DEPTH_ERR","Recursive route lookup has reached its max depth for: [IP_address]","The recursive route lookup has reached its predefined maximum depth limit.","If possible, reduce the number of rounds of next-hop lookup needed for the network address in question. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MROUTE","3","ROUTECOUNT_ZERO","Multicast route count reached zero","The running count of multicast routes reached zero when it should be non-zero.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MROUTE","3","TWHEEL_DELAY_ERR","Exceeded maximum delay (%d ms) requested: %d","An attempt was made to schedule a function with a higher delay than the maximum allowed. The function will be scheduled using the maximum delay possible.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MROUTE","3","TWHEEL_ERR","Timer wheel internal error","A timer wheel internal error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MROUTE","3","TWHEEL_INIT_ERR","Trying to re-initialize an already initialized timer wheel","An error occurred while intializing a timer wheel.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MROUTE","3","TWHEEL_INSERT_ERR","An error occured after inserting or executing a timer wheel event","An error occurred after inserting or executing a timer wheel event.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MROUTE","3","TWHEEL_INT_ERR","Timer wheel error at interrupt level %d","A timer wheel internal error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MROUTE","3","TWHEEL_SLOT_ERR","Timer wheel event:%x slot:%d func:%x unequal to exec slot: %d","The timer wheel event has an inconsistent slot number.","Enter the clear ip mroute command to delete entries from the IP multicast routing table. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MROUTE","3","WAVLINIT","Could not initialize WAVL tree for (%i,%i)","The WAVL tree could not be initialized, so the system canot search for Multicast Interface Data Blocks (MIDBs).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MROUTE","4","INCONSISTENT_IDB_TABLEID","PIM detected inconsistency in table-id information on [chars].","The PIM has detected that the interface table ID value is not the same as the value maintained by the multicast code.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MROUTE","4","MROUTELIMIT","Exceeded multicast limit for group %i, source %i on interface %s","The allowed number of multicast routes having the incoming or outgoing interface reached the limit specified by a configured access list. New routes cannot be added unless the interface configuration is changed.","If multicast traffic over the interface is of any priority among the traffic carried by this router, then enter the ip multicast limit interface command to increase the number of multicast routes. Otherwise, no action is required. Enter the debug ip mroute limit command or the show ip multicast limit command to learn which multicast interface limit was exceeded."
"MROUTE","4","MTU_MISMATCH","WARNING: With IP multicast enabled, interfaces which transmit traffic from larger to smaller MTU interfaces may not be hardware switched due to fragmentation. A degradation in performance may occur.","With IP multicast enabled, interfaces that transmit traffic from larger to smaller MTU interfaces may not be hardware switched due to fragmentation. A degradation in performance may occur.","Set the MTU values on all interfaces to be identical."
"MROUTE","4","RADIXDELETE","Error trying to delete multicast route entry %i/%d for %i (expected %#x, got %#x)","A route could not be deleted from the routing table.","Enter the clear ip mroute command to delete entries from the IP multicast routing table. Determine whether the router is low on memory. If the problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MROUTE","4","RADIXINSERT","Error trying to add multicast route entry %i/%d for %i (expected %#x, got %#x)","A route could not be inserted into the routing table.","Enter the clear ip mroute command to delete entries from the IP multicast routing table. Determine whether the router is low on memory. If the problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MROUTE","4","REGISTER_SOURCE_CONFIG","Removing pim register source configuration for [chars]","The register source interface was deleted, or its IP address was removed, or its VRF forwarding was changed.","Check the ip pim register-source configuration."
"MROUTE","4","ROUTELIMIT","Current count of %u exceeds multicast route-limit of %d","The number of multicast routes equals the configured maximum allowed. New routes cannot be added unless the configuration is changed.","If multicast traffic is of any priority among the traffic carried by this router, then use the ip multicast route-limit command to increase the number of multicast routes. Otherwise, no action is required."
"MROUTE","4","ROUTELIMIT_ATTEMPT","Attempt to exceed multicast route-limit of [dec]","The number of multicast routes equals the configured maximum allowed. New routes cannot be added unless the configuration is changed.","If multicast traffic is of any priority among the traffic carried by this router, then enter the ip multicast route-limit command to increase the number of multicast routes. Otherwise, no action is required."
"MROUTE","4","ROUTELIMITWARNING","multicast route-limit warning (curr %u threshold %u)","The number of multicast routes reached the configured percentage of the multicast route-limit.","Increase the multicast route-limit."
"MROUTE","4","RPF_LOOKUP_LOOP","RPF route lookup loop for %i, route %i/%d","A routing loop exists, possibly caused by routers reverse path forwarding to different tables .","Check the routing tables used for reverse path forwarding (RPF)."
"MROUTE","6","LARGE_TWHEEL_DELAY","Exceeded maximum delay (%d ms) requested: %d","An attempt was made to schedule a function with a higher delay than the maximum allowed. The function will be scheduled using the maximum delay possible minus a small delay offset.","Check whether a large IGMP query-interval is set. Some timers may refresh periodically to allow for the large delay."
"MSC100_SPA_CC","0","FPGA_BAY_ERROR_EXCEED_LIMIT","[chars] detected [chars] exceed limit ([dec]) (hardware-status = [hex])","A critical FPGA error was detected on the SPA or carrier card for the specified subslot. The SPA in this subslot has been disabled.","Try to reactivate the card using the hw-module subslot slot-number/subslot-number start command. If the error persists, enter the show diag slot-number command to gather data that may help identify the cause of the error. If you cannot determine the cause of the error from the error message text or from the show diag slot-number output, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MSC100_SPA_CC","0","FPGA_ERROR","[chars] Slot [dec]: Hardware error detected [[chars]]","A critical FPGA error was detected on the carrier card. The carrier card is deactivated and then an automatic recovery is initiated. If a similar error occurs more than five times within an hour, the carrier card is deactivated.","If the line card is no longer automatically reactivating, copy the error message exactly as it appears on the console or in the system log. Enter the show diag slot-number command to gather data that may help identify the cause of the error. If you cannot determine the cause of the error from the error message text or from the show diag slot-number output, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MSC100_SPA_CC","0","FPGA_ERROR_EXCEED_LIMIT","[chars] Slot [dec] detected [chars] exceed limit ([dec]) (hardware-status = [hex])","A critical FPGA error was detected on the carrier card. The carrier card is deactivated and then an automatic recovery is initiated. If a similar error occurs more than five times within an hour, the carrier card is deactivated.","If the line card is no longer automatically reactivating, copy the error message exactly as it appears on the console or in the system log. Enter the show diag slot-number command to gather data that may help identify the cause of the error. If you cannot determine the cause of the error from the error message text or from the show diag slot-number output, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MSC100_SPA_CC","0","MISSING_RP_FPGA_SUPPORT","The 7304-MSC-100 in slot [int] has been deactivated because the RP FPGA requires an upgrade.","The MSC-100 SPA carrier card in the specified slot requires a particular version of the RP FPGA. The MSC-100 will be deactivated until this FPGA incompatibility is addressed.","Enter the upgrade fpga all command to upgrade the RP FPGA. After upgrading the RP FPGA, reactivate the MSC-100 by removing and reinserting the MSC-100."
"MSDP","3","DNS_ERROR","DNS lookup time out. DNS lookup for ssm mapping will be disabled for 60 sec","DNS source lookup timeout. DNS server not respond to the DNS query, this may be due to DNS server is down. DNS lookup will be stopped for next 60 sec.","Disbale DNS ssm mapping till the DNS server come up. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"MSDP","3","NO_RPF_NODE","SA message could not be sent to peer [IP_address]. Expecting RPF node with host address [IP_address] but found node with host [IP_address] in the rpf tree.","The reverse path forwarding (RPF) node could not be found while sending a Source-Active (SA) message to the peer. The SA will not be sent in this period.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MSDP","4","PKT_TOO_BIG","Message size violation on %u-byte packet from %i, discarded","A message larger than the maximum MSDP message size was received. This message could also indicate an internal error.","Obtain the manufacturer and the version information of the router that sent the oversize packet. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show version commands and your pertinent troubleshooting logs."
"MSDP","4","SA_LIMIT","SA from peer %i, RP %i for (%i, %i) exceeded sa-limit of %d","The number of MSDP SAs exceeds the configured maximum number. SA cache entries cannot be added unless the configuration is changed.","If the MSDP SAs come from legitimate sources or RPs, then enter the ip msdp sa-limit command to increase the number of SA entries allowed from the subject peer. Otherwise, no action is required."
"MSDP","5","PEER_IS_SELF","Peering with self (%i)","Multicast Source Discovery Protocol (MSDP) on this device is peering with itself.","Check the address of the intended MSDP peer."
"MSDP","5","PEER_UPDOWN","Session to peer %i going %s","A session to an MSDP peer going up or down.","Determine whether the router is low on memory."
"MSDP","5","PEER_IS_SELF","Peering with self ([IP_address])","MSDP peering with ourselves","Check the address of the MSDP peer."
"MSPI","1","UNAVAILABLE","MSPI-bad configuration, %s","A configuration error was detected.","Add or fix the Dial Peer configuration"
"MSPI","1","UNAVAILABLE","msgtxt_nomemory","The requested operation could not be accomplished because of a low memory condition.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"MSPI","2","UNAVAILABLE","MSPI-Internal software error, cid=%d, %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MSPI","2","UNAVAILABLE","MSPI-bad context pointer, %s","A bad context pointer was passed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MSPI","4","UNAVAILABLE","MSPI- Bad message received: %s","An unexpected message was received.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MSPI","4","UNAVAILABLE","MSPI- Can't connect to the SMTP server, cid=%d, %s","No connection was created to the specified SMTP server.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MSPI","4","UNAVAILABLE","MSPI- Could notsend data to the SMTP server, cid=%d, %s","A connection was made to the SMTP server, but no data can be sent.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MSPI","4","UNAVAILABLE","SMTP- failed %s, %d","A connection attempt to a remote mail server was not successful. This unexpected behavior.","LOG_STD_NO_ACTION"
"MSPI","6","UNAVAILABLE","SMTP- opening %s, %d","A connection attempt ...","LOG_STD_NO_ACTION"
"MSFC2","3","IDB_INCORRECT_UNTHROTTLE_VECTOR","attempting to throttle idb [hex] ([chars]) with enable vector [hex]","An invalid interface enable vector was detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MSFC2","3","TOOBIG","Attempt to send giant packet on [chars] ([dec] bytes from [hex], max allowed [dec])","An attempt was made to send an oversized packet. This message typically appears when the Layer 3 switch is not fragmenting packets with a message size larger than 1500 bytes.","Increase the interface MTU size."
"MTRIE","4","MTRIECORRUPTLEAF","[IP_address]/[dec] - [chars]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MTRIE","4","MTRIELEAFOPFAIL","[IP_address]/[dec] - [chars]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MTRIE","4","PLACEALLOC","Failed to allocate place holder","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MUESLIX","1","UNAVAILABLE","%s: %s%s: 0x%08x, 0x%08x","Pull the info from the port adaptor to show what error caused the STOPFAIL/STARTFAIL problem.","Enable 'debug serial mueslix' debug command. Then collect the 'show tech' and 'show log' information and send them to the technical support representative. After that you can disable the 'debug serial mueslix' command."
"MUESLIX","1","UNAVAILABLE","%s: Start Failed at %s","The Mueslix serial interface is not responding to commands used to initialize it.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MUESLIX","1","UNAVAILABLE","%s: Stop Failed at %s","The Mueslix serial board failed to respond to a request to disable an interface.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MUESLIX","1","UNAVAILABLE","%s:Link is brought %s due to clock rate change, threshold configured = %u, received clock rate = %u","The received clock rate is changed from below the threshold configured to above or vice versa..","Check the received clock rate from the provider end, if the clock rate falls below the threshold configured"
"MUESLIX","1","UNAVAILABLE","MUESLIX slot %d: Init Failed at %s","The Mueslix serial board failed to complete hardware initialization.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MUESLIX","1","UNAVAILABLE","Mueslix microcode down load failed.","The Mueslix serial hardware failed. Hardware could not download microcode into mueslix chip.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MUESLIX","1","UNAVAILABLE","Mx serial (bay %d), Init Failed at %s","The Mx serial port adaptor failed to complete hardware initialization.","Try to reseat the PA properly in the system slots. If the error still happens, then verify for the hardware failure including the 7200 chasis in case of 7200 or vip in case of 7500 and the PA as this error will come only if there is a failure in hardware."
"MUESLIX","1","UNAVAILABLE","Mx serial (bay %d): PA down load failed","The Mx serial hardware failed. It could not download its operational microcode.","Try to reseat the PA properly in the system slots. If the error still happens, then verify for the hardware failure including the 7200 chasis in case of 7200 or vip in case of RSP and the PA as this error will come only if there is a failure in hardware."
"MUESLIX","1","UNAVAILABLE","Mx serial, %s Start Failed at %s","A software or hardware error occurred. The Mx microcode is not responding to the enable command used to restart the serial interface","Enable 'debug serial mueslix' debug command. Then collect the 'show tech' and 'show log' information and send them to the DE team or CSE team. After that you can disable the 'debug serial mueslix' command."
"MUESLIX","1","UNAVAILABLE","Mx serial, %s Stop Failed at %s","A software or hardware error occurred. The Mx microcode is not responding to the disable command used to stop the serial port.","Enable 'debug serial mueslix' debug command. Then collect the 'show tech' and 'show log' information and send them to the technical support representative. After that you can disable the 'debug serial mueslix' command."
"MUESLIX","1","UNAVAILABLE","Mx serial: %s TPU halted: cause 0x%2x status 0x%08x shadow 0x%08x","The Mx serial firmware is not in sync with the driver.","This conditions will clear by itself. Enable 'debug serial mueslix' debug command. Then collect the 'show tech' and 'show log' information and send them to the DE team or CSE team. After that you can disable the 'debug serial mueslix' command."
"MUESLIX","3","ERROR","%s","General error information.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MUESLIX","3","UNAVAILABLE","%d packet buffer, pak=0x%x","A software or hardware error occurred. The Mx serial driver detected that the transmit ring is in an inconsistent and unrecoverable state.","Enable 'debug serial mueslix' debug command. Then collect the 'show tech' and 'show log' information and send them to the DE team or CSE team. After that you can disable the 'debug serial mueslix' command."
"MUESLIX","3","UNAVAILABLE","%s","General error information.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MUESLIX","3","UNAVAILABLE","Mx serial (bay %d): Device reported %#x","The system hardware failed. A non-Mx serial device pointed at the Mx serial software.","Check the system configuration for the failure in the bay number that is reported in the error message. If it is not a mueslix based PA, then contact the appropriate component to which that PA belongs. If it is a mueslix based PA, then try to reseat the PA once agian and if the error still comes, then collect the 'show tech' and 'show log' information at the time of this problem and send it to the technical support representative"
"MUESLIX","3","UNAVAILABLE","Mx serial (bay %d): Interface found: %d","The system couldn't able to recognize all the Mueslix devices that are there on the system","Try to reseat the PA properly in the system slots. If the error is still happening, then verify for the hardware failure including the 7200 chasis in case of 7200 or vip in case of RSP and the PA as this error will come only if there is a failure in hardware."
"MUESLIX","3","UNAVAILABLE","Unit %d, buffer ownership error, pak = 0x%x","The Mueslix serial driver detected that the transmit ring is in an inconsistent state.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MUESLIX","4","UNAVAILABLE","%s %s","User has changed the dsu bandwidth using DS3 remote management commands. This won't change the user configured dsu bandwidth","Copy the error message exactly as it appears, and report it to your technical support representative."
"MVR_RP","3","OPER_PORT_SET_FAILED","MVR port operational type setting failed. Reason: %d","MVR source/receiver port operational type setting on SP failed because of failure on SP or ICC failure.","Unconfigure MVR type from this switchport and configure it back"
"MVR_RP","6","RCVR_ACCESS_PORTMODECHNG","%s MVR type receiver on %s, this access port %s MVR vlan","MVR type reciever should not be configured on a MVR vlan port. Since this port is configured as dynamic auto/desirable and due to mode change in the neighboring switch the operational switchport mode on this switch has become access and the corresponding vlan is MVR vlan","Either unconfigure MVR type receiver from this switchport or change the access vlan to non-MVR vlan"
"MVR_RP","6","RCVR_TRUNK_PORTMODECHNG","%s MVR type receiver on %s, MVR type receiver should not be configured on trunk ports","MVR type reciever should not be configured on a trunk port. Since this port is configured as dynamic auto/desirable and due to mode change in the neighboring switch the operational switchport mode on this switch has become trunk, MVR type receiver should be disabled","Either unconfigure MVR type receiver from this switchport or change the mode to access and vlan to non-MVR vlan"
"MVR_RP","6","SRC_ACCESS_PORTMODECHNG","%s MVR type source on %s, this access port %s MVR vlan","MVR type source should not be configured on a non-MVR vlan port. Since this port is configured as dynamic auto/desirable and due to mode change in the neighboring switch the operational switchport mode on this switch has become access and the corresponding vlan is non-MVR","Either unconfigure MVR type source from this switchport or change the access vlan to MVR vlan"
"MVR_RP","6","SRC_TRUNK_PORTMODECHNG","%s MVR type source on %s, this trunk port allowed vlans %s MVR vlan","MVR type source should not be configured on a non-MVR vlan port. Since this port is configured as dynamic auto/desirable and due to mode change in the neighboring switch the operational switchport mode on this switch has become trunk and the corresponding vlan range does not contain MVR vlan","Either unconfigure MVR type source from this switchport or change the trunk allowed vlan range to include MVR vlan"
"MVRP","3","ADD_REGISTRY_FAILED","MVRP subsystem fails to add callback function %s","Another subsystem has mistakenly added its own callback functions. This message is for debugging purposes.","No action is required."
"MVRP","3","ENABLE_FAILED","MVRP can't be enabled because %s","Multicast VLAN Registration Protocol (MVRP) cannot be enabled for the specified reason.","Take action according to the specified reason. For example, if the failure is due to insufficient memory, add more memory to the system."
"MVRP","3","HA_INIT_FAILED","MVRP High Availability subsystem fails to be initialized and hence MVRP won't support HA stateful switchover.","The MVRP CF client or the MVRP RF client failed to initialize.","Enter the show redundancy clients command and the show checkpoint clients command to learn which client was not initialized."
"MVRP","3","SUBSYS_INIT_FAILED","MVRP subsystem failed in initialization(%s) and MVRP won't function properly.","MVRP could not initialize, probably due to insufficient memory. Other accompanying system messages may provide further information about the failure.","Enter the show memory summary command to check the memory usage. Contact the TAC with the output of the show memory summary, show version, and show run commands and the associated syslog messages from the time of the problem."
"MVRP","6","MODECHANGE","The operating mode is changed to %s mode on interface %s.","As a result of protocol negotiation, the operating mode changed to the specified mode on the specified interface.","No action is required."
"MVRP_CONST","3","MAC_MATCH_REG_FAILED","Unable to reserve needed MAC match register - cannot run MVRP on interfaces of slot %d","Multicast VLAN Registration Protocol (MVRP) attempted to reserve a MAC match register for the slot indicated, but there is no dedicated register or programmable register available. MVRP cannot be activated on interfaces of this card.","Disable conflicting protocols that use the MAC match register or use a different card type that supports MVRP."
"MVRP_CONST","6","FEATURE_CONFLICT","Failed to enable MVRP on %s because conflicting feature %s is enabled on the interface","MVRP could not be enabled on the given interface because of conflicting features. For example, unknown unicast flood blocking(UUFB) and MVRP cannot be enabled on the same interface.","If MVRP is required on the interface, enter the show running-config interface command to investigate whether incompatible features are enabled on the interface."
"MVRP_CONST","6","MAC_LEARNING","MAC learning on VLAN %s is %s","If only two MVRP ports are forwarding and not pruned in a VLAN, MVRP will disable MAC learning on that VLAN in order to save room in the MAC table, which is a limited system-wide resource.","No action is required."
"MVRP_CONST","6","MAC_LRN_SETTING_FAILED","Failed to %s MAC learning on VLAN %s","MVRP failed to enable or disable MAC learning on the given VLAN, probably because MAC learning was already configured on the VLAN by the administrator.","To determine the status of MAC learning on the VLAN, enter the show mac-address-table learning command."
"MVRP_ISSU","2","GET_BUFFER","MVRP ISSU client failed to get buffer for message. Error: %d (%s)","The Multicast VLAN Registration Protocol (MVRP) ISSU client was unable to reserve buffer space for building a negotiation message. As a result, the negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"MVRP_ISSU","2","INIT","MVRP ISSU client initialization failed to %s. Error: %d (%s)","The MVRP ISSU client could not be initialized. This initialization failure must be addressed before an in-service software upgrade or downgrade can be performed. Otherwise, a software upgrade or downgrade will result in downtime.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MVRP_ISSU","2","SEND_NEGO_FAILED","MVRP ISSU client failed to send negotiation message. Error: %d (%s)","The MVRP ISSU client was unable to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"MVRP_ISSU","2","SESSION_NEGO","MVRP ISSU client encountered unexpected client nego_done. Error: %d (%s)","The MVRP ISSU client encountered a client negotiation done state that was unexpected. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"MVRP_ISSU","2","SESSION_REGISTRY","MVRP ISSU client failed to register session information. Error: %d (%s)","The MVRP ISSU client was unable to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"MVRP_ISSU","3","INVALID_SESSION","MVRP ISSU client does not have a valid registered session.","The Multicast VLAN Registration Protocol (MVRP) ISSU client does not have a valid registered session.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"MVRP_ISSU","3","MSG_NOT_OK","MVRP ISSU client 'Message Type %d' is not compatible","The MVRP ISSU client received an incompatible message from the peer device. The message cannot be processed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"MVRP_ISSU","3","MSG_SIZE","MVRP ISSU client failed to get the MTU for Message Type %d. Error: %d (%s)","The MVRP ISSU client was unable to calculate the MTU for the specified message. As a result, the MVRP ISSU client is not able to send the message to the standby device.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"MVRP_ISSU","3","SESSION_UNREGISTRY","MVRP ISSU client failed to unregister session information. Error: %d (%s)","The MVRP ISSU client was unable to unregister session information.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"MVRP_ISSU","3","TRANSFORM_FAIL","MVRP ISSU client %s transform failed for 'Message Type %d'. Error: %d (%s)","The MVRP ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In either case, the MVRP state between the active device and the standby device is not identical.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"MVRP_SWITCH","6","IGNORE_USER_CONFIG","The user configured list of pruned VLANs on interface %s is ignored as MVRP will prune VLANs dynamically.","The switchport trunk pruning vlan command is used by VTP pruning to prune VLANs numbered from 1 to 1001 only. This configuration command does not apply to MVRP, which prunes all 4096 VLANs. The command will be ignored.","No action is required."
"MVRP_SWITCH","6","VLAN_CREATED","MVRP created VLANs %s on this device","MVRP has created the specified VLANs. MVRP can create VLANs dynamically if the feature is enabled with the mvrp vlan create command.","No action is required."
"MXT_FREEDM","1","UNAVAILABLE","8PRI/4T board slot %d: Firmware download failed.","Failed to download firmware into 8PRI/4T board","Power Cycle the router. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MXT_FREEDM","1","UNAVAILABLE","8PRI/4T board slot %d: Firmware sent a HALT interrupt.","Double bus fault occurred in the 8PRI/4T board firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MXT_FREEDM","1","UNAVAILABLE","Invalid Shared Memory size detected","Current shared memory present in the box is not supported","Replace the Shared Memory by the supported configuration. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MXT_FREEDM","1","UNAVAILABLE","PCI-DBUS Bridge in slot %d Failure: %s","Internal error occured in 8PRI/4T board","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"MVR_RP","3","OPER_PORT_SET_FAILED","MVR port operational type setting failed. Reason: [dec]","A failure occurred while setting the MVR source or receiver port operational type on the switch port. The cause was either a failure on the switch port or an ICC failure.","Unconfigure the MVR type from this switch port and reconfigure it."
"MVR_RP","6","RCVR_ACCESS_PORTMODECHNG","[chars] MVR type receiver on [chars], this access port [chars] MVR vlan","An MVR type receiver should not be configured on a MVR VLAN port. Because this port is configured as dynamic auto/desirable, and due to a mode change in the neighboring switch, the operational switchport mode on this switch has become access and the corresponding VLAN is an MVR VLAN.","Either unconfigure MVR type receiver from this switch port or change the access VLAN to a non-MVR VLAN."
"MVR_RP","6","RCVR_TRUNK_PORTMODECHNG","[chars] MVR type receiver on [chars], MVR type receiver should not be configured on trunk ports","An MVR type receiver should not be configured on a trunk port. Because this port is configured as dynamic auto/desirable, and due to a mode change in the neighboring switch, the operational switch port mode on this switch has become trunk. MVR type receiver should be disabled.","Either unconfigure MVR type receiver from this switch port or change the mode to access and change the VLAN to a non-MVR VLAN."
"MVR_RP","6","SRC_ACCESS_PORTMODECHNG","[chars] MVR type source on [chars], this access port [chars] MVR vlan","MVR type source should not be configured on a non-MVR VLAN port. Because this port is configured as dynamic auto/desirable, and due to mode change in the neighboring switch, the operational switch port mode on this switch has become access and the corresponding VLAN is non-MVR.","Either unconfigure MVR type source from this switch port or change the access VLAN to an MVR VLAN."
"MVR_RP","6","SRC_TRUNK_PORTMODECHNG","[chars] MVR type source on [chars], this trunk port allowed vlans [chars] MVR vlan","MVR type source should not be configured on a non-MVR VLAN port. Because this port is configured as dynamic auto/desirable, and due to mode change in the neighboring switch, the operational switch port mode on this switch has become trunk and the corresponding VLAN range does not contain the MVR VLAN.","Either unconfigure MVR type source from this switch port or change the trunk allowed VLAN range to include the MVR VLAN."
"MWAM","4","FAILED_FILE_SYNC","Failure creating or synchronizing MWAM configuration file to standby: [chars], [chars]","The active supervisor engine has failed to copy an MWAM configuration file from bootflash: to slavebootflash:. The standby supervisor engine will not be up to date with the MWAM configuration files if a switchover occurs.","Verify that there is space available on the bootflash: and slavebootflash: devices. It may be necessary to compress either or both devices to recover space used by deleted or overwritten files. After taking these actions, a new attempt to synchronize files can be started either by resetting the standby supervisor engine or by configuring no mwam bootflash access followed immediately by mwam bootflash access. If these actions do not resolve the issue, obtain the output from the following commands:"
"MWAM","4","FAILED_TASK_INIT","Failed to start a required task: [chars], [chars]","A necessary process failed to be created.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NATMIB_HELPER","3","NOCREAT","NATMIB Helper Process not created - NAT MIB will not work properly","An attempt to start the NATMIB helper process failed when the NATMIB subsystem was initialized. The NATMIB helper process could not be created. This condition might be caused by a lack of memory.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Reload the system after reconfiguring it."
"NBAR","1","UNAVAILABLE","Nodes size mismatch between parsing and sending:%s","Failure during the distribution of NBAR graph nodes from the route processor to the linecards. Failure is related to node size changes between parsing and sending phase","Disable nbar protocols"
"NBAR","1","UNAVAILABLE","Reached maximum amount of memory allocated for stile","This platform allows NBAR to use a limited amount of memory for classification and that amount has been used up because of high traffic conditions.","Increase amount of memory in router."
"NBAR","1","UNAVAILABLE","link-next not NULL when allocated. link-next = %s","An attempt was made to get a link from the free bucket which is pointing to another resource. Links within the free bucket should be NULL, therefore this link is corrupted and should not be used","Configure the router with the ip nbar resources to allocate a larger initial pool of resources."
"NBAR","1","UNAVAILABLE","link-prev not NULL when allocated. link-prev = %s","An attempt was made to get a link from the free bucket which is pointing to another resource. Links within the free bucket should be NULL, therefore this link is corrupted and should not be used","Configure the router with the ip nbar resources to allocate a larger initial pool of resources."
"NBAR","2","UNAVAILABLE","Failure in the heuristic subsystem of NBAR: %s","Failure during the distribution of NBAR heuristic data structures from the route processor to the linecards.","Disable heuristic protocols"
"NBAR","2","UNAVAILABLE","Memory for maintaining state used up","NBAR uses memory to maintain state information about stateful flows. There is a maximum limit on how much memory NBAR can use for this purpose and this limit has been reached.","Increase memory on platform"
"NBAR","2","UNAVAILABLE","NBAR resource manager : too many buckets (%d)","NBAR was configured such that the internal data structures needed to maintain stateful protocol information were too large.","Configure the router with the ip nbar resources with a smaller max-idle time."
"NBAR","2","UNAVAILABLE","NBAR resources exhausted","In order to save stateful information on protocols, NBAR must use dynamic resources. These resources have been exhausted.","Configure the router with the ip nbar resources to allocate a larger initial pool of resources. The default number of initial resources is 10000. Also try configuring a shorter max-idle time."
"NBAR","2","UNAVAILABLE","No memory available for %s","An attempt at memory allocation failed.","Try these actions to remedy the problem: Add memory. Disable some features. Apply filtering to decrease the size of system data structures - the routing table, for example. In general, reduce other system activities to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"NETCONF","3","MEMORY","%s","The network configuration protocol (NETCONF) subsystem was unable to reserve the required memory to complete this operation.","Check the system memory for memory allocation errors. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"NETWORK_CLOCK_SYNCHRONIZATION","4","UNAVAILABLE","Network clock %s PLL lost lock - clock source failed.","The clock source has failed.","If alternate source is available, it will be used."
"NETWORK_CLOCK_SYNCHRONIZATION","4","UNAVAILABLE","Network clock source initialised to local oscillator.","Warning indicates that network clock used will be internal.","No action is required."
"NETWORK_CLOCK_SYNCHRONIZATION","4","UNAVAILABLE","Network clock source transitioned from Priority %d %s %s to Priority %d %s %s","This warning message indicates a change in the clock source.","No action required."
"NETFLOW_AGGREGATION","3","FLOWMASK_CONFLICT","Netflow [chars] cannot set the required flowmask","The NetFlow aggregation flow mask conflicts with other features.","If NetFlow Data Export is configured, increase the size of the NDE flow mask to VLAN full flow by entering the mls flow ip interface-full command, and then reconfigure the NetFlow aggregation scheme. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NETFLOW_AGGREGATION","4","NO_TOS_AGGR","Disable hardware switching to enable [chars]","NetFlow does not currently support ToS-based aggregation schemes for hardware-switched flows.","If ToS-based aggregation is required, disable hardware switching."
"NETFLOW_AGGREGATION","4","OER_AGG_EXPORT_ERROR","OER Error [chars]","An error occurred in receiving an Optimized Edge Routing (OER) aggregation export packet.","Disable OER monitor prefix aggregation."
"NETFLOW_AGGREGATION","6","OER_MLS_LONG_AGING","MLS long aging time modified by OER to [dec]","OER modified the long aging time to a value that may be different from the configured value.","No action is required."
"NETWORK_PORT_SATELLITE","3","PHY_LOCKUP","Repeated phy lockup seen on [chars]. Interface will be shut down.","The physical interface has locked up an excessive number of times. To avoid the interface becoming active, and then quickly becoming inactive numerous times (link flapping), the interface has been shut down.","To reenable the interface, enter the shutdown command, followed by the no shutdown command in interface configuration mode, to shut down and restart the interface."
"NETWORK_PORT_SATELLITE","6","UNAVAILABLE","Transmit lock up is detected in %s. This port is adminstratively down.","When the PHY is powered on and off, the MAC cycles from Gigabit to 100, and the port might lock up and stop sending packets. The PHY refers to the physical layer device on the switch, which sends and receives optical signals and provides framing and line integrity.","Shut down the port by using the shutdown interface configuration command, and bring it back up by using the no shutdown interface configuration command"
"NETWORK_RF_API","3","CLIENT_REGISTER_FAIL","Failed to register with [chars], rc =[dec]","A redundancy client could not be registered. An internal failure associated with client registration occurred in the run-time module specified in the message output. The return code that is specified in the message output identifies the type of failure that was detected. The failure most likely occurred because of a software error. The system state between the active and standby units might not be properly synchronized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NETWORK_RF_API","3","FAILDECODEDATADESC","Cannot decode data descriptor for [chars], descriptor type=[dec]","An internal data descriptor could not be decoded for synchronization for the interface or controller in the run-time module specified in the message output. The failure most likely occurred because of a software error. The descriptor type specified in the message output, if it is a nonzero value, identifies the type of failure. The system state between the active and standby units might not be properly synchronized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NETWORK_RF_API","3","FAILDECODEDATADESCINSTDBY","Cannot decode data descriptor in Standby for [chars], descriptor type=[dec]","An internal data descriptor could not be decoded in the standby unit. The message identifies the interface or controller that caused the decoding failure in the standby unit. This interface was encoded in the active unit but could not be decoded in the standby unit. The failure is probably caused by a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NETWORK_RF_API","3","FAILENCODEDATADESC","Cannot encode data descriptor for [chars], descriptor type=[dec]","An internal data descriptor could not be encoded for synchronization for the interface or controller in the run-time module specified in the message output. The failure most likely occurred because of a software error. The descriptor type specified in the message output identifies the type of failure. The system state between the active and standby units might not be properly synchronized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NETWORK_RF_API","3","FAILSENDMSGTOACTIVE","Failed to send [chars] message to active for [chars], [chars]","The specified synchronization message, which is an internal IPC message, could not be sent to the active unit in the specified run-time module. The failure most likely occurred because of a software error. Additional details on the cause of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NETWORK_RF_API","3","FAILSENDMSGTOSTDBY","Failed to send [chars] message to standby for [chars], rc=[dec]","The specified synchronization message, which is an internal IPC message, could not be sent to the standby unit in the specified run-time module. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the type of failure. The system state between the active and standby units might not be properly synchronized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NETWORK_RF_API","3","INVALID_CHKPT_STATUS_CODE","Invalid checkpointing status code received, rc=[dec]","An invalid checkpoint status code has been detected. An internal status code that is associated with checkpointing was found to be invalid. The return code that is specified in the message output identifies the invalid code that was detected. The failure most likely occurred because of a software error. The system state between the active and standby units might not be properly synchronized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NETWORK_RF_API","3","INVALID_MSG_RECEIVED","Invalid [chars] message received","A message that is used for state synchronization was not received correctly. An internal data structure for a message could not be retrieved. The failure most likely occurred because of a software error. The system state between the active and standby units might not be properly synchronized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NETWORK_RF_API","3","IPC","[chars] [chars]","An interprocess communication (IPC) error has occurred. Additional details on the cause of the error are specified in the message text on the console or in the system log.","Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support ipc command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NETWORK_RF_API","3","ISSU_MSG_MTU_INVALID","The ISSU message MTU is invalid: [chars]","A message buffer size that is used for state synchronization was found to be invalid. An internal data structure for a message could not be retrieved. The failure most likely occurred because of a software error. Additional details on the cause of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NETWORK_RF_API","3","ISSU_MSG_TYPE_INCOMPAT","The active and standby ISSU message types are incompatible","An incompatible message was used for state synchronization. An internal data structure for a message could not be retrieved. The failure most likely occurred because of a software error. The system state between the active and standby units might not be properly synchronized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NETWORK_RF_API","3","ISSU_REG_SES_INFO","Failed to register ISSU session information: [chars]","The system failed to register the ISSU session information required to complete version exchange between the active and standby units. The failure most likely occurred because of a software error. Additional details on the cause of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NETWORK_RF_API","3","ISSU_START_NEGO_SES","Failed to start ISSU session: [chars]","The system failed to start the ISSU negotiation session required to complete version exchange between the active and standby units. The failure most likely occurred because of a software error. Additional details on the cause of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NETWORK_RF_API","3","ISSU_TRANSFORM_FAIL","The ISSU message [chars] transformation failed: [chars]","A message that is used for state synchronization could not be transformed correctly. An internal data structure for a message could not be retrieved. The failure most likely occurred because of a software error. Additional details on the cause of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NETWORK_RF_API","3","ISSU_UNREG_SES_INFO","Failed to register ISSU session information: [chars]","The system failed to unregister the ISSU session information required to complete version exchange between the active and standby units. The failure most likely occurred because of a software error. Additional details on the cause of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NETWORK_RF_API","3","NO_CHKPT_BUFFER","No checkpointing buffer for [chars], rc=[dec]","A message data buffer that is used for state synchronization could not be obtained. An internal data structure could not be allocated for synchronization in the run-time module specified in the message output. The return code that is specified in the message output identifies the type of failure. The failure most likely occurred because of a software error or a lack of system memory. The system state between the active and standby units might not be properly synchronized.","If you determine that this condition was caused by a lack of system memory, reduce system activity to ease memory demands, or if conditions warrant, upgrade to a larger memory configuration. Otherwise, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NETWORK_RF_API","3","NO_MSG_BUFFER","No message buffer for [chars]","A message data buffer that is used for state synchronization could not be obtained. An internal data structure could not be allocated for synchronization in the run-time module specified in the message output. The failure most likely occurred because of a software error or a lack of system memory. The system state between the active and standby units might not be properly synchronized.","If you determine that this condition was caused by a lack of system memory, reduce system activity to ease memory demands, or if conditions warrant, upgrade to a larger memory configuration. Otherwise, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NETWORK_RF_API","3","NO_RESOURCES","[chars]","A run-time module could not obtain the resources that are required to complete a task. The failure most likely occurred because of a software error or a lack of system memory. Additional details on the cause of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized.","If you determine that this condition was caused by a lack of system memory, reduce system activity to ease memory demands, or if conditions warrant, upgrade to a larger memory configuration. Otherwise, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NET_SERV","4","UNAVAILABLE","Unexpected condition: %s","An unexpected condition was detected while performing a services timer operation","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NET_SERV","4","UNAVAILABLE","Unexpected error: %s","An unexpected error occurred while performing a services timer operation","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NETWORK_RF_API","6","IDB_TRANSITIONS_PENDING","Switchover terminated with [dec] transitions pending after there was no transition activity for [dec] seconds","The system terminated the switchover IDB transitioning phase with a number of IDB transitions still pending because no switchover-related IDB transitions were logged during the specified time interval. Some connected routes may experience a temporary loss of traffic.","No action is required."
"NHRP","3","TIMERLOOP","Timer process looping ([dec]/[dec]/[dec]/[dec]/[dec]/[dec]).","The process that handles timer events is looping, possibly on a malfunctioning timer event.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NHRPSNMP","3","TREEINVALID","Setting tree to Invalid State @ - (%d)","NHRP SNMP agent tree is not behaving as excepted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NHRPSNMP","5","TREERECOVERD","Tree recovered fromInvalid State @ - (%d)","NHRP SNMP agent tree is not behaving as expected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NIM","2","UNAVAILABLE","All hardware addresses have been allocated - maximum of %d","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NIM","2","UNAVAILABLE","Attempted to manipulate uninitialized ichainQ in %s","A software or hardware error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NIM","2","UNAVAILABLE","Couldn't find idb 0x%x in ichainQ in %s","A software or hardware error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"NIM","2","UNAVAILABLE","Illegal reference to non-existent slot %d","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NIM","2","UNAVAILABLE","Illegal reference to non-existent subunit %d in slot %d","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NIM","2","UNAVAILABLE","Unsupported %s NIM in slot %d","The indicated NIM is not supported on this platform.","Remove the NIM."
"NIM","2","UNAVAILABLE","Unsupported version of %s NIM in slot %d Version 0x%x","The indicated network interface module (NIM) is not supported because it is not of the correct revision. Certain platforms (Cisco 4500 or Cisco 4700, for example) require some NIMs to be of a minimum rev level.","Upgrade the NIM to the proper level."
"NMSP","3","INIT_FAIL","NMSP process failed to initialize","NMSP process failed to initialize and cannot accept incoming NMSP messages","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NMSP","3","INIT_SPI","NMSP SPI process %s failed reason %d","NMSP SPI process failed to initialize and cannot forward NMSP messages to WCM","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP","2","BADREAD","Read failed for [chars] on NP [dec].","There was a read error on the file during the microcode image load.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"NP","2","HDRCORRUPT","Microcode header has been corrupted, expected [hex], got [hex].","Network Processor microcode appears to be corrupted. This could be due to an already corrupted image or, less likely, a software problem.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"NP","2","INVALID","Corrupted microcode retrieved from the image bundle for NP [dec].","The retrieved microcode appears to be corrupted.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"NP","2","NONEXIST","Could not open or file does not exist [chars] for NP [dec].","There is a possibility that the Network Processor microcode may not be bundled into the image correctly or a software error occurred that prevented locating the microcode.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"NP","2","RESTARTED","NP [dec] restarted.","Network Processor has been restarted, either manually or by a microcode reload, or as a result of an exception.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"NP","2","WRONGHARD","The microcode type does not match, expected [hex], got [hex].","There is a possibility the images has been corrupted or, less likely, an incorrect microcode set is bundled into the image.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"NP","2","WRONGMAGIC","Microcode section contains inalid magic for NP [dec].","Network Processor microcode appears to mismatch the ucode hdr type. This could be due to an already corrupted image or a read error on the file during the downloading on the NP.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"NP","3","UNAVAILABLE","%s queue is full for Slot %d, DFC %d, Module %d.","TX queue is full for this module.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP","3","UNAVAILABLE","Control buffer pool could not be created","NextPort driver could not create the control buffer pool required for tx and rx of NP control messages","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP","3","UNAVAILABLE","DFC Reset-Cleared Failed - DFC %d","DFC Reset-Cleared Failed","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP","3","UNAVAILABLE","Message Id %x not supported.","The Nextport does not supported this control message id.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP","3","UNAVAILABLE","NAK Response Received - command 0x%x, result code 0x%x, msg id 0x%x, session id 0x%x, msg tag 0x%x","A NAK response was sent by the NextPort module.","Copy the error message exactly as it appears, and report it to your technical support representative."
"NP","3","UNAVAILABLE","Slot %d, DFC %d, Module %d not exist.","No Virtual Console opens for this module.Error Message    Copy the error message exactly as it appears, and report it to your technical support representative.NP-5Error Message    %NP-5-RESTARTEDALL: All NPs have been restarted. Explanation    All Network Processors have been restarted, either manually or by a microcode reload, or as a result of an exception.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"NP_BS","2","UNAVAILABLE","DFC in slot %d does not have three NP108s!","DFC does not have three NP108s which is an illegal configuration","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_BS","3","UNAVAILABLE","%s","Failed NextPort BootStrap and Crash Monitor Initialization.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_BS","3","UNAVAILABLE","%s","NextPort BootStrap and Crash Monitor Could not allocate memory for internal module database","No action is required."
"NP_BS","3","UNAVAILABLE","%s nonexisting NP module %d/%d/%d","NextPort BootStrap and Crash Monitor detected an internal database error","No action is required."
"NP_BS","3","UNAVAILABLE","Failed to access NextPort module %d/%d/%d crash info","NextPort BootStrap and Crash Monitor failed to access crash information","No action is required."
"NP_BS","3","UNAVAILABLE","Invalid NextPort Firmware for %d/%d/%d","NextPort BootStrap and Crash Monitor detected aninvalid NextPort firmware","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_BS","3","UNAVAILABLE","NULL NextPort Firmware pointer for %d/%d/%d","NextPort BootStrap and Crash Monitor detected aNULL NextPort firmware pointer","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_BS","3","UNAVAILABLE","NextPort Module %d/%d/%d control queue creation failure","NextPort BootStrap and Crash Monitor detected ancontrol queue creation failure","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_BS","3","UNAVAILABLE","NextPort Module %d/%d/%d detected a module POST failure 0x%x","NextPort BootStrap and Crash Monitor detected ana module POST failure","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_BS","3","UNAVAILABLE","NextPort Module %d/%d/%d detected an invalid IDT","NextPort BootStrap and Crash Monitor detected aninvalid IDT","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_BS","3","UNAVAILABLE","NextPort Module %d/%d/%d failed firmware image validation","NextPort BootStrap and Crash Monitor detected ana failed NextPort firmware CRC validation","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_BS","3","UNAVAILABLE","NextPort Module %d/%d/%d memory test failed","NextPort BootStrap and Crash Monitor detected a failedNextPort module memory test","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_BS","3","UNAVAILABLE","NextPort module %d/%d/%d failed to respond to keepalive message","NextPort BootStrap and Crash Monitor detected a module failed to respond to keepalive message","No action is required."
"NP_BS","6","UNAVAILABLE","NextPort module %d/%d/%d Started - %d.%d.%d.%d","NextPort BootStrap and Crash Monitor successfully started module","No action is required."
"NP_BS","6","UNAVAILABLE","NextPort module %d/%d/%d Stopped","NextPort BootStrap and Crash Monitor stopped module","No action is required."
"NP_CLIENT","2","FATAL","NP Client %s : %s (%d, %d)","NP Client software detected a critical programming error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_CLIENT","3","ALLEXISTS","NP Client Previously Defined Software Element - %s: %s %s","The NP Client has detected a previously defined software element.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_CLIENT","3","INITFAIL","NP Client Initialization Failed - [chars]: [chars] [chars]","The NP client could not initialize memory needed to service one or more network processors. This error may indicate that an incompatibility exists between the NP firmware and the associated Cisco IOS image.","Attempt to reload the Cisco IOS image on the affected card or platform. If the error persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_CLIENT","3","INTF","[chars] ([chars]) on [chars] - [chars] if_number=[dec]","The interface NP client detected an error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_CLIENT","3","MAXEXCEED","NP Client Max Services Exceeded - [chars]: [chars] [chars]","The maximum number of NP client services has been exceeded.","Change the configuration to reduce the number of services configured. If the error persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_CLIENT","3","METADATA","[chars] failed: [chars] [[chars]] [chars]","Processing of the metadata for the specified network processor has failed. The specified network processor will fail to operate.","Attempt to reload the network processor microcode. If the error persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_CLIENT","3","NOMEM","Memory Allocation Failure - [chars]: [chars] [chars]","The NP client could not allocate the required memory needed to service one or more network processors.","This error may indicate that more memory must be installed on the affected card or platform in order to service all the features and related entities enabled by the configuration. "
"NP_CLIENT","3","NOTFOUND","NP Client Software Element Not Found - [chars]: [chars] [chars]","The NP client could not locate a required software element.","Attempt to reload the Cisco IOS image on the affected card or platform. If the error persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_CLIENT","3","NOTSUP","NP Client Feature Not Supported - [chars]: [chars] [chars]","The NP client does not support the specified feature.","Verify that the correct Cisco IOS image is loaded on the affected card or platform for the configured features. If the error persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_CLIENT","3","NPUNKNOWN","NP Client Unsupported NP - [chars]: [chars] [chars]","The NP client detected an unsupported NP.","Verify that the correct Cisco IOS image is loaded on the affected card or platform for the configured features. If the error persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_EST","3","UNAVAILABLE","%s","EST detected an internal error","No action is required."
"NP_EST","6","UNAVAILABLE","%s","EST Control No-Acknowledge Notification is sent to IOS to convey additional debug data regarding a NAK that occurred on the Control Queue","No action is required."
"NP_EST","6","UNAVAILABLE","%s","EST Diagnostic/POST Notification is sent to IOS to convey additional information about the power-on self-test or a diagnostic test result","No action is required."
"NP_EST","6","UNAVAILABLE","%s","EST Run-time Error Notification is sent to IOS to convey additional debug data that may help to identify the cause of the error","No action is required."
"NP_MD","0","UNAVAILABLE","Attempt to %s a data channel on the unexisting line %d/%d","An internal software error occured that probably resulted in corrupted modem database","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MD","0","UNAVAILABLE","Attempt to %s a data channel on the unexisting modem %d/%d","An internal software error occured that probably resulted in corruptedmodem database","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MD","0","UNAVAILABLE","Cannot allocate %d bytes of memory for %s","The system failed to allocate an important data structure due to the lack of memory","Show mem. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MD","0","UNAVAILABLE","Cannot allocate TTY%d (%d/%02d)","Allocation of TTY structure failed. Either there is not enough memory or the TTY number is too big","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MD","0","UNAVAILABLE","Cannot allocate interface Async%d/%02d","Allocation of interface structure failed. Either there is not enough memory or the maximum number of interfaces was exceeded","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MD","0","UNAVAILABLE","Cannot bring up the module %d/%d/%d due to lack of module elements","NextPort Modem Driver cannot allocate an important data structure, called module element which is necessary to bring up the module. This should not normally happen and possibly indicates an error condition","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MD","0","UNAVAILABLE","Slot %d is already present in the system","An internal software error occured, that possibly resulted in corrupted slot database.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MD","0","UNAVAILABLE","Slot %d is not present in the system","An internal software error occured, that possibly resulted in corrupted slot database.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MD","0","UNAVAILABLE","TTY %s: Cannot allocate %s","An important buffer cannot be allocated due to the shortage of packet memory.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MD","1","UNAVAILABLE","TTY %s: Attempt to set an unknown special character (type %d) to %#02x","NextPort Modem Driver received a request for hardware detection of an unknown type of a special character due to an internal software error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MD","3","UNAVAILABLE","%s is NULL in %s for port %d","Unexpected NULL pointer at specified location","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MD","3","UNAVAILABLE","Contiguous packet sent for transmit","A software error occurred resulting in an unexpected packet being set up for transmission and the packet was dropped by the NextPort Modem Driver","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MD","3","UNAVAILABLE","Could not seed data queue for module %d/%d/%d","NextPort Modem Driver could not seed the data queue with buffers","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MD","3","UNAVAILABLE","Could not send to data queue for port %d, inflight tx buffers %d","NextPort Modem Driver could not send buffer to Interface driver","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MD","3","UNAVAILABLE","Failed to return data buffer for port %d","Call to NextPort Interface Driver to replenish data buffer for this channel failed","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MD","3","UNAVAILABLE","Failed to send inband message for TTY %s","Call to send inband message on data queue failed","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MD","3","UNAVAILABLE","Modem slot structure for slot %d could not be created","NextPort modem driver could not create the modem slot structure which is required for modem services of this card","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MD","3","UNAVAILABLE","No buffer to seed data queue for module %d/%d/%d","NextPort Modem Driver could not obtain a buffer whilst trying to seed the module data queue. Due to packet memory shortage","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MD","3","UNAVAILABLE","Static transmit paktype unavailable","A software structure was found in an unexpected state during run-time for the indicated modem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MD","3","UNAVAILABLE","TTY %s: No buffers available to set up the transmit queue","A software error occurred resulting in an unexpected exhaustion of the pool of data buffers used by the modem drivers.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MD","3","UNAVAILABLE","TTY %s: RTS is incorrectly deasserted; reasserting now","A software error occurred resulting in an invalid state for the RTS modem signal","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MD","3","UNAVAILABLE","TTY %s: Unknown NextPort in-band message (msg_id %04x) received","NextPort Modem driver received an unknown message from a NextPort module.This can happen if new firmware is used with an obsolete version of IOS","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MD","3","UNAVAILABLE","Too many buffers (%d) rxd for port %d","NextPort Module sent more buffers than is allowed for this channel","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MD","3","UNAVAILABLE","Unknown encapsulation %d on interface %s","A software error occurred resulting in an unknown encapsulation type on the interface specified by the error message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MD","6","UNAVAILABLE","NextPort module %d/%d/%d down","NextPort Modem Driver detected a module going down","No action is required."
"NP_MD","6","UNAVAILABLE","NextPort module %d/%d/%d up","NextPort Modem Driver detected a module coming up","No action is required."
"NP_MD","6","UNAVAILABLE","Slot %d (%d ports max) inserted","NextPort Modem driver detected a slot being inserted in the system. During the startup all slots that are present in the system are treated as being inserted","No action is required."
"NP_MD","6","UNAVAILABLE","Slot %d removed","Slot has been removed from the system","No action is required."
"NP_MM","3","UNAVAILABLE","Failed to allocate control message buffer for NP module %d/%d/%d - %s","NextPort Module Manager failed to allocate control message buffer","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MM","3","UNAVAILABLE","Failed to create Data Q for NP module %d/%d/%d","NextPort Module Manager failed to create Data Queue","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MM","3","UNAVAILABLE","Failed to send %s message to NP module %d/%d/%d","NextPort Module Manager failed to send control message","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MM","3","UNAVAILABLE","Invalid NP module state(%s) %d/%d/%d - %s","NextPort Module Manager detected invalid NP module state","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MM","3","UNAVAILABLE","Invalid NP_ADDRESS %d/%d/%d/%d - %s","NextPort Module Manager detected invalid NP_ADDRESS","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MM","3","UNAVAILABLE","Module Crash detected %d/%d/%d: state = %d, cause code = %d","NextPort Module Manager detected a crashed module","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MM","3","UNAVAILABLE","Module Run Time Error %d/%d/%d : recovery = 0x%x, error = 0x%x","NextPort Module Manager received a module run time error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MM","3","UNAVAILABLE","Module country code failure %d/%d/%d","NextPort Module Manager failed to set the country code","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MM","3","UNAVAILABLE","Module exceeded restart threshold %d/%d/%d","NextPort Module exceeded the restart threshold","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MM","3","UNAVAILABLE","Unsupported module ACK response %d/%d/%d: msg len = %d, session ID = %d, msg tag = %d, msg ID = %d, cmd msg ID = %d, result code = %d","NextPort Module Manager received an unsupported message response","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_MM","3","UNAVAILABLE","Unsupported module response %d/%d/%d: msg len = %d, session ID = %d msg tag = %d, msg ID = %d","NextPort Module Manager received an unsupported message response","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_SIGLIB","3","UNAVAILABLE","Format of cp tone failed for tone-id %d, port %d/%d","Formatting of the call processing tone message to the nextport module failed","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_SPE_DS","3","UNAVAILABLE","%s","SPE download code failed to initialise - SPE download will fail","LOG_STD_NO_ACTION"
"NP_SPE_DS","3","UNAVAILABLE","Cannot allocate %d bytes of memory for %s","The system failed to allocate an important data structure due to the lack of memory","Show mem. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_SPE_DS","3","UNAVAILABLE","SPE %d/%d/%d/%d: %s","SPE download code failed - download aborted","LOG_STD_NO_ACTION."
"NP_SSM","0","UNAVAILABLE","Cannot allocate %d bytes of memory for %s","The system failed to allocate an important data structure due to the lack of memory","Show mem. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_SSM","3","UNAVAILABLE","SSM(%d/%d): Invalid Session/Service Instance Handle","Session and Service Manager Received failed to obtain its instance handle for the slot/port","No action is required."
"NP_SSM","3","UNAVAILABLE","SSM(%d/%d): Session Runtime Error Code = %d, Recovery Action = %d","Session and Service Manager Received a Runtime Error for the slot and port","No action is required."
"NP_SSM","3","UNAVAILABLE","SSM: Invalid Session/Service Message, ID = 0x%x","Session and Service Manager Received an invalid message from the NextPort Message Dispatcher","No action is required."
"NP_SSM","6","UNAVAILABLE","NULL SSM Info Handle for slot %d, port %d","NextPort Session and Service Manager failed to obtain a controlinformation handle for the indicated slot and port numbers","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_SSM","6","UNAVAILABLE","NULL Vdev Common Handle for slot %d, port %d","NextPort Session and Service Manager failed to obtain aVoice Device Information handle for the indicated slot and port numbers","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NP_CRASHINFO","2","OPEN_FAILED","Could not open crashinfo file [[chars]]","The file for writing crashinfo could not be opened. This is usually caused by the file system problem.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"NP_CRASHINFO","2","WRITE_FAILED","Could not write crashinfo file [[chars]]","Could not write crashinfo to the file. This is usuallycaused by the file system problem.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"NP_CRASHINFO","2","WRITING","Writing crashinfo file [[chars]]","NP detected a watchdog timeout. The crashinfo is collectedfrom problematic NP and stored in the location.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"NP_DEV","2","INVREGINTR","Illegal Write on NP RMA Register: [hex], Data: [hex]","This is an illegal Write to an NP RMA Register. This is to debug NP Parity Error issue. Examine traceback and forward it to development team.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"NP_DEV","2","WATCHDOG","Watchdog detected on NP [dec]","A software exception occured on an NP device.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"NP_DEV","3","ECC_DOUBLE","Double-bit ECC error detected on NP [dec], Mem [dec], SubMem [hex],SingleErr [dec], DoubleErr [dec] Count [dec] Total [dec]","A double-bit ECC error was detected for a Network Processor device component.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"NP_DEV","3","ERRINTR","Error caused by: [chars] on NP [dec]","An error in Network Processor device operation was detected.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"NP_DEV","3","PERR","Non-recoverable Parity error detected on NP [dec], cause [dec] count [int] uqParityMask [hex], uqSRAMLine [hex], bRecov [dec], bRewr [dec] Total [dec]","A non-recoverable parity error was detected for a Network Processor device component.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"NP_DEV","5","INTRTHR","Interrupt: cause [dec] for NP([int]) throttled","Too many interrupts are being generated from Network Processor device.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"NP_DEV","6","PERR_RECOVERED","Recovered from a Parity error on NP [dec], cause [dec], count [int] uqParityMask [hex], uqSRAMLine [hex], bRecov [dec], bRewr [dec] Total [dec]","Recovered from a Parity error detected for a Network Processor device component.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"NP_DEV","6","ECC_SINGLE","Recovered from a single-bit ECC error detected on NP [dec], Mem [dec], SubMem [hex],SingleErr [dec], DoubleErr [dec] Count [dec] Total [dec]","Recovered from a single-bit ECC error detected for a Network Processor device component.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"NP_UCODE","3","INVALID_FILE","NP microcode %s for device %s is invalid (%s)","The file containing the microcode for an NP is not specified or not accessible. This could be due to an invalid configuration or because the microcode is missing in this image.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"NSE100","3","IOBUSTIMEOUT","IO access to the address [hex] timed out (Target: [chars])","The system controller flagged an I/O access timeout, indicating either a transient/fatal system component issue or an underlying software initialization issue. The source of the problem can be determined more accurately by decoding the address being accessed. If the I/O address is valid in the system memory map and if the system has been up and operational for a while, the problem is probably hardware related. If this problem is seen repeatedly, the corresponding component might need to be replaced.","If the message is seen repeatedly, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: description of the user activity just before the occurrence of this incident, prevailing system operational conditions like traffic pattern, amount of traffic, system neighbors, system console messages and the output of the following commands: show running-config, show c7300 pxf accounting, show c7300 pxf interfaces all, show diag and show c7300."
"NSE100","3","PINNACLE_PORT","[chars] - [chars]","A failure occurred while one of the Gigabit Ethernet (GE) ports on the NSE-100 was being initialized. This condition is probably caused by either a software error or a transient condition before the GE port becomes successfully initialized.","If the GE ports either do not initialize or fail to forward traffic as a result of this condition, enter the shutdown command, followed by the no shutdown command, in interface configuration mode to shut down and restart the affected GE ports to restore the forwarding. If the message is seen repeatedly, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: "
"NSE100","3","UNEXPECTED_TIMEREVENT","The NSE-100 GE port driver couldn't determine the port associated with the expired internal managed timer.The expired managed timer is pointing to [chars]","The expired managed timer returned a null context. This condition indicates a software failure in the management of the timer.","If the message is seen repeatedly, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: "
"NSE100","3","VA_ERROR","Vanallen ASIC detected an error condition: [chars]","The Van Allen ASIC has detected an error condition. Either a hardware error or an error in the packet was detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NSE100","4","UNAVAILABLE","CI-DEMUX FPGA detected an error (Status 0x%08x)","The Cluster Internnect DEMUX FPGA found an error with the egress packet. Type of error is indicated in the status. The message is informational.","If the mesage is seen repeatedly, please collect following information and contact Cisco technical support representative. Output of the commands, show c7300 pxf accounting, show c7300 pxf interfaces all, show diag, show c7300"
"NSE100","4","UNAVAILABLE","ROM monitor upgrade in ROM %d terminated.","ROM monitor upgrade process was terminated by the user. The user had terminated the IOS boot up process from a first-time image in the writable ROM. This causes the verification process of this new ROM monitor to fail. This automatically sets the ROM monitor image to be INVALID.","After downloading a new ROM monitor image to the writeable ROM, you must reload IOS for the new ROM monitor image to take effect. The first time a new ROM monitor image is loaded, you must allow the system to boot up IOS before doing any resets or power cycling. If the ROM monitor loading process is interrupted, the system interprets this as a boot up failure of the new ROM monitor image. Please re-download the ROM monitor image to the writable ROM and start the ROM monitor upgrade process again. If the problem persists, please issue the show tech-support command to gather more information and call your Cisco technical support representative and provide the representative with the gathered information."
"NSE100","4","UNAVAILABLE","System hardware configuration %scompliant with recommended guidelines.","The aggregate throughput of the line cards exceeds the capacity of the NSE to line card interface in this system.","Refer to the configuration guidelines for the maximum allowed aggregate throughput for the line cards in this system."
"NSE100","4","UNAVAILABLE","The aggregate throughput of the Line Cards changed from %d kbps (%scompliant) to %d kbps (%scompliant)","The aggregate throughput of the line cards in the system changed to make the system compliant or non-compliant with the hardware configuration guidelines.","Refer to the configuration guidelines for the maximum allowed aggregate throughtput for the line cards in this system."
"NSE100","4","UNAVAILABLE","Unknown GBIC type or GBIC not inserted properly for interface GigabitEthernet%d/%d","Sometimes if GBIC is not inserted all the way into its slot, the GBIC type may return as Unknown Media Type","Take out the GBIC and reinsert all the way in"
"NSE100","5","AUTONEG_ENABLE","Auto negotiation is enabled for interface GigabitEthernet[dec]/[dec] due to [chars]","The auto-negotiation feature has been enabled for the Gigabit Ethernet interface in the slot and port specified in the message text. The reason why the feature was enabled is specified in the message text. The auto-negotiation feature is required for the interface to work properly.","No action is required."
"NSE100","6","UNAVAILABLE","ROM monitor upgrade in ROM %d successful.","ROM monitor upgrade has successfully performed.","LOG_STD_NO_ACTION"
"NSP","2","UNAVAILABLE","msgtxt_nomemory","An operation could not be accomplished because of a low-memory condition. The current system configuration, network environment, or possibly a software error might have exhausted or fragmented the system's memory.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a configuration that has more memory."
"NSP","3","UNAVAILABLE","Bogus parameter passed: %s %d","Internal error: parameter pased to routine is invalid","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NSP","3","UNAVAILABLE","Invalid slots[]: %x","Internal error: slottype pointer is invalid","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NSP","4","UNAVAILABLE","%s: %s %s","A SONET line warning condition has been detectedLOG_STD_NO_ACTION.NSPINT-3Error Message    %NSPINT-3-UNAVAILABLE: no handler for index %d Explanation    Internal error: an interrupt has been detected for which no handler has been registered.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NSPINT","5","UNAVAILABLE","Spurious level %d interrupt (%d)","An interrupt for which no cause could be found has been detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NSP_APS","4","UNAVAILABLE","Interface %s switched from %s to %s channel","The APS logic has determined that a switch over from one port to another was called for.","LOG_STD_NO_ACTION"
"NSP_OIR","3","UNAVAILABLE","Cannot enable card slot(%d) subslot redundancy is active on subcard in slot(%d)","Cards present in chassis in current mode are incompatible","Remove card and clear out alarms. Card could also be incompatible with existing cards and cannot run redundantly"
"NSP_OIR","3","UNAVAILABLE","Cannot enable half height card, redundancy conflict","Redundancy/Card conflict with cards in adjacent slot.","LOG_STD_NO_ACTION"
"NSP_OIR","3","UNAVAILABLE","Inserted card incompatible with previously removed card","Card inserted is not same type as one previously removed and thus invalid.","Please insert card similar to one which was previously removed or clear out alarm source"
"NSP_OIR","3","UNAVAILABLE","Insufficient system resources to complete card insertion/redundancy request, Reverting Configuration","Unable to allocate internal data structures for interface","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NSP_OIR","3","UNAVAILABLE","Invalid card/configuration in slot(%d) Ignoring Card","Cards present in chassis in current mode are incompatible","Remove card and clear out alarms. Card could also be incompatible with existing cards and cannot run redundantly"
"NSP_OIR","3","UNAVAILABLE","Long bus stall (%u s) The newly inserted card may not seated properly. Please remove it and try again.","Card Bad or not properly seated.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NSP_OIR","3","UNAVAILABLE","OIR event structure allocation failure","Internal Oir element allocation failure. Usually this will indicate some memory leak","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. Restart/reboot box at a convenient time. This problem will not affect normal operation but you will be unable to remove old hardware, or insert new hardware and bring it online"
"NSP_OIR","3","UNAVAILABLE","Unrecognized Card, Driver for Card not available in system software, ignoring card type 0x%x","Card inserted into system is not recognized by software -- ignoring.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NSP_OIR","4","UNAVAILABLE","6400 Card %d/%d found off line - will 'virtually' remove and reinsert to bring online","Card has somehow gone off line. Possibly a power glitch?? SW will bring it back online","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NSP_OIR","4","UNAVAILABLE","Redundancy submode not present!","System config does not have Redundancy submode","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NSP_OIR","6","UNAVAILABLE","Card %s inserted into slot: %d","Full card inserted into slot","LOG_STD_NO_ACTION"
"NSP_OIR","6","UNAVAILABLE","Card %s inserted into subslot: %d/%d","Half height card inserted into subslot","LOG_STD_NO_ACTION"
"NSP_OIR","6","UNAVAILABLE","Card %s removed from slot: %d","Full card removed from slot","LOG_STD_NO_ACTION"
"NSP_OIR","6","UNAVAILABLE","Card %s removed from subslot: %d/%d","Half height card removed from subslot","LOG_STD_NO_ACTION"
"NSP_OIR","6","UNAVAILABLE","Card %s, slot: %d, being brought online","Full card being brought online","LOG_STD_NO_ACTION"
"NSP_OIR","6","UNAVAILABLE","Card %s, subslot: %d/%d, being brought online","Half Height card being brought online","LOG_STD_NO_ACTION"
"NP_UCODE","3","INVALID_FILE","NP microcode [chars] for device [chars] is invalid ([chars])","The file containing the microcode for an NP is not specified or not accessible. This could be due to an invalid configuration or because the microcode is missing in this image.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NRP","3","UNAVAILABLE","%s %s","An Interprocess Communication (IPC) error occurred. The details about what was attempted and what went wrong will be printed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NSE","3","UNAVAILABLE","Attempt to set ACL base address to null. Update aborted.","An attempt has been made to set the PXF ACL base address to a null. This condition will result in PXF exceptions being made and will eventually result in the PXF being disabled. The base address has not been updated.","Make a change in the access list that will force a reevaluation of the ACL data."
"NSE","3","UNAVAILABLE","QoS queue hung on interface %s.","The system was unable to close down the QoS support in PXF for the interface cleanly. Problems may arise if the QoS support in PXF for the interface is restarted without first reloading the pxf microcode.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NSE","3","UNAVAILABLE","Unknown QoS action type: 0x%x.","A QoS feature, unrecognised by PXF, has been configured with the Modular QoS CLI. The feature will work but excessive punting may occur if the feature is on an output interface","If performance is poor, try disabling PXF."
"NSE","6","UNAVAILABLE","No VLAN statistics are avaliable for PXF switched interface %s.","No 802.1Q statistics are avaliable for packets that are PXF switched","No action is required."
"NTI","3","AGENT_ERR","%s Notifying platform about AGENT ERROR %s, AGENT EP ID 0x%x for EP ID 0x%x, EP type %s, EP group %s","A Negotiation Trigger Infrastructure (NTI) AGENT error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTI","3","CLIENT_NOT_REGSTRD_FOR_EPTYPE","%s Client (#%d - %s) has NOT registered for platform EP type %s","A client has not registered for a platform endpoint (EP) type.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTI","3","ISSU_AGENT_LIST_ALLOC","Failed to allocate agent bitlist for endpoint 0x%x","The NTI ISSU process was unable to allocate the agent bitlist for an endpoint. The endpoint will probably be reset.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTI","3","ISSU_DUMMY_MSG_FAILED","Failed to send a dummy nego msg to endpoint 0x%x","The NTI ISSU process was unable to send a dummy negotiation message to trigger negotiation on the peer. The endpoint will probably be reset.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTI","3","ISSU_EXISTING_SESSION","Session already exists for ep 0x%x","The NTI ISSU session already exists for this endpoint. The endpoint will probably be reset.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTI","3","ISSU_INVALID_MEDMAN","Invalid MEDMan data","The Multiple Endpoint Data Manager (MEDMan) data is invalid. The endpoint will probably be reset.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTI","3","ISSU_INVALID_MSG_TRANS","NTI ISSU transformation function got an invalid message in argument","The NTI ISSU process transformation function received an invalid message. The message cannot be transformed and will not be processed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTI","3","ISSU_INVALID_RC","Invalid ISSU rc argument for endpoint 0x%x","The NTI ISSU process received an invalid ISSU return code argument. ISSU negotiation will fail and the endpoint will probably be reset.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTI","3","ISSU_INVALID_RCVD_MSG","NTI ISSU received an invalid message for transformation from endpoint 0x%x","The NTI ISSU process received an invalid message for transformation. The message cannot be processed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTI","3","ISSU_INVALID_SESSION","Invalid session for ep 0x%x","The NTI ISSU session is invalid for the endpoint. The endpoint will probably be reset.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTI","3","ISSU_MEDMAN_CREATE","Failed to create MEDMan data for endpoint 0x%x","The NTI ISSU process was unable to create the Multiple Endpoint Data Manager (MEDMan) data for an endpoint. Negotiation cannot be done, and the endpoint will probably be reset.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTI","3","ISSU_MEDMAN_GET","Failed to get MEDMan data for endpoint 0x%x (%s)","The NTI ISSU process was unable to retrieve MEDMan data for an endpoint. ISSU negotiation will fail for this endpoint, and the endpoint will probably be reset.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTI","3","ISSU_MTU_FAILED","NTI ISSU failed to get MTU for message type %d (%s)","The NTI ISSU process was unable to get the message MTU for transformation. The message cannot be sent.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTI","3","ISSU_NEGO_ALREADY_STARTED","NTI ISSU negotiation already started, endpoint 0x%x","An attempt was made to start the NTI ISSU negotiation, but it has already been started. The endpoint will probably be reset.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTI","3","ISSU_NEGO_ASYNC_ERROR","Aync error during nego with 0x%x (%s)","The NTI ISSU process received an asynchronous error during negotiation with an endpoint. The endpoint will probably be reset.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTI","3","ISSU_NEGO_INCOMPATIBLE","Negotiation incompatible for endpoint 0x%x","The NTI ISSU negotiation is not compatible for this endpoint. The endpoint will probably be reset.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTI","3","ISSU_NOT_INIT","NTI ISSU is not initialized, endpoint 0x%x.","The NTI ISSU process is not initialized. The endpoint will probably be reset.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTI","3","ISSU_PLATFORM_TRANSPORT_NEGO_GET_REQ_PAK","NTI ISSU failed to get an platform transport nego message","The NTI ISSU process was unable to receive a platform transport negotiation message. The endpoint will probably be reset.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTI","3","ISSU_PLATFORM_TRANSPORT_NEGO_SEND","NTI ISSU failed to send an platform transport nego message to 0x%x","The NTI ISSU process was unable to send a negotiation message using the platform transport. The endpoint will probably be reset.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTI","3","ISSU_RCVD_NEGO_NOT_DONE","NTI ISSU negotiation not done when received a message from 0x%x","The NTI ISSU process received a message before negotiation was done. The message cannot be processed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTI","3","ISSU_RCVD_TRANS_FAILED","NTI ISSU failed to transform received message from 0x%x","The NTI ISSU process was unable to transform a received message. The message cannot be processed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTI","3","ISSU_RCVD_UNKNOWN_MSG","NTI ISSU received an unknown message type %d from 0x%x","The NTI ISSU process received a message whose type is unknown. The message cannot be processed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTI","3","ISSU_RCV_FAILED","NTI ISSU failed to transform message type %d for receive from 0x%x (%s)","The NTI ISSU process was unable to transform the message for receive. The message cannot be processed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTI","3","ISSU_REG_ADD","NTI ISSU failed to hook to the registry %s","The NTI ISSU process was unable to hook to a registry. This endpoint will probably be reset.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTI","3","ISSU_REG_RECEIVE_NEGO_MSG","NTI ISSU failed call the platform receive nego message registry","The NTI ISSU process was unable to call the platform receive negotiation message registry. The endpoint will probably be reset.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTI","3","ISSU_TRIG_NEGO_NOT_DONE","NTI ISSU negotiation not done when getting a trigger from 0x%x","The NTI ISSU process received a trigger from this endpoint before the negotiation was done. The trigger will be ignored.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTI","3","ISSU_UNKNOWN_MSG_TYPE","NTI ISSU got an unknown message type: %d","The NTI ISSU process received an unknown message type while trying to get the message MTU. The message cannot be sent.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTI","3","ISSU_XMIT_FAILED","NTI ISSU failed to transform message type %d for transmit to 0x%x (%s)","The NTI ISSU process was unable to transform the message for transmit. The message cannot be sent.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTI","3","TRIG_ABORT_ALL_CLIENTS","%s Aborting trigger processing for all clients as requested by the platform, EP ID 0x%x trigger type %s trigger group %s","Trigger processing has been aborted for all clients due to a platform request.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTI","3","TRIG_CLIENT_NOTINLIST","%s Cannot trigger NTI client (%d) for this EP: could not find client in list, EP ID 0x%x","An NTI client could not be triggered for an endpoint because the client could not be found in the list.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTI","3","TRIG_INIT_ALREADY_IN_PROGRESS","%s Cannot initiate NTI trigger for EP ID 0x%x at this time: trigger processing of trigger type %s, trigger group %s already in progress","An NTI trigger could not be initiated because a trigger is already in progress.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTI","3","TRIG_PROCESSING","%s Trigger processing ERROR for client (#%d - %s), EP ID 0x%x trigger type %s trigger group %s : %s","An NTI trigger processing error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"NTP","4","PEERUNREACH","Peer [IP_address] is unreachable","The NTP peer is unreachable.","Check the network connection to the peer and ensure that NTP is running on the peer."
"NTP","4","UNSYNC","NTP sync is lost","NTP synchronization to its peer is lost.","Perform the following actions: - Check the network connection to the peer., - Check to ensure that NTP is running on the peer., - Check that the peer is synchronized to a stable time source., - Check to see if the NTP packets from the peer have passed the validity tests specified in RFC1305."
"NTP","5","PEERSYNC","NTP synced to peer [IP_address]","NTP has synchronized the local clock to a new peer.","No action is required."
"NTP","6","PEERREACH","Peer [IP_address] is reachable","The NTP peer is reachable.","No action is required."
"NTP","6","RESTART","NTP process starts","The NTP process has just started or restarted.","No action is required."
"NTP","6","STOP","NTP process stops","NTP is disabled.","Check to see if NTP has been manually disabled by the administrator."
"OBFL","5","DISABLED","Onboard Failure Logging disabled","Onboard Failure Logging has been disabled.","No action is required."
"OBFL_ERRMSG","5","FILECREATEFAIL","OBFL [chars] App failed to open/create file [chars] . Errno = [dec]","The file open or creation operation failed.","No action is required."
"OBFL_ERRMSG","5","FILEFSTATFAIL","OBFL [chars] App failed to fstat file [chars] . Errno = [dec]","The file fstat operation failed.","No action is required."
"OBFL_ERRMSG","5","FILELSEEKFAIL","OBFL [chars] App failed to Lseek file [chars] . Errno = [dec]","The file lseek operation failed.","No action is required."
"OBFL_ERRMSG","5","FILEMINFREEFAIL","OBFL [chars] App failed to set coalesce min free","Failed to set the coalesce minimum free value.","No action is required."
"OBFL_ERRMSG","5","FILEOPENFAIL","OBFL [chars] App failed to open file [chars] . Errno = [dec]","The file open operation failed.","No action is required."
"OBFL_ERRMSG","5","FILEREADFAIL","OBFL [chars] App read failure on file [chars] . Errno = [dec]","The file read operation failed.","No action is required."
"OBFL_ERRMSG","5","HISTFILESMALL","OBFL [chars] App: history file is exceedingly small","The history file for this application has been detected to be very small.","No action is required."
"OCE","3","MISSING_HANDLER_FOR_SW_OBJ","Missing handler for '[chars]' function","An internal API request has been ignored because it was unexpected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OCE","3","MISSING_HANDLER_FOR_SW_OBJ_TYPE","Missing handler for '[chars]' function for type [chars]","An internal API request has been ignored because it was unexpected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OCE","3","OCE_CHANGED_BY_APPLY_FUNCTION","Target OCE[hex_addr] changed to[hex_addr] by apply function[hex_addr]","An internal API request has been ignored because it was unexpected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OCE","3","OCEDEPDUMP","[chars]","An error condition triggered display of OCE dependents.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OCE","3","OCE_FWD_STATE_HANDLE","Limit of oce forward state handle allocation reached; maximum allowable number is [int]","Did not store the reinject forwarding state handle, as the maximum number of handles are already in use.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OCE","3","OCE_FWD_STATE_HANDLE_INIT","Failed to initialize a stack of reusable forward state handles; at element [int], initial stack size is [int] elements","Could not allocate enough forwarding state handles for initial handle reuse.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OCE","3","QUEUE_UNLOCK","Failed to [chars] unlock[chars] for [chars] oce [hex]","Failed to enqueue a unlock for an OCE. This condition may lead to a memory leak.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OCE","3","UNEXPECTED_DISP_TYPE","Unexpected disposition type is encounted; expecting disposition types are [chars], found [chars]","An internal disposition counter measure request has been ignored because it was unexpected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OCE","3","UNEXPECTED_SW_OBJ_TYPE","SW_OBJ handle/type mismatch; expecting oce type [chars], found [dec]","An internal API request has been ignored because it was unexpected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OCE","3","UNINITIALIZED_VECTOR","Improperly initialized [chars] vector in [chars] OCE bundle [hex], packet dropped","An OCE bundle vector was improperly initialized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ODM","3","PEER_INCOMPATIBLE","Online Diags Peer Version is different","The version of the peer online diagnostics manager is different from the expected version.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ODM","3","SC_TEST_FAIL","Slot [dec], Subcard [dec],[chars] [chars] Failed","The online diagnostic test for the subcard specified in the error message has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OER_TT_FLOW","2","OER_TT_FLOW_BR_CACHEINIT","Error initializing OER TT Flow BR cache","The NetFlow top talker cache could not be initialized on the border router because of a low-memory condition.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"OER_TT_FLOW","2","OER_TT_FLOW_BR_EXPORTINIT","Error initializing OER TT Flow BR Export queue","The OER NetFlow top talker export queue could not be initialized on the border router because of a low-memory condition.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"OER_TT_FLOW","4","OER_TT_FLOW_BR_FLOWEXPORT","Error exporting [chars]","An error involving a flow to the route processor has occurred.","This is a debug message only. No action is required."
"OIR","3","HARD_RESET","Module [dec] is being hard reset as a part of switchover error recovery","The specified module is being hard reset as a recovery for failure to respond to a switchover message.","No action is required."
"OIR","3","ISSU_RESET","Module %d is being hard reset as a part of ISSU upgrade","The specified module is being hard reset as part of a planned ISSU upgrade.","No action is required."
"OIR","3","LC_FAILURE","Module %d has Major online diagnostic failure, %s","This module experienced a major online diagnostic failure.","Re-seat the card. If the problem persists, copy the error message exactly as it appears. Copy down the system's configuration along with any other relevant information. Contact your technical support representative for assistance."
"OIR","3","PSM_SUBCARDDETECT","Slot [dec] [chars] [dec]: subcard [dec] inserted","A protection switch module (PSM) subcard has been detected in the slot specified in the message text.","No action is required."
"OIR","3","PSM_SUBCARDREMOVE","Slot [dec] [chars] [dec]: subcard [dec] removed","A protection switch module (PSM) subcard has been removed from the specified slot.","No action is required."
"OIR","3","PWRCYCLE","Card in module %d, is being power-cycled '%s'","The OIR facility detected the line card as unresponsive and attempted to power-cycle the card.","No action is required."
"OIR","3","SOFT_RESET","Module [dec] is being soft reset as a part of switchover error recovery","The specified module is being soft reset as a part of switchover error recovery.","No action is required."
"OIR","3","SOFT_RESET_SSO","Module %d is being soft reset as a part of switchover error recovery","The specified module is being soft reset as a part of a switchover error recovery.","No action is required."
"OIR","3","STDBY_PWRCYCLE","Standby was notified, Card in module [dec] is being power-cycled [chars]","The OIR facility on the redundant supervisor engine was notified that a module on the active supervisor engine is unresponsive. The module is being power-cycled.","No action is required."
"OIR","3","STDBY_UNKNOWN","Standby was notified, Unknown card in slot [dec]","The OIR facility on the redundant supervisor engine was notified that an undetermined module was detected on the active supervisor engine.","Reseat the module in the specified slot."
"OIR","3","UCODE_INTERNAL","The image download to card in slot [dec] failed due to internal error: [chars], [chars]","An internal error has occurred in the line card image download code.","Copy the message exactly as it appears on the console or in the system log. Enter the remote command switch dir system:image/ command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OIR","3","UNKNOWN","Unknown card in slot %d, card is being disabled","The OIR facility detected a line card but could not determine the type.","Reseat the card in the indicated slot."
"OIR","3","UNKNOWN_FANTRAY","Fan Tray idprom read error. Unknown fan-tray in slot %d.","The OIR facility detected a fan-tray but could not determine the type by reading idprom. Fan-tray will not go into high cooling modes.","Reseat the fan-tray in the indicated slot."
"OIR","3","VSS_PWRCYCLE","Card in Switch %d module %d, is being power-cycled '%s'","The OIR facility detected the line card as unresponsive and attempted to power-cycle the card.","No action required."
"OIR","4","DISABLE","Unsupported service module [chars] in slot [dec] disabled","This service module is not supported in this release of software.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OIR","4","INSERTION","Possible half inserted module detected in slot [dec] or a slow insertion","This module is either inserted improperly or is not making a full contact to the backplane or it is being insert very slowly. The user should follow the cisco recommandation on module insertion procedures.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"OIR","4","WARN","[chars]","The OIR facility detected the specified condition.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OIR","6","CONSOLE","Changing console ownership to %s processor","The OIR facility has switched the console to the specified processor.","No action is required."
"OIR","6","CWANVSSISSU","CWAN card present in slot [dec] in the slave chassis is powered down because ISSU is in progress","CWAN card already present in the slave chassis of a virtual switch should not be powered up during ISSU. It will be powered up on switchover or upon completion of ISSU.","No action is required."
"OIR","6","DIAG_OFFLINE","Card inserted in slot [dec], is now ready for offline diagnostics","The OIR facility detected a newly inserted line card. The line card is configured for the offline diagnostic state by the user. This state can be entered only after the module is in the online diagnostic state.","This is an informational message only. No action is required."
"OIR","6","DIAG_ONLINE","Card inserted in slot [dec], is now ready for online diagnostics","The OIR facility detected a newly inserted line card. The line card is configured for the online diagnostic state by the user or if diagnostic failure is detected during bootup.","This is an informational message only. No action is required."
"OIR","6","DISALLOW","Supervisor attempting to come up as secondary in EHSA mode, will not be allowed.","Primary is in RF mode. As EHSA and RF cannot co-exist, the software will disallow any attempts from secondary to come up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OIR","6","DOWNGRADE","Fabric capable module [dec] not at an appropriate hardware revision level, and can only run in flowthrough mode","This fabric capable module is not at an appropriate hardware revision level, and can run only in flowthrough (bus) mode.","Upgrade the line card hardware."
"OIR","6","DOWNGRADE_EARL","Module [dec] [chars] installed is not identical to system PFC and will perform at current system operating mode.","The PFC/DFC module is at a higher hardware revision than the level of the system PFC. The PFC/DFC module will operate at the same level as that of the system PFC.","This is an informational message only. No action is required."
"OIR","6","INSFAN","Fan [dec] inserted","The OIR facility detected a newly inserted fan tray.","This is an informational message only. No action is required."
"OIR","6","INSPS","Power supply inserted in slot %d","The OIR facility detected the insertion of a powersupply [n]. When turned on, the total power will be adjusted.","This is an informational message only. No action is required."
"OIR","6","NOPWRISSU","Card inserted in slot %d powered down because ISSU is in progress","The online insertion and removal (OIR) facility detected a newly inserted line card during an ISSU upgrade process. The new card will be powered down until completion of the ISSU.","No action is required."
"OIR","6","PROVISION","Module %d does not meet the provisioning requirements, power denied","The provisioning configuration does not allow the type of line card that was inserted.","This is an informational message only. No action is required."
"OIR","6","PWRFAILURE","Module [dec] is being disabled due to power convertor failure [hex]","The DC-DC power converter failed on this module and must be replaced.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OIR","6","REMFAN","Fan [dec] removed","The OIR facility detected the removal of a fan tray [n].","This is an informational message only. No action is required."
"OIR","6","REMPS","Power supply removed from slot %d","The OIR facility detected the removal of a powersupply from slot [n]. The total power will be adjusted and power will be denied to some linecards if needed.","This is an informational message only. No action is required."
"OIR","6","RUNNING_CONFIG","%s %s failed %d (%s)","During switchover, the OIR facility is unable to clean up running-config processor.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OIR","6","SEQ_MISMATCH","SCP seq mismatch for card in slot [dec] : [chars]","The OIR facility detected an SCP sequence mismatch for the card in the specified slot.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OIR","6","SOFT_RESET_ISSU","Module [dec] is being soft reset as a part of ISSU cycle","The module specified in error message is being soft reset as a part of ISSU cycle.","No action is required."
"OIR","6","SP_INSCARD","Card inserted in %sslot %d, interfaces are now online","The OIR facility detected a newly inserted line card. The inserted interfaces will be shut down until it is configured by the user or, if an interface of that type was previously configured, it will be restored to its previous state.","This is an informational message only. No action is required."
"OIR","6","SP_REMCARD","Card removed from slot %d, interfaces disabled","The OIR facility detected the removal of a processor from slot [n]. The interfaces on that processor will be administratively shut down and marked as removed. The routing table will be flushed of any routes through the removed interfaces.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OIR","6","SPINE_PWRFAILURE","Spine Module %d is being disabled due to power convertor failure.","The DC-DC power convertor failed on this module, need to replace hardware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OIR","6","STDBY_INSCARD","Standby was notified, card online in slot [dec]","The OIR facility on the standby supervisor engine was notified by the active supervisor engine that a processor was inserted in slot [n] and that all the interfaces are now usable.","No action is required."
"OIR","6","STDBY_REMCARD","Standby was notified, card removed from slot [dec]","The OIR facility on the standby supervisor engine was notified by the active supervisor engine that a processor from the specified slot has been removed.","No action is required."
"OIR","6","STDBY_SPINE_INSCARD","Standby was notified, xbar module in slot %d is now online.","The OIR facility on Standby Supervisor was notified by the Active that a spine module inserted in slot [n] and the spine module is online","No action is required."
"OIR","6","STDBY_SPINE_REMCARD","Standby was notified, spine card removed from slot %d","The OIR facility on Standby Supervior was notifed by the Active that a spine card in slot[n] has been removed","No action is required."
"OIR_ISSU","3","BUFFER","Cat6K OIR ISSU client failed to a buffer for message, error %d","The online insertion and removal (OIR) ISSU client failed to get a buffer for building a negotiation message. As a result, the client cannot send a negotiation message to the standby unit and the standby unit cannot be brought up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"OIR_ISSU","3","CAPABILITY","Cat6K OIR ISSU client %s","During capability negotiation, the OIR ISSU client detected an error that results in a mismatch between the client capability of the active and standby units.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"OIR_ISSU","3","INIT","Cat6K OIR ISSU client initialization failed at %s, error %s","The OIR ISSU client could not be initialized. This condition will cause a catastrophic failure when an ISSU upgrade or downgrade is performed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OIR_ISSU","3","MSG_NOT_OK","Cat6K OIR ISSU client message %d is not compatible","The OIR ISSU client received an incompatible message from the peer unit. The message cannot be processed by this unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"OIR_ISSU","3","MSG_SIZE","Cat6K OIR ISSU client failed to get the message size for message %d","The OIR ISSU client was unable to calculate the message size for the message specified. The client will be unable to send the message to the standby unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"OIR_ISSU","3","POLICY","Cat6K OIR ISSU client message type %d is %s","The OIR ISSU client received a message type that it does not support. A policy is applied to make the session compatible.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show issu session commands and your pertinent troubleshooting logs."
"OIR_ISSU","3","SEND_FAILED","Cat6K OIR ISSU client failed to send a negotiation message, error %d","The OIR ISSU client could not send a session negotiation message to the peer. As a result, the standby unit cannot be brought up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"OIR_ISSU","3","SESSION","Cat6K OIR ISSU client %s","The OIR ISSU client detected an error during a session negotiation with the peer unit. As a result, the standby unit cannot be brought up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"OIR_ISSU","3","TRANSFORM","Cat6K OIR ISSU client %s transform failed, error %s","The OIR ISSU client could not transform the message. If the transmit transformation failed, the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, the checkpoint message cannot be applied on the standby unit. In either case, the OIR state of the bay will not be identical with the active unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"OIR-SP","6","CONSOLE","Changing console ownership to %s processor","The OIR facility has switched the console to the specified processor.","No action is required."
"OIR-SP","6","DOWNGRADE_EARL","Module %d %s installed is not identical to system PFC and will perform at current system operating mode.","The PFC/DFC module is at a higher hardware revision than the level of the system PFC. The PFC/DFC module will operate at the same level as that of the system PFC.","No action is required."
"OIR-SP","6","INSCARD","Card inserted in slot [dec], interfaces are now online","The OIR facility detects a newly inserted module. The interfaces associated with that module are operational, but are shut down until they are configured by the user. If any interfaces of that type were previously configured, they are restored to their previous state.","No action is required."
"OIR-SP","6","INSPS","Power supply inserted in slot [dec]","The OIR facility has detected the insertion of a power supply in the specified slot. The total power adjusts after the power supply is turned on,","No action is required."
"OLM","3","UNAVAILABLE","Failed to send LMP msg to %s","Attempt to send LMP control message has failed; this could be due to an internal error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OLM","3","UNAVAILABLE","Internal error: Couldn't find neighbor while %s","An LMP processing that requires to access information about the neighbor has found that no such neighbor exists. This could be due to internal error.","Turn on generic and packet level debugging using the command, debug ip lmp and gather LMP configuration using the command, show ip olm and gather the displayed information and contact Cisco technical assistance."
"OLM","3","UNAVAILABLE","Service Discovery: Attribute %s incompatible with neighbor %s","Specified service attribute does not match with neighbor. The neighbor and/or the local node may not be properly configured.","Use the show mpls uni lmp neighbor command on the local as well as the neighbor node (where applicable), to determine the service attributes and modify the configuration, where feasible, to ensure that the attributes match"
"OLM","3","UNAVAILABLE","Service Discovery: Attributes for port %s incompatible with nbr %s","Port-level service attribute does not match with those of the neighbor. The neighbor and/or the local node may not be properly configured.","Use the show mpls uni lmp neighbor command on the local as well as the neighbor node (where applicable), to determine the service attributes and modify the configuration, where feasible, to ensure that the port-level service attributes match"
"OLM","3","UNAVAILABLE","State %s; Event %s","An LMP state machine has encountered an event that is not legal or allowed in the current state.","Write down the state and the event and call your Cisco technical support representative for assistance."
"OLM","4","UNAVAILABLE","Bad LMP Msg; type %u","An LMP message has been received with invalid message type. This suggests that we have a broken LMP implementation on the sending neighbor","Locate the sending neighbor and turn on packet level debugging using the debug ip lmp packets command. On seeing an ill-formed LMP packet, gather displayed information and contact the Cisco technical assistance."
"OLM","4","UNAVAILABLE","Bad TLV; type %u","An LMP message has been received with invalid TLV type. This suggests that we have a broken LMP implementation on the sending neighbor","Locate the sending neighbor and turn on packet level debugging using the debug ip lmp packets command. On seeing an ill-formed LMP packet, gather displayed information and contact the Cisco technical assistance."
"OLM","4","UNAVAILABLE","Invalid TLV Length %u in LMP msg; remaining size %u","An LMP message has been received with invalid TLV length. This suggests that we have a broken LMP implementation on the sending neighbor.","Locate the sending neighbor and turn on packet level debugging using the debug ip lmp packets command. On seeing an ill-formed LMP packet, gather displayed information and contact the Cisco technical assistance."
"OLM","5","UNAVAILABLE","Internal error: Couldn't find IPCC to send LMP msg; msg type : %u","This is generally caused by race conditions wherein an LMP message is received from a neighbor before the first control channel goes UP [locally]. This conditions usually happens when a node reboots.","If the problem persists even after the node has completed initialization, enter sho ip olm command to find the LMP configuration and use the debug ip lmp packets and debug ip lmp generic command to gather additional context type information and call Cisco technical assistance."
"OLM","5","UNAVAILABLE","Invalid TE Link ID %u in Link Summary message","A Link Summary or Link Summary Ack or Link Summary Nack message has been received with bad TE Link ID. The sending node probably doesn't have LMP configured correctly.","Locate the neighbor from which the LMP message with invalid TE Link ID was received and enter show ip olm command and make sure that the port ID mappings between the two nodes are correct"
"OLM","5","UNAVAILABLE","LMP %s msg id %u not 1+%u","An LMP message has been received with message id that is not sequential within the Control channel or TE Link. This situation is not caused by the known cases that cause message id sequence to be broken, including local node reboot, neighbor node reboot and neighbor retransmission","Enter the show ip olm stat command when this problem occurs and gather the information displayed and call the Cisco technical assistance."
"OLM","5","UNAVAILABLE","LMP rcvd msg from unknown src ip 0x%i, link %","An LMP message has been received from a neighbor that we don't know about. This could be due to the fact that the neighbor in question has not yet been configured on this node.","Locate the problem neighbor using the IP address and enter a show ip olm command; gather the displayed info and contact Cisco technical assistance."
"OLM","5","UNAVAILABLE","Link Summary parameter(%s) mismatch","Port ID and other link summary parameters do not match with those on the neighbor in question. The neighbor and/or the local node is not properly configured.","Enter the show ip olm command on the local as well as the neighbor node and make sure that the port IDs match."
"OLM","5","UNAVAILABLE","No such neighbor to assign","User attempted to assign interface to invalid neighbor","Use show olm to find the correct neighbor name"
"ONLINE","2","LCP_BOOT_MISMATCH","The system detected LCP boot version mismatch for module in slot [dec], and will upgrade with new LCP boot image bundled into the system image, and power cycle the module.","The system detected LCP boot version mismatch for module. This condition would normally occur if the LCP boot version on the legacy modules is old for the modules, which require rapid boot support. The LCP boot version is upgraded automatically and the module will be power-cycled.","No action is required."
"ONLINE","3","UNKNOWN_CARD_TYPE","Unknown card type is encountered: card_type = [int]","The card type is unknown or not supported.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ONLINE","6","BOOT_TIMER","Module %d, Proc. %d. Failed to bring online because of boot timer event","The system was unable to download the runtime image to the module and processor because the boot did not complete in the allocated time.","No action is required."
"ONLINE","6","DNLDFAIL","Module %d, Proc. %d, Runtime image download failed because of %s","The system was not able to download the runtime image to the module/proc because of the displayed reason","No action is required."
"ONLINE","6","DNLD_TIMER","Downloading image to Module [dec], Proc. [dec]. has failed, due to download timer expiry","The system was unable to download the runtime image to the module and processor because the download did not complete in the allocated time.","No action is required."
"ONLINE","6","DOWNLOAD_TIMER","Module %d, Proc. %d. Failed to bring online because of download timer event","The system was unable to download the runtime image to the module and processor because the download did not complete in the allocated time.","No action is required."
"ONLINE","6","FIND_MASTER_FAIL","Module %d, Proc. %d. SCP_DNLD failed to find master","The system was unable to find the master to download an image to the module and processor within the allocated time.","No action is required."
"ONLINE","6","GET_IMAGE_FAIL","Module %d, Proc. %d. SCP_DNLD failed to get image","The system was unable to get the image from the master for downloading to the module and processor.","No action is required."
"ONLINE","6","INITFAIL","Module %d: Failed to %s","The system failed to bring the module [n] online, due to the displayed reason","No action is required."
"ONLINE","6","INVALID_DNLD_REQ","Received an unexpected image download request from Linecard Module [dec], Proc [dec]. Linecard image download request reason was [chars]","The system received an image download request from the module and processor complex specified in the message text, but that complex has already downloaded the image and should be initialized and operating normally.","No action is required."
"ONLINE","6","LCC_CONFIG_FAIL","Module %d. LCC Client %s failed to configure at %08x","During a Secure Copy (SCP) download, the Linecard Configuration Coordinator (LCC) client failed to finish configuration of the module.","No action is required."
"ONLINE","6","LCP_DNLD","Error while downloading image to Module [dec], Proc. [dec].: [chars]","An error was encountered while downloading an image to a switching module. The first [dec] is the module number, the second [dec] is the process number, and [chars] is the message explanation.","No action is required."
"ONLINE","6","ONLINE_TIMER","Module %d, Proc. %d. Failed to bring online because of online timer event","The system was unable to download the runtime image to the module and processor because the online event did not happen in the allocated time.","No action is required."
"ONLINE","6","READY_TIMER","Module %d, Proc. %d. Failed to bring online because of ready timer event","The system was unable to download the runtime image to the module and processor because the ASIC initialization did not complete in the allocated time.","No action is required."
"ONLINE","6","REGN_TIMER","Module %d, Proc. %d. Failed to bring online because of registration timer event","The system was unable to download the runtime image to the module and processor because the registration did not complete in the allocated time.","No action is required."
"ONLINE","6","RUNNING_TIMER","Module %d, Proc. %d. Failed to bring online because of running timer event","The system was unable to download the runtime image to the module and processor because the running event did not happen in the allocated time.","No action is required."
"ONLINE","6","VSS_INITFAIL","Switch %d,Module %d: Failed to %s","The system failed to bring the module [n] online, due to the displayed reason","No action is required."
"ONLINEDIAG","2","CPU_SWITCH_LB_TST_PKT_THRESH_ERROR","CPU Switch Interface : [dec]/[dec] of online diagnostic packets in error.","The packet loss can be due to congestion.","Issue the command show diag online cpu sw to get more details about the failure. If this error occurs frequently, contact your technical representative for assistance with the output of the command show techsupport."
"ONS15530","1","DISCOVER_ENET","Failed to init Ethernet device [dec]","The software could not be initialized.","Power down the system, reseat the interface card, and reboot the system. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ONS15530","2","UNAVAILABLE","Invalid resource number from PXF (%d). (PLEASE REPORT THIS!)","The PXF hardware diversion path specified a bad resource number.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ONS15530","2","UNAVAILABLE","No memory available for %s","An attempt at memory allocation failed.","Try these actions to remedy the problem: Add memory. Disable some features. Apply filtering to decrease the size of system data structures - the routing table, for example. In general, reduce other system activities to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"ONS15530","2","UNAVAILABLE","Out of range Card interface, %d on slot %d","The software specified an out-of-range card interface.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ONS15530","2","UNAVAILABLE","Out of range card slot index%d","The software specified an out-of-range card slot index.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ONS15530","2","UNAVAILABLE","Out of range card slot/subslot pair%d/%d","The software specified an out-of-range card slot/subslot pair.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ONS15530","2","UNAVAILABLE","Recursive loop while getting the daughtercard info for card type %d","While getting the daughter card info for the chassismib the platform snmp code goes into an infinite loop.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ONS15530","3","UNAVAILABLE","Access to %s temperature sensor failed","Accesses to chassis temperature sensor failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ONS15530","3","UNAVAILABLE","Err calculating xpolated value: %s","physubcard or idprom ptr is NULL","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ONS15530","3","UNAVAILABLE","Interrupt %s not expected, masking off","An interrupt of a certain type was signalled, but the interrupt handler for this type of interrupt is not yet installed.","This problem should be self-correcting but indicates either a hardware or a software defect. If it's a hardware defect, further problems are to be expected. If it's a software problem, certain types of error and alarm conditions may be left undetected. Copy the error message exactly as it appears, and report it to your technical support representative."
"ONS15530","3","UNAVAILABLE","Mismatch in backplane IDPROM, %s: Active-side=%d, Sby-side=%d","There are two backplane IDPROMS. Each is readable by one of the two redundant CPUs. Most IDPROM fields should be programmed by manufacturing to contain identical information. Only the first mismatched field is shown. Use a CLI show command to see additional mismatches.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ONS15530","3","UNAVAILABLE","Mismatch in backplane IDPROM, %s: Active-side=%s, Sby-side=%s","There are two backplane IDPROMS. Each is readable by one of the two redundant CPUs. Most IDPROM fields should be programmed by manufacturing to contain identical information. Only the first mismatched string is shown. Use a CLI show command to see additional mismatches.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ONS15530","3","UNAVAILABLE","Unknown chassis model.","Data stored in midplane is bad or incomplete.","Contact technical support to update your system."
"ONS15530","3","UNAVAILABLE","card in slot [%d/%d] disabled.","The card is being deactivated.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ONS15530","4","UNAVAILABLE","Invalid CPU ID, assuming revision 1","The CPU ID could not be read from EEPROM. This is probably due to a hardware failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"ONS15530","4","UNAVAILABLE","Unknown MAC address block size.","Data stored in midplane is bad or incomplete.","Contact technical support to update your system."
"ONS15530","5","UNAVAILABLE","Compact flash card (disk0) %s","A file system's status has changed. Follow any instructions provided with the message.","No action is required."
"OOBP","4","UNAVAILABLE","Warning -- oobp can't be used","Async driver can't send out the oobp message because no resource.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OOBP","4","UNAVAILABLE","Warning -- reset async oobp no response","Async driver does not response to the ASYNC RESET command.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OPTICAL_MONITOR","4","FAILED","[chars] [chars]","The current hardware version cannot support monitoring for the rate that was specified.","Specify a different rate for monitoring, if possible. If you require further assistance, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OPTICAL_IF","1","UNAVAILABLE","%s, %s: %s","The specified Alarm has been declared or cleared","Recommended action is to repair the source of the alarm."
"OPTICAL_IF","3","UNAVAILABLE","%s","The metopt subsystem encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OPTICAL_IF_ALARMS","3","UNAVAILABLE","High Alarm Threshold for %s on port %s %s","High alarm threshold was exceeded.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OPTICAL_IF_ALARMS","3","UNAVAILABLE","High Warning Threshold for %s on port %s %s","High warning threshold was exceeded.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OPTICAL_IF_ALARMS","3","UNAVAILABLE","Low Alarm Threshold for %s on port %s %s","Low alarm threshold was exceeded.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OPTICAL_IF_ALARMS","3","UNAVAILABLE","Low Warning Threshold for %s on port %s %s","Low warning threshold was exceeded.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSCP","3","UNAVAILABLE","%s %x","An internal software error occurred. The message contains more information that can be used to identify the problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSCP","4","UNAVAILABLE","Configuration Error: %s","This message indicates a configuration error in the OSCP subsystem. The message will display more specific information about the cause of problem.","Change the configuration to correct the error."
"OSCP","4","UNAVAILABLE","Invalid pkt: %s %d %d","An invalid packet was received from a network peer.","Check the originating device for a cause of the corrupted packets."
"OSCP","7","UNAVAILABLE","%s","This is an informational message only. It is used by Cisco for testing.","Informational messages can be disabled by changing logging level."
"OSM_MULTILINK","3","PROCESS_FAIL","Process creation failed for [chars]","The system failed to create a process. The probable cause of this condition is that the system has low memory.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"OSM_MULTILINK","4","BUNDLEERROR","Bundle([chars]) is not distributed","The bundle specified in the message is not associated with the OSM.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSM_MULTILINK","4","BUNDLENULL","Unexpected bundle missing in [chars] searching for [chars]","A software error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSM_MULTILINK","4","BUNDLEVC","[chars] for vc [dec] and if_index [dec]","A software error has occurred while a bundle was being provisioned.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSM_MULTILINK","4","IDBNULL","Unexpected hwidb missing in [chars]","A software error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSM_MULTILINK","4","IPCNOTREADY","Bundle process on the line card is not ready to handle message of type [dec]","Bundle is being deleted on the line card due to an ip cef disable command and is not ready to process other messages. The most likely cause of this condition is that CEF was disabled and enabled in very quick succession.","Reset the line card."
"OSM_MULTILINK","4","MLPSBNULL","Unexpected subblock missing for [chars]","A software error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSM_MULTILINK","4","NUMLINKS","The bundle had an unexpected number of links([dec]) in [chars]","A software error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSM_MULTILINK","4","QUEUE_BUNDLE","Not able to queue the bundle ([chars]), Num. of bundles [dec]","A software error has occurred while a bundle was being inserted in the queue.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSM_MULTILINK","5","BUNDLEEXCEEDED","Bundle([chars]) cannot be associated with link([chars]), max [dec]","The number of bundles has exceeded the limit for the group belonging to the link. The bundle specified in the error message will not work in distributed mode. If the module is CT3 (OSM-CT3 module), then ports 1-12 belong to one group. If the module is a CHOC-3 module (OSM-CHOC-DS0 module), then ports 1-4 belong to one group. If the module is a CHOC-12 module (OSM-CHOC-DS0 module), then port 1 belongs to one group, and port 2 belongs to the second group. Only 168 bundles can be supported per group. The new bundle created will cause an extra load on the RP CPU.","Remove the multilink interface that is causing this condition."
"OSM_MULTILINK","5","CFGERROR","Cannot set up this bundle link-- [chars] to bundle [chars] reason:[chars]","The bundle link could not be set up. A configuration or resource limit has been reached. The bundle may be forced to become inactive (go down). If the line card is a CT3 (OSM-CT3 line card), then ports 1-12 belong to one group. If the line card is a CHOC-3 (OSM-CHOC-DS0 line card), then ports 1-4 belong to one group. If the line card is a CHOC-12 (OSM-CHOC-DS0 line card), then port 1 belongs to one group and port 2 belongs to the second group. Only 168 bundles can be supported per group and each bundle can have a maximum of 12 links.","Ensure that all links belong to the same group and slot. Check the number of links in the bundle and number of bundles in the group. After the configuration has been corrected, enter the shutdown and no shutdown commands on the multilink interface to shut down and restart the interface."
"OSPF","3","CFG_NBR_ALLOC_FAILED","Could not allocate or find neighbor [IP_address]","An internal error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSPF","3","CFG_NBR_FAILED","Neighbor [IP_address] not configured","The configured neighbor options are not valid.","Check the configuration options for the neighbor command and correct the options or the network type for the neighbor's interface."
"OSPF","3","INT_ATTACHED_MULTI_AREAS","Interface [chars] is attached to more than one area","The interface is attached on the interface list to an area other than the one that the interface links to.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSPF","3","INT_INIT_FAILED","Init failed for interface [chars], [chars].","The interface initialization failed. The following are possible reasons:- The area to which the interface is being attached is being deleted.- It was not possible to create a neighbor datablock for the local router.","Remove the configuration command that covers the interface and try again. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSPF","3","LSA_LEN","Area [chars] router-LSA of length [dec] bytes plus update overhead [dec] bytes is too large to flood.","The router tried to build a router-LSA that is larger than the huge system buffer size or the OSPF protocol imposed maximum.","If the reported total length (LSA size plus overhead) is larger than the huge system buffer size but less than 65535 bytes (the OSPF protocol imposed maximum), you may increase the huge system buffer size. If the reported total length is greater than 65535, you must decrease the number of OSPF interfaces in the reported area."
"OSPF","4","AREA_ALLOC_FAIL","Can not allocate memory for area structure","An internal error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSPF","4","ASBR_WITHOUT_VALID_AREA","Router is currently an ASBR while having only one area which is a stub area","An ASBR must be attached to an area which can carry AS external or NSSA LSAs.","Make the area to which the router is attached into an NSSA or regular area."
"OSPF","4","CFG_NBR_INVAL_NBMA_OPT","Can not use configured neighbor: cost and database-filter options are allowed only for a point-to-multipoint network","The configured neighbor was found on an NBMA network and either the cost or database-filter option was configured. These options are only allowed on point-to-multipoint type networks.","Check the configuration options for the neighbor command and correct the options or the network type for the neighbor's interface."
"OSPF","4","CFG_NBR_INVAL_NET_TYPE","Can not use configured neighbor: neighbor command is allowed only on NBMA and point-to-multipoint networks","The configured neighbor was found on a network for which the network type was neither NBMA or point-to-multipoint.","No action is required."
"OSPF","4","CFG_NBR_INVAL_P2MP_OPT","Can not use configured neighbor: poll and priority options are allowed only for a NBMA network","The configured neighbor was found on a point-to-multipoint network and either the poll or priority option was configured. These options are only allowed on NBMA type networks.","Check the configuration options for the neighbor command and correct the options or the network type for the neighbor's interface."
"OSPF","4","CFG_NBR_P2MP_NEEDS_COST","Can not use configured neighbor: cost or database-filter option is required for point-to-multipoint broadcast network","The configured neighbor was found on a point-to-multipoint broadcast network. Either the cost or database-filter option needs to be configured.","Check the configuration options for the neighbor command and correct the options or the network type for the neighbor's interface."
"OSPF","4","INVALID_METRIC","OSPF-%d Area %s: Router %i originating invalid type %d LSA, ID %i, Metric %d on Link ID %i Link Type %d","The router indicated in this message has originated a Link-State Advertisement (LSA) with an invalid metric. If this is a router LSA and the link metric is zero, routing loops and traffic loss could occur in the network.","On the router that originated the reported LSA, configure a valid metric for the given LSA type and link type."
"OSPF","4","INV_LSA_BLD_FLG","Invalid build flag [hex] for LSA [IP_address], type [dec]","An internal error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSPF","4","NO_IPADDRESS_ON_INT","No IP address for interface [chars]","The interface is not point-to-point and is unnumbered.","Either change the interface type to point-to-point or give the interface an IP address."
"OSPF","4","NO_OUTPUTQ","Packet not written to the output queue","An internal error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSPF","4","NORTRID","OSPF process [dec] failed to allocate unique router-id and cannot start","OSPF failed while attempting to allocate a unique router ID from the IP addresses of its interfaces.","Ensure that at least one interface is active (up) and has a valid IP address. If multiple OSPF processes are running on the router, each requires a unique router ID. Configure a unique router ID manually by entering the router-id a.b.c.d command, or configure an interface in the same VRF table by entering the ip vrf forwarding word command to which the OSPF process belongs. Configure on that interface an IP address that is not used as a router ID by any other OSPF process."
"OSPF","4","NULL_LINKAGE","Doubly linked list linkage is NULL","An internal error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSPF","4","NULL_PREV_LINKAGE","Doubly linked list prev linkage is NULL [hex]","An internal error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSPF","4","OSPF_MAX_LSA","Maximum number of non self-generated LSA has been exceeded '[chars]' - [dec] LSAs","The maximum number of non-self-generated LSAs has been exceeded.","Check if some router in the network is generating a large number of LSAs as a result of misconfiguration."
"OSPF","4","OSPF_MAX_LSA_THR","Threshold for maximum number of non self-generated LSA has been reached '[chars]' - [dec] LSAs","The threshold for the maximum number of non-self-generated LSA has been reached.","Check if some router in the network is generating a large number of LSAs as a result of misconfiguration."
"OSPF","4","RTRID_IN_USE","Router-ID [IP_address] is in use by ospf process [dec]","An attempt was made to assign a router ID that is in use by another process.","Configure another router ID for one of the processes."
"OSPF","4","UNREC_TIMER","Unrecognized timer [dec] in OSPF [chars]","An internal error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSPF","6","BAD_LSA_COUNT","OSPF-%d Area %s: LSA ID %i, Type %d, Adv-rtr %i, LSA counter %s","An internal error was found and automatically corrected in an OSPF Link-State Advertisement (LSA). This error does not affect operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show tech-support ospf commands and your pertinent troubleshooting logs."
"OSPF","6","PROC_REM_FROM_INT","OSPF process [dec] removed from interface [chars]","The OSPF process was removed from the interface due to IP VRF removal.","No action is required."
"OSPF","6","UNREC_VIRT_INT_TYPE","Unrecognized virtual interface [chars]. Treat it as loopback stub route","Because the virtual interface type was not recognized by OSPF, it will be treated as a loopback interface stub route.","No action is required."
"OSPF_NSR","2","ISSU_INIT","ISSU client initialization failed to %s, error: %d (%s)","The OSPF ISSU client could not be initialized. This initialization failure must be addressed before in-service software upgrade or downgrade can be performed successfully. If you do not address this failure, there will be downtime during software upgrade or downgrade.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSPF_NSR","3","CF_ADD_CLIENT","Error adding OSPF checkpoint client: %s","OSPF was not able to register as a client of the checkpoint facility.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support ospf commands and your pertinent troubleshooting logs."
"OSPF_NSR","3","CF_NOMEM","Unable to allocate checkpoint buffer: %s","NSR operation may be degraded because of insufficient memory.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support ospf commands and your pertinent troubleshooting logs."
"OSPF_NSR","3","CF_NOMSG","No space in checkpoint buffer","NSR operation may be degraded because of insufficient memory.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support ospf commands and your pertinent troubleshooting logs."
"OSPF_NSR","3","CHKPT_MSG","Invalid checkpoint message: %s (%s)","NSR will not operate because of an error in a checkpoint message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support ospf commands and your pertinent troubleshooting logs."
"OSPF_NSR","3","ISSU_MSG_SIZE","OSPF%s ISSU client failed to get the MTU for message type %s (%u): %u (%s)","The OSPF ISSU client failed to calculate the MTU for the specified message. The OSPF ISSU client is not able to send the message to the standby device.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support ospf, show issu sessions, show issu negotiated versions commands and your pertinent troubleshooting logs."
"OSPF_NSR","3","ISSU_SESSION_UNREGISTR","OSPF%s ISSU client failed to unregister session information, error: %d (%s)","The OSPF ISSU client failed to unregister session information.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support ospf, show issu sessions, show issu negotiated versions commands and your pertinent troubleshooting logs."
"OSPF_NSR","3","ISSU_TRANSFORM_FAIL","OSPF%s ISSU client %s transform failed for message type %d (%s): %d (%s)","The OSPF ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In both cases, the Archive state between the active device and the standby device is not identical.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support ospf, show issu sessions, show issu negotiated versions commands and your pertinent troubleshooting logs."
"OSPFv3","3","IPSEC_POLICY_SPI_REUSE","%s %s is already configured with SPI %u.","An attempt was made to use a SPI that has already been used","Unconfigure the SPI first, or choose a different one."
"OSPFv3","3","UNAVAILABLE","Could not allocate or find the neighbor","An internal error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSPFv3","3","UNAVAILABLE","DB already exist : area %s lsid %i adv %i type 0x%x","OSPF has a problem locating the LSA, which could lead to a memory leak.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSPFv3","3","UNAVAILABLE","Flagged as being an ABR without a backbone area","The router was flagged as an Area Border Router (ABR) without backbone area in the router.","Restart the OSPF process."
"OSPFv3","3","UNAVAILABLE","Init failed for interface %s, %s.","The interface initialization failed. Possible reasons: 1) The area to which the interface is being attached is being deleted. 2) It was not possible to create the link scope database 3) It was not possible to create a neighbor datablock for the local router","Remove the configuration command that covers the interface and then try it again. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSPFv3","3","UNAVAILABLE","Interface %s is attached to more than one area","The interface is on the interface list for an area other than the one which the interface links to.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSPFv3","3","UNAVAILABLE","Internal error: %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSPFv3","3","UNAVAILABLE","OSPF is enabled on %s during idb initialization","An internal error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSPFv3","3","UNAVAILABLE","OSPF process %d is changing router-id. Reconfigure virtual link neighbors with our new router-id","OSPF process is being reset, and it is going to select a new router-id. This will bring down all virtual links. To make them work again, virtual link configuration needs to be changed on all virtual link neighbors.","Change virtual link configuration on all the virtual link neighbors, to reflect our new router-id."
"OSPFv3","3","UNAVAILABLE","Reached unknown state in neighbor state machine","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSPFv3","3","UNAVAILABLE","if %s if_state %d","An internal error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSPFv3","3","UNAVAILABLE","lsid %i adv %i type 0x%x gateway %i metric %d network %i mask %i protocol %#x attr %#x net-metric %d","OSPF found inconsistency between its database and IP routing table.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSPFv3","4","AREA_MISMATCH","Received packet with incorrect area from[ipv6_addr], [chars], area [IP_address], packet area [IP_address]","An OSPF packet was received with an area ID in its header that does not match the area of this interface.","Check the OSPF configuration of the receiver and the sender for inconsistency."
"OSPFv3","4","ASBR_WITHOUT_VALID_AREA","Router is currently an ASBR while having only one area which is a stub area","An ASBR must be attached to an area which can carry AS external or NSSA LSAs.","Make the area to which the router is attached into an NSSA or regular area."
"OSPFv3","4","CFG_NBR_INVAL_NBMA_OPT","Can not use configured neighbor: cost and database-filter options are allowed only for a point-to-multipoint network","The configured neighbor was found on an NBMA network and either the cost or database-filter option was configured. These options are only allowed on point-to-multipoint type networks.","Check the configuration options for the neighbor command and correct the options or the network type for the neighbor's interface."
"OSPFv3","4","CFG_NBR_INVAL_NET_TYPE","Can not use configured neighbor: neighbor command is allowed only on NBMA and point-to-multipoint networks","The configured neighbor was found on a network for which the network type was neither NBMA or point-to-multipoint.","No action is required."
"OSPFv3","4","CFG_NBR_INVAL_P2MP_OPT","Can not use configured neighbor: poll and priority options are allowed only for a NBMA network","The configured neighbor was found on a point-to-multipoint network and either the poll or priority option was configured. These options are only allowed on NBMA type networks.","Check the configuration options for the neighbor command and correct the options or the network type for the neighbor's interface."
"OSPFv3","4","CFG_NBR_NOT_NBMA_NET","Neighbor command allowed only on NBMA networks","Neighbor command allowed only on NBMA networks.","Check the configuration options for the neighbor command and correct the options or the network type for the neighbor's interface."
"OSPFv3","4","CFG_NBR_P2MP_NEEDS_COST","Can not use configured neighbor: cost or database-filter option is required for point-to-multipoint broadcast network","The configured neighbor was found on a point-to-multipoint broadcast network. Either the cost or database-filter option needs to be configured.","Check the configuration options for the neighbor command and correct the options or the network type for the neighbor's interface."
"OSPFv3","4","DBD_ALLOC_FAIL","Could not allocate DBD packet","An internal error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSPFv3","4","DB_NOT_FOUND","Can't find LSA database type [hex], area [hex] , interface [hex]","An internal error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSPFv3","4","INVALID_METRIC","OSPFv3-%d Area %s: Router %i originating invalid type 0x%x LSA, ID %u, Metric %d on Link ID %d Link Type %d","The specified router has originated a Link-State Advertisement (LSA) with an invalid metric. If this is a router LSA and the link metric is zero, routing loops and traffic loss could occur in the network.","On the router that originated the reported LSA, configure a valid metric for the given LSA type and link type."
"OSPFv3","4","INV_LSA_BLD_FLG","Invalid build flag [hex] for LSA [IP_address], type [hex]","An internal error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSPFv3","4","NO_GLOBAL_ADDR","Could not select a global IPv6 address. Virtual links require at least one global IPv6 address.","A virtual link was configured. For the virtual link to function, a global IPv6 address must be available. However, no global IPv6 address could be found on the router.","Configure a global IPv6 address on an interface on this router."
"OSPFv3","4","NO_OUTPUTQ","Packet not written to the output queue","An internal error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSPFv3","4","NULL_LINKAGE","Doubly linked list linkage is NULL","An internal error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSPFv3","4","NULL_PREV_LINKAGE","Doubly linked list prev linkage is NULL [hex]","An internal error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSPFv3","4","RTRID_IN_USE","Router-ID [IP_address] is in use by ospf process [dec]","An attempt was made to assign a router ID that is in use by another process.","Configure another router ID for one of the processes."
"OSPFv3","4","TIMER_ERROR","Error for timer [dec] in OSPF process [chars]","An internal error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSPFv3","4","TWO_INT_ON_LINK","Multiple interfaces ([chars]/[chars]) on a single link detected. This is not supported","OSPFv3 enabled on multiple interfaces that are on the same link is not supported.","OSPFv3 should be disabled or made passive on all but one of the interfaces."
"OSPFv3","4","UNREC_TIMER","Unrecognized timer [dec] in OSPF [chars]","An internal error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"OSPFv3","5","UNAVAILABLE","Process %d, Nbr %i on %s from %s to %s, %s","An OSPF neighbor has changed state. The message describes the change and the reason for it. This message appears only if the log-adjacency-changes command is configured for the OSPF process.","LOG_STD_NO_ACTION"
"OSPFv3","6","UNREC_VIRT_INT_TYPE","Unrecognized virtual interface [chars]. Treat it as loopback stub route","Because the virtual interface type was not recognized by OSPFv3, it will be treated as a loopback interface stub route.","No action is required."
"OUNIC","4","UNAVAILABLE","%s","IOS OS API routine return error","Copy the error message exactly as it appears, and report it to your technical support representative."
"OUNIC","4","UNAVAILABLE","%s(%s): %s","RSVP API routine return error","Copy the error message exactly as it appears, and report it to your technical support representative."
"OUNIC","4","UNAVAILABLE","failed getting local_port_id for: neighor %i, remote_port_id=%d","Destination O-UNI client cannot find its own local_port_id","Copy the error message exactly as it appears, and report it to your technical support representative."
"OTNMGR","3","OTN_STATS_CREATE_IF_FAIL","stats for interface index [dec] could not be created with status [dec]","N/A","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACC","3","RXPAKLEN","PA-CC FPGA detected an ingress packet length error on slot [dec]","The PA carrier card has detected a packet length error during reception of an ingress packet.This condition could be caused by one of the following: - Faulty hardware (either the Cisco 7300 or the PA carrier card) - A corrupted FPGA image- A software problem (least likely).","If this message occurs frequently, remove and reinsert the PA carrier card. If reseating the card does not fix the problem, a later Cisco IOS image may have an updated FPGA bundle that could solve the problem. If this message recurs, copy the error 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACC","3","TXPAKLEN","PA-CC FPGA detected an egress packet length error on slot [dec]","The PA carrier card has detected a packet length error during transmission of an egress packet. This condition could be caused by one of the following: - Faulty hardware (either the Cisco 7300 or the PA carrier card) - A corrupted FPGA image- A software problem (least likely).","If this message occurs frequently, remove and reinsert the PA carrier card. If reseating the card does not fix the problem, a later Cisco IOS image may have an updated FPGA bundle that could solve the problem. If this message recurs, copy the error 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PA","0","UNAVAILABLE","Conflict detected when trying to install %s interrupt handler, bay %d.","An attempt was made to register an interrupt handler for either a non existent port adaptor or the wrong interrupt prority level.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PA","2","UNAVAILABLE","Bad default register(%x) setting(%x) in PA bridge","The software is unable to configure certain settings for the port adapter protocol control information bridge in the specified bay.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PA","2","UNAVAILABLE","Failed to config bridge for PA %d","The system side PCI bridge for this PA failed initialization. The PA will not be operational because of this.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PA","2","UNAVAILABLE","Illegal Port Adaptor type %d in bay %d of %s.","The port adapter is not supported by the controller to which it is plugged into.","Remove the port adapter and return the controller to its original configuration."
"PA","2","UNAVAILABLE","Out of range PCI Port Adaptor bay %d","The software specified an out-of-range port adapter bay.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PA","2","UNAVAILABLE","Out of range PCI Port Adaptor interface, %d on bay %d","The software specified an out-of-range port adapter interface.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PA","2","UNAVAILABLE","PA interface data incorrect, %#x","Incorrect PA interface data found","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PA","2","UNAVAILABLE","PA interface idb incorrect, %#x","The port adapter system control block (PASCB) data structure indicates a zero interface descriptor block (IDB).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PA","2","UNAVAILABLE","PA interface pa incorrect, %#x","Incorrect PA interface specified","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PA","2","UNAVAILABLE","PA interface pascb incorrect, %#x","The port adapter system control block (PASCB) data structure was incorrectly set in the command data structure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PA","2","UNAVAILABLE","PA interface port_inst incorrect, %#x","Failure to access port instance internal data","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PA","2","UNAVAILABLE","PA interface vcont incorrect, %#x","Incorrect VC interface specified","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PA","2","UNAVAILABLE","PA null adapter, %#x","Null PA interface specified","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PA","2","UNAVAILABLE","PA queue overflow, cmd %#x","PA queue has overflowed; programming lost","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PA","2","UNAVAILABLE","Recursive loop while getting the daughtercard info for PA type %d","While getting the daughter card info for the chassismib the platform snmp code goes into an infinite loop.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PA","2","UNAVAILABLE","Undefined Port Adaptor type %d in bay %d","The software does not have a driver for the port adapter type in the specified bay.","Make sure the image you are running is supposed to support this card. Check that the card is properly seated. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PA","2","UNAVAILABLE","Unsupported I/O Controller (type %d) in I/O Bay. The I/O Controller network interfaces will be unavailable.","The software does not have a driver for the port adapter type in the specified bay.","Make sure the image you are running is supposed to support this card. Newer I/O Controllers will only work with the -kboot- image. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PA","2","UNAVAILABLE","Unsupported Port Adaptor Bridge %#x in bay %d","The software does not have a driver for that port adapter protocol control information bridge in the specified bay.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PA","3","UNAVAILABLE","Improper insertion for slot %d. Remove and then re-insert the PA","PCI Activation of PA has failed, thus the PA is deactivated and must be removed and then re-inserted.","Remove and then re-insert the PA firmly into the slot."
"PA","3","UNAVAILABLE","PA in slot%d (%s) is not supported on this %s","This port adaptor is not supported on this chassis/cpucard.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PA","3","UNAVAILABLE","PA in slot%d (%s) requires base h/w revision of (%d.%d) for this %s","A newer hardware revision of the port adaptor is required for functional operation on this chassis.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PA","3","UNAVAILABLE","Recommended port adapter configuration exceeded","The total bandwidth of fast and medium bandwidth port adapters exceed the rated capacity of this system.","Refer to the configuration guidelines for the maximum allowed high and medium bandwidth port adapters for the system."
"PA","3","UNAVAILABLE","This PA type (%s) is not supported in slot%d of this %s","This port adaptor is not supported on this slot of this chassis/cpucard.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PA","3","UNAVAILABLE","Unable to create driver for Port Adaptor type %d in bay %d","Possible memory shortage or adaptor hardware error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PA","3","UNAVAILABLE","port adapter in bay [%d] failed to reset.","An attempt to reset and initialize the port adapter timed out.","This situation should correct itself. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PA","3","UNAVAILABLE","port adapter in bay [%d] powered off.","The port adapter is being powered off.","This situation should correct itself. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PA","4","UNAVAILABLE","Improper removal for slot %d.","PA was inserted and then removed while being initialised.","After an insertion, the PA should be pulled out only after the initialisation is complete. If there is any traffic running through the router, the initialisation can take up to 30 seconds"
"PA","4","UNAVAILABLE","PCI activation failed, bay %d, 0x%x","The system received an invalid PCI signal from the port adapter. This is probably due to a hardware failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACKET","2","ACCESSERROR","Client process %ld attempted to access packet %x owned by process %ld","A packet manager client can only access and modify packets that have been assigned to its process","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","BLOCKERROR","Client process %ld has packet 0x%8x , the buffer 0x%8x has been corrupted.","Data has been written past the end of the previous buffer causing memory to be corrupted.","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","CHANCREATEFAIL","Packet server fails to create a channel and event manager error: %s","Packet server fails to create an event manager and channel. Clients will be unable to connect to packet server, and packet server will be unable to send and receive messages.","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","CHUNKCREATEFAIL","chunk_create for %s pool failed","The packet manager encountered a chunk creation failure while creating the packet header chunk","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","CONNECTFAIL","Client process %ld failed to connect to Packet Manager (reason %s)","A packet manager client failed to connect to Packet Manager","Restart the process which could not connect to Packet Manager. Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","CTXERROR","The context information 0x%8x is not valid.","An application to the memory block manager has passed either a context pointer that is not valid.","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","DEQUEUEFAIL","Fail to remove client %ld from pak_client_list at %s","Can not remove the client from client list queue. This may cause the client fail to reconnect to packet server","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","ENQUEUEFAIL","Fail to insert client %ld into pak_client_list at %s","Can not insert the client into client list queue. This causes the client unable to connect to packet server","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","EVENTATTACHFAIL","event attach failure","The packet subsystem encountered an error when registering for synchronous or asynchronous events.","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","EVENTBLOCKFAIL","event_block failure","event block error was encountered when blocking for external events","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","EVENTCONTEXTALLOCFAIL","event_context_alloc failure","Failed while allocating the event context","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","GETNODENAMEFAIL","failed to get node name in pakman server init","packet manager server unable to retrieve the hostname for node/linecard","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","HDRPOOLINITFAIL","Packet header pool init failed","Failed to initialize the packet pool headers","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","MEMBLKERROR","Memory block 0x%8x is not valid.","An application to the memory block manager has passed a memory block that is not valid.","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","MEMFREEERROR","Memory block 0x%8x has already been freed.","An application to the memory block manager has attempted to free or lock a memory block that is not allocated.","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","MUTEXFAIL","mutex %s operation on %s in %s failed; reason %s","Mutex operation failed in the packet server","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","NEXTBLOCKERROR","The next block after buffer 0x%8x (packet 0x%8x) has been corrupted.","Data has been written past the end of the current buffer causing memory to be corrupted.","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","PTHREADCREATEFAIL","pthread create fail in pakman while creating the %s thread","packet manager server unable to create a new thread","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","PTHREADMUTEXFAIL","pthread_mutex_init failed on packet mutex. Reason : %s","The packet manager failed to initialize the global mutex","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","SHMCREATEFAIL","Error in creating the shared buffer mem: %s","Fatal error encountered while creating shared packet buffers","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","SHMCTLFAIL","Error in shm_ctl: %s","Fatal error encountered while doing the shm_ctl operations on the shared packet memory","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","3","BLKDUMP","[chars]","This message is for reporting general messages in the memory management code.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACKET","3","CLNTDISCONN","Handling disconnect for client [dec] ([chars])","The client ID was not found in the previous client list.","Remove the client's information from the list of all connected clients. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACKET","3","CORRUPTPAKHDR","Corruption in packet header [hex], pid [dec], magic [hex], buffer [hex] caller_pc [hex]","The packet header has become corrupted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACKET","3","CORRUPTPAKPOOL","[chars] Pool [hex] corrupted, magic [hex]","The packet pool has become corrupted and has failed a consistency check.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACKET","3","ERRORPUNT","Intransit flag not set in [dec]","A packet that is being redirected across processes does not have the Intransit flag set.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACKET","3","ERRPAKHDR","Not able to fix corruption in packet header [hex], pid = [dec]","There has been a corruption in the packet header memory and it cannot be fixed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACKET","3","IFINPUTCOUNTERROR","Packet: %p with linktype:%d being punted from process: %ld to process: %ld with out decrementing the input_qcount","An attempt was made to punt the packet from one process to another with the input queue flag set. This means that the input_qcount was not decremented on the interface where the packet was received. This will lead to input queue throttling on that interface","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","3","INITFAIL","Packet server initialization failed. Reason : %s","The packet subsystem was not able to initialize properly","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","3","INITWARNING","Warning(%s) while initializing the packet process","The packet subsystem detected some errors while initializing","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","3","PACKETHDRDUMP","[chars]","This message is used to report general packet header messages.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACKET","3","PAK_INPUTQ_ERROR","Packet: %p in process: %ld has PAK_INPUTQ set incorrectly","A packet outside the iosbase has the input queue flag set. This means that a packet was punted from the iosbase to another ION process without decrementing the input queue count","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","3","PARTICLEPAKDUPFAIL","Particle packet duplication attempted on non-particle packet","Duplication of packet with particles routine is called without the packet containing particles.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACKET","3","RECOVERBLK","BLOCK [hex] IS SUCESSFULLY RECOVERED AFTER CORRUPTION","Corruption was detected in a memory block, and it was possible to recover the block successfully.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACKET","3","REFCOUNTERROR","Bad reference count in packet: %p refcount: %d.","An attempt was made to free a packet that has already been freed","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","3","REINITSHMEM","Restarting [chars] to reinitialize shared memory because of memory corruption","There has been a memory corruption.","Restart the client to reinitialize shared memory. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACKET","3","RESTARTFAIL","Packet server restart failed. Reason : %s","The packet subsystem was not able to restart properly","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACC","0","UNAVAILABLE","%s HW DLLs failed to lock in linecard at slot %d","The port adapter carrier card has failed to initialize. This condition indicates a hardware failure.","Remove and reinsert the port adapter carrier card. If reseating the card does not fix the problem, a later IOS image may have an updated FPGA bundle that could potentially solve the problem. If this message recurs, do the following: show diag slot-number. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACC","0","UNAVAILABLE","%s initialization failure for slot %d, %s","The initialization of a device on the PA carrier card has failed. The error message first specifies the device whose initialization failed. Slot number and either the interface name or more details about the error are displayed at the end of the message. This condition indicates a software error.","Show memory summary. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACC","1","UNAVAILABLE","%s (slot %d) %s allocation failure","The router has failed to allocate sufficient memory for a component of the PA carrier card. This component is displayed after the slot number in the message text.","Show memory summary. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACC","3","UNAVAILABLE","%s Loss of heartbeat from linecard in slot %d","The port adapter carrier card has failed to send keepalives (heartbeats) to the Route Processor (RP). The slot number is specified in the error message. This condition usually indicates a software error.","Copy the error message, and any messages preceding this message that may be related to this message, exactly as they appear on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information."
"PACC","3","UNAVAILABLE","Egress packet parity error on slot %d","The FPGA on the PA carrier card detected a parity error on an egress frame.","This problem could be caused by either faulty hardware (either the Cisco 7300 or the PA carrier card), by a corrupted FPGA image, or, with a very low likelihood, by software problems. If this occurs frequently, remove and reinsert the PA carrier card. If reseating the card does not fix the problem, a later IOS image may have an updated FPGA bundle that could potentially solve the problem. If this message recurs, do the following: show diag slot-number. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACC","3","UNAVAILABLE","Egress packet slot ID mismatch on slot %d","The FPGA on the PA carrier card detected a slot ID mismatch on an egress packet","This problem could be caused by either faulty hardware (either the Cisco 7300 or the PA carrier card), by a corrupted FPGA image, or, with a very low likelihood, by software problems. If this occurs frequently, remove and reinsert the PA carrier card. If reseating the card does not fix the problem, a later IOS image may have an updated FPGA bundle that could potentially solve the problem. If this message recurs, do the following:show diag slot-number. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACC","3","UNAVAILABLE","Ingress packet parity error on slot %d","The FPGA on the PA carrier card detected a parity error on an ingress frame.","This problem could be caused by either faulty hardware (either the Cisco 7300 or the PA carrier card), by a corrupted FPGA image, or, with a very low likelihood, by software problems. If this occurs frequently, remove and reinsert the PA carrier card. If reseating the card does not fix the problem, a later IOS image may have an updated FPGA bundle that could potentially solve the problem. If this message recurs, do the following:show diag slot-number. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACC","3","UNAVAILABLE","No port adapter detected in slot %d","The port adapter carrier card ROM Monitor has not detected any port adapter plugged into the port adapter carrier card.","Ensure that the port adapter is plugged correctly into the port adapter carrier card"
"PACC","3","UNAVAILABLE","No port adapter type obtained for slot %d","The port adapter carrier card ROM Monitor has not reported any information about the port adapter that is plugged into the port adapter carrier card. This condition could be caused by either a hardware or a software problem and indicates a communication problem between the ROM monitor for the carrier card and the Cisco 7300.","Remove and reinsert the port adapter carrier card. If this message recurs, do the following: Show dialog slot-number). 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACC","3","UNAVAILABLE","PA-CC FPGA Common Logic egress buffer overflow on slot %d","The backplane side of the common logic in the FPGA on the PA carrier card has experienced a buffer overflow for egress packets.","This problem could be caused by either faulty hardware (either the Cisco 7300 or the PA carrier card), by a corrupted FPGA image, or, with a very low likelihood, by software problems. If this occurs frequently, remove and reinsert the PA carrier card. If reseating the card does not fix the problem, a later IOS image may have an updated FPGA bundle that could potentially solve the problem. If this message recurs, do the following: Show dialog slot-number). 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACC","3","UNAVAILABLE","PA-CC FPGA detected an egress packet length error on slot %d","The PA carrier card has detected a packet length error during transmission of an egress packet.","This problem could be caused by either faulty hardware (either the Cisco 7300 or the PA carrier card), by a corrupted FPGA image, or, with a very low likelihood, by software problems. If this occurs frequently, remove and reinsert the PA carrier card. If reseating the card does not fix the problem, a later IOS image may have an updated FPGA bundle that could potentially solve the problem. If this message recurs, do the following: Show dialog slot-number). 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACC","3","UNAVAILABLE","PA-CC FPGA detected an ingress packet length error on slot %d","The PA carrier card has detected a packet length error during reception of an ingress packet.","This problem could be caused by either faulty hardware (either the Cisco 7300 or the PA carrier card), by a corrupted FPGA image, or, with a very low likelihood, by software problems. If this occurs frequently, remove and reinsert the PA carrier card. If reseating the card does not fix the problem, a later IOS image may have an updated FPGA bundle that could potentially solve the problem. If this message recurs, do the following: Show dialog slot-number). 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACC","3","UNAVAILABLE","PA-CC FPGA flow control failure from slot %d","The FPGA on the PA carrier card was unable to generate a flow control frame.","This problem could be caused by either faulty hardware (either the Cisco 7300 or the PA carrier card), by a corrupted FPGA image, or, with a very low likelihood, by software problems. If this occurs frequently, remove and reinsert the PA carrier card. If reseating the card does not fix the problem, a later IOS image may have an updated FPGA bundle that could potentially solve the problem. If this message recurs, do the following: Show dialog slot-number). 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACC","3","UNAVAILABLE","PA-CC FPGA ingress buffer overflow on slot %d","The FPGA on the PA carrier card detected a failure of hardware flow control for ingress frames.","This problem could be caused by either faulty hardware (either the Cisco 7300 or the PA carrier card), by a corrupted FPGA image, or, with a very low likelihood, by software problems. If this occurs frequently, remove and reinsert the PA carrier card. If reseating the card does not fix the problem, a later IOS image may have an updated FPGA bundle that could potentially solve the problem. If this message recurs, do the following: Show dialog slot-number). 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACC","3","UNAVAILABLE","PA-CC FPGA ingress packet too small error on slot %d","The FPGA on the PA carrier card detected a too small packet for an ingress frame from the PA carrier card CPU interface.","Show dialog slot-number. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACC","3","UNAVAILABLE","PA-CC in slot %d has returned to ROM Monitor: %s","The PA carrier card in the slot specified in the error message has experienced a system failure and has returned to ROM monitor mode. Additional information in the error message shows the stack trace from the PA carrier card failure.","Show dialog slot-number. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACC","3","UNAVAILABLE","The PA-CC in slot %d contains a PA with a H/W revision of (%d.%d). The required minimum H/W revision for this PA is (%d.%d).","The port adapter in the slot specified in the error message has a downlevel hardware revision. A newer hardware revision of the port adapter is required for the PA carrier card to function on the chassis.","Replace the downlevel port adapter with a port adapter of a later hardware revision. The minimum hardware revision is shown in the error message."
"PACC","3","UNAVAILABLE","Unrecognized port adapter in slot %d","The port adapter carrier card ROM Monitor has detected a Port adapter but was unable to determine the port adapter type from the port adapter ID PROM","Remove the port adapter carrier card, then remove the port adapter from the line card. Reinsert the port adapter into the line card and ensure that the port adapter is fully inserted. Close the latch on the port adapter carrier card and reinsert the port adapter carrier card into the router. If the problem persists then insert the port adapter into another router (e.g. a c7200, c7400, c7301 or c7500). If the port adapter is not functional in another router, the port adapter needs to be replaced."
"PACC","3","UNAVAILABLE","Unsupported port adapter (type %d) in slot %d","An unsupported port adapter of the indicated type has been inserted into the PA carrier card in the slot indicated in the error message.","Replace the port adapter."
"PACC_IPC","0","UNAVAILABLE","Cannot create the master seat","The master IPC seat could not be created. The master seat resides on the Route Processor (RP) and the PA Carrier Card was not able to create an entry to the RP seat. This indicates a communication problem with the RP.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACC_IPC","0","UNAVAILABLE","Doorbell register information incorrect","A number of parameters are passed to the initialization code through registers known as doorbells. The parameters supplied by the RP are of the incorrect type.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACC_IPC","0","UNAVAILABLE","Nothing written to doorbells yet","The Route Processor (RP) software has not yet written the information needed by the PA Carrier Card startup code. The startup code does not wait for the data and therefore PA Carrier Card could not be initialized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACC_IPC","1","UNAVAILABLE","Cannot create IPC port. IPC error %s","The IPC command port could not be created on the PA Carrier Card. This condition indicates a resource allocation problem in the IPC code.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACC_IPC","1","UNAVAILABLE","Cannot open event port. IPC error %s","The IPC port to receive events from the Route Processor could not be opened. The IPC error code is specified at the end of the error message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACC_IPC","1","UNAVAILABLE","Cannot register local command port. IPC error %s","The IPC local command port could not be registered with the Route Processor. The IPC error code is specified at the end of the error message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACC_IPC","1","UNAVAILABLE","Unexpected wakeup event %d. Process: %s","An unexpected event was received in process only waiting for timer events. This condition indicates a software problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACC_IPC","1","UNAVAILABLE","Unrecognised message: %d","The PA Carrier Card received an unrecognized IPC message. The error message shows the unrecognized command. This condition most likely indicates a software problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACC_IPC","3","UNAVAILABLE","Cannot obtain an IPC reply buffer","The PA Carrier Card could not obtain an IPC message buffer to send a reply back to the Route Processor. This condition indicates a resource allocation problem in the IPC code.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACC_IPC","3","UNAVAILABLE","Failed to send IPC message. IPC error %s","An IPC message could not be sent. This condition indicates a resource allocation problem in the IPC code.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACKET","2","UNAVAILABLE","An attempt to coalesce memory block 0x%8x with its sibling memory block 0x%8x has failed because the sibling block is not valid.","An attempt to coalesce two memory blocks has failed because a memory block is not valid.","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","UNAVAILABLE","Client process %ld attempted to access packet %x owned by process %ld","A packet manager client can only access and modify packets that have been assigned to its process","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACKET","2","UNAVAILABLE","Client process %ld failed to connect to Packet Manager (reason %s)","A packet manager client failed to connect to Packet Manager","Restart the process which could not connect to Packet Manager. Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","UNAVAILABLE","Client process %ld has packet 0x%8x , the buffer 0x%8x has been corrupted.","Data has been written past the end of the previous buffer causing memory to be corrupted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACKET","2","UNAVAILABLE","Client process %ld has packet 0x%8x , the buffer 0x%8x has been overrun.","Data has been written past the end of the buffer causing memory to be corrupted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PACKET","2","UNAVAILABLE","Error in creating the shared buffer mem: %s","Fatal error encountered while creating shared packet buffers","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","UNAVAILABLE","Error in shm_ctl: %s","Fatal error encountered while doing the shm_ctl operations on the shared packet memory","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","UNAVAILABLE","Fail to insert client %ld into pak_client_list at %s","Can not insert the client into client list queue. This causes the client unable to connect to packet server","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","UNAVAILABLE","Fail to remove client %ld from pak_client_list at %s","Can not remove the client from client list queue. This may cause the client fail to reconnect to packet server","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","UNAVAILABLE","Memory block 0x%8x has already been freed.","An application to the memory block manager has attempted to free or lock a memory block that is not allocated.","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","UNAVAILABLE","Memory block 0x%8x is not valid.","An application to the memory block manager has passed a memory block that is not valid.","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","UNAVAILABLE","Packet header pool init failed","Failed to initialize the packet pool headers","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","UNAVAILABLE","Packet server fails to create a channel and event manager error: %s","Packet server fails to create an event manager and channel. Clients will be unable to connect to packet server, and packet server will be unable to send and receive messages.","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","UNAVAILABLE","The context information 0x%8x is not valid.","An application to the memory block manager has passed either a context pointer that is not valid.","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","UNAVAILABLE","The memory block manager has detected an ordinal error. Memory block 0x%8x has an ordinal of 0x%4x and a size of 0x%4x. Its corresponding lower sibling memory block 0x%8x has an ordinal of 0x%4x and a size of 0x%4x.","The lower sibling ordinal should be equal to the difference between the higher sibling's ordinal and size.","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","UNAVAILABLE","The next block after buffer 0x%8x (packet 0x%8x) has been corrupted.","Data has been written past the end of the current buffer causing memory to be corrupted.","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","UNAVAILABLE","chunk_create for %s pool failed","The packet manager encountered a chunk creation failure while creating the packet header chunk","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","UNAVAILABLE","event attach failure","The packet subsystem encountered an error when registering for synchronous or asynchronous events.","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","UNAVAILABLE","event_block failure","event block error was encountered when blocking for external events","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","UNAVAILABLE","event_context_alloc failure","Failed while allocating the event context","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","UNAVAILABLE","failed to get node name in pakman server init","packet manager server unable to retrieve the hostname for node/linecard","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","UNAVAILABLE","mutex %s operation on %s in %s failed; reason %s","Mutex operation failed in the packet server","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","UNAVAILABLE","pthread create fail in pakman while creating the %s thread","packet manager server unable to create a new thread","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","2","UNAVAILABLE","pthread_mutex_init failed on packet mutex. Reason : %s","The packet manager failed to initialize the global mutex","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","3","UNAVAILABLE","BLOCK 0x%x IS SUCESSFULLY RECOVERED AFTER CORRUPTION","Corruption was detected in a memory block, and it was possible to recover the block successfully.","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","3","UNAVAILABLE","%s","This is just to report general messages in the memory management code.","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","3","UNAVAILABLE","%s","This is just to report general packet header messages.","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","3","UNAVAILABLE","%s Pool %x corrupted, magic %x","The packet pool has failed a consistency check as it has got corrupted.","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","3","UNAVAILABLE","Bad reference count in packet: %p refcount: %d.","An attempt was made to free a packet that has already been freed","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","3","UNAVAILABLE","Corruption in packet header %x, pid %d, magic %x, buffer %x caller_pc %x","The packet header has become corrupted.","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","3","UNAVAILABLE","Handling disconnect for client %d (%s)","The client id is not found in the previous client list. Remove the client's information from the list of all connected clients.","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","3","UNAVAILABLE","Intransit flag not set in %d","A packet being punted across processes does not have the Intransit flag set.","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","3","UNAVAILABLE","Not able to fix corruption in packet header %x, pid = %d","There has been a corruption in the packet header memory and it cannot be fixed.","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","3","UNAVAILABLE","Packet server initialization failed. Reason : %s","The packet subsystem was not able to initialize properly","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","3","UNAVAILABLE","Packet server restart failed. Reason : %s","The packet subsystem was not able to restart properly","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","3","UNAVAILABLE","Packet: %p in process: %ld has PAK_INPUTQ set incorrectly","A packet outside the iosbase has the input queue flag set. This means that a packet was punted from the iosbase to another ION process without decrementing the input queue count","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","3","UNAVAILABLE","Packet: %p with linktype:%d being punted from process: %ld to process: %ld with out decrementing the input_qcount","An attempt was made to punt the packet from one process to another with the input queue flag set. This means that the input_qcount was not decremented on the interface where the packet was received. This will lead to input queue throttling on that interface","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","3","UNAVAILABLE","Particle packet duplication attempted on non-particle packet","Duplication of packet with particles routine is called without the packet containing particles.","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","3","UNAVAILABLE","Restarting %s to reinitialize shared memory because of memory corruption","There has been a memory corruption. Restart the client to reinitialise shared memory.","Copy the error message exactly as it appears, and report it to your technical support representative."
"PACKET","3","UNAVAILABLE","Warning(%s) while initializing the packet process","The packet subsystem detected some errors while initializing","Copy the error message exactly as it appears, and report it to your technical support representative."
"PAD","2","UNAVAILABLE","%s called at interrupt level %x","An internal software error occurred.","If this message recurs, copy the error message exactly as it appears and report it to your technical support representative."
"PAD","2","UNAVAILABLE","Tty%t, buffer already setup","An internal software error occurred.","If this message recurs, copy the error message exactly as it appears and report it to your technical support representative."
"PAD","3","UNAVAILABLE","Tty%t, bad return code %d from x3_getline()","An internal software error occurred.","If this message recurs, copy the error message exactly as it appears and report it to your technical support representative."
"PAGP_DUAL_ACTIVE","1","RECOVERY","PAgP running on [chars] triggered dual-active recovery: active id [enet] received, expected [enet]","PAgP detected that the virtual switches were in a dual-active mode on the specified interface. PAgP caused a switch to go into recovery mode.","No action is required."
"PAGP_DUAL_ACTIVE","3","ADD_TLV_FAIL","Too few bytes for [chars] TLV in PAgP (reqd. [dec], got [dec]) on port [chars]","The dual-active type-length-value (TLV) could not be added to the PAgP packet due to too few bytes in the packet. PAgP dual-active detection may be disabled as a result.","Enter these commands:"
"PAGP_DUAL_ACTIVE","3","OBJECT_CREATE_FAILED","Unable to create '[chars]'","The specified managed object could not be created.","No action is required."
"PAGP_DUAL_ACTIVE","3","PROC_CREATE_FAILED","Unable to create process '[chars]'","The specified process could not be created.","No action is required."
"PAGP_DUAL_ACTIVE","3","RECOVERY_TRIGGER","PAgP running on [chars] informing virtual switches of dual-active: new active id [enet], old id [enet]","PAgP received a new active ID on the specified interface, indicating that the virtual switches are in a dual-active mode. When PAgP notifies the virtual switches, one switch will enter recovery mode.","No action is required."
"PAGP_DUAL_ACTIVE","3","REGISTRY_ADD_ERR","Failure in adding to [chars] registry","A function could not be added to the registry.","No action is required."
"PAGP_DUAL_ACTIVE","4","NO_CHNL_GROUP","Port [chars] channel group not present while [chars]","Although the channel group was expected to be present in a link, it could not be extracted. This error may affect functionality, depending on where it occurred. This message indicates a software bug, and should not be seen under normal operation","Enter these commands:"
"PAGP_SWITCH_ISSU","3","BUFFER","PAGP SWITCH ISSU client failed to get buffer for message, error %d","The port aggregation protocol (PAgP) switch ISSU client was unable to get buffer space for building a negotiation message. As a result, it cannot send the negotiation message to the standby unit and the standby unit cannot be brought up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"PAGP_SWITCH_ISSU","3","CAPABILITY","PAGP SWITCH ISSU client %s","During capability negotiation, the PAGP switch ISSU client detected an error that will result in a mismatch in the client capability between the active and standby unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"PAGP_SWITCH_ISSU","3","INIT","PAGP SWITCH ISSU client initialization failed at %s, error %s","The PAGP switch ISSU client could not be initialized. This condition will cause catastrophic failure when an ISSU upgrade or downgrade is performed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PAGP_SWITCH_ISSU","3","MSG_NOT_OK","PAGP SWITCH ISSU client message %d is not compatible","The PAGP switch ISSU client received an incompatible message from the peer unit. The message cannot be processed by this unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"PAGP_SWITCH_ISSU","3","MSG_SIZE","PAGP SWITCH ISSU client failed to get the message size for message %d","The PAGP switch ISSU client was unable to calculate the message size for the message specified. The client will be unable to send the message to the standby unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"PAGP_SWITCH_ISSU","3","POLICY","PAGP SWITCH ISSU client message type %d is %s","The PAGP switch ISSU client received a message type that it does not support. A policy is applied to make the session compatible.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show issu session commands and your pertinent troubleshooting logs."
"PAGP_SWITCH_ISSU","3","SEND_FAILED","PAGP SWITCH ISSU client failed to send a negotiation message, error %d","The PAGP switch ISSU client could not send a session negotiation message to the peer. As a result, the standby unit cannot be brought up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"PAGP_SWITCH_ISSU","3","SESSION","PAGP_SWITCH ISSU client %s","The PAGP switch ISSU client detected an error during a session negotiation with the peer unit. As a result, the standby unit cannot be brought up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"PAGP_SWITCH_ISSU","3","SESSION_UNREGISTRY","PAGP SWITCH ISSU client failed to unregister session information. Error: %d (%s)","The PAGP switch ISSU client was unable to unregister session information.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"PAGP_SWITCH_ISSU","3","TRANSFORM","PAGP SWITCH ISSU client %s transform failed, error %s","The PAGP switch ISSU client could not transform the message. If the transmit transformation failed, the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, the checkpoint message cannot be applied on the standby unit. In either case, the PAGP_SWITCH state will not be identical with the active unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"PARSER","2","UNAVAILABLE","Interrupts disabled in mode %s by command '%s'","A hardware or software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"PARSER","3","BADUNLOCKREQ","Unlock requested by process '[dec]'. You are not the lock owner","A configuration unlock has been requested by an alien.","Check the code flow for an unwanted configuration unlock request."
"PARSER","3","CFGLOG_CLI_INITFAILED","Initialization of the Config Log CLI failed.","Initialization of the configuration log CLI failed. Configuration logging CLI commands may not be accessible. The configuration logger may not be accessible by using Cisco IOS software CLI commands.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PARSER","3","CFGLOG_EMPTYCMD","User:[chars]","The user specified entered an empty command for which a log attempt was made. Normally, empty commands will not be logged.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PARSER","3","CFGLOG_INCONSISTENT","User:[chars] command:[chars]","When logging a command entered by CLI, the configuration logger detected an inconsistency in the log. This inconsistency may result in a failure to log the command.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PARSER","3","CFGLOG_INITFAILED","Initialization of the Config Log subsystem failed.","During initialization of the configuration logger subsystem, one or more queues or data structures that are essential to the configuration logger could not be set up. As a result, the configuration logger will not be available for use.","Copy the message exactly as it appears on the console or in the system log. Execute a show version command. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PARSER","3","CFGLOG_NOMEM","User:[chars] [chars]","The command that was entered could not be logged because of a lack of memory. The configuration logger will free old entries one by one until the system logger (syslog) has enough memory to log the command so that an NMS can receive notification of it.","Attempt to free up memory on the router by stopping nonessential processes or unused features that may be running. Once sufficient memory is available, this message no longer appears."
"PARSER","3","CFGLOG_NOUSER","Command:[chars]","The user could not be determined while this command was being logged. The command could not be saved in the configuration log.","Copy the error message exactly as it appears. Enter the show version command, and copy the displayed information. Determine (if possible) which users are currently logged in to the router, and who was copying configuration files or executing commands in global configuration mode (or via SNMP or HTTP). If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PARSER","3","CFGLOG_PERSIST_APPLY_CMD_FAILED","Configuration logger persistency: Applying config command '[chars]' failed. result '[dec]'.","When applying the command to the running configuration, the parser returned an error.","Verify that no other process locks the configuration mode during this time. The parser could be locked by the HA or SNMP or by some other process."
"PARSER","3","CFGLOG_PERSIST_DB_OPEN_FAILED","Configuration logger persistency: opening persist db failed. File '[chars]'.","The file open for writing or reading persisted commands has failed.","Check for the file system availability. The file system might have been corrupted. Try formatting the file system."
"PARSER","3","CFGLOG_PERSIST_FILESYS_FULL","Configuration logger persistency: Add command to persistent db failed. File system '[chars]' full.","When logging a CLI command to the configuration logger persistent database, the configuration logger persistency detected zero bytes free in the file system.","Check the space available in the file system. Enter the dir filesystemname: command to display the free bytes. Clear some space for the configuration logger persistency feature to continue to store the config commands logged in the persistent database."
"PARSER","3","CFGLOG_PURGEFAILED","Purge config log failed.","An attempt to purge some of the configuration log entries failed.","Copy the error message exactly as it appears. Execute a show version command, and copy the displayed information. Contact your technical support representative with this information."
"PARSER","3","CFGLOG_RESIZE_FAILED","Could not resize the config logger to new size:[dec]","Due to an internal error, a request to resize the configuration log was not carried out. Besides a failure to resize, there should be no change in the behavior of the configuration logger.","Copy the error message exactly as it appears. Enter the show version command, and copy the displayed information. Determine (if possible) which users are currently logged in to the router, and who was copying configuration files or executing commands in global configuration mode (or via SNMP or HTTP). If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PARSER","3","CFGLOG_SESSIONERR","Could not delete config log session:[dec] for user:[chars].","When a user logged out, the configuration logger was unable to clean up information about the user's login session. The result might be a memory leak or an inability to add new commands to the configuration log.","Copy the error message exactly as it appears. Enter the show version command, and copy the displayed information. Determine (if possible) which users are currently logged in to the router, and who was copying configuration files or executing commands in global configuration mode (or via SNMP or HTTP). If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PARSER","3","CONFIGNOTLOCKED","Unlock requested by process '[dec]'. Configuration not locked.","A configuration unlock was requested on a free lock.","Check the code flow for an excess configuration unlock request."
"PARSER","4","INVLDSYNTX","Syntax clean up called while not syntax checking. FuncPtr / Context [chars]","Functions were mistakenly called. There may be more than those listed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PARSER","5","CFGLOG_LOGGEDCMD","User:[chars] logged command:[chars]","The configuration logger, which logs every CLI command, has an option to log messages to system logging (syslog). If this option is enabled, this message will be displayed every time a CLI command is processed. This message does not denote any error condition and is a part of the normal operation of the parser and configuration logger.","If you prefer not to see this syslog message, enter the no cfglog send to syslog command."
"PARSER","5","CFGLOG_PERSIST_APPLY_ON_RELOAD","Apply persisted config cmds on reload switched off","The switch that controls the persisted commands applied during reload is set to off.","From the ROMMON prompt, verify the value of the ROMMON logpersistreload variable. This variable might have been intentionally set to off."
"PARSER","6","CONFIGLOCKCLEARED","Configuration lock cleared by user '[chars]' process '[dec]' from terminal '[dec]'","The configuration lock was cleared using the clear configuration lock command.","This is a notification message only. No action is required."
"PARSER","6","CONFIGLOCKNOTSUPPORTED","Configuration lock not supported for this transport '[chars]'","The configuration lock was enabled from a transport other than Telnet or SSH.","This is a notification message only. No action is required."
"PARSER","6","EXPOSEDLOCKACQUIRED","Exclusive configuration lock acquired by user '[chars]' from terminal '[dec]'","An exclusive configuration lock was acquired by the user.","This is a notification message only. No action is required."
"PARSER","6","EXPOSEDLOCKRELEASED","Exclusive configuration lock released from terminal '[dec]'","An exclusive configuration lock was released by the user.","This is a notification message only. No action is required."
"PARSER","6","LI_VIEW_INIT","LI-View initialised.","A lawful intercept (LI) view was successfully initialized.","No action is required."
"PARSER","6","SUPER_VIEW_CREATED","super view '%s' successfully created.","A super view was successfully created and the system has entered the view configuration mode.","No action is required."
"PARSER","6","SUPER_VIEW_DELETED","super view '%s' successfully deleted.","A super view was successfully deleted.","No action is required."
"PARSER","6","SUPER_VIEW_EDIT_ADD","view %s added to superview %s.","A view was successfully added to the super view. All view related configuration can now be accessed from the super view.","No action is required."
"PARSER","6","SUPER_VIEW_EDIT_REMOVE","view %s removed from superview %s.","A view was successfully removed from the super view.","No action is required."
"PARSER","6","VIEW_CREATED","view '%s' successfully created.","A view was successfully created and the system has entered the view configuration mode.","No action is required."
"PARSER","6","VIEW_DELETED","view '%s' successfully deleted.","The required view was successfully deleted.","No action is required."
"PARSER","6","VIEW_SWITCH","successfully set to view '%s'.","The view was successfully selected.","No action is required."
"PARSE_RC","3","PRC_INTERRUPT","[chars]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PARSE_RC","3","PRC_INVALID_BLOCK_PTR",',"An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PARSE_RC","3","PRC_INVALID_CSB",',"An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PARSE_RC","3","PRC_OUT_OF_RANGE_ENUM","[chars] had value [int]","An out-of-range parameter was passed to an internal API.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PARSE_RC","3","PRC_UNRECOGNIZED_ERROR","error value `[dec]' is not currently mapped","An unrecognized error was caught and remapped.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PARSE_RC","4","PRC_NON_COMPLIANCE","`[chars]'","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PARSE_RC","6","PRC_DISABLE","Parser PRC Feature Disabled","The parser return code (PRC) feature is disabled.","No action is required."
"PARSE_RC","6","PRC_ENABLE","Parser PRC Feature Enabled. PRC logs are displayed for configration commands alone","The parser return code (PRC) feature is enabled. PRC logs are displayed for configuration commands alone.","No action is required."
"PATCH","3","UNAVAILABLE","Channel mismatch between %s and %s","Channel mismatch when creating patch.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PBI_OPEN","4","ERROR_ALLOC","%Error: Can't allocate [dec] bytes for pbi data","The system is unable to allocate required memory to access the file.","Check the memory usage of the system and retry the operation."
"PBI_OPEN","4","ERROR_OPEN","%Error: Can't open [chars]","The system is unable to open the file specified.","Ensure that the filename is correct. Enter the dir command to verify the file name."
"PBI_OPEN","4","ERROR_READ","%Error: pbi file [chars] read failed","An unknown error has occurred while the system was copying the PBI program file to a local buffer.","The file name is specified in the message by [chars]. Enter the del filename command to remove the file. Use the copy command to recopy the file from a known good source to its desired destination filename. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PBI_OPEN","4","ERROR_SIZE","%Error: Bad file size [chars]","The file is too small or too large for a PBI program file.","Enter the dir command and verify the size of the file. Retry the operation."
"PBR","2","NO_RMAP","Cannot create PBR data structures for route-map [chars]","The PBR manager could not allocate the data structures needed to describe a route map being used for policy routing. This condition is probably caused by lack of available memory.","Use a less complicated configuration that requires less memory."
"PBR","3","INSTALL_FAIL","Policy route-map [chars] not installed in hardware","The PBR manager was unable to install the complete route map in the hardware, so it will have to be applied in software. This requires the packets to be forwarded by the CPU.","Reconfigure the route map to use a simpler configuration. Use the same route map on multiple interfaces, if possible."
"PBR","3","MERGE_FAIL","[chars] ACL merge error [dec] on route-map [chars]","The PBR manager could not complete the merge of the configured route map into a form suitable for loading into the hardware. The most likely cause is specifying an ACL that is too large or too complex for the system to handle.","Try specifying a smaller and less complicated configuration."
"PBR","3","NO_LABEL","Cannot allocate label for route-map [chars]","The PBR manager could not allocate a label for this route map. This means that the hardware cannot be programmed to implement policy routing. There is a limit of 247 labels for policy routing","Use a less complicated configuration that allows label sharing. Use the same route maps on multiple interfaces, if possible."
"PBR","3","UNSUPPORTED_RMAP","Route-map [chars] not supported for Policy-Based Routing","The route map attached to an interface for policy routing contains an action that is not supported on this platform. This is a hardware limitation.","Reconfigure the route map. Use only permit entries and set ip next-hop actions in the route map."
"PBR","4","CPU_SUPPORTED_ACTION","Set action in sequence [dec] of route-map [chars] supported by forwarding to CPU","The route map attached to an interface for policy routing contains an action that is not supported in hardware, such as a set interface, set ip default next-hop, set default interface, or set ip df action. Because the action is not supported in hardware, the packets must be forwarded by the CPU.","Reconfigure the route map. Use only set ip next-hop in the route map, if possible."
"PBR","4","RETRY_INSTALL","Route-map [chars] installed in hardware upon retry","The PBR manager was able to fit the complete configuration into the hardware. One or more route maps had previously not been loaded because of lack of space.","No action is required."
"PCIELIB","1","NULL_RC","The pointer to root complex [[dec]] is NULL.","The pointer to the specified root complex is NULL.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"PCIELIB","2","INSERT_FAILURE","Failed to insert [hex] into [chars] list.","Failed to insert item into the specified list.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"PCIELIB","2","MMAP_FAILURE","Failed to perform mmap for [chars], errno = [chars].","Failed to perform mmap for the specified memory","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"PCIELIB","2","NO_JID","Could not get my job id. pid [dec]","Could not get my job id","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"PCIELIB","2","PCIELIB_INIT","Could not initialize PCIE library for process [dec]","Could not initialize PCIE library.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"PCIELIB","2","REMOVE_FAILURE","Failed to remove [hex] from [chars] list.","Failed to remove item from the specified list","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"PCIELIB","3","REUSE_LAWBAR","LAWBAR #[dec] is used. orig value = [hex].","The specified LAWBAR register was used for other purpose.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"PCIELIB","3","SHM_OPEN_FAIL","Failed to open shm [chars] errno = [chars].","Failed to open the specified shared memory.Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support.PCMCIAFS MessagesThis section contains PCMCIA disk messages.PCMCIAFS-3Error Message    %PCMCIAFS-3-RESETERR: PCMCIA disk [dec] [chars] Explanation    A PCMCIA disk could not be reset while the system was being initialized or reloaded. This condition will cause a transient disk error or disk timeout error when the ROMMON initialization code tries to read the DIB. This is a transient error and the system will be able to access the disk and continue normal operation.","This is an informational message only. No action is required."
"PCMCIAFS","4","DFS_FSCK_ERR","Error while running fsck on the file [chars].","The fsck process was running in a loop while walking through the cluster chain of a file and has aborted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PCMCIAFS","5","UNAVAILABLE","Error during close of the file %s. %s","An error occured during a file close operation.","Enter the fsck filesystem prefix: command to check and attempt to repair the disk. If this does not fix the problem, format the disk."
"PCMCIAFS","5","UNAVAILABLE","PCMCIA disk %d %s","The system cannot boot a image from the PCMCIA Flash disk because the Device Information Block is different. The Flash disk can be read by the router, but will require formatting by the router before an image can be booted from it.","Follow any instructions provided in the error message. Before storing a image in the Flash disk and trying to boot from this device, enter the format command to format the flash disk from the router. Then copy the desired image to the Flash disk and then boot from this device."
"PERUSER","3","UNAVAILABLE","%s %s: Can not apply configuration to ISDN channel: %s","Configuration can not be applied to individual ISDN channels.","You need virtual-profiles and virtual-access interfaces to apply configuration to ISDN. See the section on virtual-profiles in your manual."
"PF_ASIC","3","ASIC_DUMP","[[dec]:[hex]] [chars] = [hex]","This message includes relevant ASIC counters that might help to diagnose the problem with the switching bus.","Copy this message and the SWITCHING_BUS_IDLE message exactly as they appear on the console or in the system log. Contact your Cisco technical support representative with the output. Include this output along with SWITCHING_BUS_IDLE error message."
"PF_ETHERCHANNEL","3","MLACP_EXTENDED_MISMATCH","An inconstistency was detected between the operational and the configured mlacp-extended mode. Reloading. ([chars])","This error message is printed if there is an inconsistency between the persistent storage stored mode and the configuration mode. It will be display on the SP on boot-up.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"PGM","3","UNAVAILABLE","Failed to allocate %s state","Resources (memory) for retransmit state are exhausted or otherwise not serviceable.","Manually clear all retransmit state (clear ip pgm router) or deconfigure and reconfigure PGM. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PGM","3","UNAVAILABLE","Failed to free %s state","Resources (memory) for retransmit state are not serviceable.","Manually clear all retransmit state (clear ip pgm router) or deconfigure and reconfigure PGM. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PGM","6","UNAVAILABLE","Invalid %s address %i in %s","Received the packet with invalid address.","LOG_STD_NO_ACTION"
"PGM","6","UNAVAILABLE","Malformed packet: %s","A PGM packet did not pass the internal sanity check.","LOG_STD_NO_ACTION"
"PGM","6","UNAVAILABLE","Pak for %i received on %i, fixed input interface","A PGM packet was recieved on an interface other than the one it was addressed to.","LOG_STD_NO_ACTION"
"PGM","6","UNAVAILABLE","TSI group changed from %i to %i","A PGM SPM advertising a new group for the TSI was processed.","LOG_STD_NO_ACTION"
"PGM","6","UNAVAILABLE","TSI source changed from %i to %i","A PGM SPM advertising a new source for the TSI was processed.","LOG_STD_NO_ACTION"
"PGMHOST","6","UNAVAILABLE","Matched TSI but failed to match dport; expected %d actual %d","An incorrectly structured packet has been received from the netwrok.","Investigate and fix the other implementation of PGM."
"PG_TCP","3","UNAVAILABLE","%s","Error Messages","Try the debug command."
"PF","4","MEM_UNAVAIL","Memory was not available to perform the protocol filtering action","Protocol filtering is unable to operate because of a lack of memory","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"PF","4","PROC_START_ERR","Protocol filtering unable to start","The protocol filtering process was unable to be created for unknown reasons.","Start protocol filtering again in case the condition was transient. If this still fails, reload the device"
"PF","4","UNKN_ERR","An unknown operational error occurred","Protocol filtering is unable to operate because an internal operation generated an error which was not expected to ever happen","Because of the unexpected nature of the problem, the only recommended action is to reload the device"
"PF","5","SPANDSTOFF","Protocol filtering disabled on interface %s because it is a span destination","Protocol filtering does not operate on span destination. The protocol filtering configuration stays with the span destination port, but it has no effect and does not appear when you show all non-default protocol filters.","No action is required."
"PF","5","TRUNKPFOFF","Protocol filtering disabled on interface %s because it is a trunk","Protocol filtering does not operate on trunks. The protocol filtering configuration stays with the trunk port, but it has no effect and does not appear when you show all non-default protocol filters.","No action is required."
"PFINIT","1","CONFIG_SYNC_FAIL","Sync'ing the [chars] configuration to the standby Router FAILED, the file may be already locked by a command like: show config.","The active router could not synchronize its configuration with the redundant router. This condition might be a transient one that was caused by the configuration file being temporarily used by another process.","Retry the synchronization operation."
"PFINIT","1","CONFIG_SYNC_FAIL_RETRY","Sync'ing the [chars] configuration to the standby Router FAILED, the file may be already locked by a command like: show config. Will attempt to sync [dec] more time[chars]","The active router could not synchronize its configuration with the redundant router. This condition might be a transient one that was caused by the configuration file being temporarily used by another process.","The synchronization operation will be retried the specified number of times."
"PFINIT","1","CONFIG_SYNC_FAIL_SECONDARY_SYNC_RETRY","Sync'ing the [chars] configuration to the standby Router FAILED with error: [chars] ([dec]).Will attempt to sync [dec] more time[chars]","The active router could not synchronize its configuration with the redundant router. This condition might be a transient one that was caused by the configuration file being temporarily used by another process.","Retry the synchronization operation."
"PFINIT","1","CONFIG_SYNC_SIZE_NULL","Active config file is empty. No sync of the [chars] configuration file required.","The configuration of the active switch was not synchronized with the standby switch because the configuration file of the active switch is empty. This condition might have been the result of the user entering a write erase command on the active router prior to synchronization between the active and standby switches.","If the empty configuration file was the result of user-entered CLI, no action is required. If this was an unexpected condition, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PFINIT","2","EOBC","%s","The PF subsystem could not send IPC bootstap messages to RP.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PFINIT","2","IPCSEAT","Unable to add/remove IPC seats for %s","The platform initialization subsystem could not add or remove interprocess communication (IPC) elements (seats).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PFINIT","2","NOMEM","NULL","The PF subsystem could not obtain the memory it needed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PFINIT","4","IPC_ICC_INIT_FAIL","Failed to [chars]","The PF subsystem failed to initialize some IPC/ICC information.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"PFINIT","5","CONFIG_SYNC_NOT_SUPPORTED","Sync'ing the [chars] configuration to the standby Router is not supported.","The configuration has not been successfully synchronized with the standby router. [chars] is the configuration name.","No action is required."
"PFINIT","6","ACTIVE_NON_VS","Active supervisor is in standalone mode, but SWITCH_NUMBER rommon variable set on the standby or standby having vsl config.Setting SWITCH_NUMBER variable in rommon to 0 and resetting the standby.","The active supervisor is up in standalone mode while standby'srommon has SWITCH_NUMBER set. Clearing SWITCH_NUMBER rommon variable and resetting the standby","This is an informational message. No action is required."
"PF_ISSU","3","ISSU_NEGO_LC_RESET","ISSU negotiation failed between endpoint %d and line card %d, for ISSU client %d","ISSU negotiation failed between an endpoint and a line card. The line card must be reset.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show issu sessions commands and your pertinent troubleshooting logs."
"PF_OBFL","5","FEATURE","Platform OBFL [chars] feature initialization fails in slot [dec].","The PF subsystem could not initialize the on-board failure logging (OBFL) feature specified by [chars].","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PF_OBFL","5","STORAGE","Platform OBFL storage ([chars]) initialization fails in slot [dec].","The PF subsystem could not initialize on-board failure logging (OBFL) storage flash.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PF_PRST_VBL","3","MEDIA","PF persistent variable media error: %s","A media error was detected with the persistent variable PF interface.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PFREDUN","1","VTP_CONFIG_DISLOCATE","VTP config file must be in default location for standby supervisor to come online","The redundant supervisor engine failed to come online because the VTP configuration file is not in the default location.","Reset the standby supervisor engine, and then configure the VTP configuration file so that it is in the default location."
"PFREDUN","3","ACTIVE_FORCED_TO_RELOAD","Active not able to operate properly. Standby is ready to take over and forced active to reload.","The active supervisor engine is not operating properly. It is failing to respond. The standby supervisor engine is ready to take over and forces the active supervisor engine to reload.","If the active does not reload successfully, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PFREDUN","3","CCMODE_MISMATCH","Standby Supervisor cannot support Configured Card Mode [chars]([hex]) due to [chars](enf mask [hex], cap mask [hex], msg ver [hex])!","The active supervisor engine is in user-configured mode (for example, DFC-only mode). The active supervisor engine attempts to bring the standby supervisor engine on line, but incompatible software on the standby cannot support this mode The active keeps the standby in ROMMON mode.","Remove the user-configured mode on the active supervisor engine so that the active can bring the standby on line."
"PFREDUN","3","RELOAD_PEER","Failed to reload VS standby supervisor: %s","Local memory was not big enough to reserve the requested size.Logger buffer will continue with current buffer size","You are trying to reserve more space for the logger, which may affect the system performance. Try this command with less memory size."
"PFREDUN","3","STANDBY_OUT_OF_SYNC","Active and Standby are out of sync.","The active supervisor engine and standby supervisor engine are out of synchronization. This condition may be due to communication failure, configuration synchronization failure, or another cause.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PFREDUN","3","SUP","[chars]","The supervisor engine failed to boot because it detected that the system might contain an invalid combination of supervisor engines.","Examine all modules in the system, and look for an invalid combination of supervisor engines."
"PFREDUN","4","AUTOBOOT","[chars]","The RP experienced a hardware failure or another type of failure. When the redundant system initializes, the redundant supervisor will wait for the RP to initialize. Because the RP cannot initialize due to the failure, the redundant supervisor engine might never initialize. The default wait time for the RP to initialize (three minutes) has now expired, and the autoboot feature for the supervisor engine has been disabled.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PFREDUN","4","BOOTSTRING_INVALID","The bootfile [chars] is not present in standby","The bootfile that is configured is not present on the redundant supervisor engine. If the redundant supervisor engine resets, it will not come up because it will not find the image specified in the bootstring.","No action is required."
"PFREDUN","4","EARL_MISMATCH_4SUP","In-Chassis Standby being disabled ([chars])","This message indicates that there is an Earl mode mismatch between the In-Chassis Active and the In-Chassis Standby and hence In-Chassis Standby is being disabled.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"PFREDUN","4","INCOMPATIBLE","Defaulting to RPR mode (%s)","A runtime incompatibility exists between image versions running on the active and standby supervisors. The redundancy mode will default to route processor redundancy (RPR).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PFREDUN","4","PFC_MISMATCH","My PFC [chars] and Other's PCF [chars] mismatch","The active supervisor engine and the redundant supervisor engine have different versions of the PFC daughter card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PFREDUN","4","PFC_MISMATCH_4SUP","In-Chassis Active PFC is [chars] In-Chassis Standby PFC is [chars]","This message indicates that the In-Chassis Active and the In-Chassis Standby have different versions of the PFC.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"PFREDUN","4","PHYSMEM_MISMATCH","Asymmetrical redundant configuration: Active [chars] has ([int]/[int]K) memory, Standby has ([int]/[int]K).","To support the high availability feature, we recommend that your redundant supervisor engines have symmetrical memory configurations.","Upgrade the memory on the supervisor engine with less memory to match the amount of memory on the other supervisor engine."
"PFREDUN","4","SUP_FORCE_TO_ROMMON","Supervisor forced to rommon with reason: [chars]","An application forced the supervisor engine to stay in ROMMON mode with the reason given.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PFREDUN","4","SUP_OS","The peer supervisor is running a different operating system.","The active supervisor engine is in user-configured mode (for example, DFC-only mode). The active supervisor engine attempts to bring the standby supervisor engine on line, but incompatible software on the standby supervisor engine cannot support this mode. The active supervisor engine keeps the standby supervisor engine in ROMMON mode.","Remove the user-configured mode on the active supervisor engine so that the active supervisor engine can bring the standby supervisor engine on line, or insert a supervisor engine that runs the same operating system as that of the peer supervisor engine."
"PFREDUN","4","VERSION_MISMATCH","Defaulting to RPR mode ([chars])","There is a mismatch of image versions running on the active supervisor engine and on the redundant supervisor engine.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PFREDUN","6","Z_COOKIE","[chars]","Informational messages regarding the presence of z-switchover cookie","No action is required."
"PFREDUN","7","KPA_WARN","RF KPA messages have not been heard for [dec] seconds","The RF KPA messages have not been sent from the peer for the specified numbers of seconds. This message is printed after every third KPA timer expiry.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PFREDUN_SP","3","DIVC_MODE_CHANGE","Redundancy mode changed to RPR","The redundancy mode has changed from stateful switchover (SSO) to route processor redundancy (RPR) because one or more base ISSU clients have failed to successfully negotiate an ISSU session.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PFREDUN_SP","3","DIVC_MODE_CHANGE_RESET","Redundancy mode changed to RPR, standby supervisor being reset","The redundancy mode has changed from SSO to RPR because one or more base ISSU clients have failed to successfully negotiate an ISSU session. The standby supervisor is being reset and will come up in RPR mode.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PFREDUN_SP","3","STANDBY_NEGO_FAILED","Session not negotiated, resetting the standby sup","Both the active and standby supervisors are ISSU capable but the standby failed to negotiate its platform redundancy ISSU session. The standby supervisor must be reset.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PHY","4","CHECK_SUM_FAILED","SFP EEPROM data check sum failed for SFP interface [chars]","The SFP was identified as a Cisco SFP, but the system was unable to read vendor data information to verify its correctness.","Remove and reinsert the SFP. If it fails again in the same way, the SFP may be defective."
"PHY","4","EXCESSIVE_ERRORS","Excessive FCS, data, or idle word errors found on interface [chars]","The system has detected excessive FCS, data word, or idle word errors on the specified interface.","Enter the show interface command on the specified interface and check for CRC and other input errors. If errors are excessive, enter the shut command followed by the no shut command to reset the interface."
"PIM","1","INVALID_RP_REG","Received Register from router %i for group %i, %i not willing to be RP","A PIM router received a register message from another PIM router that thinks it is the rendezvous point. If the router is not configured for another rendezvous point, it will not accept the register message.","Configure all leaf routers (first-hop routers to multicast sources) with the IP address of the valid rendezvous point."
"PIM","1","SR_INTERVAL_SETTING_ERR","Incompatible SR interval from %i on %s (%d != %d)","A state-refresh capable PIM neighbor on this interface has a different setting for the state-refresh origination interval.","Configure all PIM routers connected to this LAN to use the same state-refresh origination interval for their interfaces on the LAN."
"PIM","3","MVRF_NULL_PRM","Null parameter specified for MVRF lookup.","A function to perform a Multicast Virtual Route Forwarding (MVRF) lookup by name detected a NULL input parameter. The intended action cannot proceed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PIM","3","RPDF_NULL_PRM","Null parameter specified for Bidir RP DF creation.","A function to create a bidirectional route processor (RP) designated forwarder (DF) entry detected a NULL input parameter. The RP DF entry cannot be created.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PIM","3","UPD_RPR_NULL_PRM","Null parameter specified for Bidir RP route update.","A function to perform an update of the bidirectional RP route information detected a NULL input parameter. The update cannot proceed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PIM","3","UNAVAILABLE","For multicast route (%i, %i), no register tunnel IDB found for RP %i","During an attempt to install or uninstall a register tunnel interface for an S,G multicast route, the register tunnel entry for the corresponding RP did not specify a tunnel interface. The register tunnel interface can not be added to or removed from the multicast route.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PIM","3","UNAVAILABLE","For multicast route (%i, %i), no register tunnel found for RP %i","During an attempt to install a register tunnel interface for a new S,G multicast route, a search in the PIM register encapsulation tunnel list failed to find the tunnel entry for the corresponding RP. The register tunnel interface can not be added to the multicast route.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PIM","3","UNAVAILABLE","Invalid parameter passed while walking the autorp cache to find a group-to-rp mapping for Sparse RP %i. parameter: 0x%x","An invalid parameter was specified while walking the autorp cache to find a Sparse RP match.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PIM","3","UNAVAILABLE","Managed timer wakeup received by the PIM register tunnel creation process with no expired timers.","The PIM register tunnel creation process received a wakeup for managed timer expiration, but the API to obtain the first expired timer returned a NULL pointer. The timer expiration can not be handled. Possible loss of PIM register tunnel functionality, including failure of PIM Sparse Mode registration for some multicast groups, may occur as a result.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PIM","3","UNAVAILABLE","NULL RP pointer specified for PIM register tunnel creation.","The caller passed a NULL pointer instead of providing a valid pointer to the RP cache entry for which register tunnel creation was requested. The encapsulation or decapsulation tunnel can not be created.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PIM","3","UNAVAILABLE","NULL mvrf specified in PIM register tunnel creation request for RP %i","An NULL mvrf was specified for creation of a PIM register tunnel associated with the specified RP. The register tunnel can not be created.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PIM","3","UNAVAILABLE","NULL mvrf specified in PIM register tunnel entry for RP %i","An NULL mvrf was specified for the PIM register tunnel associated with the specified RP. The register tunnel can not be used for registration.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PIM","3","UNAVAILABLE","NULL mvrf specified in RP mapping notification for RP %i","An NULL mvrf was specified when a PIM RP mapping notification was made.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PIM","3","UNAVAILABLE","No register tunnel IDB found for RP %i. Can't execute pending delete","During an attempt to delete a register tunnel interface that is currently in use for at least one mroute olist entry, the register tunnel entry did not specify a tunnel interface. The register tunnel interface can not be deleted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PIM","3","UNAVAILABLE","Null parameter specified for Bidir RP DF creation.","A function to create a Bidir RP DF entry detected a NULL input parameter. The RP DF entry can not be created.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PIM","3","UNAVAILABLE","Null parameter specified for Bidir RP route update.","A function to perform an update of Bidir RP route information detected a NULL input parameter. The update can not proceed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PIM","3","UNAVAILABLE","Null parameter specified for MVRF lookup.","A function to perform an mvrf lookup by name detected a NULL inputparameter. The intended action can not proceed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PIM","3","UNAVAILABLE","Process enqueue for %s register tunnel creation failed for RP %i.","An attempt to enqueue a request for PIM register tunnel IDB creation failed (probably because of a lack of resources). The encapsulation or decapsulation tunnel can not be created.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PIM","3","UNAVAILABLE","Register tunnel MDB client flag allocation failed.","An attempt to allocate a client flag position for use in tracking the number of mroutes using each PIM register tunnel has failed. Register tunnels can be allocated, but can not deleted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PIM","3","UNAVAILABLE","Tunnel IDB creation for a PIM register %s tunnel for RP %i failed.","An attempt to create a tunnel IDB for use with a PIM register tunnel has failed. The encapsulation or decapsulation tunnel can not be created.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PIM","4","DEPRECATED_HELLO_TLV","Deprecated PIM Hello Option TLV %d (%s) from %i (%s)","A PIM neighbor is running old software that uses deprecated Hello Option TLVs. Unless the router is upgraded, DR priority and bidirectional groups may not function properly.","Upgrade the routers."
"PIM","4","INVALID_SRC_REG","Received Register from %i for (%i, %i), not willing to be RP","A PIM router configured as a rendezvous point received a register message from another PIM router, but the source of the multicast data is disallowed in this RP.","No action is required."
"PIM","5","DRCHG","DR change from neighbor [IP_address] to [IP_address] on interface [chars] (vrf [chars])","A PIM neighbor is the new DR on an interface.","This is an informational message only. No action is required."
"PIM","5","NBRCHG","neighbor [IP_address] [chars] on interface [chars] (vrf [chars]) [chars]","A PIM neighbor has gone up or down on the specified interface.","This is an informational message only. No action is required."
"PIM","5","PROXY","Deny proxy for ([IP_address], [IP_address]) from neighbor [IP_address]","A PIM proxy from the specified neighbor was denied.","No action is required."
"PIM","6","INVALID_RP_JOIN","Received (*, %i) Join from %i for invalid RP %i","A downstream PIM router sent a join message for the shared tree, which this router does not want to accept. This behavior indicates that this router will allow only downstream routers join to a specific rendezvous point.","Configure all downstream leaf routers to join to the RP that is allowed by upstream routers toward the validated rendezvous point."
"PIM","6","REG_ENCAP_INVALID","Bad register from %i for (%i, %i); additional info = %x %x %x %x %x %x %x %x","A PIM router configured as a rendezvous point or with network address translation (NAT) received a PIM register packet from another PIM router. The data encapsulated in this packet is invalid.","No action is required."
"PIM","6","SA_ENCAP_INVALID","Bad SA from RP %i for (%i, %i); additional info = %x %x %x %x %x %x %x %x","A PIM router configured as an MSDP peer received an SA with encapsulated data. The data encapsulated in this packet is invalid.","No action is required."
"PIM_PROT","3","MSG_SEND_ERR","[chars]","An internal error occurred while trying to send a message. Events scheduled to happen on reception of the message, such as deletion of the PIM tunnel IDB, may not take place.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PIM_PROT","4","PROTOCOL_WARNING","[chars] - [chars] [chars] : [chars]","Internal protocol inconsistency warning","No action is required."
"PIM_PROT","6","IDB_ENABLE","Interface [chars] does not support multicast, not enabled","PIM is not enabled on an interface that does not support multicast.","This is an informational message only. No action is required."
"PIM_PROT","7","INTERNAL_ERR","[chars]","An internal error has occurred.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PIMSN","6","IGMPSN_GLOBAL","PIM Snooping global runtime mode [chars] due to IGMP Snooping [chars]","PIM snooping requires that IGMP snooping be enabled. When IGMP snooping is disabled, PIM snooping also becomes disabled. PIM snooping is reenabled when IGMP snooping is reenabled.","No action is required. The system is working properly. We recommend that you leave IGMP snooping enabled."
"PIMSN","6","IGMPSN_VLAN","PIM Snooping runtime mode on vlan [dec] [chars] due to IGMP Snooping [chars]","PIM snooping requires that IGMP snooping be enabled. When IGMP snooping is disabled, PIM snooping also becomes disabled. PIM snooping is reenabled when IGMP snooping is reenabled.","No action is required. The system is working properly. We recommend that you leave IGMP snooping enabled."
"PIM_REG_TUN","3","UNAVAILABLE","Failed to configure service policy on register tunnel.","When the ip pim register-rate-limit CLI command is entered, a rate-limiting policy-map is created. This policy-map is attached to each register tunnel by configuring an output service policy on the tunnel. This message is logged as a result of a failure to configure an output service policy on a register tunnel. This failure may be due to lack of temporary resources, but it may also be caused by platform restrictions on overlapping QoS configurations such as simultaneously having a service policy on a tunnel and on the real interface associated with the tunnel.","LOG_STD_NO_ACTION"
"PIM_REG_TUN","3","UNAVAILABLE","Failed to set un-numbered interface for %s (%s)","The PIM tunnel is not usable without a source address. This can happen because we couldn't find a numbered interface or due to some internal error","Manually unconfigure the PIM-SM RP and re-configure it. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PIM_REG_TUN","3","UNAVAILABLE","Lookup of rate-limit policymap %s failed","When the ip pim register-rate-limit CLI command is entered, a rate-limiting policy-map is created. This policy-map is attached to each register tunnel by configuring an output service policy on the tunnel. A policy-map lookup is therefore performed whenever the register-rate-limit command is enabled or disabled. This message is logged as a result of a lookup failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PIM_REG_TUN","3","UNAVAILABLE","Unexpected tunnel transport: %u.","An unexpected tunnel transport was detected. The location where the value was detected and the execution path that lead to it may be obtained from the traceback included in this message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PKI","3","CERTIFICATE_INVALID","Certificate chain validation has failed.","The certificate is not valid.","Verify that the system clock is set correctly."
"PKI","3","CERTIFICATE_INVALID_EXPIRED","Certificate chain validation has failed. The certificate (SN: [chars]) has expired. Validity period ended on [chars]","The certificate validity period indicates that this certificate has expired.","Verify that the system clock is set correctly."
"PKI","3","CERTIFICATE_INVALID_NOT_YET_VALID","Certificate chain validation has failed. The certificate (SN: [chars]) is not yet valid Validity period starts on [chars]","The certificate validity period indicates that this certificate is not yet valid","Verify that the system clock is set correctly."
"PKI","3","CERTIFICATE_INVALID_UNAUTHORIZED","Certificate chain validation has failed. Unauthorized","The certificate is valid but not authorized","Verify that the system clock is set correctly."
"PKI","3","CERTIFICATE_REVOKED","Certificate chain validation has failed. The certificate (SN: [chars]) is revoked","The certificate has been revoked by the CA administrator.","Contact the CA administrator to check the status of the certificate."
"PKI","3","CERTRETFAIL","Certificate enrollment failed.","A certificate enrollment transaction failed due to internal error.","Contact the CE or 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PKI","3","CS_CRIT_STORAGE","Critical certificate storage, [chars], is inaccessible, server disabled.","The critical certificate storage location is inaccessible, so the server is disabled.","Make the storage location accessible or reconfigure the storage location."
"PKI","3","GETCARACERT","Failed to receive RA/CA certificates.","A failure was encountered while CA or RA certificates were being parsed or processed.","Check the status of the certificate or contact the CA administrator."
"PKI","3","INVALIDCACERT","Failed to process CA certificate.","The CA certificate that was received from the CA server could not be processed.","Enter the parser command."
"PKI","3","INVALID_INPUT","The input to the parser command is not correct","The arguments supplied to the parser command are not correct.","Reenter the command."
"PKI","3","POLLCACERT","Polling CA certificate .....","The CA certificate is being polled.","Check to see if the CA server or the LDAP server is on line."
"PKI","3","POLLRACERT","Polling RA certificate .....","The RA certificate is being polled.","Check to see if the CA server or the LDAP server is on line."
"PKI","3","POLLROUTERCERT","Polling Router certificate .....","The router certificate is being polled.","Check to see if the CA server or the LDAP server is on line."
"PKI","3","QUERYCACERT","Failed to query CA certificate.","A CA certificate from the CA server could not be queried.Explanation    Enter the parser command.Error Message    %PKI-3-QUERY_KEY: Querying key pair failed. Explanation    A public key or private key query attempt using the subject name has failed.Explanation    Resubmit the enrollment request. Check the subject name.Error Message    %PKI-3-SOCKETSELECT: Failed to select the socket. Explanation    The socket could not be selected.Explanation    Check for a TCP of socket debugging message to attempt to investigate the problem.Error Message    %PKI-3-SOCKETSEND: Failed to send out message to CA server. Explanation    A message could not be sent to the CA server. This failure is caused by a problem with the HTTP transaction.Explanation    Check the HTTP connection to the CA server.PKI-4Error Message    %PKI-4-CRL_LDAP_QUERY: The CRL could not be retrieved from the specified LDAP server Explanation    The certificate revocation list (CRL) is located on an LDAP server but the LDAP query failed.","Check that the LDAP server is reachable and online. Verify that the CRL is at the specified location."
"PKI","4","CS_PUBLISH_STORAGE","Publish certificate storage, [chars], is inaccessible.","The publish certificate storage location is inaccessible.","Make the storage location accessible or reconfigure the storage location."
"PKI","4","NOAUTOSAVE","Configuration was modified. Issue 'write memory' to save new certificate","Auto-enroll has obtained a new router key pair and certificate. However, the running configuration was previously modified.","Enter the write memory command to save the new certificate(s) and key(s)."
"PKI","4","NOCONFIGAUTOSAVE","Configuration was modified. Issue a 'write memory' to save new IOS PKI configuration","The PKI process has generated a new PKI configuration, but the running configuration was previously modified.","Enter a write memory command to save the new PKI configuration."
"PKI","4","NOSHADOWAUTOSAVE","Configuration was modified. Issue 'write memory' to save new IOS CA certificate","Cisco IOS CA Rollover has generated a shadow CA key pair and certificate. However, the running configuration was previously modified.","Enter the write memory command to save the new certificates and keys."
"PKI","6","AUTOENROLL_KEY_LOCKED","Auto-enroll failed - RSA keypair is locked","Auto-enroll could not generate a new RSA key pair because the existing RSA key pair is locked.","Auto-enroll will retry the enrollment request. Make sure that the existing RSA key pair is unlocked before the next retry."
"PKI","6","AUTOSAVE","Running configuration saved to NVRAM","Auto-enroll has obtained a new router key pair and certificate, and has done an automatic write to memory to save them.","This is an informational message only. No action is required."
"PKI","6","CERTFAIL","Certificate enrollment failed.","A fatal error was encountered during a certificate enrollment operation.","Contact the CA administrator."
"PKI","6","CERT_FATAL_ERR","[chars]","A fatal error was encountered during a certificate enrollment operation. The operation has been terminated.","Contact the CA administrator."
"PKI","6","CERTIFSRECV","Could not receive router's Certificate from file system.","The certificate for the router could not be received from the file system.","Verify the enrollment URL and that the router is able to read from the file system."
"PKI","6","CERTIFSSEND","Could not send Certificate enrollment request to file system.","The certificate enrollment request could not be sent to the file system.","Verify the enrollment URL and that the router is able to write to the file system."
"PKI","6","CERTPENDING","Enter manual authentication ...","The CA server is attempting to manually authenticate the router.","Follow the manual authentication procedure."
"PKI","6","CERTREJECT","Certificate enrollment request was rejected by Certificate Authority","A previous certificate enrollment request was received by the Certificate Authority. The CA has rejected the enrollment request.","Contact the Certificate Authority administrator."
"PKI","6","CERTRET","Certificate received from Certificate Authority","A previous certificate enrollment request was received by the Certificate Authority. The CA has issued the certificate and sent back a copy","No action is required."
"PKI","6","CONFIGAUTOSAVE","Running configuration saved to NVRAM","The PKI process has generated and saved to memory a new PKI configuration.","No action is required."
"PKI","6","CS_DELETE","Certificate Server is deleted.","The certificate server is deleted.","No action is required. This is an informational message."
"PKI","6","CS_DELETE_TP_KEY","Trustpoint and key deleted.","The trustpoint and key used by the certificate server are deleted.","No action is required. This is an informational message."
"PKI","6","CS_GRANT_AUTO","All enrollment requests will be automatically granted.","All enrollment requests will be automatically granted.","No action is required. This is an informational message."
"PKI","6","CS_GRANT_AUTO_CACERT","All rollover subordinate CA cert requests will be automatically granted.","All rollover subordinate CA certificate requests will be automatically granted.","No action is required. This is an informational message."
"PKI","6","CS_GRANT_AUTO_RA","Enrollment requests coming from known RAs will be automatically granted.","Enrollment requests coming from known RAs will be automatically granted.","No action is required. This is an informational message."
"PKI","6","CS_GRANT_AUTO_RACERT","All rollover RA cert requests will be automatically granted.","All rollover RA certificate requests will be automatically granted.","No action is required. This is an informational message."
"PKI","6","CS_REJECT_AUTO","All enrollment requests will be automatically rejected.","All enrollment requests will be automatically rejected.","No action is required. This is an informational message."
"PKI","6","PKCS12EXPORT_FAIL","PKCS #12 Export Failed.","An attempt to generate and export information conforming to the PKCS #12 format has failed.","This is an informational message only. No action is required."
"PKI","6","PKCS12EXPORT_SUCCESS","PKCS #12 Successfully Exported.","Information conforming to the PKCS #12 format has been generated and successfully exported.","This is an informational message only. No action is required."
"PKI","6","PKCS12IMPORT_FAIL","PKCS #12 Import Failed.","An attempt to import information conforming to the PKCS #12 format has failed.","This is an informational message only. No action is required."
"PKI","6","PKCS12IMPORT_SUCCESS","PKCS #12 Successfully Imported.","Information conforming to the PKCS #12 format has been successfully imported.","This is an informational message only. No action is required."
"PKI","6","SHADOWAUTOSAVE","Running configuration saved to NVRAM","Cisco IOS CA Rollover has generated a shadow CA key pair and certificate, and has executed an automatic write memory command to save them.","No action is required. This is an informational message."
"PLATFORM","1","CRASHED","[chars]","The system is attempting to display the crash message from the previous crash.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM","3","FATALCINNAMON","The FPGA controller has received a fatal interrupt, reg=[hex], mask=[hex], config=[hex] - [chars]","The FPGA controller has received a fatal interrupt. This may be a hardware or a software problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM","3","NO_HARDWARE_RESOURCES","Not enough hardware resources. Shutting down [chars]","There are too many VLANs and routed ports on the system.","Reduce the total number of VLANs and routed ports to be fewer than 1023. If you require this configuration and connectivity to be maintained across system reboots, save the configuration to NVRAM."
"PLATFORM","3","PW_REC_HRPC_BAD_LENGTH","Received incompatible length (=[dec]) in set-password-recovery HRPC message from box [dec].","The system has received an incompatible length parameter in a set-password-recovery HRPC message. This condition could be caused by a stack that is operating with incompatible software versions on different stack members.","Ensure that all stack members are running compatible software images. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM","3","PW_REC_HRPC_NOT_ON_MASTER","Set-password-recovery HRPC msg from box [dec] received on master.","The active stack has received a set-password-recovery HRPC message. These types of messages should only be received on standby systems.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM","3","PW_REC_HRPC_ONLY_ON_MASTER","Get-password-recovery HRPC msg from box [dec] received on slave.","A standby switch has received a get-password-recovery HRPC message. These types of messages should only be received by the active stack.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM","3","UNAVAILABLE","Get-password-recovery HRPC msg from box %d received on slave.","A slave switch has received a get-password-recovery HRPC message. These messages should only be received by the stack master.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM","3","UNAVAILABLE","Not enough hardware resources. Shutting down %s","Too many vlans and routed ports","Reduce the total number of vlans and routed portsto be less than 1023 . If this configurationand connectivity needs to be maintained acrossreboots, save the configuration to nvram"
"PLATFORM","3","UNAVAILABLE","Received incompatible length (=%d) in set-password-recovery HRPC message from box %d.","The system has received an incompatible length parameter in the set-password-recovery HRPC message. This could be caused by a stack operating with incompatible software versions on different stack members.","Make sure that all stack members are running compatible software images. If the problem persists, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information."
"PLATFORM","3","UNAVAILABLE","Set-password-recovery HRPC msg from box %d received on master.","The stack master has received a set-password-recovery HRPC message. These messages should only be received on slave boxes.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM","3","UNAVAILABLE","Slot %d %s update from version %02d.%02d to version %02d.%02d failed. System may not function properly.","FPGA update failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM","3","UNAVAILABLE","Slot %d linecard activation failed after FPGA update, error code = %d","Cannot activate linecard after FPGA update.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM","3","UNAVAILABLE","Slot %d linecard deactivation failed after FPGA update, error code = %d","Cannot deactivate linecard after FPGA update.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM","3","UNAVAILABLE","Slot %d linecard reset failed after FPGA update","Cannot reset linecard after FPGA update.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM","3","UNAVAILABLE","System FPGA update skipped for slot %d and up due to no user response.","System FPGA update skipped due to no user response","Please use 'upgrade fpga all' command under EXEC mode to manually start the whole-system FPGA version check and update process to ensure all the FPGAs in system are compatible."
"PLATFORM","3","UNAVAILABLE","System in minimal boot mode.","System comes up in minimal boot mode. This may due to incompatible FPGA or hardware version or the FPGA may not be properly loaded.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM","3","UNAVAILABLE","The FPGA controller has received a fatal interrupt, reg=%#x, mask=%#x, config=%#x - %s","The FPGA controller has received a fatal interrupt. This may be a hardware or a software problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM","4","FPGA_MISMATCH","FPGA image in slot [dec] (name = [chars], hardware version = [dec].[dec], current fpga version = [chars]) does not match the FPGA image in Cisco IOS software (version [dec].[dec]). Approximate time to update the FPGA image is [dec] minutes.","The version of the FPGA image on the specified card differs from the Cisco IOS software bundled FPGA image version.","Update the FPGA image by entering the upgrade fpga all command."
"PLATFORM","4","FPGAUPD_RELOAD_SKIP","After the FPGA update, the card in slot [dec] was not reloaded. The card should be reloaded for the new FPGA image to take effect.","The FPGA image on the specified card is updated. The new FPGA image will not be operational until the card is reloaded. The FPGA image upgrade will take effect after the next reload of the card. The card was not reloaded due to negative user response to the reload prompt.","Reload the card in the specified slot. If the card is a processor, reload the router."
"PLATFORM","4","FPGA_VER_INVALID","FPGA version information for the hardware in slot [dec] (fpga [dec]) has not been cached.","An attempt to read the current FPGA version from the cache was unsuccessful. Normally, the FPGA version on the RP and line cards is read from the flash memory device and is cached during the initialization of the card. However, the FPGA image version information for the card in the specified slot has not been cached. This problem is caused by a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM","4","UNAVAILABLE","I/O memory size mismatch. Configured size is %d, allocated size is %d","The allocated I/O memory size does not agree with the configured size","Reboot router to reallocate I/O memory"
"PLATFORM","4","UNAVAILABLE","Invalid CPU ID, assuming revision 1","The CPU ID could not be read from EEPROM. This is probably due to a hardware failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM","4","UNAVAILABLE","Old version NPE-175/225 with Rev = 0x%02x system controller. Contact upgrades-info@cisco.com for replacement","NPE board has been recalled due to an errata in the system controller chip.","Replace NPE-175/225 Board."
"PLATFORM","4","UNAVAILABLE","Potential loss of external error interrupt, intreg = 0x%x: %s","Cinnamon initialization masked external error interrupts.","Verify OIR still functions."
"PLATFORM","4","UNAVAILABLE","System cannot retrieve a compatible bundled FPGA image for slot %d %s (hardware version %d.%d), FPGA version check and update skipped","IOS does not have a compatible FPGA image bundled.","Please check the field alerts and other related documents to make sure this particular lineacard or NSE is supported. Upgrade the hardware or IOS if needed."
"PLATFORM","6","UNAVAILABLE","Slot %d %s successfully updated from version %02d.%02d to %02d.%02d.","FPGA update successfully performed.","LOG_STD_NO_ACTION"
"PLATFORM","6","UNAVAILABLE","Slot %d %s update skipped.","FPGA update skipped even though the current FPGA version is potentially incompatible.","Please check the field alerts and other related documents and update the FPGA if needed."
"PLATFORM_CAPABILITY","4","UNAVAILABLE","Fatal Initialization Error - %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_CAPABILITY","4","UNAVAILABLE","Fatal Initialization Error - %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_CAT2950","3","UNAVAILABLE","Asic driver initialization has failed","One of the ASIC initialization steps has failed. This could be a failure in the PCI configuration setup, I2C initialization, Build-in self test on the internal chip memories, or other miscellaneous initialization steps, due to a hardware defect.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_CAT2950","3","UNAVAILABLE","C2950 BIST failed for memory %s count %d","During the Power-On Self Test, the Built-In memory test on the internal chip memories has failed. This could be due to an ASIC defect.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_CAT2950","3","UNAVAILABLE","GBP currently FULL or UNAVAILABLE.","During the switch driver initialization, an error has been detected in the external packet memory. This could be a defect in the ASIC or in the external SDRAM.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_CAT2950","3","UNAVAILABLE","Invalid copy %d for table %s","This message means that there was an attempt to read or write an invalid copy of the switch internal memory. This is a recoverable error but should not happen.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_CAT2950","3","UNAVAILABLE","Invalid index %d for table %s","This message means that there was an attempt to access an invalid index of the switch internal memory. This is a recoverable error but should not happen.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_CAT2950","3","UNAVAILABLE","PCI address space test failed,Wrote 0x%x, read 0x%x, re-read 0x%x","During the Power-On Self Test, it is found that the PCI address space for the ASIC has not been mapped correctly. This could be a system PCI-bus-related issue.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_CAT2950","3","UNAVAILABLE","Read memory failed for memory %s at index %d","An attempt to read a valid location in the internal chip memory was failed. This could be due to a hardware defect.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_CAT2950","3","UNAVAILABLE","Register read failed for register %s in %s","An attempt to read a valid location in the internal chip register failed. This could be due to a hardware defect.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_CAT2950","3","UNAVAILABLE","Register write failed for register %s in %s","An attempt to write to a location in the internal chip register failed. This might be cause by writing to a invalid register location, or a defect in the hardware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_CAT2950","3","UNAVAILABLE","S-channel operation read register failure at addr %x","This message means that there was a failure to read a ASIC register, which might be caused by an invalid register address or an internal bus failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_CAT2950","3","UNAVAILABLE","S-channel operation timeout for opcode %s","This message means that there was a failure to read or write to an ASIC register or a memory location because of an ASIC internal bus failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_CAT2950","3","UNAVAILABLE","The PCI address space initialization failed","During the switch driver initialization, the PCI address space for the ASIC could not be initialized. This could be a system PCI-bus-related issue.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_CAT2950","3","UNAVAILABLE","The board information could not be read correctly,initialization failed","During switch driver initialization, there was a failure to read the system board information. This could be a hardware problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_CAT2950","3","UNAVAILABLE","The number of asics expected were %d, PCI bus scan found %d","During the switch driver initialization, incorrect number of ASICs were found on the PCI bus or no ASICs with a correct PCI value was found. This could be caused by a system PCI bus defect, or incompatible software version running on the switch.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_CAT2950","3","UNAVAILABLE","The switch memory resources could not be allocated for %s, initialization failed","During the switch driver initialization, driver-related memory resources could not be allocated. This could be a hardware defect.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_CAT2950","3","UNAVAILABLE","Unable to initialize the external packet memory","During the switch driver initialization, there was an error in the external packet memory initialization. This could be a defect in the ASIC or in the external SDRAM.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_CAT2950","3","UNAVAILABLE","Unable to read PHY register at addr %x for phy id %x","This message means that there was a failure to read from or write to a PHY register on the switch. This could be caused by a defect in the MII/GMII interface of the switch.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_CAT2950","3","UNAVAILABLE","Write memory failed for memory %s at index %d","An attempt to write to a location in the internal chip memory was failed. This might be cause by writing to a invalid memory location, or a defect in the hardware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_CAT3550","1","UNAVAILABLE","%s","The system is attempting to display the crash message from the previous crash.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_CATALYST2950","1","UNAVAILABLE","%s","The system is attempting to display the crash message from the previous crash.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_FBM","4","UNAVAILABLE","Fallback bridging on bridge-group %d is experiencing a resource crunch. One or more bridge-groups may not be functional. It will recover automatically when system recovers from resource crunch. Delete the bridge-group to immediately recover.","Fallback bridging could not be configured properly. Most likely cause is TCAM full condition on atleast one stack member","Stop all traffic, issue clear mac-address-table dynamic command and restore switch's normal operation"
"PLATFORM_FBM","4","UNAVAILABLE","Fallback bridging recovered from resource crunch.","Fallback bridging has recovered from earlier resource crunch","Nothing needs to be done."
"PLATFORM_IPC","3","UNAVAILABLE","%s","A failure on the master","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_IPC","3","UNAVAILABLE","%s","A failure on the slave","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_IPC","3","UNAVAILABLE","%s","IPC failure","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_PBR","2","UNAVAILABLE","Cannot create PBR data structures for route-map %s","The PBR manager could not allocate the data structures needed to describe a route-map being used for policy routing. Probably caused by lack of available memory.","Use a less complicated configuration that requires less memory."
"PLATFORM_PBR","3","UNAVAILABLE","%s ACL merge error %d on route-map %s","The PBR manager could not complete the merge of the configured route-map into a form suitable for loading into the hardware. The most likely cause is specifying an ACL that is too large or too complex for the system to handle.","Try specifying a smaller and less complicated configuration."
"PLATFORM_PBR","3","UNAVAILABLE","Cannot allocate label for route-map %s","The PBR manager could not allocate a label for this route-map. This means that the hardware cannot be programmed to implement policy routing. There is a limit of 247 labels for policy routing","Use a less complicated configuration that allows label sharing. Use the same route-maps on multiple interfaces, if possible"
"PLATFORM_PBR","3","UNAVAILABLE","Policy route-map %s not installed in hardware","The PBR manager was unable to install the complete route-map in the hardware, so this will have to be applied in software. This requires the packets to be forwarded by the CPU.","Reconfigure the route-map to use a simpler configuration. Use the same route-map on multiple interfaces, if possible"
"PLATFORM_PBR","3","UNAVAILABLE","Route-map %s not supported for Policy-Based Routing","The route-map attached to an interface for policy routing contains an action that is not supported on this platform. This is a hardware limitation.","Reconfigure the route-map. Use only 'permit' entries and 'set ip next-hop' action in the route-map."
"PLATFORM_PBR","4","UNAVAILABLE","%s requires sdm template routing","In order to support this feature, sdm template routing needs to enabled.","Modify the Switch Database Management (SDM) template to enable the switch to support the routing template. Use the sdm prefer routing configuration command, and then reload the switch by using the reload privileged EXEC command."
"PLATFORM_PBR","4","UNAVAILABLE","Route-map %s installed in hardware upon retry","The PBR manager was able to fit the complete configuration into the hardware. One or more route-maps had previously not been loaded because of lack of space.","LOG_STD_NO_ACTION"
"PLATFORM_PBR","4","UNAVAILABLE","Set action in sequence %d of route-map %s supported by forwarding to CPU","The route-map attached to an interface for policy routing contains an action that is not supported in hardware since it contains a 'set interface', 'set ip default next-hop', 'set default interface' or or 'set ip df' actions. This requires the packets to be forwarded by the CPU.","Reconfigure the route-map. Use only 'set ip next-hop' in the route-map, if possible."
"PLATFORM_PM","3","UNAVAILABLE","Unit number %d of interface %s is more than max allowed value of %d","System supports limited number of interfaces for each interface type. User created more than supported interfaces","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_PM","3","UNAVAILABLE","internal vlan of interface %s is not active for vlan-id %d","internal vlan_data is not active for the given vlan-id","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_PM","3","UNAVAILABLE","internal vlan-id %d allocated for interface %s is still in use","internal vlan-id allocated for an interface is still in use","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_RPC","0","UNAVAILABLE","%s","System is unable to alloc memory for RPC","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_RPC","3","UNAVAILABLE","Bad Class in RPC message: %u","class table missing entry for message class","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_RPC","3","UNAVAILABLE","Failed to send RPC message in class %d, req %d, %s","Local resource error or too many outgoing messages queued up for msg class","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_RPC","3","UNAVAILABLE","RPC Msg Dropped by throttle mechanism: type %u, class %u, max_msg %u, total throttled %u","too many outgoing messages queued up for msg class","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_RPC","3","UNAVAILABLE","System is consistently unable to send RPC message: %s, paks_outstanding: %u","Persistent Low-level transport failure in sending RPC message","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_RPC","3","UNAVAILABLE","System is unable to send RPC message: %s, paks_outstanding: %u","Low-level transport failure in sending RPC message","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_RPC","3","UNAVAILABLE","Unexpected response or failure, class %d, req %d, switch %d, error %d, %s","Received a response which is unexpected","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_SPAN","3","UNAVAILABLE","Decreased egress SPAN rate.","When SPAN is enabled with multicast routing orbridge groups, egress span rates will fall down.Not all packets going out may be monitored","Contact Cisco TAC."
"PLATFORM_UCAST","3","UNAVAILABLE","%s","An internal platform unicast routing error occured","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_UCAST","3","UNAVAILABLE","%s","Platform unicast routing adjacency module encountered an error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_UCAST","3","UNAVAILABLE","%s","Platform unicast routing arp module encountered an error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_UCAST","3","UNAVAILABLE","%s","Platform unicast routing backwalk loadbalance module encountered an error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_UCAST","3","UNAVAILABLE","%s","Platform unicast routing cef module encountered an error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_UCAST","3","UNAVAILABLE","%s","Platform unicast routing hsrp module encountered an error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_UCAST","3","UNAVAILABLE","%s","Platform unicast routing interface related error occured","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_UCAST","3","UNAVAILABLE","%s","Platform unicast routing loadbalance module encountered an error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_UCAST","3","UNAVAILABLE","%s","Platform unicast routing module received a NULL software object handle","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_UCAST","3","UNAVAILABLE","%s","Platform unicast routing rpc module encountered an error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_UCAST","3","UNAVAILABLE","%s","Platform's dynamic address tracking mechanism encountered an error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_VLAN","3","UNAVAILABLE","Failed to lock vlan-id %d, associated mapped vlan id value %d","VLAN lock operation failed. Most likely cause might be either the vlan already active in the system or the vlan-id is not active","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_VLAN","3","UNAVAILABLE","Failed to unlock vlan-id %d, associated mapped vlan id value %d","failed to unlock vlan-id. Most likely cause is the vlan is already freed","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PLATFORM_VLAN","3","UNAVAILABLE","Mapped Vlan ID value %d associated with vlan-id %d is invalid","Each active vlan in the system is associated with a mapped-vlan-id and the mvid is not correct/valid","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM","1","INCONSISTENT_PORT_STATE","Inconsistent HW/SW port state for [chars]. Please shut/no shut the interface","The hardware and software port state has become inconsistent. [chars] is the interface.","shutdown/no shutdown on the interface specified in the message."
"PM","2","UNAVAILABLE","Failed to add VLAN %d - %s.","Failed in adding VLAN to VTP. The reason is stated in the string.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM","2","UNAVAILABLE","Not enough memory available for %s","The Port Manager subsystem could not obtain the memory it needed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM","2","UNAVAILABLE","Switch process available memory is less than %d bytes","Switch Processor available memory dropped to a low level. Possibly too many Layer 2 VLANs are configured in the system.","Removed features from the system to reduce memory usage."
"PM","3","ERR_INCOMP_PORT","<mod/port> is set to inactive because <mod/port> is a trunk port","An isolated or community VLAN port or private host port cannot be configured on the same COIL application-specific integrated circuit (ASIC) when another port is either a trunk, a SPAN destination, or a promiscuous PVLAN port, or if a port is configured as dynamic desirable mode (the default mode on some switches).","To reactivate the ports, remove the isolated or community VLAN port configuration and enter the shutdown command followed by the no shutdown command. Configure the incompatible port on a different ASIC on the module or on a different module. Refer to the module documentation to determine which ports share an ASIC. If ports are configured (manually or by default) as dynamic desirable mode, configure the ports as access mode using the switchport mode access command."
"PM","4","PORT_BOUNCED","Port %s was bounced by %s.","The Port Manager needed to perform a reactivation of a port in the link down state during a switchover. A port is only reactivated when the port data structures lack consistency between the active and standby supervisors. Active ports in the link down state were returned to the link up state by the reactivation event.","No action is required."
"PM","4","UNAVAILABLE","%s error detected on %s, putting %s in err-disable state","This is a defensive measure that will put the interface in err-disable state when it detects a mis-configuration or mis-behavior . A recovery will be attempted after the configured retry time (default 5 minutes).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM","4","UNAVAILABLE","%s failed to come up. No internal VLAN available","Port Manager failed to allocate internal VLAN and thus the interface cannot come up.","Remove extended range VLAN to free up resouces."
"PM","4","UNAVAILABLE","%s was detected","An invalid request was detected by the Port Manager.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM","4","UNAVAILABLE","Attempting to recover from %s err-disable state on %s","This is an attempt to bring the interface back after taking it down to err-disable state","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM","4","UNAVAILABLE","Dynamic access VLAN %d same as voice vlan on %s.","Access VLAN on VMPS server is set to same VLAN as voice VLAN on the port.","Access VLAN assignment on VMPS server should be different from voice VLAN."
"PM","4","UNAVAILABLE","Failed to allocate internal VLAN in Port Manager","Port Manager failed to find any available internal VLAN","Delete some extened range VLANs created by users or remove some features that require internal VLAN allocation, e.g. routed port"
"PM","4","UNAVAILABLE","Failed to set VLAN %d to a %s VLAN","Platform failed to set private vlan type.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM","4","UNAVAILABLE","Internal VLAN allocation failed for tunnel interface %s.","Internal VLAN allocation for the tunnel interface has failed","Delete some extended range VLANs created by users or remove some features that require internal VLAN allocation, e.g. routed port"
"PM","4","UNAVAILABLE","Invalid Host access entry event (%d) is received","Host access table is entry event is not any of add/delete/update event","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM","4","UNAVAILABLE","Invalid Host access entry type (%d) is received","Host access entry should be one of configured/dynamic type","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM","4","UNAVAILABLE","Invalid Host access value (%d) is received","Host access table is being accesses with an invalalid host access value","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM","4","UNAVAILABLE","MPLS MTU size %d is not supported by one or more ports in channel %s.","The MPLS MTU size configured on the ethernet channel is larger than the maximum MTU size that can be supported by one or more ports in this channel. As a result, large packets can be dropped.","Reduce the MPLS MTU size, or remove these ports from the channel before increasing the MPLS MTU size."
"PM","4","UNAVAILABLE","MPLS MTU size %d is not supported by port %s.","The MPLS MTU size configured on the port is larger than the maximum MTU size that can be supported by this port. As a result, large packets can be dropped.","Reduce the MPLS MTU size."
"PM","4","UNAVAILABLE","No PM subblock found for %s","Failed to find PM subblock for this interface.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM","4","UNAVAILABLE","No PM subblock found for interface %s","This syslog, along with T/B, is logged for all type of interfaces where PM subblock is absent.The interface types include WAN, loopback and tunnel, which do not have associated PM subblock as per the design.This message helps the PM group to identify the offending application.This message indicates that PM module encounters unusual conditions for diagnose purpose.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM","4","UNAVAILABLE","Port %s was bounced by %s.","The Port Manager needed to perform a reactivation of a port in the link down state during a switchover. A port is only reactivated when the port data structures lack consistency between the active and standby supervisors. Active ports in the link down state were returned to the link up state by the reactivation event.","LOG_STD_NO_ACTION"
"PM","4","UNAVAILABLE","The number of vlan-port instances on %s exceeded the recommended limit of %d","The total number of individual VLAN ports, counted over the module or switch specified in the error message, has exceeded the module or switch limit specified in the error message. VLANs can be counted more than once; if VLAN 1 is carried on 10 interfaces, it will count as 10 VLAN ports. For some platforms, e.g. Catalyst 6000, bundling is also ignored for purposes of this count; if 8 interfaces on the same module are in one bundle, and the port channel is carrying VLAN 1, it will count as 8 VLAN ports.","Reduce the number of trunks and VLANs configured in the module or switch specified in the error message. Keep the virtual port, VLAN port, count below the recommended limit specified in the configuration documentation. Enter the show interface trunk command to see the total number of trunks and VLANs."
"PM","4","UNAVAILABLE","VLAN %d currently in use by %s","Port Manager failed to allocate the VLAN for external use as the VLAN is currently occupied by another feature","Reconfigure the feature, e.g. routed port, to use another interal VLAN; Or request another available VLANs."
"PM","4","UNAVAILABLE","VLAN %d not available in Port Manager","Port Manager failed to allocate the requested VLAN. The VLAN is mostly likely used as internal VLAN by other features","Try a different VLAN on the device."
"PM","4","UNAVAILABLE","Vlan %d must be added to L2 database in order to be used, do  from config mode.","When an SVI is created, corresponding L2 VLAN is not automatically created in the L2 database. Hence give an error message if the vlan is not in the L2 database.","Create an L2 VLAN before SVI is created."
"PM","4","UNAVAILABLE","an invalid %s request by the '%s' application was detected","An invalid request was detected by the Port Manager.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM","4","UNAVAILABLE","an invalid application id (%d) was detected","An invalid request was detected by the Port Manager.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM","4","UNAVAILABLE","an invalid card cookie was detected","An invalid request was detected by the Port Manager.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM","4","UNAVAILABLE","an invalid card slot (%d) was detected","An invalid request was detected by the Port Manager.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM","4","UNAVAILABLE","an invalid port cookie was detected","An invalid request was detected by the Port Manager.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM","4","UNAVAILABLE","an invalid port number (%d) was detected","An invalid request was detected by the Port Manager.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM","4","UNAVAILABLE","an invalid vlan cookie was detected","An invalid request was detected by the Port Manager.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM","4","UNAVAILABLE","an invalid vlan id (%d) was detected","An invalid request was detected by the Port Manager.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM","4","UNAVAILABLE","application '%s' exceeded registration limit","An invalid request was detected by the Port Manager.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM","4","UNAVAILABLE","putting %s in inactive state because %s","The Port Manager has been blocked from creating a virtual port for the switch port and VLAN, causing the port to be in an inactive state. The reason for this condition is specified in the error message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM","6","ACTIVE","Interface [chars] is now active because [chars]","The port manager has detected an interface that was down as up for the VLAN, causing the port to be in the active state.","No action is required."
"PMOD","3","UNAVAILABLE","%s","Error Messages","try debug command"
"PMB","4","CANTPWROFF","Attempts to power down slot [dec] failed, card will be disabled.","The system could not power down the module in slot [dec], possibly due to a hardware failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM_ISSU","3","BUFFER","Port Manager ISSU client failed to get buffer for message, error %d","The port manager ISSU client was unable to get buffer space for building a negotiation message. As a result, the client cannot send the negotiation message to the standby unit and the standby unit cannot be brought up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"PM_ISSU","3","CAPABILITY","Port Manager ISSU client %s","The port manager ISSU client detected an error during capability negotiation. As a result, there is a mismatch in the client capability between the active and standby unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"PM_ISSU","3","INIT","Port Manager ISSU client initialization failed at %s, error %s","The port manager ISSU client could not be initialized. This condition will cause a catastrophic failure when an ISSU upgrade or downgrade is performed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM_ISSU","3","MSG_NOT_OK","Port Manager ISSU client message %d is not compatible","The port manager ISSU client received an incompatible message from the peer unit. The message cannot be processed by this unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"PM_ISSU","3","MSG_SIZE","Port Manager ISSU client failed to get the message size for message %d","The port manager ISSU client was unable to calculate the message size for the message specified. The PM ISSU client will be unable to send the message to the standby unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"PM_ISSU","3","POLICY","Port Manager ISSU client message type %d is %s","The port manager ISSU client received a message type that it does not support. A policy is applied to make the session compatible.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show issu session commands and your pertinent troubleshooting logs."
"PM_ISSU","3","SEND_FAILED","Port Manager ISSU client failed to send a negotiation message, error %d","The port manager ISSU client could not send a session negotiation message to the peer. As a result, the standby unit cannot be brought up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"PM_ISSU","3","SESSION","Port Manager ISSU client %s","The port manager ISSU client detected an error during a session negotiation with the peer unit. As a result, the standby unit cannot be brought up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"PM_ISSU","3","SESSION_UNREGISTRY","Port Manager ISSU client failed to unregister session information. Error: %d (%s)","The port manager ISSU client was unable to unregister session information.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"PM_ISSU","3","TRANSFORM","Port Manager ISSU client %s transform failed, error %s","The port manager ISSU client could not transform the message. If the transmit transformation failed, the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, the checkpoint message cannot be applied on the standby unit. In either case, the port manager state will not be identical with the active unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"PM_MODEM_HIST","7","UNAVAILABLE","%s: %s %*s State: %s","This is a tracing message indicating a state event reported by the specified modem.","LOG_STD_DBG_ACTION"
"PM_MODEM_HIST","7","UNAVAILABLE","%s: %s %s","This is a tracing message indicating a dynamic event reported by the specified modem.","LOG_STD_DBG_ACTION"
"PM_MODEM_HIST","7","UNAVAILABLE","%s: %s %s","This is a tracing message indicating a link rate event reported by the specified modem.","LOG_STD_DBG_ACTION"
"PM_MODEM_HIST","7","UNAVAILABLE","%s: %s %s","This is a tracing message indicating a static event reported by the specified modem.","LOG_STD_DBG_ACTION"
"PM_MODEM_MAINT","1","UNAVAILABLE","Initialization failed.","Modem maintenance facility initialization failed.","Disable Autotest, Poweron test and avoid manual back-2-back test. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM_MODEM_MAINT","1","UNAVAILABLE","Invalid modem management %s event 0x%02x for modem(%s)","The modem management facility received an unrecognize event.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM_MODEM_MAINT","1","UNAVAILABLE","Modem (%s) failed %s","A software or hardware problem has been detected on a modem. The specific modem and reason are listed in the message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM_MODEM_MAINT","4","UNAVAILABLE","Modems (%s) and (%s) back-to-back test: aborted","This is a tracing message indicating a back-to-back test failed between the two specified MICA modems.","Perform more back to back tests by pairing the failed modems with other modems to determine which modem is bad. Check the failed modems again after performing a power cycle. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM_MODEM_MAINT","4","UNAVAILABLE","Modems (%s) and (%s) failed back-to-back test: %s","The two modems reported in the message failed a back-to-back test. At least one of them has failed.","Perform more back to back tests by pairing the failed modems with other modems to determine which modem is bad. Check the failed modems again after performing a power cycle. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM_MODEM_MAINT","5","UNAVAILABLE","Auto Back-to-Back test initiated by %s","This is a tracing message indicating an automatic back-to-back test was initiated by the specified MICA modem.","LOG_STD_DBG_ACTION"
"PM_MODEM_MAINT","5","UNAVAILABLE","Modem (%s) passed the test","Tests on the specified modem were successful.","LOG_STD_NO_ACTION"
"PM_MODEM_MAINT","5","UNAVAILABLE","Modems (%s) and (%s) completed back-to-back test: success/packets = %d/%d","The reported modems have passed the back to back test without any errors.","LOG_STD_NO_ACTION"
"PM_MODEM_MAINT","5","UNAVAILABLE","Modems (%s) and (%s) connected in back-to-back test: %s","A back to back test connection has been made between the selected modems. The test is still in progress.","LOG_STD_NO_ACTION"
"PM_PVLAN_ISSU","3","BUFFER","Private Vlan ISSU client failed to get buffer for message, error %d","The private VLAN ISSU client was unable to get a buffer for building a negotiation message. As a result, it cannot send the negotiation message to the standby unit and the standby unit cannot be brought up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"PM_PVLAN_ISSU","3","CAPABILITY","Private Vlan ISSU client %s","The private VLAN ISSU client detected an error during capability negotiation. As a result, there is a mismatch in the client capability between the active and standby unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"PM_PVLAN_ISSU","3","INIT","pm_pvlan Client Name ISSU client initialization failed at %s, error %s","The private VLAN ISSU client could not be initialized. This condition will cause a catastrophic failure when an ISSU upgrade or downgrade is performed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM_PVLAN_ISSU","3","MSG_NOT_OK","Private Vlan ISSU client message %d is not compatible","The private VLAN ISSU client received an incompatible message from the peer unit. The message cannot be processed by this unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"PM_PVLAN_ISSU","3","MSG_SIZE","Private Vlan ISSU client failed to get the message size for message %d","The private VLAN ISSU client was unable to calculate the message size for the message specified. The client will be unable to send the message to the standby unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"PM_PVLAN_ISSU","3","POLICY","Private Vlan ISSU client message type %d is %s","The private VLAN ISSU client received a message type that it does not support. A policy is applied to make the session compatible.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show issu session commands and your pertinent troubleshooting logs."
"PM_PVLAN_ISSU","3","SEND_FAILED","Private Vlan ISSU client failed to send a negotiation message, error %d","The private VLAN ISSU client could not send a session negotiation message to the peer. As a result, the standby unit cannot be brought up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"PM_PVLAN_ISSU","3","SESSION","Private Vlan ISSU client %s","The private VLAN ISSU client detected an error during a session negotiation with the peer unit. As a result, the standby unit cannot be brought up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"PM_PVLAN_ISSU","3","TRANSFORM","Private Vlan ISSU client %s transform failed, error %s","The private VLAN ISSU client could not transform the message. If the transmit transformation failed, the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, the checkpoint message cannot be applied on the standby unit. In either case, the private VLAN ISSU state will not be identical with the active unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"PM_SCP","1","LCP_FW_ERR_POWERDOWN","Module [dec] will be powered down due to firmware error: [chars]","A nonrecoverable error was detected by the switching module firmware and the switching module will be powered down to keep the system functioning. [dec] is the module number and [chars] explains that the system will be powered down.","No action is required."
"PM_SCP","2","LCP_FW_ERR_INFORM","Module [dec] is experiencing the following error: [chars]","The linecard is reporting an error condition, where [dec] is the module number, and [chars] is the error. This condition is usually caused by an improperly seated linecard or a hardware failure. If the error message is seen on all of the linecards, the cause is an improperly seated module.","Reseat and reset the linecard or the module. If the error message persists after the module is reset, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM_SCP","2","SPURIOUS_INTERRUPT","Module [dec] detects [dec] spurious interrupts from asic [chars].","An error condition was detected by the active supervisor engine firmware. If error-detection crash-action is configured, the active supervisor engine will switch over to the standby supervisor engine in a redundant setup.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM_SCP","2","RESET","Module [dec] is resetting - Due to Packet Buffer Error.","An error condition was detected by the line card firmware and the supervisor engine has initiated a reset procedure for the line card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM_SCP","2","SHUTDOWN","Module [dec] is shutting down - Due to Packet Buffer Error.","An error condition was detected by the line card firmware and the supervisor engine has initiated a shutdown procedure for the line card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM_SCP","2","STDBY_NOT_SWTCH_OVER","Standby is not ready for switchover for Packet Buffer Error. Active-Sup (Module [dec]) is going down...","An error condition was detected by the active supervisor engine firmware and the standby supervisor engine is not ready for switchover, so the active supervisor engine is going down.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM_SCP","2","STDBY_RELOAD","Standby (Module [dec]) is reloading due to Packet Buffer Error...","An error condition was detected by the supervisor engine firmware and the standby supervisor engine is reloading now.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM_SCP","2","STDBY_SWTCH_OVER","Supervisor (Module [dec]) is preparing for switch-over - Due to Packet Buffer Error.","An error condition was detected by the supervisor engine firmware and has initiated the switchover 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM_SCP","2","TRANSCEIVER_BAD_HW","Module [dec] will be power disabled for safety reasons because a defective transceiver is inserted at [chars].","An inappropriate transceiver is inserted at the specified interface. This transceiver should not be used in this system.","Remove the specified transceiver and enable power to the module. If this transceiver was purchased from Cisco, contact Cisco TAC to get the transceiver replaced."
"PM_SCP","2","TRANSCEIVER_INCOMPATIBLE","Transceiver inserted in [chars] port [dec]/[dec] is not compatible with its interface (transceiver speed is [chars], interface speed is [chars])","An incompatible transceiver was inserted in the specified module. This transceiver should not be used with this module.","Replace the specified transceiver with another transceiver that is compatible with this module."
"PM_SCP","3","LCP_FW_ABLC","Late collision message from module [dec], port:0[dec]","The line card firmware has detected abnormal collisions in port traffic.","This is usually a temporary condition. Check for any mismatch in the Duplex or Speed setting with the remote device. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM_SCP","3","TRANSCEIVER_BAD_EEPROM","Integrity check on transceiver in [chars] port [dec]/[dec] failed: bad key","The transceiver has an incorrectly programmed EEPROM.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM_SCP","3","TRANSCEIVER_DUPLICATE","Transceiver in [chars] port [dec]/[dec] and in [chars] port [dec]/[dec] have duplicate serial numbers","The transceiver was identified as a Cisco transceiver, but its vendor ID and serial number match that of another transceiver on the system.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM_SCP","2","TRANSCEIVER_INCOMPATIBLE","Transceiver inserted in [chars] port [dec]/[dec] is not compatible with its interface (transceiver speed is [chars], interface speed is [chars])","An incompatible transceiver is inserted in the specified module. This transceiver should not be used with this module.","Replace the specified transceiver with another transceiver that is compatible with this module."
"PM_SCP","4","FPOE_INFO","An unsupported distributed fabric card has been detected","Fabric-capable modules are not supported in this system.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PM_SCP","4","LCP_FW_ABLC","Late collision message from module [dec], port:0[dec]","The line card firmware has detected abnormal collisions in port traffic. This message is typically an indication of a speed or duplex mismatch, possibly caused by a misconfiguration.","This is usually a temporary situation. Check the speed and duplex for the port and make sure that it is correct. For correct operation, both sides of a link should be auto-negotiated or both sides should be manually configured for speed and duplex. Do not configure auto-negotiation on one side and manual setting on the other, because the auto-negotiating side might lock at the wrong duplex setting."
"PM_SCP","4","TRANSCEIVER_UNSUPP_MODULE","Interface [chars] does not support receive-only transceivers","A receive-only transceiver has been inserted into a module that does not support it.","Use the receive-only transceiver with a supported module. Refer to the documentation for modules that support receive-only transceivers."
"PM_SCP","4","UNSUPPORTED","Interface [chars] does not support receive-only transceivers","A receive-only transceiver has been inserted into a slot that does not support it.","Use the receive-only transceiver with a supported module."
"PM_SCP","6","LCP_FW_ERR_INFORM","Module [dec] is experiencing the following error: [chars]","The module is reporting an error condition, where [dec] is the module number, and [chars] is the error. This condition is usually caused by an improperly seated linecard or a hardware failure. If the error message is seen on all of the linecards, the cause is an improperly seated module.","Reseat and reset the linecard or the module. If the error message persists after the module is reset, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PNNI","2","UNAVAILABLE","%s Error Message    %PNNI-2-UNAVAILABLE: Empty Internal Number Stack: %s","An internal software error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PNNI","2","UNAVAILABLE","Tent List Overflow in %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PNNI","3","UNAVAILABLE","%s%s %x","An internal software error occurred. The message contains more information that can be used to identify the problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PNNI","3","UNAVAILABLE","Bad address of %s %#x, please collect show atm pnni trace error","An internal software error occurred.","Use show atm pnni trace error to collect more information. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PNNI","4","UNAVAILABLE","%s %s for node %d %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PNNI","4","UNAVAILABLE","Address derived from the switch's prefix by soft PVC manager %s clashes with existing address in prefix table","An PVC port address assignment has collided with an existing address. An address that would have been assigned by this switch has already been assigned by another.","If possible, assign a new MAC address to the peer system that caused the assignment collision."
"PNNI","4","UNAVAILABLE","Bad Request from Signaling %x","A source routing request by another network host was corrupted.","Check the originating system for a cause of the problem."
"PNNI","4","UNAVAILABLE","Configuration Error: %s","This message indicates a configuration error in the PNNI subsystem. The message will display more specific information about the cause of problem.","Change the confguration to correct the error."
"PNNI","4","UNAVAILABLE","Error: %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PNNI","4","UNAVAILABLE","Invalid %s pkt: %s %d %d","An invalid packet was received from a network peer.","Check the originating device for a cause of the corrupted packets."
"PNNI","6","UNAVAILABLE","%s","This is an informational message only.","Informational messages can be disabled by changing logging level."
"PNNI","7","UNAVAILABLE","%s","This is an informational message only. It is used by Cisco for testing.","Informational messages can be disabled by changing logging level."
"POLARIS","4","ERR_INTRPT","Interrupt [chars] occurring in Polaris Layer 3 ASIC","An error occurred in the Layer 3 forwarding ASIC. The error description is shown by [chars].","These errors are transient conditions caused by traffic passing through the ASIC, and may appear occasionally under normal conditions. If this message recurs, enter the show earl status command on the consoles of the switch supervisor engine and any DFC-enabled modules. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"POLICY_API","4","POLICYDYNCLR","Dynamic policy on intf:[chars] cleared. Static policy in use.","A dynamic policy was attempting to override the static policy. The dynamic policy has been cleared, the static policy is now in effect.","No action is required."
"POLICY_API","4","POLICYOVERIDE","Dynamic policy overriding static on intf:[chars]","Both a static policy and a dynamic policy are configured on the interface. The dynamic policy will override the static policy.","If preferred, remove the static policy configuration."
"POLICY_API","4","POLICYSTATICCLR","Static policy on intf:[chars] cleared. Dynamic policy in use.","A dynamic policy has overridden the static policy. The static policy has been cleared.","No action is required."
"POLICY_MANAGER","2","INIT_FAILURE","Init failure: [chars]","A problem occurred during the initialization of the policy manager during system initialization.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"POLICY_MANAGER","2","NO_FREE_EVENT_BUFFERS","Event pool depleted: [chars]","The event pool has been depleted. There are no free buffers to process the event.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"POLICY_MANAGER","3","INVALID_ACTION","Invalid action","An invalid action was performed by the policy manager.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"POLICY_MANAGER","3","INVALID_PARAMETERS","A call to Policy Manager is made with invalid parameters","A call to the policy manager was made with one or more invalid parameters.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"POLICY_MANAGER","3","INVALID_SEVERITY","Invalid event severity [hex]","The event that was received by the policy manager contained an invalid severity and was not processed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"POLICY_MANAGER","3","NO_FREE_POLICY_IDS","No more Policy IDs available","There are no more policy IDs that can be allocated. Policy manager policies can no longer be created.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"POLICY_MANAGER","3","NULL_ACTION_ROUTINE","NULL action routine invoked","The policy manager attempted to invoke an action that was of a null value.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"POLICY_MANAGER","3","PRE_INIT_CALL","Policy Manager routine called prior to initialization","The policy manager component was called prior to its initialization. This action could result in vital information being lost.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PORT_SECURITY","2","INELIGIBLE","Port security configuration on [chars] is being made inactive since the port is now not eligible for port security as [chars].","A port had port security configuration on it, but the port now has a configuration not supported with port security. Because the port is now not eligible for port security, the port security configuration on it is being made inactive.","Check the port's configuration and remove the offending configuration that is not compatible with port security."
"PORT_SECURITY","2","PSECURE_VIOLATION","Security violation occurred, caused by MAC address [enet] on port [chars].","An unauthorized device attempted to connect on a secure port. The MAC address of the unauthorized device and the secure port are specified in the message.","Determine the device that attempted to connect on the secure port. Notify your network system administrator of this condition."
"PORT_SECURITY","6","ADDR_EXCEEDS_LIMIT","Address <[int]:[enet]> can not be allowed on port [chars] because of max address limits. It has been removed","A routed port has changed to a switched port. The addresses stored in the previous switched-port configuration are now causing the total secure address count to exceed the allowed limit and they have been deleted","This is an informational message only. No action is required."
"PORT_SECURITY","6","ADDR_REMOVED","Address <[int]:[enet]> exists on port [chars]. It has been removed from port [chars].","A routed port has changed to a switched port. An address stored in the previous switched-port configuration is now in conflict and has been deleted.","This is an informational message only. No action is required."
"PORT_SECURITY","6","INVALID_SESSION","Invalid Port-Security ISSU Session ID","The ISSU session ID is not valid because it has not been negotiated.","No action is required."
"PORT_SECURITY","6","VLAN_REMOVED","VLAN(S) [chars] is/are no longer allowed on port [chars]. Their port security configuration has been removed.","A configured VLAN has been excluded on a trunk port and so is being removed from the configuration.","This is an informational message only. No action is required."
"POS","1","UNAVAILABLE","%s initialization failed","The POS line card failed to complete hardware initialization.","Copy the error message exactly as it appears, and report it to your technical support representative."
"POS","1","UNAVAILABLE","%s(%d) Hardware failure. %s","The POS line card encountered a hardware failure. The line card will be deactivated.","Copy the error message exactly as it appears, and report it to your technical support representative."
"POS","1","UNAVAILABLE","%s(%d) Only found %d interfaces, deactivating line card","The POS hardware failed. Incorrect number of interfaces discovered.","Copy the error message exactly as it appears, and report it to your technical support representative."
"POS","1","UNAVAILABLE","%s(%d/%d) Failed to obtain PXF resources, error=%d, shutting down interface","The POS line card failed to get the PXF resources. The interface will be shutdown if already up or deactivated if this card was OIRed.","Copy the error message exactly as it appears, and report it to your technical support representative."
"POS","3","UNAVAILABLE","%s(%d) %s","The POS hardware is not supported on this platform.","Upgrade your system."
"POSDW","1","UNAVAILABLE","%s init timed out","The PA-POS-OC3 port adaptor driver failed to complete hardware initialization.","Copy the error message exactly as it appears, and report it to your technical support representative."
"POSDW","1","UNAVAILABLE","Only found %d interfaces on bay %d, shutting down bay","The PA-POS-OC3 port adaptor hardware initialization failed. Incorrect number of interfaces discovered.","Copy the error message exactly as it appears, and report it to your technical support representative."
"POSDW","3","UNAVAILABLE","%s","The PA-POS-OC3 port adaptor is not supported on this platform. The system log specifies the part of the system that requires an upgrade.","Upgrade your system to a platform that supports the PA-POS-OC3 port adapter. Refer to the system log to determine what part of your system requires an upgrade."
"POSDW","3","UNAVAILABLE","%s packet buffer, pak=0x%x","A software or hardware error occurred. The PA-POS-OC3 port adaptor driver detected that the transmit ring is in an inconsistent and unrecoverable state.","Copy the error message exactly as it appears, and report it to your technical support representative."
"POSDW","3","UNAVAILABLE","Device reported %#x","The PA-POS-OC3 port adaptor hardware initialization failed. Found incorrect device identifier.","Copy the error message exactly as it appears, and report it to your technical support representative."
"POSLC","1","INITFAIL","POSLC(%d/%d), initialization timeout failure","LC POS ASIC and framer initialization failed","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"POSLC","1","UNAVAILABLE","POSLC(%d/%d), initialization timeout failure","LC POS ASIC and framer initialization failed","Copy the error message exactly as it appears on the console or in the system log. If you cannot determine the nature of the error from the error message text, call your Cisco technical support representative and provide the representative with the gathered information."
"POSLC","3","4302","Runaway Skystone 4302 framer %d Tx %s counter, byte=%d, pkt=%d.","4302 hardware errors","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"POSLC","3","APS","APS(%d) %s","RP deadman timer expired on LC, LC is sending LAIS to far end","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"POSLC","3","BMAENG","%s POS, %s %s%s. (src=0x%x, det1=0x%x, det2=0x%x)","POS BMA engine hardware errors","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"POSLC","3","BMAPAR","%s POS, %s. BMA_DATA[3:0]=0x%x. (src=0x%x, det1=0x%x, det2=0x%x)","A parity error occurred onthe POS asic BMA engine","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"POSLC","3","HWERROR","[chars]","The Optical Services Module has encountered a hardware error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"POSLC","3","LINKBADEVT","Unexpected event woke up LC POS link process.","LC POS link report process receives an unexpected event","Copy the error message exactly as it appears on the console or in the system log. Issue the show subsys command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show subsys output, call your Cisco technical support representative and provide the representative with the gathered information."
"POSLC","3","LINKPROC","POSLC, lcpos_link_report process: Could not get argument","LC POS link report process stops working","Copy the error message exactly as it appears on the console or in the system log. Issue the show subsys, show memory summary commands to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show subsys, show memory summary output, call your Cisco technical support representative and provide the representative with the gathered information."
"POSLC","3","POSENG","%s POS, %s. %s, port %d. (src=0x%x, det1=0x%x, det2=0x%x)","POS engine hardware errors","Copy the error message exactly as it appears on the console or in the system log. Run diagnostics on the line card in slot (X). If diagnostics pass, call your Cisco technical support representative and provide the representative with the gathered information."
"POSLC","3","PROCESS_CREATEFAIL","[chars]","The PoS line card could not create a process required for its operation. This condition might be caused by a resource being unavailable.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"POSLC","3","PROCESS_TIMEREVENT","[chars]","An unexpected process timer event occurred in the Optical Services Module.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"POSLC","3","RXPOSTO","POSLC(%d/%d), RX POS engine shutdown failed","The software is trying to shutdown the Rx POS engine. POS engine refuses to shutdown, the software timeout","Copy the error message exactly as it appears on the console or in the system log. Run diagnostics on the line card in slot (X). If diagnostics pass, issue the execute-on slot (X) show controller pos registers command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the execute-on slot (X) show controller pos registers output, call your Cisco technical support representative and provide the representative with the gathered information."
"POSLC","3","SOP","%s SOP. (source=0x%x, halt_minor0=0x%x)","SOP hardware errors","Copy the error message exactly as it appears on the console or in the system log. Run diagnostics on the line card in slot (X). If diagnostics pass, call your Cisco technical support representative and provide the representative with the gathered information."
"POSLC","3","SRAMPAR","%s POS, %s. %s=0x%x%s. (src=0x%x, det1=0x%x, det2=0x%x)","Parity error occurred on POS asic SRAM","Copy the error message exactly as it appears on the console or in the system log. Run diagnostics on the line card in slot (X). If diagnostics pass, call your Cisco technical support representative and provide the representative with the gathered information."
"POSLC","3","TXPOSTO","POSLC(%d/%d), TX POS engine shutdown failed","The software is trying to shutdown the Tx POS engine. POS engine refuses to shutdown, the software timeout","Copy the error message exactly as it appears on the console or in the system log. Run diagnostics on the line card in slot (X). If diagnostics pass, issue the execute-on slot (X) show controller pos registers command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the execute-on slot (X) show controller pos registers output, call your Cisco technical support representative and provide the representative with the gathered information."
"POSLC","3","UNEXPECTED_PROCESSEVENT","[chars]","An unexpected process event occurred in the Optical Services Module.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"POT1E1","1","UNAVAILABLE","%s channel not disabled","The PRI port adaptor failed to respond to a request to disable an interface.","Copy the error message exactly as it appears, and report it to your technical support representative."
"POT1E1","1","UNAVAILABLE","%s channel not enabled;called from function %s","A software or hardware error occurred. The POT1E1 serial interface is not responding to commands used to initialize it.","Copy the error message exactly as it appears, and report it to your technical support representative."
"POT1E1","1","UNAVAILABLE","Download failed","Microcode download to POT1E1 port adapter failed.","Copy the error message exactly as it appears, and report it to your technical support representative."
"POT1E1","1","UNAVAILABLE","Fail to configure %d interfaces on bay %d, shutting down bay","Cannot configure some interfaces on board","Copy the error message exactly as it appears, and report it to your technical support representative."
"POT1E1","1","UNAVAILABLE","Failed for bay %d, sent = 0x%x, received = 0x%x","The download of the internal firmware to the POT1E1 failed to checksum correctly. This usually indicates a hardware failure","Perform a power cycle. If the problem persists, the POT1E1 hardware may have a problem."
"POT1E1","1","UNAVAILABLE","Microcode download failed to complete","The POT1E1 hardware has failed. It could not download its operational microcode.","Copy the error message exactly as it appears, and report it to your technical support representative."
"POT1E1","1","UNAVAILABLE","Not ready for download.","Error on the communication path between DRIVER and POT1E1","Copy the error message exactly as it appears, and report it to your technical support representative."
"POT1E1","1","UNAVAILABLE","Slot %d: %s","The PRI port adaptor failed to complete hardware initialization.","Copy the error message exactly as it appears, and report it to your technical support representative."
"POT1E1","1","UNAVAILABLE","only found %d interfaces on bay %d, shutting down bay","Mismatched type or POT1E1 hardware failure","Copy the error message exactly as it appears, and report it to your technical support representative."
"POT1E1","2","NOACCPTR","VC=[dec] [chars]","The POT1E1 port adapter could not increment the pointer count.","Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support and show controllers vip slot-number tech-support commands, with slot-number being the slot number where the POT1E1 port adapter resides. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support and show controllers vip slot-number tech-support commands, with slot-number being the slot number where the POT1E1 port adapter resides, and your pertinent troubleshooting logs."
"POT1E1","2","NOINC","[chars]","The POT1E1 port adapter encountered a null access pointer while it was incrementing the pointer count.","Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support and show controllers vip slot-number tech-support commands, with slot-number being the slot number where the POT1E1 port adapter resides. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support and show controllers vip slot-number tech-support commands, with slot-number being the slot number where the POT1E1 port adapter resides, and your pertinent troubleshooting logs."
"POT1E1","2","QTAIL","Qhead=[hex] particle_count=[dec] size=[dec]","The POT1E1 port adapter encountered a null queue heading.","Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support and show controllers vip slot-number tech-support commands, with slot-number being the slot number where the POT1E1 port adapter resides. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support and show controllers vip slot-number tech-support commands, with slot-number being the slot number where the POT1E1 port adapter resides, and your pertinent troubleshooting logs."
"POT1E1","2","TXBADVC","[chars], vc [dec]","The POT1E1 port adapter encountered a null queue heading.","Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support and show controllers vip slot-number tech-support commands, with slot-number being the slot number where the POT1E1 port adapter resides. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support and show controllers vip slot-number tech-support commands, with slot-number being the slot number where the POT1E1 port adapter resides, and your pertinent troubleshooting logs."
"POT1E1","3","FREEDMFATAL","Bay [dec]: freedm reset, command-status register [hex]","The POT1E1 port adapter has experienced a fatal problem related to the Frame Engine and Data Link Manager (FREEDM) ASIC.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"POT1E1","3","MBOXSEND","Bay [dec]: fail sending mbox msg [dec]","POT1E1 mailbox failed send","Copy the error message exactly as it appears, and report it to your technical support representative."
"POWERNET_ISSU","3","CAPABILITY","Powernet ISSU client %s","Powernet ISSU client observed an error during capability negotiation. When this error happens there is a mismatch between the client capability between the active and standby unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"POWERNET_ISSU","3","CAP_INVALID_SIZE","Powernet ISSU client capability list is empty.","The Powernet ISSU client capability exchange list size is invalid.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"POWERNET_ISSU","3","CAP_NOT_COMPATIBLE","Powernet ISSU client capability exchange result incompatible.","The Powernet ISSU client capability exchange has negotiated as incompatible with the peer.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"POWERNET_ISSU","3","INVALID_SESSION","EnergyWise ISSU client does not have a valid registered session.","EnergyWise ISSU client does not have a valid registered session.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"POWERNET_ISSU","3","MSG_NOT_OK","EnergyWise ISSU client 'Message Type %d' is not compatible","EnergyWise ISSU client received an incompatible message from the peer device. The message cannot be processed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"POWERNET_ISSU","3","TRANSFORM_FAIL","EnergyWise ISSU client %s transform failed for 'Message Type %d'. Error: %d (%s)","EnergyWise ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In both cases, the EnergyWise state between the active device and the standby device is not identical.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"POWERNET_ISSU","3","TRANSFORM_FAIL","EnergyWise ISSU client %s transform failed for 'Message Type %d'. Error: %d (%s)","EnergyWise ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In both cases, the EnergyWise state between the active device and the standby device is not identical.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"PPP","3","ISSU_ERR","[chars]","An error occurred during an ISSU versioning operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PQ3_FE","1","INITFAILP","PQ3/FE([dec]/[dec]), Init failed at [chars]","The FE could not allocate an I/O buffer pool.","Clear the interface. If the message recurs, call your technical support representative for assistance."
"PQ3_FE","1","MACADDRFAIL","PQ3/FE([dec]/[dec]), Unable to set the Mac-address for the interface","The FEC could not set the mac address of the interface.","Clear the interface. If the message recurs, call your "
"PQ3_FE","1","SHOWFAIL","PQ3/FE([dec]/[dec]), Memory error at [chars]","The FEC could not allocate memory to display controller.","Clear the interface. If the message recurs, call your technical support representative for assistance."
"PQ3_FE","2","NOISL","Interface [chars] does not support ISL","The interface cannot be configured as an ISL trunk.","Check the configuration."
"PQ3_FE","3","OVERFLO","PQ3/FE([dec]/[dec]), Receive overflow","While receiving a frame, the controller chip's local buffer transmitted insufficient data because data could not be transferred to DRAM fast enough to keep pace with its input rate. Normally, such a problem is temporary, depending on transient peak loads within the system.","The system should recover. No action is required."
"PQ3_FE","3","UNDERFLO","PQ3/FE([dec]/[dec]), Transmit underflow","While transmitting a frame, the controller chip's local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.","The system should recover. No action is required."
"PQ3_FE","4","BABBLE","PQ3/FE([dec]/[dec]), Babble error, CSR[dec]=[hex]","The transmitter has been on the channel longer than the time taken to transmit the largest frame.","The system should recover. No action is required."
"PQ3_FE","5","EXECOLL","PQ3/FE([dec]/[dec]), Excessive collision","Excessive collisions occurred on the Fast Ethernet interface.","No action is required."
"PQ3_FE","5","LATECOLL","PQ3/FE([dec]/[dec]), Late collision","Late collisions occurred on the Fast Ethernet interface.","If the interface is Fast Ethernet, verify that both peers are in the same duplex mode. No action is required."
"PQ3_FE","5","LOSTCARR","PQ3/FE([dec]/[dec]), Lost carrier. Transceiver problem?","The cable and/or transceiver is not connected.","Connect the cable and/or transceiver."
"PQ3_TSEC","1","INITFAIL","PQ3/FE([dec]), Init failed, CSR[dec]=[hex]","The software failed to initialize/restart an Ethernet/Fast Ethernet interface.","Clear the interface. If the message recurs, call your technical support representative for assistance."
"PQ3_TSEC","1","INITFAILP","PQ3/FE([dec]), Init failed at [chars]","The FEC could not allocate a I/O buffer pool.","Clear the interface. If the message recurs, call your technical support representative for assistance."
"PQ3_TSEC","1","MEMERR","PQ3/FE([dec]), Memory error, CSR[dec]=[hex]","The interface could not access system resources for a long time. This problem may occur under very heavy loads.","The system should recover. No action is required. If the message recurs, call your technical support representative for assistance."
"PQ3_TSEC","1","SHOWFAIL","PQ3/FE([dec]), Memory error at [chars]","The FEC could not allocate memory to display controller.","Clear the interface. If the message recurs, call your technical support representative for assistance."
"PQ3_TSEC","2","NOISL","Interface [chars] does not support ISL","The interface cannot be configured as an ISL trunk.","Check the configuration."
"PQ3_TSEC","3","OVERFLO","PQ3/FE([dec]), Receive overflow","While receiving a frame, the controller chip's local buffer transmitted insufficient data because data could not be transferred to DRAM fast enough to keep pace with its input rate. Normally, such a problem is temporary, depending on transient peak loads within the system.","The system should recover. No action is required."
"PQ3_TSEC","3","OWNERR","PQ3/FE([dec]), Buffer ownership error, pak=[hex]","The software detected an error in descriptor ownership.","Try a later version of the software. If the message recurs, call your technical support representative for assistance."
"PQ3_TSEC","3","UNDERFLO","PQ3/FE([dec]), Transmit underflow","While transmitting a frame, the controller chip's local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.","The system should recover. No action is required."
"PQ3_TSEC","4","BABBLE","PQ3/FE([dec]), Babble error, CSR[dec]=[hex]","The transmitter has been on the channel longer than the time taken to transmit the largest frame.","The system should recover. No action is required."
"PQ3_TSEC","5","COLL","PQ3/FE([dec]), Excessive collisions, TDR=[dec], TRC=[dec].","Ethernet/Fast Ethernet is seeing multiple collisions. This may occur under heavy loads.","The system should recover. No action is required."
"PQ3_TSEC","5","EXCESSCOLL","PQ3/FE([dec]), Excessive collision","Ethernet/Fast Ethernet is seeing multiple collisions. This may occur under heavy loads.","The system should recover. No action is required."
"PQ3_TSEC","5","LATECOLL","PQ3/FE([dec]), Late collision","Late collisions occurred on the Ethernet/Fast Ethernet interface.","If the interface is Fast Ethernet, verify that both peers are in the same duplex mode. For regular Ethernet, the system should recover. No action is required."
"PQ3_TSEC","5","LOSTCARR","PQ3/FE([dec]), Lost carrier. Transceiver problem?","The cable is not connected to the port.","Connect the cable to the port."
"PQUICC3","1","BADHDXFSM","PQUICC3([dec]/[dec]), Unexpected HDX state [dec], event [dec]","A bad event was detected in the state machine for half duplex transmission/reception.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"PQUICC3","1","CTSLOST","PQUICC3([dec]/[dec]), Clear to Send Lost","The Clear To Send (CTS) input signal on a data terminal equipment (DTE) serial interface became inactive while transmitting a frame. This problem is a result of a communication line failure or cable disconnection.","Check the serial interface cable and/or communication equipment, such as the channel service unit/data service unit (CSU/DSU)."
"PQUICC3","1","INITFAIL","PQUICC3([dec]/[dec]), SCC[dec] init failed","The software failed to initialize/restart a 1T serial card.","Clear the serial interface. If the message recurs, call your technical support representative for assistance."
"PQUICC3","1","LINEFLAP","PQUICC3([dec]/[dec]), Excessive modem control changes","The system received too many modem control signal interrupts. Modem control signals are hardware handshake signals between data terminal equipment (DTE) and data communications equipment (DCE). The signals include either a data carrier detect (DCD) or a data set ready (DSR), or both DCD and DSR.","Check the serial interface cable. The error can occur if the cable is disconnected or has come loose and is picking up noise. If the cable appears to be connected correctly, check the equipment connected to the cable."
"PQUICC3","1","NOMEMORY","Unit [dec], no memory for [chars]","The MPC8500/PowerQUICC CPU was unable to access the memory it needs to carry out its functions. Here are some possible causes.-The network is large, requiring a lot of memory for routing tables, etc.-The router configuration has many features enabled, each of which requires memory.-A software error (memory leak) exists.","Reduce system activity to ease the memory demand, or upgrade to a larger memory configuration."
"PQUICC3","1","QMC_GLOBAL_ERROR","PQUICC3([dec]/[dec]), Global error [hex] in QMC","One or more of the channels served by the QMC instance encountered transmitter underflow or receiver overflow or the QMC interrupt table overflowed. Normally, such a problem is temporary, depending on transient peak loads within the system.","The system should recover. No action is required."
"PQUICC3","1","TOOBIG","PQUICC3([dec]/[dec]), packet too big, packet size was [dec] bytes","A packet greater than the assigned MTU of this serial interface was queued up for transmission.","The system should recover. No action is required. If the message recurs, it may indicate an error related to data traffic patterns. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"PQUICC3","1","TOOSMALL","PQUICC3([dec]/[dec]), packet was less than 2 bytes, packet size was [dec] bytes","A small packet (less than 2 bytes) was queued up for transmission. The interface cannot handle such small packets for transmission.","The system should recover. No action is required. If the message recurs, it may indicate a hardware error related to data traffic patterns. copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"PQUICC3","1","UNDERFLO","PQUICC3([dec]/[dec]), Transmit underflow","While transmitting a frame, the serial controller chip's local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.","The system should recover. No action is required."
"PQUICC3","1","UNEXPECTED_INTERRUPT","PQUICC3([dec]), Unexpected modem-signal interrupt","The software did not expect to see a modem control signal change on this interface.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"PQUICC3","1","WRONG_SLOT","PQUICC3([dec]), BRI card in wrong slot(1)","The BRI card is not supported in WIC slot 0.","Power down, move the BRI card to the other WIC slot on the port module and reboot."
"PQUICC3","3","OWNERR","Unit [dec], buffer ownership error, pak = [hex]","An internal software error occurred.","Call your technical support representative to obtain a software upgrade."
"PQUICC3","3","SPURIOUS_INTERRUPT","Interface card in slot [dec] generated a spurious interrupt","Interface card on the router which is not supported by this image generated a spurious interrupt that can not be handled.","No action is required. To avoid seeing this message in the future, remove the unsupported card or use an image that supports it."
"PQUICC3","3","UNKNOWN_SCCS","PQUICC3, Incorrect SCC number","An internal software error occurred.","Call your technical support representative to obtain a software "
"PQUICC3","3","UNKNOWN_SCC_TX_VECTOR","PQUICC3, Unknown TX vector on port [dec]","An internal software error occurred.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"PQUICC3","1","UNKNOWN_WIC","PQUICC3([dec]), WIC card has an unknown ID of [hex]","The software does not recognize the type of WIC card plugged into the port module.","Check the part number on the WIC card to verify that it is supported in the IOS release operational on the router or contact your technical support representative."
"PQUICC3","1","UNSUPPORTED_CONFIG","Slot [dec] has an unsupported combination of ISDN WAN interface cards","It is not possible to support this type of BRI card in slot 1 along with another BRI card in slot 0.","Remove one of the BRI cards from either slot."
"PRBS","5","DECERR","Slot:[dec],Subcard:[dec],Port:[dec] Decoding error [dec] at time [dec] sec.","A software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PRBS","5","GETARGERR","process_get_arg_num error.","A software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PRBS","5","LOSSLOCK","Slot:[dec],Subcard:[dec],Port:[dec] Loss of Lock at time [dec] sec.","A software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PRBS","5","PASSED","Slot:[dec],Subcard:[dec],Port:[dec] [dec] sec PRBS test passed.","A PBRS test was successful.","No action is required."
"PRBS","5","STATUSERR","Slot:[dec],Subcard:[dec],Port:[dec] at [dec] sec status error [dec], quit.","A software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PRBS","5","STOP","Slot:[dec],Subcard:[dec],Port:[dec] PRBS test stop at [dec] sec.","A PBRS test stopped.","No action is required."
"PROCYON","3","CREATE_IBC_FAILED","Creation of procyon ibc idb failed","The creation of an inband control interface description block for the CPU daughter card has failed. The software or the hardware is faulty.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PROCYON","3","INIT_IBC_FAILED","Initialization of procyon ibc failed","Inband control initialization has failed. The software or the hardware is faulty.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PROCYON","3","INIT_ICDM_FAILED","Initialization of icdm driver failed","The ICDM driver initialization failed for the CPU daughter card inband control. The software or the hardware is faulty.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PROCYON","3","INIT_MAC_DRIVER_FAILED","Initialization of ethernet mac driver failed","The Ethernet MAC driver initialization failed for the CPU daughter card inband control. The software or the hardware is faulty.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PROCYON","3","MASKED_RCV_INTR","procyon_ibc_rcv_interrupt called while masked: [int]","The CPU received an inband interrupt, although the inband interrupt was masked. The software or the hardware is faulty.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PROCYON","3","NO_BUFFER_POOLS","Initialization of private buffer pools failed","Private buffer pools were not created for the CPU daughter card inband control. This condition can occur during periods of extreme traffic.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PROCYON","3","NO_PARTICLE","no particle available to populate the ethernet dma ring","No particle was available to populate the direct memory access of the Ethernet ring. This condition can occur during periods of extreme traffic.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PROCYON","3","RX_ADD_BUFFER_FAILED","particle not added to the ethernet dma ring","A particle was not added to the direct memory access of the Ethernet ring. The software or the hardware is faulty.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PROCYON_ION_INTR","3","ENABLE_INTR_REGISTER_ACCESS_FAILED","Access to interrupt registers failed","A failure occurred in accessing interrupt registers.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PROCYON_ION_INTR","3","ENABLE_KERNEL_MODE_FAILED","Access to kernel mode failed","A failure occurred in accessing kernel mode.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PROCYON_ION_INTR","3","INTERRUPT_UNMASK_FAILED","Interrupt unmask failed: interrupt_source [dec]","A failure occurred in unmasking interrupts.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PRST_IFS","3","FILE","persistent media IFS file error: %s","An error occurred in a persistent media module (IOS file system) file.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PRST_IFS","3","FILEMEM","No memory to update %s. Please free some space","There is no file system memory for the system to write an updated version of the persistent variable file.","Free space on the file system shown in the error message as soon as possible. You must delete existing files or squeeze the file system if the file system requires it (bootflash, for example, may require it)."
"PRST_IFS","3","GENERAL","persistent media IFS general error: %s","An error occurred in the persistent media module (IOS file system).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PRST_VBL","3","GENERAL","Persistent general error: %s","A general error related to a persistent variable occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PRST_VBL","3","MEDIA","Persistent media error: %s","A media error related to a persistent variable occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PT","3","PT_HW_UNAVAIL","Protocol Tunneling hardware resource not available. [chars]","Protocol tunneling could not be enabled because no redirect registers are available. Protocol tunneling requires redirect registers.","Disable any applications that use redirect registers and configure the protocol tunneling again."
"PT","3","PT_NO_SWSB","Protocol Tunneling software subblock not found. [chars]","The software subblock that is used for protocol tunneling could not be found for the port specified in the message text. Protocol tunneling has been disabled on this port.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF","2","DWNLOADCOLROW","Could not download the microcode into PXF processor @ column [dec] row [dec].","A problem occurred that prevented the microcode from being downloaded to PXF. This could be either a software or hardware abnormality.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_ACL","3","WS_ACL_CONTEXT_EVENT","[chars] [chars]","An invalid turbo ACL context has been used to call a block initialization. This condition is possibly caused by a process-level watchdog that has timed out.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_ACL","3","WS_ACL_EVENT","[chars]","PXF turbo ACL errors have occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_ACL","3","WS_ACL_PXF_CONTEXT_EVENT","[chars] [chars]","An invalid PXF turbo ACL context has been used to call a block initialization. This condition is possibly caused by a process-level watchdog that has timed out.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXFAPI","3","TIFBAD","TIF [int] is not available or invalid.","The PXF interface instance that was requested is not available or is invalid.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXFAPI","3","TIFINUSE","Request for in-use reserved TIF [int]","A PXF interface instance was requested but is currently reserved as it is still in use.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXFAPI","3","TIFNODETACH","TIF [int] could not be detached.","The PXF interface instance could not be detached.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF","2","DWNLOADCOLROW","Could not download the microcode into PXF processor @ column %d row %d.","There was some problem incurred that prevented microcode from being downloaded to PXF, this could be either a software or hardware abnormality.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_FIB","3","WS_FIB_RW_EVENT","[chars] [dec] [chars]","The Layer 2 information for this interface is not consistent in PXF. The router may resume normal operation after this message.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_FIB","3","WS_FIB_TIF_EVENT","[chars] [chars]","The interface does not have a valid PXF handle attached to it. The router may resume normal operation after this message.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_FLOW","4","INVLDAGG_SINGLE","The netflow aggregation scheme is not supported in PXF. This interface will be marked as unsupported by the PXF, all incoming traffic to this interface will be processed in the RP.","The only NetFlow aggregation schemes supported in the PXF are AS aggregation, proto port aggregation, source prefix aggregation, and destination aggregation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_FLOW","4","NO_INVLDAGG","All previously configured unsupported netflow aggregations have been disabled or removed. Netflow enabled interfaces may however still be marked unsupported due to other unsupported features configured.","Only PXF-supported NetFlow aggregation schemes are configured, or possibly no NetFlow aggregation schemes are configured.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_GRE","3","PXF_MEM_ERR_CLR_TSTATS","PXF MEM ERROR when clearing PXF tunnel stats (Addr=[hex])","An error occurred when clearing the tunnel statistics from PXF memory. The tunnel statistics could not be properly cleared.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_GRE","3","PXF_MEM_ERR_HINFO","PXF MEM ERROR when downloading tunnel hash info to PXF (Addr=[hex])","An error occurred when writing into PXF memory. Tunnel hash information could not be properly downloaded to PXF.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_GRE","3","PXF_MEM_ERR_HTIFS","PXF MEM ERROR when downloading tunnel hashed tifs to PXF (Addr=[hex])","An error occurred when writing into PXF memory. Hashed tunnel TIFs could not be properly downloaded to PXF.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_GRE","3","PXF_MEM_ERR_READ_TSTATS","PXF MEM ERROR when reading PXF tunnel stats (Addr=[hex])","An error occurred when reading the tunnel statistics from PXF memory. The tunnel statistics could not be properly read.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_GRE","3","PXF_MEM_ERR_TID","PXF MEM ERROR when downloading tunnel id to PXF (Addr=[hex])","An error occurred when writing into PXF memory. The tunnel ID could not be properly downloaded to PXF.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_GRE","3","PXF_MEM_ERR_TVRF","PXF MEM ERROR when downloading tunnel vrf to PXF (Addr=[hex])","An error occurred when writing into PXF memory. The tunnel VRF could not be properly downloaded to PXF.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_GRE","4","PXF_MEM_ERR","Memory allocation error while [chars]","An error has occurred while allocating memory. PXF could not process tunneled packets properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_MPLS_TE","3","PXF_MEM_ERR_CLR_TSTATS","PXF MEM ERROR when clearing PXF tunnel stats (Addr=[hex])","An error occurred when tunnel statistics were being cleared from PXF memory. The tunnel statistics could not be properly cleared.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_MPLS_TE","3","PXF_MEM_ERR_LKUP_TABLE","PXF MEM ERROR when downloading TE tunnel look-up table to PXF (Addr=[hex])","An error occurred while information was being written into PXF memory. The lookup table could not be properly downloaded to PXF.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_MPLS_TE","3","PXF_MEM_ERR_READ_TSTATS","PXF MEM ERROR when reading PXF tunnel stats (Addr=[hex])","An error occurred while tunnel statistics were being read from PXF memory. The tunnel statistics could not be properly read.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_MPLS_TE","4","PXF_MEM_ERR","Memory allocation error while [chars]","An error has occurred while allocating memory. PXF could not process a tunneled packet properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_QOS","3","UNAVAILABLE","Cannot %s actual QoS statistics generation in PXF","An error occurred when enabling or disabling QoS Statistic Generation.","Disable and re-enable PXF qos-statistics. Also: 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_QOS","3","UNAVAILABLE","Error attaching %s service-policy PXF data to %s: %s","The assignment of the PXF portion of the service-policy data to a sub-interface has failed. This means that, even though the configuration shows that the service-policy is attached to the sub-interface, the download of the necessary PXF data has not occurred. Because of that, the service-policy will not be effective on the sub-interface.","Detach and reattach the service-policy to the sub-interface. Also: 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_QOS","3","UNAVAILABLE","PXF MEM ERROR when attaching service policy in PXF (Addr=0x%08x)","An error occurred when reading from or writing to PXF memory. Service policy-map could not be properly attached to interface in PXF.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_QOS","3","UNAVAILABLE","PXF MEM ERROR when clearing a WRED counter in PXF (Addr=0x%08x)","An error occurred when writing to PXF memory. PXF WRED counter could not be properly cleared.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_QOS","3","UNAVAILABLE","PXF MEM ERROR when detaching CBWFQ from an interface in PXF (Addr=0x%08x)","An error occurred when reading from or writing to PXF memory. CBWFQ could not be properly detached from interface in PXF.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_QOS","3","UNAVAILABLE","PXF MEM ERROR when detaching service policy in PXF (Addr=0x%08x)","An error occurred when reading from or writing to PXF memory. Service policy-map could not be properly detached from interface in PXF.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_QOS","3","UNAVAILABLE","PXF MEM ERROR when downloading CBWFQ parameters to PXF (Addr=0x%08x)","An error occurred when reading from or writing to PXF memory. CBWFQ parameters could not be properly downloaded to PXF.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_QOS","3","UNAVAILABLE","PXF MEM ERROR when downloading QoS classificaton entry to PXF (Addr=0x%08x)","An error occurred when reading from or writing to PXF memory. QoS classification entry could not be properly downloaded to PXF.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_QOS","3","UNAVAILABLE","PXF MEM ERROR when downloading WRED parameters to PXF (Addr=0x%08x)","An error occurred when reading from or writing to PXF memory. WRED parameters could not be properly downloaded to PXF.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_QOS","3","UNAVAILABLE","PXF MEM ERROR when downloading marking parameters to PXF (Addr=0x%08x)","An error occurred when reading from or writing to PXF memory. 'set' command parameters could not be properly downloaded to PXF.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_QOS","3","UNAVAILABLE","PXF MEM ERROR when downloading policing parameters to PXF (Addr=0x%08x)","An error occurred when reading from or writing to PXF memory. Police parameters could not be properly downloaded to PXF.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_QOS","3","UNAVAILABLE","PXF MEM ERROR when downloading priority parameters to PXF (Addr=0x%08x)","An error occurred when reading from or writing to PXF memory. 'priority' command parameters could not be properly downloaded to PXF.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_QOS","3","UNAVAILABLE","PXF MEM ERROR when reading a WRED counter from PXF (Addr=0x%08x)","An error occurred when reading from PXF memory. PXF WRED counter could not be properly read (0 value assumed).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_QOS","3","UNAVAILABLE","PXF MEM ERROR when setting CBWFQ up in an interface in PXF (Addr=0x%08x)","An error occurred when reading from or writing to PXF memory. CBWFQ could not be properly set up in interface in PXF.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_QOS","3","UNAVAILABLE","Too many configured policy-maps (%d) for current number ofTurboACL classification outcomes (%d).","QoS PXF Classification Engine (based on turbo acl): due to thecurrent number of possible outcomes of the turbo acl compilation,there is not enough memory to hold new policy-maps.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_QOS","3","UNAVAILABLE","Too many possible turbo acl outcomes (%d) for current number ofconfigured policy-maps (%d).","QoS PXF Classification Engine (based on turbo acl): due to thecurrent number of policy-maps, there is not enough memory tohold all possible outcomes of the turbo acl compilation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_QOS","3","UNAVAILABLE","Too many possible turbo acl outcomes: %d (max policies: %d).","QoS PXF Classification Engine (based on turbo acl): there is not enough memory to hold all possible outcomes of the turbo acl compilation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_QOS","3","UNAVAILABLE","Unknown QoS action type: 0x%x.","A QoS feature, unrecognized by PXF, has been configured with the Modular QoS CLI. The feature will work but excessive punting may occur if the feature is on an output interface","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_QOS","3","UNAVAILABLE","VTMS will not work correctly. Use hierarchical policy-map for this interface.","This interface does not have a configured link bandwidth. A linkbandwidth is required for VTMS to operate correctly","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"PXF_VRFS","3","UNAVAILABLE","%s","Generic PXF VRFS errors","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"QA","3","UNAVAILABLE","%s","This is a software error.","Copy the error message exactly as it appears. Also copy the output of show version and show cont cbus. Contact your technical support representative."
"QA","3","UNAVAILABLE","NULL","This is a diagnostic message.","This message appears after a QA error, and contains diagnostic information regarding that error. Copy the original QA error message and all the following QA diagnostic error messages exactly as they appear. Also copy the output of show version and show cont cbus. Contact your technical support representative."
"QATM","2","UNAVAILABLE","Cannot read TCAM","Possibly bad hardware","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"QATM","2","UNAVAILABLE","Cannot read TCAM associated data","Possibly bad hardware","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"QATM","2","UNAVAILABLE","Cannot write TCAM associated data","Possibly bad hardware","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"QATM","2","UNAVAILABLE","Cannot write the TCAM","Possibly bad hardware","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"QEM","3","UNAVAILABLE","Found %s switch processors","The QEM driver found either no switch processors or more than one. Exactly one is the only supported configuration.","Make sure there is only one switch processor."
"QM","2","ACL_FAILURE","Interface %s traffic will not comply with ACLs in %s direction(s)","ACLs will not be applied to traffic for this interface due to TCAM resource contention.","The configured ACLs are too large to all fit in the hardware TCAM. Try and share the same ACLs across multiple interfaces in order to reduce TCAM resource contention."
"QM","2","CONFORM_ACTION_NE","Different aggregate and microflow conform-action in class [chars][policy [chars]]","Conform actions in the police and police flow commands must be the same for the same class in a service-policy applied to MLS interfaces.","Change the conform-action in the police or police flow command to make both actions the same, or remove one of the two commands."
"QM","2","DSCP_NE","Different aggregate and microflow DSCP in class %s[policy %s]","Conform actions in 'police' and 'police flow' commands must be the same for the same class in a service-policy applied to MLS interfaces.","Change the conform-action in the police or police flow command to make both actions the same, or remove one of two commands."
"QM","2","ERROR","%s %s:%d","This message can take many forms. It provides information about a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"QM","2","MAX_ACLS_EXCEED","The number of %s ACLs in a service-policy for %s exceeds 255","This interface doesn't support more than 255 ACLs per service-policy, per protocol.","Reduce the total number of classes (per protocol) in the service-policy."
"QM","2","MERGE_ERROR","ACL merge error for Interface [chars] in [chars] direction status [dec]","The ACL merge failed before programming ACLs into the TCAM.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"QM","2","NO_AGGREG_PLC","Hardware aggregate policer resources exceeded","The hardware doesn't have the capacity to handle aggregate policers required by configuration.","Reduce the total number of aggregate policers required by all service-polic ies installed in the device. For example, use shared aggregate policers, as defined by 'mls qos aggregate-policer' command, instead of default per-interface policers"
"QM","2","NO_AGGREG_PLC_IF","Out of hardware aggregate policers (policy %s, class %s, interface %s","The hardware doesn't have the capacity to handle aggregate policers required by the service-policy class for the indicated interface.","Reduce the total number of aggregate policers required by all service-polic ies installed in the device. For example, use shared aggregate policers, as defined by 'mls qos aggregate-policer' command, instead of default per-interface policers"
"QM","2","NO_FLOW_PLC","Hardware microflow policer resources exceeded","The hardware doesn't have the capacity to handle microflow policers required by the policy-map.","Adjust microflow policing rate/burst parameters so that the total number of different rate/burst combinations in the device is reduced."
"QM","2","PLC_ATTACH_REJECT_2_PLCRS","Command rejected: (policy [chars] interface [chars] dir [chars]) police and police aggregate commands present in same traffic class","One of two conditions has occurred: either a policy map that contains a traffic class with both police and police aggregate commands is attached to an unsupported interface or a policy attached to an interface is being modified in an unsupported manner.","Remove the unsupported command combination from the same traffic class. In the case of a modification to a policy that is already attached to unsupported interfaces, no action is required because the command is automatically rejected."
"QM","2","PLC_ATTACH_REJECT_ARP_UFLOW","Command rejected: (policy-map [chars] class [chars] interface [chars] dir [chars]) flow policer is not supported for traffic classes matching ARP ACL.","In a policy map, flow policer is not supported if the traffic class is matching ARP ACL.","Remove the flow policer from traffic class matching ARP ACL and reattach the policy or change the traffic class to match non-ARP ACL and configure flow policer."
"QM","2","PLC_ATTACH_REJECT_IPX_PROTO","Command rejected: (policy-map %s class %s) IPX access-list is not supported in EARL7.","In a class map, an IPX access list is not supported in the match criteria.","Remove the IPX access list from the traffic class match criteria and reattach the policy, or change the traffic class to match a non-IPX ACL."
"QM","2","PLC_ATTACH_REJECT_SET","Command rejected: (policy [chars] interface [chars] dir [chars]) police/trust and set commands present in same traffic class","One of two conditions has occurred: either a policy map that contains a traffic class with both set and police/trust commands is attached to an unsupported interface or a policy attached to an interface is being modified in an unsupported manner.","Remove the unsupported command combination from the same traffic class. In the case of a modification to a policy that is already attached to unsupported interfaces, no action is required because the command is automatically rejected."
"QM","2","POLARIS_POLICY_REINSTALL","Policy %s on %s is reinstalled.","Polaris version 1 card doesn't support egress QoS for multicast traffic.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"QM","2","POLARIS_POLICY_REMOVE","Policy %s on %s is removed.","Polaris version 1 card doesn't support egress QoS for multicast traffic.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"QM","2","QM_MODE_1","QoS on vlan/etherchannel interfaces or egress side is removed.","Polaris version 1 card doesn't support egress QoS for multicast traffic.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"QM","2","SET_IP_AND_MPLS","Hardware does not support 'set mpls exp' and 'set precedence | dscp' together","The hardware does not support the set mpls exp and set precedence | dscp commands together.","Use either the set mpls exp or the set precedence | dscp command."
"QM","2","TCAM_ENTRIES_EXCEEDED","ACL merge failed, ACEs exceed TCAM capacity or 0 ACES, [dec] ACEs for interface [chars] in [chars] direction","The ACL merge was halted. The results of the ACL merge have caused the number of ACEs to exceed the TCAM capacity, or zero ACEs were present.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"QM","3","ERROR_STAT","%s stat:%d in %s:%d","This message can take many forms. It provides information about a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"QM","4","AGG_POL_EXCEEDED","QoS Hardware Resources Exceeded : Out of Aggregate policers","The supported number of aggregate policers has been exceeded. On EARL 7-based switches, this limit is 1023.","Attempt to aggregate policers if possible."
"QM","4","AGGREG_PLC_IGNORED","'police' command ignored in presence of 'police aggregate %s'","If both 'police' and 'police aggregate' are specified as policy actions for the same class, 'police' is ignored as long as aggregate has been defined via 'mls qos aggregate'.","Do not specify both 'police' and 'police aggregate' in same class."
"QM","4","FRAG_INFO","QoS TINY_FRAG : enable 'mls qos vlan based' on accessports of L3 VLANs for fo1 policing to take effect","Policing of fragment offset == 1 (FO1) packets through switch ports will be supported only if the port is in VLAN-based mode, because FO1 policing is a Layer 3 feature.","Enter the mls qos vlan based command on the switch port."
"QM","4","MFLOW_POL_EXCEEDED","QoS Hardware Resources Exceeded : Out of Micro flow policers","The supported number of microflow policers has been exceeded. On EARL7-based switches, this limit is 63.","No action is required."
"QM","4","TCAM_CAPMAP","Interface %s hardware TCAM LOU usage capability exceeded","The hardware TCAM doesn't have the capacity to handle the number of logical operations used with the configured ACLs on this specific interface.","The hardware TCAM can only handle up to 9 logical operations per interface and up to 64 logical operations in total. Reduce the use of logical operations in the ACLs."
"QM","4","TCAM_ENTRY","Hardware TCAM entry programming failed for %s intf %s dir %s:  %s","The hardware TCAM doesn't have the capacity to handle all of the configured ACLs.","The configured ACLs are too large to all fit in the hardware TCAM. Try and share the same ACLs across multiple interfaces in order to reduce TCAM resource contention."
"QM","4","TCAM_LABEL","Hardware TCAM label capacity exceeded","The hardware TCAM doesn't have the capacity to handle the number of interfaces configured with ACLs.","The hardware TCAM can only handle 500 interfaces configured with ACLs. Deconfigure ACLs from some of the interfaces."
"QM","4","TCAM_LOU","Hardware TCAM LOU capacity exceeded","The hardware TCAM doesn't have the capacity to handle the number of logical operations used with the configured ACLs.","The configured ACLs are too large to all fit in the hardware TCAM. Try and share the same ACLs across multiple interfaces in order to reduce TCAM resource contention."
"QM","4","TCAM_MASK","Hardware TCAM mask entry capacity exceeded","The hardware TCAM does not have the mask capacity to handle all of the configured ACLs.","Because the configured ACLs are too large to all fit in the hardware TCAM, try to share the same ACLs across multiple interfaces in order to reduce TCAM resource contention."
"QM","4","UNEXPECTED_INTERNAL_QOS_CONDITION","Unexpected internal QoS condition.","An unexpected internal QoS condition has occurred. QoS debug may be enabled to obtain more information in case the condition recurs.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"QM","4","WARNING","%s %s:%d","This message provides information about a software warning.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"QM","6","EOM_FORCE_TRUSTED","EoMPLS on [chars] caused install of 'trust cos' state","If EoMPLS is configured on the interface or any of its subinterfaces, the no trust state is automatically replaced by the trust CoS state.","Remove all EoMPLS configurations from the interface to restore the no trust state."
"QM","6","EOM_RESTORE_UNTRUSTED","The 'no trust' state is restored on EoMPLS removal from [chars]","If EoMPLS is unconfigured on the interface and all its subinterfaces, the no trust state is restored.","No action is required."
"QM","6","EOM_TRUST_NOT_INSTALLED","'no trust' command is not installed on [chars] in presence of EoMPLS","If EoMPLS is configured on the interface or any of its subinterfaces, the no trust command is not installed.","Remove all EoMPLS configurations from the interface."
"QM","6","IOS_AND_PS_FEATURE","[chars] action cannot be present in classmap [chars] of policymap [chars] because this service-policy cannot be executed in Cat6K HW due to the presence of filters which require packets to be processed in IOS SW","NBAR is required for the match protocol commands used. NBAR exists only in software. Hardware-specific actions cannot be supported.","Remove either the hardware-specific command(s) or the match protocol criteria in class map."
"QM","6","NBAR_DISABLED","Packets will not be software switched.","NBAR is disabled so traffic will not be redirected to the RP.","No action is required."
"QM","6","NBAR_ENABLED","Packets will be software switched.","NBAR is enabled so all the traffic will be redirected to the RP.","No action is required."
"QM","6","SET_AND_POLICE","'set' and 'police' commands cannot co-exist in classmap [chars] of policymap [chars]","The set and police commands cannot coexist in a class map for a QoS manager (QM) supported interface.","Choose one of the commands or use the set-dscp-transmit | set-precedence-transmit | set-exp option for the conform action of the police command."
"QM","6","SET_AND_TRUST","'set' and 'trust' commands cannot co-exist in classmap [chars] of policymap [chars]","The set and trust commands cannot coexist in a class map for a QoS manager (QM) supported interface.","Choose one of the commands."
"QM","6","SHAREDAG_AND_POLICE","'police aggregate' and regular 'police' commands cannot co-exist in classmap [chars] of policymap [chars]","The set and police commands cannot coexist in a class map for a QoS manager (QM) supported interface.","Choose one of the commands or use the set-dscp-transmit | set-precedence-transmit | set-exp option for the conform action of the police command."
"QM","6","TRUST_AND_POLICE","'trust' and 'police/police aggregate with a set' cannot co-exist in classmap %s of policymap %s","The trust command and the police (or police aggregate) command with set statements cannot coexist in a class map for a QoS manager (QM) supported interface.","Remove the set statements in the police or police aggregate command."
"QM","6","UNDEF_SHR_AG","shared aggregate policer [chars] used in classmap [chars] of policymap [chars] is not defined","Shared aggregate policers have to be created first by entering the mls qos aggregate command before being used in a policy map.","Either define the shared aggregate policer or do not use it in the policy map."
"QLLC","3","UNAVAILABLE","%e - Different partner - originally %e - now %e","The partner for this QLLC virtual MAC address does not match the MAC address that was defined with the qllc partner command.","Verify that the qllc partner statement in the configuration file is correct."
"QLLC","3","UNAVAILABLE","%s","An I-Frame was discarded due to network congestion.","Verify that the LAN is not beaconing and that it is not in a congested state. Copy the error message exactly as it appears, and report it to your technical support representative."
"QLLC","3","UNAVAILABLE","%s","The text string provided with this error message describes the specific QLLC problem.","Follow the instructions that appear with the error message. Copy the error message exactly as it appears, and report it to your technical support representative."
"QLLC","3","UNAVAILABLE","%s ptr is null","The specified structure was not configured.","Confirm the configuration commands for the structure."
"QLLC","3","UNAVAILABLE","Bad opcode %04x from %e to %e","Either remote source-route bridging is incorrectly configured, or the other RSRB device is down.","Verify that remote source-route bridging is configured correctly with the right version of the IOS software."
"QLLC","3","UNAVAILABLE","Bad qllc state - %s - %e","An invalid LLC primitive was detected.","Verify that the Token Ring ports and any participating LAN devices are configured correctly."
"QLLC","3","UNAVAILABLE","Bad qllc state - %s","An invalid QLLC primitive was detected.","Verify that the partner QLLC device is configured correctly."
"QLLC","3","UNAVAILABLE","Bad qllc state - %s event - %s macaddr - %e","The LLC primitive specified placed the router in an invalid state.","Verify that the Token Ring ports and any participating LAN devices are configured correctly."
"QLLC","3","UNAVAILABLE","Couldn't make null xid - %e -%e","An attempt to create an IEEE XID failed.","Verify that the qllc partner statement in the configuration file is correct, and that the partner is on the desired LAN."
"QLLC","3","UNAVAILABLE","Couldn't make xid - %e -%e","The QLLC XID could not be forwarded to the LAN.","Verify that the qllc partner and the qllc xid commands are correct."
"QLLC","3","UNAVAILABLE","Incoming Call: Insufficient resources available","This message is reporting insufficient system memory.","Upgrade the memory."
"QLLC","3","UNAVAILABLE","Incoming call: No QLLC Service Access Point Configured for x.25 subaddress %s","A remote X.25 device is calling the router for QLLC service using a subaddress that was not configured by the X.25 routing facility. The subaddress was not configured for QLLC service.","Correct the QLLC configuration. Configure only the subaddress on the QLLC service, not the complete X.121 address that the remote X.25 device uses."
"QLLC","3","UNAVAILABLE","Incoming call: No partner Mac Address configured - X.25 subaddress %s","There is an incoming call, but a connection cannot be initiated to a partner since no partner is configured in a qllc dlsw command (for QLLC/DLSw+ only).","Configure a partner for the incoming calling (such as using the qllc dlsw partner command)."
"QLLC","3","UNAVAILABLE","Incoming call: QLLC map entry not found","A software error in the router code occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"QLLC","3","UNAVAILABLE","M bit Reassembly failed - couldn't allocate a packet","The router ran out of memory to allocate buffers.","Make sure that the router configuration is adequate for the service expected of it. You might want to tune the buffer pools, or upgrade to a larger router. At the very least, you will need more memory."
"QLLC","3","UNAVAILABLE","No QLLC Service Access Points defined","No QLLC services have been configured, even though the router will accept incoming calls for QLLC.","Configure the QLLC service required."
"QLLC","3","UNAVAILABLE","No lnx entry for macaddr %e","No virtual MAC address was defined for this interface.","Define the virtual MAC address, using either the x25 map qllc or the x25 pvc qllc command."
"QLLC","3","UNAVAILABLE","Not enough memory available","There is not enough memory in the system to complete this request.","Add more memory to the router. Otherwise, reduce the configuration or the load on the router."
"QLLC","3","UNAVAILABLE","Opcode %s is invalid","Either remote source-route bridging or local acknowledgment is configured incorrectly.","Verify that remote source-route bridging and local acknowledgment are configured correctly."
"QLLC","3","UNAVAILABLE","Outgoing call: Partner Mac Address %e doesn't match configured partner %e","A device tried to connect to a QLLC VMAC (from Token Ring, for instance), but the MAC address of that device does not match the partner in the qllc dlsw command.","Correct the QLLC configuration to match the right partner."
"QLLC","3","UNAVAILABLE","Pak enqueue failed","A packet was not sent to the LAN.","Verify that the LAN partner is configured correctly, and that the partner is on the desired LAN."
"QLLC","3","UNAVAILABLE","Sna configuration error for %e: Lan device is PU2.1, X.25 device is PU2.0 (XID Format 1)","The IBM Gateway (3172) or front-end processor on the LAN is sending XID Format 3 which is used to communicate with PU2.1 devices. The X.25 device is a PU2.0 (3174) that is configured to send XID Format 1 messages. This is a very rare situation - for example, Revision A5.6 on, and C5.1 on the 3172. A likely cause is that the revision levels on the IBM equipment are incompatible.","Check the revision levels on the external equipment, and upgrade them if necessary."
"QLLC","3","UNAVAILABLE","Unable to open an llc2 session","An LLC2 session could not be established with the destination MAC address.","Verify that the qllc partner statement in the configuration file is correct, and that the partner is on the desired LAN."
"QLLC","3","UNAVAILABLE","lnx_remove_macaddr_hash did not find target lnx","The qllc srb command was not defined for this interface.","Add a valid qllc srb statement for this serial interface."
"QLLC","4","UNAVAILABLE","Unable to open qllc session, current state is %s","A QLLC session could not be established.","Verify that the qllc partner and the qllc xid commands are correct."
"QNQ","6","NATIVE_VLAN_TAGGING","Please enable the native VLAN tagging feature for proper functioning of the Q-in-Q service.","QnQ may not function properly for packets in the native VLAN if native VLAN tagging is not enabled.","Enable native VLAN tagging by entering the vlan dot1q tag native command."
"QOS","3","HA_BULK_SYNC","%s Failure in completing bulk sync","The QoS configuration cannot be synchronized to the standby.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"QOS","3","HA_BULK_SYNC_BEFORE_TIMEOUT","%s Failure in completing bulk sync before timeout","The QoS configuration cannot be synchronized to the standby.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"QOS","3","HA_GET_ARG_NUM","%s Failure in getting event identification","The QoS configuration cannot be synchronized to the standby.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"QOS","3","HQFPOOLERR","interface [chars]: failed to allocate hqf particle","The HQF particle pool is empty. It cannot process a router generated packet.","Copy the message exactly as it appears on the console or in the system log. Enter the show buffer and show policy interface commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"QOS","3","NOCAPID","Failed to allocate QoS capability ID.","No more QoS capability IDs are available.","Change the Cisco IOS software image so that it can support more QoS capability IDs. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"QOS","6","EXTENDED_BURST_CHANGED_WARN","Illegal extended burst size; it is increased to [int]","Configured extended burst size is less than the Rate.It is considered to be illegal and has been reset basedon the Rate.","This is an informational message only.No action is required."
"QOS","6","NORMAL_BURST_CHANGED_WARN","Illegal normal burst size; it is increased to [int]","Configured normal burst size is less than the Rate.It is considered to be illegal and has been reset basedon the Rate.","This is an informational message only. No action is required."
"QOSMGR","3","FEATURE_NOT_FOUND","Cannot find feature for [chars]","An internal software error has occurred.","Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show running-config commands and your pertinent troubleshooting logs."
"QOSMGR","3","FILTERTYPE_INVALID","Internal Error Invalid Policy filtertype [dec]","An internal software error has occurred.","Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show running-config commands and your pertinent troubleshooting logs."
"QOSMGR","3","MERGE_RES_COUNT","Internal Error Invalid count","An internal software error has occurred.","Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show running-config commands and your pertinent troubleshooting logs."
"QOSMGR","3","NO_POLICER_QOSLABEL","Creating port Class Label Failed","An internal software error has occurred.","Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show running-config commands and your pertinent troubleshooting logs."
"QOSMGR","3","NO_VMR_QOSLABEL","qm_generate_vmrs have no qos label","An internal software error has occurred.","Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show running-config commands and your pertinent troubleshooting logs."
"QOSMGR","3","NULL_POLICER","Internal Error Invalid Policer","An internal software error has occurred.","Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show running-config commands and your pertinent troubleshooting logs."
"QOSMGR","3","POLICER_RES_COUNT","Internal Error Invalid Policer count","An internal software error has occurred.","Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show running-config commands and your pertinent troubleshooting logs."
"QOSMGR","3","POLICYMAP_NOT_FOUND","Cannot find policymap for [chars]","An internal software error has occurred.","Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show running-config commands and your pertinent troubleshooting logs."
"QOSMGR","3","QUEUE_PTR_ERROR","queue pointers out of order [hex] [hex] [hex] [hex]","An internal software error has occurred.","Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show running-config commands and your pertinent troubleshooting logs."
"QOSMGR","3","RESERVE_COUNT_ERROR","Reserved Count Exceeding total [dec]","An internal software error has occurred.","Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show running-config commands and your pertinent troubleshooting logs."
"QOSMGR","3","RESOURCE_INTERNAL","Internal Error in resource allocation","An internal software error has occurred.","Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show running-config commands and your pertinent troubleshooting logs."
"QOSMGR","3","VMRSEQ_INVALID","Internal Error Invalid VMR sequence","An internal software error has occurred.","Copy the message exactly as it appears on the console or in the system log. Enter the show running-config command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show running-config commands and your pertinent troubleshooting logs."
"QOSMGR","4","ACTION_NOT_SUPPORTED","Action is not supported in policymap [chars]","An action that cannot be configured by the set, trust, and police commands in policy map configuration mode was configured in a policy map. This condition indicates a hardware limitation.","Configure only the supported actions that can be configured by the set, trust, and police commands in policy map configuration mode."
"QOSMGR","4","CLASS_NOT_SUPPORTED","Classification is not supported in classmap [chars]","An unsupported match class-map command was entered in class-map configuration mode in a policy map and attached to an egress interface, or more than one match command was configured. This condition indicates a hardware limitation.","Reconfigure the class map or the policy map. Use only the match dscp command in class-map configuration mode in a policy map that is attached to an egress interface. Only one match per class map is supported."
"QOSMGR","4","COMMAND_FAILURE","Execution of [chars] command failed on [chars]","The command to configure a QoS setting failed. This condition possibly indicates a lack of hardware resources.","Check to see if any other messages along with this message indicate a resource failure. If other messages indicate that the hardware resources have been exceeded, retry the command with a smaller configuration. If you require more information, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"QOSMGR","4","HARDWARE_NOT_SUPPORTED","Hardware limitation has reached for policymap [chars]","The hardware cannot support the current policy map configuration. More QoS ACL entries have been configured than the number that is specified in the Switch Database Management template.","Reconfigure the class map or the policy map and reduce the number of QoS ACLs."
"QOSMGR","4","MATCH_NOT_SUPPORTED","Match type is not supported in classmap [chars]","An unsupported match type was specified. The only match types that are supported are match access-group, match dscp, and match precedence.","Reconfigure the class map. Ensure that only the match access-group, match dscp, and match precedence commands in class-map configuration mode are used within the class map."
"QOSMGR","4","NOT_SUPPORTED","Action '[chars]' is not supported for a policymap attached to output side.","A set or trust command was configured in policy-map class configuration mode in a policy map and attached to an egress interface. The requested action will not be applied to the configuration.","Do not configure a set or trust command in policy-map class configuration mode in a policy map and attach it to an egress interface. These policy map actions are supported only on ingress interfaces."
"QOSMGR","4","POLICER_PLATFORM_NOT_SUPPORTED","Policer configuration has exceeded hardware limitation for policymap [chars]","The policy map configuration has exceeded the limitation of the hardware. More policers have been configured in all policy maps by using the police or police aggregate command in policy-map class configuration mode than can be supported by the hardware.","Reconfigure the class map or the policy map or delete the policy from some interfaces."
"QOSMGR","4","POLICER_POLICY_NOT_SUPPORTED","Number of policers has exceeded per policy hardware limitation for policymap [chars]","The policy map configuration has exceeded the limitation of the hardware. More policers have been configured in a policy map by using the police or police aggregate command in policy-map class configuration mode than can be supported by the hardware.","Reconfigure the class map or the policy map, and reduce the number of policers."
"QUICC","1","UNAVAILABLE","QUICC(%d/%d), Clear to Send Lost","The Clear To Send (CTS) input signal on a data terminal equipment (DTE) serial interface became inactive while transmitting a frame. This problem is a result of a communication line failure or cable disconnection.","Check the serial interface cable and/or communication equipment, such as the channel service unit/data service unit (CSU/DSU)."
"QUICC","1","UNAVAILABLE","QUICC(%d/%d), SCC%x init failed","The software failed to initialize/restart a 1T serial card.","Clear the serial interface. If the message recurs, call your technical support representative for assistance."
"QUICC","1","UNAVAILABLE","QUICC(%d/%d), Transmit underflow","While transmitting a frame, the serial controller chip's local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.","The system should recover. No action is required."
"QUICC","1","UNAVAILABLE","Quicc(%d), BRI card in wrong slot(1)","The BRI card is not supported in WIC slot 0.","Power down, move the BRI card to the other WIC slot on the port module and reboot."
"QUICC","1","UNAVAILABLE","Quicc(%d), Unexpected modem-signal interrupt","The software did not expect to see a modem control signal change on this type of WIC card interface.","Copy the error message exactly as it appears, and report it to your technical support representative."
"QUICC","1","UNAVAILABLE","Quicc(%d), wic card has an unknown id of %x","The software does not recognize the type of WIC card plugged into the port module.","Check the part number on the WIC card to verify that it is supported in the IOS release operational on the router or contact your technical support representative."
"QUICC","1","UNAVAILABLE","Quicc(%d/%d), Excessive modem control changes","The system received too many modem control signal interrupts. Modem control signals are hardware handshake signals between data terminal equipment (DTE) and data communications equipment (DCE). The signals include either a data carrier detect (DCD) or a data set ready (DSR), or both DCD and DSR.","Check the serial interface cable. The error can occur if the cable is disconnected or has come loose and is picking up noise. If the cable appears to be connected correctly, check the equipment connected to the cable."
"QUICC","1","UNAVAILABLE","Quicc(%d/%d), Unexpected HDX state %d, event %d","A bad event was detected in the state machine for half duplex transmission/reception.","Copy the error message exactly as it appears, and report it to your technical support representative."
"QUICC","1","UNAVAILABLE","Quicc(%d/%d), packet too big, packet size was %d bytes","A packet greater than the assigned MTU of this serial interface was queued up for transmission.","The system should recover. No action is required. If the message recurs, it may indicate an error related to data traffic patterns. Copy the error message exactly as it appears, and report it to your technical support representative."
"QUICC","1","UNAVAILABLE","Quicc(%d/%d), packet was less than 2 bytes, packet size was %d bytes","A small packet (less than 2 bytes) was queued up for transmission. The interface cannot handle such small packets for transmission.","The system should recover. No action is required. If the message recurs, it may indicate a hardware error related to data traffic patterns. Copy the error message exactly as it appears, and report it to your technical support representative."
"QUICC","1","UNAVAILABLE","Slot %d has an unsupported combination of ISDN WAN interface cards","It is not possible to support this type of BRI card in slot 1 along with another BRI card in slot 0.","Remove one of the BRI cards from either slot."
"QUICC","1","UNAVAILABLE","msgtxt_nomemory","The MC68360/QUICC CPU was unable to access the memory it needs to carry out its functions. Here are some possible causes. The network is large, requiring a lot of memory for routing tables, and so on. The router configuration has many features enabled, each of which require a certain amount of memory. A software error (memory leak) exists.","Reduce system activity to ease the memory demand, or upgrade to a larger memory configuration."
"QUICC","3","UNAVAILABLE","QUICC(%d/%d), Buffer ownership error, pak=0x%x","An internal software error occurred.","Call your technical support representative to obtain a software upgrade."
"QUICC","3","UNAVAILABLE","Quicc, Incorrect SCC number","An internal software error occurred.","Call your technical support representative to obtain a software upgrade."
"QUICC","3","UNAVAILABLE","Unknown microcode revision number: %d","The MC68360/QUICC CPU was running an unexpected version of microcode. This could be possible if a new version of the QUICC chip was released or if a very old version was used in the manufacturing process. This could also occur if a new version of microcode was released to fix any bugs","A decrease in performance might occur for any async interfaces running PPP. Call your technical support representative if this is an issue."
"QUICC","3","UNAVAILABLE","msgtxt_ownerror","An internal software error occurred.","Call your technical support representative to obtain a software upgrade."
"QUICC_ASYNC","3","UNAVAILABLE","Unit %d, Clear to Send Lost","The Clear To Send (CTS) input signal on a data terminal equipment (DTE) serial interface became inactive while transmitting a frame. This problem is a result of a communication line failure or cable disconnection","Check the serial interface cable and/or communication equipment, such as the channel service unit/data service unit (CSU/DSU)."
"QUICC_ETHER","1","UNAVAILABLE","Unit %d, lost carrier. Transceiver problem?","The Ethernet 10BaseT cable is unplugged.","Connect the 10BaseT Ethernet cable."
"QUICC_ETHER","1","UNAVAILABLE","msgtxt_initfail","A software or hardware error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"QUICC_ETHER","3","UNAVAILABLE","Unit %d, underflow error","While transmitting a frame, the Ethernet controller chip's local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.","The system should recover. No action is required. If the problem reccurs, it indicates a hardware error that might be related to data traffic patterns. Copy the error message exactly as it appears, and report it to your technical support representative."
"QUICC_ETHER","3","UNAVAILABLE","Unit %d, underflow error","While transmitting a frame, the Ethernet controller chip's local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.","The system should recover. No action is required. If the problem recurs, it indicates a hardware error that might be related to data traffic patterns. Copy the error message exactly as it appears, and report it to your technical support representative."
"QUICC_ETHER","5","UNAVAILABLE","Unit %d, excessive collisions. Retry limit %d exceeded","An Ethernet cable is broken or unterminated.","Check cables for proper connections, termination, and so on."
"QUICC_ETHER","5","UNAVAILABLE","Unit %d, heartbeat check failure","The Ethernet cable might be too long, or there could be too many repeaters such that the delay from one end to the other is too long. The Ethernet cable might be overloaded with too many users.","Verify that your Ethernet cable is the correct length and that you do not have too many repeaters in use. If these are not the problem, try removing hosts from the Ethernet segment to reduce the load."
"QUICC_ETHER","5","UNAVAILABLE","Unit %d, heartbeat check failure","The Ethernet transceiver is malfunctioning.","Replace the hardware."
"QUICC_ETHER","5","UNAVAILABLE","Unit %d, late collision error","The Ethernet cable might be too long, or there could be too many repeaters such that the delay from one end to the other is too long. The Ethernet cable might be overloaded with too many users.","Verify that your Ethernet cable is the correct length and that you do not have too many repeaters in use. If these are not the problem, try removing hosts from the Ethernet segment to reduce the load."
"QUICC_SERIAL","1","UNAVAILABLE","msgtxt_initfail","The serial interface controller of the QUICC chip could not be initialized or started for operation. There is probably a hardware problem.","Power cycle the system. If the error reoccurs, replace the unit."
"QUICC_SERIAL","3","UNAVAILABLE","Unit %d, Clear to Send Lost","The Clear To Send (CTS) input signal on a data terminal equipment (DTE) serial interface became inactive while transmitting a frame. This problem stems from a communication line failure or cable disconnection.","Check the serial interface cable and or communication equipment such as the channel service unit/data service unit (CSU/DSU)."
"QUICC_SERIAL","3","UNAVAILABLE","Unit %d, underflow error","While transmitting a frame, the serial controller chip's local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.","The system should recover. No action is required. If the problem reccurs, it indicates a hardware error that might be related to data traffic patterns. Copy the error message exactly as it appears, and report it to your technical support representative."
"QUICC_SERIAL","5","UNAVAILABLE","Unit %d, carrier detect signal lost during message reception","The RS-232C Carrier Detect (DCD) signal was de-asserted during message reception. The DCE equipment is responsible for asserting this signal.","Check the serial interface cable. The error can occur if the cable is disconnected."
"QUICC_SERIAL","5","UNAVAILABLE","Unit %d, excessive modem control changes","The system received too many modem control signal interrupts. Modem control signals are hardware handshake signals between data terminal equipment (DTE) and data communications equipment (DCE). The signals include either a data carrier detect (DCD) or a data set ready (DSR), or both a DCD and a DSR.","Check the serial interface cable. The error can occur if the cable is disconnected or has come loose and is picking up noise. If the cable appears to be connected correctly, check the equipment connected to the cable."
"R4K_MP","3","CRASHED","CPU [dec] has now crashed a total of [dec] times.","The specified CPU failed the specified number of times and has been restarted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"R4K_MP","5","DELEGATE_GETBUF","Delegated call to [hex] failed, out of buffers","A remote procedure call (RPC) to the specified function failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RAC","3","UNAVAILABLE","Can not find lease information for interface %s","Internal error - DHCP lease information is missing for the interface","Report the problem and how it can be reproduced to Cisco TAC"
"RAC","3","UNAVAILABLE","Can't create RAC work queue","Internal error - probable cause is insufficient memory resources","Check available memory."
"RAC","3","UNAVAILABLE","DHCP is already running on interface %s","The interface already has a DHCP originated address via some other system mechanism","Verify the system configuration"
"RADIO","2","UNAVAILABLE","Radio%d/0, ODU %d: over temperature %s","Most likely cause is hardware failure or solar heating","Keep the RF ODU cool"
"RADIO","3","UNAVAILABLE","Radio%d/0, failed self-test","Most likely a hardware failure","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RADIO","4","UNAVAILABLE","%s%d/%d, Chip %s: failed to find image given current configuration","Most likely configured to use external files","Change configuration to use internal files"
"RADIO","4","UNAVAILABLE","Radio%d/0, DONE pin on FPGA %s did not assert after downloading","The DONE pin of a FPGA device on the RADIO line card did not assert after the downloading of the device. This probably indicates an existing or developing hardware failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RADIO","4","UNAVAILABLE","Radio%d/0, Error processing indication from DSP %s (%s:%d)","A DSP on the RADIO line card generated an indication message that could not be processed. This can happen when the router is operating under severe traffic load.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RADIO","4","UNAVAILABLE","Radio%d/0, HPI timeout while attempting to access DSP %s","A DSP on the RADIO line card was not granting access to its memory. Most likely cause is a DSP firmware internal error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RADIO","4","UNAVAILABLE","Radio%d/0, IDU IF internal serial communication error - %s","Most likely cause is a loose IF baby board","Replace hardware"
"RADIO","4","UNAVAILABLE","Radio%d/0, INIT pin on FPGA %s asserted during downloading","The INIT pin of a FPGA device on the RADIO line card asserted midway through the downloading of the device. Most likely cause is corrupted FPGA image.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RADIO","4","UNAVAILABLE","Radio%d/0, INIT pin on FPGA %s not asserted when PROG pin asserted","The INIT pin of a FPGA device on the RADIO line card did not assert when the PROG pin was asserted. This indicates either a faulty FPGA device or software problem resetting it.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RADIO","4","UNAVAILABLE","Radio%d/0, Internal %s Oscillator out of Lock %s","Most likely cause is vibration or hardware failure","Replace internal card"
"RADIO","4","UNAVAILABLE","Radio%d/0, ODU %d %s Oscillator out of Lock %s","Most likely cause is vibration or hardware failure","Replace electronics on Out Door Unit"
"RADIO","4","UNAVAILABLE","Radio%d/0, ODU %d is %s","Most likely cause is a disconnected cable","Check or replace cable from UBR to the Out Door Unit"
"RADIO","4","UNAVAILABLE","Radio%d/0, ODU %d max transmitter power exceeded %s","Most likely cause is hardware failure","Replace RF ODU"
"RADIO","4","UNAVAILABLE","Radio%d/0, ODU %d serial communication error - %s","Most likely cause is a disconnected cable","Check or replace cable from UBR to the Out Door Unit"
"RADIO","4","UNAVAILABLE","Radio%d/0, ODU %d: supply voltage out of range %s","Most likely cause is hardware failure","Replace RF ODU"
"RADIO","4","UNAVAILABLE","Radio%d/0, ODU %d: temperature is %d degrees C, threshold is %d degrees C","Most likely cause is hardware failure or solar heating","Keep the RF ODU cool"
"RADIO","4","UNAVAILABLE","Radio%d/0, Unsupported IF PIC major eeprom version (%u) on IDU","IOS should be upgraded to support the new eeprom","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RADIO","4","UNAVAILABLE","Radio%d/0, Unsupported RF PIC major eeprom version (%u) on ODU %d","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.","Call tech support - upgrade IOS"
"RADIO","4","UNAVAILABLE","Radio%d/0, bad IF PIC version (%d) on IDU","Most likely a hardware configuration oversite","Call tech support"
"RADIO","4","UNAVAILABLE","Radio%d/0, bad RF PIC version (%d) on ODU %d","Most likely a hardware configuration oversite","Call tech support"
"RADIO","4","UNAVAILABLE","Radio%d/0, could not find HW Capabilities field in IDPROM","Most likely cause is an improperly-programmed IDPROM","Have the IDPROM on the linecard reprogrammed"
"RADIO","4","UNAVAILABLE","Radio%d/0, link synchronization %s.","Most likely cause loose ODU cable","Check all cables"
"RADIO","4","UNAVAILABLE","Radio%d/0, link synchronization acquired.","Most likely cause is No Shut command","None"
"RADIO","4","UNAVAILABLE","Radio%d/0, link synchronization re-acquired.","Most likely cause is No Shut command on remote end","None"
"RADIO","4","UNAVAILABLE","Radio%d/0, radio phy eeprom %s checksum (stored:0x%02x, calculated:0x%02x)","Most likely cause is Shut or No Shut command","Enter the No Shut command"
"RADIO","4","UNAVAILABLE","Radio%d/0, spurious DSP response from %s: %08x %08x %08x %08x %08x %08x %08x %08x","A DSP on the RADIO line card generated a response message unexpectedly. This can happen when the router is operating under severe traffic load.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RADIO","4","UNAVAILABLE","Radio%d/0, uplink message queue overflow reported by DSP %s","At least one DSP-to-router message was lost due to that DSP's uplink queue being full. This can happen when many thresholds/histograms/timelines are being triggered or expiring at the same time.","Change thresholds and/or reduce histogram/timeline usage to lower the load on the system"
"RADIO","5","UNAVAILABLE","%s%d/%d, detected a bad CRC while downloading image %s to chip %s","Most likely a protocol error while downloading","If it's a TFTP download, try again; otherwise call tech support"
"RADIO","5","UNAVAILABLE","%s%d/%d, timeout trying to open image %s for chip %s","Most likely a protocol error while opening","If it's a TFTP download, try again; otherwise call tech support"
"RADIO","5","UNAVAILABLE","Radio%d/0, %s %s threshold crossed ODU %d","Most likely cause is a user defined threshold","none"
"RADIO","5","UNAVAILABLE","Radio%d/0, %s per %s threshold met(%d=%d)","Most likely cause is a mis-aligned antenna","Re-align the antenna(s)"
"RADIO","5","UNAVAILABLE","Radio%d/0, Link synchronization acquired.","Phy layer successfully acquired link.","None"
"RADIO","5","UNAVAILABLE","Radio%d/0, Lost link. Check remote transmitter.","Most likely cause remote system is not transmitting.","No Shut remote system"
"RADIO","5","UNAVAILABLE","Radio%d/0, ODU saftey interlock is preventing transmission. Check ODU and cables. %s","Most likely cause cable not attached, ODU overheated","Check ODU cable"
"RADIO","5","UNAVAILABLE","Radio%d/0, Remote end reports: %s","Most likely cause cable not attached, ODU overheated","Check ODU cables"
"RADIO","5","UNAVAILABLE","Radio%d/0, Remote end reports: Unable to acquire link synchronization.","Most likely cause cable not attached, ODU overheated","Check ODU cables"
"RADIO","5","UNAVAILABLE","Radio%d/0, Still trying to establish link (frequency sync).","Most likely cause remote system is not transmitting on correct frequency","No Shut remote system"
"RADIO","5","UNAVAILABLE","Radio%d/0, Still trying to establish link (timing sync).","Most likely cause remote system is not transmitting.","No Shut remote system"
"RADIO","5","UNAVAILABLE","Radio%d/0, Still trying to establish link (validate codeword).","Most likely cause remote system is not transmitting on correct frequency","No Shut remote system"
"RADIO","5","UNAVAILABLE","Radio%d/0, Still trying to establish link (viterbi sync).","Most likely cause remote system is not transmitting on correct frequency","No Shut remote system"
"RADIO","5","UNAVAILABLE","Radio%d/0, event %23s in state %15s","Most likely cause incorrect configuration","Review configuration and hardware capabilities"
"RADIO","5","UNAVAILABLE","Radio%d/0, hardware does not support requested configuration: %s","Most likely cause is incorrect configuration","Change the configuration to match the hardware"
"RADIO","5","UNAVAILABLE","Radio%d/0, invalid or inconsistent configuration requested %s","Most likely cause is the ARQ settings are not supported by the current radio channel parameters","Change ARQ settings to allowed values given the current radio channel parameters. You can use the radio arq reset command to do this."
"RADIO","5","UNAVAILABLE","Radio%d/0, link metrics cleared","User requested the link metrics be cleared","none"
"RADIO","6","UNAVAILABLE","%s%d/%d, could not find image %s for chip %s","Most likely a typo when set the url of the image","Try again"
"RADIO","6","UNAVAILABLE","Radio%d/0, self-test successful","Passed a self-diagnostic","This is a good thing"
"RADIO_DRIVER","1","UNAVAILABLE","Only found %d interfaces on bay %d, shutting down bay","Most likely system or hardware failure","Replace Line Card"
"RADIO_DRIVER","3","UNAVAILABLE","A line card local bus error, error status 0x%08x, error address 0x%08x","A device on the RADIO line card local bus either didn't respond to a select, timed out once selected or issued an error while selected. This probably indicates an existing or developing hardware failure.Error Message    %RADIO_DRIVER-3-UNAVAILABLE: DMAC detected a descriptor sequence error (DMAC Status Register is 0x%08x). Explanation    An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RADIO_DRIVER","3","UNAVAILABLE","DMAC reported PCI parity error (DMAC Status Reg: 0x%08x)","A parity error occured on the PCI bus while the RADIO DMA controller was performing a read/write. This probably indicates an existing or developing hardware failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RADIO_DRIVER","3","UNAVAILABLE","Device received a PCI Target Abort (DMAC Status Register is 0x%08x)","When attempting a PCI master read/write, the target issued an abort to the DMA controller. This usually indicates that an incorrect target was selected, and in this case means that shared packet memory was not the target. This is likely a software error causing the RADIO DMAC to access an invalid target.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RADIO_DRIVER","3","UNAVAILABLE","Device reported %#x","Most likely hardware failure","Replace defective hardware"
"RADIUS","3","ALLDEADSERVER","Group %s: No active radius servers found. Id %d.","All radius servers were found to be unresponsive.","Check the network connectivity to the radius servers, and check that the servers are running,"
"RADIUS","3","AIDDEFINEFAILED","a_id definition ignored.","An attempt to store a corrupted authority ID (a_id) failed or memory allocation failed during authority ID definition. Any existing authority ID will be preserved.","Configure a proper authority ID."
"RADIUS","3","BUFFER_OVERFLOW","Radius I/O buffer has overflowed","An unusually large number of Radius attributes has caused AAA to overflow it's Radius I/O buffer","This is an internal software error. Please report it to your technical support representative."
"RADIUS","3","CANNOT_OPEN_SOCKET","Cannot open UDP socket for service %s","The router is unable to open a socket for UDP communications by the indicated service.","Check your configuration to make sure that no other services are using the same port."
"RADIUS","3","CORRUPTCONTEXT","Bad Magic pattern in [chars]:[hex], magic:[hex]!","The magic pattern imprinted on the internal hash table data structures in the RADIUS subsystem is missing, which indicates memory corruption.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RADIUS","3","FORKFAIL","Failed to fork process for %s.","Quite likely, we ran out of memory. Other explanations are possible.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RADIUS","3","INVALIDFORMAT","Invalid Nas Port Format: [chars] [char]","The user is attempting to configure an incorrect format string.","Enter a 32-character string using supported characters only."
"RADIUS","3","NOACCOUNTINGRESPONSE","Accounting message [chars] for session [chars] failed to receive Accounting Response.","There was no response from the RADIUS server, and the maximum number of retransmissions has been exceeded. The network or the RADIUS server may be down.","Check the network connectivity to the RADIUS servers and check that the servers are running."
"RADIUS","3","NOATTRLIST","No attribute-list passed through parser.","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RADIUS","3","NOHOSTNAME","Failed to retrieve my hostname.","Could not find the router's hostname. A hostname needs to be defined, since it determines the radius profile we will retrieve","Define a hostname in the routers config."
"RADIUS","3","OVERRUN","Insufficient buffer space %d for string value.","This error occurs due to the insufficient memory allocated to the buffer. The condition could be caused by a software, less likely by a hardware. The traceback and process information is generated due to this condition.","If the error re-occurs, check bug toolkit on Cisco web-site to look for a bug that has symptoms similar to the one occured. If there is no entry for the problem you faced, collect the system message text exactly as it appears on the console or in the system log. Enter show tech-support, and contactyour technical support representative, and provide the representative with all the information gathered."
"RADIUS","3","SECRETDEFINEFAILED","Key definition ignored.","The user is attempting to store either a corrupted shared secret or memory allocation failed during secret definition. Any existing shared secret will be preserved.","Configure a proper secret. Refer to the shared secret configuration section for RADIUS servers in IOS documentation."
"RADIUS","3","SERVERTYPEMISMATCH","Servers [IP_address] and [IP_address] in server group '[chars]' are of different types.","All the servers in a server group should be of either type: standard or nonstandard.","Check the running configuration and verify that all the radius servers in the specified server group are of the same type: either standard or nonstandard."
"RADIUS","3","SOURCEPORTALLOCERROR","Warning: Unable to allocate port [dec]","The system was unable to allocate the port specified in the message. The system will not have the full range of source ports.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RADIUS","3","UNKNOWNAPI","Unknown API type %d","The RADIUS process has been invoked using an unknown application program interface (API) type. This condition is the result of a fault in the RADIUS subsystem.","Collect traceback and contact your technical support representative."
"RADIUS","3","ZEROATTRLEN","Radius attr [dec] len 0","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RADIUS","4","NOATTRLISTDEF","Warning: Attribute list %s is not defined.","The given attribute list is not defined.","Please define the attribute list as soon as possible."
"RADIUS","4","NOPUBLICSERV","Warning: No servers werefound in the public server list.","The given server is not on the global public serverslist. This is an internal consistency error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RADIUS","4","UNAVAILABLE","RADIUS server %i:%u,%u has returned.","A RADIUS server that previously was not responding has responded to a new request","No action is required."
"RADIUS","4","UNAVAILABLE","RADIUS server %i:%u,%u is not responding.","A RADIUS server has not responded to repeated requests.","Check to see if the RADIUS server is still active."
"RADIUS","4","UNAVAILABLE","Unable to process attribute list.","The attribute list is syntactically incorrect.","Please specify the attribute list as a comma-delimited string of integers between 1 and 255."
"RADIUS","4","UNAVAILABLE","Warning: Attribute list %s is not defined.","The given attribute list is not defined.","Please define the attribute list as soon as possible."
"RADIUS","4","UNAVAILABLE","Warning: No servers werefound in the public server list.","The given server is not on the global public serverslist. This is an internal consistency error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RADIUS","4","UNAVAILABLE","Warning: Server %i:%d,%d is not defined.","The given server is not on the master-list, and should be defined, or unexpected things might happen.","Please define the server on the appropriate master-list as soon as possible."
"RADIUS","4","UNAVAILABLE","Warning: Server %i:%d,%d is still referenced by server group.","The server being removed is still referenced by a server group","Please dereference the server from the server group as soon as possible."
"RADIUS","6","GETPOOLS","Retrieving IP-Pools via user %s","Getting initial IP-Pool definitions from RADIUS, using the given user's profile.","No action required."
"RADIUS","6","GETROUTES","Retrieving static routes in user %s","Getting initial static routes from RADIUS, using the given user's profile.","No action required. The message is informatory in nature and tells that it is getting the static routes based on user's profile."
"RADIUS","6","IDENTSAVE","Saving config with new acct ident in nvram.","Saving an accounting ident in nvram.","No action required."
"RADIUS","6","UNAVAILABLE","Group %s: Marked alive as Radius server %i:%d,%d configured.","Radius server is configured in the server group which was previously marked dead.","No action required."
"RADIUS","6","UNAVAILABLE","Group %s: Radius server %i:%d,%d is responding again (previously dead).","A radius server, which previously was dead, has started responding again.","No action required."
"RADIUS","6","UNAVAILABLE","Retrieving IP-Pools via user %s","Getting initial IP-Pool definitions from radius, using the given user's profile","No action required."
"RADIUS","6","UNAVAILABLE","Retrieving static routes in user %s","Getting initial static routes from radius, using the given user's profile","No action required."
"RADIUS","6","UNAVAILABLE","Saving config with new acct ident in nvram.","Saving an accounting ident in nvram.","No action required."
"RADIX","2","UNAVAILABLE","No memory for radix initialization: %s","The system ran out of memory during initialization. This should only occur if an image is too large for the existing dynamic memory.","Use a smaller subset image or upgrade hardware."
"RADIX","3","UNAVAILABLE","Error adding mask entry, %s","A software or hardware error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"RADIX","3","UNAVAILABLE","Error deleting trie entry, %s","A software programming error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"RADIX","3","UNAVAILABLE","Invalid pointer to head of tree, 0x%x","A software programming error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"RADIX","3","UNAVAILABLE","No memory available %s","The system is out of memory.","Try one of these actions to correct the problem: Reduce the number of routes accepted by this router. Upgrade hardware. Use a smaller subset image on run-from-RAM platforms."
"RADIX","4","UNAVAILABLE","Orphaned mask %#x, refcount=%d at %#x, next=%#x","A software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"RAIKO","3","UNAVAILABLE","Slot %d: Mgmt int. handler's registration routine was passed NULL callback address(es) -- enabler=0x%x, handler=0x%x; registering party's callback details ignored","A Mgmt-level interrupt handler has registered incorrectly with device-independent code; a software fix is requiredError Message    %RAIKO-3-UNAVAILABLE: Slot %d: a Mgmt interrupt occured but was not processed by a device-specific handler; following sources masked out: %s Explanation    A source of Mgmt-level interrupts does not have a handler registered for it; a software fix is needed to install the proper handlerError Message    %RAIKO-3-UNAVAILABLE: Slot %d: id of DFC%u is invalid (zero); cookie probably unprogrammed Explanation    When the cookie on the specified DFC was read for the id of the DFCan invalid value of 0 was returned. This suggests the DFC's cookiehas not been programmed properly.Error Message    %RAIKO-3-UNAVAILABLE: Slot %d: installation of Mgmt int. handler apparently failed -- routine currently installed at IOS Level %d is 0x%x Explanation    Tried to install required Mgmt interrupt handler at given IOS level but, upon checking, another handler was found thereError Message    %RAIKO-3-UNAVAILABLE: Slot %d: installation of desired Mgmt interrupt handler failed -- no routine is currently installed at IOS Level %d Explanation    Tried to install required Mgmt interrupt handler at given IOS level but, upon checking, no handler was installed whatsoeverError Message    %RAIKO-3-UNAVAILABLE: Slot %d: no free Mgmt int. handler callback entries (all %d in use); registering party's callback details dropped Explanation    More Mgmt interrupt handlers have registered than can be catered for; a software fix is requiredError Message    %RAIKO-3-UNAVAILABLE: Slot %d:DFC %d ERROR %s Explanation    A PCI error has occured trying to access a DFC The DFC has been shut down","Replace Hardware"
"RADPROXY","3","INIT","Initialisation failure, %s","An internal error occurred during RP initialisation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RADPROXY","3","INVALID_FSM_EVENT","Received invalid RP event %s in state %s","An internal RP error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RADPROXY","3","INVALID_FSM_STATE","Encountered an invalid RP state %d in %s","An internal RP error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RADPROXY","3","INVALID_MAC","Received invalid MAC %s in %s from %i with NAS-IP %i","Error occurred on receiving a invalid MAC","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RADPROXY","3","MEMORY_CORRUPT","RP Memory magic corrupted","RP memory magic corrupted","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RADPROXY","3","MEMORY_LOW","Memory low in RP terminating session","System memory is running low.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RADPROXY","3","NULL_FSM_CONTEXT","Encountered a NULL RP context in %s","Encountered a NULL context in RP.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RADPROXY","3","PROTOCOL_VIOLATION","RP encountered fatal protocol violation","Unrecoverable protocol error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RANDOM","6","RANDOM","A pseudo-random number was generated twice in succession","A pseudo-random number generator produced the same number twice in succession.","Under normal circumstances, a pseudo-random number generator will occasionally produce the same number twice in succession, which is not a problem. However, if this message occurs frequently, the system should be manually reloaded. If the message is persistent across reloads, copy the error message exactly as it appears, and report it to your Cisco technical support representative."
"RASP16","5","NULL_RASP16_OBJECT","The Interface Multiplexer device object pointer is set to NULL.","The memory location of the interface multiplexer device object is invalid. The interface multiplexer ASIC operation is disabled and the device interrupt is now masked.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RASP16","5","RASP_INIT_FAILURE","The Interface Multiplexer ASIC initialization failed.","The interface multiplexer ASIC could not be initialized. As a result, this device is not operational and has been disabled.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RBM","0","RBM_EMERG","%s","An error occurred in the Role-based Access Control Manager (RBM).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RBM","1","RBM_ALERT","%s","An error occurred in the Role-Based Manager (RBM).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RBM","2","RBM_CRIT","%s","An error occurred in the Role-based Access Control Manager (RBM).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RBM","3","RBM_ERR","%s","An error occurred in the Role-based Access Control Manager (RBM).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RBM","3","RBM_PARSE_ACE","Could not parse command for adding ACE '[chars]' to [chars] Role-Based Access List '[chars]'","An error occured while attempting to add an ACE to a Role-Based Access List. The ACE syntax is most likely incompatible with the type of RBACL.","Verify the syntax of the ACEs of the RBACL in ACS and the IP protocol versions the RBACL applies to. RBACL ACE syntax could be verified by manually configuring IP/IPv6 RBACL on the system within (config-rb-acl)/(config-ipv6rb-acl) configuration mode respectively."
"RBM","3","RBM_PARSE_CMD","Could not parse command. See command output and errors below %s","An error occured while attempting to parse command. Look for command output and parser errors below this message.","Follow the recommended action of the additional error messages that follow this message on your console."
"RBM","3","RBM_PARSE_RBACL","Could not parse command for creating [chars] Role-Based Access List '[chars]' '[chars]'","An error occured while attempting to create Role-Based Access List.","This error could occur when TrustSec attempts to install RBACL it has acquired from ACS while configuration mode is locked exclusively. TrustSec will retry this operation and should eventually succeed once configuration mode is no longer locked. If the error occurs when the configuration mode is not locked or if the RBACL does not get installed after the configuration mode lock is released."
"RBM","4","RBM_WARNING","%s","An error occurred in the Role-based Access Control Manager (RBM).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RBM","5","RBM_NOTICE","%s","This is a notice message from the Role-based Access Control Manager (RBM).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RBM","6","RBM_INFO","%s","This is an informational message from the Role-based Access Control Manager (RBM).","No action is required."
"RBM","7","RBM_ASSERT","Assertion Failure ( %s @%s:%d ) : %s","An error occurred in the Role-based Access Control Manager (RBM).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RCMD","4","UNAVAILABLE","DNS hostname/ip address mismatch. %s unknown to DNS","The IP address for an incoming rcmd request is not registered with DNS.","Add the IP address to DNS."
"RCMD","4","UNAVAILABLE","Remote copy from %s at %s denied","An attempt was made to connect to a router through RCP, but the router was not configured as an RCP server.","Configure an RCP server."
"RCMD","4","UNAVAILABLE","Remote shell from %s at %s denied","An attempt was made to connect to a router through rsh, but the router was not configured as an rsh server.","Configure an rsh server."
"RED_MODE","3","CAPENTRY_REG","Red Mode Cap Entry ([dec]) for Entity ([dec]) Registration failed ([chars])","A capability entry could not be registered for the redundancy mode ISSU.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu capability entries command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RED_MODE","3","CAPGROUP_REG","Red Mode Cap Group ([dec]) for Entity ([dec]) Registration failed ([chars])","A capability group could not be registered for the redundancy mode ISSU.","Copy the message exactly as it appears on the console or in the system log. Enter the show capability groups command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RED_MODE","3","CAP_REG","Red Mode cap reg failed: reason [dec]","The capabilities of the redundancy mode ISSU could not be registered.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu capability arguments command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RED_MODE","3","CAPTYPE_REG","Red Mode Cap Type for Entity ([dec]) Registration failed ([chars])","A capability type could not be registered for the redundancy mode ISSU.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu capability types command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RED_MODE","3","CLIENT_REG","Red Mode Client ([dec]) Registration failed ([chars])","The redundancy mode ISSU client could not be registered.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu clients command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RED_MODE","3","CLIENT_REG_FAILED","Red Mode ISSU client ([dec]) Client registration failed. [chars]","The redundancy mode ISSU client could not be registered during system initialization.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu clients command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RED_MODE","3","DELAYED_REGISTER","Delayed registration could not be completed succesfully, Operand = [dec]","The delayed registration operation for the RF-proxy clients could not complete successfully.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RED_MODE","3","ENTITY_REG","Red Mode Entity ([dec]) Registration failed ([chars])","The redundancy mode ISSU entity could not be registered.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu entities command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RED_MODE","3","GET_BUFFER","Red Mode ISSU session ([dec]) failed to get buffer","The redundancy mode ISSU session was unable to get a buffer.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu fsm command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RED_MODE","3","IPC_AGENT","[chars] [ [chars] ]","There has been a failure in the redundancy mode IPC agent.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RED_MODE","3","ISSU_BASE_CLIENT_INCOMP","One or more ISSU base clients are incompatible, fallback to RPR","An incompatible ISSU base client caused the redundancy mode to revert to route processor redundancy (RPR) mode.","Check the console log for the name and ID of the incompatible ISSU base clients."
"RED_MODE","3","ISSU_NEGOTIATION","[chars] [ [chars] ]","There has been a failure in the redundancy mode client.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RED_MODE","3","ISSU_RESET_PEER_IMAGE_COMP","Failed to reset peer image to be compatible","The redundancy process was unable to reset the peer image to be compatible after the standby device came back up in RPR mode. This message is usually seen in conjunction with an ISSU module error message.","Examine the associated ISSU message for the cause of the failure and the recommended action."
"RED_MODE","3","ISSU_SET_BASE_CLIENT_INCOMP","Failed to set base client incompatibility","The redundancy process was unable to set the base client incompatibility.","Check the console log for the name and ID of the incompatible ISSU base clients."
"RED_MODE","3","MSG_DATAPTR","Red Mode Client ([dec]) get msg dataptr failed. Error = [dec]","The redundancy mode ISSU client could not obtain a message data pointer.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu fsm command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RED_MODE","3","MSGGROUP_REG","Red Mode Msg Group ([dec]) for Entity ([dec]) Registration failed ([chars])","The message group for the redundancy mode ISSU entity could not be registered.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu message groups command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RED_MODE","3","MSG_MTU","Red Mode Client ([dec]) get msg mtu failed. Error = [dec]","The redundancy mode ISSU client could not obtain the message size.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu fsm command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RED_MODE","3","MSG_REG","Red Mode msg reg failed: reason [dec]","Messages for the redundancy mode ISSU could not be registered.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu message arguments command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RED_MODE","3","MSG_SEND","Red Mode ISSU client for session ([dec]) failed to send message. Error Code = [chars]","The redundancy mode ISSU client could not send a negotiation message to a peer.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu fsm command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RED_MODE","3","MSGTYPE_REG","Red Mode Msg Type for Entity ([dec]) Registration failed ([chars])","The message type for the redundancy mode ISSU entity could not be registered.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu message types command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RED_MODE","3","NO_DEREGISTER","Could not deregister plugin for redundancy mode [chars]","At system initialization the plugin that describes the capabilities of this redundancy mode could not be deregistered with the redundancy mode client.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RED_MODE","3","RED_MODE_MSG_NOT_OK","Red Mode ISSU msg type ([dec]) is not ok","The redundancy mode ISSU message type has not negotiated correctly.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu message types clientID command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RED_MODE","3","RED_MODE_START_NEGO_FAILED","Red Mode ISSU start nego session failed ([chars])","The redundancy mode ISSU could not start its negotiation process.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu fsm command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RED_MODE","3","RED_MODE_XFROM_FAIL","Red Mode ISSU [chars] transformation failed ([chars])","The transformation operation for the redundancy mode ISSU message has failed.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu fsm and show issue sessions command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RED_MODE","3","SELECT_MODE","The mode change to [dec] was unsuccessful rc = [dec], force = [dec], caller = [dec]","The specified mode change operation did not complete successfully.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information."
"RED_MODE","3","SESSION_REG","Red Mode session for Entity ([dec]) Registration failed ([chars])","The redundancy mode ISSU session could not be registered.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu sessions command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RED_MODE","3","SESSION_UNREG","Red Mode session ([dec]) Un-Registration failed ([chars])","The redundancy mode ISSU session could not be unregistered.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu sessions command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"REDUNDANCY","3","CONFIG_SYNC","%s","A REDUNDANCY config sync error occurred. The details about what was attempted and what went wrong will be printed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"REDUNDANCY","3","UNAVAILABLE","%s %s","An Interprocess Communication (IPC) error occurred. The details about what was attempted and what went wrong will be printed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"REDUNDANCY","3","UNAVAILABLE","%s","A REDUNDANCY Alarm assertions error occurred. The details about what was attempted and what went wrong will be printed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"REDUNDANCY","3","UNAVAILABLE","%s","A REDUNDANCY Finite State Machine (FSM) error occurred. The details about what was attempted and what went wrong will be printed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"REDUNDANCY","3","UNAVAILABLE","%s","A REDUNDANCY Peer Monitor error occurred. The details about what was attempted and what went wrong will be printed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"REDUNDANCY","3","UNAVAILABLE","%s","A REDUNDANCY config sync error occurred. The details about what was attempted and what went wrong will be printed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"REDUNDANCY","3","UNAVAILABLE","%s","A REDUNDANCY error occurred. The details about what was attempted and what went wrong will be printed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"REDUNDANCY","3","UNAVAILABLE","%s failed with error code [ %s ]","An ISSU related REDUNDANCY error occurred. The details about what was attempted and what went wrong will be printed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"REDUNDANCY","3","UNAVAILABLE","RP switchover (%s)","A REDUNDANCY switchover has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"REDUNDANCY","3","UNAVAILABLE","Standby processor fault (%s)","The standby processor is no longer available.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"REDUNDANCY","3","UNAVAILABLE","WARNING, nonsymetrical configuration: Active has %dK Standby has %dK","The redundant RPs have different memory configurations.","The configuation is allowed but discouraged."
"REDUNDANCY","4","PEER_DID_NOT_RESPOND","Resetting peer [chars] because it did not respond to verification of HA role.","The platform uses high availability (HA) hardware lines to perform HA role negotiation during the system boot time. The standby controller card verifies its role as the standby with the active controller card through the MBUS. If the active controller card does not respond, it is reset as it is either nonresponsive (hung) or is running an earlier version of Cisco IOS software.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"REDUNDANCY","4","RELOADING_STANDBY","Reloading the Standby [chars]","The active system has sent a reload IPC request to the standby peer. If the reload is not successful, the standby peer will be power cycled rather than reloaded.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"REDUNDANCY","5","UNAVAILABLE","%s (%s%s(%d))","A REDUNDANCY Peer Monitor event occurred and reported. The report should help to find out the reason for a switch-over.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"REDUNDANCY","6","STANDBY_HAS_RELOADED","The Standby [chars] has reloaded; reason: [chars]","The standby peer reloaded itself to correct a configuration mismatch between the active system and the standby peer. The standby peer detected that it is missing the configuration for a line card. This situation probably occurred because the standby peer was reloaded before the new card was inserted.","No action is required."
"REDUNDANCY","6","SWITCHOVERTIME","Time taken to switchover = [dec] milliseconds","This message displays the time elapsed for the standby peer to become active following a failure of the existing active system.","No action is required."
"REDUNDANCY_UTILS","3","INVALID_UNIT_DESIGNATION","An invalid redundancy designation ([chars]) has been detected.","The redundancy utility assigns each system a unit designation of either active unit, standby unit, or other unit. This designation was found to be invalid in the run-time module associated with the system traceback message. This condition most likely occurred because of a software error. The message text provides more information on the specific cause of the error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"REGISTRY","2","REG_FLAG_DEADLOCK","Registry call to [chars] timed out due to deadlock","When a remote registry is not serviced within 25 seconds, the remote process (and presumably the entire system) is deadlocked. This message is printed when the deadlock is broken by a timeout.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"REGISTRY","2","REG_PARSE_ERROR","[chars]: Could not parse notification [chars] : error/no. of items = [dec]","The registry library is unable to parse a notification that was received from a name server. This condition could exist for several reasons: - There is a bug in the sscanf function. - The notification block is corrupted. - The pathname published to the name server is invalid.This issue is serious and affects interprocess communications.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"REGISTRY","3","FASTCASE_OUT_OF_BOUNDS","Attempt made in [chars] to register with out of bounds key.","In FASTCASE registry, the key must be smaller than the size specified when the registry was created. An attempt was made to register with a key that is out of bounds.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"REGISTRY","3","REG_FLAG_ERR","Invalid combination of registry flag and scheduler control : [chars]","Process blocking has been disabled using either the raise_interrupt_level or the assign_blocking_disabled process. As a result of this action, a remote registry that contains the reg_flag_data_safe or reg_flag_peer flag has been invoked.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"REGISTRY","3","REG_SUSPEND","Registry of type SUSPEND called when suspends are not allowed.","Process blocking has been disabled using either the raise_interrupt_level or the assign_blocking_disabled process. As a result of this action, a remote registry of the suspend type has been invoked.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"REGISTRY","3","REG_XDR","[chars]","An error occurred while processing a parameter to a remote (interprocess) registry call.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"REGISTRY","3","SEQ_LIST_OVERWRITE","Attempt made to overwrite a set sequence function (%s)","A single function can be set as a callback for a specified sequence number for a sequenced list registry. An attempt to set a new callback failed because a callback function has already been set for this sequence number.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"REMOTE_OIR_ISSU","3","BUFFER","Cat6K Remote OIR ISSU client failed to a buffer for message, error %d","The remote OIR ISSU client failed to get a buffer for building a negotiation message. As a result, the client cannot send a negotiation message and the standby unit cannot be brought up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"REMOTE_OIR_ISSU","3","CAPABILITY","Cat6K Remote OIR ISSU client %s","The remote OIR ISSU client detected an error during capability negotiation. As a result, there is a mismatch in the client capability between the active and standby unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"REMOTE_OIR_ISSU","3","INIT","Cat6K Remote OIR ISSU client initialization failed at %s, error %s","The remote OIR ISSU client could not be initialized. This condition will cause a catastrophic failure when an ISSU upgrade or downgrade is performed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"REMOTE_OIR_ISSU","3","MSG_NOT_OK","Cat6K Remote OIR ISSU client message %d is not compatible","The remote OIR ISSU client received an incompatible message from the peer unit. The message cannot be processed by this unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"REMOTE_OIR_ISSU","3","MSG_SIZE","Cat6K Remote OIR ISSU client failed to get the message size for message %d","The remote OIR ISSU client was unable to calculate the message size for the message specified. The client will be unable to send the message to the standby unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"REMOTE_OIR_ISSU","3","POLICY","Cat6K Remote OIR ISSU client message type %d is %s","The remote OIR ISSU client received a message type that it does not support. A policy is applied to make the session compatible.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show issu session commands and your pertinent troubleshooting logs."
"REMOTE_OIR_ISSU","3","SEND_FAILED","Cat6K Remote OIR ISSU client failed to send a negotiation message, error %d","The remote OIR ISSU client could not send a session negotiation message to the peer. As a result, the standby unit cannot be brought up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"REMOTE_OIR_ISSU","3","SESSION","Cat6K Remote OIR ISSU client %s","The remote OIR ISSU client detected an error during a session negotiation with the peer unit. As a result, the standby unit cannot be brought up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"REMOTE_OIR_ISSU","3","TRANSFORM","Cat6K Remote OIR ISSU client %s transform failed, error %s","The remote OIR ISSU client could not transform the message. If the transmit transformation failed, the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, the checkpoint message cannot be applied on the standby unit. In either case, the OIR state of the bay will not be identical with the active unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"REP","4","LINKSTATUS","%s (segment %d) is %s","The Resilient Ethernet Protocol (REP) link status has changed. If the status changed to nonoperational, a reason is displayed.","No action is required."
"REP","5","PREEMPTIONFAIL","can not perform preemption on segment %d due to %s","A Resilient Ethernet Protocol (REP) preempt operation failed. The failure could be caused by specifying an invalid port ID or neighbor number with the rep preempt block port command or by configuring the rep preempt block port preferred command while no REP port is configured with a preferred flag.","Correct the configuration and run REP manual preemption on the primary edge port by entering the rep preempt segment command."
"REPP","5","UNAVAILABLE","Connected to server","REPP Layer connected to REPP server","LOG_STD_NO_ACTION"
"REPP","5","UNAVAILABLE","Disconnected from server","REPP Layer dis-connected from REPP server","LOG_STD_NO_ACTION"
"REP_ISSU","3","BUFFER","REP ISSU client failed to get buffer for message, error %d","The Resilient Ethernet Protocol (REP) ISSU client was unable to get buffer space for building a negotiation message. As a result, it cannot send the negotiation message to the standby unit and the standby unit cannot be brought up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"REP_ISSU","3","CAPABILITY","REP ISSU client %s","The REP ISSU client detected an error during capability negotiation. As a result, there is a mismatch in the client capability between the active and standby unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"REP_ISSU","3","INIT","REP ISSU client initialization failed at %s, error %s","The REP ISSU client could not be initialized. This condition will cause a catastrophic failure when an ISSU upgrade or downgrade is performed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"REP_ISSU","3","MSG_NOT_OK","REP ISSU client message %d is not compatible","The REP ISSU client received an incompatible message from the peer unit. The message cannot be processed by this unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"REP_ISSU","3","MSG_SIZE","REP ISSU client failed to get the message size for message %d","The REP ISSU client was unable to calculate the message size for the message specified. The REP ISSU client will be unable to send the message to the standby unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"REP_ISSU","3","POLICY","REP ISSU client message type %d is %s","The REP ISSU client received a message type that it does not support. A policy is applied to make the session compatible.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show issu session commands and your pertinent troubleshooting logs."
"REP_ISSU","3","SEND_FAILED","REP ISSU client failed to send a negotiation message, error %d","The REP ISSU client could not send a session negotiation message to the peer. As a result, the standby unit cannot be brought up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"REP_ISSU","3","SESSION","REP ISSU client %s","The REP ISSU client detected an error during a session negotiation with the peer unit. As a result, the standby unit cannot be brought up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"REP_ISSU","3","SESSION_UNREGISTRY","REP ISSU client failed to unregister session information. Error: %d (%s)","The REP ISSU client was unable to unregister session information.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"REP_ISSU","3","TRANSFORM","REP ISSU client %s transform failed, error %s","The REP ISSU client could not transform the message. If the transmit transformation failed, the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, the checkpoint message cannot be applied on the standby unit. In either case, the port manager state will not be identical with the active unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"RFPROXY","2","INIT","Initialization failed","The RF Proxy subsystem failed during its initialization","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"RFPROXY","2","NOMEM","No memory available","The RF Proxy subsystem could not obtain the memory it needed","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"RFPROXY","2","RPC","RPC message failure","The RF Proxy could not send an RPC message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"RESETMGR","3","NOMEM","Failed to allocate memory to add ID (%d) to table","The reset manager was unable to allocate memory to add the unique ID and process name to its table. If this process is restarted on the active system, the standby system might not be reset due to this error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RESETMGR","3","RESET","Reset Manager has reset the system due to '%s' process restart","The standby system is being forced to reset by the reset manager. The reset manager stores a set of IDs, each of which uniquely identifies a process on the system. If one of these monitored processes is restarted, the standby unit will be reset so that the versioning infrastructure can renegotiate. This is not a software fault.","No action is required."
"RESETMGR","3","RESET_UNKNOWN","A restarted process could not be identified by its Job ID, the Reset Manager has reset the Standby system.","The reset manager stores a set of IDs, each of which uniquely identifies a process on the system. A process was restarted but it could not be uniquely identified by its job ID. Because it cannot be determined whether the restarted process was being monitored by the reset manager, the standby system is being reset. This is probably due to a software fault on the system.","No action is required."
"RESETMGR","3","SYSMGR_JOBID_LOOKUP","Failed to get the job ID of the Reset Manger (IOS blob) from SysMgr","The reset manager was unable to get its job ID from the system manager. The reset manager cannot function without this information and will suspend any further initialization.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RESETMGR","4","SYSMGR_PROCNAME_LOOKUP","Failed to lookup process name from SysMgr, job ID = %d","The reset manager was unable to get the name of the process with the specified job ID from the system manager. Although this is a system manager error, the system can continue to operate normally because the process name is used only for reference purposes.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RESOURCE_MON","1","UNAVAILABLE","%s","The specific message text is supplied by the Resource Monitor software. This indicates an initialization failure. When this occurs, the Resource Monitor subsystem is not operational.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RESOURCE_MON","1","UNAVAILABLE","%s","The specific message text is supplied by the Resource Monitor software. This indicates that internal data was corrupted due to a software error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RF","1","UNAVAILABLE","%s","An automatic switch of activity occurred when it had been disabled.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RF","3","CANNOT_SWITCH","Cannot switchover; the peer Route Processor (RP) is not available","Cannot initiate switchover. The peer RP is not available.","This is an informational message only. No action is required."
"RF","3","CANT_GET_VERSION","Cannot get version info from peer Route Processor (RP); the RP software is incompatable.","The standby RP cannot get version information from the peer RP. The likely cause is incompatible software.","Ensure that the same software image is running on both RPs."
"RF","3","FAILED_SET_RED_MODE","ACTIVE failed to set redundancy mode. STANDBY has selected mode but unable to get confirmation from ACTIVE.","Under normal conditions, the standby RP selects the redundancy mode and sends its decision to the active RP. The active RP uses it to determine the system mode and returns the final decision on the mode to the standby RP. This system message indicates that the exchange has failed, and the standby RP does not have the right redundancy mode to proceed.","Allow the standby RP to reset once. If the problem persists, verify that all modules are working properly."
"RF","3","NEGOTIATED_ROLE_MISMATCH","Negotiated Role mismatch; The Route Processor (RP) believes it should be ACTIVE while the System Processor (SP) believes the RP should be STANDBY... or vice versa.","The RP negotiates its role (active or standby) at boot time. If the other RP is running an image that does not contain role negotiation code, then the role that is negotiated may not be valid. When this occurs, the RP detecting a mismatch between the role specified by the SP and the role negotiated will be rebooted.","Ensure that the same software image is running on both RPs. Make sure that neither RP is running the bootloader image."
"RF","3","NON_HA_SWITCHOVER","The SP switchover was NOT stateful. To support SSO on the RP, the SP must be configured with HA enabled.","The switch processor switchover that occurred was not stateful. Stateful switchover (SSO) mode on the route processor requires the switch processor to run with high availability enabled to ensure that appropriate state is synchronized between the switch processors and that there is sufficient state information on the new active switch processor to support the switchover of the route processor while in stateful switchover mode. Because there is insufficient state to support a route processor switchover in stateful switchover mode, the recovery is to reset the route processor and reboot it.","Configure the SP to enable HA. If HA is enabled, it is possible that resource exhaustion (such as memory) might have caused this non-HA switchover. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RF","3","NOTIF_TID","Notification timer extended for the wrong client, cur-client=%d, req-client=%d","The current redundancy facility (RF) client attempted to extend the RF notification timer using a client ID other than its own. This is an internal software error. The message text on the console or in the system log contains error details such as the current client ID number and the requested client ID number.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show redundancy history commands and your pertinent troubleshooting logs."
"RF","3","PEER_RP_RELOAD","The peer Route Processor (RP) is being reset because [chars]","This message provides the reason that the peer RP reset. The peer RP resets in an attempt to recover from an indeterminate state.","If the condition persists after the reset, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RF","3","VERSION_MISMATCH","Version Info mismatch; Not running same version of software on each Route Processor (RP). Cannot run in SSO mode; will go to RPR mode instead.","Each RP must be running the same version of software. The version check indicates that there is a version mismatch. As a result, the RPs cannot run in SSO (hot-standby) mode and operation will regress to RPR mode.","Ensure that both RPs are running the same software image."
"RF","3","WAKEUP_STANDBY_NOT_SEEN","Active-Standby RP Handshake Error.  The Standby RP did not receive a WAKEUP_STANDBY message from the Active RP during the early initialization phase on the Standby RP.","As part of the early initialization phase, the standby RP requests that the active RP notify it when the active RP is ready to support the standby RP. The active RP has failed to wake the standby RP. The active RP may have failed during the standby RP's early initialization phase or some other error has prevented the active RP from completing this handshake.","The standby RP will be restarted. If the problem persists, restart the system."
"RF","4","MEMORY_SIZE_MISMATCH","Memory Size mismatch: The redundant Route Processors have different memory configurations. To support the High Availability feature, it is recommended that both RPs have the same memory configurations.","To support the high availability feature, it is recommended that both redundant route processors have the same memory configuration.","Install the same amount of memory on both RPs."
"RF","5","RF_RELOAD","%s. Reason: %s","The current redundancy facility (RF) has invoked a reload.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show redundancy history reload commands and your pertinent troubleshooting logs."
"RF","5","RF_TERMINAL_STATE","Terminal state reached for (%s)","The current redundancy facility (RF) has reached a terminal state for the operating mode.","This is a notification message only. No action is required."
"RF","5","SEND_FAIL","RF client progression send failure for reason (%s)","The current redundancy facility (RF) failed to send a client progression to the standby client.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show redundancy history commands and your pertinent troubleshooting logs."
"RF","6","CONS_MSG","Console Message from [chars] RP: [chars]","This message is a console message from the peer RP.","This is an informational message only. No action is required."
"RF","6","NEGOTIATED_RED_MODE","Negotiated Redundancy MODE is [chars]","The negotiated redundancy mode may be either SSO or RPR.","This is an informational message only. No action is required."
"RF","6","STANDBY_READY","The Standby RP has reached HOT-STANDBY state and is now ready for stateful switchover.","The standby RP has reached the hot-standby state and is now ready to take over operation in the event that the active RP should fail.","No action is required."
"RF","7","KPA_WARN","RF KPA messages have not been heard for [dec] seconds","RF keepalive messages have not been sent from the peer. This message is posted after every third KPA timer expiry.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFPROXY","2","UNAVAILABLE","Initialization failed","The RF Proxy subsystem failed during its initialization","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFPROXY","2","UNAVAILABLE","No memory available","The RF Proxy subsystem could not obtain the memory it needed","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFPROXY","2","UNAVAILABLE","RPC message failure","The RF Proxy could not send an RPC message.RF_ISSU MessagesThis sections contains redundancy facility (RF) in-service software upgrade (ISSU) messages.RF_ISSU-3Error Message    %RF_ISSU-3-CAPENTRY_REG: RF Cap Entry ([dec]) for Entity ([dec]) Registration failed Explanation    A capability entry could not be registered for the RF ISSU.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu capability entries command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RF_ISSU","3","CAPGROUP_REG","RF Cap Group ([dec]) for Entity ([dec]) Registration failed","A capability group could not be registered for the RF ISSU.","Copy the message exactly as it appears on the console or in the system log. Enter the show capability groups command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RF_ISSU","3","CAP_REG","RF cap reg failed: reason [dec]","The capabilities of the RF ISSU could not be registered.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu capability arguments command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RF_ISSU","3","CAPTYPE_REG","RF Cap Type for Entity ([dec]) Registration failed","A capability type could not be registered for the RF ISSU.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu capability types command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RF_ISSU","3","CLIENT_REG","RF Client ([dec]) Registration failed","The RF ISSU client could not be registered.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu clients command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RF_ISSU","3","CLIENT_REG_FAILED","RF ISSU client ([dec]) Client registration failed. [chars]","The RF ISSU client could not be registered during system initialization.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu clients command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RF_ISSU","3","ENTITY_REG","RF Entity ([dec]) Registration failed","The RF ISSU entity could not be registered.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu entities command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RF_ISSU","3","GET_BUFFER","RF ISSU session ([dec]) failed to get buffer","The RF ISSU failed to get a buffer.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu fsm command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RF_ISSU","3","MSG_DATAPTR","RF Client ([dec]) get msg dataptr failed. Error = [dec]","The RF ISSU client could not obtain a message data pointer.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu fsm command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RF_ISSU","3","MSGGROUP_REG","RF Msg Group ([dec]) for Entity ([dec]) Registration failed","The message group for the RF ISSU could not be registered.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu message groups command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RF_ISSU","3","MSG_MTU","RF Client ([dec]) get msg mtu failed. Error = [dec]","The RF ISSU client could not obtain message size.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu fsm command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RF_ISSU","3","MSG_REG","RF msg reg failed: reason [dec]","Messages for the RF ISSU could not be registered.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu message arguments command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RF_ISSU","3","MSG_SEND","RF ISSU client for session ([dec]) failed to send message","The RF ISSU client could not send a negotiation message to a peer.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu fsm command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RF_ISSU","3","MSGTYPE_REG","RF Msg Type for Entity ([dec]) Registration failed","The message type for the RF ISSU could not be registered.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu message types command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RF_ISSU","3","RF_MSG_NOT_OK","RF ISSU msg type ([dec]) is not ok","RF ISSU message type has not negotiated correctly.","Copy the message exactly as it appears on the console or in the system log. Enter the show message types Client_ID command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RF_ISSU","3","SESSION_REG","RF session for Entity ([dec]) Registration failed","The RF ISSU session could not be registered.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu sessions command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RF_ISSU","3","SESSION_UNREG","RF session ([dec]) Un-Registration failed","The RF ISSU session could not be unregistered.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu sessions command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","CAPENTRY_REG","RFS Cap Entry ([dec]) for Entity ([dec]) Registration failed","RFS ISSU cap entry registration has failed.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu capability entries command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","CAPGROUP_REG","RFS Cap Group ([dec]) for Entity ([dec]) Registration failed","RFS ISSU cap group registration has failed.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu capability groups command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","CAPTYPE_REG","RFS Cap Type for Entity ([dec]) Registration failed","RFS ISSU cap type registration has failed.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu capability types command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","CLIENT_REG","RFS Client ([dec]) Registration failed","RFS ISSU client registration has failed.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu clients command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","CLIENT_SESSION_REG","RFS ISSU client shared msg session for entity ([dec]) registration failed","RFS ISSU client shared message session registration has failed.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu sessions command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","CLIENT_SESSION_UNREG","RFS session ([dec]) Un-Registration failed","RFS ISSU client session unregistration has failed.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu sessions command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","CREATE_ACTIVE_PORT","RFS create active port ([chars]) failed","RFS ISSU active port creation has failed.","Copy the message exactly as it appears on the console or in the system log. Enter the show ipc port command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","CREATE_CLIENT_PORT","RFS create client port (%s) failed","The remote file system (RFS) ISSU client was unable to create a client port.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show ipc port commands and your pertinent troubleshooting logs."
"RFS","3","CREATE_SERVER_PORT","RFS create server port (%s) failed","The RFS ISSU client was unable to create a server port.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show ipc port commands and your pertinent troubleshooting logs."
"RFS","3","CREATE_STANDBY_PORT","RFS create standby port ([chars]) failed","RFS ISSU standby port creation has failed.","Copy the message exactly as it appears on the console or in the system log. Enter the show ipc port command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","ENTITY_REG","RFS Entity ([dec]) Registration failed","RFS ISSU entity registration has failed.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu entities command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","IPC_GET_BUFFER","RFS issu ipc get buffer failed","RFS ISSU IPC get buffer has failed.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","LOCATE_PORT","RFS locates port ([chars]) failed","RFS ISSU port location has failed.","Copy the message exactly as it appears on the console or in the system log. Enter the show ipc port command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","MSGGROUP_REG","RFS Msg Group ([dec]) for Entity ([dec]) Registration failed","RFS ISSU message group registration has failed.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu message groups command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","MSG_MTU","RFS Client ([dec]) get msg mtu failed. Error = [dec]","RFS ISSU client get message MTU has failed.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu fsm command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","MSG_RCV","RFS Client ([dec]) receive msg failed. Error = [dec]","RFS ISSU client receive message has failed.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","MSGTYPE_REG","RFS Msg Type for Entity ([dec]) Registration failed","RFS ISSU message type registration has failed.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu message types command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","MSG_XMIT","RFS Client ([dec]) send msg failed. Error = [dec]","RFS ISSU client send message has failed.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","NEGO_COMP","RFS nego is not compatible ([dec])","RFS ISSU start shared negotiation session has failed.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu sessions command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","NEGO_SESSION_REG","RFS nego session for Entity ([dec]) Registration failed","RFS ISSU shared negotiation session registration has failed.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu sessions command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","NEGO_SESSION_UNREG","RFS session ([dec]) Un-Registration failed","RFS ISSU shared negotiation session unregistration failed.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu sessions command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","OPEN_ACTIVE_PORT","RFS open active port ([chars]) failed","The RFS ISSU client was unable to open an active port.","Copy the message exactly as it appears on the console or in the system log. Enter the show ipc port command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","OPEN_CLIENT_PORT","RFS open client port (%s) failed","The RFS ISSU client was unable to open a client port.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show ipc port commands and your pertinent troubleshooting logs."
"RFS","3","OPEN_SERVER_PORT","RFS open server port (%s) failed","The RFS ISSU client was unable to open a server port.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show ipc port commands and your pertinent troubleshooting logs."
"RFS","3","OPEN_STANDBY_PORT","RFS open standby port ([chars]) failed","The RFS ISSU client was unable to open a standby port.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu sessions command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","RECEIVE_NEGO_FAILED","RFS receive nego message ([dec]) failed","RFS ISSU receive negotiation message has failed.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu sessions command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","RECEIVE_NEGO_NOT_DONE","RFS receive nego message is not done ([dec])","RFS ISSU receive negotiation message is not done.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu sessions command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","REG_PORT","RFS reg port ([dec]) failed","RFS ISSU register port has failed.","Copy the message exactly as it appears on the console or in the system log. Enter the show ipc port command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","RFS_BOOL_CREATE_ERR","%s.","The RFS redundancy facility (RF) client detected an error when creating a watched boolean.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","RFS_ISSU_NEGO_PROCESS","RFS create rfs_issu_start_port watch boolean failed","RFS ISSU create negotiation process has failed.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","RFS_ISSU_START_PORT","RFS create rfs_issu_start_port watch boolean failed","The RFS ISSU client was unable to create anrfs_issu_start_port watched boolean.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","RFS_ISSU_START_SESSION","RFS create rfs_issu_start_session watch boolean failed","The RFS ISSU client was unable to create anrfs_issu_start_session watched boolean.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","RFS_RF_PROG_ERR","%s %d.","The RFS RF client detected an error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","RFS_RF_PROG_NOT_SENT_ERR","%s.","The RFS RF client detected an error when sending a client progression.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","SEND_NEGO_MESSAGE","RFS send nego message ([dec]) failed","RFS ISSU send negotiation message has failed.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu sessions command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","START_NEGO_SESSION","RFS start shared nego session ([dec]) failed: [dec]","RFS ISSU start shared negotiation session has failed.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu sessions command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RFS","3","UNREG_ENTITY","RFS ISSU Client unreg entity failed.","The RFS ISSU client unregister entity has failed.","Copy the message exactly as it appears on the console or in the system log. Enter the show issu command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RF_ISSU","3","INVALID_SESSION","RF ISSU client does not have a valid registered session.","The redundancy facility (RF) ISSU client does not have a valid registered session.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"RF_ISSU","3","RF_CAP_INVALID_SIZE","RF ISSU client capability list is empty.","The RF ISSU capability list is empty, which is an invalid condition.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu capability entries commands and your pertinent troubleshooting logs."
"RF_ISSU","3","RF_CAP_RESULT_INCOMP","RF ISSU client capability exchange result incompatible.","Based on the results of the capability exchange, the RF ISSU client is not compatible with the peer.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"RIP","3","UNAVAILABLE","Unable to open socket","The requested operation could not be accomplished because of a low memory condition.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"RITE","5","ACTIVATE","Activated IP traffic export on interface [chars]","IP traffic export has been enabled on the specified interface.","No action is required."
"RITE","5","DEACTIVATE","Deactivated IP traffic export on interface [chars]","IP traffic export has been disabled on the specified interface.","No action is required."
"RITE","5","MODIFIED","Changed IP traffic export outbound interface from [chars] to [chars]","The outbound interface for IP traffic export has been changed.","No action is required."
"RLM","3","UNAVAILABLE","rlm %d: %s%s.","RLM initialization operation fails.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RLM","4","UNAVAILABLE","rlm %d: %s%s.","A warning is given out for a particular RLM link.","LOG_STD_DBG_ACTION"
"RM","3","UNAVAILABLE","%s: RG-info conversion failed (%u).","An internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RM","3","UNAVAILABLE","Bad state rg %s: %d","An internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RM","3","UNAVAILABLE","Memory boundary violation","An internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RM","3","UNAVAILABLE","No response-code from local RM","An internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RM","3","UNAVAILABLE","Out of buffers in RM event buffer queue","An internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RM","3","UNAVAILABLE","Unexpected Call on %s. Current state is %d.","A call came in on a line where we think we still have an active call.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RM","3","UNAVAILABLE","Uninitialized value being used","An internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RM","3","UNAVAILABLE","Unknown Accounting type (%d), flag (%d).","Get either invalid accounting type or flag","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RM","3","UNAVAILABLE","Wavl error","An internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RLC_ISSU_PROCESS","3","NULL_RED_CONFIG","Redundancy configuration can not be NULL.","Redundancy configuration can not be NULL.","Copy the error and send it to TAC. TAC team can contact ISSU infrastruture team to check why redundancy configuration is NULL"
"RLC_ISSU_PROCESS","3","NULL_RED_CONFIG","Redundancy configuration can not be NULL.","Redundancy configuration can not be NULL.","Copy the error and send it to TAC.TAC team can contact ISSU infrastruture team to check why redundancy configuration is NULL"
"RLC_ISSU_PROCESS","3","RLC_ISSU_ERR","%s","An error occurred while running the Redundanct LC ISSU process","Copy the error and send it to TAC. TAC team can contact ISSU infrastruture team to check why this error occurs"
"RLC_ISSU_PROCESS","3","RLC_ISSU_ERR","%s","An error occurred while running the Redundanct LC ISSU process","Copy the error and send it to TAC.TAC team can contact ISSU infrastruture team to check why this error occurs"
"RLC_ISSU_PROCESS","3","RLC_ISSU_MLC_FSM_ERR","error processing %s event in %s state for LC %s, terminating process","internal error in RLC ISSU event processing","Copy the error and send it to TAC. TAC team can contact ISSU infrastruture team to check why this error occurs"
"RLC_ISSU_PROCESS","3","RLC_ISSU_MLC_FSM_ERR","error processing %s event in %s state for LC %s, terminating process","internal error in RLC ISSU event processing","Copy the error and send it to TAC.TAC team can contact ISSU infrastruture team to check why this error occurs"
"RLC_ISSU_PROCESS","3","RLC_ISSU_N1_PLC_FSM_ERR","error processing %s event in %s state for LC %s, terminating process","internal error in RLC ISSU event processing","Copy the error and send it to TAC. TAC team can contact ISSU infrastruture team to check why this error occurs"
"RLC_ISSU_PROCESS","3","RLC_ISSU_N1_PLC_FSM_ERR","error processing %s event in %s state for LC %s, terminating process","internal error in RLC ISSU event processing","Copy the error and send it to TAC.TAC team can contact ISSU infrastruture team to check why this error occurs"
"RLC_ISSU_PROCESS","3","RLC_ISSU_N1_PLC_PSLC_ERR","prepareversion error, secondary LC not standby ready for LC %s","the secondary LC failed to become standby ready","Copy the error and send it to TAC. TAC team can contact ISSU infrastruture team to check why this error occurs"
"RLC_ISSU_PROCESS","3","RLC_ISSU_N1_PLC_PSLC_ERR","prepareversion error, secondary LC not standby ready for LC %s","the secondary LC failed to become standby ready","Copy the error and send it to TAC.TAC team can contact ISSU infrastruture team to check why this error occurs"
"RLC_ISSU_PROCESS","3","RLC_ISSU_N1_PLC_WPLC_ERR","runversion error, primary LC %s not standby ready","the primary LC is not ready for switchover","Copy the error and send it to TAC. TAC team can contact ISSU infrastruture team to check why this error occurs"
"RLC_ISSU_PROCESS","3","RLC_ISSU_N1_PLC_WPLC_ERR","runversion error, primary LC %s not standby ready","the primary LC is not ready for switchover","Copy the error and send it to TAC.TAC team can contact ISSU infrastruture team to check why this error occurs"
"RLC_ISSU_PROCESS","3","RLC_ISSU_RLD_PLC_FSM_ERR","error processing %s event in %s state for LC idx %s, terminating process","internal error in RLC ISSU event processing","Copy the error and send it to TAC. TAC team can contact ISSU infrastruture team to check why this error occurs"
"RLC_ISSU_PROCESS","3","RLC_ISSU_RLD_PLC_FSM_ERR","error processing %s event in %s state for LC idx %s, terminating process","internal error in RLC ISSU event processing","Copy the error and send it to TAC.TAC team can contact ISSU infrastruture team to check why this error occurs"
"RLC_ISSU_PROCESS","4","LCRPVERSION","Linecard %s and RP have different image versions","Linecard has different version of image than RP","Use RLC ISSU commands to change these LCs' images to same version as RP"
"RLC_ISSU_PROCESS","4","RLC_ISSU_IMAGE_ERR","error loading LC image for LC %s","internal error in loading linecard image","Copy the error and send it to TAC. TAC team can contact ISSU infrastruture team to check why this error occurs"
"RLC_ISSU_PROCESS","4","RLC_ISSU_IMAGE_ERR","error loading LC image for LC %s","internal error in loading linecard image","Copy the error and send it to TAC.TAC team can contact ISSU infrastruture team to check why this error occurs"
"RLC_ISSU_PROCESS","4","RLC_ISSU_NOT_COMPLETED_WARNING","LC ISSU is not finished, please issue the next commands to complete LC ISSU","The steps to complete LC ISSU has not been fully carried out by the operator. The system is left in an intermediate state where some linecards have been upgraded and others have not. This message is to remind he operator that a significant amount of time has passed waiting for he operator to enter the next LC ISSU command.","Enter the next LC ISSU command to continue with LC ISSU, which includes commands to perform the operations of prepareversion, loadversion, runversion, acceptversion, commitversion, or abortversion"
"RLC_ISSU_PROCESS_CLI","3","NULL_RED_CONFIG","Redundancy configuration can not be NULL.","Redundancy configuration can not be NULL.","Copy the error and send it to TAC. TAC team can contact ISSU infrastruture team to check why redundancy configuration is NULL"
"RLC_ISSU_PROCESS_CLI","3","NULL_SLOTINDEX","slotindex can not be NULL.","slotindex can not be NULL.","Copy the error and send it to TAC. TAC team can contact ISSU infrastruture team to check why slotindex is NULL"
"RLC_ISSU_PROCESS_CLI","3","NULL_SLOTINDEX","slotindex can not be NULL.","slotindex can not be NULL.","Copy the error and send it to TAC.TAC team can contact ISSU infrastruture team to check why slotindex is NULL"
"RLC_ISSU_PROCESS_CLI","3","RLC_ISSU_ERR","%s","An error occurred while executing Redundanct LC ISSU CLI","Copy the error and send it to TAC. TAC team can contact ISSU infrastruture team to check why this error occurs"
"RLC_ISSU_PROCESS_CLI","3","RLC_ISSU_ERR","%s","An error occurred while executing Redundanct LC ISSU CLI","Copy the error and send it to TAC.TAC team can contact ISSU infrastruture team to check why this error occurs"
"RMON","5","HCFALLINGTRAP","Falling trap is generated because the value of %s has fallen below the falling-threshold hc value %llu","A falling trap was generated. The value of the specified MIB object fell below the falling threshold value as configured by the rmon hc-alarms command for the specified object.","Take the appropriate action on the specified MIB object."
"RMON","5","HCRISINGTRAP","Rising trap is generated because the value of %s exceeded the rising-threshold hc value %llu","A rising trap was generated. The value of the specified MIB object exceeded the rising threshold value as configured by the rmon hc-alarms command for the specified object.","Take the appropriate action on the specified MIB object."
"ROLLBACK_ISSU","2","GET_BUFFER","Rollback ISSU client failed to get buffer for message. Error: [dec] ([chars])","The Rollback ISSU client failed to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","Issue the show logging and show checkpoint client command to gather data that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"ROLLBACK_ISSU","2","INIT","Rollback ISSU client initialization failed to [chars]. Error: [dec] ([chars])","The Rollback ISSU client could not be initialized. This initialization failure must be addressed before in-service software upgrade or downgrade can be performed successfully. If you do not address this failure, there will be downtime during software upgrade or downgrade.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"ROLLBACK_ISSU","2","SEND_NEGO_FAILED","Rollback ISSU client failed to send negotiation message. Error: [dec] ([chars])","The Rollback ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","Issue the show logging and show checkpoint client command to gather data that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"ROLLBACK_ISSU","2","SESSION_NEGO_FAIL_START","Failed to start Rollback ISSU session negotiation. Error: [dec] ([chars])","The Rollback ISSU client failed to start session negotition. If a problem occurs with the ISSU session start, the standby device cannot be brought up properly.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"ROLLBACK_ISSU","2","SESSION_REGISTRY","Rollback ISSU client failed to register session information. Error: [dec] ([chars])","The Rollback ISSU client failed to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly.","Issue the show issu capability entries and show issu session and show issu negotiated capability command to gather data that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"ROLLBACK_ISSU","3","INVALID_SESSION","Rollback ISSU client does not have a valid registered session.","The Rollback ISSU client does not have a valid registered session.","Issue the show issu capability entries and show issu session and show issu negotiated capability command to gather data that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"ROLLBACK_ISSU","3","MSG_NOT_OK","Rollback ISSU client 'Message Type [dec]' is not compatible","The Rollback ISSU client received an incompatible message from the peer device. The message cannot be processed.","Issue the show issu message group and show issu session and show issu negotiated version command to gather data that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"ROLLBACK_ISSU","3","MSG_SIZE","Rollback ISSU client failed to get the MTU for Message Type [dec].Error: [dec] ([chars])","The Rollback ISSU client failed to calculate the MTU for the specified message. The Rollback ISSU client is not able to send the message to the standby device.","Issue the show issu message group and show issu session and show issu negotiated version command to gather data that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"ROLLBACK_ISSU","3","SESSION_UNREGISTRY","Rollback ISSU client failed to unregister session information. Error: [dec] ([chars])","The Rollback ISSU client failed to unregister session information.","Issue the show issu capability entries and show issu session and show issu negotiated capability command to gather data that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"ROLLBACK_ISSU","3","TRANSFORM_FAIL","Rollback ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] ([chars])","The Rollback ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In both cases, the Rollback state between the active device and the standby device is not identical.","Issue the show issu session and show issu negotiated version command to gather data that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"ROUTEMAP","4","BADTRACKOBJECTTYPE","can't track this type of object","Route maps only support STATE type track objects. This object is not a STATE object.","Reconfigure the track object to make it a STATE object."
"ROUTEMAP_IPC","2","UNAVAILABLE","Alloc fail for route-map ipc buffer","Unable to malloc a buffer to send route-map configuration down to linecards.","Enter a show chunks command and report the output, along with this error message, to your technical support representative."
"ROUTEMAP_IPC","2","UNAVAILABLE","The length of route map name tag is too long","The length of route map name tag is too long for IPC. The receiver has a 256 character long limit on route map name tag","Use a route map name tag with the length of 256 or less characters"
"RPA","3","UNAVAILABLE","%s","This message type is created for all those messages which have simple ASCII text and does not take any parameter. Message tells what the problem is.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RPA","3","UNAVAILABLE","CAS Entry does not exist for slot: %d, ctrl:%d, channel:%d","CAS entry does not exist for the given controller and channel.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RPA","3","UNAVAILABLE","Unknown message type %d enqueued to RPA CAS Process","A message type which is not known to RPA CAS process is enqueued to it's queue.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RPF","4","UNAVAILABLE","Error deleting an rpf entry from the multicast rpf tree","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RPF","4","UNAVAILABLE","Error inserting a new rpf entry into the multicast rpf tree","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RPM","3","UNAVAILABLE","Can't allocate MAC address for interface %u/%u","MAC address allocation failed because of an incorrect slot and port combination, which exceeds the maximum available hardware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RPM","4","UNAVAILABLE","Corrupt or missing MAC address cookie using random base %e","The contents of MAC address EEPROM are invalid. The system is providing random MAC addresses","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RPM","4","UNAVAILABLE","Invalid CPU ID, assuming revision 1","The CPU ID could not be read from the EEPROM. This is probably due to a hardware failure","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RPM","4","UNAVAILABLE","PCI activation failed, bay %d, 0x%x","The system received an invalid PCI signal from the port adapter. This is probably due to a hardware failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RPM_VIRTUAL_PORT","3","UNAVAILABLE","%s","This error indicates that the delete request to PXM has failed, timed out, or been rejected by PXM.","In the case of the failure or time-out the connection's state will be set to TIMEOUT and the resync process will periodically attempt to update PXM. In the case where the request is rejected by PXM (which should never occur) Copy the error message exactly as it appears, and report it to your technical support representative."
"RPM_VIRTUAL_PORT","3","UNAVAILABLE","%s Error String = %s. Error Code = %d","The rpc/ipc request to PXM has failed or been rejected by PXM.","If the error message indicates rpc-timeout, the last command must be retried later. For other error cases copy the error message exactly as it appears, and report it to your technical support representative."
"RPM_VIRTUAL_PORT","3","UNAVAILABLE","%s Message size = %d","The error message indicates that the size of the message which is supposed to be sent to PXM or is received from PXM is too big.","Copy the error message exactly as it appears, and report it to your technical support representative."
"RPM_VIRTUAL_PORT","3","UNAVAILABLE","%s Message size = %d","The ipc_get_pak_message failed. This could be due to the insufficient memeory.","Copy the error message exactly as it appears, and report it to your technical support representative."
"RPM_VIRTUAL_PORT","3","UNAVAILABLE","%s request_type = %d","The rpc request from Virtual-Port or Resync process is not valid. This error should never occur","Copy the error message exactly as it appears, and report it to your technical support representative."
"RPM_VIRTUAL_PORT","3","UNAVAILABLE","An unexpected FW error has occured. %s","An unexpected FW error has occured","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RPM_VIRTUAL_PORT","3","UNAVAILABLE","ERROR: clrAllCnf --- Fail to delete clrAllCnf file on PXM C: disk ... Please delete file manually by doing delete c:auto_config_slot%d.","This error indicates that the re-configuration request to PXM has failed, timed out, or been rejected by PXM.","In the case of the failure or time-out the connection's state will be set to TIMEOUT and the resync process will periodically attempt to update PXM. In the case where the request is rejected by PXM the connection state will be set to FAILED until the connection is deleted or re-configured."
"RPM_VIRTUAL_PORT","3","UNAVAILABLE","ERROR: clrAllCnf --- Fail to write to NVRAM. NOTE: Configuration in NVRAM is not cleaned up. RPS-3Error Message    %RPS-3-UNAVAILABLE: Redundant Power System DC Output Voltage condition is now normal","The Redundant Power System DC Output Voltage is normal.","This is an informational message only. No action is required."
"RPS","3","UNAVAILABLE","Redundant Power System FAN condition is now normal.","The Redundant Power System FAN is now normal.","The Redundant Power Supply previously detected fan failure condition which has now cleared."
"RPS","3","UNAVAILABLE","Redundant Power System Input Voltage condition is now normal","The Redundant Power System Input Voltage is normal.","This is an informational message only. No action is required."
"RPS","3","UNAVAILABLE","Redundant Power System THERMAL condition is now normal.","The Redundant Power System THERMAL is now normal.","The Redundant Power Supply previously detected an over temperature condition which has now cleared. This is most likely due to high ambient temperature where the Redundant Power Supply is located. A Redundant Power System thermal failure can also be caused by a fan failure in the Redundant Power Supply."
"RPS","3","UNAVAILABLE","Redundant Power System VOLTAGE is now normal.","The Redundant Power System voltage is now normal.","The Redundant Power System previously detected an over voltage condition which has now cleared."
"RPS","3","UNAVAILABLE","Redundant Power System detected OVERVOLTAGE condition.","The Redundant Power System detected OVERVOLTAGE condition.","The Redundant Power System detected an over voltage condition."
"RPS","3","UNAVAILABLE","Redundant Power System is now normal","The Redundant Power System is operating normally.","This is an informational message only. No action is required."
"RPS","3","UNAVAILABLE","System detected Redundant Power System DC Output Voltage failure condition.","The Redundant Power System experienced a DC Output Voltage failure condition in one of the power supplies.","One of the DC outputs has failed on the Redundant Power Supply. For 3600 and 2600 Redundant Power supplies, DC Status LED on the front of the Power Supply will identify which DC output has failed. For 5300 Redundant Power Supply, DC OK LED on the front of the Power Supply will identify which DC output has failed. When there is a DC failure, you need to replace the Redundant Power Supply."
"RPS","3","UNAVAILABLE","System detected Redundant Power System FAN FAIL condition.","The Redundant Power System experienced a Fan failure condition.","One of the fans has failed and you should replace the Redundant Power Supply."
"RPS","3","UNAVAILABLE","System detected Redundant Power System Input Voltage failure condition.","The Redundant Power System experienced an Input Voltage failure in one of the power supplies.","One of the AC or DC inputs has failed on the Redundant Power Supply. For 3600 and 2600 Redundant Power supplies, AC Input LED on the front of the Power Supply will identify which AC input has failed. For 5300 ACDC Redundant Power Supply, AC OK LED on the front of the Power Supply will identify which AC input has failed. For 5300 DCDC Redundant Power Supply, DC Input LED on the front of the Power Supply will identify which DC input has failed. Make sure that the AC/DC circuit in your building is operational, verify that the power cord is plugged into the Redundant Power Supply, and make sure that the AC/DC power switch on the Redundant Power Supply is on."
"RPS","3","UNAVAILABLE","System detected Redundant Power System THERMAL FAIL condition.","The Redundant Power System experienced either a Fan failure or an Over Temperature condition.","For 3600 and 2600 Redundant Power supplies, look at the FAN and TEMP LEDs on the front of Power Supply. If the FAN LED is amber, one of the fans has failed and you should replace the Redundant Power Supply. If the TEMP LED is amber, the ambient temperature is too high. For 5300 RPS unit, this message is displayed when the ambient temperature is too high."
"RPS","3","UNAVAILABLE","System temperature is now normal.","The system is operating at a normal temperature.","The system previously detected an over temperature condition which has now cleared. This is most likely due to high ambient temperature where the router is located."
"RPS","3","UNAVAILABLE","There is more than one failure with the Redundant Power System; please resolve problems immediately","The Redundant Power System experienced multiple failures. This is a critical condition","There are multiple failures on the Redundant Power Supply. Examine the LEDs on the front of the Redundant Power Supply to find out which failures it has."
"RP_MLP","4","BADLINKDECONFIG","Bad way of removing member link, now perform 'no shut' on both sides of Multilink","If member link has to be removed from multilink bundle, first remove the multilink configuration from the member link and then perform no channel-group command on the controller.","If the member link is removed from the multilink bundle using no channel-group command, perform no shut on both sides of the multilink interface to make it work."
"RP_MLP","4","DLFIONELINKSUPPORT","Only ONE link should be configured for dLFI bundle!!","Trying to configure more than ONE link for dLFI bundle interface, which is not supported by dLFIoFR and dLFIoATM.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RP_MLP","4","MISCONFIGLINK","Links across linecards or dCEF disabled, giving control to RP","Trying to add links to a bundle which are spread across linecards DMLP cant support this, so giving control of bundle to RP.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RP_MLP","4","NODISTMLP","Failure downloading MLP bundle %s to the LC %d","The bundle is configured to be distributed, but for some reasons we cannot download the MLP config to the LCd.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RP_MLP","4","PANOTSUPPORTED","Adding Link from unsupported PA, cant add, giving control to RP","Trying to add links to a bundle from a PA which is not supported by DMLP, so giving control of bundle to RP.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RPC","2","6","Recovered from RPC send failure for request [chars]. Resending request.","A communication error occurred during an RPC request. RPC will retry.","This is an informational message only. No action is required."
"RPC","2","APPNOTREG","Remote application '%s' not registered","The remote application has not registered itself with the RPC subsystem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RPC","2","CORE_SAT_RPC_FAIL","RPC between Core and Remote Switch - [chars] failed (non-fatal)Expected when VSL goes down","A nonfatal communication error occurred during an RPC request between the core and a remote switch or vice versa. This error message is not considered a failure when the virtual switch link (VSL) goes down.","No action is required."
"RPC","2","FAILED","Failed to send RPC request [chars] (fatal)","A fatal communication error occurred during an RPC request.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RPC","2","FAILED_RETRY","Failed to send RPC request [chars] (will try again)","A communication error occurred during an RPC request. The system will attempt the RPC request again.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RPC","2","FAILED_USERHANDLE","Failed to send RPC request [chars]","A communication error occurred during an RPC request.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RPC","2","NOMEM","No memory available for %s","The RPC subsystem could not obtain the memory it needed.","The RPC will retry the request. If the message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RPC","2","NOSUCH","The referenced RPC application (%d) does not exist","A message was received for a non-existent RPC application.","The RPC will retry the request. If the message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RPC","2","NOTREADY","The referenced RPC application (%d,%s) is not ready","A message was received for an RPC application that is not ready.","The RPC will retry the request. If the message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RPC","2","RETRY","Recovered from RPC send failure for request [chars].  Resending request.","A communication error occurred during an RPC request.","The RPC will retry the request. If the message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RPC","4","BADID","Application ID %d is invalid","The application ID used by the RPC subsystem is invalid.","The RPC will retry the request. If the message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RPC","4","DUPREG","Application '%s' is already registered","The application has already registered itself with the RPC subsystem.","The RPC will retry the request. If the message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RPC","4","TOOMANY","Too many RPC applications, '%s' not registered","There are too many applications registered with the RPC subsystem.","The RPC will retry the request. If the message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RPF","3","RTAVLDELETE","Error deleting an rpf entry from the multicast rpf tree","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RPF","3","RTAVLINSERT","Error inserting a new rpf entry into the multicast rpf tree","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RPF","4","AVLDELETE","Error deleting an rpf entry from the multicast rpf tree","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RPF","4","AVLINSERT","Error inserting a new rpf entry into the multicast rpf tree","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RPF","4","SNMP_RADIX_ERR","Failed to [chars] snmp node [chars] snmp radix tree for multicast group (*, [IP_address]).","An error occured while adding or deleting snmp node in snmp radix tree when mroute is created or deleted.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"RP_MLP","3","ADJ_FAIL","Adjacency walk for [chars] failed","An adjacency update for the specified multilink interface failed.","Reset the multilink interface by entering the shutdown command followed by the no shutdown command on the interface. If traffic does not resume, collect the output of the show adjacency internal and show cef interface internal commands. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RP_MLP","3","INCOMPATIBLELINK","The current config cannot be supported as link([chars]) [chars] for bundle ([chars])","When using multilink, the following restrictions must be met:- All the links should be from the same port.- Non-channelized T3 interfaces are not supported on multilink.- Any added link should be compatible with the existing links in the bundle.- All the links should be distributed.","Modify the configuration so that the restrictions are not violated."
"RP_MLP","3","UNSUPPORTEDCONFIG","The current config cannot be supported as [chars] for [chars]","When using multilink on hardware-assisted SPAs, the maximum number of links in the bundle and number of bundles should not exceed the maximum permissible by device. Refer to the product documentation for restrictions.","Modify the configuration so that it does not violate the restrictions."
"RP_MLP","4","DLFIONELINKSUPPORT","Only ONE link should be configured for dLFI bundle!!","The system attempted to configure more than one link for the Distributed Link Fragmentation and Interleaving (dLFI) bundle interface. The dLFIoFR and the dLFIoATM do not support configuring more than one link.","No action is required."
"RP_MLP","5","SPAWARNING","Feature support switching to LC based software for [chars] as [chars]","A link was added to the bundle, but it is not on the same bay as other member links of the bundle. The specified link that is not on the same bay has become active, and the bundle has been switched to line card-based software support instead of the hardware mode that is supported on FREEDM.","When a link is added to a bundle, ensure that it is on the same bay as the other member links of the bundle, in order to have the MLP bundle in hardware mode supported on FREEDM."
"RSP","2","UNAVAILABLE","Overrun detected. End of MEMD buffer : 0x%x End of datagram : 0x%x bufhdr %x: %08x %08x %08x %08x Flushing Processor Cache","A packet was processed that was greater in size than the maximum possible MTU size, or an illegal buffer header data area was found.","Copy the error message exactly as it appears on the console or in the system log, enter the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information."
"RSP","2","UNAVAILABLE","%s error, %s at addr %04x (%s) log %08x, data %08x %08x","While the system was attempting to process a hardware queue, an error was detected by the QA ASIC. The error could be either a zero link error or a reuse error. A zero link error is caused by an attempt to place in the hardware queue a buffer header with an address of 0x0. A reuse error occurs when the QA ASIC detects or attempts to place in the hardware queue a buffer header that is the same as another buffer header in another hardware queue. Either of these errors can occur because of a software or hardware problem with the RSP or a line card.","Run the show logging command and see that whether any parity errors were recorded just before the QAERROR error message was received. If any parity error was recorded before the QAERROR, a hardware error has occurred. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. If no parity error was recorded, and the problem recurs, enter the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the output of the commands."
"RSP","2","UNAVAILABLE","No memory available for %s","An attempt at memory allocation failed.","Try these actions to remedy the problem: Add memory. Disable some features. Apply filtering to decrease the size of system data structures - the routing table, for example. In general, reduce other system activities to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"RSP","2","UNAVAILABLE","QA Diagnostic %s error at %#08x","An error occurred during an attempt to access the RSP.","Copy the error message exactly as it appears on the console or in the system log, enter the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information."
"RSP","2","UNAVAILABLE","partially inserted or removed IPs on cyBus%u","The RSP detected a stall condition of cbus.Most likely, a board is not fully seated in the chassis. A less likely possibility is a hardware problem with the RSP or backplane.","Try reseating the boards. Call your technical support representative for assistance if this message persists."
"RSP","3","UNAVAILABLE","%s %s","An IPC error has occurred. The exact nature of the problem is described in the error message.","Copy the router configuration, along with any other relevant information. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information."
"RSP","3","UNAVAILABLE","%s (slot %u) has wrong hardware revision %u.%u","The hardware in the indicated slot needs to upgraded for operation with the RSP.","Upgrade the board."
"RSP","3","UNAVAILABLE","%s acc %08x had bad value %d","An incorrect value has been written on an accumulator.","Copy the error message exactly as it appears, and report it to your technical support representative. A micro reload can correct the error condition as a workaround."
"RSP","3","UNAVAILABLE","%s, address %x","A software or hardware error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"RSP","3","UNAVAILABLE","%s: unable to schedule restart for output queue","A software or hardware error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"RSP","3","UNAVAILABLE","%x corrupt: %08x %08x %08x %08x","The event handler at the RSP has detected a status update message from an interface processor, but the field in the status message that identifies the associated interface processor is not valid. This condition indicates that the status message is corrupted. This error could occur because of a hardware or a software problem. The address of the status message buffer and the first four words of the message will be displayed for diagnostic purposes.","Copy the error message exactly as it appears on the console or in the system log, enter the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information."
"RSP","3","UNAVAILABLE","Bad Turbo IPC msg (%s): msg=%#x lastmsg=%#x hdrsize=%#x size=%#x","An error was discovered in an IPC message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RSP","3","UNAVAILABLE","Bad or missing ID EEPROM, controller type %u","The ID EEPROM on the RSP is missing or bad.","This message indicates a manufacturing error. Report this error to your technical support representative."
"RSP","3","UNAVAILABLE","Bengal error. %s","System controller Bengal has reported an error/event","Read error reports. SBE are generally not fatal. Most others are"
"RSP","3","UNAVAILABLE","Can't allocate MAC address for interface %u/%u","No MAC address was available for allocation to the specified interface.","Report this error to your technical support representative."
"RSP","3","UNAVAILABLE","Card %s wants %d byte love letters, but only got %d bytes","An inconsistency between the microcode and the system code was detected.","Report this error to your technical support representative."
"RSP","3","UNAVAILABLE","Fixing %s by setting to default %s","The characters shown can be either on the slave RSP setting or on the master RSP setting. The ROM monitor default slave RSP setting is not synchronized with the system configuration file specifications. During bootup, the system image detects the mismatch and modifies the ROM monitor setting to conform with these specifications. This mismatch most likely occurred because a new RSP was being installed and booted in a high system availability (HSA) environment (dual RSPs) for the first time. Alternatively, in established HSA configurations, this message may result from a previous Interprocess Communication (IPC) error occurring while the HSA environment is reconfigured.","Using the show version or show boot command, determine which slot contains the current slave RSP. Using the show config command, determine which slot has been specified as the default slave RSP. If there is no slave default-slot n command in the configuration file, the value defaults to the highest numbered CPU slot (slot 3 on a Cisco 7507, and slot 7 on a Cisco 7513). If the slot number obtained in Step 1 is the same as the number obtained in Step 2, then no further action is required. You have configured HSA in simple hardware backup mode, and both RSPs are identical. However, if the two slot numbers differ, you have configured HSA in software error protection mode, and will have different images running, depending on which RSP is currently the slave RSP. If the slot numbers discovered in Steps 1 and 2 differ, reload your router to ensure that the desired system image is running. After the reload, the actual slave RSP will match the default slave RSP specified in (or inferred from) the system configuration file. For details of various HSA configuration modes consult the Cisco IOSConfiguration Fundamentals Configuration Guide. See the Loading System Images and Configuration Files chapter (Cisco 7500 series only)."
"RSP","3","UNAVAILABLE","Invalid return queue bcast_id=%d bufhdr %x: %08x %08x %08x %08x","A software or hardware error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"RSP","3","UNAVAILABLE","Invalid return queue next=%#x, hwidb=%#x, type=%#x queue_ptr=%#x, bufhdr_offset=%#x, id=%d, bcast_id=%d bufhdr %x: %08x %08x %08x %08x","A software or hardware error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"RSP","3","UNAVAILABLE","Malloc to %s failed for slot %d bay %d","The information structure for the port adapter could not be created. The interfaces on the specified port adapter might no longer be functional. A possible reason for this is a memory allocation failure involving the port adapter. This can occur as a result of insufficient hardware memory or a memory leak.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RSP","3","UNAVAILABLE","Master has m/s version %d, slave has m/s version %d","The master and slave are running incompatible software versions with regards to the master/slave exchange process.","If the slave image global configuration is used to override the default slave image from the bundle, then the slave image is incompatible. Update either the master or slave image to ensure the two are compatible. If the slave is running the image from the bundle, execute and record the output of show version, show running-config, and show controller cbus commands. Report this information and the error message to your technical support representative."
"RSP","3","UNAVAILABLE","Master/slave watchdog timed out","While handling the interrupts from the DBUS FPGA, the RSP has detected that the timeout bit in the interrupt status register has been set. This condition indicates that the master RSP no longer controls the CBUS and DBUS. The slave may become active during this time. So, the rest of the interrupt handler will not be processed. This behavior could be the result of either a hardware or a software problem.","Copy the error message exactly as it appears. If this problem recurs, copy down the router's configuration along with any other relevant information, such as the output of show tech-support and show logging commands. Contact your Cisco technical support representative for assistance, and provide him with all the gathered information."
"RSP","3","UNAVAILABLE","NULL","An internal software error has occurred. The exact nature of the problem is described in the error message.","Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information."
"RSP","3","UNAVAILABLE","NULL","The cBus buffer memory has been reset and reallocated. The exact nature of the problem is described in the error message.","Reset the memory manually (by changing the MTU on an interface, for example). If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information."
"RSP","3","UNAVAILABLE","No microcode for %s card, slot %u","No microcode is defined or available for the specified card.","Reconfigure the card to specify an existing microcode file."
"RSP","3","UNAVAILABLE","Panic: %s %08x %08x %08x %08x","The status message handler for the interface processor has detected that the firmware for the interface processor has experienced a critical condition. The name of the affected interface and the first four words of the status message buffer will be displayed along with the message for diagnostics","Copy the error message exactly as it appears on the console or in the system log, enter the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information."
"RSP","3","UNAVAILABLE","Slave NVRAM is temporarily busy","Another process is temporarily locking the slave config.","Retry the command that caused the error message. If the error message recurs, check for other execs via the show users command. If you know that there are no other users locking the slave nvram, then contact your technical support representative for assistance."
"RSP","3","UNAVAILABLE","Slave changed state from %s to %s","The slave RSP has undergone a hardware state change. Both the old state and new state are shown. Possible states are nonparticipant slave master unplugged Possible state changes indicated by the above message are any to unplugged unplugged to nonparticipant or slave nonparticipant to slave slave to nonparticipant Any other combination is unexpected.","The slave RSP has been removed. Consider reinstalling it if continued high system availability (HSA) operation is required. If the slave RSP is present, ensure that it is properly seated in the card cage. A slave RSP has been installed. Configure the router for HSA. See the Configuration Fundamentals Configuration Guide, in the Loading System Images and Configuration Files chapter (Cisco 7500 series only) for more details. In particular, use the slave sync config command to ensure that the new slave RSP is configured consistently with the current master RSP. CAUTION: Failure to ensure a consistent configuration on a freshly installed slave RSP might result in undefined behavior if the router reloads. A previously crashed slave RSP has been reset, or a newly installed slave RSP is in transition from unplugged to nonparticipant, and finally to slave state. No action is required. The slave RSP image has crashed. Log in to the slave RSP's console using the if-console slot command. You will now be connected to the ROM monitor prompt on the slave RSP. Diagnose the slave RSP failure. For example, capture the output from the stack and context ROM monitor commands. Provide that information to your technical support representative, along with the router's configuration and any other relevant information, so that the problem can be investigated. Log out from the slave RSP's console port using Ctrl-c or Ctrl-z, and enter the slave reload global configuration command on the master RSP to bring the slave RSP back online. All other state changes indicate a software or hardware error. Provide the router's configuration and any other relevant information to customer support so that the problem can be investigated."
"RSP","3","UNAVAILABLE","Slave stole mastership","The master RSP has detected that the slave RSP configuration was changed from slave to master. The old master RSP will reload and become the slave RSP, allowing the new master RSP take over. This behavior indicates a software or hardware error.","Copy the router configuration, along with any other relevant information. Copy the error message exactly as it appears on the console or in the system log, enter the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information."
"RSP","3","UNAVAILABLE","bad vc %u on %s","A chennelized interface driver received a packet on an unconfigured channel.","Copy the error message exactly as it appears, and report it to your technical support representative, along with the output of 'show tech-support'."
"RSP","3","UNAVAILABLE","cmd %u to %s (slot %u) took %u usecs, done %x","A command from the RSP to an IP took longer for the system to process than expected. This condition may be caused by a heavily loaded CPU.","If this error recurs, copy the error message exactly as it appears on the console or in the system log, enter the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information."
"RSP","3","UNAVAILABLE","corrupt bufhdr %x: %08x %08x %08x %08x","A miscommunication occurred between the RSP and an IP.","Copy the error message exactly as it appears on the console or in the system log, enter the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information."
"RSP","3","UNAVAILABLE","queue=%#x, bufhdr %x: %08x %08x %08x %08x","A software or hardware error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"RSP","3","UNAVAILABLE","reload command not allowed on standby RSP","The reload command in exec mode is not allowed on thestandby RSP","Enter the slave reload commandin exec mode."
"RSP","4","UNAVAILABLE","%s","Report this error to your technical support representative.Error Message    %RSP-4-UNAVAILABLE: %uMB required for HSA Explanation    HSA requires a minimum of 24mb of memory.","Upgrade your system to meet minimum memory requirements for HSA."
"RSP","4","UNAVAILABLE","Corrupt or missing MAC address cookie using random base %e","This message indicates the part containing the MAC addresses allocated to this chassis could not be accessed or was found to be corrupt, either due to a hardware problem or manufacturing problem.","Report this error to your technical support representative."
"RSP","4","UNAVAILABLE","DCEF switching should be enabled on member links of %s","DCEF should be enabled for Multilink interfaces if required.","Go to the multilink interface configuration mode using the interface multilink multilink# command , and then enable DCEF on the interface using ip route-cache distributed as per your requirement"
"RSP","4","UNAVAILABLE","Error saving crashinfo for slot %d. Reason: %s","A VIP crashinfo file has not been saved due to the indicated reason.","If the reason indicates Out of space, the bootflash may not have sufficient memory to save the crashinfo file. Otherwise, open a case with the Technical Assistance Center via the Internet at www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RSP","4","UNAVAILABLE","Insufficient DRAM to adequately run this IOS version. %dM is recommended.","The quantity of RSP DRAM is below the recommended amount.","Add DRAM."
"RSP","4","UNAVAILABLE","Slave configuration not updated for %s.","The configuration on the slave cannot be synced with the master.","Ensure that 'slave auto-sync config' is configured, and that the slave is active"
"RSP","4","UNAVAILABLE","VIP in slot %d was empty and was disabled","The system failed to copy the specified file to the standbyRSP.","Ensure that the standby RSP exists and has enoughmemory for the file."
"RSP","4","UNAVAILABLE","size mismatch, master %uMB, slave %uMB","Memory size mismatch between Master & Slave RSP.","Configure both Master and Slave RSPs to have an equal amount of memory."
"RSP","5","UNAVAILABLE","Slave changed to state Running, Buffer memory state : %s","This is an informational message to indicate that the slave RSP has started running the slave RSP image. This message after the router boots or after the slave reload global configuration command is issued on the master RSP.","No action required."
"RSP","6","TXSTUCK","Txacc of Interface [chars] is at [dec]% of its txlimit","The specified interface has a low TXACC value. This might be a transient condition and might be harmless if it occurs during periods of high packet traffic. If this condition is detected more than once during periods of relatively moderate traffic, it could indicate a problem. Distributed packet switching might be disrupted as a result of this condition.","If the message recurs during periods of relatively moderate traffic, this might indicate a disruption in distributed packet switching. If such a disruption occurs, enter the microcode reload command to recover. Open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RSRB","3","UNAVAILABLE","%s: %d/%i: version mismatch, mine %d, theirs %d","The remote end of a TCP remote peer is running the wrong version of the system software. Either the local end, the remote end, or both are not up to date.","Call your technical support representative for an update."
"RSRB","3","UNAVAILABLE","%s: %s: %i, op %x, len %d, trn %d","The remote end of a direct serial RSRB connection detected a configuration problem or traffic that is not recognized by the configuration.","Examine the configuration on both sides of the serial connection for possible problems. Examine the traffic being offered for propagation with respect to the configuration. The destination target ring is denoted by the value of trn."
"RSRB","3","UNAVAILABLE","%s: %s: %s, op %x, len %d, trn %d","The remote end of a direct serial RSRB connection detected a configuration problem or traffic that is not recognized by the configuration.","Examine the configuration on both sides of the serial connection for possible problems. Examine the traffic being offered for propagation with respect to the configuration. The destination target ring is denoted by the value of trn."
"RSRB","3","UNAVAILABLE","%s: sent %s to %s","The local end of a direct serial RSRB connection detected a configuration problem or traffic that is not recognized by the configuration.","Examine the configuration on both sides of the serial connection for possible problems. Examine the traffic being offered for propagation with respect to the configuration."
"RSRB","3","UNAVAILABLE","FSTin: %s: version mismatch, mine %d, theirs %d","The remote end of a direct serial peer is running the wrong version of the system software. Either the local end, the remote end, or both are not up to date.","Call your technical support representative for an update."
"RSRB","3","UNAVAILABLE","IFin: %s: version mismatch, mine %d, theirs %d","The remote end of a direct serial peer is running the wrong version of the system software. Either the local end, the remote end, or both are not up to date.","Call your technical support representative for an update."
"RSRB","3","UNAVAILABLE","Null idb and not remote","An internal software error occurred.","If any of these messages recur, call your technical support representative for assistance."
"RSRB","3","UNAVAILABLE","Peer %d/%i, HDR, vrp state wrong, %d","An internal software error occurred.","If any of these messages recur, call your technical support representative for assistance."
"RSRB","3","UNAVAILABLE","Peer %i, HDR, no vrp","An internal software error occurred.","If any of these messages recur, call your technical support representative for assistance."
"RSRB","3","UNAVAILABLE","Unit %d, no memory for %s","The requested operation could not be accomplished because of a low memory condition.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"RSRB","4","UNAVAILABLE","Bad vre type","An internal software error occurred.","If any of these messages recur, call your technical support representative for assistance."
"RSRB","4","UNAVAILABLE","Peer %d/%i, %s, bad length %d, trn %d","An internal software error occurred.","If either message recurs, call your technical support representative for assistance."
"RSRB","4","UNAVAILABLE","Peer %d/%i, CONN, illegal state %d","An internal software error occurred.","If any of these messages recur, call your technical support representative for assistance."
"RSRB","4","UNAVAILABLE","Peer %d/%i, HDR, recv state invalid, not empty %d","An internal software error occurred.","If any of these messages recur, call your technical support representative for assistance."
"RSRB","4","UNAVAILABLE","Peer %s [%-08x], illegal state %d","An internal software error occurred.","If either of these messages recur, call your technical support representative for assistance."
"RSRB","4","UNAVAILABLE","Peer %s, %s, bad length %d, trn %d","An internal software error occurred.","If either message recurs, call your technical support representative for assistance."
"RSRB","4","UNAVAILABLE","Peer %s, CONN, illegal state %d","An internal software error occurred.","If any of these messages recur, call your technical support representative for assistance."
"RSRB","4","UNAVAILABLE","Peer %s, IFin, bad connection state %d","An internal software error occurred.","If any of these messages recur, call your technical support representative for assistance."
"RSRB","4","UNAVAILABLE","Peer %s, wrong state %d","An internal software error occurred.","If any of these messages recur, call your technical support representative for assistance."
"RSRB","4","UNAVAILABLE","Remopened and t NULL","An internal software error occurred.","If any of these messages recur, call your technical support representative for assistance."
"RSRB","4","UNAVAILABLE","Ring exchange failure, resetting peer: %s","The RSRB peer initiation logic failed due to a memory shortage or congestion condition.","The problem should clear and the peers should re-open without operator intervention."
"RSRB","4","UNAVAILABLE","Unit %d, local/vring set simultaneously, vrn %d","An internal software error occurred.","If either of these messages recur, call your technical support representative for assistance."
"RSVP","1","RSVP_AUTH_NO_KEYS_LEFT","No valid keys left for [IP_address]","The router attempted to use a key in an RSVP key chain but discovered that all the keys in the chain have expired and no other per-neighbor or per-interface keys are available for the specified neighbor. The router will continue to use the last key in the chain rather than revert to an unauthenticated condition. However, the specified neighbor router may start discarding RSVP messages as a result, and reservations with that neighbor may eventually time out.","Update the key chain by updating the text and expiration times for the expired keys."
"RSVP","2","RSVP_AUTH_KEY_CHAIN_EXPIRED","All the keys in chain [chars] have expired - please update the key chain now","The router attempted to use a key in an RSVP key chain but discovered that all the keys in the chain have expired. The router will attempt to find another suitable key. If no other suitable per-neighbor key can be found, the router will attempt to use key (chain) configured for the interface over which the authenticated RSVP message is being sent or received.","Update the key chain by updating the text and expiration time(s) for the expired key(s)."
"RSVP","3","BAD_RSVP_MSG_RCVD_AUTH_COOKIE","%s message from %i discarded - challenge failed for key ID %*s","The router sent an RSVP message to challenge the untrusted source to compute a secure hash on a random piece of data and return the hash with the same data, but the source did not return the expected data. RSVP discarded the response because the untrusted source may be (unsuccessfully) attempting an RSVP challenge response replay attack.","If you can verify that the source is trusted, it is possible that the source has malfunctioned; in this case, copy the error message exactly as it appears on the console or in the system log, issue the show tech-support rsvp command to gather data which may help identify the nature of the error, and send this information to your Cisco technical support representative. Otherwise, try to find and disable the untrusted source."
"RSVP","3","BAD_RSVP_MSG_RCVD_AUTH_DIGEST","%s message from %i discarded - incorrect message digest","The router received an RSVP message that contained a different secure hash from the one computed by the router. RSVP discarded the message because the message may have come from an untrusted source.","Check the configuration on the router and the sending system to make sure they are using the correct security key and secure hash algorithm."
"RSVP","3","BAD_RSVP_MSG_RCVD_AUTH_DUP","%s message from %i discarded - authentication seq #%llu is a duplicate","The router received an RSVP message with an authentication sequence number that has already been seen. RSVP discarded the message because an untrusted source may be (unsuccessfully) attempting an RSVP message replay attack.","If you can verify that the source is trusted, it is possible that the source has rebooted and its clock has gone backward in time; in this case, the source should be configured to synchronize its clock with an NTP server. Otherwise, the sender could be an untrusted source (unsuccessfully) attempting an RSVP message replay attack; try to find and disable the untrusted source."
"RSVP","3","BAD_RSVP_MSG_RCVD_AUTH_NO_SA","%s message from %i discarded: no security association for %i - no RSVP security key configured or no memory left.","The router received an RSVP message that contained a secure hash but dropped the message because the router was not able to create a security association for the sending system.","Check the configuration on the router to make sure that RSVP has access to a security key for the sending system. If such a key is configured, then check to see if the router has run out of memory."
"RSVP","3","BAD_RSVP_MSG_RCVD_AUTH_WIN","%s message from %i discarded - seq #%llu outside authentication window","The router received an RSVP message whose authentication sequence number is less than the lower limit of the out-of-order window. RSVP discarded the message because an untrusted source may be (unsuccessfully) attempting an RSVP message replay attack.","It is possible that a trusted source is sending a burst of reordered RSVP messages that is too large for the authentication window size. If you can verify that the source is trusted and its messages are being sent in large reordered bursts, use the ip rsvp authentication window-size command to increase the window size on the receiving router. It is also possible that a trusted source has rebooted and its clock has gone backward in time; in this case, the source should be configured to synchronize its clock with an NTP server. Otherwise, the sender could be an untrusted source (unsuccessfully) attempting an RSVP message replay attack; try to find and disable the untrusted source."
"RSVP","3","RSVP_MFI_RECOVERY","RSVP calculated Recovery Time is longer than TE Rewrite Hold-Time registered with LSD. Some LSPs may not be be recovered.","TE registered a maximum cutover time with the LSD that is less than the time it may actually take to recover all LSPs. As a result, more than usual traffic loss may occur on some LSPs during recovery","Make note of the number of Checkpointed LSPs in the RSVP HA database by issuing the command show ip rsvp high-availability database internal . This number likely exceeds the hard defined limit of the number of recoverable LSPs. Provide this information to Cisco technical support representative."
"RSVP","3","RSVP_MSG_AUTH_CHALLENGE_TIMEOUT","No response to challenge issued to %i for key ID %*s","The router sent an RSVP message to challenge the untrusted source to compute a secure hash on a random piece of data and return the hash with the same data, but the source did not reply. The source may have crashed or lost its network connection. However, it is also possible that the source was (unsuccessfully) attempting to replay an RSVP message before the challenge and gave up when it saw the challenge from the router","If you can verify that the source is trusted, try to determine if it has crashed or lost its network connection and then restore network connectivity to it. If the source repeatedly crashes when challenged, a temporary workaround might be to disable challenges on the router by issuing a no ip rsvp authentication challenge command until the problem on the source is resolved. Otherwise, assume the source is untrusted; try to find and disable it."
"RSVP","3","RSVP_MSG_AUTH_TYPE_MISMATCH","%s message from %i discarded - authentication algorithm mismatch","The router received an RSVP message from a source that required authentication but the received message was using the wrong authentication algorithm.","Issue a show ip rsvp authentication detail command on the router to display the expected algorithm type. Then find the source and change its configuration to match."
"RSVP","3","UNAVAILABLE","%08x %08x %08x %08x %08x %08x %08x %08x","This is an auxiliary message to several packet-related messages. It provides a raw display of the information in the header of a corrupted data block.","This message provides additional information only. Copy the error message exactly as it appears, and report it to your technical support representative as part of the previously printed error message."
"RSVP","3","UNAVAILABLE","%08x %08x %08x %08x %08x %08x %08x %08x","This is an auxiliary message to several packet-related messages. It provides a raw display of the information in the header of a corrupted data block.","This message provides additional information only. Copy the error message exactly as it appears, and report it to your technical support representative as part of the previously printed error message."
"RSVP","3","UNAVAILABLE","%s message from %i discarded - authentication algorithm mismatch","The router received an RSVP message from a source that required authentication but the received message was using the wrong authentication algorithm.","Issue a show ip rsvp authentication detail command on the router to display the expected algorithm type. Then find the source and change its configuration to match."
"RSVP","3","UNAVAILABLE","%s message from %i discarded - authentication seq #%llu is a duplicate","The router received an RSVP message with an authentication sequence number that has already been seen. RSVP discarded the message because an untrusted source may be (unsuccessfully) attempting an RSVP message replay attack.","If you can verify that the source is trusted, it is possible that the source has rebooted and its clock has gone backward in time; in this case, the source should be configured to synchronize its clock with an NTP server. Otherwise, the sender could be an untrusted source (unsuccessfully) attempting an RSVP message replay attack; try to find and disable the untrusted source."
"RSVP","3","UNAVAILABLE","%s message from %i discarded - challenge failed for key ID %*s","The router sent an RSVP message to challenge the untrusted source to compute a secure hash on a random piece of data and return the hash with the same data, but the source did not return the expected data. RSVP discarded the response because the untrusted source may be (unsuccessfully) attempting an RSVP challenge response replay attack.","If you can verify that the source is trusted, it is possible that the source has malfunctioned; in this case, copy the error message exactly as it appears on the console or in the system log, issue the show tech-support rsvp command to gather data which may help identify the nature of the error, and send this information to your Cisco technical support representative. Otherwise, try to find and disable the untrusted source."
"RSVP","3","UNAVAILABLE","%s message from %i discarded - incorrect message digest","The router received an RSVP message that contained a different secure hash from the one computed by the router. RSVP discarded the message because the message may have come from an untrusted source.","Check the configuration on the router and the sending system to make sure they are using the correct security key and secure hash algorithm."
"RSVP","3","UNAVAILABLE","%s message from %i discarded - seq #%llu outside authentication window","The router received an RSVP message whose authentication sequence number is less than the lower limit of the out-of-order window. RSVP discarded the message because an untrusted source may be (unsuccessfully) attempting an RSVP message replay attack.","It is possible that a trusted source is sending a burst of reordered RSVP messages that is too large for the authentication window size. If you can verify that the source is trusted and its messages are being sent in large reordered bursts, use the ip rsvp authentication window-size command to increase the window size on the receiving router. It is also possible that a trusted source has rebooted and its clock has gone backward in time; in this case, the source should be configured to synchronize its clock with an NTP server. Otherwise, the sender could be an untrusted source (unsuccessfully) attempting an RSVP message replay attack; try to find and disable the untrusted source."
"RSVP","3","UNAVAILABLE","%s message from %i discarded: no security association for %i - no RSVP security key configured or no memory left.","The router received an RSVP message that contained a secure hash but dropped the message because the router was not able to create a security association for the sending system.","Check the configuration on the router to make sure that RSVP has access to a security key for the sending system. If such a key is configured, then check to see if the router has run out of memory."
"RSVP","3","UNAVAILABLE","%s: %s %s %s","An action attempted by the rsvp implementation encountered an unexpected condition","Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data which may help identify the nature of the error. Then send this information to your Cisco technical support representative."
"RSVP","3","UNAVAILABLE","Inconsistent rsvp reliable message timer","The summary refresh timer may be blocked.","Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data which may help identify the nature of the error. Then send this information to your Cisco technical support representative."
"RSVP","3","UNAVAILABLE","No response to challenge issued to %i for key ID %*s","The router sent an RSVP message to challenge the untrusted source to compute a secure hash on a random piece of data and return the hash with the same data, but the source did not reply. The source may have crashed or lost its network connection. However, it is also possible that the source was (unsuccessfully) attempting to replay an RSVP message before the challenge and gave up when it saw the challenge from the router","If you can verify that the source is trusted, try to determine if it has crashed or lost its network connection and then restore network connectivity to it. If the source repeatedly crashes when challenged, a temporary workaround might be to disable challenges on the router by issuing a no ip rsvp authentication challenge command until the problem on the source is resolved. Otherwise, assume the source is untrusted; try to find and disable it."
"RSVP","3","UNAVAILABLE","RSVP Message had a bad checksum: %d foo: %d","The router received an incorrect RSVP message.","Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data which may help identify the nature of the error. Then send this information to your Cisco technical support representative."
"RSVP","3","UNAVAILABLE","RSVP Message had a bad length; ip data len: %d rsvp len: %d","The router received an incorrect RSVP message.","Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data which may help identify the nature of the error. Then send this information to your Cisco technical support representative."
"RSVP","3","UNAVAILABLE","RSVP Message had a bad type: %d","The router received an incorrect RSVP message.","Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data which may help identify the nature of the error. Then send this information to your Cisco technical support representative."
"RSVP","3","UNAVAILABLE","RSVP Message had a bad version: %d","The router received an incorrect RSVP message.","Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data which may help identify the nature of the error. Then send this information to your Cisco technical support representative."
"RSVP","3","UNAVAILABLE","RSVP Message was malformed; traversed objects len: %d rsvp msg len: %d","The router received an incorrect RSVP message.","Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data which may help identify the nature of the error. Then send this information to your Cisco technical support representative."
"RSVP","3","UNAVAILABLE","RSVP calculated Recovery Time is longer than TE Rewrite Hold-Time registered with LSD. Some LSPs may not be be recovered.","TE registered a maximum cutover time with the LSD that is less than the time it may actually take to recover all LSPs. As a result, more than usual traffic loss may occur on some LSPs during recovery","Make note of the number of Checkpointed LSPs in the RSVP HA database by issuing the command show ip rsvp high-availability database internal . This number likely exceeds the hard defined limit of the number of recoverable LSPs. Provide this information to Cisco technical support representative."
"RSVP","3","UNAVAILABLE","Received a bad RSVP message, num objs: %d obj len: %d msg_len: %d","The router received an incorrect RSVP message.","Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data which may help identify the nature of the error. Then send this information to your Cisco technical support representative."
"RSVP","4","RSVP_AUTH_DUPLICATE_KEY_ID","Key chains [chars] and [chars] contain duplicate key ID [int]","An attempt is being made to add a new key identifier to a key chain in the router configuration but RSVP detected that this identifier is found in another key chain already assigned to RSVP. Becaue key identifiers must be unique across all the key chains used by RSVP, RSVP will not use the keys with this identifier in all such key chains. This could cause RSVP authentication to fail in some cases.","Update the listed key chain(s) so they use different key identifiers."
"RSVP","5","RSVP_AUTH_KEY_ACL_CHANGE","Key chain [chars] [chars] for [IP_address] because ACL '[chars]' [chars]","The ACL specified in the message text associates the key chain specified in the message text with a set of RSVP neighbors. RSVP uses the specified key chain to authenticate each RSVP message exchanged with that set of RSVP neighbors after the association is configured. Subsequently, the specified ACL has been reconfigured such that the key chain association is no longer valid for one or more RSVP neighbors in the set. This causes RSVP to search the configuration for another suitable key chain to use with those neighbors. If no such key chain is found, RSVP will no longer be able to provide authentication for messages exchanged with those RSVP neighbors. This causes RSVP to discard RSVP messages from that set of neighbors. Because this may ultimately lead to loss of RSVP functionality with those neighbors, RSVP generates this system message. This system message may also be generated if the ACL is subsequently changed so that it reassociates RSVP neighbors with the specified key chain. If RSVP is not using another key chain for the set of RSVP neighbors specified by the ACL, RSVP will begin using the specified key chain to exchange authenticated RSVP messages with that set of RSVP neighbors, potentially restoring RSVP functionality with those neighbors.","If the ACL change unexpectedly caused authentication to be disabled or enabled for one or more RSVP neighbors, undo the ACL change so that RSVP authentication is not impacted."
"RSVP","5","RSVP_AUTH_ONE_KEY_EXPIRED","Key (ID) [int] in chain [chars] has expired","The router has detected that one key in a RSVP key chain has expired and that RSVP has switched to the next unexpired key in that chain.","Update the key chain by changing the text and expiration time(s) for the expired key."
"RSVP_HA","3","CF_REGISTER_FAILED","Failed to register with CF","The system may be low on memory.","Verify system memory availability. Deconfigure graceful restart full mode and configure it again. This will attempt to restart the RSVP HA process and reregister with compact flash (CF)."
"RSVP_HA","3","CLI_ADD_FAILED","Failed to add RSVP HA to CLI","The system may be low on memory.","Verify system memory availability. Deconfigure graceful restart full mode and configure it again. This will attempt to restart the RSVP HA process and reregister with compact flash (CF)."
"RSVP_HA","3","DB_INIT_FAILED","Database init failed","The system may be low on memory.","Verify system memory availability. Deconfigure graceful restart full mode and configure it again. This will attempt to restart the RSVP HA process and reregister with compact flash (CF)."
"RSVP_HA","3","ENTRY_MOVE_FAILED","Failed to move a database entry to [chars] tree","An internal error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RSVP_HA","3","ISSU_INIT_FAILED","In Service Software Upgrade (ISSU) Init failed","The system may be low on memory.","Verify system memory availability. Deconfigure graceful restart full mode and configure it again. This will attempt to restart the RSVP HA process and reregister with compact flash (CF)."
"RSVP_HA","3","ITEM_SIZE_TOO_BIG","Item size ([int]) bigger than default CF buffer ([int])","An internal error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RSVP_HA","3","MAIN_INIT_FAILED","Main init failed","The system may be low on memory.","Verify system memory availability. Deconfigure graceful restart full mode and configure it again. This will attempt to restart the RSVP HA process and reregister with compact flash (CF)."
"RSVP_HA","3","MSG_MGR_INIT_FAILED","Message Manager init failed","The system may be low on memory.","Verify system memory availability. Deconfigure graceful restart full mode and configure it again. This will attempt to restart the RSVP HA process and reregister with compact flash (CF)."
"RSVP_HA","3","PROCESS_CREATE_FAILED","Failed to create RSVP HA process","The system may be low on memory.","Verify system memory availability. Deconfigure graceful restart full mode and configure it again. This will attempt to restart the RSVP HA process."
"RSVP_HA","3","PROCESS_KILL","Killing RSVP HA process","The RSVP HA process is terminating.","No action is required."
"RSVP_HA","3","RF_REGISTER_FAILED","Failed to register with RF","The system may be low on memory.","Verify system memory availability. Deconfigure graceful restart full mode and configure it again. This will attempt to restart the RSVP HA process and reregister with compact flash (CF)."
"RSVP_HA","3","RF_UNREGISTER_FAILED","Failed to unregister with RF","The RSVP HA client may not have registered with RF.","No action is required."
"RS_TDM","3","UNAVAILABLE","A TDM function is used with a bad argument: %s","An internal software error has occurred. A TDM function was called with invalid arguments and could not be processed. The invalid arguments are specified at the end of this error message, along with any other useful data.","Enter the debug tdm command. If the problem recurs, copy the error message, the trace message, and surrounding debug text exactly as they appear on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information."
"RS_TDM","3","UNAVAILABLE","Clash in usage for TDM backplane timeslot %d","The TDM backplane timeslot to be allocated is already in use","Check the split dial-shelf settings on both router shelves for conflicting setting"
"RS_TDM","3","UNAVAILABLE","TDM backplane timeslot %d is in an unknown state","The TDM backplane timeslot specified is in an unknown state","Check the split dial-shelf settings on both router shelves for conflicting setting"
"RS_TDM","3","UNAVAILABLE","TDM extended split on Router shelf Clashes to my %s other %s extended backplane ds0","The number of extended backplane ds0 for this router clashes with the other router shelfError Message    %RS_TDM-3-UNAVAILABLE: TDM legacy split on Router shelf Clashes to my %d other %d legacy backplane ds0 Explanation    The number of legacy backplane ds0 for this router clashes with the other router shelfError Message    %RS_TDM-3-UNAVAILABLE: TDM split on %s Router shelf Reduced to %d backplane ds0 Explanation    The number of backplane ds0 for this router has been forced lowerError Message    %RS_TDM-3-UNAVAILABLE: TDM split user setting are in conflict: my RS %s = %d, other RS %s = %d Explanation    The user setting for tdm split on this router shelf is in conflict with the setting on the other router, More backplane DS0 are in usethan 2048 DS0","Set the other router dial-shelf split backplane-ds0 to non conflicting setting"
"RS_TDM","3","UNAVAILABLE","TDM split user setting are not matched pairs my RS %s = %d ds0, expected other RS %s = %d ds0, actual other RS %s = %d ds0","The user setting for tdm split on this router shelf is not compatible with the setting on the other router","Set the other router dial-shelf split backplane-ds0 to above setting"
"RTT","3","PathSetupFailed","%RTR Probe [int]: Error in setting current Path. Probe will be stopped","An internal software error has occurred.","Reschedule the probe operation that was stopped. Copy the message exactly as it appears on the console or in the system log. Enter the show rtr configuration command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RTT","3","SAAMPLS","IP SLA Monitor([dec]): SAA MPLS [chars] Probe [chars] [chars] for destination-address [IP_address] lsp-selector [IP_address]","This informational message logs violations in the Service Assurance Agent probes. This message appears after the rtr logging trap command has been entered.","If this message is not necessary, enter the no rtr logging trap command to disable logging. Otherwise, no action is required."
"RTT","3","SAANEGATIVEVALUE","IP SLA Monitor([dec]): Negative Value for [chars]","The IP SLA monitor statistics generated an error message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RTT","3","SAANOPROCESS","IP SLA Monitor: Cannot create a new process","The IP SLA monitor is unable to start a new process, and may not be running.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"RTT","3","SAAPROBENOTFOUND","IP SLA Monitor: Error deleting the probe","A deletion attempt was performed on a probe that does not exist.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RTT","3","SAARESPTWINITFAIL","IP SLAs responder initialzation failed","The IP Service Level Agreement (IP SLA) responder initialization process was unable to initialize the timer wheel. As a result, the IP SLA probes on other routers for which this router acts as responder will not work.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RTT","3","SAATWINITFAIL","IP SLAs: Generic Timer wheel timer functionality failed to initialize","IP SLAs could not initialize the timer wheel.","Search for resolved software issues using the Bug Toolkit at Active"
"RTT","4","DuplicateEvent","IP SLA Monitor [dec]: Duplicate event received. Event number [dec]","The IP SLA monitor process has received a duplicate event.","This is only a warning message. If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show rtr configuration command to gather data that may help identify the cause of the error.Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered along with information about the application that is configuring and polling the Service Assurance Agent probes. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RTT","4","OPER_CLOSS","condition %s, entry number = %d","This message displays connection loss conditions in the IP Service Level Agreement (IP SLA) operations. This message is enabled when the ip sla monitor logging trap command is entered.","Ensure that the destination for the IP SLA operation is reachable and that the IP SLA responder operation is configured on the destination. To disable these messages for IP SLA operations, enter the no ip sla monitor logging trap command."
"RTT","4","OPER_TIMEOUT","condition %s, entry number = %d","The timeout condition is displayed for the IP SLA operations. This message is enabled when the ip sla monitor logging trap command is entered.","Ensure that the destination for the IP SLA operation is reachable. To disable these messages for IP SLA operations, enter the no ip sla monitor logging trap command."
"RTT","4","SAACLOCKNOTSET","IP SLA Monitor Probe(s) could not be scheduled because clock is not set.","One or more IP SLA monitor probes could not be scheduled because the system clock is not set.","Ensure that the system clock is functional by using Network Time Protocol or another mechanism."
"RTT","4","SAAGRPSCHEDCONFIGFAIL","Group Schedule Entry [dec]: [chars]","The probes could not be group scheduled. Either the configured starting time has already occurred, or the starting time is invalid.","Reschedule the group scheduling entry with a valid start time."
"RTT","4","SAASCHEDCONFIGFAIL","IP SLA Monitor Probe [dec]: [chars]","The IP SLA Monitor probe could not be scheduled. Either the configured starting time has already occurred, or the starting time is invalid.","Reschedule the failed probe with a valid start time."
"RTT","6","SAATHRESHOLD","IP SLA Monitor([dec]): Threshold [chars] for [chars]","This informational message logs threshold violations in the Service Assurance Agent probes. This messages appears after the rtr logging trap command has been entered.","If this message is not necessary, enter the no rtr logging trap command to disable logging. Otherwise, no action is required."
"RUDP","3","UNAVAILABLE","rudp %d: %s%s.","RUDP initialization operation fails.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"RUDP","4","UNAVAILABLE","rudp %d: %s%s.","A warning is given out for a particular RUDP link.","LOG_STD_DBG_ACTION"
"Regen","1","UNAVAILABLE","System detected OVERTEMPERATURE condition. Putting the system in Power save mode and going to rommon. Please resolve cooling problem and restart system!","The environmental monitor detected a high-temperature condition.","Make sure that the room temperature is not too high and that air flow to the card is not blocked. If this condition persists, the environmental monitor might shut down the system. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"Regen","3","UNAVAILABLE","Can't allocate MAC address for interface %u/%u","All the available MAC addresses for the system have been allocated.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"Regen","3","UNAVAILABLE","Detected invalid NVRAM size: %d bytes","The detected size of NVRAM is not one of the supported sizes.The NVRAM may be bad.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"Regen","3","UNAVAILABLE","Failed to erase config due to internal error","Password protection feature failed to erase config due to internal error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"Regen","3","UNAVAILABLE","Invalid Port Adaptor type (%d) reported for mainboard","The 'virtual' port adaptor type derived from the mainboard type isnot one of the supported types. It may be that this mainboard is a newmainboard type and the software release you are running does not supportthe new mainboard type.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"Regen","3","UNAVAILABLE","PCI Configuration Read Cycle Failed for bus %d, Device %d, function %d, register %d","A PCI Bus Configuration Read cycle failed. The mainboard needs to be replaced.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"Regen","3","UNAVAILABLE","PCI Configuration Write Cycle Failed for bus %d, Device %d, function %d, register %d","A PCI Bus Configuration Write cycle failed. The mainboard needs to be replaced.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"Regen","3","UNAVAILABLE","get_pci_dev_num: Invalid bay (%d) or device number offset (%D)","A software error occurred in trying to determine PCI device addressing. This is most likely a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"Regen","3","UNAVAILABLE","pas_get_device_subunit: Invalid PCI device number: %d","A software error occurred in trying to determine PCI device addressing. This is most likely a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"Regen","3","UNAVAILABLE","regen_big_endian_addr: Attempted conversion of invalid address (0x%x)","A software error occurred in trying to determine PCI device addressing. This is most likely a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"Regen","3","UNAVAILABLE","regen_little_endian_addr: Attempted conversion of invalid address (0x%x)","A software error occurred in trying to determine PCI device addressing. This is most likely a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"Regen_MAINBOARD_ASYNC_PQUICC","3","UNAVAILABLE","No memory for %s of unit %d","The router does not have enough memory to perform the function","Consider adding more shared memory. Copy the error message exactly as it appears, and report it to your technical support representative."
"SASL","2","FORKFAIL","Cannot fork process [chars]","An attempt to fork a process has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SASL","2","INITFAIL","Initialization failed - [chars]","SASL component initialization failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SBETH","1","UNAVAILABLE","%s - Cannot create IDB subblock due to insufficient memory","There was insufficent system memory to create the subblock.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SBETH","1","UNAVAILABLE","%s - Could not install or use IDB subblock","An internal IOS error prevented the IDB subblock from being installed or used.","Software bug - open a case with Development Engineering. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SBETH","1","UNAVAILABLE","Could not init buffer pools","The driver failed to get a pool of buffers from IOS","Software bug - open a case with Development Engineering.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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SBETH","1","UNAVAILABLE","Invalid Interface Descriptor Block","The driver tried to fetch the interface's IDB and failed","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SBETH","1","UNAVAILABLE","MAC Still in Reset","An attempt was made to access the MAC while it was in reset","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SBETH","1","UNAVAILABLE","Plugin function table incomplete or missing","The driver could not access the PA's specific function table","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SBETH","1","UNAVAILABLE","Problem getting particle size","The driver was unable to get the particle size for this interface","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SBETH","1","UNAVAILABLE","Unknown IDBTYPE while starting driver","The IDBTYPE in the interface's instance structure is undefined for this driver","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SBETH","1","UNAVAILABLE","Unknown media-type in subblock","The media-type specified in the driver subblock is invalid","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SBETH","1","UNAVAILABLE","Unknown or invalid chip mode (MII/TBI)","The driver subblock contains an invalid or undefined chip operating mode (MII or TBI mode)","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SBETH","2","UNAVAILABLE","Interface %s does not support ISL","ISL is not supported on the specified interface's hardware.","LOG_STD_NO_ACTION"
"SBETH","3","UNAVAILABLE","%s - GBIC contains a bad EEPROM","Interface contains a GBIC with a bad EEPROM. This causes the link to be down.","Please make sure the GBIC type is compatible with the interface. Verify that the GBIC was obtained from Cisco or a supported vendor"
"SBETH","3","UNAVAILABLE","%s - Unknown GBIC type","Interface contains a GBIC of unknown type. This causes the link to be down.","Please make sure the GBIC type is compatible with the interface. Verify that the GBIC was obtained from Cisco or a supported vendor"
"SBETH","3","UNAVAILABLE","%s, error interrupt, mac_status = 0x%016llx","The MAC controller has signalled an error condition.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SBETH","3","UNAVAILABLE","%s, packet too big (%d), from %e","The interface detects a packet larger than what is defined by MTU","Check the other station's MTU setting LOG_STD_NO_ACTION"
"S4T68360","1","UNAVAILABLE","%s %s","A software or hardware error occurred. The S4T interface is not responding to commands used to initialize it.","This failure will happen due to S4T port initialization or reset failure. Collect the 'show tech' and 'show log' information at the time of problem and send it to the technical support representative"
"S4T68360","1","UNAVAILABLE","%s %s","The S4T port adaptor failed to respond to a request to disable an interface.","This failure will happen due to S4T port initialization or reset failure. Collect the 'show tech' and 'show log' information at the time of problem and send it to the technical support representative"
"S4T68360","1","UNAVAILABLE","Bay %d for microcode download","The S4T port adaptor hardware failed. The S4T port adaptor would not begin to download the operational microcode.","Copy the error message exactly as it appears, and report it to your technical support representative."
"S4T68360","1","UNAVAILABLE","Bay %d port adaptor","The S4T port adaptor hardware failed. The periodic check routine detected the failure and restarted it.","LOG_STD_NO_ACTION"
"S4T68360","1","UNAVAILABLE","Bay %d: %s","The S4T port adaptor failed to complete hardware initialization.","Try to reseat the PA properly in the system slots. If the error still happens, then verify for the hardware failure including the 7200 chasis in case of 7200 or vip in case of RSP and the PA as this error will come only if there is failure in hardware."
"S4T68360","1","UNAVAILABLE","Failed for bay %d, sent = 0x%x, received = 0x%x","The download of the internal firmware to the S4T failed to checksum correctly. This usually indicates a hardware failure of the S4T or the Versatile Interface Processor (VIP).","Perform a power cycle. If the problem persists, the S4T hardware may have a problem."
"S4T68360","1","UNAVAILABLE","Microcode download to bay %d failed","The S4T port adaptor hardware failed. It did not acknowledge the completion of the operational microcode download.","Copy the error message exactly as it appears, and report it to your technical support representative."
"S4T68360","1","UNAVAILABLE","Microcode to port adaptor in bay %d","The S4T hardware has failed. It could not download its operational microcode.","Try to reseat the PA properly in the system slots. If the error still happens, then verify for the hardware failure including the 7200 chasis in case of 7200 or vip in case of RSP and the PA as this error will come only if there is failure in hardware."
"S4T68360","3","UNAVAILABLE","%s packet buffer, pak=0x%x","A software or hardware error occurred. The S4T driver detected that the transmit ring is an inconsistent state.","Do shut/no shut on the interface and if still this problem happens, then do OIR of the PA. If this also doesn't solve the problem then there may be a hardware failure. Please verify for it. send the 'show tech' and 'show log' information collected at the time of problem to the technical support representative"
"S4T68360","3","UNAVAILABLE","Bay %d device ID seen as %#x, expected %#x","The S4T hardware failed. A non-S4T device pointed at the software for the S4T.","Check the system configuration for the failure in the bay number that is reported. If it is not a M4T PA, contact the appropriate component to which that PA in that slot belongs. If it is a M4T PA, then try to reseat the PA once agian and if the error still happens, then send the 'show tech' and 'show log' information to the technical support representative."
"S4T68360","3","UNAVAILABLE","Bay %d stale msg %s- mbx0:%lx, mbx1:%lx, mbx2:%lx","The S4T has not responded to a message from the Versatile Interface Processor (VIP) within a specified time.","Perform a microcode reload of the VIP. If the problem persists, it indicates that the S4T or VIP hardware failed."
"S4T68360","3","UNAVAILABLE","Bay %d, Exception %d, trace %d","The S4T firmware detected an illegal or unexpected CPU exception or condition. This may be caused by a software error or by a hardware failure.","Perform a microcode reload of the Versatile Interface Processor (VIP). If the problem persists, it indicates that the S4T hardware failed."
"S4T68360","5","UNAVAILABLE","%s TX packet dropped; particle count (%d) exceeds %d","The TX packet got dropped since the TX ring was full.","This is normal when the port adapter gets overdriven. LOG_STD_NO_ACTION"
"SARMGR","1","UNAVAILABLE","The 1575 device analysis failed","The SAR Manager failed its initialization","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SARMGR","3","UNAVAILABLE","Device reported %08x","PCI devide ID was not correct.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_DNLD","3","RS_BOOT_RDY_MEM_FAIL","Unable to allocate space for BOOT_READY msg","The remote switch failed to allocate memory for a BOOT READY message to the virtual switch.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_DNLD","3","RS_BOOT_RDY_SEND_FAIL","Unable to send BOOT_READY message","The Remote Switch failed in sending a BOOT READY message to the Virtual Switch.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_DNLD","3","RS_DNLD_BAD_EVENT","Got invalid event [hex]:[hex]","An invalid event was received.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_DNLD","3","RS_DNLD_BAD_QUEUE_EVENT","Event on bad queue [hex]","An unknown message queue event was received.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_DNLD","3","RS_DNLD_BAD_TIMER_EVENT","Invalid timer [hex]","An invalid event was received or the message queue was unknown.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_DNLD","3","RS_DNLD_CREATE_PROC_FAIL","Failed to create image download process","Failed to create a message queue on the remote switch for downloading related messages from the virtual switch.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_DNLD","3","RS_DNLD_CREATE_QUEUE_FAIL","Failed to created watched queue for download messages","Failed to create a message queue on the remote switch for downloading related messages from the virtual switch.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_DNLD","3","RS_DNLD_FAILED","Failed to start download from the Virtual Switch ([chars])","The remote switch was unable to initiate a download from the virtual switch. This could be because of problems in the RSL.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_DNLD","3","RS_DNLD_PROC_FAIL","Download rocess killed. So dropping dnld data","The download process is not running on the remote switch.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_DNLD","3","RS_MSG_ENQUEUE_FAIL","Unable to enqueue message","Failed to enqueue a message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_DNLD","3","VS_BOOT_MSG_INVALID_SWITCH","Invalid switch_id (Internal) [dec] (switch number [dec])! Droppping BOOT_READY msg","An invalid BOOT RDY message was received at the virtual switch.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_DNLD","3","VS_BOOT_RDY_RESP_MEM_FAIL","Unable to allocate memory for BOOT_READY response for [chars] [dec]","The virtual switch failed to allocate memory to send a BOOT READY response message to the remote switch.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_DNLD","3","VS_BOOT_RDY_RESP_SEND_FAIL","Unable to send BOOT_READY response to [chars] [dec]","The virtual switch was unable to send a BOOT READY response message to the remote switch.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_DNLD","3","VS_BOOT_RDY_SCP_RESP_FAIL","scp_send_pak() returned 0 for BOOT_READY resp for [chars] [dec]","The virtual switch was unable to send a valid BOOT READY response message to the remote switch.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_DNLD","3","VS_CREATE_DNLD_INSTANCE_FAIL","Failed to create a download instance for [chars] [dec]","An internal error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_DNLD","3","VS_CREATE_DNLD_PROC_FAIL","Failed to create a download process for [chars] [dec]","An internal error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_DNLD","3","VS_DNLD_IMAGE_INFO_FAIL","Unable to get image info for [chars] [dec]","Failed to get image information for the remote switch from the bundled image.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_DNLD","3","VS_DNLD_IMAGE_VER_INFO_FAIL","Unable to get version for [chars] [dec]","Failed to get image version information for the remote switch from the bundled image.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_DNLD","3","VS_DNLD_UNKNOWN_RS","Unknown RS type [dec] for [chars] sup [dec]","An unknown type of hardware was detected on the remote switch.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_DNLD","3","VS_GET_DNLD_IMAGE_FAIL","Unable to get image for [chars] [dec]","Failed to get image information to be downloaded to the remote switch from the internal database.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_DNLD","3","VS_GET_DNLD_INSTANCE_FAIL","Failed to get the download process instance for Remote Switch","An internal error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_DNLD","3","VS_GET_PSLOT_FAIL","Unable to get the physical slot for the Remote Switch in virtual slot [dec]","Failed to get physical slot for the remote switch.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_DNLD","3","VS_IMAGE_DNLD_FAIL","Image download of size ([dec]) failed for [chars] [dec]","The virtual switch failed to download the image to the remote switch.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_DNLD","3","VS_INVALID_BOOT_MSG","BOOT_READY message in ONLINE state for [chars] [dec]. NAKing","The virtual switch received an invalid BOOT RDY message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_DNLD","3","VS_RS_REGISTRY_ADD_FAIL","[chars] registry addition failed.","Failed to create registries during initialization.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_DNLD","3","VS_SET_DNLD_INSTANCE_FAIL","Failed to set the download process instance for [chars] [dec]","An internal error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_DNLD","3","VS_VLSOT_ALLOC_FAIL","Unable to allocate vslot for [chars] [dec] slot [dec]","Failed to allocate a virtual slot to the remote switch.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_IBC","3","VS_IBC_PVTPOOL_PAKALLOC_FAIL","Unable to allocate Pak from VS Inband Private buffer Pool: [chars] Allocating from Public Buffer Pool","Inband packet allocation could not be done from the virtual switch link (VSL) inband private buffer pool due to the reason stated.","No action is required."
"SATVS_IBC","3","VSL_DOWN_IP_DROP","VSL inactive - dropping cached IP-over-EoBC packet: (SA/DA:[hex]/[hex], eSA/eDA:[enet]/[enet])","The VSL is no longer active. The other virtual switch to which the VSL was attached had one or more IP-over-EoBC packets remaining in the cache after the VSL became inactive (down). The cached IP-over-EoBC packets are being dropped. This condition indicates normal system operation.","No action is required."
"SATVS_IBC","3","VSL_DOWN_SCP_DROP","VSL inactive - dropping cached SCP packet: (SA/DA:[hex]/[hex], SSAP/DSAP:[hex]/[hex], OP/SEQ:[hex]/[hex], SIG/INFO:[hex]/[hex], eSA:[enet])","The VSL is no longer active. The other virtual switch to which the VSL was attached had one or more SCP packets remaining in the cache after the VSL became inactive (down). The cached SCP packets are being dropped.","No action is required."
"SATVS_IBC","5","VSL_DOWN_IPC_DROP","VSL inactive - dropping cached IPC packet: (SA/DA:[hex]/[hex], SEQ:[hex], Pak_pointer: [hex])","The VSL is no longer active. The other virtual switch to which the VSL was attached had one or more IPC packets remaining in the cache after the VSL became inactive (down). The cached IPC packets are being dropped.","This condition does not affect normal system processing. No action is required."
"SATVS_IBC","5","VSL_DOWN_SCP_DROP","VSL inactive - dropping cached SCP packet: (SA/DA:[hex]/[hex], SSAP/DSAP:[hex]/[hex], OP/SEQ:[hex]/[hex], SIG/INFO:[hex]/[hex], eSA:[enet])","The VSL is no longer active. The other virtual switch to which the VSL was attached had one or more SCP packets remaining in the cache after the VSL became inactive (down). The cached SCP packets are being dropped.","This condition does not affect normal system processing. No action is required."
"SATVS_UL_MGMT","3","RS_DNLD_ABORT","Image download aborted because RSL went down","An ongoing remote switch image download was aborted because the remote switch link (RSL) went down. This condition can be caused by any of the following:- The port channel forming the RSL was shutdown.- All members of the port channel have been shutdown.- The cables hooking to all members have been removed.- The remote switch was deconfigured.- The remote switch detected another virtual switch with a a better priority value.","Check for the above conditions and resolve them. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","RS_HW_PROG_TIMEOUT","H/w programming timed out.","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","RS_INVALID_BNDL_EVENT","Bundle event on already bundled port [chars]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","RS_INVALID_BOOL_EVENT","Invalid boolean event [hex]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","RS_INVALID_EVENT","[chars]: Invalid event [hex]:[hex]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","RS_INVALID_UNBNDL_EVENT","Unbundle event on already unbundled port [chars]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","RS_INV_FAILED","Failed to send inventory data to Virtual Switch. Will keep trying","The remote switch failed to send inventory data to the virtual switch even though the RSL is up. It will keep trying forever.","Wait 10 minutes for the system to recover from this condition. If the system does not recover, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","RS_NO_PORT_BNDL_NUMBER","No bundle port number in RSL -- SI set to BIT BUCKET","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","RS_NO_UPLINK","No uplink to master core -- SI set to BIT BUCKET","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_DEALLOC_VSLOT_MSG_FAIL","[chars] for VS UL dealloc vslot msg [dec]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_DROP_INV_MSG","Dropping Inventory message from unknown Remote Switch number [dec] switch-id(Internal) [dec]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_DUP_INV_MSG","NAKing duplicate inventory from Remote Switch number [dec] switch-id(Internal) [dec]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_GET_PSLOT_FAIL","Unable to get the physical slot of supervisor for [chars] [dec]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_GET_SWITCH_NUMBER_FAIL","Unable to get switch number for switch-id(internal) [dec]","Failed to get switch number from internal switch ID. An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_ICC_REQ_FAIL","Unable to alloc memory for status update message for [chars] [chars]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_ICC_RESP_FAIL","icc_get_resp_pak failed","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_ICC_RESP_UPLINK_STATUS_FAIL","icc_req_resp_pak to SP failed for [chars] [chars]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_INVALID_BNDL_EVENT","Bundle event on already bundled port [chars] for switch number [dec] switch-id(Internal) [dec]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_INVALID_UNBNDL_EVENT","Unbundle event on already unbundled port [chars] for switch number [dec] switch-id(Internal) [dec]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_INV_FAILED","Failed to process inventory data for Remote Switch [dec]. Will remain OFFLINE","The virtual switch is unable to process the inventory data received from the remote switch even though the RSL is up. This switch will be held offline.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_INV_VER_MISMATCH","Versin of INVENTORY message mismatch. Forcing download to switch number [dec] switch-id(internal) [dec]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_NO_INFO_EM_RECOVERY","No PM info on EM recovery for port [chars]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_NON_INV_MSG","Dropping non-INVENTORY message.","A non-inventory message was received from the remote switch.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_NON_RSL_EM_AGE","EM aging event on non-RSL port [chars]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_NO_SWIDB_EM_AGE","No swidb for EM aging event (gpid = [dec])","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_NO_SWIDB_EM_RECOVERY","No swidb for EM recovery event (gpid = [dec])","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_ADD_PORT_AGPORT_FAIL","Unable to add port [chars] to RSL.","A failure occurred while attempting to add the port to the RSL.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_ADD_TLV_FAIL","Too few bytes for [chars] TLV in PAgP (reqd. [dec], got [dec]) on port [chars]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_BAD_SUB_OPCODE","Dropping bad sub opcode ([hex]) from [chars] [dec]","An invalid message was received from the remote switch. The message could be corrupted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_BAD_VER_STR","Bad version string - inventory failed","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_CF_CLIENT_ADD_FAIL","CF: Failed to create client (err_code = [hex])","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_CF_INVALID_SYNC","CF: TLV sync for unconfigured port ([chars])","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_CHKPT_INVALID_SYNC","CF: Received invalid sync type [hex]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_CHKPT_MSG_FAIL","CF: Send FAIL status","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_CHKPT_MSG_MEM_FAIL","CF: Unable to get chkpt buffer for sync type [hex] (retval [hex])","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_CHKPT_MSG_SEND_FAIL","CF: Unable to sync type [hex] to standby (retval [hex])","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_CLEAR_LTL_INDEX","Unable to clear LTL index [hex] (retval [hex])","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_CREATE_BOOL_FAIL","Failed to create watched boolean to monitor uplink comm up","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_CREATE_PROC_FAIL","Failed to create the [chars] process","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_CREATE_QUEUE_FAIL","Failed to create watched queue for [chars]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_ENQUEUE_FAIL","Unable to enqueue unsolicited message","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_GET_LTL_PORT_INDEX","Unable to get LTL index for port [chars] (retval [hex])","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_GET_OID_FAIL","Failed to get OID - inventory failed","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_GET_UPLINK_INFO_FAIL","Failed to get uplink info for port [chars]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_ICC_REQ_FAIL","RP-SP sync: Unable to get memory for RP-SP sync type [hex]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_IGNORE_ICS_TLV","Ignore ICS TLV on non-uplink port [chars]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_IMAGE_NOT_FOUND","The system failed to find an image to download to Remote Switch [dec]. Will remain OFFLINE","The virtual switch failed to find an image for the remote switch. The remote switch will remain offline.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_IMAGE_NOT_FOUND_INV_RESP","Remote Switch image NOT found in Virtual Switch","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_INVALID_ARGS","Both [chars] [dec] and idb for port ([chars]) specified","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_INVALID_BOOL_EVENT","Invalid [chars] boolean event [dec]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_INVALID_EVENT","Invalid [chars] event [dec]:[dec]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_INVALID_ICS_TLV","Invalid ICS TLVs from port [chars]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_INVALID_QUEUE_EVENT","Event on invalid [chars] queue [dec]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_INVALID_SW_ID","Invalid switch-id(Internal) [dec]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_INVALID_SWITCH_INFO","switch number [dec] has no switch_info","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_INVALID_TIMER_ID","Invalid [chars] timer [dec]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_INVALID_TLV","Received [chars] TLV on non-uplink port [chars]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_INVALID_TLV_RS","Received Remote Switch side UL mgmt TLV on Remote Switch on port [chars]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_INVALID_TLV_VS","Received Virtual Switch side UL mgmt TLV on Virtual Switch on port [chars] for [chars] [dec]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_INVENTORY_FAIL","Out of memory - inventory failed","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_INV_RESP_FAIL","Failed sending INVENTORY response [chars]to [chars] [dec]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_INV_RESP_MEM_FAIL","Alloc failure for INVENTORY response to switch number [dec] switch-id(Internal) [dec]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_INV_SEND_FAIL","Inventory:scp send failed - session [dec]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RSL_BOUNCE","Remote switch [dec] OFFLINE since RSL bounced","The remote switch is now offline because the remote switch link (RSL) was bounced. This condition can be caused by any of the following:- An SSO switchover resulted in failures on the RSL line cards that required the RSL to be bounced.- The remote switch failed to respond to a sanity check request after an SSO switchover.","Check for the above conditions. Note that the first condition can occur when the switchover happens during a critical operation on the RSL line card. If this is not the case, or if the second condition occurred, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_LTL_ALLOC_FAIL","Dynamic allocation also failed for Remote Switch private indices (retval [hex])","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_MAX_INV_OID_SIZE","OID too long ([dec]) - inventory failed","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_NAK_INV_RESP","Virtual Switch NAKed Inventory.","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_NON_RSL_CONN_INFO_REQ","Dropping non-RSL connect info request message","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_NON_UPLINK_PORT_RM","Attempt to remove port [chars] that is not an uplink of [chars] [dec]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_NO_RS_INFO_INV_SYNC","CF: No Remote Switch info for inventory sync for [chars] [dec]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_NO_RS_INFO_STATE_SYNC","CF: No Remote Switch info for state sync for [chars] [dec]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_NOT_ENOUGH_PRIVATE_INDICES","Not enough private indices (reqd [dec], got [dec]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_NULL_RP_SP_SYNC_MSG","RP-SP sync: Received NULL sync msg","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_NULL_SWIDB","Unable to get swidb for port [dec]:[dec].","The specified port has a null software interface descriptor block.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_PO_AGG_RS_OFFLINE","Port [chars] aggregated but switch-id(InternaL) [dec] OFFLINE","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_PORT_ADD_REMOVE_ERR","Port ([chars]) add/remove from unconfigured [chars] [dec]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_REGISTRY_ADD_FAIL","[chars] registry addition failed","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_RF_CLIENT_ADD_FAIL","RF: Failed to create client (retcode = [hex])","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_RSL_CONN_INFO_RESP_FAIL","No RSL connect info info response received from [chars] [dec]","The RSL connect information response was not heard from the remote switch. This could be due to an invalid switch number, or the virtual switch may not be actively connected to the remote switch at this time.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_RSL_CONN_INFO_RESP_MSG_FAIL","Unable to alloc memory for RSL connect info response","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_RSL_CONN_REQ_MEM_FAIL","Unable to allocate memory for sending RSL connect info request to [chars] [dec]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_RSL_CONN_RESP_SEND_FAIL","Sending RSL connect info response failed.","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_RSL_LTL_INDEX_FAIL","Unable to get the local RSL LTL index","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_SET_LTL_INDEX","Unable to [chars] index [hex] on supervisor [chars] [chars] (retval [hex])","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_SET_PORT_LTL_INDEX","Unable to set LTL index for port [chars] to [hex]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_SET_RSH_MODE","Unable to set RSH mode on port [chars].","The system failed to set RSH mode.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_SET_SRC_INDICES_FAIL","Failed to [chars] SCP msg to set src indices.","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_SSO_EVENT","SSO switchover event in oir_online (slot [dec])-- not supported in Remote Switch","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_TLV_INVALID_METRIC","ICS TLV on [dec] with invalid metric on port [chars]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_RS_VSLOT_ALLOC_FAIL","Unable to alloc vslot for switch number [dec] switch-id(Internali) [dec] slot [dec]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","3","VS_UNKNOWN_MSG","Unknown message type [dec]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","4","RS_RS_MISMATCH","Virtual switch indicates software mismatch. Requesting download","Because the software running on the remote switch does not match that in the virtual switch, the proper image will be downloaded.","The image download is automatic. If it fails to complete, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","4","RS_RS_OFFLINE","Remote switch OFFLINE since RSL went down","The remote switch is now offline because the remote switch link (RSL) went down. This condition can be caused by any of the following:- The port channel forming the RSL was shutdown.- All members of the port channel have been shutdown.- The cables hooking to all members have been removed.- The remote switch was deconfigured.- The remote switch detected another virtual switch with a a better priority value.","Check for the above conditions and resolve them. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","4","VS_GET_PM_COOKIE_FAIL","RF: Unable to get cookie for port [chars]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","4","VS_RS_MAX_UPLINKS_CONF","Attempt to add port [chars] to [chars] [dec] that already has [dec] uplinks to it","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","4","VS_RS_MISMATCH","Remote switch [dec] software version mismatch. Forcing download","Because the software that is running on the remote switch does not match the software that is running on the virtual switch, matching software will be downloaded to the remote switch.","The image download is automatic. If it fails to complete, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","4","VS_RS_OFFLINE","Remote switch [dec] OFFLINE since RSL went down","The remote switch is now offline because the remote switch link (RSL) went down. This condition can be caused by any of the following:- The port channel forming the RSL was shutdown.- All members of the port channel have been shutdown.- The cables hooking to all members have been removed.- The remote switch was deconfigured.- The remote switch detected another virtual switch with a a better priority value.- The remote switch was powered off.- The remote switch rebooted.","Check for the above conditions and resolve them. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","4","VS_RS_REG_READ_FAIL","Unable to read register [hex] of port [chars]","The virtual switch failed to read the port adapter registers to verify that RSH is enabled on them.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","4","VS_RS_RS_CONF","Attempt to [chars]-configure [chars] [dec]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","4","VS_RS_VLAN_BLOCK","Unable to [chars] VLANS [hex] - [hex] for [chars]","The system could not block or unblock a range of VLANs.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","5","RS_ICS_SWITCHOVER","ICS swtichover due to priority change on RSL member [chars] from Virtual Switch [enet]","The remote switch has detected a priority change at the virtual switches and will do an ICS switchover to a new virtual switch. All RSL members, except the one from which the priority change was detected, will be bounced to allow faster detection of this situation at the virtual switches.","This is an informational message. No action is required."
"SATVS_UL_MGMT","5","RS_RSL_DOWN","RSL is DOWN","The remote switch link is down.","This is an informational message. No action is required."
"SATVS_UL_MGMT","5","RS_RSL_UP","RSL is UP","The remote switch link is up.","This is an informational message. No action is required."
"SATVS_UL_MGMT","5","RS_RSL_UP_INV","RSL is UP. Sending inventory data","The remote switch link is up. The remote switch is sending inventory data to the virtual switch.","This is an informational message. No action is required."
"SATVS_UL_MGMT","5","RS_RS_ONLINE","Remote switch is ONLINE. Exporting line card data to Virtual Switch","The remote switch is now online. The virtual switch will now look for line cards on the remote switch and try to bring them online.","This is an informational message. No action is required."
"SATVS_UL_MGMT","5","VS_RSL_UP","RSL to Remote Switch [dec] is UP. Waiting for inventory data","The remote switch link is up and waiting for inventory from the remote switch.","This is an informational message. No action is required."
"SATVS_UL_MGMT","5","VS_RS_ONLINE","Remote switch [dec] ONLINE. Looking for line cards on it","The remote switch is now online. The virtual switch will now look for line cards on the remote switch and try to bring them online.","This is an informational message. No action is required."
"SATVS_UL_MGMT","6","RS_RSL_MEMBER_BOUNCE","RSL member [chars] bounced due to unbundle action","The RSL member was bounced after it became unbundled.","This is an informational message. No action is required."
"SATVS_UL_MGMT","6","RS_VS_RSL_BOUNCE","RSL members to the active Virtual Switch bounced as RSL went down","Because the remote switch link (RSL) is down, all members to the same virtual switch are bounced to allow the virtual switch to recognize the RSL down condition.","This is an informational message. No action is required."
"SATVS_UL_MGMT","6","VS_RS_INVALID_RP_SP_SYNC_TYPE","RP-SP sync: Received invalid sync type [hex]","An internal RP-SP synchronization error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_UL_MGMT","6","VS_RSL_MEMBER_BOUNCE","RSL member [chars] bounced due to unbundle action","The remote switch link (RSL) member was bounced after it became unbundled.","This is an informational message. No action is required."
"SATVS_WARM_UPGRADE","3","VS_RS_BAD_SUB_OPCODE","(WUG)Dropping bad sub opcode ([hex]) from [chars] [dec]","Received an invalid message from the remote switch. The message could be corrupted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_WARM_UPGRADE","3","VS_RS_INVALID_EVENT","Invalid [chars] event [dec]:[dec]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_WARM_UPGRADE","3","VS_RS_INVALID_QUEUE_EVENT","Event on invalid [chars] queue [dec]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_WARM_UPGRADE","3","VS_RS_WUG_RESP_FAIL","Failed sending WARM_UPGRADE response [chars]to [chars] [dec]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_WARM_UPGRADE","3","VS_RS_WUG_RESP_MEM_FAIL","Alloc failure for WARM_UPGRADE_RESP to switch-id(Internal) [dec]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_WARM_UPGRADE","3","VS_RS_WUG_SEND_FAIL","WUG start:scp send failed","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SATVS_WARM_UPGRADE","3","VS_RS_WUG_TEST","Test msg_satvs_warm_upgrade","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SBFIFO","1","BAD_IDB","Invalid Interface Descriptor Block","The driver failed to get the interface descriptor block (IDB).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SBFIFO","1","BAD_PARTICLE","Problem getting particle size","The driver was unable to obtain the particle size for this interface.","This is a software bug. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SBFIFO","1","BAD_POOL","Could not init buffer pools","The driver failed to obtain a pool of buffers from the Cisco IOS software.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SBFIFO","1","BAD_SB_NOMEM","[chars] - Cannot create IDB subblock due to insufficient memory","There was insufficient system memory to create the subblock.","The router requires more main memory. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SBFIFO","1","BAD_STRUCT","Could not initialize structure","The driver failed to initialize a structure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SBFIFO","1","BAD_SUBBLOCK","[chars] - Could not install or use IDB subblock","An internal Cisco IOS error prevented the IDB subblock from being installed or used.","This is a software bug. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SBFIFO","1","IDBTYPE_UNK","Unknown IDBTYPE while starting driver","The IDBTYPE in the interface's instance structure is undefined for this driver.","This is a software bug. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SBFIFO","1","INITFAIL_NOMEM","[chars], initialization failed, no buffer memory","The Ethernet port initialization failed due to insufficient memory. The router requires more packet memory.","Consider a system upgrade. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SBFIFO","1","MODE_INVALID","Unknown or invalid chip mode (MII/TBI)","The driver subblock contains an invalid or undefined chip operating mode (MII or TBI mode).","This is a software bug. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SBFIFO","1","RESET","MAC-FIFO Still in Reset","An attempt was made to access the MAC-FIFO while it was in reset.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SBFIFO","3","ERRINT","[chars], error interrupt, mac_status = [hex]","The MAC-FIFO controller signalled an error condition.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SBFIFO","3","TOOBIG","[chars], packet too big ([dec]), from [enet]","The interface detects a packet larger than the value that is defined by MTU.","Determine the MTU setting of the other station. No action is required."
"SCCP","0","UNAVAILABLE","%s","Unrecoverable Internal Panic","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SCCP","2","UNAVAILABLE","%s","Critical Conditions","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SCCP","3","UNAVAILABLE","%s","Errors","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SCCP","4","UNAVAILABLE","%s","Warning","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SCCP","5","UNAVAILABLE","%s","Notice","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SCCP","6","UNAVAILABLE","%s","Informational","LOG_STD_NO_ACTION"
"SCHED","0","UNAVAILABLE","Interrupt of level %ld running for a long time.%s","The indicated Interrupt Service Routine ran for more than 2 minuteswithout relinquishing control and so caused the system to reset","When reporting this message, copy the message text exactly as it appears; include the stack trace; and report it to your technical support representative."
"SCHED","0","UNAVAILABLE","Scheduler running for a long time, more than the maximum configured (%ld) secs.%s","Scheduler was running for a long time and so caused the system to reset","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SCHED","2","UNAVAILABLE","%s attempted to unlock an unlocked semaphore","Some sections of code use semaphores to protect critical sections of software. This message indicates that an attempt was made to unlock a semaphore that was not locked.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SCHED","2","UNAVAILABLE","%s attempted to unlock semaphore owned by %s.","Some sections of code use semaphores to protect critical sections of software. This message indicates that an attempt was made to unlock a semaphore that was not owned by the process attempting to unlock it.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SCHED","2","UNAVAILABLE","%s timer %x not being watched.","A process can register to be notified when various events occur in the router. This message indicates that an attempt was made to deregister a timer expiration event that is not currently registered.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SCHED","2","UNAVAILABLE","Attempt to %s attribute %s on process %d.","Each process has various public and private attributes associated with it. This message indicates that an attempt was made to set or get a private attribute belonging to another process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SCHED","2","UNAVAILABLE","Attempt to %s unknown process attribute %d.","Each process has various attributes associated with it. This message indicates that an attempt was made to set or get a nonexistent process attribute.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SCHED","2","UNAVAILABLE","Attempt to delete non-empty watched queue %s (address %x).","A process can register to be notified when various events occur in the router. This message indicates that an attempt was made to destroy a queue that still contained items. These items are lost and not returned to free memory.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SCHED","2","UNAVAILABLE","Attempt to set %s priority on process %d (%s)","Each process executes at a specified priority level. Higher priority processes must use the new scheduler primitives, while lower priority processes can use primitives from either the new or old scheduler. This message indicates that an attempt was made to set the specified priority too high for a process using old scheduler primitives.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SCHED","2","UNAVAILABLE","Attempt to set bad %s value (%x) on process %d","Each process has various attributes associated with it. This message indicates that an attempt was made to set the specified attribute to an invalid value.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SCHED","2","UNAVAILABLE","Critical/high priority process %s may not dismiss.","Each process executes at a specified priority level. Higher priority processes must use the new scheduler primitives, while lower priority processes can use primitives from either the new or old scheduler. This message indicates that a higher priority process attempted to use an old scheduler primitive.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SCHED","2","UNAVAILABLE","Key (%s) does not match key (%s) of process (%d) in process_send_message request","An attempt was made to send a message to a process. The key associated with that process did not match the key in the message. This usually means an incorrect process id was used in the send message request.","Copy the error message exactly as it appears; include the stack trace; and report it to your technical support representative. If this message recurs, revert to an IOS image that did not exhibit this behavior."
"SCHED","3","UNAVAILABLE","%s attempted to lock a semaphore, already locked by itself","Some sections of code use semaphores to protect critical sections of software. This message indicates that an attempt was made to lock a semaphore that was already locked.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SCHED","3","UNAVAILABLE","Illegal priority (%d) specified for process %s.","Each process executes at a specified priority level. Higher priority processes must use the new scheduler primitives, while lower priority processes can use primitives from either the new or old scheduler. This message indicates that an attempt was made to set the specified process to a priority level that is not allowed for the type of scheduler primitives used.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SCHED","3","UNAVAILABLE","Illegal stack size (%d) specified for process %s.","Each process has its own stack space, which must be one of several predefined sizes. This message indicates that an attempt was made to specify an illegal stack size.","Copy the error message exactly as it appears; include the stack trace; and report it to your technical support representative. If this message recurs, revert to a previous IOS image that did not exhibit the problem."
"SCHED","3","UNAVAILABLE","Invalid scheduler action (%s) at interrupt level","This message indicates that a process_set_wakeup_reasons was attempted from an interrupt handler.","If this message recurs, call your technical support representative for assistance."
"SCHED","3","UNAVAILABLE","Low memory modified by %s (%#x = %#x)","In all Cisco products, the first 256 bytes of memory are unused and are off limits. Newer platforms have hardware to immediately trap reads or writes to this area. Older platforms periodically check this memory. This message appears only on older platforms and indicates that this off-limits memory area was modified.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SCHED","3","UNAVAILABLE","Process received unknown event (maj %x, min %x).","A process can register to be notified when various events occur in the router. This message indicates that a process received an event it did not know how to handle.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SCHED","3","UNAVAILABLE","Process still watching %s %s","A process can register to be notified when various events occur in the router. This message indicates that a process destroyed a set of events without first individually removing each event in the set.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SCHED","3","UNAVAILABLE","Process still watching %s timer %x","A process can register to be notified when various events occur in the router. This message indicates that a process destroyed a set of events without first individually removing each event in the set.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SCHED","3","UNAVAILABLE","Process thrashing on watched %s.","A process can register to be notified when various events occur. This message indicates that the indicated process relinquished control 50 consecutive times and there were still outstanding events to be processed.","Copy the error message exactly as it appears, include the stack trace; and report it to your technical support representative."
"SCHED","3","UNAVAILABLE","Queue event for unknown queue (index %d).","A process can register to be notified when various events occur in the router. This message indicates that a process received a queuing event for an unknown queue.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SCHED","3","UNAVAILABLE","Scheduler '%s' corrupted by process %s (expected %x, found %x)","The scheduler has determined that its data structures were corrupted during the execution of the current process. This corruption is the result of either the actions of the process (multiple errors reported against the same process) or an interrupt driver (multiple errors reported against different processes).","This message is a sign of memory corruption. Copy the error message text exactly as it appears; include the stack trace; and report it to your technical support representative. Reset the system. If this message re-occurs, revert to a previous release of IOS."
"SCHED","3","UNAVAILABLE","Sleep with expired managed timer %x, time %#Ta (%TE ago).","A process can register to be notified when various events occur. This message indicates that a registered timer has expired and its value is unchanged after the process has received control twice.","Copy the error message exactly as it appears, include the stacktrace; and report it to your technical support representative. Reset the system. If the error recurs, revert to a previous IOS image that did not exhibit the problem."
"SCHED","3","UNAVAILABLE","Sleep with expired timer %x, time %#Ta (%TE ago).","A process can register to be notified when various events occur. This message indicates that a registered timer has expired and its value is unchanged after the process has received control twice.","Copy the error message exactly as it appears; include the stack trace; and report it to your technical support representative."
"SCHED","3","UNAVAILABLE","Unknown message %x received (ptr arg %x, num arg %x).","A process can register to be notified when various events occur in the router. This message indicates that a process received a message from another process that it does not know how to handle.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SCHED","3","UNAVAILABLE","Unknown timer expiration, timer = %x, type %d.","A process can register to be notified when various events occur in the router. This message indicates that a process received a timer expiration event for an unknown timer.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SCHED","3","UNAVAILABLE","Wakeup information for process %s lost (maj %x, min %x).","A process can register to be notified when various events occur in the router. This message indicates that an event for the specified process was lost and that the system might not be functioning correctly.","Copy the error message text exactly as it appears; include the stack trace; and report it to your technical support representative. Reset the system."
"SCHED","4","UNAVAILABLE","Invalid argument (%d msec) for process_set_schedtime","This message indicates that there was an attempt to change the maximum time a process can run per scheduling to an invalid value. The value should range between 20msec to 200msec","Copy the error message exactly as it appears; include the stack trace; and report it to your technical support representative. If this message recurs, revert to an IOS image that did not exhibit this behavior."
"SCHED","7","UNAVAILABLE","Attempt to %s uninitialized watched %s (address %x).","A processes can register to be notified when various events occur. This message indicates that an attempt was made to register for an event without first creating the data structure for that event.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SCP","1","TASK_CREATE_FAIL","Failed to create SCP Generic Unsolicited message handler task","The system could not spawn a process that handles certain types of incoming SCP packets. This could be due to low memory on the switch, in which case other related errors may appear.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SCP","2","NOMEM","No memory available for %s","The SCP protocol subsystem could not obtain the memory it needed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SCP","2","NOTREG","Process %d(%s) not registered for SCP","The SCP application cannot send an SCP message because it has not registered for a SAP.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SCP","2","TOO_MANY_SAP","Not enough space to register process %d(%s) for SCP","The SCP application cannot register for a SAP because all possible numbers have been assigned.","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. With some messages, these tools and utilities will supply clarifying information. Search or resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SCP","3","ETHERTYPE_FAIL","Ethertype configuration on module [dec], port [dec], failed with return code [hex]","The EtherType configuration failed on the specified port. This usually means that the module hardware does not support the EtherType configuration. The return error code provides more information.","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. With some messages, these tools and utilities will supply clarifying information. Search or resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SCP","3","SCP_FAILURE","SCP Opcode:%d Module: %d returned error 0x%x","Serial Control/Communications Protocol (SCP) operation performed by RP/SP to communicate with the module failed.","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. With some messages, these tools and utilities will supply clarifying information. Search or resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SCP","3","SCP_HA_FAIL","SCP HA Seq Set - Module: [dec] failed [dec] times","The system did not receive the SCP HA sequence set acknowledgment.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SCP","4","DACK_TIMEOUT_MSG","SCP delivery ack timeout for opcode=%x","RP didn't receive SCP delivery acks from SP even after 2 retries.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SCP","4","GET_PAK_MSG","Failed for message size=%d","System is out of pak type buffers of required size.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SCP","4","UNK_OPCODE","Received unknown unsolicited message from src_addr [hex], dest_addr [hex], length [dec], dsap [dec], ssap [dec], opcode [hex]","An unsupported SCP message was sent to this processor.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SCP","5","ASYNC_WATERMARK","[dec] messages pending in [chars]","The specified number of SCP messages are waiting in the specified local queue. This condition might indicate that the SP is generating many messages, that the SP is too busy to send them, or that the module cannot process them at a faster pace. In most cases, this condition occurs when there is heavy control plane activity, such as the formation of Layer 2 trunks, the addition of new VLANs, or the toggling of links.","Determine if the SP is busy or if there is interface link toggling. If this condition persists for more than five minutes, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SCP","5","ENABLE","Module enabled [chars]","The supervisor engine sent a message to the router to indicate that a module has been enabled.","No action is required."
"SCPLIB","2","NO_JID","Could not get my job id. pid %d","Could not get my job id","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SCPLIB","2","SCPP_NOT_READY","The SCP proxy in the ios-base process is not ready. my jid/pid %d/%d","The SCP Proxy in the ios-base process is not ready.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SDLC","2","UNAVAILABLE","%s, illegal state for addr %02x, %s(%d)","An internal SDLC state violation was detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SDLC","2","UNAVAILABLE","AW_SDLC_SEC with no sdllc_llc pointer.","An error condition occurred during SDLLC initiation.","No action is required. The SDLLC session will restart without operator intervention."
"SDLC","2","UNAVAILABLE","No memory available: %s","The requested operation failed because of a low memory condition.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"SDLC","3","UNAVAILABLE","%s, DLU failed to close station %02x before re-opening, %s/%s","A hardware or software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SDLC","3","UNAVAILABLE","%s, addr %02x, Sent SNRM, received SNRM. Check link station roles.","A hardware or software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SDLC","3","UNAVAILABLE","Input idb not set","This is a software error. A frame was given to the SDLC handler to process, but the interface on which the frame arrived is not known.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SDLC","3","UNAVAILABLE","Interface %s, NULL packet ptr, rvr %d, vs %d, vr %d","An internal software error occurred in the router's SDLC processing system.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SDLC","4","UNAVAILABLE","%s, XID mismatch for %02x. CONNECTION REJECTED","An inbound exchange identification (XID) from a PU 2.0/PU 2.1 node was rejected. The targeted SDLC address is displayed. The XID information is displayed in a subsequent message = SDLLC-6-XID_DISPLAY or SDLLC-6-FORMAT.","This is a security feature. Additional information is displayed to help trace the source of the rejected XID. If the message is undesirable, simply remove the XID statement from the router configuration."
"SDLC","4","UNAVAILABLE","%s, Received bad SDLC %sframe, address %02x, control %2X","A hardware or software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SDLC","4","UNAVAILABLE","%s, addr %02x received command %02x in response to SNRM, expected UA","The router received a frame other than a UA in response to a SNRM.","Check the end station to see if the SNA stack is up and running."
"SDLC","4","UNAVAILABLE","Dropped SDLC packet from SDLC hold queue","An SDLC frame had to be dropped from the output hold queue, usually because of excessive congestion on the output link.","If this message occurs frequently, determine why your SDLC link is being overloaded with data and resolve the cause (typically by either increasing bandwidth to your SDLC line or reducing the load on your link)."
"SDLC","4","UNAVAILABLE","Interface %s, Frame error: CF %#x, VS %d %c VR %d, Reason %#x","A FRMR frame was received. This can be due to a noisy serial line, an overloaded SDLC device, or corrupted data.","If this message recurs, service the serial line and the devices attached to it."
"SDLC","4","UNAVAILABLE","Interface %s, Info field not permitted","A bad SDLC frame was received.","If this message recurs, check the SDLC serial line and the devices attached to it."
"SDLC","4","UNAVAILABLE","Interface %s, Invalid NR value","A bad SDLC frame was received.","If this message recurs, check the SDLC serial line and the devices attached to it."
"SDLC","4","UNAVAILABLE","Interface %s, Invalid control field","A bad SDLC frame was received.","If this message recurs, check the SDLC serial line and the devices attached to it."
"SDLC","4","UNAVAILABLE","Interface %s, N1 too large","An information frame was received from the other end of the SDLC link that was larger than allowed with the N1 parameter on this link.","Either increase the value of the N1 parameter for this interface on the router or reduce the size of the maximum information frame sent by the other end of the link."
"SDLC","4","UNAVAILABLE","Interface %s, ignoring group-poll mismatch, UPOLL %02x","A hardware or software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SDLC","4","UNAVAILABLE","SDLC_ERROR with no poll","A protocol error was detected on a secondary station, but FRMR could not be sent because the station did not own the poll bit. This message indicates either poor line conditions or a faulty SDLC implementation.","If this message recurs, run traces on the SDLC line. Copy the error message exactly as it appears, and report it to your technical support representative."
"SDLC","5","UNAVAILABLE","Interface %s, not configured for group-poll frame, received %02x","An unnumbered poll (UP) was received with the wrong group poll address.","Make sure the group poll address configured on the router matches the one configured in the physical unit macro (GP3174=XX) in the Network Control Program (NCP) generate file."
"SDLC","6","UNAVAILABLE","sa %e da %e ss %x ds %x [%02x%02x%02x%02x]","This message supplies the information for the received and rejected XID.","See the SDLC-6-XID_NOMATCH error message."
"SDLC","6","UNAVAILABLE","Unsupported XID format received, format %d","An inappropriate exchange identification (XID) format was received for this mode of SDLLC operation. Review the type of devices you are connecting with SDLLC to make sure they are supported.","See the SDLLC-6-XID_NOMATCH error message."
"SDLLC","5","UNAVAILABLE","SDLLC: %s LINK address %02x ACTIVATED: %s","An SDLLC media conversion session was activated.","LOG_STD_NO_ACTION"
"SDLLC","5","UNAVAILABLE","SDLLC: %s LINK address %02x DEACTIVATED: %s","An SDLLC media conversion session was deactivated. If deactivation is a result of an error condition, this message will include a reason.","If the message does not include a description of an error, the deactivation was normal and the message is for information only. If the message does include a description of an error, begin problem analysis. Determine whether session loss is related to LLC2 timers by issuing the debug llc2-err command. If the problem is related to LLC2 timers, consider using SDLLC with the local acknowledgment feature. Copy the error message exactly as it appears, and report it to your technical support representative."
"SDM","6","MISMATCH_ADVISE","[chars]","This message provides information regarding an SDM mismatch.","No action is required."
"SEC_LOGIN","1","QUIET_MODE_ON","Still timeleft for watching failures is [int] secs, [user: [chars]] [Source: [IP_address]] [localport: [int]] [Reason: [chars]] [ACL: [chars]] at [chars]","Quiet mode is now on. No request for connections are now accepted other than those allowed by the ACL, if the ACL is configured for the blocking period. An implicit deny all of any logins will be in effect.","Because all requests from other sources are blocked, check the ACL and add any source addresses as necessary."
"SEC","2","UNAVAILABLE","Box secured, no option on internal packet","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SEC","2","UNAVAILABLE","First opt in tcb not BASIC security","An internal software error occurred.","If this message recurs, contact your technical support representative."
"SEC","2","UNAVAILABLE","Security opt in tcb not SECINSERT","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SEC","3","UNAVAILABLE","No default for NLESO defined","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SEC_LOGIN","4","25","Login failed [user: [chars]] [Source: [IP_address]] [localport: [int]] [Reason: [chars]] at [chars]","A user name or password is invalid.","Specify a vaild user name or password."
"SEC_LOGIN","5","LOGIN_SUCCESS","Login Success [user: [chars]] [Source: [IP_address]] [localport: [int]] at [chars]","Login has succeeded.","No action is required."
"SEC_LOGIN","5","QUIET_MODE_OFF","Quiet Mode is OFF, because [chars] at [chars]","Quiet mode is now off. The router is now operating in normal connection processing mode. The reason for the change is specified in the message text.","No action is required."
"SEC","6","UNAVAILABLE","access-list logging rate-limited or missed %d packet%s","Some packet matching logs were missed because the access list log messages were rate-limited or no access list log buffers were available.","LOG_STD_NO_ACTION"
"SEC","6","UNAVAILABLE","list %s %s %d %i %s- %i, %d packet%s","A packet matching the log criteria for the given access list was detected.","LOG_STD_NO_ACTION"
"SEC","6","UNAVAILABLE","list %s %s %i %d packet%s","A packet matching the log criteria for the given access list was detected.","LOG_STD_NO_ACTION"
"SEC","6","UNAVAILABLE","list %s %s %s %i %s- %i (%d/%d), %d packet%s","A packet matching the log criteria for the given access list was detected.","LOG_STD_NO_ACTION"
"SEC","6","UNAVAILABLE","list %s %s %s %i %s- %i, %d packet%s","A packet matching the log criteria for the given access list was detected.","LOG_STD_NO_ACTION"
"SEC","6","UNAVAILABLE","list %s %s %s %i(%d) %s- %i(%d), %d packet%s","A packet matching the log criteria for the given access list was detected.","LOG_STD_NO_ACTION"
"SEP","3","UNAVAILABLE","%s","Sep subsystem has experienced a problem gettting the required memory to complete this operation.","Check system memory for other memory allocation errors and contact Technical support for problem resolution. In the absence of IOS errors upgrading the memory in the network device may be required."
"SERIAL","0","UNAVAILABLE","%s (slot %d) %s %d","A very high rate of bad packets were received on the specified port. This can happen due to port mis-configuration - specially for mis-matched DSU subrates (most common with Kentrox). The port is shutdown for this reason so that the line card is not overwhelmed with these bad packets.","Verify that the configuration is correct and matching on both ends of the connection. These include clock source (one end line, other internal), DSU (mode and subrate), encapsulation. Also verify the physical condition on the line (run BERT or other tests), signal strength, cable length."
"SERIAL","0","UNAVAILABLE","%s HW DLLS failed to lock in linecard at slot %d","The DS3 line card could not initialize. The line card is deactivated","Try to reactivate the line card using the hw-module slot slot-number start command. If the error persists, copy the error message exactly as it appears on the console or in the system log. Enter the show diag slot-number command to gather additional data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative with the gathered information"
"SERIAL","0","UNAVAILABLE","%s Linecard local processor at slot %d failed to boot","The DS3 line card local processor boot code did not initialize properly. The line card will be deactivated. This error indicates a line card hardware failure","Enter the hw-module slot slot-number start command to try and reactivate the card. If the line card does not recover from the error, copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather additional data, and contact your Cisco technical support representative with the gathered information"
"SERIAL","0","UNAVAILABLE","%s initialization failure for slot %d, %s","The DS3 line card driver has failed to initialize properly. This indicates a software initialization issue. The line card is deactivated","Try to reactivate the line card using the hw-module slot slot-number start command. If the error persists, copy the error message exactly as it appears on the console or in the system log. Enter the show diag slot-number command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show diag slot-number output, contact your Cisco technical support representative with the gathered information."
"SERIAL","1","UNAVAILABLE","%s (slot %d) %s Allocation failure.","The DS3 driver data structure could not be allocated during line card initialization. This condition occurs when the system is running low on memory because of a misconfiguration or because the memory installed in the system is not large enough to meet the demands of different applications in high traffic conditions. The line card is deactivated on this error.","Try to reactivate the line card using the hw-module slot slot-number start command. If the error recurs, check the system configuration for the amount of Route Processor-switched traffic. A large amount of Route Processor switched traffic can cause this error, so reconfigure the system for less Route Process switched traffic if possible. If the amount of installed memory can be upgraded, consider upgrading main memory by removing and replacing the SDRAM SODIMM. If the problem persists, collect the show tech-support command output and the error message exactly as it appears on the console and contact your Cisco technical support representative"
"SERIAL","1","UNAVAILABLE","%s line card firmware in slot %d crashed","DS3 linecard firmware crashed","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SERIAL","3","UNAVAILABLE","%s %d/%d%s hardware IDB is missing","DS3 port hardware IDB is missing","Copy the error message exactly as it appears on the console or in the system log and call your Cisco technical support representative."
"SERIAL","3","UNAVAILABLE","%s (slot %d) %s HDLC, %s %s%s. (src=0x%x, det1=0x%x, det2=0x%x)","A hardware race condition, which occurs when access to shared memory is not properly synchronized, has occurred. The linecard has been deactivated and an automatic recovery has been initiated. If the error occurs more than five times within an hour, the line card will not be reactivated","The linecard can be reactivated manually using the hw-module slot slot-number start command if it has been deactivated after five failures. If the error persists, copy the error message exactly as it appears on the console or in the system log. Enter the show diag slot-number command to gather additional data , and contact your Cisco technical support representative with the gathered information."
"SERIAL","3","UNAVAILABLE","%s (slot %d) %s HDLC, %s. %s, port %d (src=0x%x, det1=0x%x, det2=0x%x)","The High-Level Data Link Control (HDLC) engine inside the HDLC ASIC on the line card detected unrecoverable errors. The line card is deactived and then an automatic recovery is initiated. If this error occurs more than five times within an hour, the line card is deactivated","If the line card is no longer automatically reactivating, copy the error message exactly as it appears on the console or in the system log, enter the show version and show diag slot-number commands to gather additional data, and contact your Cisco technical support representative with the gathered information to determine whether to replace the line card or upgrade the IOS version."
"SERIAL","3","UNAVAILABLE","%s (slot %d) %s HDLC, %s. %s=0x%x%s. (src=0x%x, det1=0x%x, det2=0x%x)","A parity error occurred in the HDLC engine SRAM memory. The source of the problem is a hardware failure. The line card has been deactivated and automatically reactivated. If this error occurs more than five times in an hour, the automatic reactivation will not occur after the fifth reactivation and the line card will remain deactivated","If the line card is no longer automatically reactivating, copy the error message exactly as it appears on the console or in the system log, enter the show diag slot-number command to gather additional data, and contact your Cisco technical support representative with the gathered information for a replacement of the line card."
"SERIAL","3","UNAVAILABLE","%s (slot %d) %s HDLC, %s. BMA_DATA[3:0]=0x%x. (src=0x%x, det1=0x%x, det2=0x%x)","A parity error occurred on the High-Level Data Link Control Broadcast Multi-Access (HDLC BMA) engine data bus. The line card has been deactivated and subsequently reactivated. If the error occurs more than five times within an hour, the line card will not be reactivated. This message is likely due to a hardware failure","If the line card has been deactivated, copy the error message exactly as it appears on the console or in the system log, enter the show diag slot-number command to gather additional data that may help identify the nature of the error, and contact your Cisco technical support representative with the gathered information"
"SERIAL","3","UNAVAILABLE","%s Corrupt configuration, unsupported %s (%u) encountered","The running configuration for the DS3 line card is corrupted. The DS3 driver data structures which store snapshots of interface configurations are corrupted or are not correctly updated with the corresponding interface configurations in NVRAM. This problem is caused by a software caveat","Attempt a graceful OIR of the line card by removing and reinserting the line card into the same slot or into another slot. A graceful OIR can also be performed by entering the hw-module slot slot-number stop command followed by the hw-module slot slot-number start command. If the problem persists, copy the error message exactly as it appears on the console or in the system log, enter the show tech-support command to gather additional data, and contact your Cisco technical support representative with the gathered information."
"SERIAL","3","UNAVAILABLE","%s DS3 LC(slot %d), %s","An informational message has been sent from the DS3 line card firmware to the system main processor on the NSE","None. Just an informational message from firmware."
"SERIAL","3","UNAVAILABLE","%s Interface %s received an unknown far end request (%u)","The DS3 driver received an unknown FEAC code from the far end of the link. The request has been ignored. This is not a catastrophic condition","Check the configurations at both ends of the connection. If the configuration appears correct, copy the error message exactly as it appears on the console or in the system log. Enter the show controller serial slot-number/port-number command to gather additional data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show controller serial slot-number/port-number output, contact your Cisco technical support representative with the gathered information."
"SERIAL","3","UNAVAILABLE","%s Loss of keepalives from linecard in slot %d","The system main processor is not receiving keepalive messages from the line card local processor. The source of the problem could be a line card hardware failure or a software failure. The line card has been deactivated and will be automatically reactivated. If this error occurs more than five times in an hour, the automatic reactivation will not occur and the line card will remain deactivated.","If the line card is no longer automatically reactivating, copy the error message exactly as it appears on the console or in the system log, enter the show version and show diag slot-number commands to gather additional data, and contact your Cisco technical support representative with the gathered information to determine whether to replace the line card or upgrade the IOS version"
"SERIAL","3","UNAVAILABLE","%s Slot %d: %s","A daughter card was detected in the line card in the specified slot. The line card has been disabled since the daughter card is not supported. If the message appears even though no daughter card is present on the line card, an I2C bus access failure has occurred on the line card","Remove the line card and inspect it for any daughter card. If present, unmount the daughter card from the line card. After removing the daughter card, or if no daughter card was found, reinsert the line card. If the error persists, copy the error message exactly as it appears on the console or in the system log, enter the show tech-support command to gather additional data, and contact your Cisco technical support representative with the gathered information"
"SERIAL","3","UNAVAILABLE","%s linecard boot code in slot %d crashed, reason: %s (0x%x)","The DS3 line card local processor boot code crashed. This error message indicates a line card hardware failure. The line card will be deactivated.","Manually attempt to activate the line card using the hw-module slot slot-number start command and check if the linecard recovers from the error. If the error persists, copy the error message exactly as it appears on the console or in the system log, enter the show diag slot-number command to gather additional data, and contact your Cisco technical support representative with the gathered information"
"SERIAL","3","UNAVAILABLE","%s linecard boot code in slot %d not ready for firmware download, boot code status 0x%x","The DS3 line card boot code did not initialize properly. This error message indicates a line card hardware failure. The line card will be deactivated","Manually attempt to initialize the line card using the hw-module slot slot-number start command and check if the linecard recovers from the error. If the error persists, copy the error message exactly as it appears on the console or in the system log, enter the show diag slot-number command to gather additional data, and contact your Cisco technical support representative with the gathered information"
"SERIAL","3","UNAVAILABLE","%s linecard in slot %d firmware download failed","The DS3 firmware download from the system main processor on the NSE to the line card local processor memory failed","This error, if not preceded by a firmware checksum failed error, indicates a software failure. Copy the error message exactly as it appears on the console or in the system log. Enter the show diag slot-number command to gather additional data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show diag slot-number output, contact your Cisco technical support representative with the gathered information"
"SERIAL","3","UNAVAILABLE","%s linecard in slot %d firmware integrity check failed.(section: %d, expected checksum: 0x%x, calculated checksum: 0x%x)","The DS3 line card local processor firmware crashed. The line card will be restarted after the firmware crash. If the firmware crashes more than five times consecutively, the line card will not reactivate after the fifth crash.","A line card firmware failure has occured. Copy the error message exactly as it appears on the console or in the system log. Enter the show diag slot-number command to gather additional data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show diag slot-number output, contact your Cisco technical support representative with the gathered information."
"SERIAL","3","UNAVAILABLE","%s linecard in slot %d firmware ipc initialization failed","The Cisco IPC module in the DS3 linecard local processor firmware failed to complete a successful initialization. The source of the problem could be a line card hardware failure or a software failure. The line card has been deactivated and will be automatically reactivated. If this error occurs more than five times in an hour, the automatic reactivation will not occur and the line card will remain deactivated.","If the line card is no longer automatically reactivating, copy the error message exactly as it appears on the console or in the system log and enter the show version, show diag slot-number, show ipc status, and show ipc port commands to gather additional data. Contact your Cisco technical support representative with the gathered information to determine whether to replace the line card or upgrade the IOS."
"SERIAL","4","UNAVAILABLE","%s %d/%d%s parameter value is unknown","The IPC command parameter is unknown and the corresponding IPC message has been dropped. This is an informational message.","Check the release notes for your IOS version to see if this is associated with a documented caveat. If not, copy the error message exactly as it appears on the console or in the system log, gather the show tech-support command output, and contact your Cisco technical support representative with the gathered information."
"SERIAL","5","UNAVAILABLE","%s Interface %s %s far end request of type (%s)","The DS3 driver received and processed a known far end request.","None. The purpose of this message is to provide notification that a known request was received from the far end of the link and was processed successfully."
"SERIAL","5","UNAVAILABLE","Interface %s, BERT %s","The DS3 driver processed a BERT task.","None, this is just a notification upon completion of a BERT task."
"SERIAL_12IN1","1","UNAVAILABLE","%s:Link has been brought %s due to clock rate change, threshold configured = %u, received clock rate = %u","The received clock rate is changed from below the threshold configured to above or vice versa..","Check the received clock rate from the provider end and the clockrate threshold configuration, if the clock rate goes below the threshold configured, interface is brought down"
"SERIAL_12IN1","3","UNAVAILABLE","%s: A software error was encountered at %s: %s","The SPA driver detected a software error condition on the SPA card. This might result in improper operation.","The SPA driver has encountered a software error.Please power down and reseat the indicated SPA card. Copy the error message exactly as it appears andopen a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact your Cisco technical support representative. Be sure to provide the the information you have gathered and a 'show tech-support' to your support representative, or attach it to your case in non-zipped, plain text format (.txt)."
"SERIAL_12IN1","3","UNAVAILABLE","%s: A software error was encountered at %s: %s 0x%x","The SPA driver detected a software error condition on the SPA card. This might result in improper operation.","The SPA driver has encountered a software error.Please power down and reseat the indicated SPA card. Copy the error message exactly as it appears andopen a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact your Cisco technical support representative. Be sure to provide the the information you have gathered and a 'show tech-support' to your support representative, or attach it to your case in non-zipped, plain text format (.txt)."
"SERIAL_12IN1","3","UNAVAILABLE","SPA %d/%d: %s was encountered.","The SPA driver detected a Hardware error condition on the SPA card. This might result in improper operation.","The SPA driver has encountered a Hardware error on the SPA's SPI4 bus.Please power down and reseat the indicated SPA card. If the condition persists, copy the error message exactly as it appears. Next research and attempt to resolve the issue using the SPA hardware troubleshooting documentation as well as the tools and utilities provided at http://www.cisco.com/public/support/tac/tools.shtml. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact your Cisco technical support representative. Be sure to provide the the information you have gathered and a 'show tech-support' to your support representative, or attach it to your case in non-zipped, plain text format (.txt)."
"SERVER_CLOCK_SYNC","3","UNAVAILABLE","bad request - %s - from client - %s","An internal software error occurred.","If this message recurs, copy it exactly as it appears and report it to your technical support representative."
"SERVER_CLOCK_SYNC","3","UNAVAILABLE","cannot create port %s due to %s","An internal software error occurred.","If this message recurs, copy it exactly as it appears and report it to your technical support representative."
"SERVER_CLOCK_SYNC","3","UNAVAILABLE","cannot open port %s due to %s","An internal software error occurred.","If this message recurs, copy it exactly as it appears and report it to your technical support representative."
"SERVER_CLOCK_SYNC","3","UNAVAILABLE","cannot register port %s due to %s","An internal software error occurred.","If this message recurs, copy it exactly as it appears and report it to your technical support representative."
"SERVER_CLOCK_SYNC","3","UNAVAILABLE","could not locate port %s","An internal software error occurred.","If this message recurs, copy it exactly as it appears and report it to your technical support representative."
"SERVER_CLOCK_SYNC","3","UNAVAILABLE","list creation failure","An internal software error occurred.","If this message recurs, copy it exactly as it appears and report it to your technical support representative."
"SERVER_CLOCK_SYNC","3","UNAVAILABLE","watched boolean creation failure. bool %s","An internal software error occurred.","If this message recurs, copy it exactly as it appears and report it to your technical support representative."
"SERVICE_MODULE","0","UNAVAILABLE","Unit %s - failed to create data structures used for module-access","The CSU/DSU driver failed to allocate memory for its data structures. This is a catastrophic error. The system has crashed.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SERVICE_MODULE","0","UNAVAILABLE","Unit %s - failed to download properly","The CSU/DSU driver detected a checksum error while downloading WIC firmware.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SERVICE_MODULE","3","UNAVAILABLE","Unit %s - WARNING - Loopdown of remote unit failed","A remote CSU is looping pings/test patterns back to the system. This error could be triggered if the user disabled loopbacks on the remote CSU after placing the remote CSU into remote loopback.","Execute a clear command on the remote CSU."
"SERVICE_MODULE","4","UNAVAILABLE","Unit %s - Could not access alarm status - disabling alarm processing","The system issued an alarm interrupt, but could not read the alarm status register from the module. This caused the system to disable alarm processing.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SERVICE_MODULE","4","UNAVAILABLE","Unit %s - failed to create reset process - non-default module configuration may be lost","To execute a reset, the Cisco IOS software needs to initiate a separate process. The Cisco IOS software did not have sufficient memory to create this separate process. The module came up in an initialized state with the default configuration. The user defined configuration may have been lost.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SERVICE_MODULE","4","UNAVAILABLE","Unit %s - giving up after %d repeated resets couldn't bring module up again","The software issued several clear service-module requests to the module. The module did not respond to these requests.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SERVICE_MODULE","4","UNAVAILABLE","Unit %s - module request overload - lock access timeout","The system employs a Cisco IOS scheduler semaphore object to ensure mutually exclusive access across software threads to the CSU/DSU. This message indicates that a thread had to wait for more than 5 seconds on this semaphore.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SERVICE_MODULE","4","UNAVAILABLE","Unit %s - reports incompatible module type %d against router hw detect","A register read request returned an identity for a module which was not the same as the identity reported by the router hardware pinout.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SERVICE_MODULE","4","UNAVAILABLE","Unit %s - router image older than module version - access errors may be seen","The Cisco IOS software image does not recognize the PROM software version number on the module. The system displays this message if the PROM has been upgraded to a new version but the Cisco IOS software image has not been upgraded.","Upgrade the Cisco IOS software image."
"SERVICE_MODULE","4","UNAVAILABLE","Unit %s - timed out while %s byte %d of %d length register %d","The module took more than two seconds to respond between bytes.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SERVICE_MODULE","4","UNAVAILABLE","Unit %s not ready for next command","The module was waiting for the current request to be processed before sending the next request. The current request has been in progress for more than 3 seconds.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SERVICE_MODULE","4","UNAVAILABLE","Unit %s not ready for register access","The module was waiting for a ready status before executing a read/write request. The system reported a not ready status for 5 seconds. This caused the module to terminate the read/write request.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SERVICE_MODULE","4","UNAVAILABLE","Unit %s not ready/responding after register %d access command issued","The system did not receive a ready signal within the allotted time after writing to the command register.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SERVICE_MODULE","4","UNAVAILABLE","Unit %s reports register access error - %s","This message indicates that the T1 module supplied a bad register address. It might be due to having a new version of the module operating with an old Cisco IOS software image.","Update the Cisco IOS software image on the system. If this does not solve the problem, copy the error message exactly as it appears and report it to your technical support representative."
"SERVICE_MODULE","4","UNAVAILABLE","Unit %s reports unknown network alarms - alarm status reg = %x","A recent version of the module operating with an old Cisco IOS software image did not recognize an alarm condition.","Update the Cisco IOS software image on the system. If this does not solve the problem, copy the error message exactly as it appears and report it to your technical support representative."
"SERVICE_MODULE","5","UNAVAILABLE","Reset of Unit %s issued","This message indicates that the module was reset.","No action is required."
"SERVICE_MODULE","5","UNAVAILABLE","Unit %s - Loopup of remote unit failed","This notification message indicates that the loopback on the remote unit failed. The failure may indicate that the network connection is broken or that loopbacks are disabled at the other side.","Check that the router is connected to the network. Enable loopbacks on the remote unit. If the problem persists, copy the error message exactly as it appears and report it to your technical support representative."
"SERVICE_MODULE","5","UNAVAILABLE","Unit %s - Remote loopback test cancelled","A hardware or software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative for assistance."
"SERVICE_MODULE","5","UNAVAILABLE","Unit %s - Remote unit placed in loopback","This notification message indicates that the user executed a loopback command on the remote unit. The remote unit is now in loopback.","No action is required."
"SFF8472","2","NOMEM","Not enough memory available for [chars]","The SFF8472 subsystem could not obtain the memory it needed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SFF8472","3","INTERNAL_ERROR","[chars]","The SFF8472 subsystem encountered an internal software error. The error message contains text that can be used to help identify the nature of the problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SFF8472","3","READ_ERROR","[chars]","There was an error reading digital optical monitoring information from the transceiver at the specified interface.","Try removing and reinserting the transceiver. If the error remains, replace the transceiver."
"SFF8472","3","THRESHOLD_VIOLATION","[chars]: [chars]; Operating value: [chars], Threshold value: [chars].","There has been a threshold violation as specified in the message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SFF8472","3","UNEXPECTEDEVENT","Process received unknown event (maj [hex], min [hex]).","A process can register to be notified when various events occur in the router. This message indicates that a process received an event it did not know how to handle.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SFP","3","EEPROM_DUP_ERR","SFP on ports [chars] and [chars] have duplicate serial numbers","The GBIC or SFP was identified as a Cisco GBIC, but its vendor ID and serial number match those of another GBIC on the system.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SFP","4","EEPROM_CRC_ERR","EEPROM checksum error for SFP in [chars]","The SFP in the port specified in the message text contains invalid EEPROM data.","Remove the SFP from the specified port."
"SFP","4","EEPROM_READ_ERR","Error in reading SFP serial ID in [chars]","An error occurred while the SFP type was being read from the EEPROM.","Remove the SFP from the port that reported the error."
"SFP","4","EEPROM_SECURITY_ERR","SFP in [chars] failed security check","The SFP in the port specified in the message text contains invalid EEPROM data.","Remove the SFP from the port that reported the error."
"SFP_SECURITY","4","DUPLICATE_SN","SFP interface [chars] has the same serial number as another SFP interface","The SFP was identified as a Cisco SFP, but its serial number matches that of another interface on the system. Cisco SFPs are assigned unique serial numbers.","Verify that the SFP was obtained from Cisco or from a supported vendor."
"SFP_SECURITY","4","ID_MISMATCH","Identification check failed for SFP interface [chars]","The SFP was identified as a Cisco SFP, but the system was unable to verify its identity.","Check the list of supported SFPs for this version of the system software. An upgrade may be required for newer SFPs. If this does not fix the problem, verify that the SFP was obtained from Cisco or from a supported vendor."
"SFP_SECURITY","4","SFP_INTERR","Internal error occurred in setup for SFP interface [chars]","The system was unable to allocate resources or encountered some other problem while attempting to set up the specified SFP interface.","Reload the system. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SFP_SECURITY","4","UNRECOGNIZED_VENDOR","SFP interface [chars] manufactured by an unrecognized vendor","The SFP was identified as a Cisco SFP, but the system was unable to match its manufacturer with one on the known list of Cisco SFP vendors.","Check the list of supported SFPs for this version of the system software. A software upgrade may be required for newer SFPs."
"SFP_SECURITY","4","VN_DATA_CRC_ERROR","SFP interface [chars] has bad crc","The SFP was identified as a Cisco SFP, but it does not have a valid CRC in the EEPROM data.","Check the list of supported SFPs for this version of the system software. A software upgrade may be required for newer SFPs. Even if the system could not recognize the SFP, it may still operate properly, but might perform with limited functionality."
"SFF8472","2","NOMEM","Not enough memory available for %s","The sff8472 subsystem could not obtain the memory it needed.","Reload the system. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SFF8472","3","INTERNAL_ERROR","%s","The SFF8472 subsystem encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem.","Reload the system. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SFF8472","3","READ_ERROR","%s","There was an error reading digital optical monitoring information from the transceiver at the specified interface.","Please try removing and reinserting the transceiver. If it still does not work, please replace the transceiver."
"SFF8472","3","THRESHOLD_VIOLATION","%s: %s; Operating value: %s, Threshold value: %s.","There has been a threshold violation as specified in the message.","Reload the system. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SFF8472","3","UNEXPECTEDEVENT","Process received unknown event (maj %x, min %x).","A process can register to be notified when various events occur in the router. This message indicates that a process received an event it did not know how to handle.","Reload the system. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SGBP","1","AUTHFAILED","Member [chars] failed authentication","This message is generated only when SGBP hellos or errors debugging is enabled. This indicates that an attempted peer connection ended in authentication failure. A peer may be misconfigured, or this could indicate an attempted security breach.","Check if the peer is correctly configured. If there is a chance your network is under attack, obtain knowledgeable assistance. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"SGBP","1","DIFFERENT","Rcv [chars]'s addr [IP_address] is different from the hello's addr [IP_address]","The internally-configured address for an SGBP member does not match the address of the host that tried to authenticate as that member. The configuration is incorrect on either this system or the other member - they must agree.","Determine which configuration is in error and fix it."
"SGBP","1","DUPLICATE","Rcv Duplicate bundle [chars] is found on member [chars]","This message is generated only when SGBP hellos or errors debugging is enabled. This indicates that a duplicate bundle was received from the same peer more than once. The duplicate was discarded.","If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support"
"SGBP","1","MISSCONF","Possible misconfigured member [chars] using [IP_address]","This message is generated only when SGBP hellos or error debugging is enabled. This indicates a configuration error. Either this router has an incorrect IP address listed for the peer or the peer is using an incorrect IP address.","Find and correct the configuraton error."
"SGBP","1","UNKNOWNHELLO","Rcv Hello message from non-group member using [IP_address]","This message is generated only when SGBP hellos or error debugging is enabled. An SGBP Hello message was received from a host that is not a member of the SGBP group, and discarded.","This is a configuration error. Either that host should be listed in this router's configuration as a member (if that is actually true) or the other host is misconfigured to attempt to join this group."
"SGBP","3","INVALID","MQ message with [chars]","This message is generated only when SGBP error debugging is enabled. An invalid message was received and discarded.","This probably indicates an error in network media or a peer which is generating erroneous packets."
"SGBP","3","INVALIDADDR","Stack group [chars] IP address [IP_address]","The current configuration does not allow a local IP address to be configured using sgbp member . Any local address is automatically removed fro the SGBP group.","Do not configure sgbp member using a local IP address."
"SGBP","3","INVALIDB","[chars] for bundle '[chars]' -- [chars]","An internal software error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SGBP","3","INVFIELD","[chars] field type [hex] has [chars] [dec] (expected [dec])","This message indicates that an SGBP request from a peer contained invalid or corrupt data.","Check the peer equipment or network media for any problems."
"SGBP","3","PEERERROR","Peer [IP_address] [chars] during 'PB [chars]' state for bundle [chars]","An internal software error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SGBP","3","TIMEOUT","Peer [IP_address] bidding; state 'PB [chars]' deleted","This message is generated only when SGBP event debugging is enabled. It indicates that a peer timed out while closing a query. The connection has been dropped.","Check the peer equipment and network media for problems."
"SGBP","3","UNEXP","MQ [chars] from [IP_address] for query [dec]:[dec], bundle [chars], bid [dec], state [chars]","This message is generated only when SGBP error debugging is enabled. The SGBP connection has entered an unexpected state, possibly due to a software error.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"SGBP","3","UNKNOWN","[IP_address] not known","This message is generated only when SGBP error debugging is enabled. An SGBP connection was attempted by a host which was not recognized as a peer. The connection was not accepted.","Depending on the network topology and firewalling, SGBP connection attempts from a non-peer host could indicate probing and attempts to breach security. If there is a chance your network is under attack, obtain knowledgeable assistance. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"SGBP","3","UNKNOWNEVENT","Event [hex] from peer at [IP_address]","This message is generated only when SGBP error debugging is enabled. An invalid event occurred, which probably indicates an internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SGBP","3","UNKNOWNPEER","Event [hex] from peer at [IP_address]","This message is generated only when SGBP error debugging is enabled. An SGBP event came from a network host which was not recognizable as an SGBP peer. The event was discarded.","Check if a network media error could have corrupted the address, or if peer equipment is malfunctioning to generate corrupted packets. Depending on the network topology and firewalling, SGBP packets from a non-peer host could indicate probing and attempts to breach security. If there is a chance your network is under attack, obtain knowledgeable assistance. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"SGBP","5","ARRIVING","New peer event for member [chars]","This message is generated only when SGBP event debugging is enabled. An SGBP peer joined the group.","No action is required."
"SGBP","5","LEAVING","Member [chars] leaving group [chars]","This message is generated only when SGBP event debugging is enabled. An SGBP peer has left the group.","No action is required."
"SGBP","5","SHUTDOWN","[chars]","This message is generated only when SGBP event debugging is enabled. A process involved in SGBP was terminated upon completion of its work.","No action is required."
"SGBP","5","STARTUP","[chars]","This message is generated only when SGBP event debugging is enabled. An process involved in SGBP was started.","No action is required."
"SGBP","7","ACTIVE","Member [chars] State - Active","This message is generated only when SGBP errors or events debugging is enabled. This indicates that a link to another SGBP member has completed the interactions to set it up and is now entering the active state.","No action is required."
"SGBP","7","AUTHOK","Member [chars] State - AuthOK","This message is generated only when SGBP errors or events debugging is enabled. A message was received from another SGBP member indicating that an authentication attempt to that member succeeded.","No action is required."
"SGBP","7","CANCEL","Local query #[dec]:[dec] for bundle [chars]","This message is generated only when SGBP query debugging is enabled. It provides information about queries in progress.","No action is required."
"SGBP","7","CHALLENGE","Send Hello Challenge to [chars] group [chars]","This message is generated only when SGBP hellos debugging is enabled. This indicates that an authentication challenge was sent to a peer.","No action is required."
"SGBP","7","CHALLENGED","Rcv Hello Challenge message from member [chars] using [IP_address]","This message is generated only when SGBP hellos debugging is enabled. This indicates that an authentication challenge was received from a peer.","No action is required."
"SGBP","7","CLOSE","Closing pipe for member [chars]","This message is generated only when SGBP event debugging is enabled. An interprocess communication link was closed.","No action is required."
"SGBP","7","DONE","Query #[dec] for bundle [chars], count [dec], master is [chars]","This message is generated only when SGBP query debugging is enabled. It provides information about queries in progress.","No action is required."
"SGBP","7","DUPL","Duplicate local query #[dec] for [chars], count [dec], ourbid [dec]","This message is generated only when SGBP query debugging is enabled. It provides information about queries in progress.","No action is required."
"SGBP","7","EQUAL","[dec] equal highest bids, randomly select bid# [dec]","This message is generated only when SGBP query debugging is enabled. It provides information about queries in progress.","No action is required."
"SGBP","7","HANGUP","I am a forward-only member, can't forward bundle [chars], hangup","This message is generated only when SGBP query, event and/or error debugging is enabled. This indicates a routine change of role for the router in its SGBP interactions with its peers.","No action is required."
"SGBP","7","KEEPALIVE","Sending Keepalive to [chars], retry=[dec]","This message is generated only when SGBP hellos debugging is enabled. It indicates that a keepalive message was send to an SGBP member.","No action is required."
"SGBP","7","KEEPALIVE_TIMEOUT","Keepalive timeout on [chars]","This message is generated only when SGBP hellos debugging is enabled. It indicates that keepalive messages were not answered so the pipe to an SGBP member has been closed.","No action is required."
"SGBP","7","MQ","[chars] ([hex]) for query [dec]:[dec], bundle [chars], bid [dec], len [dec]","This message is generated only when SGBP error debugging is enabled. This message indicates that an SGBP query has been received.","No action is required."
"SGBP","7","MQB","Bundle: [chars]State: [chars]OurBid: [dec]","This message is part of a list of debug states displayed at the request of the operator.","No action is required."
"SGBP","7","NEWL","Local query #[dec] for [chars], count [dec], ourbid [dec]","This message is generated only when SGBP query debugging is enabled. It provides information about queries in progress.","No action is required."
"SGBP","7","NEWP","Peer query #[dec] for [chars], count [dec], peerbid [dec], ourbid [dec]","This message is generated only when SGBP query debugging is enabled. It provides information about queries in progress.","No action is required."
"SGBP","7","NORESP","Failed to respond to [chars] group [chars], may not have password","An authentication challenge was received but there was no information available to respond to it. This probably indicates a configuration error, a missing password.","Refer to the documentation to configure a username with the same name as the SGBP group."
"SGBP","7","PB","[IP_address]	State: [chars]Bid: [dec] Retry: [dec]","This message is part of a list of debug states displayed at the request of the operator.","No action is required."
"SGBP","7","RCVD","MQ [chars] from [IP_address] for query [dec]:[dec], bundle [chars], bid [dec], prot[chars]","This message is generated only when SGBP message debugging is enabled. It indicates that an SGBP packet was received.","No action is required."
"SGBP","7","RCVINFO","Received Info Addr = [IP_address] Reference = [hex]","This message is generated only when SGBP hellos debugging is enabled. It indicates that data was received by a listener process.","No action is required."
"SGBP","7","RESPONSE","Send Hello Response to [chars] group [chars]","This message is generated only when SGBP hellos debugging is enabled. This indicates that a response to an authentication challenge was sent to a peer.","No action is required."
"SGBP","7","RESPONSED","Rcv Hello Response message from member [chars] using [IP_address]","This message is generated only when SGBP hellos debugging is enabled. This indicates that a response to an authentication challenge was received from a peer.","No action is required."
"SGBP","7","SENDAUTHOK","Send Hello Authentication OK to member [chars] using [IP_address]","This message is generated only when SGBP hellos debugging is enabled. A message was send or re-sent to another SGBP member indicating that an authentication attempt from that member succeeded.","No action is required."
"SGBP","7","SENDINFO","Send Info Addr to [chars]","This message is generated only when SGBP hellos debugging is enabled. It indicates that data was sent by the listener process in response to received data.","No action is required."
"SGBP","7","SENT","MQ [chars] to [IP_address] for query [dec]:[dec], bundle [chars], bid [dec], prot[chars], len [dec]","This message is generated only when SGBP message debugging is enabled. It indicates that an SGBP packet was sent.","No action is required."
"SGCP","2","UNAVAILABLE","%s","The SGCP subsystem encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SGCP","3","UNAVAILABLE","%s","The SGCP subsystem encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SGCP","4","UNAVAILABLE","%s","The SGCP subsystem encountered an internal software error. The error message contains text which can be used to help identify the nature of the problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SGCP_APP","6","UNAVAILABLE","Cannot create SGCP application process","Failed to create the SGCP application process.","Check the size of free memory to make sure there is enough memory."
"SGCP_APP","6","UNAVAILABLE","Failed to create DNS message watched queue","Failed to create DNS message watched queue.","Check the size of free memory to make sure there is enough memory."
"SGCP_APP","6","UNAVAILABLE","Failed to create call record database","Failed to create call record database.Error Message    %SGCP_APP-6-UNAVAILABLE: Failed to create digit map database Explanation    Failed to create endpoint database.","Check the size of free memory to make sure there is enough memory."
"SGCP_APP","6","UNAVAILABLE","Failed to open UDP port for SGCP. IP Adress is not configured or UDP port (2427) already in use.","Failed to open UDP port for the SGCP process. IP Adress not configured or UDP port (2427) already in use.","Check if IP Address is configured and if any other application use the same UDP port number (2427)."
"SGPM","3","POLICY_CTX_POISONED","Policy context %X has bad magic, %X.","The magic number in the policy context is wrong.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SGPM","3","POLICY_INCOMPLETE_RULE","Subscriber policy rule (%s), event (%s) is missing a mandatory action for service (%s); automatically adding.","The subscriber policy rule was missing a mandatory action. The missing action will be automatically added.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHELF","3","UNAVAILABLE","socket open failed","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHELF","5","UNAVAILABLE","MD5 digest does not match, SDP packet received from, %i rejected","A SDP hello packet was received from shelf, which is not trusted.","Either specify the correct SDP password and/or destination on the shelf from which this message was received"
"SHELF","6","UNAVAILABLE","Configured via system controller located at %i","This is an informational message only. Configuration information was received from a system controller.","Informational messages can be disabled by changing logging level."
"SHELF","6","UNAVAILABLE","Shelf hello process has been stopped.","This is an informational message only. An internal system controller process completed its work.","Informational messages can be disabled by changing logging level."
"SHELF","6","UNAVAILABLE","Shelf hello process has started.","This is an informational message only. An internal system controller process was started.","Informational messages can be disabled by changing logging level."
"SHMINFO","3","UNAVAILABLE","API called illegally from interrupt context.","An application has made a Shared Information Utility API call from interrupt context and this is not supported","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHMINFO","3","UNAVAILABLE","Attempting to access shared resource without mutex","An internal data structure was accessed without obtaining the required mutex lock. This is a code defect with no workaround.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHMINFO","3","UNAVAILABLE","Data commit failed, %s","A commit of a new view of a dataset was attempted but failed.","Show siu all. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If youshow message typestill require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHMINFO","3","UNAVAILABLE","Group commit enable failed since not previously disabled","An attempt was made to enable commit for a group but failed since it was not previously disabled.","Show siu all. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If youshow message typestill require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHMINFO","3","UNAVAILABLE","Invalid %s parameter passed into API call","An application has made a Shared Information Utility API call with an invalid input parameter.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHMINFO","3","UNAVAILABLE","Lock of latest version of dataset %s failed due to %s, error %d","A failed attempt was made by infrastructure to lock on to the latest available version of data for this dataset. There is no known workaround","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHMINFO","3","UNAVAILABLE","Unlock of latest version of dataset %s failed, addr %#x, error %d","A failed attempt was made by infrastructure to unlock the latest available version of data for this dataset. There is no known workaround","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHMINFO","3","UNAVAILABLE","Write operation denied due to read only access","An application has made a Shared Information Utility API call which required write access, but the dataset has been registered for read only access.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHMWIN","6","ALLOC_FAILURE","Insufficient memory","There was a failure while returning physical memory to the system.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHMWIN","6","CORE_NOT_ENABLED","In function [chars] The core has not been enabled to get more physical memory","The core has not been enabled.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHMWIN","6","EXCEEDED_MAX_SIZE","In function [chars] The requested memory size exceeded the window size","The memory requested in this window exceeded the window size.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHMWIN","6","EXCEEDED_MAX_USERS","In function [chars] The maximum number of users for a shared window has been exceeded","The maximum number of users for a shared window has been exceeded.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHMWIN","3","FREE_FAILURE","Failure while freeing memory in function [chars]","An attempt was made to free memory that has already been freed or is not within the address space of the current process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHMWIN","6","INCONSISTENCY","Inconsistent state in window","Inconsistent state in window.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHMWIN","6","INVALID_ARGS","One or more invalid arguments have been passed to the function [chars]","One or more invalid arguments have been passed to the shared memory APIs.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHMWIN","6","INVALID_PARAM","An invalid parameter has been passed to the function [chars]","One or more invalid parameters have been passed to the shared memory APIs.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHMWIN","6","MAX_WINDOWS_EXCEEDED","In function [chars] process has exceeded the maximum number of windows that can be opened by it","The process has exceeded the maximum number of windows that can be opened by a process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHMWIN","6","MEM_COLLISION","In function [chars] the requested memory space collides with the memory space of other windows","There is a memory space collision.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHMWIN","6","MUTEX_ERROR","An internal mutex error has occured in the function [chars]","An error has been encountered in the locking or unlocking of the shared memory mutual exclusivity lock (mutex).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHMWIN","6","MUTEX_MONITOR_FAILURE","Registration failed with mutex monitor in [chars]","An error occurred while trying to monitor a shared memory mutual exclusivity lock (mutex).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHMWIN","6","NOT_SUPPORTED","The option passed to function [chars] is not supported","This option is not supported.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHMWIN","7","PHYS_MAP_FAILURE","In function [chars] Failed to map physical memory","Failed to map physical memory in the specified function.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHMWIN","6","PTHREAD_MUTEX_LOCK_FAILED","An internal mutex error has been encountered in function [chars]","A process that has obtained the access mutex has not released it.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHMWIN","6","PTHREAD_MUTEX_UNLOCK_FAILED","An internal mutex error has been encountered in function [chars]","An internal mutex error has been encountered.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHMWIN","6","SHMEM_FAILURE","The function [chars] Could not access shared memory","Could not access shared memory.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHMWIN","6","SYS_LOCK_CREATE_FAILED","The lock creation for the shared memory failed in function [chars]","Lock creation for the shared memory has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHMWIN","6","SYS_LOCK_FAILED","In function [chars] The process was unable to lock the shared memory against other processes","The process was unable to lock the shared memory against other users.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHMWIN","6","SYS_LOCK_MMAP_FAILED","The mmap for the shared memory lock creation failed in function [chars]","Lock creation for the shared memory has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHMWIN","6","SYS_UNLOCK_FAILED","In function [chars] The process was unable to unlock the shared memory","The shared memory could not be unlocked due to an internal error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHMWIN","7","UNLINK_ERROR","An internal error occurred while unlinking in function [chars]","An internal error occurred while unlinking.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHMWIN","6","VIRT_MAP_FAILURE","In function [chars] Could not reserve virtual memory","Could not reserve virtual memory.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SHMWIN","6","WINDOW_EXCEEDED_MAX_POOLS","The maximum number of pools has been exceeded in function [chars]","The maximum number of pools has been exceeded.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIA_INFRA","3","BAD_LISTENER","%i is not a configured SIA TCP control-plane IP address","SIA uses Authenticated TCP as the control-plane of choice. In SIAarchitecture, both service-broker and the SVE component can be listeners. The incoming connect request is not using one of the configured SIA TCPlistener IP addresses as the destination IP address for the control plane connectivity with peer SIA component.","If this syslog is seen, verify the configuration of the broker/sve/scl and service to ensure they are using the correct IP address for control plane connectivity show run service-insertion , and corresponding show at service If problem still persists, collect the following information debug service-insertion tcp control, and show tech-support. Contact your Cisco technical support representative and provide the representative with the gathered information"
"SIA_INFRA","3","UNAVAILABLE","%s failed to send message %s to %s","An SIA control-plane message could not be sent. This could be because the receiving component is not reachable, not active or has not been configured","Ensure that the receiving component has been configured and is reachable. If reachability and configuration issues have been resolved and the message is still seen, collect the outputs from the following commands debug service-insertion errors, andshow tech-support.Contact your Cisco technical support representative and provide the representative with the gathered information."
"SIA_INFRA","3","UNAVAILABLE","%s received an invalid message %s %s","A message received from an SIA component could not be processed correctly because of an error in the message. The specific error in the message is provided in the Syslog message when available.Since the messages exchanged between components are for control-plane communication, this error could result in failures in control-plane acitivity like component registration and service-pathcreation","If these messages persist, collect the outputs from the following commands debug service-insertion errors, andshow tech-support.Contact your Cisco technical support representative and provide the representative with the gathered information"
"SIA_INFRA","3","UNAVAILABLE","Message parsing failed at line %d, column %d, byte index %d (Reason: %s)","An SIA control-plane message was received with incorrectly formatted XML and could not be processed. Since these message are used for control-plane communication between SIA components, this error could result in failures in control-plane acitivity like component registration and service-path creation","If these messages persist, collect the outputs from the following commands debug service-insertion errors, debug service-insertion tcp error, andshow tech-support.Contact your Cisco technical support representative and provide the representative with the gathered information"
"SIA_INFRA","3","UNAVAILABLE","Message received from SIA peer %i is invalid (Reason: %s)","An SIA control-plane message received in XML format could not be processed because of errors in the message. The specific error encountered is provided in the message when available. The TCP Peer IP address of the component that sent the message is also provided. Since these message are used for control-plane communication between SIA components, this error could result in failures in control-plane acitivity like component registration and service-path creation","If these messages persist, collect the outputs from the following commands debug service-insertion errors, debug service-insertion tcp error, andshow tech-support.Contact your Cisco technical support representative and provide the representative with the gathered information"
"SIA_INFRA","3","UNAVAILABLE","TCP session setup with peer %i using key %s failed for SIA %s to SIA %s communication","This message indicates an error during the setting up ofthe TCP session with peer in Service-Insertion Infrastructure (SIA) code. SIA uses TCP for control-plane communication between its components. During initialization, a failure was detected while attempting to setup a TCP session with peerThis could be because of peer being not reachable, becausedid not respond to session request or because of low available memory","Copy the error message exactly as it appears and provide it to your technical support along with the outputs of the following commands show service-insertion tcp peer all, show ip route,show tech-support"
"SIA_INFRA","3","UNAVAILABLE","Two listeners (%i) with different MD5 not supported on the same box","SIA uses Authenticated TCP as the control-plane of choice. In SIAarchitecture, both service-broker and the SVE component can be listenersIn the current implementation, if both SB and SVE components are co-locatedon the same box and using the same IP address in the control plane, theyalso should use the same authentication key","If this syslog is seen, verify the configuration of the broker and sve toensure they are using the same authentication keyshow run service-insertion broker, andshow run service-insertion sveIf problem still persists, collect the following informationdebug service-insertion tcp control, andshow tech-support.Contact your Cisco technical support representative and provide the representative with the gathered information"
"SIA_INFRA","4","UNAVAILABLE","%s keepalive timed out for %s","Keepalive timed out between the two SIA components mentioned. On the Service Broker, this will result in removal of information related to the component that timed out. Status of service-paths associated with the component could change. Service-path data paths that have already been set up will remain up for the data-plane active-time configured","Check the reachability of the component that timed out to/from the Service Broker"
"SIA_INFRA","4","UNAVAILABLE","Message %s with version %d received from %s on %s running version %d Recommended Action    LOG_STD_NO_ACTIONSIA_INFRA-6Error Message    %SIA_INFRA-6-UNAVAILABLE: %s control-plane is %s","SIA control-plane connectivity between two components has been established(up) or has been disrupted (down) as specified in the message.If the control-plane communication has been disrupted, it could be becauseof a component being de-configured or becoming unreachable. This canresult in the removal of control-plane information related to SIA service-paths in the component.","If the control-plane status has changed to up, no action is required.If control-plane status has changed to down, check the reachability ofthe Service Broker from the component"
"SIA_INFRA","6","UNAVAILABLE","%s deregistered from %s","Control-plane de-registration between two SIA components was successful","LOG_STD_NO_ACTION"
"SIA_INFRA","6","UNAVAILABLE","%s registered successfully with %s","Control-plane registration between two SIA components was successful","LOG_STD_NO_ACTION"
"SIA_INFRA","6","UNAVAILABLE","%s service path segment created for ID %d between %s and %s","A service-path data path segment was created for the path ID andsequence number mentioned in the message","LOG_STD_NO_ACTION"
"SIA_INFRA","6","UNAVAILABLE","%s service path segment removed for ID %d between %s and %s","The data-path for a service-path segment with the path ID and sequence number mentioned in the message was removed and data traffic is no longer flowing through this service-pathThis could be because the service-path's configuration was removed or changed. It could also be because one of the components participating in the service-path is no longer reachable. If that is the case, other Syslog messages will be generated to indicate the disruption of control-plane communication","If the removal of datapath resulted from a configuration change no action is required.If the datapath removal was because of disruption in the control-plane communication between components, check the reachability between components"
"SIA_INFRA","6","UNAVAILABLE","TCP session setup with peer %i terminated for SIA %s to SIA %s communication","This message indicates the TCP session with peer inService-Insertion Infrastructure went downSIA uses TCP for control-plane communication between its components. The session can do down due to variousreasons including for receiving a reset by the peer","Copy the error message exactly as it appears and provide it to your technical support along with the outputs of the following commands show service-insertion tcp peer all, show ip route,show tech-support."
"SIA_SB","3","UNAVAILABLE","%s","Registration message to Service Directory failed","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIA_SB","3","UNAVAILABLE","%s failed to register with Broker%s","Service Broker component of SIA received a registration message from another component participating in SIA. But because of a software error, the registration has failed. The reason for the failure may be displayed in the error message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIA_SB","3","UNAVAILABLE","Cannot associate service type %s to service ID %s in service path %s%s","An associate cli provided for a static service path in Service Broker component has become incosistent. The reasons for inconsistency will be mentioned in the message. These could be service type mismatch between cli command and service template at a particular position, service type mismatch between cli command and actual service and service class mismatch between service and service path","Look for the reason in the message and take appropriate action to resolve the inconsistency in the cli."
"SIA_SB","6","UNAVAILABLE","%s%s from service path %s%s%s","A Classifier has sent a request to detach a service policy from a service path created by Service Broker. The result of the operation will be mentioned in the message.","LOG_STD_NO_ACTION"
"SIA_SB","6","UNAVAILABLE","%s%s to service path %s%s%s","A Classifier has sent a request to attach a service policy to a service path created by Service Broker. The result of the operation will be mentioned in the message and may be reason as well for failures.","If the attach operation fails and the reason specified is - failed to find a set up service path to attach to or there is no reason specified then copy the error message exactly as it appears on the console, collect the output of show tech-support and show service-insertion broker service-path, and contact Techincal Assistance Center(TAC) with the gathered information."
"SIA_SB","6","UNAVAILABLE","Data plane of %s has become active","The data plane interface of a SCl/SVE has become active. The interface has been brought up.","LOG_STD_NO_ACTION"
"SIA_SB","6","UNAVAILABLE","Data plane of %s has become inactive","The data plane interface of a SCl/SVE has become inactive. Either the interface has been shut down or erased.","LOG_STD_NO_ACTION"
"SIA_SB","6","UNAVAILABLE","Service path %s - state changed from %s to %s","A service path in SIA has changed state. This state change will be visible only in the Service Broker component of SIA. The event leading to this state change may have been indicated in an earlier message","LOG_STD_NO_ACTION"
"SIA_SB","6","UNAVAILABLE","Service template %s%s","A service template had been updated in Service Broker. The update has been triggered by a message pushed from Service Directory. The type of update will be shown in the message too","LOG_STD_NO_ACTION"
"SIA_SB","6","UNAVAILABLE","TCP Transport is not setup","TCP Transport listener is not running for broker.","No action is required."
"SIA_SCL","3","DP_ERROR","%s","Data path setup error.","Service Classifier tried to setup a data path with its peers after receiving a service path segment update from Service Broker. However, there was an error during the data path setup. The specific error condition should be displayed in the error message. Please capture the error message. Copy the error message exactly as it appears on the console or in the system log. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIA_SCL","3","REGISTRATION_FAILURE","%s failed to register with %s %s","Service Classifier failed to register with Service Broker.","Registration with Service Broker could fail due to multiple reasons. 1) Service Broker failed to add the Service Classifier to the internal database. This could be due to memory allocation failure or inconsistent internal state. Turn on the command debug service-insertion broker error on Service Broker and capture the logs. 2) Check if another Service Classifier with same name is already registered with Service Broker. If this is the case, try using a different Service Classifier name before registering with Service Broker. 3) Service Classifier is running a different control plane version than Service Broker. Service Classifier should automatically retry registration with Service Broker using a correct version based on the supported versions sent by Service Broker. Copy the error message exactly as it appears on the console or in the system log. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIA_SCL","3","UNAVAILABLE","%s","Data path setup error.","Service Classifier tried to setup a data path with its peers after receiving a service path segment update from Service Broker. However, there was an error during the data path setup. The specific error condition should be displayed in the error message. Please capture the error message. Copy the error message exactly as it appears on the console or in the system log. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIA_SCL","3","UNAVAILABLE","%s failed to register with %s %s","Service Classifier failed to register with Service Broker.","Registration with Service Broker could fail due to multiple reasons. 1) Service Broker failed to add the Service Classifier to the internal database. This could be due to memory allocation failure or inconsistent internal state. Turn on the command debug service-insertion broker error on Service Broker and capture the logs. 2) Check if another Service Classifier with same name is already registered with Service Broker. If this is the case, try using a different Service Classifier name before registering with Service Broker. 3) Service Classifier is running a different control plane version than Service Broker. Service Classifier should automatically retry registration with Service Broker using a correct version based on the supported versions sent by Service Broker. Copy the error message exactly as it appears on the console or in the system log. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIA_SCL","3","UNAVAILABLE","Failed to configure SCL data plane","Not able to obtain data path information from the SCL interface.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIA_SD","3","UNAVAILABLE","%s %d","Unknown message type received.","Capture the error message with message type received. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIA_SD_HA_API","3","UNAVAILABLE","%s","A run-time module could not obtain the resources that are required to complete a task. The failure most likely occurred because of a software error or a lack of system memory. Additional details on the nature of the error are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized.","If you determine that this condition was caused by a lack of system memory, reduce system activity to ease memory demands, or if conditions warrant, upgrade to a larger memory configuration. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIA_SVE","3","UNAVAILABLE","Failed to configure interface SVE data plane","Not able to obtain data path information from the SVE interface.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIBYTE","0","ADDRESS_TRAP","Address trap: [dec] occurred on physical address: [hex] at EPC: [hex], ERR_EPC: [hex]","A previously defined address trap has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIBYTE","0","MISDIRECTED_INTERRUPT","A misdirected interrupt occurred with int_mask: [hex]","A misdirected interrupt has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIBYTE","0","UNCORRECTABLE_ECC_ERR","An uncorrectable ECC error has occurred, A_BUS_L2_ERRORS: [hex], A_BUS_MEMIO_ERRORS: [hex], A_SCD_BUS_ERR_STATUS: [hex]","An uncorrectable ECC error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIBYTE","3","CORRECTABLE_ECC_ERR","A correctable ECC error has occurred, A_BUS_L2_ERRORS: [hex], A_BUS_MEMIO_ERRORS: [hex], A_SCD_BUS_ERR_STATUS: [hex]","The card detected and corrected a single-bit parity error using the error correction code (ECC) functionality. There was no interruption of service. Transient parity errors are typically caused by RF radiation.","No action is necessary if the message occurs infrequently. If errors become frequent, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIBYTE","6","SB_RMON_OVRFL","RMON register [dec] overflow on mac [dec]","The indicated RMON register has overflowed (wrapped around), meaning that the counter reached its maximum value and restarted from zero. The affected register is in the RMON statistical information associated with the specified MAC interface of the Sibyte ethernet controller located on the linecard.","This message is informational, and is normal when the service internal command is enabled. The service internal command should be enabled only for troubleshooting. To disable service internal messages, enter the global configuration command no service internal."
"SIBYTE_ION","3","SB_THREAD_CTL_ERR","Call to ThreadCTL() failed: function = [chars], line number = [dec], return_code = [dec], errno = [dec]","A QNX call to ThreadCTL() failed. [chars] is the function, the first [dec] is the line number, the second [dec] is the return code, and the third [dec] is the error number.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIGNATURE","3","UNAVAILABLE","%%ERROR: Aborting %s.","The system is aborting the specified operation because it failed to verify a valid signature in the image file.","Attempt to restart the operation by using an image file with a valid signature. A valid signature ensures the integrity of the image."
"SIGNATURE","3","UNAVAILABLE","%%ERROR: Continuing Operation %s in spite of failure.","Although the system failed to verify a valid signature in the image file, the user decided to continue the specified operation. A valid signature ensures the integrity of the image.","If you decide to continue the operation without a valid signature in the image file, no action is required. If you want to cancel the operation after choosing to continue it, perform one of the following: - If the copy command was used, delete the copied file by using the delete command; - If the reload command was used, cancel the operation at the Proceed with reload [confirm] prompt."
"SIGNATURE","3","UNAVAILABLE","%%ERROR: Not able to process Signature in %s.","An unknown error occurred when the system attempted to process the signature in the specified image file. A valid signature ensures the integrity of the image.","Do not use this file. The file might be corrupted or modified. Attempt to copy the file again, or download the file again from the http://www.cisco.com page before copying it. If you continue to get this error message, open a case with the Technical Assisstance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, contact your Cisco technical support representative with the information you have gathered."
"SIGNATURE","3","UNAVAILABLE","%%ERROR: Signature not valid for file %s.","The specified Cisco IOS Software image has an invalid signature. A valid signature ensures the integrity of the image.","Do not use this file. The file might be corrupted or modified. Attempt to copy the file again, or download the file again from the http://www.cisco.com page before copying it. If you continue to get this error message, open a case with the Technical Assisstance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, contact your Cisco technical support representative with the information you have gathered."
"SIGNATURE","3","UNAVAILABLE","%%ERROR: Unable to auto delete file %s. Remove file manually","The specified Cisco IOS Software image file contains an invalid signature, but automatic deletion of the file has failed. A valid signature ensures the integrity of the image.","Delete the file by entering the delete command."
"SIGNATURE","4","UNAVAILABLE","%%WARNING: Found unknown signature type 0x%x, in file %s Skipping the signature.","If the desired image belongs to a later release than the running image, the desired image might have a newer signature type. A valid signature ensures the integrity of the image.","If the specified file is a Cisco IOS software image in executable and linkable format, be cautious when deciding whether or not to use this file. Check the release notes, or check the Feature Navigator at http://tools.cisco.com/ITDIT/CFN/jsp/index.jsp and search for Image Verification, to see if a signature of the type specified was added."
"SIGNATURE","4","UNAVAILABLE","%%WARNING: Signature not found in file %s.","The specified image file does not have a signature. Only Cisco IOS Software images in Executable and Linkable format are signed. Releases that do not support the image verification feature do not contain a signature in the image file. If you enter verify, copy, or reload command, and the specified file is not a Cisco IOS Software image in Executable and Linkable format or of an earlier release, the system displays this warning message because the file does not have a signature. A valid signature ensures the integrity of the image.","If the specified file is a Cisco IOS Software image in Executable and Linkable Format, be cautious when deciding whether or not to use this file. Check the release notes, or check the Feature Navigator at http://tools.cisco.com/ITDIT/CFN/jsp/index.jsp and search for Image Verification, to see if the image that you are using supports the image verification feature."
"SIGSM","1","UNAVAILABLE","No static template found for slot %d port %d with parameters provided","The sigsm could not find a matching static template with the same parameters as the controller being used","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIGSM","1","UNAVAILABLE","Out of range variable index %d %s","There is a fault in a default template or the user has provided a custom template that refers to a variable that is outside the range of cas-custom variables","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIGSM","1","UNAVAILABLE","Unexpected event","An error in the signalling state machine","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIGSM","3","UNAVAILABLE","Failed to allocate memory for the %s","An attempt to allocate memory has failed.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"SIP10G_QM","2","CONFORM_ACTION_NE","Different aggregate and microflow conform-action in class %s[policy %s]","Conform actions in 'police' and 'police flow' commands must be the same for the same class in a service-policy applied to MLS interfaces.","Change the conform-action in 'police' or 'police flow' command to make both actions the same, or remove one of two commands."
"SIP10G_QM","2","DSCP_NE","Different aggregate and microflow DSCP in class %s[policy %s]","Conform actions in 'police' and 'police flow' commands must be the same for the same class in a service-policy applied to MLS interfaces.","Change the conform-action in 'police' or 'police flow' command to make both actions the same, or remove one of two commands."
"SIP10G_QM","2","NO_AGGREG_PLC","Hardware aggregate policer resources exceeded","The hardware doesn't have the capacity to handle aggregate policers required by configuration.","Reduce the total number of aggregate policers required by all service-polic ies installed in the device. For example, use shared aggregate policers, as defined by 'mls qos aggregate-policer' command, instead of default per-interface policers"
"SIP10G_QM","2","NO_AGGREG_PLC","Hardware aggregate policer resources exceeded","The hardware doesn't have the capacity to handle aggregate policers required by configuration.","Reduce the total number of aggregate policers required by all service-policies installed in the device. For example, use shared aggregate policers, as defined by 'mls qos aggregate-policer' command, instead of default per-interface policers"
"SIP10G_QM","2","NO_FLOW_PLC","Hardware microflow policer resources exceeded","The hardware doesn't have the capacity to handle microflow policers required by the policy-map.","Adjust microflow policing rate/burst parameters so that the total number of different rate/burst combinations in the device is reduced."
"SIP10G_QM","2","TCAM_ENTRIES_EXCEEDED","ACL merge failed, ACEs exceed TCAM capacity or 0 ACES, %d ACEs for interface %s in %s direction","ACL merge results in number of ACES exceeding TCAM capacity or zero ACEs, so merge has been aborted","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP10G_QM","4","TCAM_CAPMAP","Interface %s hardware TCAM LOU usage capability exceeded","The hardware TCAM doesn't have the capacity to handle the number of logical operations used with the configured ACLs on this specific interface.","The hardware TCAM can only handle up to 9 logical operations per interface and up to 64 logical operations in total. Reduce the use of logical operations in the ACLs."
"SIP10G_QM","4","TCAM_ENTRY","Hardware TCAM entry capacity exceeded","The hardware TCAM doesn't have the capacity to handle all of the configured ACLs.","The configured ACLs are too large to all fit in the hardware TCAM. Try and share the same ACLs across multiple interfaces in order to reduce TCAM resource contention."
"SIP10G_QM","4","TCAM_LABEL","Hardware TCAM label capacity exceeded","The hardware TCAM doesn't have the capacity to handle the number of interfaces configured with ACLs.","The hardware TCAM can only handle 500 interfaces configured with ACLs. Deconfigure ACLs from some of the interfaces."
"SIP10G_QM","4","TCAM_LOU","Hardware TCAM LOU capacity exceeded. The policy-map might not work as expected","The hardware TCAM doesn't have the capacity to handle the number of logical operations used with the configured ACLs.","The hardware TCAM can only handle up to 9 logical operations per interface and up to 64 logical operations in total. Reduce the use of logical operations in the ACLs and then remove the policy-map and apply it again on the interface."
"SIP10G_QM","4","TCAM_MASK","Hardware TCAM mask entry capacity exceeded","The hardware TCAM doesn't have the mask capacity to handle all of the configured ACLs.","The configured ACLs are too large to all fit in the hardware TCAM. Try and share the same ACLs across multiple interfaces in order to reduce TCAM resource contention."
"SIP10G_QM","6","SET_AND_POLICE","'set' and 'police' commands cannot co-exist in classmap %s of policymap %s","set' and 'police' commands cannot co-exist in a classmap for a QM supported interface","Chose between one of the commands or use the set-dscp-transmit | set-precedence-transmit | set-exp option for the conform action of the police command"
"SIP10G_QM","6","SHAREDAG_AND_POLICE","'police aggregate' and regular 'police' commands cannot co-exist in classmap %s of policymap %s","set' and 'police' commands cannot co-exist in a classmap for a QM supported interface","Chose between one of the commands or use the set-dscp-transmit | set-precedence-transmit | set-exp option for the conform action of the police command"
"SISF","3","UNAVAILABLE","Internal error, %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SISF","4","UNAVAILABLE","Entry blocked %s","An attempt to install an entry in the IPv6 binding table was blocked. This can be due to a conflicting entry or maximum number of entries reached","If the maximum table size is reached, consider increasing it. If a conflicting entry already exist, this maybe an attempt to steal address ownership. You should investigate which host is connected on the interface and wether it should be disconnected"
"SISF","4","UNAVAILABLE","Message dropped %s","A message was dropped because one of the IPv6 first-hop security features said so","Look at the reason. It can either be a valid drop and the could go up to disconnect the host attached to the interface, or the policy configured on this interface is too severed and should be amended"
"SISF","6","UNAVAILABLE","Entry changed %s","An entry was changed in the binding table","This is an informationnal message"
"SISF","6","UNAVAILABLE","Entry created %s","An entry was created in the binding table","This is an informationnal message"
"SISF","6","UNAVAILABLE","Entry deleted %s","An entry was created in the binding table","This is an informationnal message."
"SISF_ISSU","2","UNAVAILABLE","Sisf ISSU client encountered unexpected client nego_done. Error: %d (%s)","An ISSU-compliant client transitions through a series of internal states. The Sisf ISSU client encountered a 'client negotiation done' state that was unexpected. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","Show issu session and show issu negotiated capability. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SISF_ISSU","2","UNAVAILABLE","Sisf ISSU client failed to get buffer for message. Error: %d (%s)","The Sisf ISSU client failed to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","Show logging and show checkpoint client. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SISF_ISSU","2","UNAVAILABLE","Sisf ISSU client failed to register session information. Error: %d (%s)","The Sisf ISSU client failed to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly.","Show issu capability entries, issu session and show issu negotiated capability. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SISF_ISSU","2","UNAVAILABLE","Sisf ISSU client failed to send negotiation message. Error: %d (%s)","The Sisf ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","Show logging and show checkpoint client. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SISF_ISSU","2","UNAVAILABLE","Sisf ISSU client initialization failed to %s. Error: %d (%s)","The Sisf ISSU client could not be initialized. This initialization failure must be addressed before in-service software upgrade or downgrade can be performed successfully. If you do not address this failure, there will be downtime during software upgrade or downgrade.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SISF_ISSU","3","UNAVAILABLE","SISF ISSU client capability list is empty.","The SISF ISSU client capability exchange list size is invalid.","Show issu message group and issu session, and show issu negotiated version. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SISF_ISSU","3","UNAVAILABLE","Sisf ISSU client %s transform failed for 'Message Type %d'. Error: %d (%s)","The Sisf ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In both cases, the Sisf state between the active device and the standby device is not identical.","Show issu session and show issu negotiated version. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SISF_ISSU","3","UNAVAILABLE","Sisf ISSU client 'Message Type %d' is not compatible","The Sisf ISSU client received an incompatible message from the peer device. The message cannot be processed.","Show issu message group and show issu session and show issu negotiated version. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SISF_ISSU","3","UNAVAILABLE","Sisf ISSU client capability exchange result incompatible.","The Sisf ISSU client capability exchange have negotiated as incompatible with the peer.","Show issu negotiated capability. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SISF_ISSU","3","UNAVAILABLE","Sisf ISSU client does not have a valid registered session.","The Sisf ISSU client does not have a valid registered session.","Show issu capability entries, issu session and show issu negotiated capability. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SISF_ISSU","3","UNAVAILABLE","Sisf ISSU client failed to get the MTU for Message Type %d. Error: %d (%s)","The Sisf ISSU client failed to calculate the MTU for the specified message. The Sisf ISSU client is not able to send the message to the standby device.","Show issu message group and show issu session and show issu negotiated version . 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SISF_ISSU","3","UNAVAILABLE","Sisf ISSU client failed to unregister session information. Error: %d (%s)","The Sisf ISSU client failed to unregister session information.","Show issu session and show issu negotiated capability. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SISF_TRACKING_HA","4","UNAVAILABLE","Host mac-address %e ip-address %i interface %s","An inconsistency has been detected in the IP device tracking table for this host between active and standby","LOG_STD_NO_ACTION."
"SK","0","UNAVAILABLE","%s","Unrecoverable Internal Panic","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SK","1","UNAVAILABLE","%s","A condition that should be corrected immediately.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SK","2","UNAVAILABLE","%s","Critical Conditions","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SK","3","UNAVAILABLE","%s","Errors","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SK","4","UNAVAILABLE","%s","Warning","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SK","4","UNAVAILABLE","Slot %d: Could not %s memory ( %d bytes ) to receive IPC","IOS was not able to allocate memory to receive IPC from Switch Kernel. Some IPCs between IOS and 8PG linecard in that slot may be lost.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SK","4","UNAVAILABLE","Slot %d: Could not send IPC for %d seconds. Still trying...","IOS was not able to send an IPC to Switch Kernel running in the CPU in the 8PG card. IOS will retry to send the IPC","The message may occur occasionally depending on the load on the system. If the condition persists, the line card on the slot will be reset. In that case, please contact your Cisco technical support representative and provide information about events that led to the reset"
"SK","4","UNAVAILABLE","Traffic may be locally switched between %s & %s. Routing over these interfaces may not be fully functional","The subinterfaces specified have the same encapsulation configured. Since 8PG has a local-switching ASIC, traffic with that encapsulation will be bridged among those interfaceseven though they may not be in the same bridge-group. In addition,if the subinterfaces have different configuration, routing overthese subinterfaces may not work since there is only one backend portchannel that represents both the subinterfaces.","Re-evaluate the implications of local-switching between the interfaces specified. If local-switching among the subinterfaces is not desired, change the encapsulation on one of the subinterfaces."
"SK","6","UNAVAILABLE","%s","Informational","LOG_STD_NO_ACTION"
"SK","7","UNAVAILABLE","Assertion Failure ( %s @%s:%d ) : %s","Assertion","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP10G_QM","2","ACL_MERGE_NO_MEM","Memory low: ACL merge failed for interface %s in %s direction","An ACL merge failed due to insufficient system memory.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP10G_QM","2","BAD_TLV","Error in internal messaging - bad tlv %d","A software error occurred during the programming of ACLs into the TCAM.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP10G_QM","2","CONFORM_ACTION_NE","Different aggregate and microflow conform-action in class %s[policy %s]","The conform actions must be identical in both the police and police flow commands for the same class in a service policy applied to MLS interfaces.","Change the conform action in the police or the police flow command to make both actions the same, or remove one of two commands."
"SIP10G_QM","2","DSCP_NE","Different aggregate and microflow DSCP in class %s[policy %s]","The conform actions must be identical in both the police and police flow commands for the same class in a service policy applied to MLS interfaces.","Change the conform action in the police or the police flow command to make both actions the same, or remove one of two commands."
"SIP10G_QM","2","MERGE_ERROR","ACL merge error for Interface %s in %s direction status %d","An ACL merge failed before programming the ACLs into the TCAM.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP10G_QM","2","NO_AGGREG_PLC","Hardware aggregate policer resources exceeded","The hardware cannot support the number of aggregate policers required by configuration.","Reduce the total number of aggregate policers required by all service policies installed in the device. For example, use shared aggregate policers, as defined by the mls qos aggregate-policer command, instead of default per-interface policers."
"SIP10G_QM","2","NO_FLOW_PLC","Hardware microflow policer resources exceeded","The hardware cannot support the microflow policers required by the policy map.","Adjust the microflow policing rate and burst parameters to reduce the total number of different rate and burst combinations in the device."
"SIP10G_QM","2","P10G_PLC_ATTACH_REJECT_ARP_UFLOW","Command rejected: (policy-map %s class %s interface %s dir %s) flow policer is not supported for traffic classes matching ARP ACL.","In a policy map, a flow policer is not supported if the traffic class matches an ARP ACL.","Remove the flow policer from the traffic class matching the ARP ACL and reattach the policy, or change the traffic class to match a non-ARP ACL and configure the flow policer."
"SIP10G_QM","2","TCAM_BAD_LOU","Bad TCAM LOU operation in ACL","A software error caused a failure in programming ACLs into the TCAM.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP10G_QM","2","TCAM_ENTRIES_EXCEEDED","ACL merge failed, ACEs exceed TCAM capacity or 0 ACES, %d ACEs for interface %s in %s direction","An ACL merge was aborted because the number of ACES exceeded the TCAM capacity or because the number of ACES was zero.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP10G_QM","2","TCAM_ERROR","TCAM programming error %d","A software error caused a failure in programming ACLs into the TCAM.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP10G_QM","2","TCAM_MEMORY","NMP processor memory low","The programming of ACLs into the TCAM failed due to insufficient memory.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP10G_QM","4","TCAM_CAPMAP","Interface %s hardware TCAM LOU usage capability exceeded","The hardware TCAM cannot support the number of logical operations used with the configured ACLs on this specific interface. The hardware TCAM can support a maximum of 9 logical operations per interface and a maximum total of 64 logical operations.","Reduce the use of logical operations in the ACLs."
"SIP10G_QM","4","TCAM_ENTRY","Hardware TCAM entry capacity exceeded","The configured ACLs exceed the capacity of the hardware TCAM.","To reduce TCAM resource contention, try to share the same ACLs across multiple interfaces."
"SIP10G_QM","4","TCAM_LABEL","Hardware TCAM label capacity exceeded","The hardware TCAM cannot support the number of interfaces configured with ACLs. The hardware TCAM supports 500 interfaces configured with ACLs.","Unconfigure ACLs from some of the interfaces."
"SIP10G_QM","4","TCAM_LOU","Hardware TCAM LOU capacity exceeded","The hardware TCAM cannot support the number of logical operations used with the configured ACLs. The hardware TCAM can support a maximum of 9 logical operations per interface and a maximum total of 64 logical operations.","Reduce the use of logical operations in the ACLs."
"SIP10G_QM","4","TCAM_MASK","Hardware TCAM mask entry capacity exceeded","The hardware TCAM does not have the mask capacity to handle the number of configured ACLs.","To reduce TCAM resource contention, try to share the same ACLs across multiple interfaces."
"SIP10G_QM","6","IOS_AND_PS_FEATURE","%s action cannot be present in classmap %s of policymap %s because this service-policy cannot be executed in Cat6K HW due to the presence of filters which require packets to be processed in IOS SW","Network-Based Application Recognition (NBAR) is required for the match protocol commands used. Because NBAR exists only in software, hardware-specific actions are not supported.","Remove the hardware-specific commands or remove the match protocol criteria in the class map."
"SIP10G_QM","6","SET_AND_POLICE","'set' and 'police' commands cannot co-exist in classmap %s of policymap %s","The set and police commands cannot coexist in a class map for a QoS manager (QM) supported interface.","Remove one of the commands or use the set-dscp-transmit | set-precedence-transmit | set-exp option for the conform action of the police command."
"SIP10G_QM","6","SET_AND_TRUST","'set' and 'trust' commands cannot co-exist in classmap %s of policymap %s","The set and trust commands cannot coexist in a class map for a QM supported interface.","Remove one of the commands."
"SIP10G_QM","6","SHAREDAG_AND_POLICE","'police aggregate' and regular 'police' commands cannot co-exist in classmap %s of policymap %s","The police aggregate and police commands cannot coexist in a class map for a QM supported interface.","Remove one of the commands or use the set-dscp-transmit | set-precedence-transmit | set-exp option for the conform action of the police command."
"SIP200","3","BADIFCTRL","Corrupted sip-200 information for interface [chars] [[hex]]","The interface SIP-200 information is not valid. This is an internal software error.","Copy the message exactly as it appears on the console or in the system log. Collect the output of the show memory command on the line card. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP200","4","MEM_MODULE_MISMATCH","Memory modules are not identical","The memory modules do not have identical parameters. This may impact the performance.","Copy the message exactly as it appears on the console or in the system log. Collect the output of the show memory command on the line card. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP200_MP","1","UNSAFE","Multiprocessor error on [chars]","The line card CPU contains two CPU cores, one of which is the master CPU. The CPU specified in the error message attempted to perform an operation that is illegal for multiprocessor operation between the two CPU cores.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP200_MP","3","INIT_FAILURE","Second CPU initialization failed","The line card CPU unit contains two CPU cores. The second CPU core has not initialized successfully. The line card is operating with one CPU core only. You may also see a SYS-2-MALLOCFAIL warning message.","If this message appears when a line card boots up, reload the line card by entering the hw-module module slot reset command. Also, check how much memory the line card has by entering the show controller cwan command."
"SIP200_MP","4","PAUSE","Non-master CPU is suspended for too long, from [hex]([int]) to [hex] for [int] CPU cycles. [chars]","The line card CPU contains two CPU cores, one of which is the master CPU. The master CPU caused the second, nonmaster CPU to be suspended for too long a time. This condition could cause packet drops on the nonmaster CPU. This warning indicates a transient software problem. The line card should continue to operate normally.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP200_MP","4","TIMEOUT","Master CPU request timed out [chars]","The line card CPU contains two CPU cores, one of which is the master CPU. The nonmaster CPU is not responding in time to a request from the master CPU. This warning indicates a transient software problem. The line card should continue to operate normally.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP200_SPIRX","3","INITFAIL","Failed to configure the ingress SPI4.2 device. Error = [hex]","The system was unable to program or configure the ingress SPI4.2 device on the line card. This indicates an internal hardware error.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPIRX","3","SPA_INTERRUPT","SPA [int] - [chars], SPA Int status = [hex]","A SPA interrupt occurred from the ingress SPI4.2 device.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPIRX","3","SRAM_ERROR_DATA","SRAM[dec] Address = [hex][hex] Data = [hex][hex][hex]_[hex][hex][hex]_[hex][hex][hex]_[hex][hex][hex]","An SRAM address and data dump is displayed.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPIRX","3","SRAM_INTERRUPT","[chars], Sram Int status = [hex]","An SRAM interrupt occurred from the ingress SPI4.2 device.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPIRX","3","STATUS_INTERRUPT","[chars], Global Int status = [hex]","A status interrupt occurred from the ingress SPI4.2 device.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","BADDESC","descriptor [hex], tag [hex], global channel [int]","The egress SPI4.2 device on the line card returns a descriptor entry that is corrupted.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","BADPAK","corrupted packet to [chars]","The egress SPI4.2 device on the line card is handling a packet that is corrupted. This indicates an internal software error. The corrupted packet is dropped.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","CHANNEL_ENABLE_FAIL","SPI4 Channel [int] for Bay [int], [chars] Failed","The system was unable to enable or disable a given SPI4 channel.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","DESCR_ERR_SPA0","SPAstatus=[hex], syndrome=[hex], RdRspOvf=[int], RdRspTo=[int], OvfVal=[int], OvfCh=[int], OvfDescHi=[hex], OvfDescLo=[hex], DisChk=[int], SeqErrVal=[int], SeqErrCh=[int]","The egress SPI4.2 device on the line card detected a sequence or FIFO overflow error while processing a transmit descriptor. This condition could cause packet drops.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","DESCR_ERR_SPA1","SPAstatus=[hex], syndrome=[hex], RdRspOvf=[int], RdRspTo=[int], OvfVal=[int], OvfCh=[int], OvfDescHi=[hex], OvfDescLo=[hex], DisChk=[int], SeqErrVal=[int], SeqErrCh=[int]","The egress SPI4.2 device on the line card detected a sequence or FIFO overflow error while processing a transmit descriptor. This condition could cause packet drops.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","DESCR_ERR_SPA2","SPAstatus=[hex], syndrome=[hex], RdRspOvf=[int], RdRspTo=[int], OvfVal=[int], OvfCh=[int], OvfDescHi=[hex], OvfDescLo=[hex], DisChk=[int], SeqErrVal=[int], SeqErrCh=[int]","The egress SPI4.2 device on the line card detected a sequence or FIFO overflow error while processing a transmit descriptor. This condition could cause packet drops.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","DESCR_ERR_SPA3","SPAstatus=[hex], syndrome=[hex], RdRspOvf=[int], RdRspTo=[int], OvfVal=[int], OvfCh=[int], OvfDescHi=[hex], OvfDescLo=[hex], DisChk=[int], SeqErrVal=[int], SeqErrCh=[int]","The egress SPI4.2 device on the line card detected a sequence or FIFO overflow error while processing a transmit descriptor. This condition could cause packet drops.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","DMA_SQERR","Syndrome=[hex], SPA=[int], Ch=[int], RdSz=[int], RdOff=[int][chars]","The egress SPI4.2 device on the line card detected a sequence error while processing a DMA operation. This condition could cause packet drops.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","EFC_ERR_SPA0","SPAstatus=[hex][chars]","The egress data path device on the line card detected an error condition with the extended flow control bus interface. This condition could cause packet drops.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","EFC_ERR_SPA1","SPAstatus=[hex][chars]","The egress data path device on the line card detected an error condition with the extended flow control bus interface. This condition could cause packet drops.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","EFC_ERR_SPA2","SPAstatus=[hex][chars]","The egress data path device on the line card detected an error condition with the extended flow control bus interface. This condition could cause packet drops.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","EFC_ERR_SPA3","SPAstatus=[hex][chars]","The egress data path device on the line card detected an error condition with the extended flow control bus interface. This condition could cause packet drops.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","EFCEVNT_ERR","[chars]","The egress data path device on the line card detected an error while processing internal extended flow-control events. This condition could cause a reduced packet rate.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","EFC_QUEUE_STUCK","[chars]","The egress data path device on the line card detected an error condition with the extended flow control bus interface. This condition could cause packet drops.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","EFCSTAT_FAIL_SPA0","[chars]","The egress SPI4.2 device on the line card detected an EFC status clock or synchronization failure. This condition could cause packet drops.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","EFCSTAT_FAIL_SPA1","[chars]","The egress SPI4.2 device on the line card detected an EFC status clock or synchronization failure. This condition could cause packet drops.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","EFCSTAT_FAIL_SPA2","[chars]","The egress SPI4.2 device on the line card detected an EFC status clock or synchronization failure. This condition could cause packet drops.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","EFCSTAT_FAIL_SPA3","[chars]","The egress SPI4.2 device on the line card detected an EFC status clock or synchronization failure. This condition could cause packet drops.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","FCSTAT_FAIL_SPA0","[chars]","The egress SPI4.2 device on the line card detected an SPI4.2 status clock or synchronization failure. This condition could cause packet drops.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","FCSTAT_FAIL_SPA1","[chars]","The egress SPI4.2 device on the line card detected an SPI4.2 status clock or synchronization failure. This condition could cause packet drops.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","FCSTAT_FAIL_SPA2","[chars]","The egress SPI4.2 device on the line card detected an SPI4.2 status clock or synchronization failure. This condition could cause packet drops.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","FCSTAT_FAIL_SPA3","[chars]","The egress SPI4.2 device on the line card detected an SPI4.2 status clock or synchronization failure. This condition could cause packet drops.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","INITFAIL","Failed to configure the egress SPI4.2 device. Error = [hex]","The system was unable to program or configure the egress SPI4.2 device on the line card. This indicates an internal hardware error.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","INT_PERR_SPA0","IntMemPerr=[hex][chars]","The egress SPI4.2 device on the line card detected an internal memory parity error. This condition could cause packet drops.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","INT_PERR_SPA1","IntMemPerr=[hex][chars]","The egress SPI4.2 device on the line card detected an internal memory parity error. This condition could cause packet drops.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","INT_PERR_SPA2","IntMemPerr=[hex][chars]","The egress SPI4.2 device on the line card detected an internal memory parity error. This condition could cause packet drops.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","INT_PERR_SPA3","IntMemPerr=[hex][chars]","The egress SPI4.2 device on the line card detected an internal memory parity error. This condition could cause packet drops.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","MISMATCH","Descriptor ring mismatch: expects [int] got [int]","The egress SPI4.2 device on the line card returns a descriptor entry that does not match what the line card CPU expects. This condition could cause packet drops.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","OVERRUN_DROP","SPI4 overrun drops packet for SPA [int], queue [int], count [int]","While the egress SPI4.2 device on the line card sends an packet on the extended flow controlled channel, it overruns the SPI4 channel but cannot queue it to the internal hold queue. This indicates an internal software error.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","SPI4_ERR_SPA0","SPAstatus=[hex][chars]","The egress SPI4.2 device on the line card detected an error condition with the SPI4.2 bus interface. This condition could cause packet drops.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","SPI4_ERR_SPA1","SPAstatus=[hex][chars]","The egress SPI4.2 device on the line card detected an error condition with the SPI4.2 bus interface. This condition could cause packet drops.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","SPI4_ERR_SPA3","SPAstatus=[hex][chars]","The egress SPI4.2 device on the line card detected an error condition with the SPI4.2 bus interface. This condition could cause packet drops.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP200_SPITX","3","SRAM_ECCERR","EccSynd=[hex], Err1bit=[int], ErrMbit=[int], SecHalf=[int], SPA=[int], Ch=[int], Addr=[hex], DataHi=[hex], DataLo=[hex], DataEcc=[hex]","The egress SPI4.2 device on the line card detected a a parity error in the egress packet memory. This condition could cause packet drops.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show tech-support command for the line card and the show platform hardware spi4 spa-id efc channel [channel-id] command for the SPA."
"SIP400","2","IOBUS_ERROR","IO bus error occurred: [chars] last addr [hex] data [hex] tran [hex]","There was a communication problem with a device on the I/O bus.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP400","2","PCI_BUS_ERROR","A PCI Bus Error occurred while trying to access a device (status reg = [hex], addstatus reg = [hex])","There was a problem with a PCI read access to a device that caused a bus error on the host processor.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP400","2","PCI_ERROR_INT","A PCI Error interrupt occurred while trying to access a device (status reg = [hex], addstatus reg = [hex])","There was a problem with a PCI write access to a device that caused a PCI error interrupt.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600","2","DEVMGR_ASIC_INIT_FAILED","SIP-600 ASIC Initialization failed at stage-asic_init[dec]","The SIP-600 received an error during initialization when attempting to initialize the ASICs that make up the forwarding hardware. A hardware problem has prevented the SIP-600 from fully initializing on the target line card. This will result in packets not being forwarded.","Attempt to reload the line card. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600","2","DEVMGR_PROC_CREATE_FAILED","SIP-600 Initialization failed to create a required IOS process[dec]","The SIP-600 received an error during initialization when attempting to create the ASIC stage2 initialization process. A potential memory or other software resource problem has prevented the SIP-600 from fully initializing on the target line card. This will result in packets not being forwarded.","Attempt to reload the line card. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600","2","INITFAIL","SIP-600 Initialization Failed - [chars]: [chars] [dec] [dec]","The SIP-600 could not initialize the memory that is needed for the feature specified in the message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600","2","NULL_OBJECT","Missing device object ([chars]) for pending interrupt","A hardware device asserted an interrupt to report an event, but there is no device object for this device.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600","2","NULL_SPA_BAY_OBJECT","SPA Bay [dec] is missing","A SPA bay object is missing.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600","2","PE_BUS_UNRECOVERABLE_INT","Packet Engine Unrecoverable Bus Interrupt: [chars] = [hex]","A packet engine unrecoverable bus interrupt has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600","2","QUPDATE","SIP-600 Update Queue Hardware Failed - [chars]: [chars] [dec] Cause: [hex]","The SIP-600 received an error on the specified hardware queue when attempting the specified action. A hardware problem has prevented system queues from being updated on the target line card. This could result in packets not being forwarded.","Reload the line card. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600","2","UNRECOVERABLE_FAILURE","SIP-600 Unrecoverable Failure","An unexpected fatal condition has occurred on the SIP-600. The message that was previously received on the console or in the system log should provide more information on the specific nature of the problem. This message indicates a hardware failure or malfunction. The system will reload to attempt to fix the problem.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600","3","IO_BUS_ERR_INT","IO Bus Error Interrupt: [hex] - Deadman Timer = [hex] Trans Status = [hex] Last Address = [hex] Last Data = [hex]","An I/O bus error interrupt has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600","3","NMI","NMI Reset Status = [hex]","A nonmaskable interrupt has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600","3","NOMEM","[chars]","The SIP-600 card could not obtain statistics due to insufficient memory.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600","3","NO_STATID","PXF([dec]): no stat_id is available for statistics collection","The SIP-600 line card has used up all statistics collection resources. No more resources are available for further statistics collection.","Reduce number of features configured on this PXF. If conditions warrant, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600","3","NO_STAT_PROCESS","Failed to create statistics process","The SIP-600 card failed to create a statistics process. All statistics counters will be zero.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600","3","PE_BUS_ERR_INT","Packet Engine Bus Error Interrupt: [chars]","A packet engine bus error interrupt has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600","3","PE_SPA_BUS_ERR_INT","SPA Bus Error Interrupt: SPA Bus Error Status ([hex]) = [hex], SPA Bus Trans Status ([hex]) = [hex], SPA Bus Last Data ([hex]) = [hex]","A SPA bus error interrupt has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600","3","PE_UNEXPECTED_INT","Unexpected Packet Engine Interrupt: [chars]","An unexpected packet engine interrupt has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600","3","SIP10G_GEN_DEV_ERR","[chars] unexpected error: [chars]","The software driver for the specified SIP-600 device has detected the specified unexpected condition.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600","3","STATID_INCONSISTENCY","PXF([dec]):Inconsistent stats id([hex]) [int] packets dropped.","A WAN line card has received inconsistent statistics from PXF. PXF reported that one or more packets have been dropped, but no corresponding packet count has been reported.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600","3","UNEXPECTED_GLOBAL_INT","Unexpected Global Interrupt: [chars]","An unexpected global interrupt has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600","3","UNSUPPORTED_LABEL_RANGE","The maximum label range configured for this system exceedsthe [int] limit supported by the OSM module.","The MPLS label range that was configured for this system is not supported. The maximum label range limit is specified in the message.","Change the maximum MPLS label range by entering the mpls label range command."
"SIP600","4","INVALID_STATID","PXF:Invalid-Statid ([dec]) for vc [int] under interface [int]","The SIP-600 line card has encountered an internal error while setting up the statistics report subsystem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600","4","MR_CFG_ALL_PORTS","CFM configuration is global to sip-600 and applies to all ports","An SCP message to configure match register functionality on the specified port will apply to all ports on the MSC-600 card as match register configurations are done on the parsing engine.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600","4","SIP10G_PXF_IRAM_PARITY_ERROR","Correcting a PXF instruction error.","This is a Parallel Express Forwarding (PXF) error message that indicates a detection and correction of a typically rare event. If the error is persistent, it may indicate faulty hardware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600","6","NULLQID","PXF([dec]):Null-QID ([chars]) [int] packets dropped.","The SIP-600 line card has encountered an invalid queue. The packet has been dropped. The packet will be counted in the null queue statistics. Packet traffic should continue normally.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600_PARSING_ENGINE","3","DROP_FIFO_OVERFLOW","Parsing Engine Drop Fifo Overflow","The SIP-600 parsing engine has detected that the drop FIFO queue has exceeded the maximum limit. New updates will be discarded. The parsing engine continues to process data from the interfaces if possible.","If traffic has resumed, no action is required. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600_PARSING_ENGINE","3","INTERRUPT_ERROR","[chars]","The SIP-600 parsing engine has detected the specified interrupt event. The message text on the console or in the system log provides more information on this error. The parsing engine continues to process data from the interfaces, if possible.","If traffic has resumed, no action is required. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600_PARSING_ENGINE","3","MASTER_ABORT","Parsing Engine CPU Master Abort Error","The SIP-600 parsing engine has detected a CPU Master Abort Interrupt. A read to a write-only register or a write to a read-only register could cause this interrupt. The parsing engine continues to process data from the interfaces, if possible.","If traffic has resumed, no action is required. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600_PARSING_ENGINE","3","PARITY_ERROR","Parsing Engine CPU Parity Error","The SIP-600 parsing engine has detected a CPU parity error. A hardware fault is suspected on the second occurrence only. Otherwise, the parsing engine continues to process data from the interface if possible.","If traffic has resumed, no action is required. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600_PARSING_ENGINE","3","RP_INT_WATCHDOG_TIMEOUT","Parsing Engine RP Interface Watchdog Timeout","The SIP-600 parsing engine has detected an RP interface watchdog timeout. The RP interface process has not relinquished the processor for the watchdog timeout period. The parsing engine continues to process data from the interfaces, if possible.","If traffic has resumed, no action is required. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600_QOS","2","INITFAIL","SIP-600 Initialization Failed [chars]: [chars] [dec] [dec]","The SIP-600 could not initialize the memory that is needed for the QoS feature. A hardware problem has occurred on the line card that prevents QoS from functioning.","If QoS is a desired feature, try to reload the line card. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600_QOS","2","NOMEM","Memory Allocation Failure - [chars]: [chars] [dec] [dec]","SIP-600 could not allocate the memory that is required for the QoS feature. This condition might indicate that more memory must be installed on the affected line card or platform to service all features and related entries that are enabled in the configuration.","Check available memory and install more if necessary. If sufficient memory is available, reload the Cisco IOS image on the affected line card or platform. If the error persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600_QOS","3","CLASSIFYUPDATE","SIP-600 Update QoS Classify Hardware Failed - [chars]: [chars] [dec] Cause: [hex]","SIP-600 received an error on the specified hardware classify entry when attempting the specified action.","If the error occurs on allocating any of the Default Classify Entries, attempt to reload the line card because traffic cannot be forwarded out this line card. If the error occurs in all other cases, remove the QoS action just performed at the user interface, wait a period of time, then reapply the service-policy. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600_QOS","3","EXCEEDEXCESSQRATE","SIP-600 Exceeded system maximum excess queue rates - [chars]: [chars] [dec] Cause: [hex]","The SIP-600 received an error on the specified hardware queue when attempting the specified action. This condition is the result of attempting to configure a QoS action. The sum of excess bandwidth for all allocated queues has exceeded the system limit.","Remove the service policy that failed and try applying the shape command to each of the classes if they are not already configured. Then reapply the service policy. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600_QOS","3","EXCEEDGUARTQRATE","SIP-600 Exceeded Guaranteed Rates on interface - [chars]: [chars] [dec] Cause: [hex]","The SIP-600 received an error on the specified hardware queue when attempting the specified action. This condition is the result of attempting to configure a QoS action. The sum of all queue-guaranteed rates has exceeded the maximum that can be configured for the interface to which the queues are applied. This condition could be caused when the priority command is configured without the police command.","Add the police command to limit the rate of the priority queue. If this is not the problem, remove the service policy and reapply it. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600_QOS","3","INSUFFDFLTBW","SIP-600 Insufficient bandwidth for default processing: port [dec] queue id [dec] Cause: [hex]","The SIP-600 reserves 1 percent of the bandwidth of a port for router control packets. When a service policy is applied, this bandwidth is first deducted from the QoS class default queue. If there is not sufficient bandwidth in the class default queue and the sum of queue-guaranteed bandwidth exceeds the link rate, this message is generated instead of the EXCEEDGUARTQRATE message.","Determine if there is any bandwidth available for class default so that space is made available for the port's queue to handle control packets. Reduce the amount of bandwidth configured on user-defined classes so that more bandwidth is available for class default. If necessary, explicitly configure bandwidth for class default by entering the bandwidth command. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600_QOS","3","NORESOURCE","SIP-600 Out of Resources- [chars]: [chars] [dec] Cause: [hex]","The specified resource has been depleted from the SIP-600.","Change the SIP-600 configuration to conserve the specified resource."
"SIP600_QOS","3","NOTFOUND","SIP-600 Software Element Not Found - [chars]: [chars] [dec]","SIP-600 client could not locate a required software element.","Reload the Cisco IOS image on the affected line card or platform. If the error persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600_QOS","3","NOTSUP","SIP-600 Feature Not Supported - [chars]: [chars] [chars]","The SIP-600 does not support the specified feature.","Change the SIP-600 configuration so that it does not include the specified feature."
"SIP600_QOS","3","QEXCEEDWREDGRP","SIP-600 Exceeded WRED limit groups for queue [dec]","The SIP-600 depleted available resources when configuring WRED on the specified hardware queue. This condition is a result of attempting to configure a QoS action.","For each queue, there is a limited number of unique WRED limits sets that can be configured. The user's configuration action has caused the limits to go beyond the system limit. As a result, WRED is not configured on that queue. The following configuration illustrates three unique sets of WRED min/max limits:"
"SIP600_QOS","3","QUPDATE","SIP-600 Update Queue Hardware Failed - [chars]: [chars] [dec] Cause: [hex]","The SIP-600 received an error on the specified hardware queue when attempting the specified action. This condition is the result of attempting to configure a QoS action.","There are a variety of reasons that this condition occurs: 1) If the user configuration action was to remove a service policy and then reapply a service policy to the same interface, it is possible that queues are still draining, which prevents new queues from being allocated. You need to remove the service-policy that failed, wait for a period of time, and then reapply the service policy. 2) It is possible that the number of resources has been depleted. You can consolidate your current QoS configuration to free up resources, and then try reapplying your new configuration. 3) If the error was the result of removing queue hardware, then there is a hardware problem that must be reported. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIP600_QOS","3","QWREDGTQLIMIT","SIP-600 WRED maximum threshold exceeds queue-limit for queue [dec]","The WRED maximum threshold values should be greater than the assigned queue limit. This condition is the result of the user attempting to configure WRED or changing bandwidth rates, which changes queue-limit values. If this error has occurred, the queue is allocated but WRED is not enabled.","Make sure that the queue-limits configured does not exceed any of the WRED max_threshold values. If the queue-limit command is not configured, configure one that is greater than WRED max_threshold values."
"SIP600_QOS","4","NOTINSHAPE","Warning - Ingress shaping on [chars] not supported on this interface.","Ingress shaping on the specified precedences or DSCP is not supported on this interface because such packets are control data, which go through a separate high-priority path.","Because the specific match statements are ignored, no action is required."
"SIPSPA","3","BADCMD","[chars]: Unsupported command [dec], arg0=[hex], arg1=[hex], arg2=[hex]","The route processor issued a command that the software was not able to process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIPSPA","3","BAD_IFCOMTYPE","Bad ifcom message type=[int]","The route processor sent a message that the software was not able to process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIPSPA","3","BADINT","Attempted to access HWIDB for port [int]","The line card attempted to access the hardware interface descriptor block (IDB) associated with a nonexistent port.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIPSPA","3","CMDNOINT","HWIDB Null for command [dec], arg=[hex]","The route processor issued a command that the software was unable to process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIPSPA","3","DEVICE_ERROR","subSlot [dec], spatype [hex]. Device error: [chars]","An error related to a device on the SPA has been detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIPSPA","3","EFC_CHAN_ERR","EFC error - interface [chars], vc [dec], anyphy [dec], err_code [dec] : [chars]","There was a failure to configure EFC channel or parameters.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIPSPA","3","FCI_NOT_SET","Bay [dec]: [chars]: FCI type not set","An FCI type of zero was detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIPSPA","3","HWIDB_FAILURE","Creation: port [dec] vc [dec]","There was a failure to create a hardware interface descriptor block (IDB).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIPSPA","3","INVALID_ANYPHY","Bay [dec] - Invalid anyphy number [int] for vc [dec]","The specified interface has an invalid anyphy number.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIPSPA","3","IPCALLOCFAIL","Failed to allocate IPC buffer [chars]","The line card failed to allocate a buffer for communication with the route processor.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIPSPA","3","IPCSENDFAIL","Failed to send IPC message [chars]","The line card failed to send a message to the route processor.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIPSPA","3","ISR_RC_ERROR","ISR return code out of range. rc=[dec]","The ISR error return code is out of range.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIPSPA","3","LINKREC_ERROR","Link record error - Bay [dec] vc [dec], error code [dec]","There was an error during processing of the link record structure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIPSPA","3","MESSAGE_ERROR","Bay [dec]: [chars]","An unexpected error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIPSPA","3","MSGTOOBIG","Message length exceeds max, [int] bytes","The line card attempted to send too large a message to the route processor.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIPSPA","3","NODISPATCH","Dispatch vector Null, cmd=[dec], dintf=[dec]","No command dispatch vector was found for the specified interface.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIPSPA","3","POWER","Bay [dec] 12V power is [chars]","The SPA 12 V power fault indicator is displaying the indicated condition.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIPSPA","3","SONET_CLOCK_FAILED","SPA Sonet clock has failed (status = [hex])","The SPA SONET clock has failed. SPAs that rely on the SPA SONET clock for proper operation, such as POS and ATM, will be affected.","If the SPA SONET clock does not recover, perform an online insertion and removal (OIR)."
"SIPSPA","3","SONET_CLOCK_RECOVERED","SPA Sonet clock has recovered (status = [hex])","The SPA SONET clock has recovered.","No action is required."
"SIPSPA","3","SPI4_CONFIG_FAILURE","Bay [dec], spi4 configuration failure, error [dec]","An attempt to configure the SPI4 interface has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIPSPA","3","SPI4_INIT_FAILURE","Bay [dec] initialization failure","An attempt to create a SPI4 subblock has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIPSPA","4","MAX_BANDWIDTH","Total SPA bandwidth exceeds line card capacity of [int] Mbps","The total bandwidth of SPAs exceeds the specified rated capacity of this line card.","Refer to the line card guidelines for the maximum allowed aggregated SPA bandwidth for the line card."
"SIPSPA","4","MAX_BANDWIDTH_NS","Total SPA bandwidth exceeds line card capacity, full utilization of installed SPA interfaces is not supported","The total bandwidth of SPAs exceeds the rated capacity of this line card.","Refer to the line card guidelines for the maximum allowed aggregated SPA bandwidth for the line card."
"SIPSPA","4","SPABUS","Bay [dec] [chars] failed. sz=[int] rd_par=[int] noresp=[int] err_l=[int] addr=[hex] data=[hex] parity=[hex] deadman=[int]","The SPA bus has reported an error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIPSPA","4","SPABUS2","Bay [dec] [chars] failed. sz=[int] rd_par=[int] noresp=[int] absent=[int] err_l=[int] addr=[hex] data=[hex] parity=[hex] deadman=[int]","The SPA bus has reported an error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SIPSPA","6","ERRORRECOVER","A Hardware or Software error occurred on [chars]. Reason : [chars] Automatic Error recovery initiated. No further intervention required.","An error occurred in one of the devices. Automatic recovery will be attempted. If recovery succeeds, no further messages will be logged and no action will be required.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLB","4","CF","Unexpected error: [chars]","An unexpected error occurred in SLB slave replication.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLB","4","CF_BULK","[chars]","An unexpected error has occurred in SLB slave replicationand bulk synchronization.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLB","4","CF_IPC","Slave replication messages are creating a backlog in IPC. Some SLB objects may not be synchronized.","Due to an IPC resource contention, SLB was unable to replicate all objects.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLB","4","CF_NUM","Unexpected error: [chars] [dec]","An unexpected error has occurred in SLB slave replication.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLB","4","CF_RATE","Overrun of SLB's slave replication rate, some SLB objects may not be synchronized.","Due to a high connection rate, SLB was unable to replicate all objects.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLB","4","IF_REMOVED","Access interface removed: [chars] being set to outofservice.","An interface being referenced in SLB access configuration has been removed. The virtual server or firewall farms referencing this interface will be brought out of service.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLB","4","PROBE","Probe %s for %i:%u %s","An error occured during SLB probe operation","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLB","6","REAL","Real %s (%s) has changed state to %s","Informational message whenever a real server changes its state to/from OPERATIONAL: possible causes might be e.g. testing, probe testing, maxconns","No action required."
"SLB","6","UNAVAILABLE","Real %s (%s) has changed state to %s","Informational message whenever a real server changes its state to/from OPERATIONAL: possible causes might be e.g. testing, probe testing, maxconns","No action required."
"SLBSCPU","3","UNAVAILABLE","Cannot create SLB SCPU Process","Error occurred during initialization of SLB process on SLB CPU","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLBSCPU","3","UNAVAILABLE","Did not receive ICC response","Error occurred during communication between SLB CPU","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLBSCPU","3","UNAVAILABLE","Failed to get request packet for ICC","Error occurred during communication between SLB CPU","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLBSCPU","3","UNAVAILABLE","Unable to request initial config download from main CPU.","After initialization, SLB CPU requests main CPU to send configuration readfrom NVRAM. This message is generated when a failure occurs in communication.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLBSCPU","3","UNAVAILABLE","Unknown type of indication %x","Microcode is sending bad indication type.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLBSCPU","6","UNAVAILABLE","Request %d initial config download from main CPU.","After initialization, SLB CPU requests main CPU to send configuration readfrom NVRAM. This message is indicates a request was sent.SLB_DFP-4Error Message    %SLB_DFP-4-UNAVAILABLE: Agent %i:%u - Could not parse message Explanation    Could not parse message from SLB DFP Agent","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLB_DFP","4","UNAVAILABLE","Agent %i:%u - Have not received keep alive","The system has not received a keepalive message from the SLB DFP Agent.","Verify that the DFP Agent is reachable via ping or traceroute. Verify that the DFP Agent on the server is running. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLB_DFP","4","UNAVAILABLE","Agent %i:%u - Invalid message length - %u","Too many errors reading message header from SLB DFP Agent","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLB_DFP","4","UNAVAILABLE","Agent %i:%u - Message length %u, too big","A message from the SLB DFP Agent exceeds the allowable maximum size.","A message exceeding allowable maximum size can be caused by a connection error between DFP Manager and Agent. Try to restart DFP Agent (by unconfiguring and reconfiguring it) to see if it fixes the connection error. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLB_DFP","4","UNAVAILABLE","Agent %i:%u - Message type %u, vector %u too big","A message from the SLB DFP Agent exceeds the allowable maximum size.","A message exceeding allowable maximum size can be caused by a connection error between DFP Manager and Agent. Try to restart DFP Agent (by unconfiguring and reconfiguring it) to see if it fixes the connection error. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLB_DFP","4","UNAVAILABLE","Agent %i:%u - Send failed","An attempt to send a message to the SLB DFP Agent has failed.","Verify that the DFP Agent is reachable via ping or traceroute. Verify that the DFP Agent on the server is running. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLB_DFP","4","UNAVAILABLE","Agent %i:%u - Socket alreay open","The system tried to open Socket to SLB DFP Agent that is already open.","If the problem persists, unconfigure and reconfigure SLB DFP. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLB_DFP","4","UNAVAILABLE","Agent %i:%u - Socket_connect failed","Socket_connect to SLB DFP Agent failed","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLB_DFP","4","UNAVAILABLE","Agent %i:%u - Socket_recv error %d","Socket_recv error receiving message from SLB DFP Agent","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLB_DFP","4","UNAVAILABLE","Agent %i:%u - Too many read errors","Too many errors reading message header from SLB DFP Agent","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLB_DFP","4","UNAVAILABLE","Agent %i:%u - Unknown connection state %u","Unknown connection state processing SLB DFP timer","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLB_DFP","4","UNAVAILABLE","Agent %i:%u - Unknown message type %u","Message from SLB DFP Agent has unknown type","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLB_DFP","4","UNAVAILABLE","Agent %i:%u - Unknown message type %u, vector %u","An unknown message type received from SLB DFP Agent","An unknown message can be caused by a connection error between DFP Manager and Agent. Try to restart DFP Agent (by unconfiguring and reconfiguring it) to see if it fixes the connection error. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLB_DFP","4","UNAVAILABLE","Manager %i is reconnecting","The SLB Manager is reconnecting without disconnecting","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLB_DFP","4","UNAVAILABLE","Unexpected error: %s","An unexpected error occurred while performing SLB DFP operation","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLIP","2","UNAVAILABLE","Impossible input state %x","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLIP","2","UNAVAILABLE","Impossible quoted character %x","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLOTDUMP","3","UNAVAILABLE","Core dump error slot %d: %s","An error occured during a core dump of slot","None."
"SLOT_FPD","3","UNAVAILABLE","Failed to %s FPD subblock in Slot %u.","Failed to create, delete, or populate a FPD subblock due to operation error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLOT_FPD","3","UNAVAILABLE","Failed to get FPD version for FPD=%u in Slot %u: %s.","Failed to get FPD version due to either IPC problem or operation error. The card will be disabled.","Check module seating and module status. Ensure compatibility among FPD and IOS by comparing output of command show hw-module slot fpd with IOS Release Notes. Obtain IOS version by command show version."
"SLOT_FPD","3","UNAVAILABLE","Failed to get baseboard hardware revision number in Slot %u.","Failed to get the board's revision number.","Check module seating and module status. Re-insert the module. Contact TAC if this message is seen again."
"SLOT_FPD","3","UNAVAILABLE","Failed to upgrade FPD for slot %d, %s.","The FPD image upgrade operation failed. The cause could be a wrong image file, error in accessing fpga storage, physical interrupt such as power failure or card removal. Depending on the slot type and error cause, the card could be in an unusable state. Normally the system automatically reattempts the upgrade and shuts the card after repeated failures.","Do not interrupt the system while an FPD upgrade is in progress. Obtain the matching FPD package. Refer to IOS Release Notes for more information on obtaining the correct FPD package for the card. Review the output of the RP FPD logs."
"SLOT_FPD","4","UNAVAILABLE","%s on slot %u.","Display the upgrade state","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLOT_SYNC","2","UNAVAILABLE","%s","A software error occurred during initialization of the Interface Sync RF subsystem","Check for sufficient processor memory. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLOT_SYNC","3","UNAVAILABLE","Incorrectly formatted message (0x%x, 0x%x) received by %s","Inconsistent message data was received from the peer CPU, possibly due to an incompatible image version.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLOT_SYNC","3","UNAVAILABLE","Received a slot sync message with subcard count as %d for slot %d","A slot sync message with bad subcard count is being recvd","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLOT_SYNC","3","UNAVAILABLE","Sending a slot sync message with subcard count as %d for slot %d","A slot sync message with bad subcard count is being sent","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLOT_SYNC","3","UNAVAILABLE","Unable to transmit message type %d from %s","A transmit error occurred while sending msg to other CPU, due to msg translation","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLOT_SYNC","3","UNAVAILABLE","Unable to transmit message type %d from %s","A transmit error occurred while sending msg to other CPU, due to non-availability of buffer","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLOT_SYNC","3","UNAVAILABLE","Unknown message type 0x%x received by %s","An unknown message type was received from the peer CPU, possibly due to an incompatible image version.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SLOT_SYNC","5","UNAVAILABLE","Msgtype %s sent by %s unsupported by peer.","Peer responded that it didn't recognize a message sent by this CPU, possibly due to a different image version.","May require a software upgrade on the Standby CPU. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SM","4","BADEVENT","Event '%s' is invalid for the current state '%s': %s %s","An attempt was made to post an event to a state machine that is invalid for the current state.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SM","4","PERSIST","Persistent event '%s' did not leave the current state '%s': %s %s","An attempt was made to post a persistent event to a state machine that would cause an infinite loop in the current state.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SM","4","STOPPED","Event '%s' ignored because the state machine is stopped: %s %s","An attempted was made to post an event to a state machine that has already been stopped.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SM","4","UNAVAILABLE","Event '%s' ignored because the state machine is stopped: %s %s","An attempted was made to post an event to a state machine that has already been stopped.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SM","4","UNAVAILABLE","Event '%s' is invalid for the current state '%s': %s %s","An attempt was made to post an event to a state machine that is invalid for the current state.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SM","4","UNAVAILABLE","Internal error while initializing state machine '%s', state '%s': %s","An attempt was made to initialize an invalid state machine.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SM","4","UNAVAILABLE","Persistent event '%s' did not leave the current state '%s': %s %s","An attempt was made to post a persistent event to a state machine that would cause an infinite loop in the current state.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SMC","2","BAD_ID_HW","Failed Identification Test in [chars] [[dec]/[dec]] The module in [chars] in this router may not be a genuine Cisco product. Cisco warranties and support programs only apply to genuine Cisco products. If Cisco determines that your insertion of non-Cisco memory, WIC cards, AIM cards, Network Modules, SPA cards, GBICs or other modules into a Cisco product is the cause of a support issue, Cisco may deny support under your warranty or under a Cisco support program such as SmartNet.","The hardware in the specified location could not be identified as a genuine Cisco product.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SMC","2","FAILED_ID_HW","Failed Identification Test in [chars] [[dec]/[dec]]","An error occurred while identifying the hardware in the specified location.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SMC","2","PROTO_HW","Module ([chars]) is a registered proto-type for Cisco Lab use only, and not certified for live network operation.","The hardware in the specified location is a prototype module from Cisco and should not be used in a live network.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SMF","4","UNAVAILABLE","failed to create SMF entry for %e on %s with result %08x","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SMI","3","IMAGELIST_FAILED","Default imagelist creation failed.","flash:default_imagelist creation failed. Possible reasons for this failure is that there is inadequate space in the director flash or new file creation error or default image not configured.","Check the Director flash space. Free some space. default_imagelist would need about 100 bytes of space and configure the Device as director again"
"SMI","3","IMG_CFG_NOT_CONFIGURED","%s (IP Address :%i) : The Director does not have a image file or a configuration file configured for this Product-ID","The Director does not have image file or configuration file configured for this SKU. As a result of this the image and configuration upgrade would not take place properly.","The user needs to configure a image file and the configuration file for a built in Product-ID or for a custom Product-ID. The cli to under which this can be configured is vstack group . Both the image and configuration file should be configured for correct operation."
"SMI","3","INTERNAL_ERROR","%s - %d","The director encountered an internal software error.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SMI","3","INVALID_IMGLIST_FILE","Device (IP address: %i) %s upgrade failed for invalid imagelist file","The Client Device upgrade failed because the specified image list file was not valid. A valid imagelist file is a text file that contains only the names of the images.","Verify that the imagelist file is a text file containing the names of images that are available to be downloaded."
"SMI","3","NOMEMORY","Smart Install memory allocation failure; could not allocate %s","An attempt to allocate memory for Smart Install failed. More RAM may be required to execute this image.","Copy the error message exactly as it appears, gather the show tech output and report it to your technical support representative."
"SMI","3","SMI_CLIENT_BACKUP_FAILURE","Client Device startup configuration backup fail on repository","This message is displayed on Client Device when an attemptto backup its startup configuration fails.","Please consult the configuration guide for more details. Verify that you can ping from client to the director and vstack backup feature is enabled. Also check the reachability from client to the repository. Check the directory setting on repository is correct especially when the repository is external tftp server."
"SMI","3","SMI_DIRECTOR_BACKUP_FAILURE","Client Device (%i) startup configuration backup fail on repository: %s - reason: %s","This message is displayed on the Director when the Client Device fails to backup its startup configuration to the specified repository.","Please consult the configuration guide for more details. Verify that you can ping from client to the director and vstack backup feature is enabled. Also check the reachability from client to the repository. Check the directory setting on repository is correct especially when the repository is external tftp server."
"SMI","3","TAILOR_FAILED","Legacy switches will not be upgraded","Tailored config creation failed. Possible reasons for this failure is that there is inadequate space in the director flash or new file creation error","Check the Director flash space. Free some space. Tailored config would need about 100 bytes of space and configure the Device as director again"
"SMI","3","UPGRD_FAILED","Device (IP address: %i) %s upgrade failed","The Client Device upgrade failed. Possible reasons include network reachability to the Director or tftp server, or a missing or incorrect upgrade file.","Verify the configuration on the Director. Check the reachability of the tftp server from the Client. Verify that the image or configuration file exists on the tftp server and is specified correctly."
"SMI","5","DIRECTOR","Director is %s","SMI Director status changed","Informational only. No action required."
"SMI","6","AUTOINSTALL","%s AUTOINSTALL","Aborted or continued with AUTOINSTALL","Informational only. No action required."
"SMI","6","CLIENT_CONN_FAILED","Device (IP address: %i) failed to connect to Director (IP address : %i)","Client Device has failed to connect to the Director. This could be because of reachability issue. This could be also because the Client does not have Director's IP address.","Verify that the IP address of the Director is configured properly in the Client."
"SMI","6","INCORRECT_CFG","No image and config configured for this %s %s","No configuration present for the Switch stack on Director.","Configure a group for this Switch stack. Please consult the configuration guide for more details."
"SMI","6","INVALID_PKT_SIZE","Received invalid packet from %s (IP Address : %i), SMI Version : %d, Message Type : %d","The Client/Director has received an invalid packet size during exchange of smart install messages. This is because of a newer version of smart install protocol is trying to interoperate with a older version of smart install. The new message type may not be supported by the older version.","The network Administrator needs to see that the Director has the latest version of the smart install running. A new version of Director can interoperate with a older version of Client"
"SMI","6","SMI_CLIENT_BACKUP_SUCCESS","Client Device startup configuration backup successful on repository","This message is displayed on the Client to indicate that the Client Device has successfully backed up its startup-configuration to the repository specified by the director.","Please consult the configuration guide for more details."
"SMI","6","SMI_DHCP_ERR","Device failed to %s DHCP %s","The Director failed to configure or remove a DHCP parameter, such as a DHCP pool, subnet, or pool options.","Verify that the configuration setting is a permitted value."
"SMI","6","SMI_DHCP_SUCCESS","Device to %s DHCP %s","The Director succeeded in configuring a DHCP parameter, such as a DHCP pool, subnet, or pool options.","Informational only. No action required."
"SMI","6","SMI_DIRECTOR_BACKUP_SUCCESS","Client Device (%i) startup configuration backup successful on repository: %s","This message is displayed on the Director to indicate that the Client Device has successfully backed up its startup-configuration to the repository specified by the director.","Please consult the configuration guide for more details."
"SMI","6","SMI_INVALID_MESSAGE","Received invalid message from %s (IP Address : %i), SMI Version : %d, Message Type : %d","The Client/Director has received an invalid message type during exchange of smart install messages. This is because of a newer version of smart install protocol is trying to interoperate with a older version of smart install. The new message type may not be supported by the older version.","The network Administrator needs to see that the Director has the latest version of the smart install running. A new version of Director can interoperate with a older version of Client"
"SMI","6","SMI_JOIN_WINDOW_MESSAGE","SMI Join window %s on IBD(IP address: %i)","This message indicates the Start or End of the Smart Install Join window","The Network Administrator needs to knowthat the join window has started or terminated. If the join window feature is enabled then client devices scheduled for upgrade during this period would get the image and configuration file from the Director ."
"SMI","6","SMI_VLAN_MSG","Make sure that SMI Startup Management Vlan %d exists on IBD","Make sure that SMI Startup Management VLAN exists on IBD.","If the startup management VLAN does not exist on the director, create the VLAN on the IBD."
"SMI","6","SWITCH_ADD","New Device detected by Director with mac address: %e","A new Device has been detected in the network and has been added to the Director database.","Informational only. No action required."
"SMI","6","SWITCH_REMOVE","Device %e removed from the Director Database","A Device has been removed from the Director database because it has stopped communicating. It may have been removed from the network.","Informational only. No action required."
"SMI","6","SWITCH_REPLACE","Device %e is being replaced by %e Device","Device Replaced into the network","Informational only. No action required."
"SMI","6","UPGRD_STARTED","Device (IP address: %i) %s upgrade has started","Client Device image/configuration upgrade started","Informational only. No action required."
"SMI","6","UPGRD_SUCCESS","Device (IP address: %i) %s has upgraded successfully","The Device has been successfully upgraded with a new image or configuration file.","Informational only. No action required."
"SMI_ISSU","2","GET_BUFFER","Smart Install ISSU client failed to get buffer for message. Error: %d (%s)","The Smart Install ISSU client failed to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show checkpoint client commands and your pertinent troubleshooting logs."
"SMI_ISSU","2","INIT","Smart Install ISSU client initialization failed to %s. Error: %d (%s)","The Smart Install ISSU client could not be initialized. This initialization failure must be addressed before in-service software upgrade or downgrade can be performed successfully. If you do not address this failure, there will be downtime during software upgrade or downgrade.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support commands and your pertinent troubleshooting logs."
"SMI_ISSU","2","SEND_NEGO_FAILED","Smart Install ISSU client failed to send negotiation message. Error: %d (%s)","The Smart Install ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show checkpoint client commands and your pertinent troubleshooting logs."
"SMI_ISSU","2","SESSION_NEGO","Smart Install ISSU client encountered unexpected client nego_done. Error: %d (%s)","An ISSU-compliant client transitions through a series of internal states. The Smart Install ISSU client encountered a 'client negotiation done' state that was unexpected. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show issu sessions, show issu negotiated capability commands and your pertinent troubleshooting logs."
"SMI_ISSU","2","SESSION_REGISTRY","Smart Install ISSU client failed to register session information. Error: %d (%s)","The Smart Install ISSU client failed to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show issu sessions, show issu negotiated capability commands and your pertinent troubleshooting logs."
"SMI_ISSU","3","INVALID_SESSION","Smart Install ISSU client does not have a valid registered session.","The Smart Install ISSU client does not have a valid registered session.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show issu sessions, show issu negotiated capability commands and your pertinent troubleshooting logs."
"SMI_ISSU","3","MSG_NOT_OK","Smart Install ISSU client Message Type %d is not compatible","The Smart Install ISSU client received an incompatible message from the peer device. The message cannot be processed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show issu sessions, show issu negotiated version commands and your pertinent troubleshooting logs."
"SMI_ISSU","3","MSG_SIZE","Smart Install ISSU client failed to get the MTU for Message Type %d. Error: %d (%s)","The Smart Install ISSU client failed to calculate the MTU for the specified message. The Smart Install ISSU client is not able to send the message to the standby device.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show issu sessions, show issu negotiated version commands and your pertinent troubleshooting logs."
"SMI_ISSU","3","SESSION_UNREGISTRY","Smart Install ISSU client failed to unregister session information. Error: %d (%s)","The Smart Install ISSU client failed to unregister session information.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show issu sessions, show issu negotiated version commands and your pertinent troubleshooting logs."
"SMI_ISSU","3","TRANSFORM_FAIL","Smart Install ISSU client %s transform failed for Message Type %d. Error: %d (%s)","The Smart Install ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In both cases, the Smart Install state between the active device and the standby device is not identical.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show issu sessions, show issu negotiated capability commands and your pertinent troubleshooting logs."
"SMRP","2","UNAVAILABLE","SMRP assertion failed: %s","The software detected an inconsistency. This is considered a serious error. The router attempts to continue, but SMRP processing may be impaired.","Copy the error message exactly as it appears, noting any SMRP problems that you are experiencing, and report it to your technical support representative."
"SMSC_RP","3","GETHWVER_FAILED","Unable to set 7600-SSC-400 in slot [dec] in single-spa-mode because of error in obtaining its hardware revision.","The 7600-SSC-400 could not be set to single-SPA mode.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SMSC_RP","3","NO_SCP_BUFFER","Unable to set 7600-SSC-400 in slot [dec] in single-spa-mode because of insufficient scp buffers.","The 7600-SSC-400 could not be set to single-SPA mode.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SMSC_RP","3","SSC_SSPA_RETRY","7600-SSC-400 in slot [dec] is reset as a [dec] try to set it in single-spa-mode.","The specified slot has reset in an attempt to set it to single-SPA mode. A maximum of three retries are performed.","If the third retry is unsuccessful, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SMSC_RP","3","SSC_SSPA_SHUT","7600-SSC-400 in slot [dec] is shutdown because it cannot be set in single-spa-mode","The specified slot has been shut down because it cannot be set to single-SPA mode.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SMRP","5","UNAVAILABLE","%s: SMRP neighbor down - %s","A neighboring SMRP router is now down.","Notification message only. No action required."
"SMRP","5","UNAVAILABLE","%s: SMRP port down - %s","An SMRP port is down and is no longer operational.","Notification message only. No action required."
"SMRP","6","UNAVAILABLE","%s: SMRP neighbor up - %s","A neighboring SMRP router has appeared.","Notification message only. No action required."
"SMRP","6","UNAVAILABLE","%s: SMRP port up - %s","An SMRP port has come up.","Notification message only. No action required."
"SMRP","7","UNAVAILABLE","SMRP Debug: %s","This message is generated by some debug commands to provide additional information about conditions in SMRP.","If you are experiencing problems in SMRP, these messages should be provided, along with any other information, in a report to your technical support representative."
"SMSC_RP","6","INVALID_HW_VERSION","Single-spa-mode is not allowed for 7600-SSC-400 hardware version [dec].[dec].","Only 7600-SSC-400 versions greater than 0.3 can be set in single-SPA mode.","To use single-SPA mode, use 7600-SSC-400 versions greater than 0.3."
"SNAPSHOT","2","UNAVAILABLE","Bad state for Snapshot block %s[%d], location %d","An internal software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SNAPSHOT","2","UNAVAILABLE","Exceeded maximum dialer interfaces to watch. Ignoring %s","Snapshot is being used over more than 100 DDR interfaces.","Do not use snapshot over more than 100 DDR interfaces."
"SNASW","3","CLS_LOG_0","PROBLEM - [int] - Could not validate process handle [chars]","CLS has passed the SNA switch a DLC packet, but the SNA switch does not have a valid handle to invoke the correct SNA process. The CLS message has been discarded.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SNASW","3","HPR_LOG_20","PROBLEM - [int] - Remote node supplied a corrupted RSCV: the next hop is the local CP [chars]","A high performance routing (HPR) route setup request or response unit (RU) has been received with a Route Selection Control Vector (RSCV) that gives the local node as the next ANR hop, which is an invalid vector. The remote node is sending invalid protocol data.","Report the error to the remote end administrator."
"SNASW","4","RTP_LOG_10","EXCEPTION - [int] - LFSID in use, moving on to next one. [chars]","An LFSID was found to be in use. The SNA switch will use another one.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SNASW","3","UNAVAILABLE","DLC unrecognized message, header= %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SNASW","3","UNAVAILABLE","Diagnostic trace record too large for configured buffer. Buffer ID %x","A trace record could not be written to one of the cyclic trace buffers, because it was bigger than the whole of the available buffer space. The buffer will be cleared.","Increase the size of the relevant cyclic trace buffer or, if diagnostics are not currently necessary, disable the tracing."
"SNASW","3","UNAVAILABLE","Invalid Input=%s to SNASW %s %x with OldState=%s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SNASW","3","UNAVAILABLE","Invalid message name specified for snasw msg-trap","An invalid message name was supplied on a snasw msg-trap command.","Reissue the command with a valid message name."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - A BIND request received by an LU type 0,1,2 or 3 was rejected by SNA Switch because it failed parameter checks %s","A BIND request was received by an LU type 0,1,2, or 3 that failed parameter checks. The sense codes that apply to this condition are 08210004 - Cryptography required by SLU, not supported by PLU 08210005 - Session key missing 0835xxxx - parameter error at offset xxxx in BIND RU. The offsets that apply to this sense code are 0002 - invalid FM profile 0003 - invalid TS profile 0004 - invalid primary FM usage 0005 - invalid secondary FM usage 0006 - invalid common FM usage 0007 - invalid common FM usage 0008 - invalid secondary send pacing 0009 - invalid secondary receive pacing 000A - invalid secondary send RU size 000B - invalid secondary receive RU size 000E - invalid PS profile (ie. invalid session type) 000F - invalid PS usage (applies to RJE BIND only) 0010 - invalid primary half-session PS usage (applies to RJE BIND only) 0014 - invalid default screen size: rows (applies to 3270 display BIND only) - invalid default buffer size: rows (applies to 3270 printer BIND only) 0015 - invalid default screen size: columns (applies to 3270 display BIND only) - invalid default buffer size: columns (applies to 3270 printer BIND only) 0016 - invalid alternate screen size: rows (applies to 3270 display BIND only) - invalid alternate buffer size: rows (applies to 3270 printer BIND only) 0017 - invalid alternate screen size: columns (applies to 3270 display BIND only) - invalid alternate buffer size: columns (applies to 3270 printer BIND only) 001A - invalid cryptography 001B - invalid cryptography method BIND request will be rejected with the specified sense code. PLU-SLU session is not activated.","If possible investigate the configuration of the system that sent the BIND request. If a configuration error is found then correct it, otherwise contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - A BIND request received by an LU type 0,1,2 or 3 was rejected by SNA Switch because the application connection was not open %s","A BIND request received by an LU type 0,1,2 or 3 was rejected because the application connection was not open. This may be caused by a normal window condition or it may indicate that the system that sent the BIND request is incorrectly configured or is defective. BIND request will be rejected with the specified sense code. PLU-SLU session is not activated.","Investigate the cause of the problem. If it indicates that the system that sent the BIND request is incorrectly configured then correct the configuration error. If it appears that the system is defective then contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - A BIND request received by an LU type 0,1,2 or 3 was rejected by an application connected to SNA Switch %s","A BIND request received by an LU type 0,1,2 or 3 was rejected by an application connected to SNA Switch. BIND request will be rejected with the specified sense code. PLU-SLU session is not activated.","Investigate why the application rejected the BIND request (the sense code should help with this). It may be necessary to investigate the configuration of the system that sent the BIND request (if this is possible). If a configuration error is found then correct it, otherwise contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - A new DSPU has activated with the same node ID and CP name as an existing DSPU %s","A new DSPU has activated with the same node ID/CP name or link address as an existing (active) DSPU. The new link will be deactivated.","Change the node ID or CP name on one of the DSPUs."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - ACTLU received for LU which is not defined locally, and implicit LU definition is not supported %s","ACTLU received for LU which is not defined locally, and implicit LU definition is not supported. This typically indicates a mismatch between this node and the host configuration. LU-SSCP session is not activated (ACTLU is rejected with the specified sense code).","Remove the LU from the host configuration."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - ACTPU, ACTLU, DACTPU or DACTLU received on link on which dependent LUs are not supported %s","ACTPU, ACTLU, DACTPU or DACTLU received over a link on which dependent LUs are not supported. This may indicate an interoperability problem. Request will be rejected with the specified sense code.","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Adjacent node sent a TG number that was already in use by another LS %s","Adjacent node has attempted to use a TG number for this link which is already in use by another link station. This may indicate an interoperability problem. Link activation will fail.","Run a trace on the link station or port to get more diagnostic information on the problem, and contact support with the log and trace."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Adjacent node sent a TG number that was pre-assigned to another LS %s","Adjacent node has attempted to use a TG number for this link which is already pre-defined on another link station. Link activation will fail.","Correct mismatched TG number configuration at this node (using snasw link) or at adjacent node."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - An UNBIND RSP was received at a secondary LU %s","An UNBIND RSP was received at a secondary LU. This is illegal SNA as no UNBIND RQ was sent. The UNBIND RSP is dropped.","The session may not be coming down properly. Check that dependent LU applications are correctly replying to all signals. Otherwise, contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - An active link station has failed %s","An active link station has failed. The link and any sessions using it will be deactivated","Attempt to restart the link. If the problem persists, inspect the log for problems or exceptions logged by the DLC which give more specific reasons for the failure, and follow the actions specified by those logs. Otherwise, run a trace on the specified port or link station to find the reason for the failure."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Attach protocol error %s","Attach protocol error. This may indicate a problem in the partner LU. The sense codes are as follows 080F6051 - Attach security protocol violation 10086011 - LUW identifier format error, or LUW identifier not specified when sync level is syncpt 10086040 - sync level not supported by session, or already-verified not accepted from partner LU 10086031 - PIP not allowed by TP The session will be deactivated with the specified sense code.","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Attach rejected because requested TP is permanently disabled %s","Attach rejected because the specified TP is permanently disabled. This should only occur if an application has explicitly disabled the transaction program. The Attach will be rejected.","Collect trace and contact support."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Attach rejected because requested TP is temporarily disabled %s","Attach rejected because the specified TP is temporarily disabled. The Attach will be rejected.","This condition is not currently supported by SNA Switch, so this log should not occur."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Attach rejected because requested conversation duplex type not supported by requested transaction program %s","Attach rejected because the specified conversation duplex type is not supported by the specified transaction program. This may be a mismatch in the capabilities of the originating transaction program and the destination transaction program, or it may simply be a configuration error. Possible sense codes are as follows. 10086034 Half-duplex Attach, not supported by TP 08640003 Full-duplex Attach, not supported by TP The Attach will be rejected.","Check the conversation duplex type or types supported by the specified transaction program, and check that this matches the conversation type supported defined for the transaction program. If they match, or the transaction program is not defined, there is a mismatch between the originating and destination transaction programs."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Attach rejected because requested conversation type not supported by requested transaction program %s","Attach rejected because the specified conversation type is not supported by the specified transaction program. This may be a mismatch in the capabilities of the originating transaction program and the destination transaction program, or it may simply be a configuration error. The Attach will be rejected.","Check the conversation type or types supported by the specified transaction program, and check that this matches the conversation type supported defined for the transaction program. If they match, or the transaction program is not defined, there is a mismatch between the originating and destination transaction programs."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Attach rejected because requested sync level not supported by requested transaction program %s","Attach rejected because the specified sync level is not supported by the specified transaction program. This may be a mismatch in the capabilities of the originating transaction program and the destination transaction program, or it may simply be a configuration error. The Attach will be rejected.","Check the sync level supported by the specified transaction program, and check that it matches the sync_level defined for the transaction program. If they match, or the transaction program is not defined, there is a mismatch between the originating and destination transaction programs."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Attach rejected because security information invalid %s","Attach rejected because security information invalid. This indicates an attempt to access a secure TP by an unknown user, or a known user who has specified an incorrect password. The Attach will be rejected.","Use the information in the log to locate the attempted security violation."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Attach rejected because security information not specified %s","Attach rejected because security information not specified. This indicates an attempt to access a secure TP without specifying a user ID or password. The Attach will be rejected.","Use the information in the log to locate the security mismatch"
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - BIND or +RSP(BIND) specifies duplex support which is different from that for existing sessions %s","An incoming BIND or +RSP(BIND) has specified a duplex support for the remote LU which is inconsistent with that for existing sessions between the partner LUs. The BIND or +RSP(BIND) is rejected.","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - BIND received with the next hop in the RSCV set to the local node again %s","SNA Switch received a BIND request with a badly formatted RSCV. The CP name for the next hop in the RSCV is this local node again. Sesion activation will fail.","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - BIND(-RSP) request received in response to a BIND request %s","BIND(-RSP) received in response to a BIND request. This may indicate a configuration error, or a protocol error. Common sense codes which typically indicate a configuration error or a normal race condition include 0805xxxx - the session could not be activated as session activation limits have been reached 08060014 - the partner LU is not known 0806xxxx - the BIND specified a resource which is not known 080Fxxxx - security authorization failed 0821xxxx - the BIND supplied an invalid session parameter 0835xxxx - parameter error in BIND RU at offset xxxx Other sense codes include 0812xxxx - session activation failed due to resource shortage at the remote node 083Bxxxx - invalid PCID in BIND RU 0852xxxx - duplicate session activation request 0861xxxx - invalid COS name in BIND RU 088Cxxxx - control vector or subfield missing from BIND RU 0895xxxx - BIND RU contained a control vector that was in error 0896xxxx - BIND RU contained a control vector that was too long Session activation will fail with the specified sense code.","If the sense code indicates a configuration error, check for inconsistencies between the configuration at the local LU and the configuration at the partner LU. If the configuration is consistent and the problem persists, contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Badly formed partner LU name in received BIND request %s","Partner LU name on received BIND request is badly formed. Session activation will fail with the specified sense code.","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Badly-formed BIND request rejected by SNA Switch %s","SNA Switch received and rejected a badly-formed BIND request. This may indicate an interoperability problem. Session activation will fail.","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Both sent and received XIDs indicate the same, non-negotiable, link station role %s","Both sent and received XIDs indicate the same, non-negotiable, link station role. The link activation will fail.","Either correct the local port definition, or the remote definition, so that the link station roles are complementary, or at least one link station is negotiable."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Bracket protocol error %s","BIS protocol error. This may indicate a problem in the partner LU. The sense code is always set to 20100000. The session will be deactivated with the specified sense code.","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Bracket protocol error %s","Bracket protocol error. This may indicate a problem in the partner LU. The sense codes are as follows. 20080000 - partner LU attempted to start bracket after sending BIS 20030000 - partner LU attempted to start bracket after local LU had BID for session successfully, or unexpected RTR request received 20100000 - Received negative response to BID with sense code 088B0000 from a partner LU who supports parallel sessions, or BIS protocol error The session will be deactivated with the specified sense code.","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Branch Network Node received BIND request with badly formed RSCV %s","A Branch Network Node has received a BIND request with a badly formed RSCV. This may indicate an interoperability problem. Session activation will fail.","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - CP capabilities exchange failed because of contention loser CP-CP session failure %s","CP capabilities exchange failed because of contention loser CP-CP session failure. Contention winner CP-CP session will be deactivated. SNA Switch will attempt to reactivate CP-CP sessions with this adjacent CP.","This log flags the fact that a CP-CP session failed. Other logs give more details on the reason for the session failure (eg. insufficient resources, link failure)."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - CP capabilities exchange failed because of contention winner CP-CP session failure %s","CP capabilities exchange failed because of contention winner CP-CP session failure. Contention loser CP-CP session will be deactivated. SNA Switch will attempt to reactivate CP-CP sessions with this adjacent CP.","This log flags the fact that a CP-CP session failed. Other logs give more details on the reason for the session failure (eg. insufficient resources, link failure)."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - CP capabilities exchange failed because of protocol error %s","CP capabilities exchange has failed because of protocol error. This may indicate an interoperability problem. Sense codes are as follows. 08060030 - CP capabilities requested by unknown CP 08210002 - CP capabilities requested on other than CPSVCMG mode 08150007 - CP capabilities requested when CP-CP session already established 08B60000 - CP-CP sessions not supported by adjacent node 08090039 - CP transaction error CP-CP sessions with the specified adjacent node will be deactivated. SNA Switch will not attempt to reactivate CP-CP sessions with this adjacent CP.","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - CP-CP session deactivated because of excessive delay %s","An adjacent node has not responded within a reasonable period to a request on a CP-CP session. SNA Switch will deactivate CP-CP sessions with this adjacent node. CP-CP sessions are deactivated with the sense code 08640002.","Contact the supplier of the adjacent node."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - CP-CP sessions deactivated while directed Locate outstanding %s","CP-CP sessions deactivated while directed Locate in process. Session activation may fail.","This log simply flags the fact that a session failure impacted a pending directed Locate. Other, more specific, logs give reasons for the session failure and appropriate actions."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Conflicting requirements for error recovery, link is not HPR-capable %s","Conflicting requirements for error recovery between the local node and a partner node when attempting to activate a link that is HPR-capable. Link will activate but will not be HPR-capable.","To allow HPR protocols to be used on the link the local and partner nodes must be able to accommodate the other's error recovery requirement. At the minimum this will require reconfiguration but may not always be possible."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Conversation ended by protocol error %s","The session being used by a conversation has been deactivated because of a protocol error, causing the conversation to fail. The conversation will be terminated, either by an APPC primary_rc of NAP_CONV_FAILURE_NO_RETRY, or a CPI-C return_code of CM_RESOURCE_FAILURE_NO_RETRY.","This log gives information on which TPs and conversation have been affected by a protocol error on a session. Other, more specific problem or exception logs give more information on the protocol error. Use the Session identifier to correlate this log with other related logs."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Conversation ended by session outage %s","The session being used by a conversation has been deactivated because of a session outage, causing the conversation to fail. The conversation will be terminated, either by an APPC primary_rc of NAP_CONV_FAILURE_RETRY, or a CPI-C return_code of CM_RESOURCE_FAILURE_RETRY.","This log gives information on which TPs and conversation have been affected by a session outage. Other, more specific, problem or exception logs give more information on the reason for the session outage. Use the Session identifier to correlate this log with other related logs."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Could not validate process handle %s","CLS has passed SNA Switch a DLC packet, but SNA Switch does not have a valid handle to invoke the correct SNA process. The CLS message has been discarded.","Dump traces and contact the Cisco TAC."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - DLC failed %s","A DLC has ended abnormally. All ports and link stations defined on the DLC will be inoperative.","Restart the DLC (using snasw start port). If the problem is persistent, look for DLC specific logs giving more information on the reason for the failure."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - DLC failure during creation %s","The DLC has returned inconsistent data during creation The DLC will be destroyed, and all ports and link stations defined on the DLC will be inoperative.","Run a trace on the DLC and contact support with the log and trace information."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Deactivating session because of insufficient storage %s","Deactivating session because of insufficient storage. SNA Switch will deactivate the session.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Delete failure reply received with sense code that is unrecoverable %s","Delete reply received with a sense code that is unrecoverable. CP-CP sessions to node will be deactivated.","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Detected consistency errors in received BIND request %s","Detected consistency errors in received BIND request. This may indicate an interoperability problem. Sense codes are as follows. 0835xxxx - parameter error at offset xxxx in BIND RU 080F6051 - security error Session activation will fail with specified sense code.","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Detected consistency errors in received BIND response %s","Detected consistency errors in received BIND response. This may indicate an interoperability problem. Sense codes are as follows 0835xxxx - parameter error at offset xxxx in BIND RU 080F6051 - security error Session will be deactivated with specified sense code.","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Detected fatal BIND or UNBIND protocol error %s","Detected fatal BIND or UNBIND protocol error. This may indicate an interoperability problem. Sense codes are as follows. 20110000 - BIND pacing window overrun, or PI not set when expected 20110001 - unexpected solicited BIND IPM 20110002 - PI set when not expected 20110003 - pacing response not IPM 10020000 - RU (BIND, UNBIND or BIND IPM) length error 10010003 - BIND IPM format error 80070000 - BIND or RSP(BIND) segment out of sequence, or segmented UNBIND or RSP(UNBIND) 80070002 - BIND or RSP(BIND) segments interleaved 800F0000 - LFSID incorrect for SC request 800F0001 - ODAI incorrect Link will be deactivated.","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - EXPD RU received while previous expedited data remains to be processed %s","An EXPD RU has been received while previous expedited data remains to be processed. The session will be deactivated with the specified sense code. (200F0000)","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Error message received reporting invalid format of our MDS_MUs %s","MS Capabilities received an error message reporting a format error on an MDS_MU our node supposedly sent. The error message will be logged, however, no further action can be taken. Ignoring the message may lead to further unexpected occurrences.","Contact support with details of the problem"
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - FQPCID collision on received BIND request %s","FQPCID collision. The FQPCID specified on a received BIND request matches the FQPCID being used for an existing active session. This can be caused by a collision in the hashing algorithm used to generate an FQPCID, or it may indicate a problem in the node generating the FQPCID. Session activation will fail with specified sense code.","If problem is persistent or occurs often, contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Failed to activate a new session, because mode name was not recognized %s","SNA Switch was unable to activate a new session because the mode name specified was not recognized. ALLOCATE, MC_ALLOCATE or CMALLC verbs will fail.","Check the mode name."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Failed to activate a new session, since this would exceed LU or mode session limit %s","SNA Switch was unable to activate a new session because the maximum session limit specified for the mode or the local LU would be exceeded. ALLOCATE, MC_ALLOCATE or CMALLC verbs will either fail or hang waiting for a session to become free.","Wait for a session to become free and retry, or use a different mode."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Failed to create DLC %s","A DLC could not be started either because of insufficient resources, or because the specified DLC type is not supported. The DLC is inoperative.","If the DLC type is supported, then either decrease the system load (for example, by reducing the number of active sessions, or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Failed to dynamically load TP %s","Failed to dynamically load an APPC transaction program or CPI-C application. The received Attach will be failed with the specified sense code.","Collect trace and report the problem to support."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Failed to initialize address space instance %s","Insufficient storage to create a local form session identifier routing table for a link station. Link activation will fail.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Failed to send alert due to insufficient memory %s","Insufficient Memory was available to send an Alert. The Host will not see an Alert. The alert number below identifies the alert 1 - CPDB001 2 - CPDB002 3 - CPDB003 4,6 - CPDB004 5,7 - CPDB005 The alerts are detailed in the Management Services Reference (C30-3346) No other symptoms will be seen.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Fatal error detected in ISR session %s","ISR detected a fatal error in an intermediate session. The ISR session will be deactivated with the specified sense code.","This log should be preceded by a log 536 or 537. Follow the actions given in those logs."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Fatal error detected on LU6.2 session %s","Fatal error detected on LU6.2 session. Session will be deactivated with specified sense code.","This log gives additional information on the failed session, but is preceded by an exception log (150, 151, 153, 154, 155 156 or 157) giving more specific information about the fatal error."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Format error in received LU6.2 BIND request %s","Format error in received LU6.2 BIND request. Sense codes are as follows. 0835xxxx - parameter error at offset xxxx in BIND RU 088C6000 - FQPCID not included in extended BIND 083B0000 - invalid FQPCID format Session activation will fail with specified sense code.","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Format error in received LU6.2 BIND response %s","Format error in received LU6.2 BIND response. Sense codes are as follows. 0835xxxx - parameter error at offset xxxx in BIND RU Session activation will fail with specified sense code.","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Format error in received UNBIND request %s","Format error in received UNBIND request. This may indicate an interoperability problem. Sense codes are as follows. 0835xxxx - parameter error at offset xxxx in UNBIND RU 0895xxyy - format error in control vector, where xx is key of control vector, and yy is offset into control vector of byte in error 10020000 - RU length error None (session will still be deactivated).","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - ISR is unable to support requested RU size %s","ISR is unable to support RU size requested on non-negotiable BIND request or response. Sense codes are as follows. 0835000A - maximum secondary send RU size is larger than that supported by ISR 0835000B - maximum primary send RU size is larger than that supported by ISR ISR session activation will fail with the specified sense code.","Collect trace and report the problem to support."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - ISR is unable to support requested pacing window size %s","ISR is unable to support fixed receive pacing window requested on non-negotiable BIND request or response. Sense codes are as follows. 08350009 - maximum primary send window size is larger than that supported by ISR 0835000D - maximum secondary send window size is larger than that supported by ISR ISR session activation will fail with the specified sense code.","Collect trace and report the problem to support."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - ISR session activation failed - ISR session limit reached %s","Intermediate session activation failed because SNA Switch is not configured to support any more intermediate sessions. This is usually caused by a normal network race condition (since SNA Switch will inform other network nodes that it has reached its limit on intermediate sessions via topology). ISR session activation will fail with the specified sense code (0805000D).","Collect trace and report the problem to support."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - ISR session failure because of link outage or error %s","ISR session failed because of link outage or error. The ISR session will be deactivated with the specified sense code.","This log gives information on which ISR sessions are affected by a link outage or error. Preceding logs give more specific information about the reason for the link outage or error."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Inaccurate directory entry held for this LU %s","A directed locate for this LU has been tried, but the LU was not recognised at the end node stored in the directory. The directory entry is removed and a broadcast locate is sent instead.","None."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Incoming call rejected because port link-activation limits exceeded %s","An incoming call was rejected because the port link-activation limits would be exceeded. The link activation will fail.","If possible, increase the port link-activation limits."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insuffcient storage to dyamically define dependent LU with host %s","Insufficient storage to dynamically define dependent LU with host. LU-SSCP session will not be activated.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insufficient storage for CP-CP sessions %s","Insufficient storage for CP-CP sessions. CP-CP sessions will be deactivated with the specified sense code.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insufficient storage to BIND LU type 0,1,2 or 3 PLU-SLU session (as PLU) %s","Insufficient storage to BIND LU type 0,1,2 or 3 PLU-SLU session. BIND request will not be sent.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insufficient storage to activate ISR session %s","Insufficient storage to activate ISR session ISR session activation will fail with the specified sense code (08120014).","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insufficient storage to activate LU type 0,1,2 or 3 PLU-SLU session (as SLU) %s","Insufficient storage to activate LU type 0,1,2 or 3 PLU-SLU session. BIND request will be rejected with the specified sense code.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insufficient storage to activate LU-SSCP session %s","Insufficient storage to activate LU-SSCP session. ACTLU will be rejected with specified sense code.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insufficient storage to activate LU-SSCP session for LU type 0,1,2 or 3 (as LU) %s","Insufficient storage to activate LU-SSCP session for LU type 0,1,2 or 3. ACTLU request will not be rejected with the specified sense code.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insufficient storage to activate LU-SSCP session for LU type 0,1,2 or 3 (as SSCP) %s","Insufficient storage to activate LU-SSCP session for LU type 0,1,2 or 3. ACTLU request will not be sent.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insufficient storage to activate LU6.2 session %s","Insufficient storage to activate LU6.2 session. Session activation will fail with the specified sense code.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insufficient storage to activate link %s","Insufficient storage to activate link. Link activation will fail.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insufficient storage to define LU type 6.2 %s","Insufficient storage to define a new LU type 6.2.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insufficient storage to enable intra-node sessions %s","Insufficient storage to enable intra-node sessions. Intra-node session cannot be activated.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insufficient storage to generate Alert CPSS003 %s","Insufficient storage to generate Alert CPSS003 (protocol error in received BIND or LOCATE). Alert will not be sent.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insufficient storage to generate an Alert %s","Insufficient storage to generate Alert to report a BIND segmentation or pacing error. The Alert will not be sent.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insufficient storage to generate link Alert %s","Insufficient storage to generate link Alert. Alert will not be sent.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insufficient storage to initiate automatic session activation %s","Insufficient storage to initiate automatic session activation. Fewer active sessions will be available on the specified mode, which may cause application delays or failures.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insufficient storage to initiate session activation requested by ACTIVATE_SESSION %s","Insufficient storage to initiate session activation requested by ACTIVATE_SESSION verb. ACTIVATE_SESSION will fail with NAP_ACTIVATION_FAIL_NO_RETRY","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insufficient storage to initiate session activation requested by [MC_]ALLOCATE or CMALLC %s","Insufficient storage to initiate session activation requested by ALLOCATE, MC_ALLOCATE or CMALLC. [MC_]ALLOCATE will fail with primary_rc of NAP_ALLOCATION_ERROR and secondary_rc of NAP_ALLOCATION_FAILURE_NO_RETRY. CMALLC will fail with return_code of CM_ALLOCATION_FAILURE_NO_RETRY","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insufficient storage to process ACTLU %s","Insufficient storage to process received ACTLU LU-SSCP session will not be started (an ACTLU -ve response with the specified sense code is sent).","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insufficient storage to process Locate received from adjacent node %s","Insufficient storage to process Locate received from adjacent node. CP-CP sessions with the adjacent node will be deactivated (this avoids possible deadlocks).","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insufficient storage to process received BIND request %s","Insufficient storage to process received BIND request. The BIND will be rejected with the specified sense code.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insufficient storage to reassemble received BIND response %s","Insufficient storage to reassemble received BIND response. Session will be deactivated with the specified sense code.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insufficient storage to register ANR label %s","Insufficient storage to register ANR label. HPR traffic using this ANR label will not be routed correctly, which may cause RTP connections to path-switch, or fail altogether.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insufficient storage to register resources owned by a served end node %s","Insufficient storage to register resources owned by a served end node. The specified resource will not be registered (and the registration request rejected). Network searches for the resource may fail if the end node is unable to register it.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insufficient storage to start SNA Switch %s","Insufficient storage to start SNA Switch. SNA Switch was not started.","Make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insufficient storage to start TP instance and conversation requested by received Attach %s","Insufficient storage to start the transaction program instance and conversation requested by a received Attach (FMH5). If other instances of the same transaction program are active, SNA Switch will queue the Attach waiting for one of them to become free. Otherwise, the session will be deactivated (with a sense code of 08640000).","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insufficient storage to start TP instance requested by TP_STARTED %s","Insufficient storage to start the transaction program instance requested by TP_STARTED. If other instances of the same transaction program are active, SNA Switch will queue the TP_STARTED waiting for one of them to become free. Otherwise, the TP_STARTED verb will fail with primary_rc of NAP_UNEXPECTED_SYSTEM_ERROR.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insufficient storage to start a network search %s","Insufficient storage to start a network search. Session activation will fail with the specified sense code.","Make more resource available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insufficient storage to start conversation requested by [MC_]ALLOCATE or CMALLC %s","Insufficient storage to start a new conversation requested by ALLOCATE, MC_ALLOCATE or CMALLC. [MC_]ALLOCATE will fail with primary_rc of NAP_UNEXPECTED_SYSTEM_ERROR, or CMALLC with fail with return_code of CM_PRODUCT_SPECIFIC_ERROR","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insufficient storage to start link inactivity timer %s","Insufficient storage to start link-inactivity timer. Limited resource link will not be automatically deactivated.","If the link is idle (that is, not being used by any sessions), deactivate it using snasw stop link."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insufficient storage to update topology database with connection network %s","Insufficient storage to update topology database with connection network information. Topology will be inconsistent, which may result in unexpected session activation failures (typically with sense codes 8014xxxx, 0806002B, or 08500001).","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch. Cycling the specified port (ie. either activating then deactivating, or deactivating then activating) may clear the condition."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Insufficient storage to update topology database with link station %s","Insufficient storage to update topology database with link station information. Topology will be inconsistent, which may result in unexpected session activation failures (typically with sense codes 8014xxxx, 0806002B, or 08500001).","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch. Cycling the specified link station (ie. either activating then deactivating, or deactivating then activating) may clear the condition."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Intra-node session support ended abnormally %s","Intra-node session support ended abnormally. This should only occur because of a shortage of available storage. Any active intranode sessions will fail, and no more intra-node sessions will be activatable.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Invalid internal state detected %s","A software error has caused a bad internal state to be detected. Potential loss of function - refer to other problem logs for actual effect.","Shut down and restart"
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - LEN LU registration failed because the LU name is already registered as the child of a different CP %s","Node is configured to register LEN LU names when BINDs from LEN nodes are passed through us. In this case registration failed due to a resource name conflict. The LU name is already registered as the child of a different CP. Registration of the resource in question will fail, so sessions to the LEN LU cannot be started except by the LEN itself. Other resources should still be registered correctly.","Check the network node's directory for the duplicate entry. If it is a home entry, then remove the home entry from the directory. If it is a registered entry owned by a different end node, redefine the LU to use a different name."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - LU-LU verification failed. %s","LU-LU verification failed. The partner LU has sent an incorrect response to a challenge sent by a local LU. This is either a mismatch in configuration or a security attack. Session activation will fail.","Check the identity of the partner LU. If this is a mismatch in configuration then reconfigure the password either at the local LU or at the partner LU (or at both LUs), so that both LUs have the same password."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - LU-LU verification failed. %s","LU-LU verification failed. The partner LU has sent an incorrect response to a challenge sent by a local LU. This is either a security attack or a defect in the software at the partner LU location. The session will be deactivated.","Check the identity of the partner LU. If this is a defect in the software at the partner LU location then contact support."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - LU-LU verification protocol error %s","LU-LU verification protocol error. This may indicate an interoperability problem. The session will be deactivated with the specified sense code.","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - LU-LU verification protocol failed. %s","Duplicate random data received. A list is kept of all random data sent as challenges by the local LU. Receiving duplicate random data from a partner LU should be a rare event, and is evidence of a security attack. Session activation will fail.","Check the identity of the partner LU. Check that the random number generators available to the local and partner LUs are good quality (and therefore unlikely to generate matching data). Investigate recurrences of this problem as security attacks."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - LU-LU verification protocol mismatch. %s","LU-LU verification protocol mismatch. The partner LU has requested that the basic protocol is used when the local LU runs only the enhanced protocol with the partner LU. The local LU may be configured to run only the enhanced protocol with the partner LU or it may be configured to run either protocol with the partner LU and has determined that the partner LU can run the enhanced protocol. This is either (i) a mismatch in configuration (ii) a migration problem (iii) a security attack. Session activation will fail.","Check the identity of the partner LU. If the problem is (i) reconfigure the verification protocol that the partner LU uses at the partner LU's location (ii) upgrade the software at the partner LU's location (iii) investigate the security attack."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - LU-mode session limit exceeded %s","LU-mode session limit exceeded. This problem normally should not occur, since the session limits are negotiated with a CNOS exchange prior to sessions being activated. However, this log can also be caused by a normal race condition when the session limits are reset, or when this node has been restarted after having previously had sessions with this partner LU. Session activation will fail with specified sense code.","If problem persists, check the session limits and active session counts on the specified local LU, partner LU."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Link to back-level LEN node not configured %s","An XID3 from an adjacent back-level LEN node (ie. not carrying a network name control vector) was received and there was not a link configured to that back-level LEN node. An implicit link cannot be activated because the adjacent node's CP name is not known. Inbound link activation will fail.","Define a link station (using snasw link) with adj_cp_type set to NAP_BACK_LEVEL_LEN_NODE."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Link to host not configured %s","An unexpected SET_MODE (ie. received before XID exchange had completed) was received from an adjacent host and there was not a link configured to that host. An implicit link cannot be activated because there is not a local PU defined to use the link. Inbound link activation will fail.","Define a link station (using snasw link) with adj_cp_type set to NAP_HOST_XID3 or NAP_HOST_XID0."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Link to host not configured correctly (host is not a DSPU) %s","Link to host not configured correctly (that is, configured as a link to a DSPU). Link activation will fail.","Redefine (or define) link station (using snasw link) with adj_cp_type set to NAP_HOST_XID3 or NAP_HOST_XID0."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Link to host not configured correctly (host is not a Type 2.1 node) %s","Link to host not configured correctly (that is, configured as a link to a Type 2.1 node). Link activation will fail.","Redefine (or define) link station (using snasw link) with adj_cp_type set to NAP_HOST_XID3 or NAP_HOST_XID0."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Link/session failure while registering resources with network node server %s","Link or session failure while registering resources with the network node server. CP-CP sessions to node will be deactivated.","This log flags the fact that a registration request was disrupted by the link or session failure. Other, more specific logs give details on the reasons for the failure, and the appropriate actions."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Locate received from adjacent node exceeded the maximum number of concurrent locates supported by this node %s","Locate received from adjacent node exceeded the maximum number of concurrent locates supported by this node. CP-CP sessions with the adjacent node will be deactivated (this avoids possible deadlocks).","The network will recover from this problem (that is, the CP-CP sessions will be reactivated). If the problem persists, collect trace and report it to support."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Network search not started because it would exceed the maximum number of concurrent locates supported by this node %s","Network search not started because it would exceed the maximum number of concurrent locates supported by this node. Session activation will fail with the specified sense code.","Collect trace and report the problem to support."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - No free TG numbers %s","No free TG numbers between this node and the specified adjacent node. This should only occur if there are already 236 parallel TGs between this node and the adjacent node. Link activation will fail.","Re-configuring the network to reduce the number of parallel TGs between this node and the specified adjacent node."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Parallel TGs not supported to this adjacent node %s","Attempted to activate more than one TG to an adjacent node that does not support parallel TGs. Link activation will fail.","Modify the configuration so that there is only one link station defined to the specified adjacent node. (Alternatively, several links to the adjacent node can be defined, but only one can be active concurrently.)"
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Pre-defined TG number does not match that sent by adjacent node %s","The specified link station is configured with a pre-defined TG number but the adjacent node has sent a different non-zero TG number. Link activation will fail.","Correct mismatched TG number configuration at this node (using snasw link) or at adjacent node."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Protocol error in CP capabilities exchange %s","CP capabilities exchange has failed because of badly formatted CP CAPS GDS variable. Sense codes are as follows. 10101000 - CP capabilities length error 10101002 - Unexpected GDS identifier (not CP capabilities) CP-CP sessions with the specified adjacent node will be deactivated. SNA Switch will not attempt to reactivate CP-CP sessions with this adjacent CP.","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Protocol error in received ISR BIND request %s","Protocol error in received ISR BIND request. This may indicate an interoperability problem. Sense codes are as follows. 08350008 - secondary-to-primary staging indicator incorrect 0835000C - primary-to-secondary staging indicator incorrect 10010024 - unextended non-LU6.2 BIND 10020000 - BIND RU length error ISR session activation will fail with the specified sense code.","Report the problem to support (running a trace on the specified link if more diagnostics are required)."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Protocol error in received ISR BIND request %s","Protocol error in received ISR BIND response. This may indicate an interoperability problem. Sense codes are as follows. 08350007 - control vectors included indicator incorrect 08350008 - secondary-to-primary staging indicator incorrect 0835000C - primary-to-secondary staging indicator incorrect 086F0000 - BIND response length inconsistent 10010024 - unextended non-LU6.2 BIND response 10020000 - BIND RU length error ISR session activation will fail with the specified sense code.","Report the problem to support (running a trace on the specified link if more diagnostics are required)."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Protocol error while registering resources with network node server %s","Protocol error while registering resources with the network node server. CP-CP sessions to node will be deactivated.","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - REQACTPU rejected %s","DLUS rejects REQACTPU with given sense code. An SSCP-PU session with the given DLUS will not be activated. If a backup DLUS is configured for the PU, DLUR will attempt to activate the PU via the backup DLUS.","Examine sense code and retry activation if appropriate."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Received BIND IPM on link where adaptive BIND pacing not supported %s","Received BIND IPM on link where adaptive BIND pacing is not supported. This may indicate an interoperability problem. BIND IPM will be discarded.","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Received BIND request directed at this node with unrecognized secondary LU name %s","Received BIND request directed at this node (that is, either without an RSCV, or at the last hop on the RSCV) with an unrecognised secondary LU name. This usually indicates a configuration error at the primary LU. Session activation will fail with the specified sense code.","Correct primary LU configuration."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Received BIND request where network ID of secondary LU does not match local network ID %s","Received BIND request where network identifier of secondary LU does not match local network identifier. Session activation will fail with the specified sense code.","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Received BIND request with badly formed secondary LU name %s","Received BIND request with badly formed secondary LU name. This may indicate an interoperability problem. Session activation will fail with the specified sense code.","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Received BIND using LFSID that is already in use %s","Received BIND using LFSID that is already in use. This is usually caused by a race condition (a BIND, UNBIND, BIND sequence all using the same LFSID, where the second BIND overtakes the UNBIND). Nodes at the current level of APPN contain 'LFSID ageing' processing to minimise the changes of this race condition, but some older implementations may not support this processing. BIND will be rejected with specified sense code.","If problem is persistent, or occurs frequently, contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Received ISR BIND request with duplicate FQPCID %s","Received ISR BIND request with duplicate FQPCID. ISR session activation will fail with the specified sense code. (083B0002)","Report the problem to support (running a trace on the specified link if more diagnostics are required)."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Received PLU-SLU BIND request with duplicate FQPCID %s","Received PLU-SLU BIND request with duplicate FQPCID. Session activation will fail with the specified sense code. (083B0002)","Report the problem to support (running a trace on the specified link if more diagnostics are required)."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Received Register/Delete GDS variable containing format errors %s","Received a Register or Delete GDS variable from a served end node which contained format errors. Sense codes are as follows. 08950000 - GDS variable or control vector length error. 10140080 - invalid control vector Register or delete attempt is rejected. The resources specified will not be registered","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Received badly formed Locate from an adjacent node %s","Received badly formed Locate from an adjacent node. This may indicate an interoperability problem. Sense codes are as follows. 1010B080 - missing command parameters control vector in Found GDS variable 10140080 - GDS variable or control vector length error 1014A082 - missing search argument directory entry in Find GDS variable CP-CP sessions with adjacent node will be deactivated with the specified sense code.","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Received registration or deletion request from an unknown end node %s","Received a registration or deletion request from an unknown end node. This may indicate an interoperability problem, but is not considered fatal. The registration request is discarded.","None."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Registration failure notification received from network node server is badly formed %s","Registration failure GDS variable received from the network node server is badly formed. This may indicate an interoperability problem. CP-CP sessions to node will be deactivated.","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Remote node supplied a corrupted RSCV: the next hop is the local CP %s","An HPR Route Setup RU has been received with an RSCV that gives the local node as the next ANR hop. This is invalid. Therefore the remote node is sending invalid protocol data.","Report error to remote end."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Resource registration failed because network node server detected a protocol error in the Register request %s","A resource registration failed because the network node server detected a protocol error in the Register request. This may indicate an interoperability problem. Registration of the resource in question will fail, other resources should still be registered correctly.","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Resource registration failed because the resource conflicted with an existing entry in the network node's directory %s","A resource registration failed because the resource conflicted with existing resources in the network node server's directory. This most commonly occurs when two LUs with the same name are defined on two different end nodes being served by the same network node. It may also occur if the network node has a home directory entry defined for the same resource. Registration of the resource in question will fail, other resources should still be registered correctly.","Check the network node's directory for the duplicate entry. If it is a home entry, then remove the home entry from the directory. If it is a registered entry owned by a different end node, redefine the LU to use a different name."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Resource registration failed with an unknown sense code %s","A resource registration failed with an unknown sense code. This may indicate an interoperability problem. No further resource registration will occur until CP-CP sessions are deactivated and reestablished.","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Resource registration failure: resource already registered %s","Failed to register resource for a served end node because the resource is already registered but with a different parent resource. This typically occurs when the same LU is defined on two or more end nodes. The registration request is rejected, which may result in other resources not being registered, and subsequent network search failures.","Remove or rename the LU on one of the end nodes."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - SNA Switch DEBUG log %s","SNA Switch Debug log.","Report to SNA Switch technical support."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - SNA Switch could not allocate necessary storage %s","SNA Switch could not allocate necessary storage. Some operation will fail. See other logs/verbs.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Served end node attempted to delete a home directory entry %s","A served end node attempted to delete a directory entry that is defined as a home entry at this node. This normally occurs when snasw location has been used to define LUs owned by served end or LEN nodes. The Delete request is rejected with the specified sense code.","Use no snasw location to remove the home entry from the directory."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Served end node attempted to delete a resource it doesn't own %s","Served end node attempted to delete a resource, when it was not registered as the owner of the resource. This may indicate an interoperability problem. The Delete request is rejected with the specified sense code. This may cause the end node to deactivate CP-CP sessions.","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Session control request received with invalid LFSID %s","Session control request received with invalid local form session identifier (that is, the LFSID is not in a range appropriate for the request). This may indicate an interoperability problem. Request will be rejected with the specified sense code.","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Session identifier collision on received BIND request %s","Session identifier collision. The session identifier specified on a received BIND request matches the session identifier being an existing active session. Session activation will fail with specified sense code.","If problem is persistent or occurs often, contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - The CP name on an XID3 received from adjacent node is different to that expected %s","The CP name on an XID3 received from an adjacent node is different to that expected. The link activation will fail.","If the received adjacent CP name is correct, correct the link station configuration using snasw link. Depending on other aspects of the link station definition, the CP name check can be disabled by issuing snasw link with the adj_cp_name field set to all zeros."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - The IPDLC UDP stub process has abended - SNAP IPDLC will abend %s","The UDP stub process has abended. IPDLC will abend itself. All links using SNAP-IPDLC will fail. SNAP-IPDLC will fail.","Check for the UDP/IP problem that caused the UDP stub to abend. If the reason cannot be determined, gather full trace and contact support."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - The node ID on an XID3 received from a back-level node is different to that expected %s","The node ID on an XID3 received from a back level node is different to that expected. The link activation will fail.","If the received node ID is correct, correct the link station configuration using snasw link. Depending on other aspects of the link station definition, the node ID check can be disabled by issuing snasw link with the adj_node_id field set to all zeros."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - The node type indicated on an XID3 received from an adjacent node is different to that expected %s","The node type indicated on an XID3 received from an adjacent node is different to that expected. The link activation will fail.","If the received node type is correct, correct the link station configuration using snasw link. Depending on other aspects of the link station definition, the node type check can be disabled by issuing snasw link with the adj_node_type field set to NAP_LEARN_NODE."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Unable to activate RTP connection %s","Unable to activate RTP Connection In certain situations, the origin may retry activation.","Examine sense code and retry activation if appropriate."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Unable to activate session to single session partner LU, because there is an active session on another mode %s","Unable to activate session to single session partner LU, because there is already an active session on another mode. This usually indicates contention between two or more APPC transaction programs or CPI-C applications for the same dependent LU6.2. Session activation will fail with specified sense code (which may cause ALLOCATE, MC_ALLOCATE or CMALLC requests to fail).","Collect trace and report the problem to support."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Unable to assign LFSID to secondary stage of ISR session %s","Unable to assign a local-form session identifier (LFSID) to the secondary stage of an ISR session. This problem is probably caused by insufficient storage to extend the appropriate LFSID routing table, although it could also indicate that the table is full (each link can route a maximum of 64770 ISR sessions). ISR session activation will fail with the specified sense code.","This log gives information on which ISR session is affected by a failure in the LFSID table management. Preceding logs give more detail on the reason for the failure."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Unable to correlate received Register or Delete reply to a directory entry %s","Directory Error Correlator returned on a Register or Delete reply cannot be correlated to a directory entry. This is considered a protocol error and may indicate an interoperability problem. CP-CP sessions to node will be deactivated.","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Unable to deactivate port %s","Unable to deactivate port. snasw stop port will fail, port may not restart successfully.","If required, attempt to restart the port. If this fails, look for DLC specific logs giving more information on the reason for the failure."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Unable to delete resources because this node is not authorised at the network node server %s","The network node server has rejected a Delete request with a sense code indicating this node is not authorised to register resources at the network node. This usually indicates a mismatch between the network node server's configuration (to consider this end node unauthorised) and this node's configuration (to register resources). No further resource registration or deletion will occur until CP-CP sessions are deactivated and reestablished.","Modify the network node server configuration to consider this node authorised."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Unable to forward an HPR NLP - insufficient storage %s","Insufficient storage to forward HPR Network Layer Packet. NLP will be discarded. If this error occurs frequently, it may cause RTP connections to path-switch or fail altogether.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Unable to identify or activate the next hop of an ISR session %s","Unable to identify or activate the next hop of an ISR session. ISR session activation will fail with the specified sense code.","This log is preceded by other logs giving more specific reasons for the failure. Follow the actions given in those logs."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Unable to register resources because the network node server's directory is full %s","A resource registration failed because the network node server's directory is full. This may indicate a shortage of storage at the network node, or a configured upper bound on the size of it's directory. No further resource registration will occur until CP-CP sessions are deactivated and reestablished.","Increase the size of the directory at the network server. This may be a simple configuration change, or it may require freeing up storage by reducing the load at the server."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Unable to register resources because this node is not authorised at the network node server %s","The network node server has rejected a Register request with a sense code indicating this node is not authorised to register resources at the network node. This usually indicates a mismatch between the network node server's configuration (to consider this end node unauthorised) and this node's configuration (to register resources). No further resource registration will occur until CP-CP sessions are deactivated and reestablished.","Modify the network node server configuration to consider this node authorised."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Unrecognized mode name in received BIND request %s","Mode name on received BIND request is unrecognized. Session activation will fail with the specified sense code.","Modify the partner LU configuration so it does not attempt to use the unrecognized mode."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - Unrecoverable DLC failure %s","Unrecoverable DLC failure. The DLC will be destroyed, and all ports and link stations defined on the DLC will be inoperative.","Restart the DLC and ports (using snasw start port). If these operations fail, or this problem is persistent, run a trace on the DLC and contact support with the log and trace information."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - XID exchange count exceeds activation limit %s","The number of XIDs received during link activation exceeded the limit defined for the port. This could indicate an XID protocol error, or an excessively unreliable physical media. The sense data gives more information about the error. 083E0001 - the limit was exceeded while exchanging prenegotiation or negotiation XIDs 0809003A - the limit was exceeded while exchanging NULL XIDs. Link activation will fail.","Retry the activation. If SNA Switch is still unable to activate the link station, run a trace on the link station or port to diagnose the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - XID exchange count exceeds nonactivation limit %s","The number of XIDs received during non-activation exchange exceeded the limit defined for the port. This could indicate an XID protocol error, or an excessively unreliable physical media. Non-activation XID exchange will fail and the link will be deactivated.","Run a trace on the link station or port to diagnose the problem, and contact support with trace information."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - XID protocol error during activation exchange %s","XID protocol error during activation exchange. This may indicate an interoperability problem between this node and the adjacent node, or it may be cause by the adjacent node resetting and restarting the exchange without sending a DISC or DM frame. The sense codes are as follows. 0806002C - the adjacent node has changed its network name during the course of an XID exchange 0809003A - received a null XID when an XID format 3 was expected 0809003C - prenegotiation XID received when not expected (had already received a negotiation proceeding XID3) 0809003D - nonactivation XID received when a null XID or activation XID was expected 08090040 - received an unexpected or invalid mode-setting command (eg. SNRM or SABME) 08090045 - the adjacent node has stopped supporting exchange state indicators in the middle of an XID exchange 08090046 - the adjacent node had previously indicated it did not support exchange state indicators, but has sent a XID with exchange state indicators set 08090047 - received XID after receiving mode-setting command (eg. SNRM or SABME) 08090048 - received unsolicited XID from NRM secondary link station 08090049 - the adjacent node sent an XID error control vector (x'22') 08090055 - invalid VRN in TG descriptor CV of XID3 086F0000 - XID3 control vector length error 088C1000 - the adjacent node is a network node, but did not include a product set identifier control vector in the XID3 088C0EF1 - the adjacent node is type 4 or 5, but did not include a PU name control vector 088C0EF4 - the adjacent node has no been inconsistent in including a network name control vector 088C4680 - an XID was received on an ATM port, but did not include a TG identifier TG descriptor subfield 08910004 - the network name control vector does not contain a valid network identifier 08910005 - the network name control vector does not contain a valid CP name 0895xxyy - XID3 control vector error (xx indicates key of first control vector in error, yy indicates offset of error within control vector) 08960000 - control vector too long 08960001 - network name control vector is too long 10150001 - received XID3 is too short (less than 29 bytes) 10150002 - length of received XID3 does not match length indicated in XID3 10160000 - the adjacent node indicated an invalid BIND pacing setting 10160001 - the maximum number of I-frames that the adjacent node can receive before sending an acknowledgement is set to zero 10160003 - the maximum BTU size the adjacent node can receive is set to less than 99 bytes 10160004 - unexpected XID format 10160005 - the adjacent end node supports receipt of BIND segments, but does not support BIND segment generation 10160006 - the adjacent end node does not support receipt of BIND segments and has a maximum BTU size less than 265 bytes 10160007 - the adjacent network node does not support receipt of BIND segments and has a maximum BTU size less than 521 bytes 10160008 - adjacent node has been inconsistent in its setting of networking capabilities 10160009 - the adjacent network node supports CP-CP sessions but does not provide CP services 1016000B - the adjacent node has selected zero as the TG number (which is invalid) 1016000C - the adjacent network node does not support BIND segment generation and has a maximum BTU size less than 521 bytes 1016000D - the adjacent node does not support the SDLC","Contact support with details of the problem."
"SNASW","3","UNAVAILABLE","PROBLEM - %lu - XID protocol error during non-activation exchange %s","XID protocol error during non-activation exchange. This may indicate an interoperability problem between this node and the adjacent node. The sense codes are as follows. 0809003A - received a null XID when an activation XID format 3 was expected 0809003B - received a null XID when a nonactivation XID format 3 was expected 0809003E - activation XID received when non-activation XID expected 0809003F - adjacent node initiated a secondary-initiated non-activation XID exchange on a link that does not support secondary-initiated non-activation XID exchanges 08090042 - nonactivation exchange initiation indicator not set when expected 0809004E - received a non-null XID from a secondary NRM link station, when a null XID was expected 10160002 - adjacent node has been inconsistent in its setting of ACTPU suppression indicator 10160008 - adjacent node has been inconsistent in its setting of networking capabilities 1016000B - adjacent node attempted to change TG number during nonactivation exchange to a TG number that was already in use 10160019 - adjacent node has attempted to change its CP name when CP-CP sessions supported on link station, or link station not quiesced The link will be deactivated.","Run a trace on the link station or port to obtain more diagnostic information on the problem. Contact support with details of the log and trace."
"SNASW","3","UNAVAILABLE","Port %s activation failed: %s","An error was received from CLS. Typically, indicates a configuration error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SNASW","3","UNAVAILABLE","Query %s failed. NOF primary rc=%x secondary rc=%x.","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SNASW","3","UNAVAILABLE","Resizing of %s buffer failed due to insufficient memory; using buffer-size of %d KB.","A cyclic trace buffer could not be resized due to insufficient memory. The previously allocated buffer, if any, will continue to be used.","Reconfigure a smaller buffer-size for the specified buffer type."
"SNASW","3","UNAVAILABLE","SNASW failed to process CLSI message, header= %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SNASW","3","UNAVAILABLE","SNASW failed to process DLC message, header= %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SNASW","3","UNAVAILABLE","Trap failed. %s MIB OID=%s index OID=%s.","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - A DLUS has sent an ACTPU with a PU name different from the name in the last ACTPU received for the same DSPU. %s","A DLUS has sent an ACTPU with a PU name that is different to the PU name in the last ACTPU received for the same DSPU. The PU name of this implicit or DLUS-defined DSPU will change its name to the name from this new ACTPU.","Reconfigure the DLUS(es) in the network to use the same PU name when referring to the same PU."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - A DLUS has sent an ACTPU with a PU name that is already in use %s","A DLUS has sent an ACTPU with a PU name that is already in use. The ACTPU will be rejected with the specified sense code. PU activation will not continue.","Reconfigure the DLUS or the DLUR to use different PU names. If the DLUS and the DLUR use the same PU name, then they must apply the name to the same PU."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - A DLUS has sent an ACTPU without a PU name %s","A DLUS has sent an ACTPU without a PU name. The ACTPU will be rejected with the specified sense code. PU activation will not continue.","Check the status of the named DLUS. Check that it is correctly configured. Optionally, reconfigure SNA Switch to use a different DLUS."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - A DLUS-defined downstream DLUR-served link could not be defined %s","A DLUS-defined downstream DLUR-served link could not be defined because either: - the specified port does not exist - there is an existing link station to the same destination address. The PU will not be activated.","Correct the configuration."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - A DLUS-defined downstream DLUR-served link failed to activate %s","A DLUS-defined downstream link failed to activate. The PU will not be activated.","Check that the named port is active. Check that the downstream node at the given address is powered on. Check surrounding logs for reasons that the named LS has not activated. Check the configuration of the DLUS."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - A REQACTPU RSP has not been received. Possible hung PU problem %s","A REQACTPU RSP has not been received for this PU and it appears the PU is hung. There will be no further action taken","If this is an internal PU then contact support with details of this log. If this is a downstream PU then contact the supplier of the downstream node."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - A Route Setup Reply has been received with the backout sense code HPR will not be used for this session %s","The local node has received an HPR Route Setup Reply with the backout sense code. The Route Setup has failed because the destination node does not support RTP. No intermediate node supports RTP and was able to become the new destination. The Route Setup has failed and HPR will not be used for the session that is being activated. This is a normal event when a node in the route has an auto-activateable link to a node that does not support RTP or HPR.","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - A Route Setup has been backed out from the orignal destination to the new destination %s","The local node has received an HPR Route Setup Reply in which the destination node is not the same as the destination node that was in the corresponding Route Setup Request. The Route Setup has successfully backed out. The Route Setup is between the origin node and the new destination. RTP Connections will be activated between these two nodes. This is a normal event when a node in the route has an auto-activateable link to a node that does not support RTP or HPR. Sessions that originate at (or beyond) the local node will use HPR from the local node to the new destination and use ISR from new destination and beyond it.","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - A conventional half-session has aborted. %s","Critical buffer shortage or protocol error or CRV exchange protocol error. This indicates a possible interoperability problem. Sense codes for CRV exchange errors are as follows. 20090000 - CRV request received from secondary LU, or CRV response received from primary LU, or CRV not received when expected 10020000 - CRV RU too short 400F0000 - CRV with FI not set 400B0000 - CRV chain indicators not set to BC, EC 40140000 - CRV not RQD1 40110000 - CRV not expedited 40150000 - CRV with QRI not set 40080000 - CRV with PI set 400C0000 - CRV request with BBI, EBI or CEBI set 400D0000 - CRV request with CDI set 40100000 - CRV request with CSI set to CODE1 40160000 - CRV request with EDI set 40170000 - CRV request with PDI set 40130000 - CRV response RTI and SDI inconsistent Session will be deactivated with specified sense code.","If surrounding logs indicate critical congestion, decrease the system load or make more resources available to SNA Switch. Otherwise, contact support with details of the problem."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - A request to activate a connection network TG was rejected because a defined link was already active between the local and destination address and multiple links are not supported %s","SNA Switch cannot start a link to an adjacent node over a connection network TG because the DLC does not support mutiple links between the local and destination addresses. The session will fail, with the specified sense code.","Check the local and destination link addresses."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - A request to activate a connection network TG was rejected because the local and destination link addresses were incompatible %s","SNA Switch cannot start a link to an adjacent node over a connection network TG because the link address on the local node is not compatible with the link address on the adjacent node. The session will fail, with the specified sense code.","Check the local and destination link addresses."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - APPC Transaction Program or CPI-C application has ended abnormally with active conversations %s","An APPC transaction program or CPI-C application has ended abnormally with active conversations. This usually indicates an error in the application. SNA Switch will deactivate all sessions currently being used by the application.","Run a trace on the APPC API or the CPI-C API to see the sequence of verbs causing the problem."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Abnormal UNBIND request received %s","Abnormal UNBIND request received. This may indicate a configuration error, or a protocol error. The session will fail with the specified sense code.","If the sense code indicates a configuration error, check for inconsistencies between the configuration at the local LU and the configuration at the partner LU. If the configuration is consistent and the problem persists, contact support with details of the problem."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Adjacent node registered an Associated Resource which was not an ENCP %s","The local node is a Branch Network Node or Network Node and a downstream node registered an Associated Resource that was not an ENCP resource.","None, the node will force the resource type to be ENCP."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Alert/Resolution received and cannot be sent %s","Memory failure in trying to allocate space to route a back- level alert or resolution to the parent MS process. The alert or resolution will not be sent. It is logged here.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - An LU received an aping with data size greater than the maximum allowed %s","An LU received an aping with data length greater than the maximum allowed. The conversation will be terminated with primary_rc of DEALLOC_ABEND.","Report the error. SNA Switch LUs should not be apinged with a data size greater than the defined maximum."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - An LU-SSCP session activation attempt failed because the SSCP was not suitable %s","An ACTLU was received for an LU from the wrong SSCP. The ACTLU is rejected with sense code 084B0000 (i.e. the LU activation attempt fails).","If it is required that the LU accepts the ACTLU (i.e. that the activation attempt succeeds) then the LU definition must be changed so that either i) the LU requires the particular SSCP Identifier that is actually received from the SSCP ii) the LU accepts any SSCP Identifier."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - An attempt to activate a persistent pipe to a DLUS has failed %s","DLUR has requested a persistent pipe to a DLUS but the DLUS does not support persistent pipes. The sense codes are as follows. 088E0009 - the DLUR has failed the pipe activation because it requires all pipes to be persistent. 08A0000C - the DLUS has failed the pipe activation because there is no PU needing service. The attempt to activate a persistent pipe to the DLUS will fail.","If the DLUR is unable to contact a different DLUS that does support persistent pipes then the following should be considered. If the sense code is 088E0009 then DLUR requirement for persistent pipes could be removed. Otherwise, the DLUS must be upgraded to support persistent pipes."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Application sent invalid Acknowledgment or Status message %s","LU type 0,1,2 or 3 application sent invalid Acknowledgment or Status message. Status Error sent to application.","Investigate the error in the application."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Application sent invalid Data message %s","LU type 0,1,2 or 3 application sent invalid Data message. Status Acknowledge (NACK-2) sent to application.","Investigate the error in the application."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Application sent invalid Status Control message %s","LU type 0,1,2 or 3 application sent invalid Status Control message. Status Control (NACK-2) sent to application.","Investigate the error in the application."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Automatic retry of CP-CP sessions on a timer has failed %s","The node failed to start a timer in order to retry CP-CP sessions to a Network Node Server. The node will not automatically attempt to activate CP-CP sessions and so may be left with no CP-CP sessions at all or CP-CP sessions with a node that is not the best available. CP-CP sessions will however be retried in the normal way when a local application needs them or a new link activates.","None if CP-CP sessions are not required or if the administrator is happy with the existing Network Node Server. If the administrator wants to start CP-CP sessions they can be started manually."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - BIND race with single-session partner LU - partner LU has lost race %s","BIND race with single-session partner LU. This is a normal network race condition. The race is resolved in favour of the LU with the higher name. In this case the partner LU lost the race. Session activation will fail with specified sense code.","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Buffer congestion relieved %s","Buffer congestion relieved. SNA Switch will stop throttling back session traffic. If the congestion eases further SNA Switch will start to increase pacing windows on adaptively paced sessions.","None"
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - CP-CP sessions deactivated while broadcast Locate outstanding %s","CP-CP sessions deactivated while broadcast Locate in process. Session activation may fail.","This log simply flags the fact that a session failure impacted a pending broadcast Locate. Other, more specific, logs give reasons for the session failure and appropriate actions."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - CP-CP sessions established between network nodes in different networks %s","CP-CP sessions established between two network nodes in different networks. CP-CP sessions will be deactivated with the specified sense code.","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - CP-CP sessions established with end node: invalid directory entry removed %s","CP-CP sessions have been established with an adjacent end node which was previously defined using snasw location. The invalid directory definitions for the end node and any of its LUs will be removed.","Do not configure the invalid entries in future."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - CPSVRMGR pipe session failure %s","CPSVRMGR pipe failed to specified DLUS. Any PUs using the specified DLUS are deactivated (that is, DACTPU(cold) is sent. DLUR may attempt to contact one or more backup DLUS's, if configured.","If a pipe with backup DLUS is not initiated automatically manually restart any required PUs"
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - CRV exchange failed %s","CRV exchange failed. This indicates the cryptography keys configured at this LU and the partner LU are inconsistent. Session will be deactivated with the specified sense code (08350001).","Use information on the session deactivated problem log (log 271) to identify the local LU and partner LU, and correct the mismatch in cryptography keys."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - CRV exchange failed on a PLU-SLU session. The session will fail %s","CRV exchange failed. This indicates the cryptography keys configured at this LU and the partner LU are inconsistent. Session will be deactivated with the specified sense code (08350001).","Use information on the session deactivated problem log (log 271) to identify the local LU and partner LU, and correct the mismatch in cryptography keys."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - CRV exchange failed on a PLU-SLU session. The session will fail. %s","CRV exchange failed. This indicates the cryptography keys configured at this LU and the partner LU are inconsistent. Session will be deactivated with the specified sense code (08350001).","Correct the mismatch in cryptography keys."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Central Resource Registration failure %s","Central Resource Registration failure. Network performance may degrade because of additional broadcast Locate searches.","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Central Resource Registration failure: invalid correlator received %s","Central Resource Registration failure and invalid correlator received. Network performance may degrade because of additional broadcast Locate searches.","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Connection Setup NLP received for previous NCE instance %s","A connection setup NLP has been received, specifying a previous instance of this NCE. The NCE must have been shut down and restarted since processing the Route Setup request No RTP connection can be started, so the NLP will be discarded.","Report error to remote end."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Connection Setup NLP rejected because it specified unsupported Topic ID %s","A Connection Setup NLP was rejected because it specified the CP-CP session or Route Setup Topic ID, but was received on a TG which does not support the Control Flows over RTP Tower. The CP-CP session or Route Setup RTP Connection will fail with sense code HA0010017.","Contact support with details of the problem."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Correlator clash detected in MDS_MU processing %s","A correlation error was detected while processing an MDS_MU. The MDS_MU will not be processed. If the MDS_MU originated at the local node the SEND_MDS_MU verb containing the MDS_MU will be returned to the sending application noting the error. If the MDS_MU did not originate from the local node, an error message will be returned to the originating application. An error message may also be sent to other applications if they are affected by the correlation clash.","User should reissue the SEND_MDS_MU but with a correct correlator value."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Critical buffer congestion %s","The Buffer Manager Monitor detected critical buffer congestion SNA Switch will throttle back session traffic by withholding pacing responses or resetting pacing windows on adaptive-paced sessions until the congestion has reduced.","This condition can occur if the node receives a large, sudden burst of data traffic on several sessions. The condition should clear itself automatically, but if it occurs frequently, it may indicate the node is routing more sessions than it can handle efficiently with the available buffer storage. Reduce the number of sessions through the router."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Critical buffer congestion detected while attempting to relieve congestion %s","The Buffer Manager detected critical buffer congestion while attempting to relieve a previous congestion condition. SNA Switch will throttle back session traffic by withholding pacing responses or resetting pacing windows on adaptive-paced sessions until the congestion has reduced.","This condition can occur if the node receives a large, sudden burst of data traffic on several sessions. The condition should clear itself automatically, but if it occurs frequently, it may indicate the node is routing more sessions than it can handle efficiently with the available buffer storage. Reduce the number of sessions through the router."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - DLUS-defined DSPU name clashes with locally-defined DSPU name %s","A DLUS-defined DSPU name clashes with the locally-defined DSPU name of a different PU. An implicit link will fail. The ACTPU for the DSPU connected over this link will be rejected.","Reconfigure this node, or the DLUS, to remove the clash in the use of this PU name. If the DLUS and the DLUR use the same PU name, then they must apply this name to the same PU."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Deactivating intermediate session because of insufficient storage %s","Deactivating intermediate session because of insufficient storage. The intermediate session will be deactivated.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Delete request failed because the resource was not found or not removable %s","A Delete request failed, either because the entry was defined as a home entry at the network node server, or because the resource was not found. Neither error is severe, and will not affect future registration and deletion, or other aspects of network operation. Delete attempt has failed, further deletion and registration will continue unaffected.","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Dependent LU session deactivated because LU deleted %s","A dependent LU-LU session has been deactivated because the LU has been deleted. None.","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Different PUs have LUs whose names clash %s","Two LUs of the same name exist under different PUs. One is already activated and DLUS has attempted to activate the other. The second LU will not be activated.","Rename one of the LUs with a unique network name."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Duplicate FQPCID prevents start of network search %s","A LOCATE message received with duplicate PCID. This could occur if two LEN nodes send BINDs to SNA Switch at the same time and with the same PCID. Session activation will fail with the specified sense code.","None. The downstream box should retry the session activation using a different PCID."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Entry could not be added to signed-on-to list sending PV sign-on Attach. %s","The local LU failed to add an entry into the signed-on-to list when sending a PV sign-on Attach (FMH-5) due to resource shortage. The Attach wil be sent, but will not contain the sign-on request.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Error data received from partner LU. %s","The partner TP issued a SEND_ERROR or DEALLOCATE verb specifying error data. an error state was generated by the partner TP. The specified TP will experience a problem. Subsequent recovery or termination of the conversation will be determined by the applications.","Check that both the local TP and the partner TP exist, are correctly named, and are working properly."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Error data sent to partner LU. %s","The local TP issued a SEND_ERROR or DEALLOCATE verb specifying error data. The specified TP will experience a problem. Subsequent recovery or termination of the conversation will be determined by the applications.","Check that both the local TP and the partner TP exist, are correctly named, and are working properly."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Error message received at MS Capabilities (delivery failure) %s","MS Capabilities received an error message. This is assumed to be the result of a send failure. The error message received will be logged so that send failure types can be examined. MS capabilities will take appropriate recovery action if the failed send effects the focal point table.","Contact support with details of the problem."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Error on alert send not correlated with entries on send alert queue %s","The system was unable to correlate an error received on an alert send with the alerts stored in the send alert queue. The send alert queue is either too small and the original alert has been deleted or a previous error prevented the alert from being held on the queue. The alert will not be sent to the focal point.","Investigate whether prior memory shortage caused alert not to be held on the queue."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Failed to adjust a buffer pool %s","The desired number of buffers could not be reserved for a buffer pool. The receive pacing window size for the session will not increase as fast as configured.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Failed to contact a DLUS for PU. Retry count exceeded. %s","The DLUR has failed to contact either the DLUS or the backup/ default DLUSs after the configured number of retries. Contact is not made with the DLUS.","Check earlier logs for causes of individual failures to contact Host. Resolve any problems or increase the timeout or retry count and try again."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Failed to contact one or both of the default DLUS when attempting to activate a persistent pipe required by a DLUS-dependent port. The retry count is exceeded. %s","The DLUR has failed to contact either the default primary DLUS or the default backup DLUS or both after the configured number of retries when attempting to activate a persistent pipe required to enable a DLUS-dependent port. The DLUS-dependent port is not enbaled.","Check earlier logs for causes of individual failures to contact Host. Resolve any problems or increase the timeout or retry count and try again."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Failed to register resource with NNS/CDS %s","Failed to allocate memory for storage of resource in the register list. Registration will not take place immediately.","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Following alert failed to be sent to focal point %s","The system received a send failure for an alert stored on the send alert queue. No held alert function is available to store the alert until another focal point is established. alert to the alert handler. The alert will not be sent, however, it will be logged.","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Following locally originated MSCAPS message failed to be sent %s","The system received a send failure for a local MS capabilities originated message. MS capabilities will treat the send failure as a loss of connectivity to the partner node. If focal point relationships are affected then MS capabilities will take appropriate recovery action.","Investigate cause of failed send."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - HPR Route Setup RU received with existing FQPCID %s","An HPR Route Setup RU has been received with an FQPCID that matches an existing route. The message will be rejected and the route not established.","Report error to remote end."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - HPR Route Setup RU received with format errors %s","An HPR Route Setup RU has been received with format errors The message cannot be processed, and will be discarded.","Report error to remote end."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - HPR manager failed to obtain memory to send indication %s","HPR manager failed to get memory to send an RTP indication. The data_lost flag will be set in the next indication successfully sent.","Investigate memory shortage."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - IPDLC failed to allocate necessary storage %s","IPDLC could not allocate necessary storage. Some operation may fail. See other logs.","Either decrease the system load (for example, by reducing the number of active links), or make more storage available to IPDLC."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - IPDLC failed to create a UDP stub %s","IPDLC failed to create a UDP stub. Port activation will fail.","Either decrease the system load (for example, by reducing the number of active links), or make more storage available to IPDLC."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - IPDLC failed to grow a link hash table %s","IPDLC failed to grow a link hash table. Data transmission rates may be marginally degraded.","If there are few instances of this log, IPDLC has recovered, and no action is required. If this log occurs repeatedly, then either decrease the system load (for example, by reducing the number of active links), or make more storage available to SNAP-IPDLC."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - IPDLC failed to request a posting %s","IPDLC failed to request a posting. Link activation may fail or data transmission may be delayed.","Either decrease the system load (for example, by reducing the number of active links), or make more storage available to IPDLC."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - IPDLC's UDP stub has failed to initialise %s","IPDLC has created a UDP stub, but the UDP stub failed to initialise successfully. Port activation will fail.","Check surrounding logs and other diagnostics for reports of a failure from a UDP stub process."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Implicit alias space wrapped %s","The space for implicit aliases has wrapped. There is a very slight possibility of duplicate aliases.","Shut down and restart to avoid any conflict."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Inconsistent DLUS Names %s","Inconsistent DLUS Names. The Host has requested the activation of a Downstream link to a PU by sending an ACTPU. The link is configured to request a different DLUS. The DLUS initiating the activation is used.","None required. If the Host DLUS is the regular DLUS (i.e., not a backup) then adjust the downstream link configuration when convenient."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Independent LU session deactivated because LU deleted %s","An independent LU-LU session has been deactivated because the local LU has been deleted. None.","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Insufficient buffers to create new buffer pool %s","Insufficient buffers to create a new buffer pool Activation of some resource (eg. session, LS) will fail. See other logs.","Investigate buffer shortage and system load."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Insufficient information to create a DLUS-defined link to a DLUR DSPU %s","Insufficient information to create a DLUS-defined link. A PU will not be activated. The ACTPU for the named PU will be rejected with the given sense code.","Correct the PU definition at the DLUS. The DLUS-defined link could not be created using the information from the DLUS in the TG descriptor (CV x'46') shown below. For example, for a Token-Ring link to be created, SNA Switch requires the x'46' to contain the following subfields. - x'91' Signaling information CV specifying EBCDIC 'TR'. - x'92' Port identifier containing an 8-byte EBCDIC port name. - x'93' LSAP info containing a 1-byte destination SAP address. - x'94' MAC info containing a 6-byte destination MAC address."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Insufficient resources to (un)register adjacent LEN %s","Branch Network node has insufficient resources to (un)register an adjacent LEN node The directory of this node and/or that of its NNS may become inconsistent, in that the LEN CP will still be there when it should not be, or vice versa. Thus session activation to the LEN may fail when a link to it is active, or neighbouring nodes may believe the LEN to be contactable when the link to is down.","Ensure sufficient resources are available to SNA Switch and then re-cycle the link to the required state."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Insufficient resources to register LU on adjacent LEN %s","Branch Network node has insufficient resources to register an LU on an adjacent LEN node. The LU resource may not be put into the directory, and may not be accessible to other resources.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Insufficient resources to register adjacent LEN LU %s","Branch Network node has insufficient resources to register an adjacent LEN node's LU The directory of this node and/or that of its NNS may become inconsistent, in that the LEN LU will not be registered when it should be. Thus session activation to the LEN LU may fail when a link to it is active","Ensure sufficient resources are available to SNA Switch and then re-cycle the link to the required state."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Insufficient storage to create new buffer pool %s","Insufficient storage to create a new buffer pool Activation of some resource (eg. session, LS) will fail. See other logs.","Investigate memory shortage and system load."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Insufficient storage to deactivate limited resource session %s","Insufficient storage to deactivate limited resource session. The limited resource session will not be deactivated (although it may be deactivated later). This could result in limited resource links being kept active while they are not required.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Insufficient storage to deactivate link %s","Insufficient storage to deactivate a link. The link will not be deactivated","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Insufficient storage to deliver MDS_MU to a registered application %s","Insufficient storage to deliver MDS_MU to a registered application. The MU will be returned to the sender indicating a resource shortage error.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Insufficient storage to forward Alert generated by DLC %s","Insufficient storage to forward Alert generated by DLC. Alert will be discarded.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Insufficient storage to generate Alert %s","Insufficient storage to generate Alert to report invalid received data. Alert is not generated.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Insufficient storage to initialise half session %s","Insufficient storage to initialise the half session. The half session will fail to activate with the specified sense code.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Insufficient storage to pass Alert data to registered Alert handler %s","Insufficient storage to pass Alert to registered Alert Handler. The alert will not be sent, however, it will be logged.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Insufficient storage to perform orderly link deactivation (link deactivated immediate instead) %s","Insufficient storage to perform orderly link deactivation, performing immediate deactivation instead. None.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Insufficient storage to process received MS Capabilities information %s","Insufficient storage to processed received MS Capabilities information. The category for which this failure occurred will be reset.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Insufficient storage to queue Alert/Resolution for error correlation, %s","Insufficient storage to queue alert or resolution for error correlation The alert or resolution will not be queued, and thus, if an error message regarding the failure to send this alert or resolution is received, MDS will be unable to correlate it. If the alert or resolution is sent successfully, no further problems will result.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Insufficient storage to report RTM statistics to Host %s","Insufficient storage to report RTM statistics to host. RTM statistics displayed by host will be inconsistent.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Insufficient storage to report RTM status to application %s","Insufficient storage to report RTM status to application. RTM statistics reported and displayed by application may be inconsistent.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Insufficient storage to request posting %s","Insufficient storage to request posting The component using the Buffer Manager may fail to operate or lock up. See other logs for effects.","Investigate memory shortage and system load."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Insufficient storage to send RTM statistics to host %s","Insufficient storage to send RTM statistics to host. RTM statistics displayed by host will be inconsistent.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Insufficient storage to update ANR routing tables following activation of an HPR-capable link %s","Insufficient storage to update ANR routing tables following activation of an HPR-capable link. HPR traffic using this ANR label will not be routed correctly, which may cause RTP connections to path-switch, or fail altogether.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch"
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Insufficient storage to update ANR routing tables following deactivation of an HPR-capable link %s","Insufficient storage to update ANR routing tables following deactivation of an HPR-capable link. The node may not be able to free resources that are no longer required but will otherwise operate normally.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch"
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Invalid ARB support received from remote node %s","A value for ARB support that the local node does not support has been received in an ARB setup segment. The remote node has not completed the ARB negotiation correctly. This is a protocol error. The connection will be deactivated.","Investigate the cause of the error at the adjacent node."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Invalid MU type received by DLUR %s","An invalid MU type has been received by DLUR from an internal or downstream PU. None (the invalid MU will be discarded).","If this is an internal PU then contact support with details of this log. If this is a downstream PU then contact the supplier of the downstream node."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Invalid TG descriptor received from DLUS %s","An invalid TG descriptor was received from a DLUS. The PU will not be activated.","Check the configuration of the DLUS named by this log. Contact support with details of the problem."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - LDLC command frame retry limit exceeded %s","LDLC command frame retry limit exceeded. Link activation will fail, or an active link will be brought down.","Check connectivity to remote address"
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - LDLC link reported inoperative by underlying media %s","LDLC link reported inoperative by underlying media. Link activation will fail, or an active link will be brought down.","Check for faults at the supplied destination address. Check for faults and error conditions in the underlying drivers and media. Check for connectivity in the underlying media. Check for outages on the connection path. Check all your wires are still plugged in."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - LFSID in use, moving on to next one. %s","An LFSID was found to be in use so SNA Switch is using a different one.","If this log appears frequently, inform your support contact."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - LU type 0,1,2 or 3 format error %s","LU type 0,1,2 or 3 format error. This may indicate an interoperability problem. The PIU containing the error is discarded.","Contact support with details of the problem"
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - LU type 0,1,2 or 3 session ended abnormally because of insufficient storage %s","LU type 0,1,2 or 3 session ended abnormally because of insufficient storage. Session will be deactivated with the specified sense code.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - LU type 0,1,2 or 3 session ended abnormally because of invalid application data %s","LU type 0,1,2 or 3 session ended abnormally because of invalid data received from application. Session will be deactivated with the specified sense code.","Contact support with details of the problem."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - LU type 0,1,2 or 3 session ended abnormally while receiving data %s","LU type 0,1,2 or 3 session ended abnormally while receiving data. Session will be deactivated with the specified sense code.","Contact support with details of the problem."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - LU-mode session limit exceeded - BIND race %s","LU-mode session limit exceeded - BIND race. This is normal race condition caused by both the local LU and partner LU attempting to activate the last session on the mode simultaneously. The race will be resolved in favour of the node with the higher name. In this case the partner LU has lost the race. Session activation will fail with specified sense code.","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - LU6.2 response correlation error %s","LU6.2 response correlation error. This may indicate an interoperability problem. Sense codes are as follows. 200E0000 - uncorrelated positive response, or uncorrelated RTR response Session will be deactivated with the specified sense code.","Use information on the session deactivated problem log (271) to identify the local LU and partner LU. If required, run a trace on the specified link station and contact support with the log and trace."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - LU6.2 session ended abnormally - insufficient storage %s","LU6.2 session ended abnormally because of insufficient storage. Session will be deactivated with the specified sense code.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - LU6.2 session state error %s","LU6.2 session state error. This may indicate an interoperability problem. Sense codes are as follows. 20020000 - chaining sequence error 20030000 - bracket state error 20040000 - received normal flow request when half-duplex flip-flop state not receive 200A0000 - immediate request mode violated by partner LU 200B0000 - queued response indicator invalid 200E0000 - unexpected SIGNAL response 200F0000 - received unexpected response or received EXPD RU before previous EXPD RU has been acknowledged 20120000 - unexpected sense code on negative response 40040000 - received RQE, BB, CEB chain from contention loser 40110000 - RU category of response doesn't match request 40120000 - request code of response doesn't match request 40210000 - QRI setting on response doesn't match request The session will be deactivated with the specified sense code.","Use information on the session deactivated problem log (271) to identify the local LU and partner LU. If required, run a trace on the specified link station and contact support with the log and trace."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Link activation race detected - adjacent node responsible for disconnect %s","A link activation race was detected on an ATM port. The remote node is responsible for resolving this race. The local node will send a negotiation error CV indicating that the remote link activation request should fail. The local node's link activation request will succeed.","This is a normal race condition - no action is required."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Link activation race detected - local node responsible for disconnect %s","A link activation race was detected on an ATM port. The local node is responsible for resolving this race. The local node will disconnect its link. The remote node's link activation request will succeed.","This is a normal race condition - no action is required."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Link activation retry limit reached %s","An automatic retry link station is still inactive after the maximum allowed number of retries. The link station will remain inactive awaiting operator intervention. In the mean time, the activation of any sessions relying on this link station will fail.","Check surrounding logs for link activation failures. Check the configuration of the link station. Check the state of the adjacent node. Issue snasw start link to retry activation."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Link failure because too many outgoing packets are queued for transmission %s","A remote node is not processing information fast enough and is causing large queues to form on this node. Link failure.","Check the error logs on the remote node that this link is connected to."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Link failure because too many outgoing packets are queued for transmission %s","A remote node is not processing information fast enough and is causing large queues to form on this node. Link failure.","Check the error logs on the remote nodes that this MLTG is connected to."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Link failure caused HPR route setup request to be dropped %s","Link failure between this node and source of Route Setup req The route setup request is dropped by this node. The partner node on that link should generate -ve reply.","Investigate link failure."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Link not configured for automatic activation or last stopped non-automatically %s","A session or application required SNA Switch to automatically activate a link station, but the link station was not configured to be automatically activated or was last stopped non-automatically. The session or application will fail, with the specified sense code.","Either manually activate the link (using snasw start link), or redefine the link to support automatic activation (using snasw link)."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Local node has received a HPR Route Setup RU that it cannot forward because the next hop is not HPR-capable so is acting as the new destination %s","The local node has received an HPR Route Setup RU that it cannot forward because the next hop in the route is not HPR-capable. The local node supports RTP so can act as the destination. The Route Setup will be between the origin node and the local node (the new destination). RTP Connections will be activated between these two nodes. This is a normal event when the local node has an auto-activateable link to a node that does not support RTP. Sessions that originate at (or beyond) the origin node will use HPR from the origin to the new destination and use ISR from the new destination and beyond it.","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Local node has received a HPR Route Setup RU that it cannot forward because the next hop is not HPR-capable so is replying with the backout sense code %s","The local node has received an HPR Route Setup RU that it cannot forward because the next hop in the route is not HPR-capable. The local node does not support RTP so it can not act as the destination node and replies with the backout sense code. The Route Setup between the origin node and the destination fail. RTP Connections cannot be activated between these two nodes. This is a normal event when the local node has an auto-activateable link to a node that does not support HPR. It may be possible for an intermediate node in the route that supports RTP to take over the role of the destination node for the Route Setup. If this happens sessions that originate at (or beyond) the origin node will use HPR from the origin to the new destination and use ISR from the new destination to the local node (and beyond it). If no intermediate node is able to act as the destination then HPR will not be used at all by such sessions.","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Local node is the destination of a HPR Route Setup RU but does not support RTP so is replying with the backout sense code %s","The local node has received an HPR Route Setup RU as the destination node but cannot accept it because it does not support RTP. The local node replies with the backout sense code. The Route Setup between the origin node and this node will fail. RTP Connections cannot be activated between these two nodes. This is a normal event when another HPR-capable node has an auto-activateable link to this node. It may be possible for an intermediate node in the route that supports RTP to take over the role of the destination node for the Route Setup. If this happens sessions that originate at (or beyond) the origin node will use HPR from the origin to the new destination and use ISR from the new destination to the local node (and beyond it). If no intermediate node is able to act as the destination then HPR will not be used at all by such sessions.","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Locate search failed: search error %s","A network search for which this node was the originator or the network node server has failed. The most common sense codes are as follows (the sense code is an amalgam of sense codes received from the various nodes that took part in the search). 08900060 - insufficient storage to process Locate search 08900010 - routing error on a directed Locate search 08900070 - session outage in the search tree 0812000A - insufficient resources at the CDS These sense codes usually indicate a transient problem in the network (either a resource shortage, or link failure). Session activation will fail with the specified sense code.","Retry the session activation. If the problem persists, contact support with details of the problem."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Locate search timed out %s","Local node timed out waiting for a Locate response from the specified adjacent node. This typically indicates a problem in another node in the network not responding to Locates (possibly because only one CP-CP session is active with an adjacent node). The Locate will be failed with the specified sense code, which is one of the following 08120010 - the adjacent CP is short of resources, CP-CP sessions will be deactivated 08900060 - search failure: the adjacent CP does not have sufficient resources (CP-CP sessions will not be deactivated)","Verify that there are no nodes in the network with a single CP-CP session active to an adjacent node."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - MDS unable to get memory for SNASVCMG session list entry %s","MDS unable to get memory for a SNASVCMG session control block. The control block will not be obtained.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - MDS unable to get memory to send TP_ENDED %s","MDS unable to get buffer to send TP_ENDED for SEND_TP. TP_ENDED will not be sent.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - MS Capabilities unable to send request due to memory shortage %s","MS Capabilities failed to get space to send a message. The message will not be sent. If the intended message was a request for focal point services, MS will pursue focal point services alternatively. If the intended message was to revoke a previous focal point, the message will not be sent. The node will still appear in the focal point's sphere of control list.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - MS unable to add time stamp and/or product set id %s","The system was unable to add the product set id or the date time stamp requested due to either memory shortage or the addition causing an NMVT to exceed maximum size. Additions will not be made to the signal.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - MS unable to allocate space for link control block %s","The system was unable to allocate resource to set up a link control block for a received PU_STATUS message. The active link will be treated as unknown by MS. Any messages received over the link will be returned as undeliverable. Any TRANSFER_MS_DATA or SEND_MDS_MUs received from applications specifying the link in the PU_STATUS will be returned with link_name unknown.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - MU format errors %s","LU6.2 session format error. This may indicate an interoperability problem. Sense codes are as follows. 080F6051 - security error (FMH12 error) 10030000 - function not supported (unrecognised request code) 10050000 - SIGNAL or LUSTAT request too short 10084001 - invalid FM header type (not 5, 7 or 12) 40030000 - BB not allowed 40040000 - CEB or EB not allowed 40070000 - definite response not allowed 40090000 - CD not allowed 400B0000 - chaining error or EC,RQE1/2,CD RU received on full-duplex conversation 400C0000 - bracket error 400F0000 - incorrect use of format indicator (FI) 40100000 - alternate code not supported 40110000 - incorrect specification of RU category 40120000 - incorrect specification of request code 40130000 - incorrect specification of SDI and RTI 40140000 - incorrect use of DR1I, DR2I and ERI 40150000 - incorrect use of QRI 40160000 - incorrect use of EDI 40170000 - incorrect use of PDI 40180000 - incorrect setting of QRI with bidder's BB 40190000 - incorrect indicators with last-in-chain request The session will be deactivated with the specified sense code.","Use information on the session deactivated problem log (271) to identify the local LU and partner LU. If required, run a trace on the specified link station and contact support with the log and trace."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Memory Failure in MDS creation sequence %s","MDS failed to get needed memory during the creation sequence. The MDS creation will fail.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Memory shortage in MDS_MU processing %s","The system was unable to needed memory for processing an MDS_MU. The MDS_MU will not be processed. If the MDS_MU originated at the local node the SEND_MDS_MU verb containing the MDS_MU will be returned to the sending application noting the error. If the MDS_MU did not originate from the local node, an error message will be returned to the originating application.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Memory shortage in processing signal %s","The system was unable to allocate memory to process an incoming TRANSFER_MS_DATA or SEND_MDS_MU or register signal. The signal will be returned to the sender noting the resource shortage error.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Memory shortage in trying to send an alert %s","The system was unable to allocate memory needed to send an alert. The alert will not be sent, however, the sense code of the alert will be logged.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Memory shortage in verb processing %s","The system was unable to allocate control block space to process an incoming verb. The verb will not be processed and it will be returned to the sending application with a primary return code of NAP_UNEXPECTED_SYSTEM_ERROR.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Memory shortage preventing data log %s","The system was unable to allocate memory and was thus unable to log data supplied by the user. The data will not be logged.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - NLP received for RTP connection which no longer exists %s","An NLP has been received for an RTP connection which no longer exists The message cannot be processed, and will be discarded.","Report error to remote end."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - NLP received with format errors %s","An NLP has been received with format errors The message cannot be processed, and will be discarded.","Report error to remote end."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Network Node server not required %s","Network Node server not required. This is logged when a back-level APPN network node (ie. one that does not support function set 1015) attempt to activate CP-CP sessions with SNA Switch (EN) when it already has a network node server. The CP-CP session will be deactivated with the specified sense code. SNA Switch cannot subsequently use this network node as its server unless all links to it are deactivated (and at least one restarted).","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - PORT_BANDWIDTH_UPDATE (status = OK) received %s","A PORT_BANDWIDTH_UPDATE signal (status = OK) has been received. Any Connection Network TGs on this port which had been advertised as quiescing will be advertised as active. Any auto-activatable TGs which had been advertised as non-operational will be advertised as operational.","To avoid future problems with bandwidth shortage, increase the bandwidth available to the local port."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - PORT_BANDWIDTH_UPDATE (status = QUIESCING) received %s","A PORT_BANDWIDTH_UPDATE signal (status = QUIESCING) has been received. Any Connection Network TGs on this port will be advertised as quiescing. Any auto-activatable TGs will be advertised as non-operational.","If possible, increase the bandwidth available to the local port."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - PU not found for REQACTPU RSP or REQDACTPU %s","A REQACTPU RSP or REQDACTPU has been recevied and the node has not been able to correlate it to a PU_CB. The REQ(D)ACTPU(RSP) will be discarded.","Contact the supplier of the DLUS with details of this log."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Parsing error found in MDS_MU header %s","MDS received an MDS_MU that it could not parse correctly. An alert will be raised. If the MDS_MU originated from a local application, the SEND_MDS_MU will be returned with the return codes NAP_PARAMETER_CHECK and NAP_INVALID_MDS_MU_FORMAT.","Investigate syntax of MDS_MU sent, correct syntax, and reissue the SEND_MDS_MU."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Path-switch failure %s","RTP connection has failed to path-switch The RTP connection will be disconnected","Investigate the cause of the error"
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Protocol Error from DLUS Host: RU Size too large for SSCP Session %s","Protocol Error from DLUS. Received an RU too large for SSCP Session. This is typically due to the SSCP sending too large a LOGON Screen. The Data is thrown away.","If you are expecting an SSCP LOGON screen, enter your LOGON command as usual."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Protocol error detected in PIU on intermediate session %s","SNA Switch detected a protocol error in an PIU received on an intermediate session. This typically indicates a problem on an adjacent node. The sense codes are as follows. 10010003 - invalid IPM format 10020000 - RU length error 10030000 - CLEAR request on secondary stage, or CLEAR response on primary stage 20110000 - sender has overrun pacing window, or PI not set on first RU of window 20110001 - unexpected IPM 20110002 - PI set on other than first RU in window 20110003 - invalid pacing response 80070000 - segment error The intermediate session will be deactivated.","Report the problem in the adjacent node to support (running a trace on the specified link if more diagnostics are required)"
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Protocol error detected on conversation %s","SNA Switch detected a protocol error on an APPC conversation. Sense codes are as follows. 10010000 - invalid GDS logical length 1008201D - FMH7 or log data mismatch (for example, FMH7 not received when expected, or log data truncated, or CEB not set on FMH7 when expected) 10086000 - received FMH but not FMH7 1008200E - FMH7 format error (log data concatenation not valid) 1008200A - FMH7 received with no sense data (sense data is zero) 20040000 - An incoming RU has been received on a full-duplex conversation which is in send-only state The conversation will be terminated, either by an APPC primary_rc of NAP_CONV_FAILURE_NO_RETRY, or a CPI-C return_code of CM_RESOURCE_FAILURE_NO_RETRY, and the session deactivated.","Report the protocol error to partner LU support. If additional diagnostic information is required, run a link trace (the session identifier can be used to correlate this log to other logs which contain the appropriate link station name)."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Protocol error during CRV exchange %s","Protocol error during CRV exchange. This indicates a possible interoperability problem. Sense codes are as follows. 20090000 - CRV request received from secondary LU, or CRV response received from primary LU, or CRV not received when expected 10020000 - CRV RU too short 400F0000 - CRV with FI not set 400B0000 - CRV chain indicators not set to BC, EC 40140000 - CRV not RQD1 40110000 - CRV not expedited 40150000 - CRV with QRI not set 40080000 - CRV with PI set 400C0000 - CRV request with BBI, EBI or CEBI set 400D0000 - CRV request with CDI set 40100000 - CRV request with CSI set to CODE1 40160000 - CRV request with EDI set 40170000 - CRV request with PDI set 40130000 - CRV response RTI and SDI inconsistent Session will be deactivated with specified sense code.","Use information on the session deactivated problem log (271) to identify the local LU and partner LU. Run a trace on the specified link station, and contact support with the log and trace."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - RTP Connection has disconnected %s","The RTP Connection has disconnected due to an error Sessions using the connection will fail","Investigate the cause of the error"
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - RTP Connection is path-switching to a much longer path %s","An RTP connection is path-switching to a much longer path than it started with. Much more room is needed in each packet for routing information than was originally planned. Performance across this RTP connection may degrade, since some packets may have to be segmented.","If performance degradation is noticed, reactivate failed links then issue the 'PATH_SWITCH' verb."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - RTP connection dropped due to local link failure %s","An RTP connection has been dropped by a local link failure (possibly due to operator intervention) The node will attempt to path switch","Investigate the cause of the link failure"
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - RTP connection has timed-out %s","A Route Setup RTP Connection has timed out waiting for status from the adjacent node. The RTP Connection will be failed.","Investigate the cause of the error at the adjacent node."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - RTP connection has timed-out %s","he RTP Connection has timed out The node will attempt to path-switch","Investigate the cause of the error"
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - RU length error %s","RU length error. This may indicate an interoperability problem. Sense codes are as follows. 10020000 - RU length error The session will be deactivated with the specified sense code.","For an LU6.2 session, use information on the session deactivated problem log (271) to identify the local LU and partner LU. If required, run a trace on the specified link station and contact support with the log and trace."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Received ACTLU when LU already active %s","ACTLU received when LU already active. ACTLU will be rejected with specified sense code.","Run a trace on the link station corresponding to the specified PU name. Contact host support with details of the problem."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Received Locate with no Find GDS variable %s","Received Locate with no Find GDS variable. None (the Locate is discarded).","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Received a Locate reply with an invalid RSCV %s","A locate reply was received that contained an invalid RSCV. The locate request that solicited the reply may be failed.","Contact support with details of the problem."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Received a frame with a badly formed transmission header or a frame that is too small to be a valid SNA frame %s","Received a frame with a badly formed transmission header or a frame that is too small to be a valid SNA frame. The invalid frame will be discarded. An alert is generated.","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Register GDS variable received with an invalid resource name %s","Invalid resource name in received register request. Register request will fail.","Contact support with details of the problem."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Remote NCE has restarted, so disconnect this RTP connection with previous instance of that NCE %s","A connection setup NLP has been received from a remote NCE which has shut down and restarted. An RTP connection still exists from that NCE before it shut down. The old RTP connection will be disconnected","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Remote end of RTP Connection has disconnected %s","The RTP Connection has disconnected due to an error Sessions using the connection will fail","Investigate the cause of the error"
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Retrying CP-CP session activation after failure %s","Retrying CP-CP session establishment after error. None.","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - SIGNAL RU received on full-duplex conversation %s","An incoming SIGNAL RU has been received on a full-duplex conversation. The session will be deactivated with the specified sense code. (10030004)","Contact support with details of the problem."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - SNA Switch could not allocate necessary storage %s","SNA Switch could not allocate necessary storage. Some operation may fail. See other logs.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - SNA Switch cryptography call failed, possibly due to missing password %s","A call from SNA Switch to perform a cryptographic operation failed. Session activation will fail, or an active session will end abnormally with the given sense code, or some other action will fail. More information may appear in subsequent logs.","Check following logs for evidence of failed session activation. If this is evident, check MODE, LS, or INTERNAL PU definitions for cryptographic support. Check that any passwords necessary have been defined. If this problem occurs intermittently or with sessions already active with the same PLU, SLU and mode then make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - SNA Switch detected a mapped conversation protocol error on an APPC mapped conversation %s","SNA Switch detected a mapped conversation protocol error on an APPC mapped conversation. The conversation will be terminated, either by an APPC primary_rc of NAP_CONV_FAILURE_NO_RETRY, or a CPI-C return_code of CM_RESOURCE_FAILURE_NO_RETRY. The partner TP will fail the conversation with an APPC primary_rc of NAP_DEALLOCATE_ABEND or a CPI-C return_code of CM_DEALLOCATE_ABEND. The session will not be deactivated.","Report the protocol error to partner LU support. If additional diagnostic information is required, run a link trace (the session identifier can be used to correlate this log to other logs which contain the appropriate link station name)."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - SNA Switch detected a mapped conversation protocol error on an APPC mapped conversation %s","SNA Switch received an error data GDS variable on an APPC mapped conversation. The conversation will be terminated, either by an APPC primary_rc of NAP_CONV_FAILURE_NO_RETRY, or a CPI-C return_code of CM_RESOURCE_FAILURE_NO_RETRY. The partner TP will fail the conversation with an APPC primary_rc of NAP_DEALLOCATE_ABEND or a CPI-C return_code of CM_DEALLOCATE_ABEND. The session will not be deactivated.","Report the protocol error to partner LU support. If additional diagnostic information is required, run a link trace (the session identifier can be used to correlate this log to other logs which contain the appropriate link station name)."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Segmented NLP received on Route Setup RTP connection %s","A Route Setup RTP Connection RTP process received a segmented NLP. This is an error because all NLPs received should contain Route Setup GDS data, which should never be segmented. The NLP will be dropped.","Contact support with details of the problem."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Served end node attempted to delete a non-existant directory entry %s","A served end node attempted to delete a directory entry that does not exist. This is normally caused by a network race condition, causing the Delete request to arrive when the resource has not been registered. The Delete request is rejected with the specified sense code.","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Session pacing error %s","Session pacing error. This may indicate an interoperability problem. Sense codes are as follows. 20110000 - sender has overrun pacing window, or PI not set on first RU of window 20110001 - unexpected IPM 20110002 - PI set on other than first RU in window 20110003 - invalid pacing response 10010003 - invalid IPM format The session will be deactivated with the specified sense code.","Use information on the session deactivated problem log (271) to identify the local LU and partner LU. If required, run a trace on the specified link station and contact support with the log and trace."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Session segmentation error %s","Session segmentation error. This may indicate an interoperability problem. Sense codes are as follows. 80070000 - segmenting error 80070001 - segmentation not supported on this link The session will be deactivated with the specified sense code.","Use information on the session deactivated problem log (271) to identify the local LU and partner LU. If required, run a trace on the specified link station and contact support with the log and trace."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Standard compression levels used %s","A bind response was received that accepted session compression, but it did not specify the compression levels required (either because the response is from a back-level node or because the bind request was shortened). The compression level negotiation fails and the standard compression levels are used - this means that compression will be used in both directions even though it may have been configured for one direction only.","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - The Buffer Manager Monitor could not allocate necessary resource %s","The Buffer Manager Monitor could not allocate necessary resource. The Buffer Manager will fail to operate and detect congestion conditions or relief from congestion, possibly leading to the node locking up.","Shutdown and restart the node."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - The local node is acting as the new destination for a backed-out Route Setup %s","The local node has received an HPR Route Setup Reply that contains the backout sense code and is able to act as the new destination for the Route Setup. The Route Setup has been successfully backed out. The Route Setup is between the origin node and the local node (the new destination). RTP Connections will be activated between these two nodes. This is a normal event when a node in the route has an auto-activateable link to a node that does not support RTP or HPR. Sessions that originate at (or beyond) the origin node will use HPR from the origin node to the new destination and use ISR from the new destination and beyond it.","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - UNBIND could not be correlated to DLUR-served LU %s","Unable to correlate received UNBIND request to a DLUR-supported session. This is a normal race condition (caused by UNBIND requests crossing). None (will send a +ve response to UNBIND).","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - UNBIND request received in response to a BIND request %s","UNBIND request received in response to a BIND request. This may indicate a configuration error, or a protocol error. Common sense codes which typically indicate a configuration error or a normal race condition include 0805xxxx - the session could not be activated as session activation limits have been reached 08060014 - the partner LU is not known 0806xxxx - the BIND specified a resource which is not known 080Fxxxx - security authorization failed 0821xxxx - the BIND supplied an invalid session parameter 0835xxxx - parameter error in BIND RU at offset xxxx Other sense codes include 0812xxxx - session activation failed due to resource shortage at the remote node 083Bxxxx - invalid PCID in BIND RU 0852xxxx - duplicate session activation request 0861xxxx - invalid COS name in BIND RU 088Cxxxx - control vector or subfield missing from BIND RU 0895xxxx - BIND RU contained a control vector that was in error 0896xxxx - BIND RU contained a control vector that was too long Session activation will fail with the specified sense code.","If the sense code indicates a configuration error, check for inconsistencies between the configuration at the local LU and the configuration at the partner LU. If the configuration is consistent and the problem persists, contact support with details of the problem."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to activate IPDLC link %s","Unable to activate an IPDLC link. Link activation cannot continue. This will result in the failure of an outbound link activation attempt or the rejection of an inbound link activation.","- Check surrounding logs for evidence of buffer congestion. If buffer congestion is causing this failure, either decrease system load or make more resources available to IPDLC. - Ensure that the necessary facilities are available for the UDP interface to operate correctly. - Check that valid DLC specific configuration data was provided to SNAP-IPDLC at define time."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to activate IPDLC port %s","Unable to activate an IPDLC port. This will result in the failure of a port activation attempt. No further IPDLC operation will be possible until a port is activated successfully.","- Check surrounding logs for evidence of buffer congestion. If buffer congestion is causing this failure, either decrease system load or make more resources available to IPDLC. - Ensure that the necessary facilities are available for the UDP interface to operate correctly. - Check that valid DLC specific configuration data was provided to IPDLC at define time."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to activate Route Setup RTP connection %s","Unable to activate a Route Setup RTP Connection, during processing of a Route Setup request. The Route Setup request will fail with the sense code shown. The next Route Setup request will trigger another attempt to activate the Route Setup RTP Connection.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to activate a new session since it would exceed the LU-mode session limit %s","Unable to activate a new session since it would exceed the LU-mode session limits. This problem is a normal race condition, and so should occur infrequently. Session activation will fail with specified sense code (which may cause ALLOCATE, MC_ALLOCATE or CMALLC requests to fail).","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to activate dynamic link station because owning port is not active %s","A session required SNA Switch to automatically activate a dynamic link station, but the request was failed because the owning port was not active. This problem usually indicates an inconsistent network topology, which may be transient (that is, caused by a normal race condition), or permanent (indicated by logs 127 or 128). The session will fail, with the specified sense code.","If possible, increase the port activation limits. Otherwise, check the consistency of the network topology."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to activate dynamic link station because port outbound link-activation limit reached %s","A session required SNA Switch to automatically activate a dynamic link station, but the request was failed because it would have exceeded the maximum number of concurrently active outbound links allowed for the owning port. This number is the total link-activation limit minus the inbound link-activation limit (that part of the total limit reserved for active inbound links). This problem usually indicates an inconsistent network topology, which may be transient (that is, caused by a normal race condition), or permanent (indicated by logs 127 or 128). The session will fail, with the specified sense code.","Check the consistency of the network topology."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to activate dynamic link station because port total link-activation limit reached %s","A session required SNA Switch to automatically activate a dynamic link station, but the request was failed because it would have exceeded the port total link-activation limit. This problem usually indicates an inconsistent network topology, which may be transient (that is, caused by a normal race condition), or permanent (indicated by logs 127 or 128). The session will fail, with the specified sense code.","Check the consistency of the network topology."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to activate link station because owning port is not active %s","A session or application required SNA Switch to automatically activate a link station, but the request was failed because the owning port was not active. This problem usually indicates an inconsistent network topology, which may be transient (that is, caused by a normal race condition), or permanent (indicated by logs 127 or 128). The session or application will fail, with the specified sense code.","If possible, increase the port link-activation limits. Otherwise, check the consistency of the network topology."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to activate link station because port outbound link-activation limit reached %s","A session or application required SNA Switch to automatically activate a link station, but the request was failed because it would have exceeded the maximum number of concurrently active outbound links allowed for the owning port. This number is the total link-activation limit minus the inbound link-activation limit (that part of the total limit reserved for active inbound links). This problem usually indicates an inconsistent network topology, which may be transient (that is, caused by a normal race condition), or permanent (indicated by logs 127 or 128). The session or application will fail, with the specified sense code.","Check the consistency of the network topology."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to activate link station because port total link-activation limit reached %s","A session or application required SNA Switch to automatically activate a link station, but the request was failed because it would have exceeded the port total link-activation limit. This problem usually indicates an inconsistent network topology, which may be transient (that is, caused by a normal race condition), or permanent (indicated by logs 127 or 128). The session or application will fail, with the specified sense code.","Check the consistency of the network topology."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to correlate BIND response received during ISR session activation %s","Unable to correlate BIND response received during ISR session activation. None. This is a normal race condition (caused by a BIND request being immediately followed by an UNBIND request for the same session).","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to correlate DLC credit for MLTG link %s","Unable to correlate DLC credit for MLTG link. Probably none. This exception will occur during a window condition in normal link deactivation.","If several instances of this log appear and also poor RTP connection performance is observed, investigate further by querying link stations which are members of MLTGs. Unexpectedly low quantities of data sent over a link may indicate problems with DLC credit. Contact support with details of the problem, including trace of signals sent to and from the DLCs underlying the affected links."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to correlate HPR Route Setup RU %s","Unable to correlate HPR Route Setup Reply The message cannot be processed, and will be discarded.","Report error to remote end."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to correlate UNBIND request received for an ISR session %s","Failed to correlate an UNBIND request received for an ISR session. None (+RSP(UNBIND) is sent in reply). This is a normal race condition (typically caused by UNBIND requests for the same session crossing).","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to correlate received BIND response %s","Unable to correlate received BIND response. This is a normal race condition, caused by a BIND being followed immediately by an UNBIND for the same session. BIND response is discarded.","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to correlate received BIND response %s","Unable to correlate received BIND response. This is probably caused by a normal race condition (a BIND request, followed immediately by an UNBIND request and then by another BIND request using the same LFSID - the response to the first BIND request will not be correlated). None (BIND response will be discarded).","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to correlate received INIT-SELF response or NOTIFY request %s","Unable to correlate received INIT-SELF response or NOTIFY request. This is a normal race condition (caused by the session being deactivated before the INIT-SELF response has arrived). None (request or response is discarded).","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to correlate received UNBIND request %s","Unable to correlate received UNBIND request. This is a normal race condition (caused by UNBIND requests crossing). None (will send a +ve response to UNBIND).","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to create a new LDLC_CTRL instance %s","Unable to create a new LDLC_CTRL instance. Link activation cannot continue. This will result in the failure of an outbound link activation attempt or the rejection of an inbound link activation.","Check surrounding logs for evidence of buffer congestion. If buffer congestion is causing this failure, either decrease the system load or make more resources available to LDLC."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to extend local form session identifier routing table %s","Unable to extend local form session identifier routing table. Session activation will fail with the specified sense code.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to find requested connection network %s","A session required SNA Switch to automatically activate a dynamic link station, but SNA Switch was unable to identify the requested connection network TG. This problem usually indicates an inconsistent network topology, which may be transient (that is, caused by a normal race condition), or permanent (indicated by logs 127 or 128). The session will fail, with the specified sense code.","Check the consistency of the network topology."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to find requested connection network %s","A session required SNA Switch to automatically activate a dynamic link station, but SNA Switch was unable to identify the requested connection network. This problem usually indicates an inconsistent network topology, which may be transient (that is, caused by a normal race condition), or permanent (indicated by logs 127 or 128). The session will fail, with the specified sense code.","Check the consistency of the network topology."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to find requested link %s","A locally initiated dependent session activation request required SNA Switch to automatically activate a link to a specified PU name, but SNA Switch was unable to identify the a link to the PU. This problem indicates an inconsistent local configuration which is transient and is caused by a recent modification. The session activation request will fail, with the specified sense code.","Check the consistency of the local configuration (link definitions can be viewed using show snasw link)."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to find requested link %s","A session required SNA Switch to automatically activate a link station, but SNA Switch was unable to identify the requested link. This problem usually indicates an inconsistent network topology, which may be transient (that is, caused by a normal race condition), or permanent (indicated by logs 127 or 128). The session will fail, with the specified sense code.","Check the consistency of the network topology."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to forward an HPR NLP - unknown ANR label %s","Failed to forward an HPR Network Layer Packet because the ANR label could not be matched to an outgoing link. This is usually a normal race condition when an HPR-capable link is deactivated, although it may also be caused by an earlier resource shortage (look for log 192). An RTP connection will attempt to path switch, or may fail.","Use show snasw link to look for an active HPR-capable link with the specified ANR label. If there is one, then the problem has been caused by a storage shortage. Either decrease the system load (for example, by reducing the number of active sessions, or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to generate session route - RSCV truncated %s","Route Selection Control Vector generated for route was too long (must be less than 256 bytes long). A session activation will fail with the specified sense code.","Reconfigure the network to ensure there is a short enough route between the origin and destination nodes."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to generate session route - no suitable TGs from origin node %s","No suitable TG could be found from the origin end node to the backbone network for the class of service specified for a session activation. This may be caused by a temporary link failure between the origin node and a network node. A session activation will fail with the specified sense code.","First check for a link failure at the origin node that explains the route failure. If no link failure is found, either - change the mode-to-COS mapping on the origin node or its network node server to use a different class of service, or - reconfigure the network to ensure there is a usable route from the origin node to the backbone network (for example, by defining and/or activating another link from the origin node to a network node)."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to generate session route - no suitable TGs to destination node %s","No suitable TG could be found from the backbone network to the destination end node for the class of service specified for a session activation. This may be caused by a temporary link failure between the destination node and a network node. A session activation will fail with the specified sense code.","First check for a link failure at the destination node that explains the route failure. If no link failure is found, either - change the mode-to-COS mapping on the origin node or its network node server to use a different class of service, or - reconfigure the network to ensure there is a useable route from the destination node to the backbone network (for example, by defining and/or activating another link from the destination node to a network node)."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to generate session route : unknown COS name %s","A Class of Service name specified for a session activation could not be associated with a valid COS. A session activation will fail with the specified sense code.","Ensure no mode-to-COS mapping tables at the origin node or its network node server use the unrecognised COS."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to generate session route to adjacent node %s","No suitable TG could be found for a session activation to an adjacent node for the given Class of Service. This may be caused by a link failure. A session activation will fail with the specified sense code.","Check for a link failure that explains the failure. If no link failure is found reconfigure the network to ensure there is a useable link between this node and the specified adjacent node."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to grant credit %s","Unable to grant credit LDLC is unable to grant further send credit.","Check surrounding logs for evidence of buffer congestion. If buffer congestion is causing this failure, either decrease the system load or make more resources available to LDLC."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to process Sign-Off verb due to resource shortage. %s","The local LU was unable to process a Sign-Off verb issued by a local TP due to resorce shortage. The Sign-Off request will fail, and any entries in the signed-on-to and sign-on-from lists will remain valid.","Either decrease the system load (for example, by reducing the number of active sessions), or make more storage available to SNA Switch."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to route inter-node session data %s","Unable to route inter-node session data. This usually indicates a race condition when an inter-node session is deactivating. None.","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to route intra-node session data %s","Unable to route intra-node session data. This usually indicates a race condition when an intra-node session is deactivating. None.","None."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unable to start requested CP-CP sessions with adjacent node %s","The specified link is configured to support CP-CP sessions, but these sessions could not be started. This could either be because the remote node is not configured to support CP-CP sessions on this link, or because both the local and remote nodes are End Nodes, and hence CP-CP sessions are not allowed to be started. CP-CP sessions will not be established.","Correct the configuration mismatch, either by removing CP-CP sessions support from the local connection definition, or by adding it to the adjacent node's connection definition."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unexpected what_received in MDS Transaction Program %s","An MDS Transaction Program received an unexpected what_received. The transaction program will re-initialize. The MDS_MU that was being sent will be returned to the originator if the error was detected at the originating node, or the originator will be notified of the send failure via an error message.","Investigate cause of unexpected what_received."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unrecognised LDLC RU identifier %s","Unrecognised LDLC RU identifier. This packet cannot be processed by LDLC and will be discarded. Link activation may fail. Link deactivation may fail. Data may be lost. This may indicate an interoperability problem.","Check surrounding logs for other evidence of interoperability problems. If failures or problems occur, gather trace of the protocol flows then report this problem to support."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unrecognised NHDR routing instruction %s","Unrecognised NHDR routing instruction. This packet cannot be routed by LDLC and will be discarded. Data may be lost. This may indicate an interoperability problem.","Check surrounding logs for other evidence of interoperability problems. If failures or problems occur, gather trace of the protocol flows then report this problem to support."
"SNASW","4","UNAVAILABLE","EXCEPTION - %lu - Unrecognized signal received from application %s","A signal was received which was unrecognized and could not be returned to the sender. The signal memory will be freed.","Check that issued signals are acceptable according to the API specification."
"SNASW","4","UNAVAILABLE","SNASw process, type 0x%x ran for %lu ms processing IPS of type 0x%x, address 0x%lx","A process within SNA Switch ran for an unexpectedly long time.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SNASW","6","UNAVAILABLE","INFO - %lu - A PLU-SLU session has been activated for LU type 0,1,2 or 3 %s","A PLU-SLU session has been activated.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - A PLU-SLU session has been deactivated for LU type 0,1,2 or 3 %s","A PLU-SLU session has been deactivated.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - A PU previously logged as possibly hung is no longer possibly hung %s","A PU that had previously been logged as hung is now not believed to be hung. There will be no further action taken","None."
"SNASW","6","UNAVAILABLE","INFO - %lu - A PU-SSCP session has been activated %s","A PU-SSCP session has been activated.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - A PU-SSCP session has been deactivated %s","A PU-SSCP session has been deactivated.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - A pipe to a DLUS has activated %s","A pipe to a DLUS has activated.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - A pipe to a DLUS has deactivated %s","A pipe to a DLUS has deactivated.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - Adjacent CP contacted %s","Adjacent CP contacted.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - Adjacent node has changed its CP name %s","An adjacent node has changed its CP name.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - Alert data logged %s","TRANSFER_MS_DATA/SEND_MDS_MU data has arrived.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - An LU-SSCP session has been activated for LU type 0,1,2 or 3 %s","An LU-SSCP session has been activated.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - An LU-SSCP session has been activated for LU type 6.2 %s","An LU-SSCP session has been activated.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - An LU-SSCP session has been deactivated for LU type 0,1,2 or 3 %s","An LU-SSCP session has been deactivated.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - An LU-SSCP session has been deactivated for LU type 6.2 %s","An LU-SSCP session has been deactivated.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - CP-CP sessions deactivated %s","CP-CP sessions to the adjacent node have been deactivated.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - CP-CP sessions established %s","CP-CP sessions have been successfully established with the adjacent node.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - Central Directory Server located %s","Central Directory Server located.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - DLC started %s","A DLC has been successfully started.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - DLC stopped %s","A DLC has been successfully stopped.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - Deactivating a persistent pipe because it is not required %s","The DLUR is deactivating a persistent pipe because it is not required to keep it active.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - HPR-capable SNA Switch link started %s","An SNA Switch link has been successfully started (on a node that supports HPR).","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - ISR Session Activated %s","An ISR Session has been activated","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - ISR Session Deactivated %s","An ISR Session has been deactivated","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - Implicit link limit on port reached %s","An implicit, dynamic or discovery link could not be activated because the implicit link limit defined on the port has been reached or exceeded. The link type being activated is: 1 - dynamic 3 - implicit 4 - discovery","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - Invalid IP address specified for a IPDLC link %s","Invalid IP address specified for a IPDLC link. The link will fail to start.","Correct the configuration. These settings are supplied in the address information passed to SNA Switch on snasw link."
"SNASW","6","UNAVAILABLE","INFO - %lu - LU6.2 session activated %s","An LU6.2 session has been activated.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - LU6.2 session deactivated %s","An LU6.2 session has been deactivated.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - Link activation race has occurred %s","Link activation race has occurred Link activation will complete, but the routes may be different in each direction. No other effect will be noticeable.","None."
"SNASW","6","UNAVAILABLE","INFO - %lu - Link station to DSPU started %s","A non-APPN link station to a downstream PU has been successfully started.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - Link station to DSPU stopped %s","A non-APPN link station to a downstream PU has been successfully stopped.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - Link station to host started %s","A non-APPN link station to an upstream host has been successfully started.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - Link station to host stopped %s","A non-APPN link station to an upstream host has been successfully stopped.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - Locate search failed: LU not found %s","A network search for which this node was the originator or the network node server failed to locate the target LU. This may be caused by the target LU name being incorrect, the target system being inoperative, or by link errors in the backbone of the network. Session activation will fail with the specified sense code.","If the target LU name is correct, check that the system the LU is defined on is active. If the system is active, check the topology of the network to ensure that the target system (or its network node server) is reachable from this node."
"SNASW","6","UNAVAILABLE","INFO - %lu - Node started %s","Node has been successfully started.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - Node stopped %s","Node has been successfully stopped.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - Port started %s","A Port has been successfully started.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - Port stopped %s","A Port has been successfully stopped.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - Processed APING from partner LU. %s","An APING from the partner LU has been processed successfully.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - RTP Connection has connected %s","The RTP Connection has connected","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - RTP Connection has disconnected %s","The RTP Connection has disconnected normally","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - SNA Switch link started %s","An SNA Switch link has been successfully started.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - SNA Switch link stopped %s","An SNA Switch link has been successfully stopped.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - Session limits changed %s","The session limits for a local LU, partner LU and mode have changed. The termination count indicates the number of sessions SNA Switch will deactivate as a result of the change in session limits.","None"
"SNASW","6","UNAVAILABLE","INFO - %lu - Successful path-switch %s","he RTP Connection has successfully switched paths","None"
"SNMP","3","AUTHFAILIPV6","Authentication failure for SNMP request from host %P","An SNMP request sent by this host was not authenticated.","Make sure that the community and user name used in the SNMP request has been configured on the router."
"SNMP","3","BADIFINDEXTABLE","The file nvram:ifIndex-table is corrupt.","The file is not in the expected format.","Delete the file if possible."
"SNMP","3","DVR_DUP_REGN_ERR","Attempt for dupe regn with SNMP IM by driver having ifIndex [dec] and ifDescr [chars]","A driver is attempting to register an IDB with the interface manager while there is already an interface with the same ifIndex and ifDescr but different IDB registered. A duplicate registration would cause the interface counters shown by SNMP to not work properly for this particular interface.","Fix the duplicate registration in the driver level."
"SNMP","3","DVR_DUP_REGN_WARNING","Attempt for dupe regn with SNMP IM by driver having ifIndex [dec] and ifDescr [chars]","A driver is attempting to register an IDB that is already registered with the interface manager. This is just a warning message and handled by SNMP.","Fix the duplicate registration in the driver level."
"SNMP","3","DYNSYNCFAIL","Snmp Dynamic Sync Failed for %s %s %s%s","The dynamic synchronization of an SNMP MIB to the standby device failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SNMP","3","INPUT_QFULL_ERR","Packet dropped due to input queue full","An SNMP packet was dropped because the input queue is full.","Enter the show snmp command to see the number of packets dropped. Stop any SNMP access to the device until the error condition has recovered."
"SNMP","3","INTERRUPT_CALL_ERR","[chars] function, cannot be called from interrupt handler","A call has been made to the function from an interrupt handler. This is not permitted. The function call will fail and the device will reboot down the stack in a memory allocation call.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SNMP","3","ISSU_ERR","[chars]","An error occurred during an ISSU versioning operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SNMP","3","MAX_TRAPS_EXCEED_ERR","Maximum number of traps exceeded the maximum allowed in the current sync-message to STANDBY","This is a software development debug message. The number of SNMP traps defined exceeded the maximum allowed in a checkpoint synchronization message.","(These actions apply only to the developer, and not to the user.) Increase SNMP_SYNC_BITMASK_MAX to a higher value. Check smci_rf_status_event() for further details."
"SNMP","3","SYNCFAIL","SNMP MIB Sync Failure: [chars]","An error occurred while synchronizing an SNMP MIB to standby.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SNMP","4","HIGHCPU","Process exceeds %dms threshold (%dms IOS quantum) for %s of %s--result %s","A warning threshold was exceeded when SNMP was processing a variable binding.","Enter the debug snmp packet command to determine the contents of the SNMP request that is causing the message. Some MIB objects require a relatively large amount of time to process. MIB objects in the multi-variable-binding are processed one by one. If possible, do not retrieve MIB objects appearing in this messages by using multi-variable-binding SNMP PDUs. Copy the error message exactly as it appears, and report it along with any debug output to your technical support representative."
"SNMP","4","NOENGINEIDV6","Remote snmpEngineID for %P not found when creating user: %s","An attempt to create a user failed, probably because the engine ID of the remote agent or SNMP manager was not configured.","Configure the remote snmpEngineID and reconfigure the user. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SNMP","5","LINK_DOWN","LinkDown:Interface %s changed state to down","The state of the interface is changed to down.","No action is required."
"SNMP","5","LINK_UP","LinkUp:Interface %s changed state to up","The state of the interface is changed to up.","No action is required."
"SNMP","5","MODULERESET","[chars] object has been set to 'reset' for [chars]=[dec] from IP address [chars].","The SNMP server has reset a module.","No action is required."
"SNMP_BULKSTAT","3","5","Memory not available for [chars] for [chars]","Data collection or transfer could not be successfully carried out because of lack of memory.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"SNMP_BULKSTAT","3","REMOTE_FILE_WRITE_ERR","File Write failed for the remote file [chars]","The user name or password specified in the error message might not have the required privileges to write a file to the network management station specified in the error message, or the destination directory specified in the error message is invalid.","Ensure that the user name and password in the network management station address has the necessary privileges to write to the destination directory."
"SNMP_BULKSTAT","3","TOOSMALL_BUFFER","Buffer size is insufficient to accommodate even the header part for [chars]","The buffer size is insufficient to accommodate the header for the bulk data file. The header contains the schema definitions of all the configured schemas.","Increase the maximum buffer size using the buffer-size size-of-buffer command, where size-of-buffer is the increased buffer size."
"SNMP_BULKSTAT","4","BUFFER_OVERFLOW","Buffer size too small to accomodate data for one collection interval for [chars]","The bulk data file is too large for the configured buffer size for a single transfer interval. Data collection will continue in another new buffer of the configured size, and the collected buffer will be transferred to the configured destination.","Increase the maximum buffer size using the buffer-size size-of-buffer command, where size-of-buffer is the increased buffer size."
"SNMP_BULKSTAT","4","PRI_URL_UNREACHABLE","Primary network management station is unreachable for [chars]","The collected bulk data file could not be successfully transferred to the primary network management station address specified in the error message. This condition can occur because the primary network management address is not configured or the configured primary network management station address is unreachable. If a secondary network management station address is configured, the collected bulk data file will be sent to the secondary network management station address.","Ensure that the primary network management station address is configured. If the primary network management station address is configured, check the connectivity to the destination indicated by the primary network management station address specified in the error message."
"SNMP_BULKSTAT","4","SEC_URL_UNREACHABLE","Secondary network management station is unreachable for [chars]","The collected bulk data file could not be successfully transferred to the secondary network management station address destination specified in the error message. This condition can occur because the secondary network management station address is not configured or the configured secondary network management station address is unreachable. If a retention interval is not configured, the bulk data file will be immediately deleted. If a retention interval is configured, retries will be attempted for the configured number of times.","Check the connectivity to the destination indicated by the secondary network management station address shown in the error message."
"SNMP_MGR","3","BADINFORMTRANSPORT","Unknown inform transport type: [chars]","This SNMP inform destination uses an unknown transport type. Inform notifications cannot be sent to this destination.","Copy the error message and the output from show techsupport exactly as it appears, and report it to your technical support representative."
"SNMP_MGR","3","MISSINGHOSTIPV6","Cannot locate information on SNMP informs host: %P","A table entry cannot be found for the indicated SNMP informs destination. As a result, inform notifications will not be sent to this destination.","Delete and readd the informs destination by entering the snmp-server host configuration command. If this does not clear the condition, reload the system and 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show snmp host, and show snmp commands and your pertinent troubleshooting logs."
"SNMP_MGR","4","BADRESPONSESTATUS","Unknown response status code: [int]","The SNMP Manager process received an internal response with an unknown status code.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"SNMP_MIB_ISSU","2","GET_BUFFER","SNMP MIB ISSU client failed to get buffer for message. Error: %d (%s)","The SNMP MIB ISSU client was unable to get buffer space for building a negotiation message. As a result, the negotiation message cannot be sent to the standby device and the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"SNMP_MIB_ISSU","2","INIT","SNMP MIB ISSU client initialization failed to %s. Error: %d (%s)","The SNMP MIB ISSU client could not be initialized. This initialization failure must be addressed before an in-service software upgrade or downgrade can be performed successfully. Otherwise, a software upgrade or downgrade will result in downtime.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SNMP_MIB_ISSU","2","SEND_NEGO_FAILED","SNMP MIB ISSU client failed to send negotiation message. Error: %d (%s)","The SNMP MIB ISSU client was unable to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"SNMP_MIB_ISSU","2","SESSION_NEGO","SNMP MIB ISSU client encountered unexpected client nego_done. Error: %d (%s)","An ISSU-compliant client transitions through a series of internal states. The SNMP MIB ISSU client encountered a client negotiation done state that was unexpected. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"SNMP_MIB_ISSU","2","SESSION_REGISTRY","SNMP MIB ISSU client failed to register session information. Error: %d (%s)","The SNMP MIB ISSU client was unable to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"SNMP_MIB_ISSU","3","CAP_INVALID_SIZE","SNMP MIB ISSU client capability list is empty.","The SNMP MIB ISSU client capability exchange list is empty, which is an invalid condition.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu capability entries commands and your pertinent troubleshooting logs."
"SNMP_MIB_ISSU","3","CAP_NOT_COMPATIBLE","SNMP MIB ISSU client capability exchange result incompatible.","Based on the results of the capability exchange, the SNMP MIB ISSU client is not compatible with the peer.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"SNMP_MIB_ISSU","3","INVALID_SESSION","SNMP MIB ISSU client does not have a valid registered session.","The SNMP MIB ISSU client does not have a valid registered session.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"SNMP_MIB_ISSU","3","MSG_NOT_OK","SNMP MIB ISSU client 'Message Type %d' is not compatible","The SNMP MIB ISSU client received an incompatible message from the peer device. The message cannot be processed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"SNMP_MIB_ISSU","3","MSG_SIZE","SNMP MIB ISSU client failed to get the MTU for Message Type %d. Error: %d (%s)","The SNMP MIB ISSU client was unable to calculate the MTU for the specified message. The SNMP MIB ISSU client is not able to send the message to the standby device.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"SNMP_MIB_ISSU","3","SESSION_UNREGISTRY","SNMP MIB ISSU client failed to unregister session information. Error: %d (%s)","The SNMP MIB ISSU client was unable to unregister session information.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"SNMP_MIB_ISSU","3","TRANSFORM_FAIL","SNMP MIB ISSU client %s transform failed for 'Message Type %d'. Error: %d (%s)","The SNMP MIB ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In either case, the SNMP MIB state between the active device and the standby device is not identical.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"SONET","3","APSCOMMCHANGE","[chars]: Link to [chars] channel reverts to PGP protocol version [dec]","APS has reverted to a different version of the PGP protocol between working and protect routers.","This is an informational message only. No action is required."
"SONET","3","APSEVENT","[chars]: APS event type error: event [dec] undefined","The APS software has malfunctioned.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SONET","3","APSHAHOLDTIME","[chars]: [chars]","The PGP hold time was adjusted.","This is an informational message only. No action is required."
"SONET","3","APSSYNCSECONDARY","[dec]/[dec]: No hwidb","A new secondary RP was unable to find a device descriptor block corresponding to slot and unit specified by primary the RP.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SONET","3","DELAYTIMER","[chars]","The system was unable to create a delay timer.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SONET","6","APSREFL","[chars]: Remote reflection of APS status now [chars]","The APS software has detected a change in the reflected local APS status.","This is an informational message only and occurs in normal operation. No action is required."
"SONET","6","APSREMSWI","[chars]: Remote APS status now [chars]","The APS software has detected a change in the APS status of the remote interface.","This is an informational message only and occurs in normal operation. No action is required."
"SONETMIB","1","UNAVAILABLE","Lost raw stats update for if_index=%d Error Message    %SONETMIB-1-UNAVAILABLE: Malloc failed for new interface=%d","Unable to allocate enough memory to create SONET MIB structure for new interface.","LOG_STD_NO_ACTION"
"SONETMIB","1","UNAVAILABLE","could not delete interface, if_index=%d","The specified interface was not successfully dequeued.","LOG_STD_NO_ACTION"
"SONETMIB","3","UNAVAILABLE","NULL SONET MIB config pointer, if_index=%d","Attempted to initialize the SONET MIB using a NULL pointer.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SONICT","1","UNAVAILABLE","msgtxt_initfail","There was a failure in the initialization sequence of the sonict chip.","Show cont e0/0/x. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SONICT","2","UNAVAILABLE","msgtxt_nomemory","An operation could not be accomplished because of a low-memory condition. The current system configuration, network environment, or possibly a software error might have exhausted or fragmented the system's memory.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a configuration that has more memory."
"SPA","0","TEMP_SHUTDOWN","[chars] temperature too high. ([dec]C) SPA has been shut down.","The SPA has been shut down.","Ensure that the temperature is normal in the area where the router is located and resolve any conditions, such as malfunctioning fans, that are causing a temperature increase."
"SPA","0","TEMP_SHUTDOWN_OVR","[chars] temperature too high ([dec]C) but shutdown has been overridden.","SPA shutdown has been overridden by the configuration.","Ensure that the temperature is normal in the area where the router is located and resolve any conditions, such as malfunctioning fans, that are causing a temperature increase."
"SPA","0","VOLT_SHUTDOWN","[chars] voltage out of operating range. Nominal ([dec]mV), value ([dec]mV). The SPA has been shut down.","The SPA has been shut down to prevent component damage.","Replace the SPA immediately. Record the associated messages and return the SPA for service."
"SPA","2","TEMP_CRITICAL","[chars] temperature too high. ([dec]C)","The SPA temperature is too high.","Ensure that the temperature is normal in the area where the router is located and resolve any conditions, such as malfunctioning fans, that are causing a temperature increase."
"SPA","2","VOLT_CRITICAL","[chars] voltage outside of nominal range. Nominal ([dec]mV), value([dec]mV)","One of the measured environmental test points exceeded the nominal voltage threshold. This condition could cause the system to fail to operate properly.Explanation    Correct the specified condition, or the system may shut itself down as a preventive measure. Enter the show environment all command to help determine if this problem is due to a voltage condition.Error Message    %SPA-2-VOLT_SHUTDOWN_OVR: [chars] voltage outside of operating range. Nominal ([dec]mV), value([dec]mV). SPA shutdown has been overridden by configuration. Explanation    One of the measured environmental test points exceeded the nominal voltage threshold. SPA shutdown has been overridden by the configuration.","Correct the specified condition. Enter the show environment all command to help determine if this problem is due to a voltage condition."
"SPA","3","BAD_FCITYPE","[chars]: Illegal FCI type [dec].","An invalid FCI type was passed to the SPA. This is a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA","3","ENVMON_INITFAIL","SPA environmental monitoring initialization error","A failure occurred during the SPA environmental monitoring subsystem startup. Environmental monitoring is not enabled.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"SPA","3","ENVMON_NOT_MONITORED","Environmental monitoring is not enabled for [chars]","The specified SPA has not registered any sensors with the environmental monitoring system.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA","3","RESOURCE_ERROR","[chars] ([hex], [hex], [hex], [hex]) [chars]","A required resource could not be allocated.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA","3","SOFTWARE_ERROR","[chars] ([hex], [hex], [hex], [hex]) [chars]","The specified software error has been detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA","4","TEMP_WARNING","[chars] temperature too high. ([dec]C)","The SPA temperature is too high.","Ensure that the temperature is normal in the area where the router is located and resolve any conditions, such as malfunctioning fans, that are causing a temperature increase."
"SPA","4","TEMP_WARNLOW","[chars] temperature too low. ([dec]C)","The SPA temperature too low. Component reliability and data integrity may be compromised.","Raise the ambient temperature if it is too low. If there is no issue with the ambient temperature, then the SPA temperature sensor has likely failed. If there are no data errors, this warning can be ignored."
"SPA_CCB","3","CMDFAIL_0ARG","[chars]: host command [dec] error: [chars].","A command from the host failed to execute for the specified reason.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CCB","3","CMDFAIL_1ARG","[chars]: host command [dec](arg0=[dec]) error: [chars].","A CCB command failed to execute for the specified reason.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CCB","3","CMDFAIL_2ARG","[chars]: host command [dec](arg0=[dec], arg1=[dec]) error: [chars].","A command from the host failed to execute for the specified reason.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CCB","3","CMDFAIL_3ARG","[chars]: host command [dec](arg0=[dec], arg1=[dec], arg2=[dec]) error: [chars].","A command from the host failed to execute for the specified reason.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CCB","3","CMD_TOOEARLY","[chars]: host command [dec] received before handler ready.","A host command was received before the handler was initialized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CCB","3","ENQUEUE_FAIL","[chars]: host command [dec] failed to enqueue.","An error occurred while the SPA console was attempting to enqueue a host command to the command queue.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CCB","3","IF_CONFIG","[chars]: IF_CONFIG type [dec] failed.","The specified interface configuration type is not valid for the SPA card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CCB","4","BADENCAP","[chars]: Unknown encapsulation command [dec].","An invalid encapsulation command was received by the SPA. This is a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOC_DSX","3","COR_MEM_ERR","SPA %d/%d: %d correctable %s memory error(s) encountered. The error has been corrected and normal processing should continue. The memory address of most the recent error is: %x","The SPA driver detected a correctable memory error on the SPA card.","The SPA has encountered a correctable memory error on the SPA card. The error has been corrected and normal processing should continue. The hexadecimal memory address of the most recent error is specified in the message text on the console or in the system log. If the condition persists, or other errors are indicated for the SPA, copy the error message exactly as it appears. Then power down and reseat the indicated SPA card. Next research and attempt to resolve the issue using the SPA hardware troubleshooting documentation as well as the tools and utilities provided at http://www.cisco.com/public/support/tac/tools.shtml. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact your Cisco technical support representative. Be sure to provide the the information you have gathered and a 'show tech-support' to your support representative, or attach it to your case in non-zipped, plain text format (.txt)."
"SPA_CHOCX","3","UNAVAILABLE","Failed to create %s : slot/bay:%d/%d","The CHOCX SPA controller descriptor block creation failed. Check the amount of system memory available..","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOCX","3","UNAVAILABLE","Fatal error for %s : slot/bay:%d/%d","The CHOCX SPA controller encounters a fatal error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOCX","3","UNAVAILABLE","Invalid SPA type : slot/bay:%d/%d, spa_type=%d.","The CHOCX SPA type cannot be recognized by the version of Cisco IOS software currently running on the system.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOCX","3","UNAVAILABLE","NULL %s","The NULL pointer was seen in when getting the datastructure.","This is a internal software error. Decode the traceback. Enable debug hw-module subslot / oir plugin when the problem is happening. Check Bug Toolkit before calling the TAC. When calling the TAC, please provide the aboveinformation along with output of show logging and the output of show tech details."
"SPA_CHOCX","3","UNAVAILABLE","Null %s instance for %s : slot/bay:%d/%d","The instance pointer is NULL when getting datastructure","This is a internal software error. Decode the traceback and get the output of show running-config. Check Bug Toolkit before calling the TAC. When calling the TAC, please provide the above information along with the output of show running and show tech details."
"SPA_CHOCX","3","UNAVAILABLE","Received unknown %s: option=%d","Unknown option received","This is a internal software error. Decode the traceback and get the output of show running-config. Check Bug Toolkit before calling the TAC. When calling the TAC, please provide the above information along with the output of show running and show tech details."
"SPA_CHOCX","3","UNAVAILABLE","Return error for %s: return_value=%d","Return error code received","This is a internal software error. Decode the traceback and get the output of show running-config. Check Bug Toolkit before calling the TAC. When calling the TAC, please provide the above information along with the output of show running and show tech details."
"SPA_CHOC_DSX","3","BAD_SIZE_ERR","SPA [dec]/[dec]: [dec] [chars] events on HDLC Controller were encountered.The SPA is being restarted.","The SPA driver detected an error event on the HDLC controller.","If the condition persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOC_DSX","3","COR_MEM_ERR","SPA [dec]/[dec]: [dec] correctable [chars] memory error(s) encountered.The error has been corrected and normal processing should continue.The memory address of most the recent error is: [hex]","The SPA driver detected a correctable memory error on the SPA card. The error has been corrected and normal processing should continue. The hexadecimal memory address of the most recent error is specified in the message text on the console or in the system log.","If the condition persists, or other errors are specified for the SPA, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOC_DSX","3","EFC_ERROR","EFC ERROR: [chars] - [chars] [int]","The SPA extended flow control (EFC) encountered an error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOC_DSX","3","HDLC_CTRL_ERR","SPA [dec]/[dec]: [dec] [chars] events on HDLC Controller were encountered.","The SPA driver detected an error event on the HDLC controller.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOC_DSX","3","INVALID_IF_TYPE","Invalid SPA type [dec] on [chars]. Port Number = [dec].","The software cannot recognize the interface type.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOC_DSX","3","INVLIAD_IF_INDEX","Invalid interface index [dec] on slot/bay:[dec]/[dec]. Min. Index = [dec]. MAx. Index = [dec].","The index is not valid for the specified interface.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOC_DSX","3","LINK_TABLE_ERR","[chars]: Could not create link table, error [dec]","An error occurred during the creation of the link record table. Interfaces may not come up or pass traffic.","If the ports on the SPA are not operating as expected, power down and reseat the specified SPA card. If the error messages persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOC_DSX","3","NODESTROYSUBBLOCK","The [chars] subblock named [chars] was not removed","IDB subblocks could not be removed during the unprovisioning of a channel. This condition indicates a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOC_DSX","3","NULL_DATA_STRUCTURE","Failed to create [chars] on slot/bay:[dec]/[dec]. Port Number = [dec].","The specified software resource cannot be allocated for this hardware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOC_DSX","3","NULL_SPA_PTR",',"The pointer to a SPA value is null.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOC_DSX","3","SEMAHOG","SPA on [chars]: Semaphore Hog was encountered.","The semaphore used by the IPC communication between host and the SPA was monopolized by one process. This behavior would cause other processes fail to send commands down to the SPA and might result in improper operation.","Stop all the traffic on the SPA, and then reload the configuration by entering shutdown and no shutdown commands on the controllers. If the problem persists, power cycle the SPA. If the condition persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOC_DSX","3","SPA_CMD_RETURN_ERR","SPA command [chars] return error [int]","The SPA returned an error status for a host command.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOC_DSX","3","SPA_CMD_SEND_ERR","Failed to send [chars] command to SPA","The host failed to send a command to the SPA.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOC_DSX","3","SPA_SW_ERR","SPA on [chars]: [chars] Software error was encountered.","The SPA driver detected a software error condition on the SPA card. This condition might cause improper operation.","Reload the configuration by entering shutdown and no shutdown commands on the controllers. If the problem persists, power cycle the SPA. If the condition persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOC_DSX","3","SPI4_HW_ERR","SPA on [chars]: [chars] Hardware error was encountered.","The SPA driver detected a hardware error condition on the SPA card's SPI4 bus. This condition might cause improper operation.","Power down and reseat the specified SPA card. If the condition persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOC_DSX","3","UNCOR_MEM_ERR","SPA [dec]/[dec]: [dec] uncorrectable [chars] memory error(s) encountered.The memory address of most the recent error is: [hex] The SPA is being restarted.","The SPA driver detected an uncorrectable memory error condition on the SPA card. Packet corruption may result. The hexadecimal memory address of the most recent error is specified in the message text on the console or in the system log.","Power down and reseat the specified SPA card. If the condition persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOC_DSX","3","UNCOR_PARITY_ERR","SPA [dec]/[dec]: [dec] [chars] parity error(s) encountered.","The SPA driver detected an uncorrectable parity error condition on the SPA card. Packet corruption may result.","Power down and reseat the specified SPA card. If the condition persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOC_DSX","3","UNKNOWN_CMD","Unknown [chars] command recieved on slot/bay:[dec]/[dec]. Command Type = [dec]","An unknown command was received by the SPA card carrier.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOC_DSX","4","UNPROV_FAIL","Interface [chars] unprovisioning failed: [chars]","The system failed to respond to an unprovisioning command. A hidden VLAN could not be deleted within a 2-second timeout window. This condition may be caused by a system that is too busy or by a FIB IPC failure. The line card driver code will attempt to delete the hidden VLAN.","If processing continues normally, no action is required. If system operation is adversely affected, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOC_DSX","3","VCCFG_ERROR","Interface [chars] config command error (cmd [int], arg [int], retval [int])","A command sent from the system to a line card has failed. This is an internal software error.","Decode the traceback and get the output of the show logging command on the RP and SIP-1 and check if there are any errors being reported. Try to recreate the problem to see if there is a consistent method to recreate. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs"
"SPA_CHOCX","3","NULL","NULL [chars]","The NULL pointer was seen when getting the data structure. This is an internal software error.","Decode the traceback. Enter the debug hw-module subslot slot/bay oir plugin command while the problem is happening. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOCX","3","CREATE_FAIL","Failed to create [chars] : slot/bay:[dec]/[dec]","The CHOCX SPA controller descriptor block creation failed.","Check the amount of system memory available. Upgrade your system to the latest version of Cisco IOS software. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOCX","3","FATAL_ERROR","Fatal error for [chars] : slot/bay:[dec]/[dec]","The CHOCX SPA controller encountered a fatal error.","Upgrade your system to the latest version of Cisco IOS software. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOCX","3","INVALID_SPA_TYPE","Invalid SPA type : slot/bay:[dec]/[dec], spa_type=[dec].","The CHOCX SPA type cannot be recognized by the version of Cisco IOS software currently running on the system.","Upgrade your system to the latest version of Cisco IOS software in your release train. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOCX","3","NULL_INSTANCE","Null [chars] instance for [chars] : slot/bay:[dec]/[dec]","The instance pointer is NULL when getting the data structure. This is an internal software error.","Decode the traceback and get the output of show running-config. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOCX","3","RETURN_ERROR","Return error for [chars]: return_value=[dec]","An error code was received. This is an internal software error.","Decode the traceback and get the output of show running-config. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOCX","3","UNKNOWN_OPTION","Received unknown [chars]: option=[dec]","An unknown option was received. This is an internal software error.","Decode the traceback and get the output of show running-config. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOCX_CWRP","1","ALLOCFAIL","OC3/STM1 [dec]/[dec] [chars] allocation failure","A memory allocation failure occurred in the CHOCX controller or channel. This is an internal software error.","Decode the traceback. Enter the debug hw-module subslot slot/bay oir plugin command while the problem is happening. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOCX_CWRP","3","APS_CMD_FAIL","Failed to send APS command [hex] to [chars] (retcode [hex])","An APS command send failed. This is an internal software error.","If this error happened while configuring APS, try reconfiguring the interface. If the error persists or occurred during normal operation, decode the traceback and 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOCX_CWRP","3","CORRUPT","Corrupt configuration, unsupported [chars] ([int]) encountered","The OC3/STM1 RP driver running configuration is corrupt.","Decode the traceback and get the output of show running-config. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOCX_CWRP","3","NULL_SUBBLOCK","Null ssb for [chars]","The hardware IDB subblock is NULL. This is an internal software error.","Decode the traceback and get the output of show running-config. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOCX_CWRP","3","PLUGIN_ERR","[chars]","The RP plugin encountered an error during a plugin call. This is an internal software error.","Decode the traceback. Enter the debug hw-module subslot slot/bay oir plugin command while the problem is happening. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOCX_CWRP","3","TIMEOUT","Interface ([chars]): [chars]","The line card did not reply to a query for SONET information from the CHOCX RP driver. This is an internal software error.","Decode the traceback. Enter the debug hw-module subslot slot/bay oir plugin command while the problem is happening. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOCX_CWRP","5","DEF_SUBRATE","[chars] [chars]","The remote subrate configuration has changed.","No action is required."
"SPA_CHOCX_CWRP","5","PATH_UPDOWN","Path [chars], changed state to [chars]","A SONET high-order path changed its state. This is an internal software error.","Decode the traceback and get the output of show controller sonet. Look into this output to see if there are any alarms being reported at the path level. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CHOCX_CWRP","5","T3_UPDOWN","T3 [chars], changed state to [chars]","A T3 within STS1 has changed its state. This is an internal software error.","Decode the traceback and get the output of show controller sonet. Look into this output to see if there are any alarms being reported at the path level. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CONSOLE","3","BADDETACH","SPA console session detach failed with IPC error [chars].","A failure occurred when attempting to detach SPA console subsystem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CONSOLE","3","INITFAIL","[chars]: SPA console initialization error: [chars].","A failure occurred during initialization of the SPA console subsystem. The SPA console may not be functioning.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CONSOLE","3","NOBUF","No packet buffer available for sending SPA console messages","An error occurred while the SPA console was attempting to acquire a packet buffer from the IPC buffer pool.","Copy the message exactly as it appears on the console or in the system log. Enter the show ipc status command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CONSOLE","3","NO_DRIVER","[chars]: VCON_SPACP: Driver not ready.","The SPA sent a message before the line card was fully initialized.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CONSOLE","3","RX_BUS_PARAM","[chars]: VCON_SPACP: Invalid SPA bus parameters.","There was an error receiving a message from the SPA.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CONSOLE","3","TX_BUS_PARAM","[chars]: VCON_SPACP: Invalid SPA bus parameters.","There was an error sending a message to the SPA.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CONSOLE","5","CANTGET","Cannot get spa client ipc port","The SPA virtual console subblock is not properly initialized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CONSOLE","5","CANTSEND","Cannot send SPA console messages.","An error occurred while a SPA console message was being sent through the IPC. This condition might result in a malfunction in the operation of the IPC.","Copy the message exactly as it appears on the console or in the system log. Enter the show ipc status command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CONSOLE","5","CANTSET","Cannot set spa client ipc port","The SPA virtual console subblock is not properly initialized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CONSOLE","5","QUEUEFULL","Queue holding SPA console messages is full current console packet will be dropped","An error occurred while the SPA console was queueing a packet for transmission. Some console data may be lost.","Copy the message exactly as it appears on the console or in the system log. Enter the show ipc status command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPACP","3","BUFFER","[chars]: Failed to allocate buffer for SPACP message.","Cannot allocate memory for an SPACP message.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPACP","3","CREATE","[chars]: SPA Bus Device creation failed.","Cannot allocate memory for the SPA bus structure.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPACP","3","INIT","[chars]: Failed to initialize SPACP. [chars].","SPACP messaging could not be initialized for the specified reason.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPACP","3","OPCODE","[chars]: SPACP opcode [hex] unknown.","An unexpected message was received from the SPA.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPACP","3","SEND","[chars]: Failed to send SPACP message.","Failed to send a message to the SPA.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CT3","3","INVALID_SPA_TYPE","Invalid SPA type : slot/bay:[dec]/[dec], SPA_type=[dec].","The CT3 SPA type cannot be recognized by the version of Cisco IOS software currently running on the system.","Upgrade the system to the latest version of Cisco IOS software in your release train. If you require further assistance, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CT3","3","PROCESS_FAIL","process creation failed for [chars]","A command could not be processed because of a process-creation failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_CT3","3","SUBRATE_FPGA_DL_FAILED","[chars]: Failed to download the subrate FPGA image.","The specified SPA was not able to download the subrate FPGA image during a card-initialization sequence. The image might be corrupted and the system will try to recover from this error by upgrading the image.","If the system cannot recover from this error automatically after a few attempts, it will power off the affected SPA. In that case, copy the message exactly as it appears on the console or in the system log. Enter the show hw-module subslot slot-number/subslot-number fpd and show hw-module subslot slot-number/subslot-number oir commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_DATABUS","3","PACKET_GAP_ERROR","[chars] [chars] - A packet gap error has occurred","The data bus interface on this line card is experiencing a hardware-related issue. No loss of data or data corruption should occur. Packets should continue to be forwarded because this error will occur only with a hardware failure.","If this error recurs, verify whether the failed hardware is the SIP or the SPA. Copy the message exactly as it appears on the console or in the system log. Enter the show hw-module slot-number/subslot-number errors spi4 command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_DATABUS","3","SPI4_BAD_CHAN_NUM","[chars] [chars] - An error condition on the SPA data bus has occurred.","An error condition on the SPA data bus has occurred. This condition can be caused by a software fault only.","Copy the message exactly as it appears on the console or in the system log. Enter the show hw-module slot-number/subslot-number errors spi4 command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_DATABUS","3","SPI4_BAD_CNTR_WORD","[chars] [chars] - An error condition on the data bus between the SPA and the SIP has occurred.","An error condition has occurred on the data bus between the SPA and the SIP. Symptoms of this error include data corruption or a short duration of data loss. In addition, the interface may lock up.","If this error recurs, verify whether the failed hardware is the SIP or the SPA. Copy the message exactly as it appears on the console or in the system log. Enter the show hw-module slot-number/subslot-number errors spi4 command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_DATABUS","3","SPI4_CALENDAR_LEN","[chars] [chars] - An error condition on the data bus between the SPA and the SIP has occurred.","An error condition on the data bus between the SPA and the SIP has occurred. This condition results from a software fault.","Copy the message exactly as it appears on the console or in the system log. Enter the show hw-module slot-number/subslot-number errors spi4 command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_DATABUS","3","SPI4_CRTL_WD_NO_DIP4","[chars] [chars] - An error condition on the data bus between the SPA and the SIP has occurred.","This message points to an error condition on the SPA data bus. Symptoms of this error include data corruption or a short duration of data loss.","If this error recurs, verify whether the failed hardware is the SIP or the SPA. Copy the message exactly as it appears on the console or in the system log. Enter the show hw-module slot-number/subslot-number errors spi4 command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_DATABUS","3","SPI4_FIFO_STATUS_BUS","[chars] [chars] - FIFO status bus out of frame condition has occurred.","The data bus interface on this line card is experiencing a hardware-related issue. When this condition is occurring, the interface will be down or may not forward any traffic. This error will occur only with a hardware failure.","If this error recurs, verify whether the failed hardware is the SIP or the SPA. If supported by the platform, try running diagnostics on the suspected hardware. Copy the message exactly as it appears on the console or in the system log. Enter the show hw-module slot-number/subslot-number errors spi4 command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_DATABUS","3","SPI4_OUT_OF_FRAME","[chars] [chars] - A data bus out of frame error condition has occurred","An error has occurred on the data bus between the SPA and the SIP. When this condition is occurring, the interface will be down or may not forward any traffic. This error will only occur with a hardware failure.","Power down and reseat the card. If this error recurs, verify whether the failed hardware is the SIP or the SPA. If supported by the platform, try running diagnostics on the suspected hardware. Copy the message exactly as it appears on the console or in the system log. Enter the show hw-module slot-number/subslot-number errors spi4 command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_DATABUS","3","SPI4_SEQUENCE","[chars] [chars] - A sequence error has occurred.","A sequence error has occurred on the data bus between the SPA and the SIP. When this condition is occurring, a short duration of packet loss may be noticed. This condition may indicate a developing hardware failure. This error should occur very infrequently during normal operation and should not occur when no changes are made to the configuration. This error will occur only with a hardware failure.","If this error recurs, verify whether the failed hardware is the SIP or the SPA. If supported by the platform, try running diagnostics on the suspected hardware. Copy the message exactly as it appears on the console or in the system log. Enter the show hw-module slot-number/subslot-number errors spi4 command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_DATABUS","3","SPI4_SINGLE_DIP2_PARITY","[chars] [chars] - A single DIP 2 parity error on the FIFO status bus has occurred.","The data bus interface on this line card is experiencing a hardware-related issue. Some packets may be dropped. This error will occur only with a hardware failure.","If this error recurs, verify whether the failed hardware is the SIP or the SPA. If supported by the platform, try running diagnostics on the suspected hardware. Copy the message exactly as it appears on the console or in the system log. Enter the show hw-module slot-number/subslot-number errors spi4 command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_DATABUS","3","SPI4_SINGLE_DIP4_PARITY","[chars] [chars] - A single DIP4 parity error has occurred on the data bus.","A single parity error has occurred on the data bus between the SPA and the SIP. When this condition is occurring, a short duration of packet loss or symptoms resulting from data corruption may occur. This condition may indicate a developing hardware failure. This error should occur very infrequently during normal operation and should not occur when no changes are made to the configuration.","Power down and reseat the card. If this error recurs, verify whether the failed hardware is the SIP or the SPA. If supported by the platform, try running diagnostics on the suspected hardware. Copy the message exactly as it appears on the console or in the system log. Enter the show hw-module slot-number/subslot-number errors spi4 command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_DATABUS","3","SPI4_SINK_FIFO_OVERFLOW","[chars] [chars] - An error condition on the data bus between the SPA and the SIP has occurred.","An error condition on the data bus between the SPA and the SIP has occurred. Possible causes include misconfiguration of maxburst parameters, incorrect FIFO sizing, or improper FIFO threshold settings.","Copy the message exactly as it appears on the console or in the system log. Enter the show hw-module slot-number/subslot-number errors spi4 command to gather data that may help identify the cause of the error. You may need to load a more recent version of the software. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_DATABUS","3","SPI4_SINK_FIFO_UNDERRUN","[chars] [chars] - An error condition on the data bus between the SPA and the SIP has occurred.","An error condition on the data bus between the SPA and the SIP has occurred. Possible causes include misconfiguration of maxburst parameters, incorrect FIFO sizing, or improper FIFO threshold settings.","Copy the message exactly as it appears on the console or in the system log. Enter the show hw-module slot-number/subslot-number errors spi4 command to gather data that may help identify the cause of the error. You may need to load a more recent version of the software. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_DATABUS","3","SPI4_UNALIGNED_BURST","[chars] [chars] - An error on the data bus has occurred.","Under normal conditions, the transitions from the data burst state to payload control or idle control are possible only on integer multiples of 8 cycles or upon the end of a packet. This error happens if the modelware (MW) bit flips on the bus with coincidental good 4-bit diagonal interleave parity (dip4) or due to a malfunctioning source.","Power down and reseat the card. If this error recurs, verify whether the failed hardware is the SIP or the SPA, because this error will occur only with a hardware failure. If supported by the platform, try running diagnostics on the suspected hardware. Copy the message exactly as it appears on the console or in the system log. Enter the show hw-module slot-number/subslot-number errors spi4 command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_EEPROM","3","FIELD_NOT_FOUND","[chars]: Failed to find content of field type [hex] with data size = [dec] bytes. The EEPROM might require an update.","The system failed to find the content of the specified field type from the SPA EEPROM. The format of the EEPROM of the specified SPA might not be up to date.","Retry the operation. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show idprom module slot-number/subslot-number dump command or the show diag subslot slot-number/subslot-number command (depending on the support of the platform) to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_EEPROM","3","FORMAT_ERROR","[chars]: [chars]. The EEPROM might require an update.","A format error has been detected in the EEPROM of the specified SPA. The type of error is specified in the message.","Retry the operation. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show idprom module slot-number/subslot-number dump command or the show diag subslot slot-number/subslot-number command (depending on the support of the platform) to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_EEPROM","3","READ_FAILED","Failed to read the EEPROM content of [chars] in [chars] (offset=[hex], num_byte=[int])","The system failed to read the EEPROM content of the specified SPA with the specified offset value and number of bytes to read.","Retry the operation. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show idprom module slot-number/subslot-number dump command or the show diag subslot slot-number/subslot-number command (depending on the support of the platform) to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_EEPROM","3","RPC_FAILED","Failed to send RPC message to [chars] EEPROM of [chars] in [chars] - [chars]","The system failed to send an RPC message to read or write the EEPROM of the specified SPA. The cause of the error condition is shown in the message.","Retry the operation. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_EEPROM","3","SET_WR_PROTECT_FAILED","[chars]: Failed to [chars] the EEPROM write protect mode on [chars].","The system failed to enable or disable the write protect mode for the SPA EEPROM on the specified device. This might happen if the device were busy performing other tasks.","Retry the operation. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show idprom module slot-number/subslot-number dump command or the show diag subslot slot-number/subslot-number command (depending on the support of the platform) to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_EEPROM","3","SW_ERROR","NULL","There is a problem in the internal software coding. This message should not be seen under normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_EEPROM","3","WRITE_FAILED","Failed to write the EEPROM content for [chars] in [chars] (offset=[hex], num_byte=[int])","The system failed to write data into the EEPROM of the specified SPA with the specified offset value and number of bytes to write.","Retry the operation. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show idprom module slot-number/subslot-number dump command or the show diag subslot slot-number/subslot-number command (depending on the support of the platform) to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_EEPROM","4","CANNOT_UPDATE","[chars]: EEPROM data cannot be updated at this moment because the SPA is not in service.","The EEPROM update operation cannot be performed because the specified SPA could have been in an out-of-service state, an admin down state, or is trying to get initialized.","Retry the operation when the SPA is in service. Check the operational status of the SPA with the show hw-module subslot slot-number/subslot-number oir command. If the SPA is shown to be in the out-of-service state, correct the specified problem before the retry to update EEPROM. If the state shown is admin down, reenable the SPA by entering the no hw-module subslot slot-number/subslot-number shutdown command."
"SPA_EEPROM","4","DATA_TRUNCATED","[chars]: Data will be truncated for field type [hex] - size ([int] bytes) too big for this field type ([int] bytes)","The provided data to be written into the specified field type of the SPA EEPROM is too big. The data will be truncated to fit into the allowed space.","Retry the operation with a data size that will fit into the specified size for the field type."
"SPA_ETHER","1","ALLOCFAIL","Subslot [dec]/[dec], [chars] allocation failure ([chars])","The router has failed to allocate sufficient memory for a software module on the Ethernet SPA located in the specified subslot. The error message indicates the modular services card slot, the SPA subslot, the SPA type and the name of the software module.","Perform an OIR of the SPA located in the specified subslot. Before removing the SPA, enter the hw-module subslot stop command. Remove the SPA, wait 5 seconds, and reinsert the SPA into the MSC. Enter the show memory summary command to attempt to determine the cause of the error. Reduce system activity to reduce memory demands. If conditions warrant, upgrade to a larger memory configuration. If you require further assistance, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_ETHER","3","HW_ERROR","Subslot [dec]/[dec], [chars] Hardware device error ([chars]) detected, reactivating the SPA","An internal hardware device error has occurred on the Ethernet SPA. The message text specifies the modular services card slot, the SPA subslot, the SPA type, and the name of the hardware device. The SPA has been deactivated and reactivated to resolve the problem. If the error occurs more than five times within an hour, no further attempts to reactivate the SPA will be made. This condition is most likely due to an unrecoverable hardware failure.","Perform an OIR operation of the SPA located in the specified subslot. Before removing the SPA, enter the hw-module subslot stop command. Remove the SPA, wait 5 seconds, and reinsert the SPA into the MSC. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show diag command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_ETHER","3","INITFAIL","Subslot [dec]/[dec], [chars] initialization failure ([chars])","Initialization of an internal device on the Ethernet SPA in the specified subslot has failed. The message text specifies the modular services card slot, the SPA subslot, the SPA type, and the name of the device that failed to initialize. The message also provides the interface name and other details about the error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_ETHER","3","INVALID_PORT","Subslot [dec]/[dec], [chars] Incorrect port number ([dec]) specified for SPA","An internal error has been encountered by the Ethernet software driver for the SPA. The message text specifies the modular services card slot, the SPA subslot, the SPA type, and the invalid interface port number. This condition is caused by a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_ETHER","3","SEND_MSG","Subslot [dec]/[dec], [chars] Failed to notify driver process about a line state change in one of the SPA interfaces","A state change has occurred on the line of one of the interface ports on the Ethernet SPA. The message text specifies the modular services card slot, the SPA subslot, and the SPA type. Information to identify the affected interface port on the SPA is not provided. The affected interface might not function properly.","Perform an OIR operation of the SPA located in the specified subslot. Before removing the SPA, enter the hw-module subslot stop command. Remove the SPA, wait 5 seconds, and reinsert the SPA into the MSC. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show diag command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_ETHER","3","SFP_EEPROM_READ_FAIL","[chars], [chars] initialization failure ([chars])","The pluggable transceiver module (SFP) on the Ethernet SPA could not be initialized because the EEPROM on the pluggable transceiver module (SFP) could not be read. The error message specifies the modular services card slot, the SPA subslot, the SPA port, the SPA type and the name of the device that failed to initialize.","Ensure that the pluggable transceiver module (SFP) is properly seated in the SPA port by reseating it. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_ETHER","3","SFP_SEC_FAIL","[chars], [chars] initialization failure ([chars])","The pluggable transceiver module (SFP) on the Ethernet SPA could not be initialized because it could not pass the SFP security check. The error message specifies the modular services card slot, the SPA subslot, the SPA port, the SPA type and the reason for the security check failure.","Try replacing the pluggable transceiver module (SFP) with a Cisco approved pluggable transceiver module (SFP). If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_ETHER","3","SPI4_NOT_IN_SYNC","Subslot [dec]/[dec], [chars] SPI4 internal interface is not synchronized with the modular services card for the SPA located in the specified subslot.","The SPI4 internal path between the modular services card and the SPA is not synchronized. The message text specifies the modular services card slot, the SPA subslot, and the SPA type. This error indicates that either the SPA is not properly inserted into the MSC or a hardware failure has occurred on the SPA.","Perform an OIR operation of the SPA located in the specified subslot. Before removing the SPA, enter the hw-module subslot stop command. Remove the SPA, wait 5 seconds, and reinsert the SPA into the MSC. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show diag command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_ETHER","3","TCAM_ACCESS_FAILURE","Subslot [dec]/[dec], [chars] Failure in accessing the TCAM device ([chars], status = [hex])","An attempt to access the TCAM device on the SPA has failed. The message text specifies the modular services card slot, the SPA subslot, and the SPA type. This condition indicates a hardware failure.","Perform an OIR operation of the SPA located in the specified subslot. Before removing the SPA, enter the hw-module subslot stop command. Remove the SPA, wait 5 seconds, and reinsert the SPA into the MSC. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show diag command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_ETHER","3","TCAM_INST_CREATE_FAIL","Subslot [dec]/[dec], [chars] Failed to create the TCAM management instance (status = [hex])","The SPA failed to create the internal data structures that are required to manage TCAM entries. The message text specifies the modular services card slot, the SPA subslot, and the SPA type. This condition indicates a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_ETHER","3","TCAM_MAC_DA_TABLE_ACCESS_FAILURE","Subslot [dec]/[dec], [chars] Failure in accessing the TCAM destination MAC address table ([chars])","The TCAM destination MAC address table for the SPA interface could not be accessed. The message text specifies the modular services card slot, the SPA subslot, the SPA type, and the affected interface number. This error indicates either a software error or a hardware failure.","Perform an OIR operation of the SPA located in the specified subslot. Before removing the SPA, enter the hw-module subslot stop command. Remove the SPA, wait 5 seconds, and reinsert the SPA into the MSC. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show diag command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_ETHER","3","TCAM_MAC_DA_TABLE_INVALID","Subslot [dec]/[dec], [chars] Destination MAC address filter table is invalid for interface [dec]","The internal data structure that is used by the SPA to manage the destination MAC address filtering for an interface port is invalid. The message text specifies the modular services card slot, the SPA subslot, the SPA type, and the interface port. This condition indicates a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_ETHER","3","TCAM_VLAN_TABLE_ACCESS_FAILURE","Subslot [dec]/[dec], [chars] Failure in accessing the TCAM VLAN address table ([chars])","An attempt to access the TCAM VLAN table for the SPA has failed. The message text specifies the modular services card slot, the SPA subslot, the SPA type, and the affected interface. This condition indicates either a software error or a hardware failure.","Perform an OIR operation of the SPA located in the specified subslot. Before removing the SPA, enter the hw-module subslot stop command. Remove the SPA, wait 5 seconds, and reinsert the SPA into the MSC. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show diag command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_ETHER","3","TCAM_VLAN_TABLE_INVALID","Subslot [dec]/[dec], [chars] VLAN filter table is invalid for interface [dec]","The internal data structure used by the SPA to manage the VLAN filtering is invalid. The SPA supports a separate VLAN table for each interface. The message text specifies the modular services card slot, the SPA subslot, the SPA type, and the affected interface. This condition indicates a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_ETHER","4","BAY_NOT_FOUND","Subslot [dec]/[dec], [chars] Failed to get the bay information","A software data structure could not be retrieved for the subslot. The message text specifies the modular services card slot, the affected subslot, and the SPA type. This condition indicates a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_ETHER","4","NOPROCESS","Subslot [dec]/[dec], [chars] creation of [chars] process failed","A software process to manage the SPA could not be created. The message text specifies the modular services card slot, the SPA subslot, the SPA type, and the name of the process. This error message will be accompanied by a Cisco IOS software error message that gives more information about the cause for this failure.","Enter the show memory summary command to attempt to determine the cause of the error. Reduce system activity to reduce memory demands. If conditions warrant, upgrade to a larger memory configuration. If you require further assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_ETHER","4","TCAM_MAC_DA_TABLE_FULL","Subslot [dec]/[dec], [chars] Destination MAC address filter table is full for interface [dec], MAC address = [enet], mask = [enet]","The TCAM destination MAC address table for an interface on the SPA is full. The SPA supports a separate MAC table for each interface. The message text specifies the modular services card slot, the SPA subslot, the SPA type, the affected interface, and the MAC address. The specified MAC address will not be added to the TCAM table.","Attempt to remove some of the registered MAC addresses for the interface by changing the interface configuration. To verify the MAC addresses currently in use by an interface, enter the show controllers command."
"SPA_ETHER","4","TCAM_VLAN_TABLE_FULL","Subslot [dec]/[dec], [chars] VLAN filter table is full for interface [dec], VLAN identifier = [dec]","The TCAM VLAN filter table for an interface on the SPA is full. The SPA supports a separate MAC table for each interface. The message text specifies the modular services card slot, the SPA subslot, the SPA type, the affected interface, and the VLAN entry that failed. The specified VLAN identifier will not be added to the TCAM table.","Attempt to remove some of the registered VLANs for the interface by changing the interface configuration. To verify the VLAN IDs currently in use by an interface, enter the show controllers command."
"SPA_ETHER","4","TEMPERATURE_READ_FAIL","Subslot [dec]/[dec], [chars] Failed to read current temperature from sensor [dec], (status = [hex])","The current temperature reading on the SPA cannot be determined. The message text specifies the modular services card slot, the SPA subslot, and the SPA type. This condition indicates a hardware failure.","Perform an OIR operation of the SPA located in the specified subslot. Before removing the SPA, enter the hw-module subslot stop command. Remove the SPA, wait 5 seconds, and reinsert the SPA into the MSC. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show diag command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_ETHER","4","VOLTAGE_READ_FAIL","Subslot [dec]/[dec], [chars] Failed to read the current voltage for [chars] supply","The current voltage reading for the SPA voltage supply cannot be determined. The error message indicates the modular services card slot, the SPA subslot, the SPA type and the identification of the voltage supply. This error indicates a hardware failure.","Perform an OIR operation of the SPA located in the specified subslot. Before removing the SPA, enter the hw-module subslot stop command. Remove the SPA, wait 5 seconds, and reinsert the SPA into the MSC. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show diag command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_ETHER","6","TCAM_VLAN_FILTERING_DISABLED","Subslot [dec]/[dec], [chars] TCAM VLAN filter table is full, disabling VLAN filtering for interface [dec]","VLAN filtering for the specified interface has been disabled because the VLAN table is full. This means that the SPA will transmit frames destined for any VLAN ID to the route processor. The SPA supports a separate VLAN table per interface. The error message indicates the modular services card slot, the SPA subslot, the SPA type, and the affected interface.","To verify the VLAN IDs that are currently in use by an interface, enter the show controllers command. You can remove some of the existing VLANs from the interface configuration to reactivate VLAN filtering on the indicated interface."
"SPA_ETHER","6","TCAM_VLAN_FILTERING_ENABLED","Subslot [dec]/[dec], [chars] Enabling VLAN filtering for interface [dec]","VLAN filtering for the specified interface is enabled. The SPA supports a separate VLAN table per interface. The error message indicates the modular services card slot, the SPA subslot, the SPA type, and the affected interface.","VLAN filtering has been reactivated, and the VLAN table is no longer full. This means that the SPA will transmit frames to the route processor only for those VLAN IDs configured on the specified interface.To verify the VLAN IDs that are currently in use by an interface, enter the show controllers command."
"SPA_FPD","2","PWR_NO_OK","SPA POWER OK signal is not asserted for [chars] in [chars] for FPD upgrade.","A check for the SPA POWER OK signal assertion failed. This might indicate a hardware problem with the SPA.","Contact your Cisco technical support representative to have the SPA replaced."
"SPA_FPD","3","GETVER_FAILED","Failed to get FPD version for SPA in subslot [dec]: [chars].","Failed to get a field-programmable device (FPD) version due to either an IPC problem or an operation error. The card will be disabled.","Check the SPA seating and the SPA status. Ensure compatibility among FPD, Cisco IOS, and possible SPA firmware by comparing the output of the show hw-module subslot fpd command with Cisco IOS release notes. Obtain the Cisco IOS version by entering the show version command."
"SPA_FPD","3","JTAG_ERR","[chars]: Failed to program a [chars] FPD image file. Error code [hex].","An error occurred while attempting to program a SPA FPGA using the JTAG bus. It could be caused by an outdated carrier card FPGA or SPA connection, or it may also result from an internal software error.","Reseat the SPA and retry the upgrade. Verify that the carrier card FPGA is current. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_FPD","3","PWR_OFF_FAILED","Failed to power-off [chars] in [chars] for FPD offline upgrade within [dec] seconds.","The power-off operation of the indicated SPA failed within the number of specified seconds. This might indicate that the waiting time for the SPA to power off is not long enough, which can happen if the SPA has many interfaces configured.","Retry the upgrade operation again later. If the problem persists, remove the configuration of the SPA before retrying the upgrade operation."
"SPA_FPD","3","SMM665_CONF_WRITE_ERROR","[chars]: Failed to write new configuration into SMM665 device.","An error occurred while attempting to write to the SMM665 through the Cisco 2-wire (C2W) serial interface from the SPA carrier card. The C2W serial interface may be busy.","Retry the upgrade operation again later. If the problem persists, remove the configuration of the SPA before retrying the upgrade operation."
"SPA_FPD","3","SW_ERROR","NULL","This is an internal software error, which should not be seen under normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_FPD","3","UPGRADE_FAILED","Failed to upgrade FPD for SPA in subslot [dec], [chars].","The FPD image upgrade operation has failed. This error is specific to the SPA. The cause could be a wrong image file, an error in accessing FPGA storage, or a physical interrupt, such as a power failure or card removal. Depending on the SPA type and error cause, the card could be in an unusable status. Normally the system automatically reattempts the upgrade and shuts down the card after repeated failures.","Do not interrupt the system while an FPD upgrade is in progress. Obtain the matching FPD package. Refer to the Cisco IOS release notes for more information on obtaining the correct FPD package for the SPA. Review the output of the RP FPD logs."
"SPA_HA","3","BADSWITCHOVER","[chars]: Invalid HA event detected: [chars]","An HA switchover event occurred before initialization was finished.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_IPSEC","3","BOOT_FAIL","[chars]: [chars].","The SPA failed to boot up for the specified reason.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_IPSEC","3","BRDTYPE","Incorrect jacket card board type [dec] detected.","The detected SIP/SSC module type is not a C7600-SSC-400 or C7600-SSC-600.","Install the module carrier type that supports your SPA."
"SPA_IPSEC","3","OVERRIDE","[chars]: Overriding bundled firmware with ssc[int]-[chars].","The specified file was used instead of a bundled file. This is a debugging feature.","This is an informational message only. No action is required."
"SPA_IPSEC","3","PROC_FAIL","[chars]: [chars] Process creation failed.","Cannot allocate memory for the specified process.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_IPSEC","3","PWRCYCLE","SPA ([dec]/[dec]) is being power-cycled (Module not responding to keep-alive polling).","The SPA has stopped responding to keepalive polling from the carrier card. The SPA has been power-cycled.","Once the SPA is back on line, retrieve the crash dump data that was saved on the bootflash of the supervisor engine. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_IPSEC","3","QUACK","%s: Skipping quack authentication for hw ver %d.%d.","Quack authentication was not performed for some prototype boards.","No action is required."
"SPA_IPSEC","3","SKIP_SPI","%s: Skipping SPI Init.","SPI initialization will not be performed. This is a debugging feature.","No action is required."
"SPA_IPSEC","3","SPA_BUS","%s: SPA Bus timeout.","A timeout occurred while trying to access the SPA.","Reseat the board and try again. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","2","ACE_PKA_KAT_FAILURE","PKA: Known Answer Test failure: [chars]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_IPSEC_2G","2","ACEIKEADRVPKRM","Decode of RSA Private Key [dec] failed","Data error in PKI certificate.","Verify certificate server for proper operation."
"SPA_IPSEC_2G","2","ACEIKEAPRVCREDRV","Driver refused RSA Private Key","Attempt to create too many PKI sessions on SPA.","Reduce system load."
"SPA_IPSEC_2G","2","ACEIKEAPRVDRV","Driver refused RSA Private Key","Attempt to create too many PKI sessions on SPA.","Reduce system load."
"SPA_IPSEC_2G","2","ACEIKEAPRVRMDRV","Decode of RSA Private Key [dec] failed","Data error in PKI certificate.","Verify certificate server for proper operation."
"SPA_IPSEC_2G","2","ACENVRAMCSUM","NVRAM Checksum failed","Error reported by firmware.","Contact TAC."
"SPA_IPSEC_2G","2","ACENVRAMWR","Write to nvram failed","Error reported by firmware.","Contact TAC."
"SPA-IPSEC-2G","2","ACESCPERROR","Null MAC address pointer in SCP module","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_IPSEC_2G","3","ACEI0BADPARAM","PcpManCreateTunn: cannot create tunnel with expiring Sa","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, contact TAC with the output of show tech-support command ."
"SPA-IPSEC-2G","3","ACEI0TCAMFAILED","SpdSpInstall: cannot install Sp [dec]: TmInsertSp failed","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI1BADPARAM","SpdSpInstall: cannot install generic SP [dec] with non-zero priority","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI1OUTOFSA","PcpQOpCreSaBegin: cannot create new Sa using SpdMan","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_IPSEC_2G","3","ACEI10OUTOFCME","PcpManCreateAcl: cannot allocate new Acl for aclId=[int]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_IPSEC_2G","3","ACEI11NESTOVERFLOW","SpdSaAddTmInsCb: cannot have more than [dec] pending nested callbacks from TcamMan","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI11OUTOFSEL","PcpAclGetSpSelSet: cannot clone SelSet for ACL [dec]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI2BADPARAM","PcpManUpdateFlow: cannot update flow [dec] with invalid ID","Configuration not downloaded correctly.","Can safely ignore."
"SPA-IPSEC-2G","3","ACEI12IDNOTINUSE","PcpManRemoveAcl: cannot remove non-existing access list [int]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI12OUTOFSAPAR","SpdSaSetKeys: cannot allocate new SaPar for Sa [dec]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI13IDINUSE","PcpManRemoveAcl: cannot remove access list [int] while in use","An error has been reported by the firmware.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI3OUTOFSEL","PcpQOpActSaBegin: cannot allocate selector set for outer Sa in flowId [dec]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI14BADCMEID","PcpSpdCreateCme: cannot create Cme with ID=[dec]: too large","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI14NOLOGA","SpdSaSetParams: cannot allocate SPI with TcamMan for Sa [dec]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI15IDNOTINUSE","PcpManRemoveCme: cannot remove non-existing Cme [int]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI16BADPARAM","PcpManActivateFlowAsync: cannot activate flow [dec]: Sa is in the wrong state","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI16TCAMFAILED","SpdSaTmInstallIn: cannot install inbound Sa [dec] with TcamMan","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI17BADPARAM","PcpManActivateFlowAsync: cannot activate non-existing flow [dec]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI17TCAMFAILED","SpdSaTmInstallOut: cannot install outbound Sa [dec] with TcamMan","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI18BADPARAM","PcpManCreateSMap: cannot create outbound SPD Map [int] with ingress access list [int]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI19BADCMEID","PcpManActivateFlowAsync: cannot activate flow [dec] with non-existing Cme [dec]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_IPSEC_2G","3","ACEI1BADPARAM","SpdSpInstall: cannot install generic SP [dec] with non-zero priority","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI2BADPARAM","PcpManUpdateFlow: cannot update flow [dec] with invalid ID","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_IPSEC_2G","3","ACEI1OUTOFSA","PcpQOpCreSaBegin: cannot create new Sa using SpdMan","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_IPSEC_2G","3","ACEI20OUTOFSEL","PcpUtilSelSetFromPar: cannot allocate new selector set","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_IPSEC_2G","3","ACEI26OUTOFSP","PcpCmeInstallNext: cannot create a new Sp","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_IPSEC_2G","3","ACEI27BADPARAM","PcpManSetFlowKeys: cannot set keys for flow [dec]: SA is in the wrong state","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI2NESTOVERFLOW","SpdSaInitTmSaOut: outer outbound Sa [dec] of Sa [dec] is above nesting limit of [dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI20OUTOFSEL","PcpUtilSelSetFromPar: cannot allocate new selector set","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI21BADPARAM","PcpAclAppend: got too many denys for aclId=[dec], max is [dec]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI22BADPARAM","PcpAclAppend: got out-of-sequence line number [dec] for aclId=[dec]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI23IDINUSE","PcpSpdCreateCme: cannot create Cme with ID=[int]: already used","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI24BADPARAM","PcpAclAppend: got invalid ranges for selector set at lineNo=[dec], aclId=[dec]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI25IDINUSE","PcpAclAppend: got duplicate line number [dec] for aclId=[dec]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI26OUTOFSP","PcpCmeInstallNext: cannot create a new Sp","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI27BADPARAM","PcpManSetFlowKeys: cannot set keys for flow [dec]: SA is in the wrong state","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI28IDINUSE","PcpQOpCreSaBegin: cannot create second Sa for flow [dec]: conditions for transport adj. are not met","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI29SPDFAILED","PcpCmeInstallNext: cannot install Sp [dec] with SpdMan","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI3NESTOVERFLOW","SpdSaGetXformSeq: outer inbound Sa [dec] of Sa [dec] is above nesting limit of [dec]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI3OUTOFSEL","PcpQOpActSaBegin: cannot allocate selector set for outer Sa in flowId [dec]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI30BADPARAM","PcpSpdUpdateCme: cannot update already queued Cme [int]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI31BADALENUM","PcpQOpActSaBegin: cannot find access list entry number [dec] for cmeId=[dec]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI32BADPARAM","PcpQOpActSaBegin: cannot delete old [chars]bound flow [dec] while activating [chars]bound flow [dec]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI33BADPARAM","PcpCmeActivateSa: got invalid lifetime values softSecs=[int], hardSecs=[int]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI34BADPARAM","PcpCmeActivateSa: got invalid lifetime values softKBytes=[int], hardKBytes=[int]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI35BADPARAM","PcpCmeIntersectSaWithSp: cannot activate flow [dec] with selector ranges not intersecting parent Sp","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI36BADSELADDR","PcpQOpActSaBegin: cannot activate per-host flow [dec] with addresses [dec].[dec].[dec].[dec] and [dec].[dec].[dec].[dec] not included in Sp [dec] selector sets","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI37OUTOFSEL","PcpQOpActSaBegin: cannot clone selector set to activate per-host flow [dec]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI38BADSELADDR","PcpQOpActSaBegin: cannot activate transport mode flow [dec] with addresses [dec].[dec].[dec].[dec] and [dec].[dec].[dec].[dec] not included in Sp's selector sets","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI39BADPARAM","PcpTrInProcess: got invalid opcode [dec]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI4BADPARAM","PcpQOpCreSaBegin: got invalid addresses [int].[int].[int].[int] and [int].[int].[int].[int] for other Sa of flow [dec]: expected [int].[int].[int].[int] and [int].[int].[int].[int]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI40BADACLID","PcpManCreateCme: cannot create Cme with non-existing access list [int]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI41SPDFAILED","PcpQOpSaActivated: cannot finish activating Sa [dec]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI42QUEUEFULL","PcpCmeActivateSa: cannot activate Sa [dec]: queue is full","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI43BADPARAM","PcpAclAppend: got invalid line number [dec] for ACL [dec]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI44QUEUEFULL","PcpSpdCreateCme: cannot create Cme [int] (aclId=[int]): queue is full","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI45IDNOTINUSE","PcpManDestroyFlowAsync: cannot delete already deleted flow [dec]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI46BADPARAM","PcpQOpActSaBegin: cannot activate non-fully-specified Sa for Cme [dec] without Acl","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI47BADPARAM","PcpQOpActSaBegin: cannot activate Sa for manual Sp (cmeId=[dec],entry=[dec]), Sa already exists","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI48CMEINUSE","PcpManSetInitMode: cannot set fast init-mode in TcamMan: [dec] pending Ops, [dec] Flows and [int] Cmes already exist or TcamMan is busy","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI49BADPARAM","PcpManQueryFlow: cannot query flow [dec]: Sa is not active","Configuration not downloaded correctly.","Can safely ignore."
"SPA-IPSEC-2G","3","ACEI5BADPARAM","SpdSaActivate: cannot activate Sa [dec], old Sa [dec] already has successor Sa [dec]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI5OUTOFSA","PcpQOpCreSaBegin: cannot create new Sa for flow [dec]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI50CMEINUSE","PcpQOpRemCmeBegin: cannot remove Cme [dec]: TcamMan is in Init mode","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI51BADPARAM","PcpSpdCreateCme: got invalid flags (manual,dynamic,discover,drop,clear) = ([dec],[dec],[dec],[dec],[dec]), cmeId=[dec]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI52IDINUSE","PcpManCreateAcl: cannot process opcode [int] for Acl [int] in state [int]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI53BADPARAM","PcpManCreateAcl: cannot create Acl with id [int] out of range [0,[int]]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI54CMENOTREADY","PcpSpdCreateCme: cannot create Cme [int] with Acl [int] when Acl state is [int]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI55SPDFAILED","PcpQOpActSaBegin: cannot begin activating Sa [dec] for flowId [dec]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI56IDNOTINUSE","PcpManDestroyFlowAsync: cannot delete flow [dec] already being deleted","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI57CMEINUSE","PcpManSetInitMode: cannot set normal init-mode in TcamMan: there are pending Flows or Cmes","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI58IDNOTINUSE","PcpManDestroyFlowAsync: flow [dec] already queued for deletion","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI59BADPARAM","PcpCmeActivateSa: cannot activate flow [dec] as per-host with subset of Sp as a selector set","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI6BADPARAM","PcpTrInProcess: got invalid size [dec] for opcode [dec]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI6OUTOFSEL","SpdSpInstall: cannot compute SP's permit-SelSets from mixed SelSet list","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI60SPDFAILED","PcpManSaUpdateError: cannot update Flow [dec]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI61BADPARAM","PcpQOpActSaBegin: cannot activate Sa for cmeId=[dec], entry=[dec] with bad spdId=[dec]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI62IDINUSE","PcpQOpCreSaBegin: cannot setup Flow [dec] in trans.adj. with outer SA in tunnel mode","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI63CMEINUSE","PcpManActivateFlowAsync: cannot activate flow [dec] while using fast policy mode","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI64BADPARAM","PcpQOpActSaBegin: got invalid ranges for selector set of fully-specified flow [dec]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI65BADPARAM","PcpManSetInitMode: got invalid flags [hex] for setting fast policy mode","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI66NOTREADY","PcpManUpdateFlow: cannot update flow [dec] when SA is not active","Configuration not downloaded correctly.","Can ignore safely."
"SPA-IPSEC-2G","3","ACEI67BADPARAM","PcpSpdCreateSMap: cannot create SMap [int] with Acl [int] when Acl state is [int]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI68BADPARAM","PcpAclAppend: got invalid flags [hex] at lineNo=[dec], aclId=[dec]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI69BADPARAM","PcpManCreateCme: cannot create Cme [int] with spdId [int] out of range [0,[int]]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI7BADPARAM","PcpManSetFlowKeys: cannot set keys for flow [dec]: invalid ID","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI7OUTOFSEL","SpdSaTmInstallOut: cannot compute outbound SA's permit-SelSets from mixed SelSet list","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI70IDNOTINUSE","PcpManUpdateCme: cannot update non-existing Cme [int]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI71QUEUEFULL","PcpSpdUpdateCme: cannot update Cme [int]: queue is full","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI72QUEUEFULL","PcpSpdCreateSMap: cannot create SPD map with mapId [int]: queue is full","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI73BADPARAM","PcpSpdCreateSMap: cannot create SPD map with mapId [int] out of range [0,[int]]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI74IDINUSE","PcpSpdCreateSMap: cannot create SPD map with mapId [int] already in use","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI75TMFAILED","PcpSMapInstall: cannot insert SMap [int] with TcamMan","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI76BADPARAM","PcpSpdCreateSMap: cannot create SPD map [int] with invalid flags [hex]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI77BADPARAM","PcpManCreateSMap: cannot create SPD Map [int] using non-existent access list [int]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI78OUTOFSMAP","PcpSpdCreateSMap: cannot create SPD map [int]: out of memory","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI79BADPARAM","PcpQOpActSaBegin: cannot activate Sa for cmeId=[dec], entry=[dec] when Cme is not ready","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI80QUEUEFULL","PcpManDestroyFlowAsync: cannot delete flowId [dec]: operation queue is full","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI81IDNOTINUSE","PcpQOpDelSaBegin: cannot delete already deleted flow [dec]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI82QUEUEFULL","PcpManRemoveCme: cannot remove Cme with cmeId [int]: queue is full","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI83TMFAILED","PcpSpdInitialize: cannot insert SPD [int] with TcamMan","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI84BADPARAM","PcpManCreateSMap: cannot create SPD map [int] with spdId [int] out of range [0,[int]]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI85OUTOFSMAP","PcpManCreateSpd: cannot create SPD [int]: out of memory","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI86IDINUSE","PcpManActivateFlowAsync: cannot activate already active flow [dec]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI87BADPARAM","PcpManCreateFlow: cannot create Flow with id=[dec], max is [dec]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI88IDNOTINUSE","PcpManRemoveSMap: cannot remove non-existing SMap [int]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI89OUTOFCME","PcpSpdCreateCme: cannot allocate new Cme for aclId=[int]","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","3","ACEI92QUEUEFULL","PcpManCreateFlow: cannot create flowId [dec]: operation queue is full","Configuration not downloaded correctly.","Remove and reapply crypto map. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_IPSEC_2G","3","ACEIKEADELCB","[chars]:[dec]: unexpected ([dec]) error on delete callback","Probable software bug.","Contact TAC."
"SPA_IPSEC_2G","3","ACEPKARSAPRVXCR","PKA: PkaRsaPrivXcrypt() invalid input buffer length [dec]","Data error in PKI certificate.","Verify certificate server for proper operation."
"SPA_IPSEC_2G","3","ACEPKARSAPUBXCRBUFLEN","PKA: PkaRsaPubXcrypt() invalid input buffer length [dec]","Data error in PKI certificate.","Verify certificate server for proper operation."
"SPA_IPSEC_2G","3","ACEPKASK0LENCROP2","PKA: 0 length crypto operation","Data error in PKI certificate.","Verify certificate server for proper operation."
"SPA_IPSEC_2G","3","ACEPKASK0LENCRYOP3","PKA: 0 length crypto operation","Data error in PKI certificate.","Verify certificate server for proper operation."
"SPA_IPSEC_2G","3","ACEPKASK0LENOP","PKA: 0 length crypto operation","Data error in PKI certificate.","Verify certificate server for proper operation."
"SPA_IPSEC_2G","3","ACEPKASK1STFRAGSHRT","PKA: 1st frag too short for crypto operation","Data error in PKI certificate.","Verify certificate server for proper operation."
"SPA_IPSEC_2G","3","ACEPKASKDESNOTMUL82","PKA: DES/3DES data length not multiple of 8","Data error in PKI certificate.","Verify certificate server for proper operation."
"SPA_IPSEC_2G","3","ACEPKASKDESNOTMULT8","PKA: DES/3DES data length not multiple of 8","Data error in PKI certificate.","Verify certificate server for proper operation."
"SPA_IPSEC_2G","3","ICPUBADGRESA","Invalid GRE SA - can't find match. saptr:[hex]","Error reported by firmware.","Contact TAC with output from the show pcp sas command."
"SPA_IPSEC_2G","4","ICPUPP3","Illegal pkt dst:[dec].[dec].[dec].[dec] proto:[dec] spi:[hex], no match on SA SPI [hex].","Auditable event.","To see the details, enter the show crypto ipsec sas command."
"SPA-IPSEC-2G","3","SPI_NOT_AVAIL","SPI [hex] is not available","Crypto connect config could not be programmed correctly.","Remove and reapply crypto connect commands. If the failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_IPSEC_2G","4","ACEIPCMPINGPRE","IPC ping ([chars]): premature ping...awaiting response to previous ping","Error reported by firmware.","Contact TAC."
"SPA_IPSEC_2G","4","ACEIPCMPINGSEQ","IPC ping ([char]CPU): seq.# does not match: Expected [dec], got [dec]","Error reported by firmware.","Contact TAC."
"SPA_IPSEC_2G","4","ACEIPCMPINGSKIP","IPC ping ([char]CPU): Skipped [dec] times before receiving reply","Error reported by firmware.","Contact TAC."
"SPA_IPSEC_2G","4","ACEIPCXNOBUF2","ICPU unable to allocate msg buf for Ping Reply: [dec]","Error reported by firmware.","Contact TAC."
"SPA_IPSEC_2G","4","ACEIPCXNOBUF3","OCPU unable to allocate msg buf for Ping Reply: [dec]","Error reported by firmware.","Contact TAC."
"SPA_IPSEC_2G","4","ACEIPCXPINGNOBUF","[dec] srcCPU unable to allocate msg buf for Ping Reply in CB: [dec]","Error reported by firmware.","Contact TAC."
"SPA-IPSEC-2G","4","ACETCAMFULLINSMANSP","Full SA insertion for a manual SP.","Configuration not downloaded correctly.","Remove and reapply the crypto map. If failure persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","4","ACETCAMPKTNOSA","Packet event for a non-existing SA.","Configuration not downloaded correctly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","4","ACETCAMPKTNOSP","Packet event for a non-existing SP.","Configuration not downloaded correctly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_IPSEC_2G","4","ACETCAMPKTNOSP1","EarlyPkt Exit1.","Configuration not downloaded correctly.","Remove and reapply the crypto map. If failure persists, contact TAC with the output of the show tech-support command."
"SPA_IPSEC_2G","4","ACETCAMPKTNOSP2","EarlyPkt Exit2.","Configuration not downloaded correctly.","Remove and reapply the crypto map. If failure persists, contact TAC with the output of the show tech-support command."
"SPA_IPSEC_2G","4","ACETCAMPKTNOSP3","EarlyPkt Exit3.","Configuration not downloaded correctly.","Remove and reapply the crypto map. If failure persists, contact TAC with the output of the show tech-support command."
"SPA-IPSEC-2G","4","ACEXCPUALLOC","IPC: Unable to allocate and send STATFLUSH.","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_IPSEC_2G","4","ACEXCPUALLOC","IPC: Unable to allocate and send STATFLUSH.","Error reported by firmware.","Transient error. No action."
"SPA_IPSEC_2G","4","ACEXCPUALLOC2","IPC: Unable to allocate IPC to set debug flag.","Error reported by firmware.","Transient error. No action."
"SPA_IPSEC_2G","4","ACEXCPUALLOC3","IPC: Unable to allocate IPC to start 5840 test.","Error reported by firmware.","If persistent, restart VPNSPA."
"SPA-IPSEC-2G","4","ACEXCPUCMMTU2","CFGMON: Failed to set MTU. Invalid data [dec], ifvlan [hex].","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","4","ACEXCPUCMRESP","XcpuCfgMonReqCallback:Can't respond to host.","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","4","ACEXCPUCMRESP3","XcpuCfgMonReqCallback:Global stats...Can't respond to host.","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","4","ACEXCPUCMRESP4","XcpuCfgMonReqCallback: PerFlow Stats....Can't respond to host.","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","4","ACEXCPUCMRESP5","XcpuCfgMonReqCallback: PerFlow Stats....Can't respond to host.","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_IPSEC_2G","4","ANTIREPLAYWINDOWDEFAULT","Using default replay window for SA SPI [hex]","Unable to allocate more than 8K extended replay windows.","New SAs will use the default window size if no resource is available."
"SPA_IPSEC_2G","4","BULKIP","Wrong type [dec] size:5d.","System IP address not downloaded correctly.","Remove and reapply the IP address on the interfaces, and if the problem persists, contact TAC."
"SPA-IPSEC-2G","4","DUMPMEM","[hex]: [hex] [hex] [hex] [hex]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","4","EDSDEBUG","SingleBufErr:([hex])","Multibuffer packet received during FIPS test.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","4","FIPSCHECK2","FIPS RCVD Multi-buffer Packet.","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","4","FIPSCHECK3","FIPS Failed Packet Comparison.","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","4","FIPSCHECK4","FIPS Test Completed Successfully.","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","4","ICPUFRAG1","PktReasmSetAction failed.","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","4","ICPUPP2","SaCheckSelectors: Illegal pkt, no valid SA","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","4","ICPUPP3","Illegal pkt dst:[dec].[dec].[dec].[dec] proto:[dec] spi:[hex], no match on SA SPI [hex].","No matching SA was found for the received encrypted packet. This message is most likely to occur during rekeying when the inbound SA is not yet established.","If the message persists and packets are being lost, check whether the CPU is overloaded or the crypto engine is oversubscribed."
"SPA-IPSEC-2G","4","ICPUPP4","Illegal pkt dst:[dec].[dec].[dec].[dec] proto:[dec] spi:[hex], no match on SA dst[dec].[dec].[dec].[dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","4","ICPUPP8","Illegal clear pkt src:[dec].[dec].[dec].[dec] dst:[dec].[dec].[dec].[dec] proto:[dec].","Clear packets were received that should have been encrypted.","Check whether the remote peer has a correct security policy and SA to encrypt the packets. Compare IP addresses of the packets with crypto ACLs."
"SPA-IPSEC-2G","4","ICPUPP9","Packet src:[dec].[dec].[dec].[dec] dst:[dec].[dec].[dec].[dec] seq num:[hex] failed replay check last seq num:[hex] for SA:[hex].","IPsec packets have failed the anti-replay check. A common cause is the use of QoS in your network. With QoS, lower priority packets can arrive late, missing the anti-replay check window. When this condition occurs, higher level protocols can request retransmission so that functionality is not lost. Time-sensitive protocols, such as voice traffic, might be degraded due to dropped or late packets.","Increase the anti-replay window size. If anti-replay checking is not needed, disable it. Display the SA with the given index - show tacm ipr sa ."
"SPA-IPSEC-2G","4","ICPUPP10","Packet src:[dec].[dec].[dec].[dec] dst:[dec].[dec].[dec].[dec] proto ESP, but not SA proto!","The received packet's protocol does not match the SA protocol. The SA expects AH, but the packet uses ESP.","Check whether the negotiated protocol matches the configured transform sets of both peers. Contact TAC with outputs of show crypto ipsec sas command."
"SPA-IPSEC-2G","4","ICPUPP11","Packet src:[dec].[dec].[dec].[dec] dst:[dec].[dec].[dec].[dec] proto AH, but not SA proto!","The received packet's protocol does not match the SA protocol. The SA expects ESP, but the packet uses AH. Contact TAC with outputs of show crypto ipsec sas command.","Check whether the negotiated protocol matches the configured transform sets of both peers."
"SPA-IPSEC-2G","4","ICPUPP12","IPPE says IPSec, not pkt src:[dec].[dec].[dec].[dec] dst:[dec].[dec].[dec].[dec] proto:[dec]!","An error has been reported by the firmware.","No action."
"SPA-IPSEC-2G","4","ICPUPP13","Policy check failed for pkt src:[dec].[dec].[dec].[dec] dst:[dec].[dec].[dec].[dec] proto:[dec] SA index:[hex]","The decrypted packet does not match the security policy.","Check whether the security policy on both peers is symmetric."
"SPA-IPSEC-2G","4","ICPUPP14","Pkt src:[dec].[dec].[dec].[dec] dst:[dec].[dec].[dec].[dec] proto:[dec] match deny; SA index [hex]","Auditable event: Policy check failed for inbound packet.","Check the crypto ACLs (whether the security policy on both peers is symmetric)."
"SPA-IPSEC-2G","4","ICPUPP15","SecInfo [hex] doesn't match with SA [hex] SA index:[hex]","An unexpected and unsupported nesting of SA was detected.","Remove any nested SA."
"SPA-IPSEC-2G","4","ICPUPP16","Inner proto [dec] must be IPSec but is not","An unexpected and unsupported nesting of SA was detected.","Remove any nested SA."
"SPA-IPSEC-2G","4","ICPUSYSIPADDRADD","PktProcAddSysIpAddr: Unable to add local IP Addr [hex]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","4","ICPUSYSIPADDRDEL","PktProcAddSysIpAddr: Unable to delete local IP Addr [hex]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","4","ISAUNCA7","PktProcAtnModSas: Mismatch valid flag unca:invalid index:[hex]","An error has been reported by the firmware.","For details enter the show tcam ipr sa command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","4","RECOVERYDONE","CP Lockup Recovery - Done","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","4","RECOVERYFRAG","Ipfrag: Unable to transmit. CP Lockup Occured.","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA-IPSEC-2G","4","RECOVERYSTART","CP Lockup Recovery - Start(OCPU)","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_IPSEC_2G","4","SINGLEIP","Wrong type [dec] size:[dec].","Error reported by firmware.","No action."
"SPA_IPSEC_2G","4","SPDID","XcpuSetVlanSpdId: IpcAllocFailed","Crypto connect config could not be programmed correctly.","Remove and reapply crypto connect commands, and if problem persists, contact TAC."
"SPA-IPSEC-2G","4","XCPURECOVERY","Error Disabling CP","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_IPSEC_2G","5","ACEPKADHGSHIDNOALL","PkaDhGenerateShared:DH session ID [dec] not allocated","Invalid crypto ID used, command rejected, likely due to high system load.","Reduce system load."
"SPA_IPSEC_2G","5","ACEPKADHGSIDINUSE","PKA: PkaDhGenerateSessionInt: DH session id [dec] already in use","Invalid crypto ID used, command rejected, likely due to high system load.","Reduce system load."
"SPA_IPSEC_2G","5","ACEPKADHGSINVID","PKA: PkaDhGenerateSessionInt: invalid DH session id [dec]","Possible software bug.","Contact TAC."
"SPA_IPSEC_2G","5","ACEPKAINITCMPL","BCM5820: Initialization complete","These messages are normal after SPA bootup.","Can ignore safely."
"SPA_IPSEC_2G","5","ACEPKANOBDESC","PKA: no data buffer descriptors available","Out of buffers for crypto operation.","Reduce system load."
"SPA_IPSEC_2G","5","ACEPKANOMOREDHGRPS","PKA: no more DH groups available","Too many DH groups defined. Possible software error.","Contact TAC."
"SPA_IPSEC_2G","5","ACEPKAPOSTRSTDELAY","PKA: BCM5820 post reset delay","These messages are normal after SPA bootup.","Can ignore safely."
"SPA_IPSEC_2G","5","ACEPKARESUB","BCM5820: Resubmitting crypto request","These messages are normal after SPA bootup.","Can ignore safely."
"SPA_IPSEC_2G","5","ACEPKARESUBPK","BCM5820: Resubmitting PK request [hex]","These messages are normal after SPA bootup.","Can ignore safely."
"SPA_IPSEC_2G","5","ACEPKARSARMPSBUSYID","PKA: can't remove busy RSA private session [dec]","Trying to delete a busy RSA session. May be caused by out-of-order messaging on a highly loaded system.","Reduce system load."
"SPA_IPSEC_2G","5","ACEPKARST","PKA: BCM5820 in reset","These messages are normal after SPA bootup.","Can ignore safely."
"SPA_IPSEC_2G","5","ACEPKARSTCOMPL","BCM5820: Reset complete","These messages are normal after SPA bootup.","Can ignore safely."
"SPA-IPSEC-2G","6","ACEPKAHWCRNGT","PKA: HW RNG has duplicate data, discarding","Duplicate random data detected, duplicate data was discarded.","This is normal operation if seen rarely. Contact TAC if seen frequently."
"SPA_IPSEC_2G","6","ACEPKAPKNOMCR2","PKA: no Public Key MCRs available","Out of buffers for crypto operation.","Reduce system load."
"SPA-IPSEC-2G","6","ACEPKARNGDUP","PKA: A pseudo-random number was generated twice in succession. [hex][hex]; 0Unrecognized format `x%p' 0Unrecognized format `x%p' idx:[hex]","An error has been reported by the firmware","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_IPSEC_2G","6","ACEPKARNG","PKA: seed key is same as the seed, discarding","Duplicate random data detected, duplicate data was discarded.","This is normal operation if seen rarely. Contact TAC if seen frequently."
"SPA_IPSEC_2G","6","ACEPKARNGDUP","PKA: A pseudo-random number was generated twice in succession. [hex][hex]; 0Unrecognized format `x%p' 0Unrecognized format `x%p' idx:[hex]","Duplicate random data detected, duplicate data was discarded.","This is normal operation if seen rarely. Contact TAC if seen frequently."
"SPA-IPSEC-2G","6","ACEPKARNGKAT","PKA: RNG failed KAT","Pseudo-RNG known-answer-test failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_MIB","4","DATA_LEN","[chars]: MIB message lengths mismatch([chars]), expecting [dec] bytes, receiving [dec].","The MIB updates expected more data than was received.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPAN","0","DISTRIBUTED_EGRESS_INCOMPATIBLE","Distributed egress SPAN is not recommended up to certain hardware revision of WS-X6708-10GE","The distributed egress SPAN feature is not supported on WS-X6708-10GE hardware revisions earlier than version 1.4. By default, the system will be in centralized mode. Attempting to enable the distributed feature will cause this warning message, but will not prevent the feature from being configured.","Disable distributed egress SPAN by entering the no monitor session egress replication-mode distributed command in global configuration mode. For further caveats on the distributed egress SPAN feature, see the Cisco IOS software release notes and search for bug ID CSCso05127 using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl."
"SPAN","3","MEM_UNAVAIL","Memory was not available to perform the SPAN operation","Unable to perform a SPAN operation because of a lack of memory","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"SPAN","3","REDIR_HW_UNAVAIL","Redirect hardware resource not available [chars]","The system could not allocate resource for redirecting BPDUs. A possible cause of this condition is that all available redirect registers in the policy feature card (PFC) are used by other features.","Free up a redirect register in the PFC by unconfiguring features that use redirect registers and retry allowing BPDUs for SPAN service modules. If protocol tunneling is configured on any ports, remove the protocol tunneling configuration from all ports to free up one redirect register."
"SPAN","3","SESS_DEC_CFG","SPAN hardware resource is in use. [chars]","The system could not allocate a SPAN hardware resource for the feature specified in the message. It is possible that a distributed EtherChannel has been configured in the system that is using SPAN hardware resource.","Remove one or all of the distributed EtherChannels from the system and retry the operation."
"SPAN","3","SESS_HW_UNAVAIL","SPAN hardware resource not available [chars]","The system could not allocate a SPAN hardware resource for the feature specified in the message. A possible cause of this condition is that all available SPAN source sessions are already in use. The system can be configured with a maximum of two SPAN source sessions or one RSPAN source session","Remove one of the existing SPAN or RSPAN source sessions and retry the operation."
"SPAN","3","UNKN_ERR","An internal error occurred during a SPAN operation.","SPAN detected an error in its internal operation.","The error might be transient, in which case trying the SPAN operation again might be successful. If this fails, the switch might need to be reloaded for the desired operation to complete."
"SPAN","3","UNKN_ERR_PORT","An internal error occurred when configuring SPAN on port %s","SPAN detected an error in its internal operation.","The error might be transient, in which case trying the SPAN operation again might be successful. If this fails, the switch might need to be reloaded for the desired operation to complete."
"SPAN","4","DISTRIBUTED_EGRESS_INCOMPATIBLE","Distributed egress SPAN is not recommended up to certain hardware revision of WS-X6708-10GE","The distributed egress SPAN feature is not supported on hardware revisions earlier than v1.4 of WS-X6708-10GE. By default the system will be in centralized mode. An attempt to enable the distributed feature will cause this warning message but will not prevent the feature from being configured.","Disable distributed egress SPAN by entering the no monitor session egress replication-mode distributed command in global configuration mode. See the documentation release notes and DDTS CSCso05127 for more information on the caveats exposed by this feature."
"SPAN","5","ERSPAN_ADJ_TUNNEL","ERSPAN Destination behind a tunnel. Shutting down session [dec]","The next hop to the IP address specified as the ERSPAN destination lies behind a tunnel. This configuration is not supported. The ERSPAN session is shut down when such a configuration is detected.","Specify another ERSPAN destination IP address that does not have a tunnel as the next-hop adjacency."
"SPAN","5","PKTCAP_START","Packet capture session %d started","A packet capture session was activated manually or after the scheduled time.","Stop the capture if it is not required. By configuring the rate-limit value in the monitor session type capture configuration mode, you can change the rate of packets reaching the CPU for capture. If the capture traffic rate is too high, you can drop protocol packets."
"SPAN","5","PKTCAP_START_FAILED","Packet capture session [dec] failed to start. [chars]","Packet capture is activated by user or after the scheduled time but failed to start.","Correct the failure reason and re-activate or re-schedule the capture."
"SPAN","5","PKTCAP_STOP","Packet capture session %d ended %s, %d packets captured","Packet capture was stopped. The capture stops if the capture buffer is full or if the user manually stops the capture or if a capture timeout occurs.","You can view the capture on the console or you can export the capture buffer using the monitor capture export buffer command. Delete the capture session if it is no longer required."
"SPAN","6","SPAN_EGRESS_REPLICATION_MODE_CHANGE","Span Egress HW Replication Mode Change Detected. Current replication mode for [chars] is [chars]","When autodetection of egress SPAN replication mode is enabled, the system will transition any available sessions to centralized mode when a distributed egress SPAN-incapable line card is inserted. The system will transition back the available sessions to distributed egress SPAN mode when the last distributed egress SPAN-incapable line card is removed.","To prevent a session switching back to distributed egress SPAN mode, enter the monitor session egress replication-mode centralized command."
"SPANTREE","2","BRIDGE_ASSURANCE_BLOCK","Bridge Assurance blocking port %s%s.","Bridge Protocol Data Units (BPDUs) were not received from a neighboring switch on the interface that has spanning tree Bridge Assurance (BA) configured. As a result, the interface was moved to the spanning tree blocking state.","Disable BA on the interface or make sure that the interface is connected to a L2 switch or bridge device."
"SPANTREE","2","BRIDGE_ASSURANCE_UNBLOCK","Bridge Assurance unblocking port %s%s.","The indicated interface has been restored to the normal spanning tree state after receiving BPDUs from the neighboring Layer 2 switch or bridge.","No action is required."
"SPANTREE","2","PVST_PEER_BLOCK","PVST+ peer detected on port %s","Although the Multiple Spanning Tree Protocol (MSTP) Per-VLAN Spanning Tree Plus (PVST+) simulation feature is disabled, PVST+ BPDU(s) are detected on the indicated interface.","Make sure the PVST+ switch is removed from the network or enable the MSTP PVST simulation feature."
"SPANTREE","2","PVST_PEER_UNBLOCK","Unblocking port %s","The indicated interface is no longer receiving the PVST+ BPDUs. The inconsistency is cleared and the interface has returned to normal operation.","No action is required."
"SPANTREE","2","PVSTSIM_OK","PVST Simulation inconsistency cleared on port [chars].","The listed interface is no longer receiving PVST BPDUs advertising information inconsistent with the CIST port information. The PVST simulation inconsistency condition is cleared and the interface will return to normal operation.","No action is required."
"SPANTREE","3","PRESTD_NEIGH","pre-standard MST interaction not configured ([chars]). Please, configure: 'spanning-tree mst pre-standard' on ports connected to MST pre-standard switches.","The switch has received a prestandard multiple spanning-tree (MST) BPDU on a port that is not configured for prestandard MST BPDU transmission. The switch will automatically adjust its mode of operation on this port and will start sending prestandard BPDUs. However, this autodetection of prestandard neighbors is not 100 percent accurate and we recommended that you explicitly configure the port for prestandard MST BPDU transmission. This warning message will be displayed only once.","Configure the spanning-tree mst pre-standard command on all the ports that are connected to switches running the Cisco prestandard version of MST. We recommended that you migrate all the switches in the network to the IEEE standard MST version when it is possible."
"SPANTREE","4","PORT_NOT_FORWARDING","[chars] [chars] [chars] [chars]","The port is not in a forwarding state and is not forwarding packets.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPANTREE","6","PORTADD_ALL_VLANS","[chars] added to all Vlans","The interface has been added to all VLANs","This is an informational message only. No action is required."
"SPANTREE","6","PORTDEL_ALL_VLANS","[chars] deleted from all Vlans","The interface has been deleted from all VLANs.","This is an informational message only. No action is required."
"SPANTREE","6","PORT_STATE","Port [chars] instance [dec] moving from [chars] to [chars]","The state of the specified spanning tree port has changed.","No action is required."
"SPANTREE","7","PORTDEL_SUCCESS","[chars] deleted from Vlan [dec]","The interface has been deleted from the specified VLAN.","This is an informational message only. No action is required."
"SPAN_ICC_ISSU","3","BUFFER","SPAN ICC ISSU client failed to get buffer for message, error %d","The SPAN ICC ISSU client was unable to get a buffer for building a negotiation message. As a result, it cannot send the negotiation message to the standby unit and the standby unit cannot be brought up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"SPAN_ICC_ISSU","3","CAPABILITY","SPAN ISSU client %s","The SPAN ISSU client detected an error during capability negotiation. A mismatch exists in the client capability between the active and standby unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"SPAN_ICC_ISSU","3","MSG_NOT_OK","SPAN ICC ISSU client message %d is not compatible","The SPAN ICC ISSU client received an incompatible message from the peer unit. Since the message is not compatible, it cannot be processed by this unit","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"SPAN_ICC_ISSU","3","MSG_SIZE","SPAN ICC ISSU client failed to get the message size for message %d","The SPAN ICC ISSU client was unable to calculate the message size for the message specified. The SPAN ICC ISSU client will be unable to send the message to the standby unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"SPAN_ICC_ISSU","3","POLICY","SPAN ICC ISSU client message type %d is %s","The SPAN ICC ISSU client received a message type that it does not support. A policy is applied to make the session compatible.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu session commands and your pertinent troubleshooting logs."
"SPAN_ICC_ISSU","3","SEND_FAILED","SPAN ICC ISSU client failed to send a negotiation message, error %d","The SPAN ICC ISSU client could not send a session negotiation message to the peer. As a result, the standby unit cannot be brought up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"SPAN_ICC_ISSU","3","SESSION","SPAN ICC ISSU client %s","SPAN ICC ISSU client detected an error during a session negotiation with the peer unit. As a result, the standby unit cannot be brought up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"SPAN_ICC_ISSU","3","TRANSFORM","SPAN ICC ISSU client %s transform failed, error %s","The SPAN ICC ISSU client could not transform the message. If the transmit transformation failed, the ICC message cannot be sent to the peer unit. If the receive transformation failed, the ICC message cannot be applied on the peer unit. In either case, the SPAN ICC ISSU state will not be identical with the active unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"SPA_OIR","2","INITFAIL","SPA OIR initialization error","A failure occurred during the SPA OIR subsystem startup. SPA OIR is not functional for the RP or line card that generated the message.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"SPA_OIR","2","SUBSLOTINITFAIL","SPA OIR initialization error for [chars]","A failure occurred during the SPA OIR subsystem startup. SPA OIR is not functional for the specified slot or subslot.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"SPA_OIR","3","CMD_ATTR","[chars]: Unexpected command identifier ([int])","An unexpected command identifier was detected when processing a command related to a SPA OIR. The command was not processed. This is most likely due to a software problem.","Copy the message exactly as it appears on the console or in the system log. Enter the show monitor event-log spa all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_OIR","3","CORRUPT_EVENT","[chars]","Corruption was detected within a SPA OIR event for the subslot specified in the message. When this error occurs, the system attempts automatic recovery by reloading the SPA. This condition could be caused by a software, firmware, or hardware problem, but a firmware or software problem is more likely. For distributed platforms, SPA OIR events are transported over different media depending on the platform (for example, the Cisco 12000 uses the MBUS). An unlikely cause of this error is that an event message was corrupted during transport.","No immediate action is required on the system if the SPA is operational. Copy the message exactly as it appears on the console or in the system log. Enter the show monitor event-log spa all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_OIR","3","EVENT_DATA_ERROR","SPA OIR event data error - [chars]([int])","Invalid data was detected within a SPA OIR event. The SPA OIR state machines may not reflect the state of the hardware. The problem affects only one SPA, but the SPA cannot be determined from the context where the error was detected. This condition could be caused by a software or hardware problem, but a software problem is more likely. For distributed platforms, SPA OIR messages are transported over different media depending on the platform (for example, the Cisco12000 uses the MBUS). An unlikely cause of this error is that an event message was corrupted during transport.","Check the system log for other messages that may help determine which SPA is affected. Enter the hw-module target_spa reload command, with target_spa being the slot or subslot of the affected SPA. Entering this command will perform a power cycle and synchronizes the affected SPA software with the hardware. Copy the message exactly as it appears on the console or in the system log. Enter the show monitor event-log spa all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_OIR","3","EVENT_HANDLING","[chars]: [chars][hex]","A data structure error was detected when handling a SPA OIR event for the SPA in the slot or subslot specified in the message. The SPA OIR state machines may not reflect the state of the hardware. This condition is most likely due to a software problem.","Copy the message exactly as it appears on the console or in the system log. Enter the show monitor event-log spa all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_OIR","3","EVENT_TIMEOUT","[chars]: Timeout waiting for SPA OIR event","While waiting for a SPA OIR event, a timeout occurred for the subslot specified in the message. The SPA did not complete initialization. When this error occurs, the system attempts automatic recovery by reloading the SPA. This condition could be caused by a software or hardware problem, but a software problem is more likely. For distributed platforms, SPA OIR events are transported over different media depending on the platform (for example, the Cisco 12000 uses the MBUS). An unlikely cause of this error is that an event message was corrupted during transport.","No immediate action is required on the system if the SPA is operational. Copy the message exactly as it appears on the console or in the system log. Enter the show monitor event-log spa all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_OIR","3","HW_INIT_TIMEOUT","[chars]","A timeout occurred for the specified subslot while waiting for the SPA hardware to initialize. The SPA did not complete initialization. When this error occurs, the system attempts an automatic recovery by reloading the SPA. This condition could be caused by a software, firmware, or hardware problem, but a firmware or hardware problem is most likely.","No immediate action is required on the system if the SPA is operational. Copy the message exactly as it appears on the console or in the system log. Enter the show monitor event-log spa all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_OIR","3","HW_SIGNAL_DEASSERTED","[chars]","One or more hardware signals indicated that the SPA hardware in the specified subslot should be reinitialized. When this error occurs, the system attempts an automatic recovery by reloading the SPA. This condition could be caused by a software, firmware, or hardware problem, but a firmware or hardware problem is most likely. This condition could be caused by a rare interaction between SPA and its SIP.","No immediate action is required on the system if the SPA is operational. Copy the message exactly as it appears on the console or in the system log. Enter the show monitor event-log spa all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, or would like to report a suspected hardware failure, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_OIR","3","MESSAGE_ERROR","[chars]: SPA OIR event message error - [chars]([int])","An error was detected in a SPA OIR event message for the SPA in the specified slot or subslot. The SPA OIR state machines may not reflect the state of the hardware for this SPA. This condition could be caused by a software or hardware problem, but a software problem is more likely. For distributed platforms, SPA OIR messages are transported over different media depending on the platform (for example, the Cisco 12000 uses the MBUS). An unlikely cause of this error is that an event message was corrupted during transport.","Enter the hw-module target_spa reload command, with target_spa being the slot or subslot of the affected SPA. Entering this command will perform a power cycle and synchronizes the affected SPA software with the hardware. Copy the message exactly as it appears on the console or in the system log. Enter the show monitor event-log spa all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_OIR","3","POST_EVENT_ERROR","[chars]: event [int]","A SPA OIR event message was not enqueued for the SPA in the specified slot or subslot. The SPA OIR state machines may not reflect the state of the hardware for this SPA. This condition is most likely due to a software problem.","Enter the hw-module target_spa reload command, with target_spa being the slot or subslot of the affected SPA. Entering this command will perform a power cycle and synchronizes the affected SPA software with the hardware. Copy the message exactly as it appears on the console or in the system log. Enter the show monitor event-log spa all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_OIR","3","RECOVERY_RELOAD","[chars]: Attempting recovery by reloading SPA","The OIR facility attempted an automatic recovery by reloading the SPA in the specified subslot. Look for other messages related to this SPA subslot to determine the failure that triggered the automatic recovery.","This is an informational message only. No action is required."
"SPA_OIR","3","SEQUENCE_NUMBER_ERROR","[chars]","A sequence number error was detected within a SPA OIR event for the specified subslot. When this error occurs, the system attempts an automatic recovery by reloading the SPA. This condition could be caused by a software, firmware, or hardware problem, but a firmware or software problem is most likely. For distributed platforms, SPA OIR events are transported over different media depending on the platform (for example, the Cisco 12000 uses the MBUS). An unlikely cause of this error is that an event message was corrupted during transport.","No immediate action is required on the system if the SPA is operational. Copy the message exactly as it appears on the console or in the system log. Enter the show monitor event-log spa all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, or would like to report a suspected hardware failure, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_OIR","3","SPA_POWERED_OFF","[chars]: SPA [chars] powered off after [int] failures within [int] seconds","The SPA was powered off because it failed too often. This condition may be caused by a software, firmware, or hardware error.","Look for other system messages related to this SPA subslot to determine the root cause of the failure. Enter the hw-module target_spa reload command, with target_spa being the slot or subslot of the affected SPA. Entering this command will perform a power cycle and synchronizes the affected SPA software with the hardware. Copy the message exactly as it appears on the console or in the system log. Enter the show monitor event-log spa all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_OIR","3","SW_INIT_TIMEOUT","[chars]: SPA initialization not completed","A timeout occurred for the specified subslot while waiting for the SPA software driver to initialize the SPA. The SPA did not complete initialization. When this error occurs, the system attempts automatic recovery by reloading the SPA. This condition could be caused by software, firmware or hardware problem, but a software or firmware problem is more likely.","Check for other reported messages for more verification. Hardware replacement should not occur on the first occurrence. Before requesting hardware replacement, review troubleshooting logs with a Cisco technical support representative. No immediate action is required on the system if the SPA is operational. Copy the message exactly as it appears on the console or in the system log. Enter the show monitor event-log spa all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, or would like to report a suspected hardware failure, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_OIR","3","UNEXPECTED_EVENT","[chars]: SPA OIR unexpected event([int])","An unexpected SPA OIR event was detected for the SPA in the specified slot or subslot. The SPA OIR state machines may not reflect the state of the hardware for this SPA. This condition could be caused by software or hardware problem, but a software problem is more likely. For distributed platforms, SPA OIR messages are transported over different media depending on the platform (for example, the Cisco 12000 uses the MBUS). An unlikely cause of this error is that an event message was corrupted during transport.","Enter the hw-module target_spa reload command, with target_spa being the slot or subslot of the affected SPA. Entering this command will perform a power cycle and synchronizes the affected SPA software with the hardware. Copy the message exactly as it appears on the console or in the system log. Enter the show monitor event-log spa all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_OIR","3","UNEXPECTED_INSERTED_EVENT","[chars]","An unexpected inserted event occurred for the specified subslot. When this error occurs, the system attempts automatic recovery by reloading the SPA. This condition could be caused by a software, firmware, or hardware problem, but a firmware or software problem is most likely. This condition could be caused by a rare interaction between SPA and its SIP.","No immediate action is required on the system if the SPA is operational. Copy the message exactly as it appears on the console or in the system log. Enter the show monitor event-log spa all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, or would like to report a suspected hardware failure, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_OIR","3","UNEXPECTED_RECOVERY_ACTION","[chars]: SPA [chars], unexpected recovery action([int]) for fail code [hex]","An error occurred while processing a failure message for the SPA in the slot or subslot number specified in the message. The recovery action to be taken after a SPA failure is determined by calling a SPA driver function. This message indicates that the SPA driver function returned an invalid recovery action. After this message was issued, the SPA was reloaded in an attempt to recover. The SPA driver most likely returned an invalid recovery action because of a software problem.","No immediate action is required on the system if the SPA is operational. Copy the message exactly as it appears on the console or in the system log. Enter the show monitor event-log spa all command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation and the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, or would like to report a suspected hardware failure, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_OIR","3","UNRECOGNIZED","The SPA of type [hex] in [chars] is not recognized","The type of the SPA in the specified subslot is not recognized by the operating system. Either the operating system might not support this SPA type on this platform or the SPA type identification stored on the SPA is invalid.","Ensure that the system is running a version of the operating system that supports the specified SPA type on this platform. If the correct operating system version is in use, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Include the information about the SPA type found on the front of the SPA. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_OIR","3","UNSUPPORTED","The [chars] in [chars] is not supported by the [chars] module","The SPA in the specified subslot is not supported in the specified SIP by the version of the operating system currently running on the system. The SPA type may be supported by another SIP or by a later operating system release.","Ensure that the SIP specified in the error message supports the specified SPA type. Ensure that the operating system release supports the SPA type in the SIP. It may be necessary to upgrade your system to the latest operating system release in your release train, or it may be necessary to use a different SIP type. If the SPA type specified in the error message does not match the interface types or numbers shown on the front of the SPA, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Include information regarding the SPA type found on the front of the SPA. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_OIR","6","INSCARD","Card inserted in [chars]","The OIR facility detected a newly inserted SPA. The interfaces associated with that SPA are operational, but will be shut down until they are configured by the user. If any interfaces of that type were previously configured, they will be restored to their previous state.","This is an informational message only. No action is required."
"SPA_OIR","6","PRECONFIG_MISMATCH","[chars]: Inserted SPA type does not match preconfigured SPA type. Configuration updated","There is mismatch between the inserted SPA type and the preconfigured SPA type on platforms that support preconfiguration. The inserted SPA replaces the preconfigured SPA.","Verify the configuration by entering the show running-config command. If you would like to revert to the preconfigured type, remove the SPA and then update the configuration from a backup copy."
"SPA_OIR","6","REMCARD","Card removed from [chars], interfaces disabled","The OIR facility detected the removal of a SPA from the specified slot or subslot. The interfaces on that SPA will be administratively shut down and marked as removed. The routing table will be flushed of any routes through the removed interfaces.","This is an informational message only. No action is required."
"SPA_OIR","6","SHUTDOWN","[chars] is administratively shutdown; Use 'no hw-module [chars] shutdown' to enable","The SPA was not brought up because the SPA bay is in an administrative down state. The SPA bay will appear as hw-module target_spa shutdown in the running configuration.","Use the no hw-module target_spa shutdown command to administratively enable the SPA bay."
"SPA_PLIM","3","FATALERROR","SPA in slot [dec] bay [dec] experienced a fatal error [chars] and is being reset.","A fatal error was encountered during SPA operation. The SPA may be restarted.","If the error is not observed more than once, it might be a singular event and the SPA needs to be monitored. If the issue occurs repeatedly, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_PLIM","3","FW_RELOAD","[chars] is being reloaded due to firmware/application exception.","The SPA firmware application has failed. The SPA is being reloaded to recover its operational state.","Collect the application core file from flash. The core filename and time stamp are shown in the preceding message."
"SPA_PLIM","3","HEARTBEAT","[chars] has experienced an heartbeat failure Current Sequence [int] received Sequence [int] Time since last keep [dec]ms.","The IPC communication between the local CPU and host in the specified slot is not functional. The IPC module will be restarted, after which communication might be reestablished. If the problem persists the SPA will be reset.","If the system continues running normally, no action is required. If this message recurs, or the system behaves abnormally, collect the logs from the system (RP and line card). Copy the message exactly as it appears on the console or in the system log. Enter the show hw-module slot-number/subslot-number tech-support command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_PLIM","3","INITFAIL","[chars] has failed initialization because SPA [chars].","A failure occurred during the SPA initialization. SPA is not functional and may be restarted by the RP or line card.","If the line card or RP successfully initialized the SPA, no action is required. If the SPA was not successfully initialized, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_PLIM","3","INIT_PORT","[chars] PLIM client IPC port has not been initialized.","The specified PLIM client IPC port has not been initialized.","Copy the message exactly as it appears on the console or in the system log. Enter the show ipc status command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_PLIM","4","EXCEPTION","[chars] has experienced an exception: [chars]. Writing SPA crash dump information to [chars].","The local CPU in the specified slot has experienced an exception condition. The process that caused the exception might have been restarted. If an exception core dump was created, the core dump is stored in the line card flash memory, if available.","If the system continues running normally, no action is required. If this message recurs, or the system behaves abnormally, collect the crash dump file from the line card flash. Copy the message exactly as it appears on the console or in the system log. Enter the show hw-module slot-number/subslot-number tech-support command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_PLIM","4","SBE_ECC","[chars] reports [dec] SBE occurance at [dec] addresses","The SPA has reported single-bit correctable ECC errors. The log shows that more than one SBE has occurred. SBEs are correctable memory problems. It will not affect router operation. Excessive occurrences may indicate defective memory.","Observe at the first occurrence. If the error recurs, replace the faulty memory chip at the earliest opportunity."
"SPA_PLIM","4","SBE_OVERFLOW","[chars] SBE table([dec] elements) overflows.","The SPA has reported more unique single-bit correctable ECC errors than the platform defined internal table can hold. SBEs are correctable memory problems. It will not affect router operation. Excessive occurrences indicate defective memory.","Replace the faulty memory chip at the earliest opportunity."
"SPA_PLIM","5","RECEIVINGFILE","Receiving [chars] from [chars].","The SPA has sent a file (syslog or core dump) to the line card and the file has been stored in the line card flash if available.","This is a debug message only. No action is required."
"SPA_PLUGIN","3","AUXC2W_CREATE","[chars]: Device auxiliary C2W creation failed.","Cannot allocate memory for auxiliary C2W structure.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"SPA_PLUGIN","3","EEPROM_READ","[chars]: Error reading EEPROM.","Cannot read EEPROM content. It indicates either an improperly seated SPA or a hardware failure.","Power down and reseat the specified SPA card. If the condition persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_PLUGIN","3","EFC_NOTSYNC","[chars]: Can not synchronize EFC bus.","Extended flow control between the modular services card and the SPA is not synchronized. The SPA is shut down. It indicates either an improperly seated SPA, a hardware failure, or an outdated ROMMON or FPGA image.","Power down and reseat the specified SPA card. If the condition persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_PLUGIN","3","EXCEPTION","[chars]: Exception with cause [dec].","One of the SPA software components has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_PLUGIN","3","FAILED","[chars]: Plugin initialization failed.","Plug-in initialization has failed. Plug-in initialization can fail for many reasons. Preceding messages may state the cause.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_PLUGIN","3","FILE_ERROR","[chars]: Error accessing file [chars].","The specified file cannot be accessed. Either the file is not found, lack of permission, out of space, or other file system or device errors.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_PLUGIN","3","FILE_TRANSFER","[chars]: Failed to transfer file to or from SPA.","Failed to transfer a file to or from the SPA. This error might be caused by lack of memory on the SPA or jacket card, IPC failures, improperly seated SPA, or other errors.","Power down and reseat the specified SPA card. If the condition persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_PLUGIN","3","FIRMWARE_APPS_DOWNLOAD","[chars]: Firmware application download failed.","Failed to download an application image to the SPA. This error might be caused by lack of memory on the SPA, IPC failures, an improperly seated SPA, or other download errors.","Power down and reseat the specified SPA card. If the condition persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_PLUGIN","3","FIRMWARE_APPS_STARTUP","[chars]: Firmware application startup failed. SPA status([hex]) host status([hex])","Cannot start application image downloaded to SPA. Possible causes might be either a bad image on the line card flash disk, a hardware failure, or an outdated FPGA or ROMMON image.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_PLUGIN","3","FIRMWARE_BADIMAGE","[chars]: Firmware file [chars] read failed.","The firmware image pointed to by the path is not valid.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_PLUGIN","3","FIRMWARE_BADPATH","[chars]: Invalid firmware file path [chars].","The specified firmware file path is invalid. This is a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_PLUGIN","3","FIRMWARE_DOWNLOAD","[chars]: Firmware download failed.","Failed to download firmware image to the SPA. This error is caused by either lack of memory on the SPA, IPC failures, an improperly seated SPA, or other download errors.","Power down and reseat the specified SPA card. If the condition persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_PLUGIN","3","FIRMWARE_NOMEMORY","[chars]: Insufficient memory for firmware file [chars], size [dec].","Cannot allocate memory for firmware image downloading to the SPA.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"SPA_PLUGIN","3","FIRMWARE_STARTUP","[chars]: Firmware startup failed. SPA status([hex]) host status([hex])","Cannot start the firmware image downloaded to the SPA. Possible causes are either a bad image on the line card flash disk, hardware failures, or an outdated FPGA or ROMMON image.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_PLUGIN","3","IOFPGA_CREATE","[chars]: Device IOFPGA creation failed.","Cannot allocate memory for IOFPGA structure.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"SPA_PLUGIN","3","NOPLIM","[chars]: No PLIM subblock.","An invalid pointer was passed in. Cannot dereference the PLIM subblock pointer. This is an internal error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_PLUGIN","3","NOPORT","[chars]: Failed to open IPC port.","The PLIM client IPC port has not been initialized.","Copy the message exactly as it appears on the console or in the system log. Enter the show ipc status command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_PLUGIN","3","PLIM_CREATE","[chars]: PLIM subblock creation failed.","Cannot allocate memory for a PLIM structure.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"SPA_PLUGIN","3","RETRY_EXHAUSTED","[chars]: plugin initialization failed(retries exhausted).","One or more critical conditions happened that prevented plug-in initialization from moving forward, after the designated number of retries. Preceding messages may specify a failure cause.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_PLUGIN","3","ROMMON","[chars]: ROMMON reports error. SPA status([hex]), host status([hex]).","ROMMON has reported a fatal condition during bootup. It may be caused by outdated ROMMON or FPGA images or by defective hardware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_PLUGIN","3","SPI4_CREATE","[chars]: Device SPI4 creation failed.","Cannot allocate memory for a SPI4 structure.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"SPA_PLUGIN","3","SPI4_INIT","[chars]: SPI4 initializaion failed.","SPI4 initialization has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_PLUGIN","3","SPI4_NOTSYNC","[chars]: Can not synchronize SPI4 bus.","The SPI4 bus between the modular services card and the SPA is not synchronized. It indicates either an improperly seated SPA, a hardware failure, or an outdated ROMMON or FPGA image.","Power down and reseat the specified SPA card. If the condition persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_PLUGIN","3","SPI4_SETCB","[chars]: IPC SPI4 set callback failed(status [dec]).","Cannot set up a callback function for the SPI4 bus. It might be caused by an improperly seated SPA, an outdated ROMMON or FPGA image, or a hardware failure.","Power down and reseat the specified SPA card. If the condition persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_PLUGIN","3","SPI4_SETCB_PORT","[chars]: IPC SPI4 set callback failed(error: [dec]) for port [dec].","Cannot set up a callback function for the SPI4 bus for the specified interface port. It might be caused by an improperly seated SPA, an outdated ROMMON or FPGA image, or a hardware failure.","Power down and reseat the specified SPA card. If the condition persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_PLUGIN","4","LED_CREATE","[chars]: LED driver initialization failed.","Cannot allocate memory for LED structure.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"SPA_PLUGIN","4","LED_READ","[chars]: LED read failed for port [dec], status [dec].","Cannot read LED register values. This error indicates either an improperly seated SPA or a hardware failure.","Power down and reseat the specified SPA card. If the condition persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_PLUGIN","4","LED_WRITE","[chars]: LED write failed for port [dec], status [dec].","Cannot write to the LED register. This error indicates either an improperly seated SPA or a hardware failure.","Power down and reseat the specified SPA card. If the condition persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_PLUGIN","6","EFC_SYNC","[chars]: EFC bus synchronization achieved.","Extended flow control between the modular services card and the SPA is synchronized.","This is an informational message only. No action is required."
"SPA_PLUGIN","6","FIRMWARE_APPS_DOWNLOADING","[chars]: Downloading SPA firmware application ([chars])...","Downloading SPA firmware application.","This is an informational message only. No action is required."
"SPA_PLUGIN","6","FIRMWARE_DOWNLOADING","[chars]: Downloading SPA firmware ([chars])...","Downloading SPA firmware.","This is an informational message only. No action is required."
"SPA_PLUGIN","6","SPI4_SYNC","[chars]: SPI4 bus synchronization achieved.","The SPI4 bus between the modular services card and the SPA is synchronized.","This is an informational message only. No action is required."
"SPA_PMB","4","CANTREADSPAIDPROM","The SPA in Subslot [int]/[int] could not be accessed. The error code received is [dec]","An internal software consistency issue regarding the SPA has been detected.","If the SPA's operation is affected, perform an OIR for the line card on which the SPA or SPAs are located. The slot and subslot of the affected SPA is specified in the message. If this does not fix the problem, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_PMB","4","CARDPWREDON","The line card in slot [dec] is powered on due to out of range electrical signals","The SPAs in the line card in the specified slot could not be accessed because of out-of-range electrical signals. There might be problems in reading in startup configuration for the SPAs in the specified slot.","Check the running and startup config for the specified slot. If the configuration for the ports in the slot is different, then manually copy the startup config to the running config. If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_PMB","4","NOACK","The device with id [hex] in slot [dec] is not responding","The SPAs in the line card in the specified slot could not be accessed because of a hardware problem.The system might not be able to read the startup configuration for the SPAs.","Check the running and startup config for the specified slot. If the configuration for the ports in the slot is different, then manually copy the startup config to the running config. If this problem recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_T3E3","3","LOVEFAIL","[chars]: failed to send [chars] love letter","A 'love letter' (operating status or configuration message) was not sent.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_T3E3","3","MSGERR","Illegal message type [dec] received for Interface [chars]","An unknown message was received by the RP.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_T3E3","3","SSBINIT","[chars]: Fail to initialize serial IDB","Serial IDB initialization has failed. The most common reason is lack of system memory. Previous messages might indicate memory allocation failures.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPA_T3E3","3","SUBRATE_FPGA_LOAD_FAILED2","[chars] Programming [chars] subrate FPGA failed again. The SPA will be disabled as it cannot recover from the FPGA image corruption.","The specified subrate FPGA image is corrupted after an FPD upgrade. It might indicate an FPD image package problem. The SPA is disabled until this problem is corrected.","Verify the correctness of the FPD image package. The FPD image package used in the upgrade should match the running Cisco IOS release. This can be verified by entering the show upgrade fpd package default command."
"SPA_T3E3","4","SUBRATE_FPGA_LOAD_FAILED","[chars] Programming [chars] subrate FPGA failed. The FPGA image is corrupted. One upgrade attempt will be made to recover from the failure.","The specified subrate FPGA image is corrupted and programming of the FPGA has failed. One upgrade attempt will be made to recover from the failure.","Automatically upgrade the subrate FPGA image using the default FPD image package. The package should match the running Cisco IOS release. This can be verified by entering the show upgrade fpd package default command. If the subrate FPGA failure persists after the upgrade, the SPA is disabled. Ensure that the package file is intact."
"SPA_T3E3","5","BERT","Interface [chars], BERT [chars]","The SPA T3E3 driver processed a BERT task.","This is just a notification upon completion of a BERT task. No action is required."
"SPA_T3E3","5","DEF_SUBRATE","[chars] [chars]","The remote subrate configuration has changed.","Inform the network operator that subrate configuration was changed by the remote end."
"SPE","3","UNAVAILABLE","Database reported 0 modules for slot %d","The card in this slot should contain multiple modules. However the database indicates that there are none.","LOG_STD_NO_ACTION"
"SPE","3","UNAVAILABLE","Failed to allocate %s for slot %d","Port Management failed to allocate memory to create slot object.","LOG_STD_NO_ACTION"
"SPE","3","UNAVAILABLE","Failed to find the response buffer for modem %s command","Modem direct query responses could not find buffer to send data to router shelf.","LOG_STD_NO_ACTION"
"SPE","3","UNAVAILABLE","Failed to register %s with Modem Service Manager","Port Management failed to register with Modem Service Manager.","LOG_STD_NO_ACTION"
"SPE","3","UNAVAILABLE","PM ST failed to create %s.","Port Management failed to allocate dynamic chunk memory for event logging.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPE","3","UNAVAILABLE","PM failed to create %s.","Port Management failed to initialize the CSM event processing component.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPE","3","UNAVAILABLE","Recovery Download Maintenance ran out of chunk memory; %s %s","The Recovery Download Maintenance messages cannot be sent.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPE","3","UNAVAILABLE","SPE %s crashed","The firmware running on the SPE aborted.","LOG_STD_NO_ACTION"
"SPE","3","UNAVAILABLE","SPE %s is BAD - %s.","The SPE failed to download and it will be marked BAD.","LOG_STD_NO_ACTION"
"SPE","3","UNAVAILABLE","SPE %s is BAD.","The SPE failed the POST and it will be marked BAD.","LOG_STD_NO_ACTION"
"SPE","3","UNAVAILABLE","SPE SM out of event buffers; %s %s","The PM SPE State Machine has run out of event memory.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPE","3","UNAVAILABLE","SPE SM out of response buffers","The PM SPE State Machine has run out of response event memroy.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPE","4","UNAVAILABLE","Active session count = %d. Country code not set","Country code cannot be set on a system with active sessions.","LOG_STD_NO_ACTION"
"SPE","4","UNAVAILABLE","Country Code Trunk card mismatch for.","A Country Code was configured that may not work with the trunk Card.","LOG_STD_NO_ACTION"
"SPE","6","UNAVAILABLE","%s %s","Download maintenance is running and information","LOG_STD_NO_ACTION"
"SPE","6","UNAVAILABLE","%s","Download maintenance process information","LOG_STD_NO_ACTION"
"SPE","6","UNAVAILABLE","SPE %s : Firmware download deferred","Firmware download for the SPE is postponed due to active calls.","LOG_STD_NO_ACTION"
"SPE","6","UNAVAILABLE","SPE %s : Firmware download initiated","Firmware download for the SPE is initiated.","LOG_STD_NO_ACTION"
"SPE","6","UNAVAILABLE","SPE %s Cleared","The SPE will be re-downloaded with the configured firmware.","LOG_STD_NO_ACTION"
"SPE","6","UNAVAILABLE","SPE %s busiedout(maintenance will be allowed)","The SPE is taken out of service temporarily. Maintanence activities can still be performed.","LOG_STD_NO_ACTION"
"SPE","6","UNAVAILABLE","SPE %s shutdown","The SPE is taken out of service.Maintenance activities cannot be performed.","LOG_STD_NO_ACTION"
"SPE","6","UNAVAILABLE","SPE object %s is unavailable.","Information about this SPE could not be retrieved. The SPE may not exist.","LOG_STD_NO_ACTION."
"SPE2488","3","UNAVAILABLE","spe2488 API failed (errcode=%d): p1=%u, p2=%u, %s","wrong parameters passed in when calling an API","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPE2488","3","UNAVAILABLE","spe2488 channel provisioning failed (slice:%d ch:%d): %s","required resources unavailable.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPE2488","3","UNAVAILABLE","spe2488 channel unprovisioning failed (slice:%d ch:%d): %s","required resources unavailable.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPE2488","3","UNAVAILABLE","spe2488 chip initialization failed (errcode=%d): %s","required resources unavailable.","Reinsert the linecard. If still fails, do 'test cwtlc show seeprom red', swap hardware, and copy the error message exactly as it appears, and report it to your technical support representative."
"SPE2488","3","UNAVAILABLE","spe2488 chip reset failed (errcode=%d): %s","required resources unavailable.","REinsert the linecard. Copy the error message exactly as it appears, and report it to your technical support representative."
"SPE2488","3","UNAVAILABLE","spe2488 indirect poll timeout. addr:%#x","hardware problem","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPE4X155","3","UNAVAILABLE","Chip initialization failed (errcode=%d): %s","required resources unavailable.","Reinsert the linecard. If still fails, do 'test cwtlc show seeprom red', swap hardware, and copy the error message exactly as it appears, and report it to your technical support representative."
"SPE4X155","3","UNAVAILABLE","Pointer to device structure is 0","Software error occured.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPE4X155","3","UNAVAILABLE","Pointer to device structure is invalid","Software error occured.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SPLC_DNLD","1","VS_HA_PS_NOT_SUPPORTED","Chassis Standby is not supported in the current release. Forcing the chassis standby in switch [dec] slot [dec] to drop to rommon","Chassis Standby is not supported in Cisco IOS Release 12.2 SXI(1).","No action is required."
"SPLC_DNLD","1","VS_HA_PS_RUNNING_LEGACY_IMAGE","Chassis Standby in switch [dec] slot [dec] is running non Virtual Switch image. Please remove the chassis standby.","Chassis Standby running non Virtual Switch image is not supported.","No action is required."
"SPLC_DNLD","3","VS_ADD_VSL_ENTRY_FAILED","Add VSL configured port for vslot [int] port [int] failed. Exceed port member count limit.","Attempt to add entry for (vslot, port) to VSL configured port list failed. Exceed port member count limit.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"SPLC_DNLD","3","VS_BOOLEAN_CREATE_FAILED","Unable to create watched boolean '[chars]'","Unable to create the specified watched boolean due to unknown reasons","No action is required."
"SPLC_DNLD","3","VS_ENQUEUE_FAILED","Unable to enqueue to [chars] queue","An internal error occurred that prevented a message from being enqueued to the specified process. The packet was dropped","No action is required."
"SPLC_DNLD","3","VS_HA_HB_NOT_HEARD","Heartbeat messages have not been heard from [[chars]] for [dec] seconds","Heartbeat messages have not been heard for a significant amount of time. It is likely that a timeout will occur soon which will reset the system.","No action is required."
"SPLC_DNLD","3","VS_HA_HB_TIMED_OUT","Heartbeat messages have failed, resetting [[chars]]","Heartbeat messages have failed and the system is no longer operational.","No action is required."
"SPLC_DNLD","3","VS_ICC_PAK_FAIL","Unable to get ICC packet for opcode [dec], operation [dec]","Packet allocation failed for sending an ICC message to do the specified operation","Issue the show tech-support command to gather data that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"SPLC_DNLD","3","VS_ICC_RESP_PAK_NULL","Failed to obtain response packet","Response packet pointer is NULL. This could be no memory condition on response packet sending side or failure to get IPC message on receiving side.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"SPLC_DNLD","3","VS_PROC_CREATE_FAILED","Unable to create process '[chars]'","Unable to create the specified process due to unknown reasons","No action is required."
"SPLC_DNLD","3","VS_QUEUE_CREATE_FAILED","Unable to create queue '[chars]'","Unable to create the specified queue due to unknown reasons","No action is required."
"SPLC_DNLD","3","VS_SPLC_CREATE_DNLD_INSTANCE_FAIL","Dnld instance could not be created for Inchassis-Standby on slot-id [dec] and switch-id [dec]","Not available","Not available"
"SPLC_DNLD","3","VS_SPLC_CREATE_DNLD_PROC_FAIL","Dnld proc could not be created by Inchassis-Active for Inchassis standby on slot-id [dec] and switch-id [dec]","Not available","Not available"
"SPLC_DNLD","3","VS_SPLC_DNLD_BAD_EVENT","Bad event for major [int] and minor [int] in Sup-LC download queue","Not available","Not available"
"SPLC_DNLD","3","VS_SPLC_DNLD_CREATE_PROC_FAIL","Process creation for Sup-LC download at the vs_ha subsys init level","Not available","Not available"
"SPLC_DNLD","3","VS_SPLC_DNLD_CREATE_QUEUE_FAIL","Create queue failed for SPLC dnld process at the vs_ha subsys init level","Not available","Not available"
"SPLC_DNLD","3","VS_SPLC_DNLD_ENQUEUE_FAIL","Could not enqueue the message on the splc_dnld_rx_queue","Not available","Not available"
"SPLC_DNLD","3","VS_SPLC_DNLD_IMAGE_INFO_FAIL","Unable to get the correct image size inchassis standby [dec] on switch-id [dec]","Unable to get the correct image size for the inchassis standby from the inchassis active","No action is required."
"SPLC_DNLD","3","VS_SPLC_DNLD_REQ_ACK_FAIL_SEQ_ABS","Inchassis-Active could not send splc_dnld_req_ack to Inchassis-standby on slot-id [dec] on switch-id [dec] due to missing seq_num","Not available","Not available"
"SPLC_DNLD","3","VS_SPLC_DNLD_REQ_ACK_FAIL_SEQ_ERR","Inchassis-Active could not send splc_dnld_req_ack to Inchassis-standby on slot-id [dec] on switch-id [dec] due to seq_num error","Not available","Not available"
"SPLC_DNLD","3","VS_SPLC_DNLD_REQ_MEM_FAIL","Inchassis-Standby could not get the scp request packet to be sent to Inchassis-Active due to scp get packet memory not present","Not available","Not available"
"SPLC_DNLD","3","VS_SPLC_DNLD_REQ_SEND_FAIL","Inchassis-Standby could not send the dnld_request msg to Inchassis-Active","Not available","Not available"
"SPLC_DNLD","3","VS_SPLC_DNLD_UNKNOWN","Unable to get sup-lc image filename for inchassis standby [dec] on switch-id [dec]","Unable to get the correct image filename for the inchassis standby from the inchassis active","No action is required."
"SPLC_DNLD","3","VS_SPLC_GET_ARG_PTR_FAIL","Argument pointer for SUP-LC download failed on Inchassis-Standby slot-id :[dec] switch-id:[dec]","Not available","Not available"
"SPLC_DNLD","3","VS_SPLC_GET_DNLD_IMAGE_FAIL","Sup-LC Image could not be downloaded to the Inchassis Standby slot-id: [dec] switch-id: [dec]","Not available","Not available"
"SPLC_DNLD","3","VS_SPLC_SET_DNLD_INSTANCE_FAIL","Dnld instance could not be set on the inchassis-standby for slot-id [dec] switch-id [dec]","Not available","Not available"
"SPLC_DNLD","5","VS_CONFIG_DIRTY","Configuration has changed. [chars]","Attempt to reload ignored due to config change","No action is required"
"SPLC_DNLD","5","VS_SWITCH_NUMBER_CHANGE","Switch_number getting changed from [dec] to [dec].","Not available","Not available."
"SPLC_DNLD","6","VS_HA_HOT_STANDBY_NOTIFY","Standby switch is in Hot Standby mode.","Not available.","Not available."
"SPLC_DNLD","6","VS_HA_ICS_EARL_MISMATCH","In-chassis Standby has an incompatible Earl version and will be put down.","Not available.","Not available."
"SPLC_DNLD","6","VS_HA_INCORRECT_ACTIVE","[chars]","Informational messages regarding the state of the active supervisor.","None."
"SPLC_DNLD","6","VS_HA_ISSU_SUP_INSERT","The supervisor in switch [dec] in slot [dec] was inserted during the ISSU cycle and was put down.","As stated above.","Please boot this supervisor manually after the ISSU cycle is complete."
"SPLC_DNLD","6","VS_ICA_ICS_SWITCHID_MISMATCH","Inconsistent switch id detected on ICS([dec])compared to ICA([dec]),correcting it to align with ICA","Not available.","Not available."
"SPLC_DNLD","6","VS_SPLC_IMAGE_VERSION_MISMATCH","In-chassis Standby in switch [dec] is trying to boot with a different image version than the In-chassis Active","Not available","Not available"
"SRC","3","AFOVEN_ERROR","Attempt to enable [chars] protection autofailover on interface [chars] when port status is [hex]","The software failed in an attempt to enable the autofailover feature.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SRCP_APP","2","UNAVAILABLE","%s 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.SRCP_APP-3Error Message    %SRCP_APP-3-UNAVAILABLE: %s 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.SRCP_APP-4Error Message    %SRCP_APP-4-UNAVAILABLE: %s 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.SRCP_APP-6Error Message    %SRCP_APP-6-UNAVAILABLE: Cannot create SRCP application process","Failed to create the SRCP application process.","Check the size of free memory to make sure there is enough memory."
"SRCP_APP","6","UNAVAILABLE","Failed to create DNS message watched queue","Failed to create DNS message watched queue.","Check the size of free memory to make sure there is enough memory."
"SRCP_APP","6","UNAVAILABLE","Failed to create SRCP system message watched queue","Failed to create SRCP system message watched queue.","Check the size of free memory to make sure there is enough memory."
"SRCP_APP","6","UNAVAILABLE","Failed to open UDP port for SRCP","Failed to open UDP port for the SRCP process.","Check if any other application use the same UDP port number (2427)."
"SRP","1","WRAPPING_PROCESS_LOCKED","[chars] The wrap/unwrap state-change process is locked","A wrap and unwrap state change process did not complete in the maximum specified amount of time.","If this message recurs periodically, enter the shutdown and no shutdown commands on the interface to shut down and restart the interface."
"SRP","3","FALSE_VAL_ALARM","[chars] - error in [chars]","A false value has been returned. Some features or commands may not work properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SRP","3","NULL_P_ALARM","Dereferencing NULL pointer [chars] in [chars]","A pointer with a null value has been detected. Some features or commands may not work properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SRP","4","UNAVAILABLE","%s SRR usage changed (%s)","SRR ring usage is changed using Inner, Outer or Both rings.","Diagnose the cause of the ring usage change."
"SRP","4","UNAVAILABLE","%s SRR version missmatch detected.","Different SRR version received from other nodes.","Update the IOS image on all nodes of the ring to the same SRR version"
"SRP","4","UNAVAILABLE","%s Side %c %s","A physical error condition detected at the indicated RAC","Diagnose and repair the physical error"
"SRP","4","UNAVAILABLE","%s Side %c %s","A physical line error condition exists on the indicated network","Diagnose and repair the physical error."
"SRPMIB","3","FALSE_VAL_ALARM","[chars] - error in [chars]","A false value has been returned. Some features or commands may not work properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SRPMIB","3","NULL_P_ALARM","Dereferencing NULL pointer [chars] in [chars]","A pointer with a null value has been detected. Some features or commands may not work properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SSE","2","UNAVAILABLE","No memory available for %s","An operation could not be accomplished because of a low memory condition.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"SSE","2","UNAVAILABLE","SSE bogus equal branch %#x, %#x, %d %x","An internal inconsistency in the data structures used by the SSE occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SSE","2","UNAVAILABLE","SSE delete didn't end at a match node, type %c,value %d, address %i, bytecount %d, high %d, state %d","An internal inconsistency in the data structures used by the SSE occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SSE","2","UNAVAILABLE","SSE hardware failure -- %s code %#x","A hardware error occurred, indicating an unexpected condition on the silicon switch processor (SSP) board.","It might be necessary to replace the SSP. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter OUTPUT_INTERPRETER . Issue the show tech-support command to gather data that may help identify the nature of the error. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SSE","2","UNAVAILABLE","SSE hung -- %s","The SSE is hung.","Reboot the SSE."
"SSE","2","UNAVAILABLE","SSE memory failure, address %#x, expected %#x, got %#x","A hardware error occurred, indicating memory failure on the silicon switch processor (SSP) board.","It might be necessary to replace the SSP. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter OUTPUT_INTERPRETER . Issue the show tech-support command to gather data that may help identify the nature of the error. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SSE","2","UNAVAILABLE","SSE nested addresses detected, protocol %d %i","An internal inconsistency in the data structures used by the SSE occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SSE","2","UNAVAILABLE","SSE software failure -- %s %#x","A software failure occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SSE","2","UNAVAILABLE","program memory does not start at zero","A hardware error occurred, indicating an unexpected condition on the silicon switch processor (SSP) board.","It might be necessary to replace the SSP. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SSE","3","UNAVAILABLE","SSE compilation failure -- %s","A software failure occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SSE","3","UNAVAILABLE","SSE memory failure detected, orig %#x %#x, tested %#x %#x","A memory error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SSH","3","UNAVAILABLE","Attempt to generate server keys failed - error code: %s","Server RSA key-pair could not be generated.","If this message recurs, contact your technical support representative."
"SSH","3","UNAVAILABLE","Unable to retrieve RSA private key for %s","RSA private key does not exist or is corrupted.","If this message recurs, contact your technical support representative."
"SSH","4","UNAVAILABLE","CRC-32 compensation attack detected src %i dst %i, attack thwarted. Connection is closed.","CRC-32 compensation vulnerability allows an attacker to execute arbitrary commands on the SSH server or otherwise subvert an encrypted SSH channel with arbitrary data. (for more information on this attack see http://www.core-sdi.com/english/ssh)","No action necessary - attack has been thwarted"
"SSH","5","UNAVAILABLE","SSH %d.%d has been disabled","The SSH protocol has been disabled for connections","No action necessary - informational message"
"SSH","5","UNAVAILABLE","SSH %d.%d has been enabled","The SSH protocol has been enabled for connections","No action necessary - informational message"
"SSH","5","UNAVAILABLE","SSH Session from %s (tty = %d) for user '%s' using crypto cipher '%s' closed","The SSH Session closure information","No action necessary - informational message"
"SSH","5","UNAVAILABLE","SSH Session request from %s (tty = %d) using crypto cipher '%s' %s","The SSH session request information","No action necessary - informational message"
"SSH","5","UNAVAILABLE","SSH2 Session from %s (tty = %d) for user '%s' using crypto cipher '%s', hmac '%s' closed","The SSH Session closure information","No action necessary - informational message"
"SSH","5","UNAVAILABLE","SSH2 Session request from %s (tty = %d) using crypto cipher '%s', hmac '%s' %s","The SSH session request information","No action necessary - informational message"
"SSH","5","UNAVAILABLE","User '%s' authentication for SSH Session from %s (tty = %d) using crypto cipher '%s' %s","The SSH user authentication status information","No action necessary - informational message"
"SSH","5","UNAVAILABLE","User '%s' authentication for SSH2 Session from %s (tty = %d) using crypto cipher '%s', hmac '%s' %s","The SSH user authentication status information","No action necessary - informational message"
"SSA","4","FABRICCRCERRS","[dec] Fabric CRC error events in 100ms period","The SSA fabric interface encountered more CRC error events than the supervisor engine CRC error threshold allows.","The module has notified the supervisor engine, and the error has been logged. No action is required."
"SSA","4","FABRICSYNCERRS","[dec] Fabric sync error events in 100ms period","The SSA fabric interface encountered more synchronization error events than the supervisor engine synchronization error threshold allows.","The module has notified the supervisor engine, and the fabric interface will be resynchronized. No action is required."
"SSA","4","SSA_CONFIG_FAIL","The Super Santa Ana ASIC configuration failed","The Super Santa Ana ASIC could not be configured. If the switch fabric has gone inactive (down), this message can be expected.","If the module comes on line and traffic processing resumes, no action is required. Otherwise, capture the error and copy the message exactly as it appears on the console or in the system log. On the route processor, enter the show logging and show version commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SSA","5","CHAN_LINK_SPEED_OOB","Array access bounds violated, channel_num=[int], link_num=[int], speed=[int]","The Cisco IOS code has attempted to access an internal array with an invalid index for an SSA channel number, link number, or speed.","If there is no system impact, no action is required. If traffic stops or the line card fails, collect the logs and 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SSA","5","FABRICDOWN_CRCERRS","[dec] Fabric CRC error events in 100ms period","The Super Santa Ana Fabric interface encountered more CRC errors than the maximum configured threshold. However, the reason for this error is that the switch fabric is inactive (down). The line card has notified the supervisor engine of this condition and the error has been logged.","This is an informational message only and occurs in normal operation. No action is required."
"SSA","5","FABRICDOWN_SYNCERRS","[dec] Fabric sync error events in 100ms period","The Super Santa Ana Fabric interface encountered more synchronization errors than the maximum configured threshold. However, the reason for this error is that the switch fabric is inactive (down).","This is an informational message only and occurs in normal operation. No action is required."
"SSA","5","FABRICSYNC_DONE","Fabric sync on [chars] channel done.","The fabric interface ASIC was resynchronized.","No action is required."
"SSA","5","FABRICSYNC_REQ","Fabric sync requested on [chars] channel ([dec])","The line card has requested that the supervisor engine resynchronize its fabric interface ASIC.","No action is required."
"SSA","5","NOFABRICPROCESS","The Super Santa Ana fabric process could not be created","The SSA fabric interface does not have a link process running because the system failed to create it. This module will not support the fabric interface.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SSA","5","NULL_SSA_OBJECT","The Super Santa Ana device object pointer is set to NULL","The memory location of the SSA device object is invalid. The SSA ASIC operation is disabled, and the device interrupt is now masked.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SSA","5","SMB_ACCESSERROR","The Module Super Santa Ana ASIC cannot be accessed","The SSA ASIC read and write access failed. The serial bus that is connected to the SSA ASIC on this module is not functioning correctly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SSA","5","SSA_INIT_FAILURE","The Super Santa Ana ASIC initialization failed","The SSA ASIC could not be initialized. As a result, this device is not operational and has been disabled.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SSH","4","SSH2_UNEXPECTED_MSG","Unexpected message type has arrived. Terminating the connection","SSH Session closure warning on receiving an inappropriate message from the peer","If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support"
"SSH","5","SSH2_CLOSE","SSH2 Session from [chars] (tty = [dec]) for user '[chars]' using crypto cipher '[chars]', hmac '[chars]' closed","Displays the SSH session closure information.","No action is required."
"SSH","5","SSH2_SESSION","SSH2 Session request from [chars] (tty = [dec]) using crypto cipher '[chars]', hmac '[chars]' [chars]","Displays the SSH session request information.","No action is required."
"SSH","5","SSH2_USERAUTH","User '[chars]' authentication for SSH2 Session from [chars] (tty = [dec]) using crypto cipher '[chars]', hmac '[chars]' [chars]","Displays the SSH user authentication status information.","No action is required."
"SSH","5","SSH_CLOSE","SSH Session from [chars] (tty = [dec]) for user '[chars]' using crypto cipher '[chars]' closed","Displays the SSH session closure information.","No action is required."
"SSH","5","SSH_SESSION","SSH Session request from [chars] (tty = [dec]) using crypto cipher '[chars]' [chars]","Displays the SSH session request information.","No action is required."
"SSH","5","SSH_USERAUTH","User '[chars]' authentication for SSH Session from [chars] (tty = [dec]) using crypto cipher '[chars]' [chars]","Displays the SSH user authentication status information.","No action is required."
"SSP","3","DATACREATEFAIL","Creation of required data structures failed.","SSP will not operate properly due to the abnormal initialization of required data structures.","Reload the device. If the error persists, contact your technical service representative."
"SSP","3","EXCEEDMAXDOI","SSP maximum DOI exceeded.","The configuration has exceeded the maximum number of SSP clients allowed on this device at any one time.","Verify your configuration and reduce the number of SSP clients running at the same time. If a large number of SSP clients is required, contact your technical service representative for assistance."
"SSP","3","NOSTART","SSP could not initialize.","The SSP process could not successfully initialize. This condition might be caused by unusual protocol startup times in certain topologies.","Ensure that your IP redundancy mechanism (HSRP) configuration is valid and that all protocols have started. Try to configure SSP again. If this error recurs, contact your technical support representative."
"SSP","3","SRVSOCKCREATEFAIL","SSP socket creation failed.","The SSP process could not establish a socket connection with the SSP peer. This condition is likely to occur because either the device is under extreme load or it is misconfigured.","Verify that the SSP configuration is valid. Configure SSP to use a different port number. Reduce the load on the device."
"SSP","4","CANNOTRUNVER","SSP version [dec].[dec] was requested but is not supported in this image.","The version of SSP requested by the active device is not available in this image. SSP will not run on this device until it is upgraded or the active device is downgraded.","Verify that all SSP peers are running compatible images and that the configuration on each device is correct."
"SSP","4","GROUPCREATEFAIL","The SSP group could not be created.","The maximum number of SSP groups has been reached. Only one SSP group is permitted at one time.","No action is required."
"SSP","4","MISMATCHEDVERRECV","Wrong version on received packet.","The SSP version information in a received packet does not match the version that is currently running on this device.","Verify the configuration of all the SSP peers. Ensure that all peers are running the correct image."
"SSP","5","DISABLED","SSP entering disabled state.","SSP has entered the disabled state. This condition is normal under many circumstances. An example of a normal condition is when the SSP configuration is changed or when a tracked interface is shut down or fails.","If this change occurred because of failure on the active peer, eliminate the cause of failure and reload the failed device."
"SSP","6","ACTIVE","SSP entering active state.","SSP has entered the active state.","No action is required."
"SSP","6","IPREDGRPADD","An IP Redundancy group listed in the SSP config has been added to this device.","The device might now become the active device or the redundant device if no other configuration items are missing.","No action is required."
"SSP","6","IPREDGRPDEL","An IP Redundancy group listed in the SSP config has been removed from this device.","The device might not become the active device or the redundant device if any configuration items are missing.","Add the IP redundancy group to the device, or remove it from the SSP configuration."
"SSP","6","STANDBY","SSP entering standby state.","SSP has entered standby state.","No action is required."
"SSRP","1","UNAVAILABLE","SRP(%d/%d), initialization timeout failure","The SRP Port adaptor has failed to Initialize","Check card seating, and if problem persists, copy the error message exactly as it appears, and report it to your technical support representative, along with show tech-support."
"SSRP","2","UNAVAILABLE","SRP(%d/%d), TX_ERROR Interrupt cause :%s","Cause of fatal that occured in the Tx PCI","Copy the error message exactly as it appears, and report it to your technical support representative, along with show tech-support and test srp tx srp"
"SSRP","2","UNAVAILABLE","SRP(%d/%d), TX_ERROR Interrupt has occured. Error Register=%08X","Fatal error has occured in the Tx PCI","Copy the error message exactly as it appears, and report it to your technical support representative, along with show tech-support and test srp tx srp"
"SSRP","3","UNAVAILABLE","%s","The SSRP hardware is not supported on this platform.","Upgrade your system."
"SSRP","3","UNAVAILABLE","SRP(%d/%d), buffer ownership error, pak=0x%x","A software or hardware error occurred. The SRP port adaptor driver detected that the transmit ring is in an inconsistent and unrecoverable state.","Copy the error message exactly as it appears, and report it to your technical support representative, along with show tech-support."
"SSSMGR","3","BAD_CONTEXT_HANDLE","Corrupted SSS handle [[hex]] in SSS message.","An internal SSS manager error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SSSMGR","3","DYNAMIC_UPDATE_NOT_SUPPORTED","[%d] Dynamic session updates not allowed on this %s session. It is an unsupported configuration.","Updates on these sessions are not supported. This is an unsupported configuration.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SSSMGR","3","INFO_TYPE_NO_COPY_VECTOR","info type has no copy vector (%d).","An internal error occurred in the Subscriber Service Switching (SSS) Manager process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SSSMGR","3","INIT","Initialisation failure, %s","An initialization failure occurred in the SSS Manager process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SSSMGR","3","INVALID_FSM_STATE","Encountered an invalid SSS Mgr state [dec] in [chars]","An internal SSS manager error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SSSMGR","3","INVALID_INFO_TYPE","Received an INVALID info type value (%d).","The SSS Manager received an invalid information type.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SSSMGR","3","INVALID_SERVICE_TYPE","Received an INVALID service type (%d)%s.","The SSS Manager received an invalid service type.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SSSMGR","3","MEMORY_LOW","Memory low (%d times), disconnecting session","The SSS Manager has disconnected a session due to insufficient memory.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SSSMGR","3","NULL_FSM_CONTEXT","Encountered a NULL SSS Mgr context in [chars]","The system has encountered a null context in the SSS manager.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SSSMGR","3","NULL_INFO_STRING","Received a NULL info string value.","The SSS Manager received a NULL information string value.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SSSMGR","3","POLICY_CTX_POISONED","Policy context [hex] has bad magic, [hex].","The magic number in the policy context is wrong.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SSSMGR","3","RESOURCE_OVERFLOW","Resource overflow","A fixed-size system resource has been exceeded.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SSSMGR","3","UNEXPECTED_MSG","Encountered an unexpected message: %s","The SSS Manager received an unexpected message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SSSMGR","3","UNEXPECTED_SIP_INFO","Encountered an unexpected SIP info: %s","The SSS Manager encountered an unexpected SIP.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SSSMGR","3","UNSUPPORTED_CFG","Unsupported configuration detected: [uid: [int]] [chars]","Unsupported configuration detected.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"SSSMGR","5","IFCFG_NOTALLWED_IN_SVC","Interface-config not allowed at service config level, ignoring","The interface configuration attribute is not allowed while in a service profile. It is supported only in user profiles.","Remove the interface configuration attribute from the service profile and reconfigure using a user profile."
"SSSMGR","5","UNSUPPORTED_CFG_NOTICE","Unsupported configuration detected, [chars]","The value of the specified configuration parameter was out of range. This is not considered an error as the value was adjusted to be within the supported range. Update the configuration source to a value within the supported range to avoid this message.","No action is required."
"STACKMGR","6","HDM_GET_DEVICE_RECORD_FAIL","Device Manager could not get device record.","This switch could not obtain the device record for some or all of the all other switches in the stack.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"STACKMGR","6","MASTER_ELECTED","Switch [dec] has been elected as MASTER of the stack","The specified switch has been selected as the active switch.","No action is required."
"STACKMGR","6","MASTER_READY","Master Switch [dec] is READY","The active switch is ready for use.","No action is required."
"STACKMGR","6","MSG_FAIL","Failed to retrieve stack message from port-asic [dec] in direction [dec]","The module for the stack manager module failed to retrieve stack messages.","No action is required."
"STACKMGR","6","NORECORD","Switch removed event for switch [dec] with no switch record","The module for the stack manager notifier has detected that a switch has been removed, but no switch record exists for the removed switch.","No action is required."
"STACKMGR","6","STACK_LINK_CHANGE","Stack Port [chars] Switch [dec] has changed to state [chars]","The status of the specified stack port has changed to active or inactive (up or down).","No action is required."
"STACKMGR","6","SWITCH_ADDED","Switch [dec] has been ADDED to the stack","The specified switch has been added to the stack.","No action is required."
"STACKMGR","6","SWITCH_ADDED_SDM","Switch [dec] has been ADDED to the stack (SDM_MISMATCH)","The specified switch has been added to the stack.","No action is required."
"STACKMGR","6","SWITCH_ADDED_VM","Switch [dec] has been ADDED to the stack (VERSION_MISMATCH)","The specified switch has been added to the stack.","No action is required."
"STACKMGR","6","SWITCH_READY","Switch [dec] is READY","The specified switch is in the ready state.","No action is required."
"STACKMGR","6","SWITCH_REMOVED","Switch [dec] has been REMOVED from the stack","The specified switch has been removed from the stack.","No action is required."
"STORM_CONTROL","2","UNAVAILABLE","Storm control shut down %s","Excessive traffic has been detected on a port that has been configured to be shutdown if a storm event is detected.","Once the source of the packet storm has been fixed, reenable the port using port configuration command."
"STORM_CONTROL","3","UNAVAILABLE","A %s storm detected on %s. A packet filter action has been applied on the interface.","The amount of traffic detected on the interface exceeded the configured threshold values. The system is filtering excess trafficwhen packet is received. Packet traffic is not being forwarded bythe system.","Determine and fix the root cause of the excessivetraffic on the interface."
"STORM_CONTROL","3","UNAVAILABLE","A packet storm was detected on %s. The interface has been disabled.","The amount of traffic detected on the interface exceeded the configured threshold values. Since the interface wasconfigured to be shutdown if a packet storm event is detected,it has been placed in error disable state.If automatic recovery is preferred, the error disable recoverymechanism can be used. Determine and fix the root cause ofthe excessive traffic on the interace.STAPL_OPEN MessagesThis section contains Standard Test And Programming Language (STAPL) processing messages.STAPL_OPEN-4Error Message    %STAPL_OPEN-4-ERROR_ALLOC: %Error: Can't allocate [dec] bytes for STAPL data Explanation    The system could not allocate the required memory to access the file.","Check the memory usage of the system and retry the operation."
"STAPL_OPEN","4","ERROR_OPEN","%Error: Can't open [chars]","The system is unable to open the specified file.","Ensure that the file name is correct. Enter the dir command to verify the file name."
"STAPL_OPEN","4","ERROR_READ","%Error: STAPL file [chars] read failed","An unknown error has occurred while the system was copying the STAPL program file to a local buffer.","Enter the del [chars] command to remove the file. Enter the copy command to recopy the file from a known good source to its desired destination [chars]. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"STAPL_OPEN","4","ERROR_SIZE","%Error: Bad file size [chars]","The file is too small or too large for a STAPL program file.","Enter the dir command and check the size of the file. Retry the operation."
"STORM_CONTROL","3","FILTERED","A [chars] storm detected on [chars]. A packet filter action has been applied on the interface.","The amount of traffic that has been detected on the interface has exceeded the configured threshold values. The system is filtering excess traffic when packets are received, and the system is not forwarding packet traffic.","Determine and fix the root cause of the excessive traffic on the interface."
"STP_ISSU","3","BUFFER","STP ISSU client failed to get buffer for message, error %d","The Spanning Tree Protocol (STP) ISSU client was unable to get buffer space for building a negotiation message. As a result, it cannot send the negotiation message to the standby unit and the standby unit cannot be brought up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"STP_ISSU","3","CAPABILITY","STP ISSU client %s","The STP ISSU client detected an error during capability negotiation. As a result, there is a mismatch in the client capability between the active and standby unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"STP_ISSU","3","CFM_MISMATCH","Unsupported CFM and STP configuration detected. Reloading standby","STP ISSU client observed MST PVST simuation capability negotiation failure while CFM was enabled. When this error happens, remove CFM configuration on the active and restart ISSU upgrade.","Issue the show tech-support command to gather data that may help identify the nature of the error. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"STP_ISSU","3","INIT","STP ISSU client initialization failed at %s, error %s","The STP ISSU client could not be initialized, this will cause catastrophic failure when an ISSU upgrade or downgrade is performed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"STP_ISSU","3","MSG_NOT_OK","STP ISSU client message %d is not compatible","The STP ISSU client received an incompatible message from the peer unit. The message cannot be processed by this unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"STP_ISSU","3","MSG_SIZE","STP ISSU client failed to get the message size for message %d","The STP ISSU client was unable to calculate the message size for the message specified. The client will be unable to send the message to the standby unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"STP_ISSU","3","POLICY","STP ISSU client message type %d is %s","The STP ISSU client received a message type that it does not support. A policy is applied to make the session compatible.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show issu session commands and your pertinent troubleshooting logs."
"STP_ISSU","3","SEND_FAILED","STP ISSU client failed to send a negotiation message, error %d","The STP ISSU client could not send a session negotiation message to the peer. As a result, the standby unit cannot be brought up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"STP_ISSU","3","SESSION","STP ISSU client %s","The STP ISSU client detected an error during a session negotiation with the peer unit. As a result, the standby unit cannot be brought up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"STP_ISSU","3","SESSION_UNREGISTRY","STP ISSU client failed to unregister session information. Error: %d (%s)","The STP ISSU client was unable to unregister session information.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"STP_ISSU","3","TRANSFORM","STP ISSU client %s transform failed, error %s","The STP ISSU client could not transform the message. If the transmit transformation failed, the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, the checkpoint message cannot be applied on the standby unit. In either case, the STP state will not be identical with the active unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"STP_SP","3","STP_MODE_CHANGE_NOT_ALLOWED","Unable to program port ASIC MAC match register on one or more slots. Cannot run change STP mode.","The Spanning Tree Protocol (STP) is unable to reserve and program the port ASIC MAC match registers because insufficient match registers are available. PVST and rapid-PVST cannot be run.","To make available more MAC match registers, disable other protocols that use the MAC match registers. You can view protocols that use port ASIC match registers by entering the remote command switch show platform mrm info command."
"STUN","2","UNAVAILABLE","Interface %s, no buffer available to %s","A memory shortage existed at the time that the configuration command was issued. This condition is rare and, under normal conditions, temporary.","Reconfigure the STUN group. If memory shortages persist, call your Cisco technical support representative for assistance."
"STUN","2","UNAVAILABLE","No memory available: %s","The requested operation failed because of a low memory condition.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"STUN","2","UNAVAILABLE","Please remove and redefine protocol group %d","An internal error occurred. The configuration is irregular.","Remove and reconfigure the STUN protocol group. Record the configuration and call your Cisco technical support representative for assistance."
"STUN","3","UNAVAILABLE","%s: bad len or unknown op, op %d, len %d","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"STUN","3","UNAVAILABLE","%s: peer %s, wrong magic, mine %x, theirs %x","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"STUN","3","UNAVAILABLE","%s: sent %s to %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"STUN","3","UNAVAILABLE","%s: sent %s to ([%u])%i","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"STUN","3","UNAVAILABLE","%s: wrong magic, mine %x, theirs %x (%d)","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"STUN","3","UNAVAILABLE","CONN: Peer %s, illegal state %d","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"STUN","3","UNAVAILABLE","CONN: bad connection (%d), peer: %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"STUN","3","UNAVAILABLE","Input idb not set","A software or hardware error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"STUN","3","UNAVAILABLE","passive open from %i(%d) - %d failed","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"STUN","4","UNAVAILABLE","%s: %s: %s, op %x, len %d","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"STUN","4","UNAVAILABLE","Cannot define duplicate route on the same group","This route command is defined on another interface belonging to the same group. Cannot define duplicate route on the same group","Consider defining a new group and moving this interface onto that group"
"STUN","4","UNAVAILABLE","Peer %s, wrong state %d (%d)","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"STUN","6","UNAVAILABLE","%s %s, %i(%d)","This route closed a STUN connection with a remote peer.","Examine this router to see why it closed this connection with this peer. (This can be caused by normal events, such as reconfiguration.)"
"STUN","6","UNAVAILABLE","%s: peer %s opened, [previous state %s]","A connection attempt to a remote peer completed successfully (OPENED, PASSIVE-OPEN) or is in the process of being opened (OPENING). This is good, expected behavior.","LOG_STD_NO_ACTION"
"STUN","6","UNAVAILABLE","CONN: opening peer %s, %d","A connection attempt to a remote peer completed successfully (OPENED, PASSIVE-OPEN) or is in the process of being opened (OPENING). This is good, expected behavior.","LOG_STD_NO_ACTION"
"STUN","6","UNAVAILABLE","CONN: peer %s open failed, %s [%u]","An attempt to connect to a remote TCP STUN peer failed.","Verify that the remote peer is accessible from this router, that it is running software capable of supporting STUN, and that it is configured correctly."
"STUN","6","UNAVAILABLE","PHDR: reconnect from peer %s","A remote peer reestablished a connection to this router.","LOG_STD_NO_ACTION"
"STUN","6","UNAVAILABLE","passive open %i(%d) - %d","A connection attempt to a remote peer completed successfully (OPENED, PASSIVE-OPEN) or is in the process of being opened (OPENING). This is good, expected behavior.","LOG_STD_NO_ACTION"
"STUN","6","UNAVAILABLE","peer %s closed [previous state %s]","A remote peer closed a STUN connection with this router.","Examine the other router to see why it closed this connection with this peer. (This can be caused by normal events, such as reconfiguration.)"
"STUN","6","UNAVAILABLE","shutting down peer %s on %s","A connection to a remote peer is being shut down. This is typically the result of user intervention in STUN reconfiguration or disabling. This is good, expected behavior.","LOG_STD_NO_ACTION."
"SUBSYS","2","UNAVAILABLE","Bad subsystem class (%d) - ignoring subsystem","A software consistency check failed.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SUBSYS","2","UNAVAILABLE","Bad subsystem version number (%d) - ignoring subsystem","A software consistency check failed.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SUBSYS","2","UNAVAILABLE","Kernel and subsystem version differ (%d.%d) - ignoring subsystem","A software consistency check failed.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SUBSYS","2","UNAVAILABLE","Maximum sequence depth exceeded (%d) by (%s)","A software or hardware error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SUBSYS","2","UNAVAILABLE","Subsystem (%s) has cross-class sequence for (%s)","A software or hardware error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SUBSYS","2","UNAVAILABLE","Subsystem (%s) needs subsystem (%s) to start","A software consistency check failed.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SUBSYS","3","UNAVAILABLE","The %s class subsystem %s was being initialized.","In all Cisco products the first 256 bytes of memory is unused and off limits. Newer platforms have hardware to immediately trap reads or writes to this area. Older platforms periodically perform checks on this memory. This message appears only on older platforms and indicates that this off limits memory area was modified.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SUBSYS","3","UNAVAILABLE","The API %s has no lookup hook for subsystems.","This process uses the named API, but the process initialization code could not find the subsystem-initialization hook for this API. Process initialization cannot proceed without all hooks being present.","Copy the error message exactly as it appears, and report it to your technical support representative, along with output from 'show tech'."
"SUBSYS","3","UNAVAILABLE","The subsys class %d(%s) has no initialization order.","The specified class subsystem has an unknown initialization order.","Copy the error message exactly as it appears, and report it to your technical support representative, along with output from 'show tech'."
"STP_SP","2","STP_EARL_MR_PROG_FAIL","Failed to program the EARL match register for STP.","The STP SSTP MAC address needs to be programmed in the Earl match register for normal STP operations. There are a limited number of Earl match registers. This messages indicates that either a SW error occured or the HW resource is not available.","Please review the configuration guidelines for the switch features. You can try rebooting the switch. If issue persists, please contact the Cisco Technical Support for further assistance."
"SUBSYS","3","UNORDERED","The subsys class [dec]([chars]) has no initialization order.","The specified class subsystem has an unknown initialization order.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SUPERVISOR","4","UNAVAILABLE","%s","The system found unexpected message in CPU Queues","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SUPERVISOR","4","UNAVAILABLE","%s","The system has detected a condition when no static packets are present for a CPU Queue","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SUPERVISOR","4","UNAVAILABLE","%s","The system has detected and corrected the condition: one of CPU is causing Head of Line blocking for other CPU Queues","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SUPERVISOR","4","UNAVAILABLE","%s","The system has detected error while disabling CPU Queues","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SUPERVISOR","4","UNAVAILABLE","%s","The system has received a static pak and freed it in the RX path","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SUPERVISOR","4","UNAVAILABLE","%s","There was a buffer/fifo overrun","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SUPERVISOR","4","UNAVAILABLE","Trying to send larger than supported packet size %s","There is a possible buffer/fifo overrun","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SUPERVISOR","3","FATAL","[chars]","An internal error occurred in the supervisor engine ASIC.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SUP_LINE_CARD_COMPATIBILITY","6","SW_VERSION_MISMATCH","[chars]","Compatibility mismatch between software versions of Line Card and Supervisor. Card allowed to bootup.","No action is required."
"SUPQ","3","THROTTLE_CPU_QUEUE","Invalid application ID [dec] used for throttling","An application has passed an invalid application ID to the facility that is used for throttle checking operations.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SUPQ","4","CPUHB_RECV_STARVE","[chars]","The system has detected that messages directed for the CPU are being delayed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SUPQ","4","CPUHB_SLOW_TRANSMIT","[chars]","The interface is no longer transmitting at an optimal speed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SUPQ","4","CPUHB_TX_FAIL","[chars]","The system is discarding system status or operational messages (heartbeat messages).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SUPQ","4","PORT_QUEUE_STUCK","Port queue Stuck for asic [dec] port [dec] queue [dec]","The system has detected that the port queue could not be cleared in a reasonable time.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SUPQ","4","RECV_QUEUE_STUCK","Receive queue Stuck for asic [dec] queue [dec]","The system has detected that the receive queue could not be cleared in a reasonable time.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SW56","1","UNAVAILABLE","%s","Failed SW56 Initialization. Most likely because lacking of memory","The amount of memory available in the router may not be sufficient. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SW56","3","UNAVAILABLE","%s","Failed to send message to internal software process","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SUPW_PROCMIB","3","IPC_PORTOPEN_FAIL","Failed to open port while connecting to process statistics: error code = [chars]","An error occurred during an attempt to open a port for an IPC message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SUPW_PROCMIB","3","IPC_TRANSMIT_FAIL","Failed to send process statistics update : error code = [chars]","An error occurred during an attempt to send an IPC message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SUPW_PROCMIB","3","MALLOC_FAILURE_IPC","Failed to allocate IPC message to contact process","A memory allocation failure has occurred during the processing of an IPC message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SVCLC","2","MAJORTEMP","Module [dec] CPU[dec] has exceeded its allowed operating temperature. (current temp=[dec]C)  Module will be shut down immediately","The specified service line card in the system has sent a thermal shutdown request to the supervisor engine. The first [dec] is the module number, the second [dec] is the CPU number, and the third [dec] is the temperature.","Determine if the environment is too hot. If the environment is not too hot, replace the hardware."
"SVCLC","4","MINORTEMP","Module [dec] CPU[dec] has exceeded its normal operating temperature. (current temp=[dec]C)","The specified CPU on the specified service line card is too hot. The first [dec] is the module number, the second [dec] is the CPU number, and the third [dec] is the temperature.","Determine if the environment is too hot. If the environment is not too hot, replace the hardware."
"SVCLC","4","TEMPRECOVER","Module [dec] CPU[dec] has returned to its normal operating temperature. (current temp=[dec]C)","The specified service line card in the system has sent a thermal recovery event to the supervisor engine. The first [dec] is the module number, the second [dec] is the CPU number, and the third [dec] is the temperature.","No action is required."
"SVCLC","5","INTDOWN","mod [dec] failed to bring up all interfaces","One or more of the module interfaces failed to come up.","Reset the module."
"SVCLC","5","SVCLCMULTI","Group [dec] being tied to more than one module","The specified group is tied to multiple service modules. A group should not be associated with more than one service module unless a failover configuration is being used.","If a failover configuration is in use, no action is required. Otherwise enter the show svclc module command to find out which group is being tied to more than one module. Then remove multiple associations by entering the no svclc module mod vlan-group group command."
"SVCLC","5","SVCLCNTP","Could not update clock on the module [dec], rc is [dec]","Either the line card or the Cisco IOS software encountered some problems while sending a clock update from Cisco IOS to the line card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SVCLC","5","SVCLCSCP","Service module SCP communication failed for module [dec], subopcode is [dec]","Either the line card or the Cisco IOS software encountered some problems while communicating through SCP channels.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SVCLC","5","SVCLCVTPMODE","VTP mode is set to non-transparent","VTP mode is not transparent, so VTP may dynamically modify VLANs, including those that are associated with the service modules.","Change the VTP to transparent mode by entering the vtp mode transparent command."
"SW_DAI","4","ACL_DENY","[dec] Invalid ARPs ([chars]) on [chars], vlan [dec].([[enet]/[chars]/[enet]/[chars]/[time-of-day]C])","The switch has received ARP packets that are considered invalid by ARP inspection. The packets are invalid, and their presence indicates that administratively denied packets have been seen in the network. This log message shows up when packet(s) have been denied by ACLs either explicitly or implicitly (with static ACL configuration). The presence of these packets indicates that man-in-the-middle attack(s) may have been attempted in the network.","This is an informational message only. No action is required."
"SW_DAI","4","DHCP_SNOOPING_DENY","[dec] Invalid ARPs ([chars]) on [chars], vlan [dec].([[enet]/[chars]/[enet]/[chars]/[time-of-day]C])","The switch has received ARP packets that are considered invalid by ARP inspection. The packets are invalid, and their presence may be an indication of man-in-the-middle attacks being attempted in the network. This message is logged when the sender's IP and MAC binding for the received VLAN is not present in the DHCP snooping database. The first [chars] is either Req (request) or Res (response), and the second [chars] is the short name of the ingress interface. The second [dec] is the ingress VLAN ID. [enet]/[chars]/[enet]/[chars]/[time-of-day] is the MAC address of the sender, the IP address of the sender, the MAC address of the target, the IP address of the target, and the time of day.","This is an informational message only. No action is required."
"SW_DAI","4","INVALID_ARP","[dec] Invalid ARPs ([chars]) on [chars], vlan [dec].([[enet]/[chars]/[enet]/[chars]/[time-of-day]C])","The switch has received ARP packets that are considered invalid by ARP inspection. The packets do not pass one or more validation checks of the source or destination MAC address or the IP address. The first [dec] is the number of invalid ARP packets. The first [chars] is either Req (request), Res (response), or Invalid Opcode. The second [chars] is the short name of the ingress interface. The second [dec] is the ingress VLAN ID. [enet]/[chars]/[enet]/[chars]/[time-of-day] is the MAC address of the sender, the IP address of the sender, the MAC address of the target, the IP address of the target, and the time of day.","This is an informational message only. No action is required."
"SW_DAI","4","PACKET_BURST_RATE_EXCEEDED","[dec] packets received in [dec] seconds on [chars].","The switch has received the given number of ARP packets in the specified burst interval. The interface is in the error-disabled state when the switch receives packets at a higher rate than the configured packet rate every second over the configured burst interval. The message is logged just before the interface is error disabled and if the configured burst interval is more than a second. The first [dec] is the number of packets, the second [dec] is the number of seconds, and [chars] is the affected interface.","This is an informational message only. No action is required."
"SW_DAI","4","PACKET_RATE_EXCEEDED","[dec] packets received in [dec] milliseconds on [chars].","The switch has received the specified number of ARP packets in the specified time on the specified interface. This message is logged just before the port is error-disabled because of the exceeded packet rate. This message also is logged when the burst interval is set to 1 second.","This is an informational message only. No action is required."
"SW_DAI","4","SPECIAL_LOG_ENTRY","[dec] Invalid ARP packets [[time-of-day]C]","The switch has received ARP packets considered invalid by ARP inspection. The packets are invalid, and their presence may be an indication of man-in-the-middle attacks being attempted in the network. This message differs from other messages in that while the others can be used to provide as much information about the packet as possible, this message is used as a general message when the rate of incoming packets exceeds the DAI logging rate.","This is an informational message only. No action is required."
"SW_DAI","6","ACL_PERMIT","[dec] ARPs ([chars]) on [chars], vlan [dec].([[enet]/[chars]/[enet]/[chars]/[time-of-day]C])","The switch has received ARP packets that have been permitted as a result of an ACL match.","This is an informational message only. No action is required."
"SW_DAI","6","DHCP_SNOOPING_PERMIT","[dec] ARPs ([chars]) on [chars], vlan [dec].([[enet]/[chars]/[enet]/[chars]/[time-of-day]C])","The switch has received ARP packets that have been permitted because the sender's IP and MAC address match against the DHCP snooping database for the received VLAN. The first [dec] is the number of valid ARP packets. The first [chars] is either Req (request) or Res (response), and the second [chars] is the short name of the ingress interface. The second [dec] is the ingress VLAN ID. [enet]/[chars]/[enet]/[chars]/[time-of-day] is the MAC address of the sender, the IP address of the sender, the MAC address of the target, the IP address of the target, and the time of day.","This is an informational message only. No action is required."
"SWEPA","6","EPA_EXP_RUNNING","Exp Running ....","The EXP process is running.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SWEPA","6","EPA_EXP_TIMER_EXPIRED","Exp Timer Expired!","The EXP timer has expired.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SWEPA","6","FAILED_TO_ALLOCATE_ENCRYPT_QUE","Failed to allocate the encrypt queue.","The encryption queue could not be allocated.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SWEPA","6","FAILED_TO_START_DES_PROCESS","Failed to start DES process","The DES process has failed to start.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SWEPA","6","FAILED_TO_START_EXP_PROCESS","Failed to start EXP process","The EXP process has failed to start.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SWEPA","6","INIT_SW_EPA_IDB","Init swepa idb start ...","The software encryption port adapter information descriptor block (IDB) is being initialized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SWEPA","6","START_DES_PROCESS","DES process start ...","The DES process has started.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SWEPA","6","START_EXP_PROCESS","EXP process start ...","The EXP process has started.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SWITCH","1","RF_REGISTRTN_FAILED","unable to register switch driver client to RF","The switch driver client could not be registered to the redundancy facility (RF).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SWITCHOVER","6","LC_HA_UNAWARE","Line card (type [hex]) in slot [dec] is not confgured HA mode aware","The line card in the specified slot does not support the configured RP redundancy mode. The line card will be reset and reinitialized during RP failover.","No action is required."
"SWITCH_QOS_TB","5","TRUST_DEVICE_DETECTED","[chars] detected on port [chars], port trust enabled.","The trusted boundary facility has detected a device that matches the trusted device setting for the port, and the port trust state has been modified.","No action is required."
"SWITCH_QOS_TB","5","TRUST_DEVICE_LOST","[chars] no longer detected on port [chars], port set to untrusted.","The trusted boundary facility has lost contact with a trusted device, and has set the port trust state to untrusted.","No action is required."
"SWITCH_SPAN_ISSU","3","BUFFER","span switch ISSU client failed to get buffer for message, error %d","The SPAN switch ISSU client was unable to get a buffer for building a negotiation message. As a result, it cannot send the negotiation message to the standby unit and the standby unit cannot be brought up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"SWITCH_SPAN_ISSU","3","CAPABILITY","span switch ISSU client %s","The SPAN switch ISSU client detected an error during capability negotiation. As a result, there is a mismatch in the client capability between the active and standby unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"SWITCH_SPAN_ISSU","3","INIT","span switch ISSU client initialization failed at %s, error %s","The SPAN switch ISSU client could not be initialized. This condition will cause a catastrophic failure when an ISSU upgrade or downgrade is performed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SWITCH_SPAN_ISSU","3","MSG_NOT_OK","span switch ISSU client message %d is not compatible","The SPAN switch ISSU client received an incompatible message from the peer unit. The message cannot be processed by this unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"SWITCH_SPAN_ISSU","3","MSG_SIZE","span switch ISSU client failed to get the message size for message %d","The SPAN switch ISSU client was unable to calculate the message size for the message specified. The client will be unable to send the message to the standby unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"SWITCH_SPAN_ISSU","3","POLICY","span switch ISSU client message type %d is %s","The SPAN switch ISSU client received a message type that it does not support. A policy is applied to make the session compatible.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu session commands and your pertinent troubleshooting logs."
"SWITCH_SPAN_ISSU","3","SEND_FAILED","span switch ISSU client failed to send a negotiation message, error %d","The SPAN switch ISSU client could not send a session negotiation message to the peer. As a result, the standby unit cannot be brought up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"SWITCH_SPAN_ISSU","3","SESSION","span switch ISSU client %s","The SPAN switch ISSU client detected an error during a session negotiation with the peer unit. As a result, the standby unit cannot be brought up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"SWITCH_SPAN_ISSU","3","TRANSFORM","span switch ISSU client %s transform failed, error %s","The SPAN switch ISSU client could not transform the message. If the transmit transformation failed, the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, the checkpoint message cannot be applied on the standby unit. In either case, the SPAN switch state will not be identical with the active unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"SW_DAI","4","UNAVAILABLE","%d packets received in %d milliseconds on %s.","The switch has received the given number of ARP packets in the given duration on the given interface. This message is logged just before the port is err-disabled because of exceeded packet rate. And this message is logged when the burst interval is set to 1 second.","LOT_STD_NO_ACTION"
"SW_DAI","4","UNAVAILABLE","%d packets received in %d seconds on %s.","The switch has received the given number of ARP packets in the specified burst interval. The interface is errdisabled when the switch receives packets at a rate higher than the configured packet rate every second over the configured burst interval. The message is logged just before the interface is err-disabled, and if the configured burst interval is more than a second.","LOT_STD_NO_ACTION"
"SW_DAI","4","UNAVAILABLE","%ld Invalid ARP packets [%CC]","The switch has received ARP packets considered invalid by ARP inspection. The packets are bogus, and their presence may be an indication of man-in-the-middle attacks being attempted in the network. This message differs from other messages in that while the other can be used to provide as much information of the packet as possible, this message is used as a catch all message when the rate of incoming packets exceed DAI logging rate.","LOT_STD_NO_ACTION"
"SW_DAI","4","UNAVAILABLE","%ld Invalid ARPs (%s) on %s, vlan %d.([%e/%s/%e/%s/%CC])","The switch has received ARP packets considered invalid by ARP inspection. The packets are bogus, and their presence indicates that administratively denied packets have been seen in the network. This log message shows up when packet(s) have been denied by acls either explicitly or implicitly(with static acl configuration). The presence of these packets indicates that man-in-the-middle attack(s) may have been attempted in the network.","LOG_STD_NO_ACTION"
"SW_DAI","4","UNAVAILABLE","%ld Invalid ARPs (%s) on %s, vlan %d.([%e/%s/%e/%s/%CC])","The switch has received ARP packets considered invalid by ARP inspection. The packets are bogus, and their presence may be an indication of man-in-the-middle attacks being attempted in the network. This message is logged when the senders ip and mac binding for the received vlan is not present in the dhcp snooping database.","LOG_STD_NO_ACTION"
"SW_DAI","4","UNAVAILABLE","%ld Invalid ARPs (%s) on %s, vlan %d.([%e/%s/%e/%s/%CC])","The switch has received ARP packets considered invalid by ARP inspection. The packets are bogus, and they do not pass one or more of source mac or destination mac or IP validation checks.","LOG_STD_NO_ACTION"
"SW_DAI","6","UNAVAILABLE","%ld ARPs (%s) on %s, vlan %d.([%e/%s/%e/%s/%CC])","The switch has received ARP packets that have been permitted as a result of ACL match.","LOG_STD_NO_ACTION"
"SW_DAI","6","UNAVAILABLE","%ld ARPs (%s) on %s, vlan %d.([%e/%s/%e/%s/%CC])","The switch has received ARP packets that have been permitted as a result of senders IP and MAC address match against the dhcp snooping database for the received vlan.","LOG_STD_NO_ACTION"
"SW_MGR","3","CM_ERROR","Connection Manager Error - [chars].","An error has occurred in the segment switch connection manager.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SW_MGR","3","CM_ERROR_CLASS","Connection Manager Error: Class [chars]: - [chars].","An error has occurred in the connection manager.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SW_MGR","3","CM_ERROR_FEATURE","Connection Manager Feature Error: (%s) - %s.","A segment switch connection manager feature class error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SW_MGR","3","CM_ERROR_FEATURE_CLASS","Connection Manager Feature Error: Class %s: (%s) - %s.","A segment switch connection manager feature error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SW_MGR","3","FHM_ERROR","SSM Feature Handler Manager Error - %s.","A feature handler manager error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SW_MGR","3","INVALID_HANDLE","Segment Manager Error - Invalid [chars] handle - [dec].","The connection manager encountered an invalid handle.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SW_MGR","3","INVALID_SEGMENT","Segment Switch Manager Error - Invalid segment - [chars].","The segment switch manager encountered an invalid segment.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SW_MGR","3","SM_ERROR","Segment Manager Error - [chars].","An error has occurred in the segment manager.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SW_MGR","3","SSM_SEG_ISSU","SSM Segment ISSU: [chars] not supported.","ISSU of this SSM Segment is not supported.","Not Available."
"SW_VLAN","3","UNAVAILABLE","VLAN Manager synchronization failure with Port Manager over %s","Due to lack of ready pool space, the VLAN manager dropped a notification from the Port Manager as indicated by the message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SW_VLAN","3","UNAVAILABLE","VTP protocol code internal error: %s","VTP protocol code encountered an unexpected error will processing configuration request, packet, or timer expiration.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SW_VLAN","3","VLAN_PM_NOTIFICATION_FAILURE","VLAN Manager synchronization failure with Port Manager over %s","Due to lack of ready pool space, the VLAN manager dropped a notification from the Port Manager as indicated by the message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SW_VLAN","3","VTP_PROTOCOL_ERROR","VTP protocol code internal error: %s","VTP protocol code encountered an unexpected error will processing configuration request, packet, or timer expiration.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SW_VLAN","4","BAD_STARTUP_VLAN_CONFIG_FILE","Failed to configure VLAN from startup-config. Fallback to use VLAN configuration file from non-volatile memory","VLAN software failed to use VLAN configuration from startup-config file. It will fallback to use the binary VLAN configuration file in non-volatile memory.","Check the usage of the VLAN in the active and standby device to determine whether the VLAN is valid. Check the memory usage in the standby device. Unconfigure the feature that occupies more memory and retry the VLAN creation operation. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SW_VLAN","4","BAD_VLAN_CONFIGURATION_FILE","VLAN configuration file contained incorrect verification word: 0x%x","The VLAN configuration file read by the VLAN manager did not begin with correct value which would indicate a valid VLAN configuration file. Thus, it has been rejected.","Check the usage of the VLAN in the active and standby device to determine whether the VLAN is valid. Check the memory usage in the standby device. Unconfigure the feature that occupies more memory and retry the VLAN creation operation. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SW_VLAN","4","BAD_VLAN_CONFIGURATION_FILE_VERSION","VLAN configuration file contained unknown file version: %d","The VLAN configuration file read by the VLAN manager contained an unrecognized file version number. (This may indicate an attempt to regress to an older version of the VLAN manager software.)","Check the usage of the VLAN in the active and standby device to determine whether the VLAN is valid. Check the memory usage in the standby device. Unconfigure the feature that occupies more memory and retry the VLAN creation operation. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SW_VLAN","4","BAD_VLAN_TIMER_ACTIVE_VALUE","Encountered incorrect VLAN timer active value: %s","Due to a software error, a VLAN timer was dectected active when it should have been inactive or inactive when it should have been active.","Check the usage of the VLAN in the active and standby device to determine whether the VLAN is valid. Check the memory usage in the standby device. Unconfigure the feature that occupies more memory and retry the VLAN creation operation. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SW_VLAN","4","EXT_VLAN_INTERNAL_ERROR","Extended VLAN manager received an internal error %d from %s: %s","An unexpected error code was received by the VLAN Manager from the extended VLAN configuration software.","Check the usage of the VLAN in the active and standby device to determine whether the VLAN is valid. Check the memory usage in the standby device. Unconfigure the feature that occupies more memory and retry the VLAN creation operation. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SW_VLAN","4","IFS_FAILURE","VLAN manager encountered file operation error: call = %s / file = %s / code = %d (%s) / bytes transfered = %d","The VLAN manager received an unexpected error return from a IOS file system call.","Check the usage of the VLAN in the active and standby device to determine whether the VLAN is valid. Check the memory usage in the standby device. Unconfigure the feature that occupies more memory and retry the VLAN creation operation. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SW_VLAN","4","STARTUP_EXT_VLAN_CONFIG_FILE_FAILED","Failed to configure extended range VLAN from startup-config. Error %s","VLAN software failed to use extended VLAN configuration from startup-config file. All extended range VLANs configuration will be lost after system boot up.","Check the usage of the VLAN in the active and standby device to determine whether the VLAN is valid. Check the memory usage in the standby device. Unconfigure the feature that occupies more memory and retry the VLAN creation operation. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SW_VLAN","4","VLAN_ADD_FAIL","Failed to add VLAN [dec] to vlan database: [chars]","The specified VLAN could not be added to the VLAN database. The platform may not allow the addition or there may be insufficient memory to expand the VLAN database.","Check the usage of the VLAN in the active and standby device to determine whether the VLAN is valid. Check the memory usage in the standby device. Unconfigure the feature that occupies more memory and retry the VLAN creation operation. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SW_VLAN","4","VLAN_CREATE_FAIL","Failed to create VLANs [chars]: [chars]","The specified VLANs could not be created. The VLAN manager called a VLAN database routine to create one or more VLANs, but the port manager failed the VLAN creation requests. A possible cause of this error is that the VLANs already exist in the port manager as internal VLANs.","Check the internal VLAN usage by entering the show vlan internal usage command. Unconfigure the feature that occupies the internal VLAN and retry the VLAN creation operation. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SW_VLAN","4","VLANMGR_INVALID_DATABASE_DATA","VLAN MANAGER received bad data of type %s: value %d from function %s","The VLAN manager received invalid data from a VLAN configuration database process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SW_VLAN","4","VTP_DB_INVALID_VLANID","Invalid VLAN ID [dec] found in VTP database download","An invalid VLAN ID was detected in the VTP database during the download of the VTP configuration file. This condition indicates that the VTP configuration file in NVRAM is corrupted.","Save a copy of the vlan.dat file that includes the invalid VLAN ID to help investigate the condition. Copy the message exactly as it appears on the console or in the system log. Enter the show vtp status and the show vlan commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SW_VLAN","4","VTP_DB_SIZE_CHECK_FAILED","The %s VTP database of length %d cannot be supported by the system","The VLAN trunking protocol (VTP) database size is larger than the system can support.","Reduce the database size by decreasing the configuration parameters. For example, reduce the size of vlan-names."
"SW_VLAN","4","VTP_INTERNAL_ERROR","VLAN manager received an internal error %d from vtp function %s: %s","An unexpected error code was received by the VLAN Manager from the VTP configuration software.","Save a copy of the vlan.dat file that includes the invalid VLAN ID to help investigate the condition. Copy the message exactly as it appears on the console or in the system log. Enter the show vtp status and the show vlan commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SW_VLAN","4","VTP_SEM_BUSY","VTP semaphore is unavailable for function %s. Semaphore locked by %s","The VTP database is currently locked by another task and is not available. Users should retry the operation sometime later.","Save a copy of the vlan.dat file that includes the invalid VLAN ID to help investigate the condition. Copy the message exactly as it appears on the console or in the system log. Enter the show vtp status and the show vlan commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SW_VLAN","4","VTP_USER_NOTIFICATION","VTP protocol user notification: %s","VTP protocol code encountered an unusual diagnostic situation which the user should be made aware of.","Save a copy of the vlan.dat file that includes the invalid VLAN ID to help investigate the condition. Copy the message exactly as it appears on the console or in the system log. Enter the show vtp status and the show vlan commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SW_VLAN","4","VTP_PRIMARY_SERVER_CHG","%e has become the primary server for the %s VTP feature","The primary server status has changed and the indicated device has become the primary server for the indicated VTP feature.","No action is required."
"SW_VLAN","4","VTP_SEM_BUSY","VTP semaphore is unavailable for function [chars]. Semaphore locked by [chars]","The VTP database is currently locked by another task and is not available.","Retry the operation later. If this condition recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SW_VLAN","6","VTP_DOMAIN_NAME_CHG","VTP domain name changed to [chars].","The VTP domain name was changed through configuration to the name specified in the message. A management domain is the naming scope of a VLAN name. Each VLAN has a name that is unique within the management domain.","This is an informational message only. No action is required."
"SW_VLAN","6","OLD_CONFIG_FILE_READ","Old version [dec] VLAN configuration file detected and read OK. Version [dec] files will be written in the future.","This message indicates that the VLAN software detected an old version of the VLAN configuration file format. The software was able to interpret the file with no problems but will create files using the new format in the future. The first [dec] is the old version number, and the second [dec] is the new version number.","No action is required."
"SW_VLAN","6","VTP_MODE_CHANGE","VLAN manager changing device mode from [chars] to [chars].","Some switch devices must automatically change VTP device modes upon receipt of a VLAN configuration database containing more than a set number of VLANs, depending on the device. This message indicates that such a spontaneous conversion has occurred, what the previous mode was, and what the current mode is. [chars] is the VTP device mode. In VTP server mode, the VLAN manager must record each change of VTP configuration and each change of device configuration relating to VTP (such as mode changes, device domain name changes, and password changes) to non-volatile storage using IFS system calls. If a system call fails, the device must spontaneously convert to the VTP client mode. Call failures are usually the result of a hardware failure of the non-volatile storage system, which may require replacement. Other possible causes include software bugs or, in the case of TFTP storage, a transient network or TFTP server failure.","No action is required."
"SW_VLAN","6","VTP_PRUNING_CHANGE","VTP Operational Pruning [chars].","VTP operational pruning has been enabled or disabled as shown in [chars], due to either an administrative pruning change, a VTP mode change, or VTP configuration propagation. To view the reason for the change, enter the show vtp status command.","No action is required."
"SW_VLAN_RF","3","CREATE_PROCESS","Switch Vlan RF client failed to create %s process","Switch Vlan RF client could not create a process, this will cause bulk sync to fail.","Save a copy of the vlan.dat file that includes the invalid VLAN ID to help investigate the condition. Copy the message exactly as it appears on the console or in the system log. Enter the show vtp status and the show vlan commands to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SW_VLAN-SP","6","VTP_DOMAIN_NAME_CHG","VTP domain name changed to %s.","The VTP domain name was changed through configuration to the name specified in the message. A management domain is the naming scope of a VLAN name. Each VLAN has a name that is unique within the management domain.","No action is required."
"SW_VLAN_ISSU","2","GET_BUFFER","Switch Vlan ISSU client failed to get buffer for message. Error: %d (%s)","The switch VLAN ISSU client was unable to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"SW_VLAN_ISSU","2","INIT","Switch Vlan ISSU client initialization failed to %s. Error: %d (%s)","The switch VLAN ISSU client could not be initialized. This initialization failure must be addressed before an in-service software upgrade or downgrade can be performed successfully. Otherwise, a software upgrade or downgrade will result in downtime.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SW_VLAN_ISSU","2","SEND_NEGO_FAILED","Switch Vlan ISSU client failed to send negotiation message. Error: %d (%s)","The switch VLAN ISSU client was unable to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"SW_VLAN_ISSU","2","SESSION_NEGO","Switch Vlan ISSU client encountered unexpected client nego_done. Error: %d (%s)","An ISSU-compliant client transitions through a series of internal states. The switch VLAN ISSU client encountered a client negotiation done state that was unexpected. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"SW_VLAN_ISSU","2","SESSION_REGISTRY","Switch Vlan ISSU client failed to register session information. Error: %d (%s)","The switch VLAN ISSU client was unable to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"SW_VLAN_ISSU","3","CAP_INVALID_SIZE","Switch Vlan ISSU client capability list is empty.","The switch VLAN ISSU client capability exchange list is empty, which is an invalid condition.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu capability entires commands and your pertinent troubleshooting logs."
"SW_VLAN_ISSU","3","CAP_NOT_COMPATIBLE","Switch Vlan ISSU client capability exchange result incompatible.","Based on the results of the capability exchange, the switch VLAN ISSU client is not compatible with the peer.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"SW_VLAN_ISSU","3","INVALID_SESSION","Switch Vlan ISSU client does not have a valid registered session.","The switch VLAN ISSU client does not have a valid registered session.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"SW_VLAN_ISSU","3","MSG_NOT_COMPATIBLE_WITH_PEER","'Message Type %d' is not supported by Switch Vlan ISSU client at peer","The switch VLAN ISSU client at the peer supervisor is not compatible for this message type. The switch VLAN client will be marked as incompatible with the peer.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"SW_VLAN_ISSU","3","MSG_NOT_OK","Switch Vlan ISSU client 'Message Type %d' is not compatible","The switch VLAN ISSU client received an incompatible message from the peer device. The message cannot be processed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"SW_VLAN_ISSU","3","MSG_SIZE","Switch Vlan ISSU client failed to get the MTU for Message Type %d. Error: %d (%s)","The switch VLAN ISSU client was unable to calculate the MTU for the specified message. As a result, the client is unable to send the message to the standby device.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"SW_VLAN_ISSU","3","SESSION_UNREGISTRY","Switch Vlan ISSU client failed to unregister session information. Error: %d (%s)","The switch VLAN ISSU client was unable to unregister session information.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"SW_VLAN_ISSU","3","TRANSFORM_FAIL","Switch Vlan ISSU client %s transform failed for 'Message Type %d'. Error: %d (%s)","The switch VLAN ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In either case, the switch VLAN state between the active device and the standby device is not identical.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"SW_VLAN_RF","3","CREATE_PROCESS","Switch Vlan RF client failed to create %s process","The switch VLAN redundancy facility (RF) client could not create a process. As a result, bulk synchronization will fail.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYS","1","UNAVAILABLE","CCA Detected System Error, code = %d","CCA has detected a severe system software error. This condition is usually caused by one of the components using CCA or by the interaction among components using CCA.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYS","1","UNAVAILABLE","System detected OVERTEMPERATURE condition. Please resolve cooling problem immediately!","The environmental monitor detected a high-temperature condition.","Make sure that the room temperature is not too high and that air flow to the card is not blocked. If this condition persists, the environmental monitor might shut down the system. Call your technical support representative for assistance, if necessary."
"SYS","1","UNAVAILABLE","Threshold: %s CPU Utilization(Total/Intr) %d%%/%d%%.","CPU usage has returned to normal after crossing over from a threshold of high usage. Any process that was disabled during the period of high CPU use can now be enabled.","No action is required."
"SYS","1","UNAVAILABLE","Threshold: %s CPU Utilization(Total/Intr): %d%%/%d%%, Top 3 processes(Pid/Util): %d/%d%%, %d/%d%%, %d/%d%%","The system is experiencing high CPU usage, possibly from a process that is using too much CPU. This condition demands immediate attention, or packets or calls may be dropped.","Enter the show processes CPU command to determine the CPU hogging process that is causing this condition and, if possible, disable the activity that is causing the CPU hog condition so that CPU utilization is reduced."
"SYS","2","BAD_BM_ARG","Invalid BM index boolean used as argument ([dec])","An illegal boolean manager index argument was referenced.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYS","2","CHUNKPARTIAL","Attempted to destroy partially full chunk, chunk [hex].","A software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYS","2","CHUNKSIBLINGDEST","Attempted to destroy a sibling chunk %x (%s).","A software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYS","2","FAILEDUPDATE","Failed to update Process id: %d in %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYS","2","IMMORTAL","Attempt to shut down management process [dec] ([chars]).","An attempt was made to shut down the specified management process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands, the stack trace, and your pertinent troubleshooting logs."
"SYS","2","INPUT_GETBUF","Bad getbuffer, bytes= [dec], for interface= [chars]","The software requested a buffer that is larger than the largest configured buffer size, or it requested a negative-sized buffer.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYS","2","MMAP","mmap failed for size %d bytes Caller PC 0x%x errno %d","Failed to allocate memory for the requested size.The memory could not be mapped because there is no memory.","This message may indicate either a logic error in the issuing component or it may indicate that a mmap failed to allocatecontiguous memory for the requested size. When reporting this message, copy the text exactly as it appears; include the asssociated stack trace; and report it to your technical support representative."
"SYS","2","NOPID","Process MIB is not aware of Process id: %d","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYS","2","NV_BAD_PTR","Bad NVRAM pointer. NV Header values are, nv: %p .textbase: %p .textsize: %d .magic: 0x%X .checksum: 0x%X .system_version: %d .textptr: %p v1_ptr: %p .priv: %p","A pointer corruption in NVRAM caused a failure in accessing the NVRAM.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYS","2","STACKMAGIC","Stackmagic corrupted for process %s, stackstart = %x magic = %x","An internal software error occurred.","If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
"SYS","2","STACKMMAP","Stack allocation mmap for IOStasks failed","An internal software error occurred.","If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
"SYS","2","SYSMEMINFO","System Memory: %luK total, %luK used, %luK free","This is an auxiliary message to several memory-related messages. It provides system memory information usage.","This message provides additional information only. Copy the error message exactly as it appears, and report it to your technical support representative as part of a previously printed error message."
"SYS","2","UNAVAILABLE","Bad chunk reference count, chunk %x data %x refcount %x alloc pc %x.","An inconsistency was detected while managing the chunk memory pool.The probability that this is a software error is close to 100 percent,but there could be a hardware problem with memory.","Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. Save any crashinfo or crashdump files. If the router has crashed, and was not configured to automatically reload, the router will need to be reloaded manually."
"SYS","2","UNAVAILABLE","Bad chunk reference count, chunk %x data %x.","An inconsistency was detected while managing the chunk memory pool.The probability that this is a software error is close to 100 percent,but there could be a hardware problem with memory.","Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. Save any crashinfo or crashdump files. If the router has crashed, and was not configured to automatically reload, the router will need to be reloaded manually."
"SYS","2","UNAVAILABLE","Bad free magic number in chunk header, chunk %x data %x chunk_freemagic %x","An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent, but there could be a hardware problem with memory.","Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. Save any crashinfo or crashdump files. If the router has crashed, and was not configured to automatically reload, the router will need to be reloaded manually."
"SYS","2","UNAVAILABLE","Bad getbuffer, bytes= %d","The software requested a buffer that is larger than the largest configured buffer size, or it requested a negative-sized buffer.","When reporting this condition, copy the error message text exactly as it appears; include the associated stack trace; and report it to your technical support representative."
"SYS","2","UNAVAILABLE","Bad getbuffer, bytes= %d, for interface= %s","The software requested a buffer that is larger than the largest configured buffer size, or it requested a negative-sized buffer.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYS","2","UNAVAILABLE","Bad magic number in chunk header, chunk %x data %x chunkmagic %x chunk_freemagic %x","An inconsistency was detected while managing the chunk memory pool. The probability that this is a software error is close to 100 percent, but there could be a hardware problem with memory.","Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. Save any crashinfo or crashdump files. If the router has crashed, and was not configured to automatically reload, the router will need to be reloaded manually."
"SYS","2","UNAVAILABLE","Bad parameter (%d) when calling to the allocator utility","Illegal parameter is used when called to allocator. may represent data some corruption.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","2","UNAVAILABLE","Bad pid %d for tty %t","An internal software error occurred.","If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
"SYS","2","UNAVAILABLE","Bad poolsize returned by the system : %u","System returns a non-optimal pool size. Need to change pool sizes","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","2","UNAVAILABLE","Bad refcount in %s, ptr=%x, count=%x","A reference count is used to track the usage of many data structures. A function increments the count when it begins to use a structure and decrements it when it finishes. When the count becomes zero, the data structure is freed. This message indicates that when the count was accessed, it was found to be negative which means that the data structure will not be freed until the system is reloaded.","If this messages recurs, copy it exactly as it appears; include the stack trace; and report it to your technical support representative."
"SYS","2","UNAVAILABLE","Buffer %x already in free pool %s","A block of memory at the indicated location is corrupt and/or has been erroneously freed twice.","If this message recurs, copy it exactly as it appears and the output of 'show buffer address ' for the given address as well as 'show buffer pool dump' for the given pool. Report it to your technical support representative."
"SYS","2","UNAVAILABLE","Buffer %x found in pool %x, should be in pool %x","A software error occurred.","Copy the message exactly as it appears, and report it your technical support representative."
"SYS","2","UNAVAILABLE","Buffer %x linked to itself in free pool %s","An internal software error occurred.","If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
"SYS","2","UNAVAILABLE","Buffer in list, ptr= %x","An internal software error occurred.","If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
"SYS","2","UNAVAILABLE","Buffer in list, ptr= %x, caller= %x","An internal software error occurred.","If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
"SYS","2","UNAVAILABLE","CCA Detected Logic Error, code = %d","CCA has detected a severe internal logic error. This condition is usually caused by one of the components using CCA or by the interaction among components using CCA.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYS","2","UNAVAILABLE","Can't create process with start address = %x","An internal software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","2","UNAVAILABLE","Chunk element size is more than 64k for %s","Chunk manager cannot function properly with big chunk elements","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","2","UNAVAILABLE","Could not expand chunk pool for %s. No memory available","There is not enough processor memory left to grow this chunk pool.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","2","UNAVAILABLE","Could not find the sibling to allocate memory from. Chunk %s, total free %d inuse %d.","An inconsistency was detected while managing the chunk memory pool.The probability that this is a software error is close to 100 percent,but there could be a hardware problem with memory.","Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. Save any crashinfo or crashdump files. If the router has crashed, and was not configured to automatically reload, the router will need to be reloaded manually."
"SYS","2","UNAVAILABLE","Could not return memory Neutrino via munmap at %lx, size %d errno %d","Failued to unmap memory memory at the indicated location. The memory could not be unmapped because it was allocated via mmap.","This message may indicate either a logic error in the issuing component or it may indicate that a portion of the memory management structures have been over written. When reporting this message, copy the text exactly as it appears; include the asssociated stack trace; and report it to your technical support representative."
"SYS","2","UNAVAILABLE","EXMEM %d: %s","The requested external memory allocator failed to be initialized. reasons are not clear.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","2","UNAVAILABLE","Error noticed in the sibling of the chunk %s, Chunk index : %d, Chunk real max : %d","A software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","2","UNAVAILABLE","Error: %s","A software Error occurred while decompressing the Image. The actual error is within the string of the error message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYS","2","UNAVAILABLE","Failed to update Process id: %d in %s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYS","2","UNAVAILABLE","Free a non allocated ptr %x size %d.","Trying to free a memory which not all of it marked as allocated.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","2","UNAVAILABLE","Generated configuration not backward compatible","The router has been configured to generate nonvolatile memory using the commands of an older software version. The current configuration of the router contains a command that cannot be saved using only the older command set.","Allow the router to save the configuration using the command set of the current software version, or remove the commands that cannot be saved using the older command set."
"SYS","2","UNAVAILABLE","INPUTQ set, but no IDB, ptr=%x","This message is issued when an attempt is made to alter the input queue count for a packet that should not be counted.","When reporting this condition, copy the text of the message exactly as it appears; include the associated stack trace; and report it to your technical support representative."
"SYS","2","UNAVAILABLE","Inconsistant counters for chunk : %stotal free %d/%d, total sibs %d/%d, total alloc %d/%d","System returns a non-optimal pool size. Need to change pool sizes","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","2","UNAVAILABLE","Invalid BM index boolean used as argument (%d)","An illegal boolean manager index argument was referenced","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","2","UNAVAILABLE","Invalid BM name","An illegal name string was registered with the BM","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","2","UNAVAILABLE","Invalid chunk header type %d for chunk %x, data %x","An inconsistency was detected while managing the chunk memory pool.The probability that this is a software error is close to 100 percent,but there could be a hardware problem with memory.","Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. Save any crashinfo or crashdump files. If the router has crashed, and was not configured to automatically reload, the router will need to be reloaded manually."
"SYS","2","UNAVAILABLE","Killing process %s, associated with line %d","A process associated with a tty line was killed by another process. The line may go dead","If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
"SYS","2","UNAVAILABLE","Killing process %s, pid %d again","An internal software error occurred.","If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
"SYS","2","UNAVAILABLE","Low-memory debug exception (limit=%u free=%u)","The router is configured to crash when total available IO memory drops below a specified threshold. That threshold has been reached. This may have occurred due to a memory leak or from supporting additional features.","If you suspect a memory leak, copy the message exactly as it appears and report it to your technical support representative. Otherwise, you may need to add memory or reduce the number of features you are trying to support."
"SYS","2","UNAVAILABLE","Low-memory debug exception (limit=%u free=%u)","The router is configured to crash when total available processor memory drops below a specified threshold. That threshold has been reached. This may have occurred due to a memory leak or from supporting additional features.","If you suspect a memory leak, copy the message exactly as it appears and report it to your technical support representative. Otherwise, you may need to add memory or reduce the number of features you are trying to support."
"SYS","2","UNAVAILABLE","Memory allocation of %u bytes failed from %#x, alignment %d Pool: %s Free: %u Cause: %s Alternate Pool: %s Free: %u Cause: %s","The requested memory allocation is not available from the specified memory pool. The current system configuration, network environment, or possibly a software error may have exhausted or fragmented the router's memory.","If you suspect a software error, copy the error message exactly as it appears on the colsole or in the system log, contact your technical supportrepresentative,and provide the representative with the gathered information. Otherwise, you may need to add more memory or reduce the number of features you are trying to support."
"SYS","2","UNAVAILABLE","Memory fragmentation check debug exception (fragment size %u)","The router is configured to crash when the largest available contiguous IO memory block drops below a specified threshold. That threshold has been reached. This may have occurred due to excessive memory thrashing or from supporting additional features.","If you suspect memory thrashing, copy the message exactly as it appears and report it to your technical support representative. Otherwise, you may need to add memory or reduce the number of features you are trying to support."
"SYS","2","UNAVAILABLE","Memory fragmentation check debug exception (fragment size %u)","The router is configured to crash when the largest available contiguous processor memory block drops below a specified threshold. That threshold has been reached. This may have occurred due to excessive memory thrashing or from supporting additional features.","If you suspect memory thrashing, copy the message exactly as it appears and report it to your technical support representative. Otherwise, you may need to add memory or reduce the number of features you are trying to support."
"SYS","2","UNAVAILABLE","Memory requested from Null Chunk","Chunk manager cannot allocate memory from NULL chunks","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","2","UNAVAILABLE","Message from %t(%s): %s","A user has used the 'send log' command to include a message on theconfigured logging destinations. Such messages can be used to helptag where user-initiated events occur during debugging.","This message is informational only."
"SYS","2","UNAVAILABLE","Multiple Signals are sent to a process %d","An internal software error occurred.","If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
"SYS","2","UNAVAILABLE","No memory available for %s %d","An operation could not be accomplished because of a low-memory condition. The current system configuration, network environment, or possibly a software error might have exhausted or fragmented the router's memory.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a configuration that has more memory."
"SYS","2","UNAVAILABLE","No such process %d","An internal software error occurred.","If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
"SYS","2","UNAVAILABLE","Process %s has trashed stack, old size %d","An internal software error occurred.","If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
"SYS","2","UNAVAILABLE","Process MIB is not aware of Process id: %d","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYS","2","UNAVAILABLE","Process aborted on invalid signal, signum = %d.","An attempt was made to send an invalid signal to another process.","If this message occurs more than once, report this message to your technical support representative."
"SYS","2","UNAVAILABLE","Process aborted on watchdog timeout, process = %s.%s","The indicated process ran for too long without relinquishing control. The system killed it as a runaway process.","This message may be realted to a combination of system load and configuration. When reporting this message, copy the message text exactly as it appears; include the stack trace; and report it to your technical support representative."
"SYS","2","UNAVAILABLE","Process creation of %s failed (at level %d).","An internal software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","2","UNAVAILABLE","Process creation of %s failed (no memory).","Insufficient memory was available to create a process either while trying to support additional features or due to a memory leak.","A memory leak may be the cause if the system has been running for a while without changing its configuration. If you suspect a leak, then copy this message exactly as it appears and report it to your technical support representative. Otherwise, ensure that more memory is available to support the additional features."
"SYS","2","UNAVAILABLE","Regular expression access check with bad list %d","This message indicates that a pointer to an access list is invalid.","The event that caused this message to be issued should not have occured. It can mean that one or more data structures have been overwritten. If this message recurs, and you decide to report it to your technical representative, you should copy the text of the message exactly as it appears and include the associated stack trace. Since access list corruption may have occurred, a technical representative should verify that access lists are functioning corectly."
"SYS","2","UNAVAILABLE","Root chunk need to be specified for %x","A software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","2","UNAVAILABLE","Stack allocation mmap for IOStasks failed","An internal software error occurred.","If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
"SYS","2","UNAVAILABLE","Stackmagic corrupted for process %s, stackstart = %x magic = %x","An internal software error occurred.","If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
"SYS","2","UNAVAILABLE","System Crashed, Writing Core....","The system has crashed because of an exception, A core is being generated","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYS","2","UNAVAILABLE","System Memory: %luK total, %luK used, %luK free","This is an auxiliary message to several memory-related messages. It provides system memory information usage.","This message provides additional information only. Copy the error message exactly as it appears, and report it to your technical support representative as part of a previously printed error message."
"SYS","2","UNAVAILABLE","Task hung with blocking disabled, value = 0x%x.","The indicated process has exceeded the time limit for which it may relinquish control with blocking disabled.","This message may be a result of high loads. If it recurs, copy the text exactly as it appears and report it, along with the associated stack trace to your technical support representative."
"SYS","2","UNAVAILABLE","Trying to set unknown special character %d to %d","An internal software error occurred.","If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
"SYS","2","UNAVAILABLE","mmap failed for size %d bytes Caller PC 0x%x errno %d","Failed to allocate memory for the requested size.The memory could not be mapped because there is no memory.","This message may indicate either a logic error in the issuing component or it may indicate that a mmap failed to allocatecontiguous memory for the requested size. When reporting this message, copy the text exactly as it appears; include the asssociated stack trace; and report it to your technical support representative."
"SYS","2","UNAVAILABLE","pthread_mutex_lock failed for %s","The thread failed in pthread_mutex_lock while trying to acquire a mutex.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","3","BADRESID","Clock hardware returned bad residual [dec].","A software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","3","CHUNK_NO_EXMEM","No handler to [chars] external memory.","An attempt was made to allocate or free a chunk of external memory, but no handler for managing external memory was registered.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYS","3","INVMEMPID","Invalid pid %d in block: %x","There has been attempt to allocate memory on behalf of an invalid process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYS","3","LOGGER_DROPPED","System dropped %d console debug messages.","Debugging or informational messages are being generated faster than they can be displayed on the console. The messages can not be guaranteed to be seen so this message replaces the lost messages.","Consider using conditional debugging or turning off console logging."
"SYS","3","MEMSEMFAIL","Mempool semaphore creation failed for [chars]","Semaphore creation for the specified memory pool has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYS","3","PREEMPTSUSP","Suspending a preemptive process [chars]","A preemptive process attempted a suspend, which is not allowed because they are expected to finish their work as quickly as possible and go back to idle queue.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYS","3","PROCSEMFAIL","Process semaphore creation for preemptive processes failed.","Creation of a process function semaphore to protect the critical section of the process create routine has failed. The semaphore creation can fail if there is not enough chunk memory to create the event structure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYS","3","UNAVAILABLE","Cannot start timer (%#x) with negative offset (%d).","An internal software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","3","UNAVAILABLE","Clock hardware returned bad residual %d.","A software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","3","UNAVAILABLE","Corrupt block at %x (magic %08x)","The free memory pool is corrupt.An inconsistensy was detected in the free memory pool.","Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. Save any crashinfo or crashdump files. If the router has crashed, and was not configured to automatically reload, the router will need to be reloaded manually."
"SYS","3","UNAVAILABLE","Corrupt free block at %x (magic %08x)","A block of memory at the indicated location is corrupt. An inconsistency was detected while checking the free memory area.","Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. Save any crashinfo or crashdump files. If the router has crashed, and was not configured to automatically reload, the router will need to be reloaded manually."
"SYS","3","UNAVAILABLE","Couldn't add process process pid %d to resource group %x, Cause: %s","An attempt to create a resource group failed at the indicatedlocation","This message may indicate either a logic error in the issuing component or may be due to a low memory condititon as specified in theCause. When reporting this message, copy the text exactly as it appears; include the asssociated stack trace; and report it to your technical support representative."
"SYS","3","UNAVAILABLE","Couldn't delete process process pid %d from resource group Cause: %s","An attempt to remove a process from a resource group failed atthe indicated location","This message indicates a logic error in the issuing component When reporting this message, copy the text exactly as it appears; include the asssociated stack trace; and report it to your technical support representative."
"SYS","3","UNAVAILABLE","Couldn't destroy resource group %x, Cause: %s","An attempt to destroy a resource group failed at the indicated location","This message indicates a logic error in the issuing component When reporting this message, copy the text exactly as it appears; include the asssociated stack trace; and report it to your technical support representative."
"SYS","3","UNAVAILABLE","Crashinfo subsys initialization did not add registry crashinfo_get_default_file_name.","In order to figure out the device which the crashinfo writes to, the crashinfo subsys has to add the registry crashinfo_get_default_file_name.","Use Topic to search for a similar DDTS. If you find none, write a DDTS for this problem. This SHOULD never happen - it is an indication of a bug elsewhere in the code."
"SYS","3","UNAVAILABLE","Failed to parse boot command:%s Error:%d","Boot configuration failed to parse when copied to startup-config.Most likely reason would be syntax errors in the boot configuration.","Decode the traceback and check configuration file for the boot commands. Boot commands are sandwiched between boot-start-marker and boot-end-marker"
"SYS","3","UNAVAILABLE","Function %s: value %#x passed in parameter %s","A software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","3","UNAVAILABLE","Illegal printing attempt from interrupt level.","An internal software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","3","UNAVAILABLE","Invalid memory action (%s) at interrupt level","This message indicates that a memory allocation or deallocation was attempted from an interrupt handler.","If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
"SYS","3","UNAVAILABLE","Invalid pid %d in block: %x","There has been attempt to allocate memory on behalf of an invalid process.","Copy the error message exactly as it appears on the console or in the system log and look up the message in the Bug Toolkit at: http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you are unable to resolve the issue using Bug Toolkit, please copy the text of the message exactly as it appears; include the stack trace, any additonal related failure data and the output of the command show tech-support and report it to your technical support representative."
"SYS","3","UNAVAILABLE","Mempool semaphore creation failed for %s","This message indicates that the semaphore creation for the specified mempool failed.Error Message    %SYS-3-UNAVAILABLE: No handler to %s external memory. Explanation    An attempt was made to allocate or free a chunk of external memory, but no handler for managing external memory was registered.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","3","UNAVAILABLE","No space remaining to save private config","A software or hardware error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","3","UNAVAILABLE","Nonvolatile storage write error; configuration failed","The write of the nonvolatile configuration failed.","If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
"SYS","3","UNAVAILABLE","Null IDB in %s","An internal software error occurred.","If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
"SYS","3","UNAVAILABLE","Overflow in %s, chars %d, buffer size %d","A software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","3","UNAVAILABLE","Process %s top-level routine exited","An internal software error occurred","If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
"SYS","3","UNAVAILABLE","Process has no associated tty (in %s).","An internal software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","3","UNAVAILABLE","Process semaphore creation for preemptive processes failed.","Creation of process function semaphore to protect the critical section of process create routine failed. The semaphore creation can fail if there isnt enough chunk memory to create the event structure.Error Message    %SYS-3-UNAVAILABLE: Questionable reset of process %d on tty%t Explanation    A process was reset without giving it a chance to clean itself up.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","3","UNAVAILABLE","Removed a non-empty list(%x, name: %s), having %lu elements","A non-empty list should not be destroyed. If it happens, there is a possibility that all elements enqueued into the list will never be deallocated. This message reports that an non-empty list got destroyed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYS","3","UNAVAILABLE","Requested memory thresholding operation on resource group failed Resource Group handle: %x, Cause: %s","The message indicates that an request to Set/Get memory thresholding data or enable/disable thresholding failed in the indicated location","This message indicates a logic error in the issuing component asspecified in the Cause. When reporting this message, copy thetext exactly as it appears; include the asssociated stack trace; and report it to your technical support representative."
"SYS","3","UNAVAILABLE","Resource group creation failed, Cause: %s","An attempt to create a resource group failed at the indicated location","This message may indicate either a logic error in the issuing component or may be due to a low memory condititon. When reporting this message, copy the text exactly as it appears; include the asssociated stack trace; and report it to your technical support representative."
"SYS","3","UNAVAILABLE","Same tty%t in linewatch_timers, type %d","A tty appeared twice in a timer list where it should have only appeared once.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","3","UNAVAILABLE","Storing of console terminal control settings failed","This occurs during console initialization, the retrieving and storing ofconsole terminal control settings soon after initialization fails","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","3","UNAVAILABLE","System cannot release chunk memory.","The system was not able to destroy a previously allocated chunk of memory.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","3","UNAVAILABLE","System dropped %d console debug messages.","Debugging or informational messages are being generated faster than they can be displayed on the console. The messages can not be guaranteed to be seen so this message replaces the lost messages.","Consider using conditional debugging or turning off console logging."
"SYS","3","UNAVAILABLE","System pausing to ensure console debugging output.","Debugging or informational messages are being generated faster than they can be displayed on the console. In order to guarantee that they can be seen, the rest of the system is paused until the console output catches up. This can break time-critical behavior, such as maintaining an ISDN link.","Consider using conditional debugging, turning off console logging, or using the o logging console guaranteed command, or turning off link-state messages for some interfaces"
"SYS","3","UNAVAILABLE","System reloading, unable to complete startup configuration update","Startup configuration updation is already in progress and reload has been called either from interrupt level or with all interrupts disabled. Reload can not suspend to let startup configuration updation get completed. Startup configuration may get corrupted.","This is a notification message only. No action is required."
"SYS","3","UNAVAILABLE","System running-config write error; configuration failed","The write of the system running configuration failed.","If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
"SYS","3","UNAVAILABLE","System was paused for %TE to ensure console debugging output.","Debugging or informational messages are being generated faster than they can be displayed on the console. In order to guarantee that they can be seen, the rest of the system was paused until the console output catches up. This can break time-critical behavior, such as maintaining an ISDN link.","Consider using conditional debugging, turning off console logging, or using the o logging console guaranteed command, or turning off link-state messages for some interfaces"
"SYS","3","UNAVAILABLE","TTY%t: Managed Timer(s) %s still running","One or more managed timers for a TTY that is deleted are still running.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYS","3","UNAVAILABLE","Task is running for (%d)msecs, more than (%d)msecs (%d/%d),process = %s.%s","The indicated process ran too long without relinquishing the processor. Each process should run for a small amount of time and then relinquish the CPU so that other processes can run. This problem can be caused by many things like traffic or system load, hardware or operational configuration, a configuration change, initialization (of many interfaces, cards or ports for example), a high momentary error rate, a sustained abnormal condition or many other conditions.","If you suspect a software error, copy the error message exactly as it appears on the colsole or in the system log, contact your technical supportrepresentative, and provide the representative with the gathered information."
"SYS","3","UNAVAILABLE","Timer callback ran long, PC = %x.","The indicated callback routine ran for too long without relinquishing the processor.","Copy the message exactly as it appears, and report it your technical support representative."
"SYS","3","UNAVAILABLE","Unknown socket protocol %d","An internal software error occurred.","If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
"SYS","3","UNAVAILABLE","Unknown stack. Process: %s","An internal error occurred when running the garbage detector","Copy the error message exactly as it appears on the console or in the system log and look up the message in the Bug Toolkit at: http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you are unable to resolve the issue using Bug Toolkit, please issue a show tech and contact your technical support representative with the gathered information."
"SYS","3","UNAVAILABLE","Unknown stack. Process: %s","An internal error occurred when running the memory leak detector","Copy the error message exactly as it appears on the console or in the system log and look up the message in the Bug Toolkit at: http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you are unable to resolve the issue using Bug Toolkit, please issue a show tech and contact your technical support representative with the gathered information."
"SYS","3","UNAVAILABLE","Variable %s not set properly in the routine %s.","The write of the nonvolatile configuration failed because an internal variable was not set properly.","If this messages occurs, copy it exactly as it appears and report it to your technical support representative."
"SYS","3","UNAVAILABLE","cannot open file for reading '%s'","The URL for the cannot be opened for reading.","Check for proper Uniform Resource Locator syntax and for read permission and retry."
"SYS","3","UNAVAILABLE","cannot set TCL interpreter variable '%s' to '%s' : '%s'","The value could not be passed to the TCL interpreter","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","3","UNAVAILABLE","heap timer at 0x%x has not been initialized","A heap timer has not been initialized","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","3","UNAVAILABLE","heap timer at 0x%x in state %d","A heap timer has not been initialized","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","3","UNAVAILABLE","redirection url write failed '%s'","Redirection of output to URL failed.","Check for free space on destination URL and retry."
"SYS","3","UNAVAILABLE","timer heap at 0x%x needed to expand, but hasn't","A timer heap should have expanded, but has not","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","4","UNAVAILABLE","%s while processing the input regular expression. Aborting processing, use alternate regular expression. Input regular expression: %s","Regular expression processing limitation: Certain regular expressions require huge stack space for processing or can lead to processing timeouts. We abort processing such regular expressions and print this message to avoid stack overflow/unexpected reload.","The regular expression specified leads to stack overflow/processing timeout of the indicated process. Recommended to use a different regular expression."
"SYS","4","UNAVAILABLE","%s%s is seeing %s cpu util %u%% at %s level more than the configured %s limit %u %%","The system is experiencing high CPU usage, possibly from a process that is using too much CPU. This condition demands immediate attention, or packets or calls may be dropped. CPURESRISING notifications should be matched with the corresponding CPURESFALLING/CPURESUNAPPLY notification.","No action is required"
"SYS","4","UNAVAILABLE","%s.","An internal software error occurred.","If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
"SYS","4","UNAVAILABLE","An nvram checksum is already in progress","User attempted multiple nvram operations at the same time. If not at interrupt, the system will attempt the nvram operation again.","Nothing - unless the command fails; in which case, the command needs to be attempted again."
"SYS","4","UNAVAILABLE","An nvram checksum is already in progress; the nvram checksum from interrupt cannot be serviced","An interrupt service routine attempted to perform a checksum on the nvram contents and found the resource in use.","Nothing - unless the command fails; in which case, the command needs to be attempted again."
"SYS","4","UNAVAILABLE","Attempt via SNMP failed, system shutdown not configured","SNMP cannot be used to reload the router unless this functionality has been previously configured. This message reports that an attempt to reload the router failed because SNMP reloads are not currently configured on the router.","This is a notification message only. No action is required."
"SYS","4","UNAVAILABLE","Configuration from version %d.%d may not be correctly understood","The software detected that the configuration saved in memory was written by a newer version of software. There might be commands saved in memory that are not implemented by the older software version.","Examine all the messages printed while the router was booting. For each message about an unknown command, determine whether that feature is required. If so, upgrade to a newer version of software that supports that feature."
"SYS","4","UNAVAILABLE","Configuration needs to be truncated to fit into nvram","The software detected that the configuration is to be truncated to fit in the nvram. There was not enough space to save the compressed configuration","Save the configuration to flash if the platform supports boot config nvbypass command."
"SYS","4","UNAVAILABLE","External memory allocation of %d bytes failed from EXMEM %d","The requested memory allocation is not available from the specified memory pool. The current system configuration, network environment, or possibly a software error might have exhausted or fragmented the router's memory.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","4","UNAVAILABLE","Free Memory has dropped below low watermark Pool: %s Free: %lu freemem_lwm: %lu","The memory pool specified in the error message is experiencing a low-memory condition. The amount of free memory available in the specified memory pool has dropped below the configured low-memory limit.","No action is required"
"SYS","4","UNAVAILABLE","Non config data present at the end of nvram is corrupted","The software detected that the configuration saved into nvram has overlaid a part of the nvram occupied by non config data files.Typically these files are used by snmp to store and retrieve non config persistent data accross system reload.","Compress the configurtion and store or copy to flash as appropriate"
"SYS","4","UNAVAILABLE","Non config data present at the end of nvram needs to be overwritten to fit the configuration into nvram","The software detected that the non config data files occupying the end of nvram need to be overwritten to fit the configuration. Typically these files are used by snmp to store and retrieve non config persistent data accross system reload.","Compress the configurtion and store or copy to flash as appropriate"
"SYS","4","UNAVAILABLE","Running invalid image for platform!","The software image being run is for a different hardware architecture. This problem can occur on a Cisco 1003, Cisco 1004, or Cisco 1005. The Cisco 1003 and Cisco 1004 use a different image from the Cisco 1005.","Install the correct software image."
"SYS","4","UNAVAILABLE","SNMP WriteNet request. Writing current configuration to %i","SNMP is writing the current configuration to a network host.","These are notification messages only. No action is required."
"SYS","4","UNAVAILABLE","SNMP hostConfigSet request. Loading configuration from %i","SNMP is reading the host configuration from a network host.","This is a notification message only. No action is required."
"SYS","4","UNAVAILABLE","SNMP netConfigSet request. Loading configuration from %i.","SNMP is reading the network configuration from a network host.","This is a notification message only. No action is required."
"SYS","4","UNAVAILABLE","SNMP system message request %d denied because of pending job","A software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","4","UNAVAILABLE","System config parse from (%s) failed","The configuration file from the URL specified in the error message could not be read.","Enter the no service config command to disable autoloading of configuration files OR investigate why the tftp load is failing."
"SYS","4","UNAVAILABLE","The configuration could not be locked","A software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"SYS","4","UNAVAILABLE","Truncated configuration to %ld bytes from %ld bytes","The software detected that the configuration saved into nvram has been truncated. There was not enough space to save the compressed configuration.","Save the configuration to flash if the platform supports boot config command."
"SYS","4","UNAVAILABLE","Unable to initialize the geometry of nvram","The software detected that it failed to initialize the nvram block geometry, a part of the nvram to host non config data files. Typically these files are used by snmp to store and retrieve non config persistent data accross system reload. This may happen when the entire nvram is packed with the configuration and the newer version of software which supports this feature, could not find the minimum room in the nvram to initialize block file system.","Reduce the configurations in the nvram atleast by 2K"
"SYS","4","UNAVAILABLE","Update to memory leak detector on free of 0x%x failed, CLI output is unreliable","managed chunk malloc to store the range that is freed while memory leak detector is in progress failed. Hence memory leak detector will not be updated of this free and this can be reported as leak which is false.","Ignore the output of show memory debug leaks.. if system is in low memory condition else perform a bug toolkit search on the web for existing bugs related to this error message, if none found, contact TAC for this problem providing show version and show memory statistics output."
"SYS","4","UNAVAILABLE","sanity check failed for string %s","The owner of this string must have freed their structure without letting the string database know","No action is required"
"SYS","5","UNAVAILABLE","Scheduled reload cancelled at %s","A scheduled reload that was requested for the router has been cancelled.","No action is required."
"SYS","5","UNAVAILABLE","%s table %s damaged: %s.","An internal table entry became corrupt.","Copy the message exactly as it appears, and report it your technical support representative."
"SYS","5","UNAVAILABLE","Configuration file %s accepted, aborting setup","A configuration was accepted over the network, so the setup session will be aborted.","This is a notification message only. No action is required."
"SYS","5","UNAVAILABLE","Configured from %s","The router's configuration was changed.","This is a notification message only. No action is required."
"SYS","5","UNAVAILABLE","Configured from %s by %s","The router's configuration was changed.","This is a notification message only. No action is required."
"SYS","5","UNAVAILABLE","Flow-control threshold on module %d has exceeded the default value. Threshold will be set to lower value","The FIFO threshold values are monitored for flow-control. When the threshold value exceeds the default, the value is set to new (lower) value","LOG_STD_NO_ACTION"
"SYS","5","UNAVAILABLE","Free Memory has recovered above low watermark Pool: %s Free: %lu freemem_lwm: %lu","The memory pool specified in the error message has recovered from a low-memory condition and the free memory in that pool is now above the configured low-memory limit.","No action is required"
"SYS","5","UNAVAILABLE","Nonvolatile storage configured from %s","The configuration was written successfully.","This is a notification message only. No action is required."
"SYS","5","UNAVAILABLE","Nonvolatile storage configured from %s by %s","The configuration was written successfully.","This is a notification message only. No action is required."
"SYS","5","UNAVAILABLE","Privilege level set to %d by%s%s","The privileged mode is enabled or the privilege level is changed; therefore, the associated , and information will be logged.","This is a notification message only. No action is required. To disable this particular logging feature, issue the no logging userinfo command from the global configuration mode."
"SYS","5","UNAVAILABLE","Reload requested for %s","A scheduled reload has been requested for the router.","No action is required."
"SYS","5","UNAVAILABLE","Reload requested%s","A reload or restart was requested.","This is a notification message only. No action is required."
"SYS","5","UNAVAILABLE","Switchover requested","A switchover was requested.","This is a notification message only. No action is required."
"SYS","5","UNAVAILABLE","Switchover requested%s","A switchover was requested.","This is a notification message only. No action is required."
"SYS","5","UNAVAILABLE","System restarted -- %s","A reload or restart was requested.","This is a notification message only. No action is required."
"SYS","6","UNAVAILABLE","%#x: %#x %#x %#x %#x","This is an auxiliary message to several memory-related messages. It provides a raw display of the information in the header of a corrupted data block.","This message provides additional information only. Copy the error message exactly as it appears, and report it to your technical support representative as part of the previously printed error message."
"SYS","6","UNAVAILABLE","%d queue error messages have been dropped","Some queue error messages were dropped due to message buffer full.","This is an informational message. There should have been other queue related error messages before this one. Report those earlier messages to your technical support represenatative."
"SYS","6","UNAVAILABLE","%s %s.","A configured boot system command failed.","If a system image was eventually loaded, no action is recommended. If the system image did not load as configured, send a log file and configuration information to your technical support representative."
"SYS","6","UNAVAILABLE","%s packet %x has a zero reference count, freeing pid = %x, freeing pc = %x %s.","Provides additional information about original freer of packet.","If this messages recurs, copy it exactly as it appears; include the stack trace; and report it to your technical support representative."
"SYS","6","UNAVAILABLE","%s%s is no longer monitoring %s cpu at %s level for the configured %s limit.","CPU usage is no loger monitored for the configured threshold level mentioned in the error message The corresponding policy is revoked.","No action is required"
"SYS","6","UNAVAILABLE","%s%s is no longer seeing %s high cpu at %s level for the configured %s limit %u%%, current value %u%%","CPU usage has returned to normal after crossing over from a threshold of high usage. Any process that was disabled during the period of high CPU use can now be enabled.","No action is required"
"SYS","6","UNAVAILABLE","%s: addr, pc ADDRPC ADDRPC ADDRPC ADDRPC ADDRPC ADDRPC ADDRPC ADDRPC","This is an auxiliary message to several memory-related messages. It provides the address of the memory block and the calling program counter for the last eight blocks allocated and for the last eight blocks freed.","This message provides additional information only. Copy the error message exactly as it appears, and report it to your technical support representative as part of a previously printed error message."
"SYS","6","UNAVAILABLE","%sblk %x, words %u, alloc %x, %s, dealloc %x, rfcnt %x","This is an auxiliary message to several memory-related messages. It provides a formatted display of some of the information in the header of a corrupted data block.","This message provides additional information only. Copy the error message exactly as it appears, and report it to your technical support representative as part of the previously printed error message."
"SYS","6","UNAVAILABLE","Bridging software not present","Your system is not configured to be a bridge.","Configure the bridging software."
"SYS","6","UNAVAILABLE","Logging of buginf debugs was %s","All calls to debugging have been disabled in Cisco IOS software as a result the user entering the no logging buginf command. This command is used to avoid a situation where a large amount of debugging calls might overload the processor (CPU hog condition). This condition differs from the use of the undebug all command in that all debugging calls have been disabled in the Cisco IOS software. No debug reporting is available, even if debugging is enabled. Note that even though debugging has been completely disabled in the system, other message reporting, including error reporting, is still available.","This is an informational message only. No action is required."
"SYS","6","UNAVAILABLE","Logging to host %s%s%s%s","Syslog logging to specified server or host(vrf) has started or stopped","LOG_STD_NO_ACTION"
"SYS","6","UNAVAILABLE","Messages above this line are from the boot loader.","At least one informational or error message was printed by the boot loader.","If the system image was loaded, no action is recommended. If the system image did not load as configured, send a log file and configuration information to your technical support representative."
"SYS","6","UNAVAILABLE","Process %s just finished executing","This message is an auxiliary to the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages. It identifies the process or process fragment that was executing when the error occurred.","Copy this messages exactly as it appears, and report it, along with the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages, to your technical support representative."
"SYS","6","UNAVAILABLE","Reserve memory is being created","A portion of memory is reserved exclusively for console","The console access is made available even in low memory condition. User can collect the details like tech-support for further diagnosis"
"SYS","6","UNAVAILABLE","Reserve memory is being used","The reserved memory is being used by the console","The system is low in memory. The reserved memory will be used only by the console process. Please take a techsupport so that the reason for low memory can be found"
"SYS","6","UNAVAILABLE","Scheduler test %#x (for %s) just executed","This message is an auxiliary to the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages. It identifies the process or process fragment that was executing when the error occurred.","Copy this message exactly as it appears, and report it, along with the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages, to your technical support representative."
"SYS","6","UNAVAILABLE","Stack for %s %s running low, %d/%d","An internal software error occurred.","If this messages recurs, copy it exactly as it appears and report it to your technical support representative."
"SYS","6","UNAVAILABLE","System clock has been updated from %s to %s, configured from %s by %s.","This message indicates that the system clock has been modified.","This is informational message."
"SYS","6","UNAVAILABLE","Time since last reboot not available","This is an informational message for the user. The time taken for the router to come up after OIR is not available.","No action required."
"SYS","6","UNAVAILABLE","Time taken to reboot after reload = %-4d seconds","This is an informational message for the user. This provides the time taken for the router to come up after reload or crash. The time is actually the difference between the last crash and a successive boot. If autoboot was not set, and router is in rommon for a long time, then the reload time shown could be large.","No action required."
"SYS","6","UNAVAILABLE","boot system %s command is skipped","A configured boot system command is skipped. Either the system experienced a crash while loading this image in the last attempt or the filename is not properly specified. Subsequent boot system commands will be tried","Replace the failed boot system image with a good one. There could be various reasons that this specified image failed, for example the image might be with a bad checksum."
"SYS","7","UNAVAILABLE","ESM shutdown","The Embedded Syslog Manager has been shut down","LOG_STD_NO_ACTION"
"SYS","7","UNAVAILABLE","Initialized the geometry of nvram","Initialized the nvram block geometry, a part of the nvram to host non config data files. Typically these files are used by snmp to store and retrieve non config persistent data accross system reload.SYS-SPSYS-SP-3Error Message    %SYSCTLR-3-UNAVAILABLE: Health monitoring setup failed on shelf_id %d Explanation    Health monitor failed to setup the monitoring command on that particular shelfError Message    %SYSCTLR-3-UNAVAILABLE: Invalid parameter/mangled pointer routine: %s, file: %s, line: %d Explanation    An internal software error occurred.","If any of these messages recur, call your technical support representative for assistance."
"SYSCTLR","3","UNAVAILABLE","No context associated with the expired SDP timer","An internal software error occurred.","If any of these messages recur, call your technical support representative for assistance."
"SYSCTLR","3","UNAVAILABLE","SDP packet received by system controller containted invalid version number.","Check that shelf is running compatible version of SDP","If any of these messages recur, call your technical support representative for assistance."
"SYSCTLR","3","UNAVAILABLE","SDP packet with duplicate shelf-id %d received from %s,already discovered shelf located at %s","Two shelves with same shelf-id are configured in the system.","Change the shelf-id for one of the shelf."
"SYSCTLR","3","UNAVAILABLE","Shelf id protocol error","An internal software error occurred.","If any of these messages recur, call your technical support representative for assistance."
"SYSCTLR","3","UNAVAILABLE","Unable to send message %d to process with pid %d.","Most likely the performance collector process has terminated.Error Message    %SYSCTLR-3-UNAVAILABLE: socket bind failed Explanation    An internal software error occurred.","If any of these messages recur, call your technical support representative for assistance."
"SYSCTLR","3","UNAVAILABLE","socket open failed","An internal software error occurred.","If any of these messages recur, call your technical support representative for assistance."
"SYSCTLR","4","UNAVAILABLE","Hello packet from shelf %d not received, shelf removed.","No SDP hello packets were received from the particular shelf, this could indicate that particular router shelf is down or is mis-configured.Error Message    %SYSCTLR-4-UNAVAILABLE: Local time %s %s on shelfid %d is not active, resetting monitor_type %d Explanation    Health monitor setup commands polling information. If you see this message shows up every ten minutes, that means health monitor is not able to set that corresponding entry on that shelf.Error Message    %SYSCTLR-4-UNAVAILABLE: Shelf %d located %i reloaded Explanation    SDP protocol on system controller has detected that a particular shelf has reload.Error Message    %SYSCTLR-4-UNAVAILABLE: Shelf %d located at address %i removed. Explanation    SDP protocol on system controller didn't receive hello packets from particular shelf.Error Message    %SYSCTLR-4-UNAVAILABLE: Shelf %d not reachable via SNMP Explanation    Shelf indicated above is not responding to SNMP requests.","Check the snmp configuration for the above shelf and also check correct community string is specified in configuration command system-controller community on the system controller."
"SYSCTLR","5","UNAVAILABLE","MD5 digest does not match, SDP packet received from, %i rejected","A SDP hello packet was received from shelf, which is not trusted.","Either specify the correct SDP password and/or destination on the shelf from which this message was received."
"SYSCTLR","6","UNAVAILABLE","Communication with shelf %d located at address %i","SDP protocol on system controller has detected a particular shelf.Error Message    %SYSCTLR-6-UNAVAILABLE: Found Shelf %d with an invalid IP address %s Explanation    System Controller found a Shelf with an invalid ip address","Check the IP address set on the Shelf"
"SYSCTLR","6","UNAVAILABLE","Shelf %d discovered located at address %i","SDP protocol on system controller has detected a particular shelf.SYSLOGD MessagesThis section contains system logging (SYSLOG) messages.SYSLOGD-3Error Message    %SYSLOGD-3-DROPPED_MESSAGES: A total of [int] messages have been dropped by the syslog daemon, due to [chars]Explanation    The syslogd process has dropped received messages. The syslogd process may be receiving too many messages to process before the buffer fills, or it may have received a message for which there was insufficient memory available. In either case, there may be a bug in the sending process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYSLOG_SERVER","3","UNAVAILABLE","Failed to add Syslog file %s, maximum Syslog files %d.","Exceeded the maximum Syslog files allowed.Error Message    %SYSLOG_SERVER-3-UNAVAILABLE: Failed to create a Syslog file. Explanation    Failed to create a Syslog file.","There is probably no PCMCIA disk on slot0 on the System Controller. Please check to see if it is not a PCMCIA Flash"
"SYSLOG_SERVER","3","UNAVAILABLE","Failed to open %s.%d syslog file.","Failed to open a syslog file.One or more of the subfiles may have been deleted or there is no PCMCIA disk","You may not be having a PCMCIA disk in slot0 on the System Controller. Please check to see if it is not a PCMCIA Flash. If one or more of the subfiles is missing, then they will be automatically restored when the current file reaches its capacity and gets archived"
"SYSLOG_SERVER","3","UNAVAILABLE","Failed to read a file.","Failed to read a file.Error Message    %SYSLOG_SERVER-3-UNAVAILABLE: Failed to write a syslog file. Explanation    Failed to write a syslog file.Error Message    %SYSLOG_SERVER-3-UNAVAILABLE: Illegal file system %s. Explanation    Illegal file system.Error Message    %SYSLOG_SERVER-3-UNAVAILABLE: Parsing file error. Explanation    The Router is not configured to timestamp all the log messages","Please configure your router with appropriate commands to timestamp the log messages. Eg: service timestamps"
"SYSLOG_SERVER","3","UNAVAILABLE","Unknown command or device name, or unable to find device address.","Unknown command or device name, or unable to find device address.SYSLOG_SERVER-4Error Message    %SYSLOG_SERVER-4-UNAVAILABLE: No configuration change. Explanation    There is no configuration change to the syslog-serverError Message    %SYSLOG_SERVER-4-UNAVAILABLE: No memory left. Explanation    No memory left.","The System Controller is running very low on memory."
"SYSLOG_SERVER","4","UNAVAILABLE","No syslog file.","No syslog file.Error Message    %SYSLOG_SERVER-4-UNAVAILABLE: Syslog file [%s] exists. Explanation    You may have issued a directory name that already exists on the PCMCIA disk.","Please check to see if the directory name you supplied already exists on the PCMCIA disk and re-enter a different one"
"SYSLOG_SERVER","4","UNAVAILABLE","syslog records do not appear to be timestamped.","This may be a result of not turning the service timestamp command.","Please turn the service timestamps log datetime command on your router. This will cause the system to timestamp debugging or logging messages.Use atleast datetime."
"SYSMGT_RPC","3","UNAVAILABLE","SYSMGT RPC - IPC %s %s failed (%s)","System Management Remote Procedure Call operation failure. Request for information from the CIP card will not be processed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYSMGT_RPC","3","UNAVAILABLE","SYSMGT RPC - NETMGT Event: %s (%d)","System Management Remote Procedure Call Network management event error detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYSMGT_RPC","3","UNAVAILABLE","SYSMGT RPC - RPC %s %s failed (%s %d)","System Management Remote Procedure Call operation failure. Request for information from the CIP card will not be processed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYSMGR","3","ABNORMTERM","[chars]:[dec] (jid [dec]) abnormally terminated, [chars]","A process was abnormally terminated.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYSMGR","3","ERROR","[chars]:[dec] (jid [dec]) [chars] ([chars])","The system manager server has encountered an error condition.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYSMGR","6","ERROR_EOK","[chars]:[dec] (jid [dec]) [chars]","The system manager server has encountered an error condition.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYSMGR","6","RESTART","Restarting process [chars] by [chars]","A process was restarted through the CLI.","This is an informational message only. No action is required."
"SYSMGR_PLATFORM","5","WAIT_RP","Waiting RP to complete crashinfo and core file collection","Sysmgr.proc process is waiting for the RP to signal the end of crashinfo or core file collection.","This is an informational message only. No action is required."
"SYSTEM_BUS_ASIC","3","INTR_FATAL","SYSTEM BUS ASIC [dec]: recoverable interrupt [chars]","The System Bus Translator ASIC detected an unexpected interrupt condition. This message indicates a hardware failure or malfunction. The system will reload to fix the problem.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYSTEM_BUS_ASIC","3","INTR_RECOVERY","SYSTEM BUS ASIC [dec]: recoverable interrupt [chars]","The System Bus Translator ASIC detected an unexpected interrupt condition.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYSTEM_BUS_ASIC","3","INTR_RESET","SYSTEM BUS ASIC [dec]: was reset","The System Bus Translator ASIC was reset as part of the system recovery sequence.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYSTEM_BUS_ASIC","3","INTR_STATS_RECOVERY","SYSTEM BUS ASIC [dec]: Recoverable Interrupt warning [chars]","The System Bus Translator ASIC detected an unexpected condition in the statistics collection module.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYSTEM_BUS_ASIC","3","INTR_WARN","SYSTEM BUS ASIC [dec]: Non-fatal Interrupt warning [chars]","The System Bus Translator ASIC detected an unexpected nonfatal condition.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYSTEM_BUS_ASIC","3","INTR_WARN_TYPE2","SYSTEM BUS ASIC [dec]: Non-fatal interrupt Warning [chars] error code [dec]","The System Bus Translator ASIC detected an unexpected nonfatal condition.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYSTEM_BUS_ASIC","3","KUMA_INTR_THROTTLED","SYSTEM BUS ASIC %d: Kuma interrupts throttled","The system bus translator ASIC detected too many interrupts. To avoid performance degradation, the system has temporarily masked interrupts.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYSTEM_BUS_ASIC","3","KUMA_INTR_UNTHROTTLED","SYSTEM BUS ASIC %d: Kuma interrupts unthrottled","The system has unmasked the interrupts that were masked temporarily.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYSTEM_CONTROLLER","3","COR_MEM_ERR","Correctable DRAM memory error. Count [dec], log [hex]","A transient DRAM memory error was detected and corrected.","If the error message appears infrequently, no action is required. If the message recurs, reseat the SDRAM SIMM on the supervisor engine. If errors persist, replace the SIMM. If the errors continue after the SIMM is replaced, the supervisor engine may need to be replaced."
"SYSTEM_CONTROLLER","3","ERROR","Error condition detected: [chars]","The most common errors from the Mistral ASIC on the MSFC are TM_DATA_PARITY_ERROR, SYSDRAM_PARITY_ERROR, SYSAD_PARITY_ERROR, and TM_NPP_PARITY_ERROR. Possible causes of these parity errors are random static discharge or other external factors.","If the error message appears only once (or rarely), monitor the system log to determine whether the error message was an isolated incident. If the message recurs, check the environmental conditions for problems such as power brownouts, static discharges, or strong EMI fields. If these environmental conditions are within normal ranges and the error continues to appear, the supervisor engine may need to be replaced."
"SYSTEM_CONTROLLER","3","EXCESSIVE_RESET","System Controller is getting reset so frequently","The MISTRAL ASIC is being reset frequently. The usual cause is an improperly seated module or another hardware condition.","Power down and reseat the module. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYSTEM_CONTROLLER","3","INVALID_EARL_HANDLER","EARL interrupt handler is not valid","The EARL interrupt handler is not valid.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"SYSTEM_CONTROLLER","3","MISTRAL_RESET","System Controller is reset:Normal Operation continues","The system controller is being reset. Operation will continue, but the message rate will be limited.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TAC","3","SERVCONF","Server config failure: [chars]","The server configuration failed.","Please configure the server properly."
"TAC","3","SERVINT","[chars]","This is an internal software error.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"TAC","3","SERVNO","Server [chars] is not configured","The server is not configured.","Please configure a server before un-configuring it."
"TAC","3","XTACACL","%s: accesslist 0x%x out of range for %s","The TACACS facility created a message that contains an accesslist which is not a valid accesslist (out of bounds).","If this error recurs, then issue the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information."
"TAC","4","NOTIMEOUT","Warning: This command has been deprecated in favor of the line-command timeout login response","This command is deprecated, and should no longer be used. Instead, the line-command timeout login response now provides this functionality","Use the line-command timeout user-response"
"TAC","4","SERVREFNAME","Warning: Server [chars] is still referenced by server group.","The server being removed is still referenced by a server group.","Please dereference the server from the server group as soon as possible."
"TAC","4","UNEXREP","Reply for non-existent request, %d on queue","The TACACS facility received a message it was not expecting. This may occur when a TACACS server sends duplicate responses or when it responds to a request that has already timed out. It also may be due to an internal software problem.","If this error recurs, then issue the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information."
"TAC","6","SENDTMO","Send type %d to %i timed out","A background TACACS notification (enabled with the command tacacs notify) was not acknowledged by the TACACS server processor within the timeout period (5 minutes). The information contained in that notification was lost. This loss of information may interfere with accounting or auditing on the server. This condition arises when the TACACS server is misconfigured, crashed, or became unreachable via the network.","Check the TACACS server and the network attached to it."
"TAC","6","SENDTMO","Send type %d to %i timed out","A background TACACS notification (enabled with the command tacacs notify) was not acknowledged by the TACACS server processor within the timeout period (5 minutes). The information contained in that notification was lost. This loss of information may interfere with accounting or auditing on the server. This condition arises when the TACACS server is misconfigured, crashed, or became unreachable via the network.","Check the TACACS server and the network attached to it."
"TAC","6","SERVDEP","tacacs-server host CLI will be deprecated soon. Please move to tacacs server CLI","Migration from tacacs-server host CLI to tacacs server CLI.","Please try to use the new CLI."
"TAGCON","3","UNAVAILABLE","%i/%i, %s","A problem was encountered in clean up following termination of a Tag Distribution Protocol (TDP) session.","ACTION_COPY_REPORT_TAGCON"
"TAGCON","3","UNAVAILABLE","%i/%i; %s","An operation on the TDP Directed Adjacency data structure failed.","ACTION_COPY_REPORT_TAGCON"
"TAGCON","3","UNAVAILABLE","%s","An action attempted by the Tag Control process encountered an unexpected condition.","Copy the message exactly as it appears and report it to your technical service representative."
"TAGCON","3","UNAVAILABLE","%s sort bad; item %d","EXPLANATION_ADDR_TBL_TAGCON","ACTION_TOGGLE_TAG_IP_TAGCON"
"TAGCON","3","UNAVAILABLE","Can't alloc work item for %s","Internally when a process, such as the TDP process, must request the tag distribution and control process take some action, it queues a work item for the tag distribution and control process. This message is generated when an attempt to queue work for the tag distribution and control process fails. The failure can occur if the system is unable to allocate memory to hold the work request, or if the process has stopped processing requests on its work queue.","ACTION_COPY_REPORT_TAGCON"
"TAGCON","3","UNAVAILABLE","Cannot alloc %s","An attempt to allocate a label switching data structure failed because of a low memory condition.","ACTION_STD_LOW_MEMORY_TAGCON"
"TAGCON","3","UNAVAILABLE","Cannot allocate local tag","An attempt to allocate a local (incoming) tag failed. This should happen only if the system has allocated all available local tags.","The number of tags available for allocation can be changed by the tag-switching tag-range ... configuration command. Consult with your technical service representative to determine whether you should use this command to increase the number of available tags."
"TAGCON","3","UNAVAILABLE","Duplicate Address %i advertised by peer %s is already bound to %s","An address message advertisement is received from TDP/LDP peer. The address is rejected as it has already been advertised by an another peer. This implies that the rejected IP address has been configured on both peers by mistake","Correct the configuration by changing the IP address on one of the peers."
"TAGCON","3","UNAVAILABLE","Platform specified information for label region %s is invalid.","A platform service routine provides label region information about all label regions it supports. This error message is printed when the service routine does not specify its label region information correctly.","Report this condition to your technical service representative."
"TAGCON","3","UNAVAILABLE","TDP peer %i(%s): %s","An operation involving the state machine for a TDP peer failed.","ACTION_COPY_REPORT_TAGCON"
"TAGCON","3","UNAVAILABLE","TIB walk failed (%s)","Some Tag Information Base (TIB) maintenance operations involve a complete scan (walk) of the TIB radix tree data structure. This message is generated when a TIB walk encounters an unexpected failure.","ACTION_COPY_REPORT_TAGCON"
"TAGCON","3","UNAVAILABLE","Tag Local Address Table revision number wrapped","The revision number used to manage advertisement of interface addresses to TDP peers overflowed. This will result in faulty advertisement of interface addresses to TDP peers and faulty tag switching on those peers.","To restore proper interface address advertisement reboot the platform. Report this condition to your technical service representative."
"TAGCON","3","UNAVAILABLE","Unexpected blist_type (%d) for %s PIE from peer %s","A TDP protocol information element (PIE) received from a TDP peer contained an unexpected binding list type. The PIE will be be ignored.","ACTION_IGNORE_PIE_TAGCON"
"TAGCON","3","UNAVAILABLE","Unexpected event; state=%s, event=%s","An operation on the state machine for the tag distribution and control process failed.","ACTION_COPY_REPORT_TAGCON"
"TAGCON","3","UNAVAILABLE","peer %s, TDP Id/Addr mapping problem (%s)","EXPLANATION_ADDR_TBL_TAGCON","ACTION_TOGGLE_TAG_IP_TAGCON"
"TAGCON","3","UNAVAILABLE","peer %s; %s not implemented","A tag distribution protocol (TDP) peer has requested an action which is not currently implemented by the tag distribution and control subsystem.","The request will be ignored. If it repeatedly occurs, copy the message exactly as it appears and report it to your technical service representative."
"TAGCON","3","UNAVAILABLE","process cannot initialize","The tag distribution and control process failed to initialize itself. The probable cause is insufficient memory.","ACTION_STD_LOW_MEMORY_TAGCON"
"TAGCON","3","UNAVAILABLE","process not created","An attempt to create the tag distribution and control process failed. The probable cause is insufficient memory.","ACTION_STD_LOW_MEMORY_TAGCON"
"TAGCON","3","UNAVAILABLE","unexpected error %d; peer %s; %s","An unexpected failure occurred while building a TDP protocol information element (PIE) for transmission to a TDP peer. It occurred when attempting to add a tag binding or an address to the PIE.","ACTION_COPY_REPORT_TAGCON"
"TAGCON","4","UNAVAILABLE","Adjusting configured label range to default range","The saved configuration has been ignored and the default label range is being used.","Please reconfigure the label range to a valid range using mpls label range ... configuration command."
"TAGCON","4","UNAVAILABLE","Can't alloc work item for %i","When a new IP address for a TDP peer is learned, it may be necessary to update the Tag Forwarding Information Base (TFIB) for any routes for which the new address is a next hop. Deciding whether it is necessary to update the TFIB is the responsibility of an 'address process'. This message is generated when an attempt to queue work for the address process fails.","This is an informational message. The system remembers that it needs to do this work and will regularly attempt to queue the necessary work item. If this message occurs repeatedly, copy it exactly as it appears and report it to your technical service representative."
"TAGCON","4","UNAVAILABLE","Can't create tagcon addr proc","When a new IP address for a TDP peer is learned, it may be necessary to update the Tag Forwarding Information Base (TFIB) for any routes for which the new address is a next hop. Deciding whether it is necessary to update the TFIB is the responsibility of an 'address process'. This message is generated when an attempt to create the address process fails.","This is an informational message. As long as it needs the process, the system will regularly attempt to create it. If this message occurs repeatedly, copy it exactly as it appears and report it to your technical service representative."
"TAGCON","4","UNAVAILABLE","Failure to initialize tag allocation pool %d","The system was unable to initialize the data structure used to support allocation of tags for tag switching for the specified tag pool.","The system proceeds by ignoring the event. However, since the system will not be able to allocate tags from the tag pool, it will not advertise them to peers and, therefore, will not be able to forward tagged packets it receives (because it advertises no tags, it should not receive any tagged packets). Copy the message exactly as it appears and report it along with the startup and running configuration to your technical service representative."
"TAGCON","5","UNAVAILABLE","cannot queue TDP %s pie for %i(%s)","An attempt to queue a TDP PIE (protocol information element) for transmission to a TDP peer failed.","This is an informational message. Failure to queue a PIE for a peer should occur only when the TDP session with the peer no longer exists. The software should recover from this situation by discarding the TDP session and trying to establish a new one. If this message occurs repeatedly, copy it exactly as it appears and report it to your technical service representative."
"TAR_FS","3","IMAGE_FILE_INVALID","[chars] file not found in archive","The tar file system could not locate the relevant tar element inside the archive.","Check whether the archive is complete and not corrupted, or if it is the wrong format. If the problem can be recreated with debug ifs file turned on, you can more quickly identify the problem. Save the output of the archive tar /table archive-name command if it is a pure tar archive, or the show image contents file archive-name command if the archive is a system image. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TBRIDGE","4","UNAVAILABLE","%s received on %s - invalid media for transparent bridging","Transparent bridging was configured on an interface that does not support it.","Remove transparent bridging from the configuration on the specified interface."
"TBRIDGE","4","UNAVAILABLE","Destination VC unknown for packet","A transparently bridged packet destined for an ATM interface cannot be fully addressed.","Clear the bridge table to force re-learning of all addresses."
"TBRIDGE","4","UNAVAILABLE","Giant received on %s, %d exceeds %d DA %e SA %e [0x%08x]","A packet was received that exceeds the expected maximum transmission unit (MTU) length for the receiving interface. The first four bytes of the packet following the source address are also provided to assist diagnosis.","Use the address and packet information provided to trace the source of these packets and reduce its MTU to conform to the standard for the given media."
"TBRIDGE","4","UNAVAILABLE","MAC-address table size limit (%lu entries) reached","The total number of bridge MAC-address table entries (across all bridge groups) has reached the configured maximum limit.","Check the bridge tables to determine the origin of the bridge MAC-address table entries. Check the network configuration and ensure that the entries are as expected. Use the bridge mac-address-table limit configuration command to either increase the maximum limit or to disable limit-checking altogether."
"TBRIDGE","4","UNAVAILABLE","No VC's configured for bridging on %s","An ATM interface was configured for transparent bridging without also specifying the associated virtual circuits.","Configure the required virtual circuits on the specified interface."
"TBRIDGE","4","UNAVAILABLE","Subscriber SA %e moved or loop between circuits %d and %d","A subscriber bridged packet dropped because potential circuit loop or roaming host at subscriber end of network.","Clear bridge table. If problem persists it is not a roaming host, but a loop between virtual circuits at subscriber end of network. Take looping virtual circuits out of service and/or shut the software interface they are on while subscriber is contacted to remove loop condition at subscriber end of network."
"TBRIDGE","4","UNAVAILABLE","Unexpected encapsulation received on %s %s","The transparent bridging driver received a packet with unrecognizable encapsulation. The packet had to be discarded.","This could indicate a network media error or that a protocol which is newer than this version of the Cisco IOS software is being used. If it is believed that the dropped packets are of a real protocol, upgrade to a new version of the software which handles it."
"TBRIDGE","4","UNAVAILABLE","XMACACCESS: Invalid extended access list %d","This is a configuration problem. The specified extended access list either does not exist or contains an error.","Correct the configuration problem."
"TBRIDGE","4","UNAVAILABLE","invalid action found for %e on %s - %08x","A software or hardware error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"TCAM_MGR","3","BAD_FIRST_DYN_REGION","[dec]","A TCAM error was detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCAM_MGR","3","BAD_LAST_DYN_REGION","[dec]","A TCAM error was detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCAM_MGR","3","INTERNAL_ERROR","[chars], [chars], [dec]","A TCAM error was detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCAM_MGR","3","INVALID_OPERATION","[chars], [dec]","A TCAM error was detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCAM_MGR","3","INVALID_REG_TYPE","[chars], [dec]","A TCAM error was detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCAM_MGR","3","MALLOC_FAIL","[chars], [chars]","A TCAM error was detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCAM_MGR","3","OP_FAIL","[chars] failed for application [chars], application entry [hex] with [chars] error","A TCAM error was detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCAM_MGR","3","UNUSUAL_BUG_WARNING","[chars] mbu [hex] free_array_index [dec] region_id [dec]","A TCAM error was detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCAMMGR","3","GROW_ERROR","cam region [dec] can not grow","This CAM region is configured as a static region with a fixed number of entries, and a call was requested to add more CAM entries to the specified region.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCAMMGR","3","HANDLE_ERROR","cam handle [hex] is invalid","The CAM handle that was used by the caller is invalid.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCAMMGR","3","INDEX_ERROR","cam value/mask index [dec] is invalid","The CAM index that was used by the caller is invalid.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCAMMGR","3","MOVE_ERROR","cam entry move from index [int] to index [int] failed","A move operation for a CAM entry from one index to another has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCAMMGR","3","REGION_ERROR","cam region [dec] is invalid","The CAM region is invalid.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCAMMGR","3","REGMASK_ERROR","invalid cam region [dec] mask [dec] pair","Only a predetermined set of masks are allowed in a region. The caller requested to install an entry in the specified region that contained an invalid mask for that region.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCATM","3","INTERNAL","[chars]","An operation that is required for proper operation of the TCATM has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCP","2","UNAVAILABLE","%s called but TCP not initialized","An internal software error occurred.","If this message recurs, copy the message exactly as it appears and contact your technical support."
"TCP","2","UNAVAILABLE","Bad TCB refcount: TCB 0x%x, refcnt %d","An internal software error occurred","If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance."
"TCP","2","UNAVAILABLE","Callback failed to accept connection from %s(%d) to %s(%d) -- discarding","An internal software error occurred.","If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance."
"TCP","2","UNAVAILABLE","Invalid TCB encaps pointer: 0x%x","An invalid TCP ENCAPS is used.","If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance."
"TCP","2","UNAVAILABLE","Invalid TCB pointer: 0x%x","An invalid TCB is used.","If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance."
"TCP","2","UNAVAILABLE","Multiple entry for packet %x","An internal software error occurred.","If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance."
"TCP","2","UNAVAILABLE","Tty%t, buffering bug","An internal software error occurred.","If this message recurs, contact your technical support representative."
"TCP","2","UNAVAILABLE","Tty%t, tcp_putbyte() with blocking disabled","An internal software error occurred.","If this message recurs, contact your technical support representative."
"TCP","2","UNAVAILABLE","Tty%t, tcp_putbyte() write disabled","TCP received a packet from a user application after the connection was already halfclosed.","Determine which TCP application is still sending after the connection was halfclosed."
"TCP","2","UNAVAILABLE","Tty%t: Bad refcnt for packet 0x%x during retransmit, %s(%d) to %s(%d), state %d","An internal software error occurred.","If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance."
"TCP","3","BADMSS","Incorrect mss [dec] observed","The maximum segment size is incorrect. TCP cannot guarantee further reliable operation for this connection.","Check the MTU for the interface and increase it as required. If, after adjusting the MTU, this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCP","3","CHKPT_INIT","TCP failed to initialize checkpoint storage: %s","The TCP process failed to initialize checkpoint storage for ports.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCP","3","ERR_DUMP_DEB","netdump_print_context failed, %d","Netdump print failed while dumping a process debug context.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCP","3","ERR_MD5_INVALID","MD5 validation failed, incoming packet src: %s:%d, dst: %s:%d","MD5 validation failed on an incoming packet.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCP","3","ERR_MD5_WRITE","MD5 option write failed, dst: %s:%d","The TCP process failed to write an MD5 option.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCP","3","ERR_NETWORK_INIT","TCP failed to connect with network layer: %s, error %s","TCP initialization with the network layer failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCP","3","ERR_OUT_BUFF","ran out of buffer with %ld bytes %s to send","TCP ran out of buffer space while copying segment data.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCP","3","ERR_PAK_FSV","%s","An FSV operation failed on the packet.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCP","3","ERR_PAK_DISCARD","%s: %s,  <%s:%d> -> <%s:%d>","Packet information from a discarded packet is displayed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCP","3","ERR_PCB_VECTOR","ip_pcb_get_family_vector failed, %d","The TCP process failed to get a pointer to the PCB family vector.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCP","3","ERR_SET_APP_LEN","%s: set_Application_length failed: %s","The TCP process failed to set an application buffer for the segment.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCP","3","FORKFAIL","Failed to start a process to negotiate options.","The system failed to create a process to handle requests from a client. This condition could be caused by insufficient memory.","Reduce other system activity to ease memory demands."
"TCP","3","SOCKET_RESMGR_ATTACH","Failed to setup the transport as a resource manager: %s","The TCP process failed to advertise itself to the system as a resource manager.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCP","3","TRACE_ERR","%s error (%d). Premature trace termination for control block 0x%p","A trace terminated prematurely.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCP","4","ERR_PAK_CLIENT","%s, res %d","A packet client operation failed in TCP.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCP","4","WARNING_DEBUG","%s","TCP failed to open the console device for debug.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCP","6","INFO_RCV_SIG","recieved signal %d","The TCP process received a signal.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCP","6","MD5NOSPACE","Insufficient space for MD5 option","There was insufficient space for the MD5 option. This condition should not occur, because the MD5 option, when requested, is required and is given preference over other TCP options.","Unconfigure other TCP options, if any, in an attempt to create space for the MD5 option. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TCP","7","ERR_TCP_INIT","TCP failed to initialize: %s, error %s","TCP initialization failed.Error Message    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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the %TDM-1-UNAVAILABLE: Motherboard TDM init failure: stream %d, channel %d, channel register 0x%x, control register 0x%x. Explanation    A TDM port on the system motherboard failed to be initialized. The error message specifies which port. This is possibly due to a hardware failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TDM","1","UNAVAILABLE","Slot %d TDM init failure: stream %d, channel %d, channel register 0x%x, control register 0x%x.","A TDM port failed to be initialized. The error message specifies which port. This is possibly due to a hardware failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TDM","3","UNAVAILABLE","Slot %d bad board ID 0x%x detected.","The specified board returned an ID that was not recognized by the operating system. This could be due to a hardware failure reporting an incorrect ID or because this software predates the hardware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TDM","4","UNAVAILABLE","Bad connection requested: slot %d, stream %d, channel %d to slot %d, stream %d, channel %d.","The TDM cross-connect that was requested was not possible. This is probably because one of the devices either does not exist or is not properly configured for TDM.","Check the command for errors and the ports for correct configuration before trying again. Note that the ype option of the dm-group command only applies if the mode cas command is enabled. If configuring cross-connect pass-through from UIO serial port 0 or 1 to a controller, the encapsulation clear-channel command must be configured on the serial port."
"TDM_CLOCK_SYNCHRONIZATION","4","UNAVAILABLE","TDM frame clock %s lost lock - clock source failed.","The clock source has failed.","If alternate source is available, it will be used."
"TDM_CLOCK_SYNCHRONIZATION","4","UNAVAILABLE","TDM frame clock source transitioned from Priority %d %s %s to Priority %d %s %s","This warning message indicates a change in the clock source.","No action required."
"TDM_CLOCK_SYNCHRONIZATION","4","UNAVAILABLE","TDM frame clock state change, state: %s","This debug message indicates a clock state change","No action required."
"TDM_CLOCK_SYNCHRONIZATION","4","UNAVAILABLE","TDM frame clock state error, state: %s event: %s","This warning message indicates a invalid clock event","No action required."
"TDP","3","UNAVAILABLE","%s","An action attempted by the Tag Distribution Protocol (TDP) encountered an unexpected condition.","ACTION_COPY_REPORT_TDP"
"TDP","3","UNAVAILABLE","%s","An action attempted by the Tag Distribution Protocol (TDP) implementation failed.","ACTION_COPY_REPORT_TDP"
"TDP","3","UNAVAILABLE","Can't alloc KA PIE","An attempt to allocate a buffer for Tag Distribution Protocol (TDP) Keep Alive protocol information element (PIE) has failed.","The system will continue by omitting transmission of the TDP Keep Alive PIE. This may result in termination of one or more TDP sessions as the peers time out the sessions. If this message persists, reduce other system activity if possible, and call your technical service representative for assistance."
"TDP","3","UNAVAILABLE","Interface %s, Bad VPI/VCI range. Can't start a TDP session","The VPI range exchanged between the Tag Distribution Protocol (TDP) peers is non-overlapping.","The system will not be able to create a TDP session between the affected TDP peers. Re-issue the tag-switching vpi command on the appropriate interface with the correct VPI range."
"TDP","3","UNAVAILABLE","Interface %s, Resource failure. Can't start a TDP session","An attempt to allocate a buffer for Tag Distribution Protocol (TDP) TAGATM VPI/VCI ranges has failed.","The system will not be able to create a TDP session between the affected TDP peers. If this message persists, reduce other system activity if possible, and call your technical service representative for assistance."
"TDP","3","UNAVAILABLE","peer %s, read failure","An error occurred while attempting to read a TDP PDU received from a peer.","ACTION_NEW_SESSION_TDP"
"TDP","3","UNAVAILABLE","peer %s; address len %d","A Tag Distribution Protocol (TDP) protocol information element (PIE) containing an address with a bad length has been received from a peer.","ACTION_IGNORE_REST_OF_PIE_TDP"
"TDP","3","UNAVAILABLE","peer %s; alist_type %d; %s pie","A Tag Distribution Protocol (TDP) protocol information element (PIE) containing an address list type that is unexpected for the situation has been received from a peer.","ACTION_IGNORE_PIE_TDP"
"TDP","3","UNAVAILABLE","peer %s; alist_type %d; %s pie","A Tag Distribution Protocol (TDP) protocol information element (PIE) containing an unknown address list type has been received from a peer.","ACTION_IGNORE_PIE_TDP"
"TDP","3","UNAVAILABLE","peer %s; blist_type %d; %s pie","A Tag Distribution Protocol (TDP) protocol information element (PIE) containing a binding list type that is unexpected for the situation has been received from a peer.","ACTION_IGNORE_PIE_TDP"
"TDP","3","UNAVAILABLE","peer %s; blist_type %d; %s pie","A Tag Distribution Protocol (TDP) protocol information element (PIE) containing an unknown binding list type has been received from a peer.","ACTION_IGNORE_PIE_TDP"
"TDP","3","UNAVAILABLE","peer %s; format error for pie type 0x%x","A Tag Distribution Protocol (TDP) protocol information element (PIE) that is malformed has been received from a TDP peer.","ACTION_NEW_SESSION_TDP"
"TDP","3","UNAVAILABLE","peer %s; mlist_type %d; %s pie","A Tag Distribution Protocol (TDP) protocol information element (PIE) containing an unknown metric list type or one that is unexpected for the situation has been received from a peer.","ACTION_IGNORE_PIE_TDP"
"TDP","3","UNAVAILABLE","peer %s; prefix len %d","A Tag Distribution Protocol (TDP) protocol information element (PIE) containing a destination prefix with a bad length has been received from a peer.","ACTION_IGNORE_REST_OF_PIE_TDP"
"TDP","3","UNAVAILABLE","peer %s; unexpected pie type 0x%x","A Tag Distribution Protocol (TDP) protocol information element (PIE) that is unexpected for the situation has been received from a peer.","ACTION_IGNORE_PIE_TDP"
"TDP","3","UNAVAILABLE","peer %s; unknown pie type 0x%x","An unknown Tag Distribution Protocol (TDP) protocol information element (PIE) type has been received from a peer.","ACTION_IGNORE_PIE_TDP"
"TDP","3","UNAVAILABLE","unexpected event: peer %i(%s), state=%s, event=%s%s","An operation on the state machine for a TDP peer failed.","ACTION_COPY_REPORT_TDP."
"TDP","4","UNAVAILABLE","Peer %s; %s","The session parameters proposed by an LDP peer differ from those preferred by the platform. The differences are not sufficient to prevent the LDP session from being established, but may have an impact on label distribution operation","If the parameters identified relate to the optional path vector-based loop detection mechanism, note that the IETF LDP specification recommends that when Loop Detection is enabled in a portion of a network, it is recommended that all LSRs in that portion of the network be configured with Loop Detection enabled and with the same path vector limit. If the parameters identified relate to some other aspect of the LDP session and the message occurs repeatedly, copy it exactly as it appears and report it to your technical service representative."
"TDP","4","UNAVAILABLE","Peer = %s %s(%i%m) Maxhop=%d hopcount=%d %s","This message appears when signalling to establish an MPLS Label Switched Path (LSP), or Tag Switching Tag Switched Path, discovers a transient loop in the path to the LSP destination. Normally this is a transient condition.","ACTION_LOOPING_LSP"
"TDP","4","UNAVAILABLE","Peer = %s %s(%i%m) hopcount=%d %s","This message appears when LDP loop detection is configured and signalling to establish an MPLS Label Switched Path (LSP) detects a transient loop in the path to the LSP destination. Normally this is a transient condition.","ACTION_LOOPING_LSP"
"TDP","4","UNAVAILABLE","cannot set %s%s TDP ident","The Tag Distribution Protocol (TDP) requires each TDP instance have a TDP identifier. An attempt to set the TDP identifier for the shown VRF or TDP instance has failed.","This is an informational message. As long as it needs to set its chassis TDP identifier the system will periodically attempt to do so until it succeeds. If this message occurs repeatedly, copy it exactly as it appears and report it to your technical service representative."
"TDP","4","UNAVAILABLE","peer %s, %s","A violation of the TDP protocol by a TDP peer has been detected.","ACTION_NEW_SESSION_TDP"
"TDP","5","UNAVAILABLE","%s","This is an informational message generated by the Tag Distribution Protocol (TDP) implementation.","No action is required."
"TDP","5","UNAVAILABLE","tag advertise-tags has no effect for tc-atm","EXPLANATION_ACL_TDP","No action is required."
"TEMUX84","3","UNAVAILABLE","temux84 Byte-Sync indirect access failed, %s","hardware busy bit not cleared","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TEMUX84","3","UNAVAILABLE","temux84 RTTB indirect access failed, %s","hardware busy bit not cleared","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TEMUX84","3","UNAVAILABLE","temux84 SBI indirect access failed, %s","hardware busy bit not cleared","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TEMUX84","3","UNAVAILABLE","temux84 T1E1 indirect access failed, %s","hardware busy bit not cleared","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TEMUX84","3","UNAVAILABLE","temux84 T3E3 PMON update failed, %s","T3E3 PMON counter failed to latch","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TENGIGE_LC","3","LASER_TEMP_ERR","Laser Temperature Alarm : [dec]/[dec]","A laser temperature alarm condition has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TENGIGE_LC","3","MIB_TENGIGE_LASER_FAILURE","Laser failure detected during soft-start procedures : [chars]","A laser failure has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TENGIGE_LC","3","MIB_TENGIGE_LOSYNC_ALM","Loss of Sync ; [chars]","The Gigabit Ethernet function lost its synchronization.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TENGIGE_LC","3","TENGIGE_LOSYNC_ALM","[chars] side Loss of Sync lock: [chars]","The Gigabit Ethernet function lost its synchronization.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TENGIGE_LC","3","TENGIGE_LOSYNC_ALM_CLR","CLEARED : [chars] Loss of Sync lock: [chars]","The Gigabit Ethernet function lost its synchronization.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TENGIGE_LC","6","LASER_DISABLED","Laser disabled as per user configuration [[dec]/[dec]]","The laser has been disabled as specified by the user configuration.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TENGIGE_LC","6","LASER_DISABLED_BY_HW","Laser disabled as per laser safety configuration [[dec]/[dec]]","The laser has been disabled as specified by the safety configuration.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TENGIGE_LC","6","MIB_TENGIGE_TRUNK_LOSYNC_PALM","Trunk side Loss of Sync Prealarm; [chars]","The trunk lost its synchronization while it was receiving data.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TENGIGE_LC","6","TENGIGE_TRUNK_RX_LOSYNC_PALM","Trunk side Loss of Sync lock Prealarm: [chars]","The trunk lost its synchronization while it was receiving data.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TESTPA","3","UNAVAILABLE","bay [%d] analyze failed","The TestPA port adapter driver failed to successfully complete the necessary tasks for initial bring up of the port adapter. This is typically due to shortage of memory. Previous messages in the log will indicate the exact reason for the failure. The port adapter will be deactivated.","Verify that the port adapter is properly seated in the bay."
"TESTPA","3","UNAVAILABLE","bay [%d] dma error: %s","A DMA failure occurred.","Verify that the port adapter is properly seated in the bay."
"TESTPA","3","UNAVAILABLE","bay [%d] initialization failed: %s","The TestPA port adapter driver failed to successfully initialize the hardware on the TestPA port adapter. The port adapter will be deactivated.","Verify that the port adapter is properly seated in the bay."
"TESTPA","3","UNAVAILABLE","bay [%d] powered off","The port adapter has been powered off. Other messages in the log specify the cause of this event.","If possible, correct any errors indicated by the other messages occurring at the time of this message. If the error persists, verify that the port adapter is properly seated in the bay."
"TI1570","1","UNAVAILABLE","%s %s","The ATM Port Adapter failed to complete hardware initialization. Details of the failure are shown in the error message.","Reset the adapter. This should not be a recurring condition. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TI1570","1","UNAVAILABLE","%s for subunit %d in bay %d","The ATM Port Adapter failed to complete hardware initialization.","Reset the adapter. This should not be a recurring condition. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TI1570","1","UNAVAILABLE","Only %#x bytes of memory available for %s","The port adaptor needs more PCI memory. The installed amount is less than required by the drivers for packet buffers.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TI1570","1","UNAVAILABLE","PCI configuration for %s in slot %d","The ATM Port Adapter failed to complete hardware initialization.","Reset the adapter. This should not be a recurring condition. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TI1570","1","UNAVAILABLE","VIP only supports one PA-A1 ATM LITE PA. The other PA bay must be emptied in order for the PA-A1 ATM LITE PA to function.","The bandwidth requirements of the installed port adapters exceed the processor's rated capability.","Either remove one of the port adapters or upgrade the VIP."
"TI1570","3","UNAVAILABLE","%s block command (code %d) failed, error code %d","An internal hardware or software error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TI1570","3","UNAVAILABLE","%s receive freeze %d","This message indicates excessive traffic congestion on the ATM interface may have resulted in cell loss. The PCI-ATM interface's cell buffers were full when a cell arrived on the interface, resulting in a receive freeze condition. A small number of freezes might not be a cause for concern.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TI1570","3","UNAVAILABLE","%s transmit freeze %d","This message indicates the PCI-ATM interface had to stop the transmitter while waiting for data. A small number of freezes might not be a cause for concern.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TI1570","3","UNAVAILABLE","%s tx buffer data start not aligned to 32 bit boundary, data block0x%08x, data start 0x%08x","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TI1570","3","UNAVAILABLE","Bay %d device ID seen as %#x, expected #%x","The ATM-PCI Port Adapter driver found incorrect device ID's on the specified card. This could indicate either a hardware failure or that the software needs to be upgraded to recognize newer hardware.","Power down, reseat the interface card, and reboot. Or investigate if newer software is needed for your hardware. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TI1570","3","UNAVAILABLE","Bay %d device ID seen as %#x, expected %#x","The ATM-PCI port adapter driver could not recognize the interface chips.","Power down, reseat the interface card, and reboot. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TI1570","3","UNAVAILABLE","Found %d out of %d devices (ID %08X) in bay %d","The ATM-PCI Port Adapter software driver found fewer devices than it was configured to expect. This could mean that the missing one(s) failed to start and may have failed.","Try shutting off the power, re-seating the card, and rebooting. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TI1570","3","UNAVAILABLE","Interface %s, %s not supported","An attempt was made to configure a rate queue on an ATM Lite port adapter that does not support rate queues.","Check the configuration and try again, avoiding unsupported features."
"TI1570","3","UNAVAILABLE","Interface %s, Failed to down vc %d (Cause: %s)","An ATM virtual circuit could not be shut down for the reason shown in the error message. This probably indicates a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TI1570","3","UNAVAILABLE","Interface %s, Failed to setup vc %d (Cause: %s)","This probably indicates a hardware failure in the ATM-PCI Port Adapter.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TI1570","3","UNAVAILABLE","RX DMA entry %#x not going inactive","A receive DMA channel failed to deactivate during shutdown of a virtual circuit. This failure could originate in hardware or software.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TI1570","3","UNAVAILABLE","TI1570 unit %d: PCI memory unavailable.","The system experience memory exhaustion in the PCI/packet memory. This is probably due to heavy traffic congestion but could also be a software error.","Review the configuration for performance bottlenecks. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TI1570","3","UNAVAILABLE","TI1570 unit %d: PCI mini buffer unavailable.","An internal hardware or software error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TI1570","3","UNAVAILABLE","TI1570 unit %d: PCI parity error (0x%08x)","A parity error occurred on the PCI bus. This probably indicates an existing or developing hardware failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TI1570","3","UNAVAILABLE","TI1570 unit %d: Receive Channel Halt","This probably indicates a hardware failure in the ATM-PCI Port Adapter.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TI1570","3","UNAVAILABLE","TI1570 unit %d: SYSTEM memory unavailable.","Memory exhaustion has occurred in the ATM-PCI Port Adapter driver.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TI1570","3","UNAVAILABLE","TI1570: received corrupted shadow particle pointer","The ATM-PCI Port Adapter driver experienced an internal error, probably due to software but possibly from a hardware failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TI1570","3","UNAVAILABLE","TX DMA not flushed","A transmit DMA channel failed to flush its buffers during shutdown of an ATM interface. This failure could originate in hardware or software.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TI1570","5","UNAVAILABLE","ti1570_vc_setup failed. (vci %d of the last vpi %d exceeds (vc-per-vp - 3)).","The TI1570 chip reserves 3 RX DMA channels for OAM cells. As a result, the last 3 VCIs of the last VPI block cannot be used for regular traffic.","Avoid try different vci/vpi combinations."
"TI1570","7","UNAVAILABLE","TI1500 framer interrupt isr1 0x%02x, isr2 0x%02x, isr3 0x%02x","This is a informational/debugging message indicating that the ATM-PCI Port Adapter driver received and handled a framer interrrupt","LOG_STD_NO_ACTION."
"TIB","3","UNAVAILABLE","%i/%i, %s; unexpected tag state=%d","An operation on the Tag Information Base (TIB) involving a locally assigned (incoming) tag failed.","ACTION_OMIT_OPER_TIB"
"TIB","3","UNAVAILABLE","%i/%i, peer %s; tag %d; %s","An operation on the Tag Information Base (TIB) involving a tag assigned by a TDP peer failed.","ACTION_OMIT_OPER_TIB"
"TIB","3","UNAVAILABLE","%i/%i; %s","An operation on the Tag Information Base (TIB) data structure failed.","ACTION_COPY_REPORT_TIB"
"TIB","3","UNAVAILABLE","%s","An action attempted by the Tag Information Base (TIB) implementation failed.","ACTION_COPY_REPORT_TIB"
"TIB","3","UNAVAILABLE","Cannot allocate TIB","During initialization for tag switching an attempt to initialize the Tag Information Base (TIB) failed. A probable cause is insufficient memory","ACTION_COPY_REPORT_TIB"
"TIB","3","UNAVAILABLE","TIB revision number wrapped; toggling dynamic tag switching off and on to recover.","The TIB revision number used to manage advertisement of tags to TDP peers overflowed. This will result in faulty tag distribution to TDP peers. The system recovers by toggling dynamic tag switching off and on, which forces the revision number to be re-initialized.","None required."
"TIB","3","UNAVAILABLE","Unexpected event; state=%s, event=%s","An operation on the Tag Information Base (TIB) state machine failed.","ACTION_COPY_REPORT_TIB."
"TIB","5","UNAVAILABLE","%i/%i, peer %s; tag %d; Unexpected LDP label release; %s","An operation on the Tag Information Base (TIB) involving a tag assigned by a TDP peer failed.","This is an informational message. The system proceeds by omitting the tag operation. This will not result in impaired or faulty behavior for tagged packets for this destination."
"TIB","5","UNAVAILABLE","%i/%i, tag %d; Withdrawn tag record has timed out.","Record associated with a withdrawn label has timed out before receiving acknowledgements from all peers.","This is an informational message. This will not have any operational impact. The system will ignore any subsequently received release messages associated with the label."
"TID_HA","3","ISSUERR","[chars] [chars]","An error occurred during an in-service software upgrade (ISSU) versioning operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TID_HA","3","ISSUERRCF","[chars] checkpoint code [dec]","An error occurred during an ISSU versioning operation due to an error in the checkpoint facility.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TID_HA","3","RXFAIL1","[chars]","An error occurred while receiving a table ID synchronization message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TID_HA","3","RXFAIL2","[chars], type [dec], version [dec], flags [hex]","An error occurred while receiving a table ID synchronization message.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information."
"TID_HA","3","RXFAIL3","[chars] type [dec], version [dec],flags [hex], application [dec], action [dec], tableid [dec], name [chars]","An error occurred while receiving a table ID synchronization message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TID_HA","3","SYNCFAIL","[chars]","Internal table ID information may have not been synchronized to the standby unit correctly.","Reload the standby unit. If the error condition persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TID_HA","3","SYNCFAILCF","[chars] checkpoint code [dec]","Internal table ID information may have not been synchronized to the standby unit correctly due to an error in the checkpoint facility.","Reload the standby unit. If the error condition persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TID_HA","3","TXFAIL","[chars], name [chars] tableid [dec] action [dec]","An error occurred while sending the internal table ID information.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TID_HA","3","TXFAILCF","[chars], name [chars], tableid [dec], action [dec], checkpoint code [dec]","Failed to send internal table ID information due to an error in the checkpoint facility.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TLV","3","UNAVAILABLE","Reading data type %d","An expected field in the TLV buffer was either missing or malformed","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TLV","3","UNAVAILABLE","Unable to write type %d","An attempt to update a TLV entry failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TMCIPC","4","UNAVAILABLE","Received a duplicated IPC record for %s with seq #:%d.","The sequence # on received record is the same as the previous received IPC msg.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TMQ","3","UNAVAILABLE","TMQ, Attempt to delete entry not in queue","An attempt was made to delete an entry not in the queue.","Advisory message only. No action required."
"TIDP","3","RESTART","Restarting TIDP due to unexpected error","An unexpected error has occurred in the Threat Information Distribution Protocol (TIDP) process. TIDP has been restarted in an attempt to restore operation.","Enter the debug tidp errors and debug tidp events commands to gather data that may help identify the nature of the error. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TIDP","4","AUTHFAIL","Message from %s, %i failed authentication","The signature of a received message failed authentication. The message has been dropped.","Check the local and peer configurations to make sure that compatible authentication key sets are used."
"TIDP","4","REPLAYMSG","Unexpected message from %s, %i received","A message with a sequence number outside of the acceptable range was received and has been dropped. The message might be a replay message and might indicate an intrusion attack.","Verify that the peer's hardware and configuration has not been altered. Verify connectivity to the peer."
"TIDP","4","SRCCHANGED","Address changed was being used by TIDP","An interface IP address was changed, but the former address was being used as the Threat Information Distribution Protocol (TIDP) source address. TIDP cannot operate properly if the address is not local.","Restore the original IP address to the original interface or to a new interface, or change the TIDP source address."
"TIDP","5","BADMSG","Message from %s, %i failed validation","A message has failed basic header and range check validation. The message has been dropped.","Check the local and peer configurations to make sure that compatible versions of TIDP and encryption keys are used."
"TIDP","5","OVERSIZE","Oversized message received from %s, %i","A larger than expected message was received and has been dropped.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TIDP","5","PEERSRCCHANGED","TIDP source address of the connection to peer %i is changed","The Threat Information Distribution Protocol (TIDP) source address changed. The change might be caused by DHCP renewal or by the user manually changing the IP address at the interface.","No action is required."
"TIDP","5","REGFAIL","Failed to register to peer %s, %i, group %u","Attempts to register with the specified peer have failed. Another attempt will be made after the configured maximum retry interval.","Verify connectivity to the peer and make sure that the configuration between peers is compatible."
"TIDP","6","DUPLICATE","Duplicate message from %s, %i received","A message was received that had the same sequence number as a previously received message. The message has been dropped.","No action is required."
"TINY_FRAG_POLICER","6","AGGREGATE_THRESHOLD_EXCEEDED","[dec] bps: it is recommended to reduce the hi threshold value","The fragment offset == 1 (fo1) packets aggregate threshold has exceeded the acceptable value.","Reduce the interface high-threshold values."
"TINY_FRAG_POLICER","6","HI_THRESHOLD_EXCEEDED","[dec] bps: installing rate limiter for vlan [int] on interface [chars]","The fragment offset == 1 (fo1) packets high threshold has exceeded the acceptable value.","This is an informational message only. No action is required."
"TINY_FRAG_POLICER","6","RATELIMITER_FAILED","could not [chars]install rate limiter for vlan [int] interface [chars]","The fragment offset == 1 (fo1) rate installer failed due to resource issues.","This is an informational message only. No action is required."
"TINY_FRAG_POLICER","6","RATELIMITER_REMOVED","removing rate limiter for vlan [int] from interface [chars]","The fragment offset == 1 (fo1) packets dropped below the low threshold.","This is an informational message only. No action is required."
"TMS","2","PROCESS_ERR","Router could not create a TMS controller process","The router was unable to create a TIDP-based Mitigation Services (TMS) controller process.","Reload the device."
"TMS","4","UNAVAILABLE","%s| Group=%u|%s Type=%d| Flags=%d","This message informs that the controller has received an invalid or unexpected packet from the consumer","Check the specified consumer for the TMS protocol operation"
"TMS","4","UNAVAILABLE","An unknown Timer operational error occurred","The TMS process cannot operate due to an internal system error.","Reload the device"
"TMS","4","UNAVAILABLE","An unknown operational error occurred.","The EOU process cannot operate due to an internal system error.","Reload the device"
"TMS","4","UNAVAILABLE","PROCESS=%s| ACTION=%s.","This message indicates that the specified process is stopped.","Reload the device"
"TMS","4","UNAVAILABLE","UNKNOWN Event for Event=%d.","This is an unknown message for the TMS controller process.","File a ddts with Cisco"
"TMS","4","UNAVAILABLE","Unknown message event reveived","The TMS process received an unknown message event.","If this message recurs, reload the device."
"TMS","6","UNAVAILABLE","%s","This messages informs that the consumer has cleared all the stats.","This is an informational message and no action is required."
"TMS","6","UNAVAILABLE","%s","This messages informs that the tms consumer is configured or unconfigured","This is an informational message and no action is required."
"TMS","6","UNAVAILABLE","%s| Group=%u|%s Action=%s| Start TID=%d| End TID=%d","This message informs that the controller has sent a reset request for an action to a specific consumer or a group","This is an informational message and no action is required."
"TMS","6","UNAVAILABLE","%s| Group=%u|%s Start TID=%d| End TID=%d","This message informs that the controller has sent a status request to a specific consumer or a group","This is an informational message and no action is required."
"TMS","6","UNAVAILABLE","%s| Group=%u|%s Status=%s","This messages informs that a consumer is registered or deregistered on the specifed group","This is an informational message and no action is required."
"TMS","6","UNAVAILABLE","%s| Group=%u|%s Status=%s","This messages informs that a group is configured or unconfigured on on the specifed host","This is an informational message and no action is required."
"TMS","6","UNAVAILABLE","%s| Group=%u|%s TID=%d","This message informs that the controller has sent a threat message to a specific consumer or a group","This is an informational message and no action is required."
"TMS","6","UNAVAILABLE","%s| Group=%u|%s Threat=%d| Version=%d| Action=%s","This messages informs the status of a threat on a consumer in the specifed group","This is an informational message and no action is required."
"TN","2","BADCONN","Bad conn pointer [hex] closing all connections on terminal line [dec]","An internal software error has occurred.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TN","2","BADLOGIN","Bad login string pointer %#x","An internal software error occurred.","If this error recurs, then issue the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information."
"TN","3","UNAVAILABLE","Illegal state %d","An internal software error occurred.","If this error recurs, then issue the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information."
"TN","3","UNAVAILABLE","Unknown return code %d from telnet_readline()","An internal software error occurred.","If this error recurs, then issue the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information."
"TN3270","2","UNAVAILABLE","Input Buffer overflow","A problem in TN3270 protocol was detected. Eight KB (8192) bytes of data were received without a TN3270 end-of-packet indicator. The TN3270 buffer overflowed.","Copy this error message exactly as it appears, and contact your technical support representative for assistance."
"TOPN_COUNTERS","3","MGMT","%s transmit receive byte count is excessive, 1st poll %llu, 2nd poll %llu","The traffic counter value on the interface is higher than expected. The module might be reporting an erroneous number.","Verify the traffic flow on the interface. If the flow does not match the TOPN report, contact your Cisco technical support representative."
"TOPN_COUNTERS","4","MEM_UNAVAIL","Memory was not available for handling the TopN request","The system cannot handle the TopN request because of lack of memory.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"TOPN_COUNTERS","5","AVAILABLE","TopN report [dec] is available","The specified report is ready and can be viewed by the users.","This is an informational message only. No action is required."
"TOPN_COUNTERS","5","DELETED","TopN report [dec] deleted by [chars]","The specified report has been deleted by the specified user.","This is an informational message only. No action is required."
"TOPN_COUNTERS","5","KILLED","TopN report [dec] task killed by [chars] [chars]","The system was in the process of generating the specified report, but the specified user terminated the report before its completion.","This is an informational message only. No action is required."
"TOPN_COUNTERS","5","NOPORTS","No interfaces in the system match the interface type for the generation of the topN report [dec]","There were no interfaces in the system that matched the interface type selected in the specified report.","This is an informational message only. No action is required."
"TOPN_COUNTERS","5","STARTED","TopN collection for report [dec] started by [chars]","The TopN report that was requested by the specified user starts with the specified report number.","This is an informational message only. No action is required."
"TPLUS","3","FORKFAIL","Failed to fork process for [chars].","A process fork failed, probably due to insufficient memory.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TR","2","UNAVAILABLE","Unit %d, %s error","This message is similar to the %TR-3-PANIC error message, but indicates a nonfatal error. This message appears in very unusual situations that should not arise in normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TR","2","UNAVAILABLE","Unit %d, PI %-08x %-08x %-08x %-08x %-08x %-08x","This message is similar to the %TR-3-PANIC error message, but indicates a nonfatal error. This message appears in very unusual situations that should not arise in normal operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TR","2","UNAVAILABLE","Unit %d, no memory for %s","The requested operation could not be accomplished because of a low memory condition.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"TR","2","UNAVAILABLE","Unit %d, panic %-08x %-08x %-08x","The Token Ring monitor firmware detected a fatal error that indicates an impending interface failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs._CRIT"
"TR","3","UNAVAILABLE","%s: Can't set address to a multicast (%e)","An attempt was made to set the Token Ring interface MAC address to a reserved multicast address.","Check your configuration. Make sure that your XNS and/or Novell Token Ring addresses have not inadvertently been set to reserved multicast addresses."
"TR","3","UNAVAILABLE","Bad unit number %d","This error message pertains only to the IGS. When displayed, it indicates that the system cannot find the chipset registers where it expects them to be. This is most likely a hardware error.","If this message recurs, call your technical support representative for assistance. It will be necessary to determine the hardware unit configuration."
"TR","3","UNAVAILABLE","Interface %s failed init diags (0x%04x), %s","The microcode attempted to run its diagnostics on the chip and failed.","Issue a clear interface command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TR","3","UNAVAILABLE","Interface %s, adapter check error (fatal) (%04x %04x %04x %04x)","The Token Ring monitor firmware detected a fatal error on the interface card.","Issue a clear interface command. If this message recurs, call your technical support representative for assistance. You may need to replace the interface card"
"TR","3","UNAVAILABLE","Interface %s, adapter check error (non-fatal)(%04x %04x %04x %04x)","The Token Ring monitor firmware detected a non-fatal error on the interface card.","Issue a clear interface command. If this message recurs, call your technical support representative for assistance."
"TR","3","UNAVAILABLE","Unit %d interface failure: %#x %#x %#x, idb state %d","The Token Ring Monitor firmware detected a fatal error due either to an internal software problem or to a hardware failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TR","3","UNAVAILABLE","Unit %d, Start completion and wrong idb state - state= %d","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TR","3","UNAVAILABLE","Unit %d, Tokenring firmware download failed got %#x, expected %#x, at address 0x%04x.%04x","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TR","3","UNAVAILABLE","Unit %d, bad bridge parameters: bridge_num=%d, max_rd=%d thisring=%d, targetring=%d","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TR","3","UNAVAILABLE","Unit %d, bad buffersize = %d","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TR","3","UNAVAILABLE","Unit %d, bad firmware type code during %s. type=%#x, fw=%#x","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TR","3","UNAVAILABLE","Unit %d, bad functional address=0x%08x, ring mode=0x%08x","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TR","3","UNAVAILABLE","Unit %d, change mode failed. result code=%#x, error code=%#x","An internal hardware or software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TR","3","UNAVAILABLE","Unit %d, init failed. result code=%#x, error code=%#x","The Token Ring hardware failed to initialize properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TR","3","UNAVAILABLE","Unit %d, no TMS380 firmware present. eagle=%#x, magic=%#x","An internal hardware or software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TR","3","UNAVAILABLE","Unit %d, open failed: %s, %s","The Token Ring interface was unable to insert itself into the ring. This is an indication of a busy or broken ring. The first character string in this error message indicates the stage of initialization at which the error occurred, and the second describes the error.","Try to open the interface again. This generally can be accomplished by issuing the clear interface tokenring command. If the error message recurs, call your Cisco technical support representative for assistance."
"TR","3","UNAVAILABLE","Unit %d, open failed: check the lobe cable DB-9 connection.","The Token Ring interface was unable to insert itself into the ring, and the error code returned indicates a wiring problem.","Check the cable connecting the router to the Token Ring MAU, and try to open the interface again. This generally can be accomplished by issuing the clear interface tokenring command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TR","3","UNAVAILABLE","Unit %d, reset failed, error code %-08x.","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TR","3","UNAVAILABLE","Unit %d, ring number (%d) doesn't match established number (%d).","The number you have configured for the local ring does not match the value currently in use on the ring.","Check the configuration to make sure you used the correct ring number. If it is correct, confirm the configuration of all other bridges on the ring to make sure they are using the same ring number."
"TR","3","UNAVAILABLE","Unit %d, set bridge failed (code %#x).","A hardware error occurred. The source routing accelerator (SRA) chip on the Token Ring card could not be initialized.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TR","3","UNAVAILABLE","Unit %d, set functional address failed (code %#x).","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TR","3","UNAVAILABLE","Unit %d, set group address failed (code %#x).","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TR","3","UNAVAILABLE","Unit %d, wire fault: check the lobe cable MAU connection.","The Token Ring hardware is reporting a wire fault condition.","Check the cable connecting the router to the Token Ring media attachment unit (MAU)."
"TR","6","UNAVAILABLE","%s: Ring Status: %s","This message is displayed when the Token Ring's status changed as determined by the chipset. This information also is used to automatically determine whether the interface is still usable to propagate network traffic.","LOG_STD_NO_ACTION"
"TR","6","UNAVAILABLE","TR%d: Ring Status: %s %s","This message is displayed when the Token Ring's status changed as determined by the chipset. This information also is used to automatically determine whether the interface is still usable to propagate network traffic. The meaning of each status code is shown in the Token Ring Status Codes Table. Code Explanation Fatal 0x8000 Signal loss Yes 0x4000 Hard error Yes 0x2000 Soft error No 0x1000 Transmit beacon Yes 0x0800 Lobe wire fault Yes 0x0400 Auto removal error Yes 0x0100 Receive request removed Yes 0x0080 Counter overflow No 0x0040 Single station No 0x0020 Ring recovery No","Check the Token Ring for the indicated condition."
"TRACKING","5","STATE","%d %s %s %s %s-%s","A tracked object has changed its state.","No action is required."
"TRAFFIC_UTIL","4","MONITOR_BACKPLANE_BELOW_THR","Backplane traffic utilization is %d%%, below threshold(%d%%) within %d second interval","The backplane traffic utilization is below the utilization threshold.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRAFFIC_UTIL","4","MONITOR_BACKPLANE_REACH_THR","Backplane traffic utilization is %d%%, reached threshold(%d%%) within %d second interval","The backplane traffic utilization has reached a utilization threshold.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRAFFIC_UTIL","4","MONITOR_FABRIC_EG_BELOW_THR","Module %d, Channel %d egress traffic utilization is %d%%, below or equal threshold(%d%%) within %d second interval","The fabric channel egress traffic utilization is below a utilization threshold.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRAFFIC_UTIL","4","MONITOR_FABRIC_EG_REACH_THR","Module %d, Channel %d egress traffic utilization is %d%%, reached threshold(%d%%) within %d second interval","The fabric channel egress traffic utilization has reached a utilization threshold.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRAFFIC_UTIL","4","MONITOR_FABRIC_IG_BELOW_THR","Module %d, Channel %d ingress traffic utilization is %d%%, below or equal threshold(%d%%) within %d second interval","The fabric channel ingress traffic utilization is below a utilization threshold.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRAFFIC_UTIL","4","MONITOR_FABRIC_IG_REACH_THR","Module %d, Channel %d ingress traffic utilization is %d%%, reached threshold(%d%%) within %d second interval","The fabric channel ingress traffic utilization has reached a utilization threshold.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRANGE","2","NOMEMORY","Alloc fail for time-range config buffer. Disabling distributed mode on lc","The system was unable to allocate a buffer to send time-range configuration information to the line cards.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show chunks commands and your pertinent troubleshooting logs. show chunks"
"TRANGE","2","WRONGREQUEST","Invalid request to allocate chunk of size %d","A request was made to allocate a time-range chunk greater than the maximum allowed size (TRANGE_LARGE_CHUNK_SZ).","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRANGE","2","WRONGSIZE","Incorrect length trange ipc xdr of len=%d received","The RP sent a time-range configuration message of the wrong size.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRANGE","2","NOMEMORY","Alloc fail for time-range config buffer. Disabling distributed mode on lc","Unable to malloc a buffer to send time-range configuration down to linecards.","Enter a show chunks command and report the output, along with this error message, to your technical support representative."
"TRANSCEIVER","3","ATTACH_FAILURE","Detected for transceiver module in [chars], module disabled","A software device driver attach has failed. This condition could be caused by a software, firmware, or hardware problem, but a software or firmware problem is more likely. As a result of the error, the module is disabled.","Power down and reseat the module. Hardware replacement should not occur on the first occurrence. Before requesting hardware replacement, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRANSCEIVER","3","CHECKSUM_ERROR","Detected in the transceiver module in [chars], module disabled","A checksum error was detected when reading the ID PROM of a transceiver module for the specified interface. As a result of the error, the module is disabled.","Power down and reseat the module. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRANSCEIVER","3","INIT_FAILURE","Detected for transceiver module in [chars], module disabled","An initialization failure occurred for the transceiver module for the specified interface. This condition could be caused by a software, firmware, or hardware problem. As a result of the error, the module is disabled.","Power down and reseat the module. Hardware replacement should not occur on the first occurrence. Before requesting hardware replacement, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRANSCEIVER","3","INTERNAL_ERROR","[chars]","The transceiver subsystem encountered an internal software error. The message contains text that can be used to help identify the nature of the problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRANSCEIVER","3","NOT_COMPATIBLE","Detected for transceiver module in [chars], module disabled","The transceiver module for the specified interface is not compatible with the interface. As a result of the error, the module is disabled.","Replace the module with a compatible transceiver. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRANSCEIVER","3","NOT_IDENTIFIED","Detected for transceiver module in [chars], module disabled","The transceiver module for the specified interface could not be identified and may not be compatible with the interface. As a result of the error, the module is disabled.","Replace the module with a compatible transceiver. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRANSCEIVER","3","NOT_SUPPORTED","Detected for transceiver module in [chars], module disabled","The transceiver module for the specified interface is not a Cisco supported module. As a result of the error, the module is disabled.","Replace the module with a Cisco supported transceiver. If the problem persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRANSCEIVER","3","OPER_ENABLE_FAILURE","Detected for transceiver module in [chars], module disabled","Failed to enable the transceiver module for the specified interface. This condition could be caused by a software, firmware, or hardware problem. As a result of the error, the module is disabled.","Power down and reseat the module. Hardware replacement should not occur on the first occurrence. Before requesting hardware replacement, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRANSCEIVER","3","RPC_FAILED","Application error rc = [dec]:","The system failed to retrieve the information required to execute the command.","Copy the message exactly as it appears on the console or in the system log. Enter the show version command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRANSCEIVER","3","RPC_LC_PROC_INIT_FAIL","Transceiver RPC init failure: [chars]","The system failed to create the resources required to process user interface commands for transceivers. The error is not fatal but some show commands could fail.","Copy the message exactly as it appears on the console or in the system log. Enter the show version command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRANSCEIVER","3","RPC_PROCESSING_ERROR","Transceiver RPC error: [chars]","A nonfatal error occurred during the processing of an RPC message.","Copy the message exactly as it appears on the console or in the system log. Enter the show version command to gather data that may help identify the cause of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRANSCEIVER","3","SM_CREATION_FAILURE","Transceiver OIR State Machine creation failed for [chars], module disabled.","A state machine could not be created for the transceiver OIR operation. If a memory allocation message was also received with this message, this condition indicates insufficient system memory. Other possible causes include an invalid subblock pointer.","If it is insufficient system memory, reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Otherwise, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRANSCEIVER","6","INSERTED","transceiver module inserted in [chars]","The online insertion and removal (OIR) facility detected a newly inserted transceiver module for the interface specified in the error message.","This is an informational message only. No action is required."
"TRANSCEIVER","6","REMOVED","Transceiver module removed from [chars]","The online insertion and removal (OIR) facility detected the removal of a transceiver module from the specified interface.","This is an informational message only. No action is required."
"TRUNK","3","UNAVAILABLE","Bad doorbell message type to framer: %d","An invalid or undefined message type was sent to the framer processor.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRUNK","3","UNAVAILABLE","Cannot send message to framer; no more messages available","The memory buffer for message passing between the trunk card and framer processors has been exhausted. Either the messages are not being picked up or are being generated too quickly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRUNK","3","UNAVAILABLE","Invalid framer firmware code file.","The software has detected an invalid framer firmware image that cannot be downloaded.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRUNK","3","UNAVAILABLE","Invalid value (%d) for shelf %d; exceeds %d","An internal software error occurred. An attempt was made to reference a shelf number larger than the installed maximum.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRUNK","3","UNAVAILABLE","No longer receiving heartbeats from framer CPU.","Communication from the framer processor to the trunk card processor has stopped. The framer processor is no longer passing status to the trunk card processor nor accepting messages from the trunk card processor.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRUNK","3","UNAVAILABLE","T1 Port %d on slot %d is now in drop-insert mode.","The user has dropped a T1 port on a CT3 card by pressing the pushbutton on the CT3 card. This is a disruptive action in that any existing calls will be dropped.Error Message    %TRUNK-3-UNAVAILABLE: T1 Port %d on slot %d taken out of drop-insert mode. Explanation    The user has restored a T1 port on a CT3 card by pressing the pushbutton on the CT3 card. This port was earlier dropped by the user and has now been taken out of dropped mode.Error Message    %TRUNK-3-UNAVAILABLE: Timed out waiting for framer CPU to respond. Explanation    The framer processor did not reply to the read request during a specified amount of time.Error Message    %TRUNK-3-UNAVAILABLE: Trunk card initialization failed due to: %s Explanation    Trunk card initialization has failed due to the specified reason.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRUNK","3","UNAVAILABLE","Unknown type 0x%x in shelf %d slot %d","The card in the specified slot and shelf was not recognized as either a T1 or E1 interface. This indicates a hardware or software failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRUNK","3","UNAVAILABLE","selected clock on slot %d port %d is bad.Accepting the config.","The clock status as reported by the framer is bad. Either no cable is plugged in or the port is indeed bad. Configuration is accepted and as soon as the port in reference turns good, it will be applied.","If user is configuring the clocks configuration in advance while there is no card in the corresponding slot or no cable is plugged in yet and if he is aware of this fact, then there is no action that needs to be taken. Otherwise, choosing another good clock and troubleshooting the bad clock from the port in reference is receommended."
"TRUNK_CLOCK","3","UNAVAILABLE","Failed to allocate memory for the clocks","The clock switching software has failed to allocate memory while adding a clock.","LOG_STD_NO_ACTION"
"TRUNK_CLOCK","6","UNAVAILABLE","Switching to the clock on slot %d port %d priority %d as the current primary has gone bad","The TDM primary clock has switched to a backup clock coming in via the specified trunk as the current primary clock has gone bad.","LOG_STD_NO_ACTION"
"TRUNK_CLOCK","6","UNAVAILABLE","Switching to the user configured external clock on motherboard","The TDM primary clock is switching from the default clock to the user configured external clock in motherboard.","LOG_STD_NO_ACTION"
"TRUNK_CLOCK","6","UNAVAILABLE","Switching to the user configured freerunning clock on motherboard","The TDM primary clock is switching from the default clock to the user configured free running clock in motherboard.","LOG_STD_NO_ACTION"
"TRUNK_CLOCK","6","UNAVAILABLE","Switching to the user configured trunk clock on slot %d port %d priority %d","The TDM primary clock is switching from the default clock to the user configured trunk clock.","LOG_STD_NO_ACTION."
"TRUNK_CLOCK","6","UNAVAILABLE","There are no good clocks in the system. Remain in HOLDOVER mode","The clock selection algorithm has failed to select any clock as the TDM primary clock.","LOG_STD_NO_ACTION."
"TRUNK_DFC","3","UNAVAILABLE","Could not download trunk firmware in slot %d","Cannot download trunk firmware","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRUNK_DFC","3","UNAVAILABLE","Failed to create context for dsx3 controller in %d/%d","This message indicates internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRUNK_DFC","3","UNAVAILABLE","Failed to create controller for %d/%d","This message indicates internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRUNK_DFC","3","UNAVAILABLE","Failed to create trunk slot instance for slot %d","This message indicates internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRUNK_DFC","3","UNAVAILABLE","Reset failed for Trunk DFC ROM in slot %d","Cannot take Trunk DFC out of reset","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRUNK_DFC","3","UNAVAILABLE","Trunk DFC ROM in slot %d failed: %s","Trunk DFC ROM failed to boot properly","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRUNK_DFC","3","UNAVAILABLE","Trunk DFC firmware in slot %d is not ready","Trunk DFC firmware failed to start","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRUNK_DFC","3","UNAVAILABLE","Trunk DFC in slot %d: SDRAM failed [0x%x..0x%x]","Trunk DFC SDRAM test failed indicating bad memory location","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TSP","3","UNAVAILABLE","%s","Internal Finite State Machine Error.","Contact your technical support representative, include the full text of the error message."
"TSP","3","UNAVAILABLE","no free event structure available from %s for DSP message","There were no event structures remaining in the system pools to alert the router of a voice or signaling event.","Check that the voice port for which the event was reported is still operational. If not, clear the voice port."
"TSP","3","UNAVAILABLE","voice port %s: call connection id [0x%x 0x%x 0x%x 0x%x]","There was a capabilities mismatch between the two call legs. capabilities are negotiated between call legs for CODEC, VAD and FAX rate.","Check that the dial peer configuration is appropriate for the interface in question. Also check that and configuration on the interface is correct."
"TSP","3","UNAVAILABLE","voice port %s: status=0x%x message=0x%x","The DSP reported a fatal error. All calls on the DSP were dropped and a DSP reload was attempted.","Verify that the DSP reloaded properly by attempting to place a call on the affected voice port. Contact your technical support representative, include the full text of the error message."
"TSP","5","UNAVAILABLE","%s at slot %d, unit %d, channel %d","A PRI signalling channel is added/deleted to TSP's inventory of signalling channels.","This is a notification message only. No action is required."
"TTY","3","UNAVAILABLE","Cannot create %s process","Failed creating the process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TTY","3","UNAVAILABLE","TTY%t: Modem auto-configuration failed","Modem auto-configuration failed either because the modem rejected the configuration string or because of a timeout. An attempt should be made to apply the configuration string mannually.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TTYDRIVER","2","UNAVAILABLE","Unable to allocate %d I/O buffers","A buffer memory shortage existed at the time that the configuration command was issued. This condition is rare and, under normal conditions, temporary.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TTYDRIVER","2","UNAVAILABLE","Unable to allocate break block from I/O mem","The router does not have enough I/O memory for buffers.","Consider adding more shared memory. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TTYDRIVER","3","UNAVAILABLE","No particles available to set up for output on tty %s","A software error occurred resulting in an unexpected exhaustion of the pool of data buffers used by the modem drivers.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TTYDRIVER","3","UNAVAILABLE","Non-zero outcount but no transmit particle on tty %s","A software error occurred and left a software structure in an unexpected state.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TTYDRIVER","3","UNAVAILABLE","RTS is incorrectly deasserted for tty %s; reasserting now","A software error occurred resulting in an invalid state for the RTS modem signal","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TTYDRIVER","3","UNAVAILABLE","Unknown encapsulation on interface %s","A software error occurred resulting in an unknown encapsulation type on the interface specified by the error message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TTYDRIVER","3","UNAVAILABLE","Unknown port type (%d)","A software error occurred due to an unrecognised port type","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TRIFECTA","6","X86_FPGAVER_MISMATCH","Module [dec]: [chars]","Trifecta X86 FPGA version mismatch.","No action is required."
"TRIFECTA","6","X86ONLINE","Trifecta X86 in slot [dec] is online.","Trifecta X86 has finished booting up and is online.","No action is required."
"TRIFECTA","6","X86_RESTART_REASON","Module [dec]: [chars]","Trifecta X86 restart reason.","No action is required."
"TTFIB_NP_CLIENT","3","ERROR","[chars] [chars] [chars]","Failed to set or clear port mode flags because the NP returned a failure condition.","Reload the Cisco IOS image on the affected card or platform. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TTFIB_NP_CLIENT","3","INFO","[chars]","TTFIB NP client failed to initialize properly, which results in improper operation of the any transport over MPLS (AToM) feature.","Reload the Cisco IOS image on the affected card or platform. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TTFIB_NP_CLIENT","3","NOMEM","[chars]","TTFIB NP client failed to initialize properly, which results in improper operation of the any transport over MPLS (AToM) feature.","This message may indicate that more memory must be installed on the affected card or platform in order to service all the features and related entities enabled via the configuration. Reload the Cisco IOS image on the affected card or platform. If the error persists, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TTFIB_NP_CLIENT","4","HDLC","[chars]","Improper usage of SIP-400 for the HDLC over MPLS (HDLCoMPLS) feature.","This is an informational message only. No action is required."
"TTFIB_NP_CLIENT","4","PPP","[chars]","Improper usage of SIP-400 for the PPP over MPLS (PPPoMPLS) feature.","This is an informational message only. No action is required."
"TTFIB_NP_CLIENT","4","VPLS","[chars]","Improper usage of SIP-400 for the Virtual Private LAN Service (VPLS) feature.","This is an informational message only. No action is required."
"TTFIB_NP_CLIENT","4","WARN","[chars] [dec] [chars]","A TTFIB entry could not be added because the entry passed is invalid.","Reload the Cisco IOS image on the affected card or platform. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TUN","3","API_ARGS","unexpected arguments: [chars], [chars]","A public tunnel component API was called with arguments outside the expected boundaries.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TUN","3","ENDPOINT_ERROR","[chars] [chars]","An internal software error occurred during manipulating the tunnel endpoint database.","No action is required."
"TUN","3","ENDPOINT_STORE","Operation [chars] failed for [chars]","Manipulation of the tunnel endpoint store has failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TUN","3","ILLEGAL_ARGS","Illegal arguments - [chars]","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TUN","3","MTUCONFIGEXCEEDSL2MTU_IPV4","[chars] IPv4 MTU configured [int] exceeds tunnel maximum MTU [int]","An IPv4 MTU value is configured on the tunnel interface and this value exceeds the tunnel's maximum MTU. This message is typically observed when the tunnel header size changes or when the MTU of the underlying exit interface changes. As a result of either, the tunnel maximum MTU can change. This message can also be observed when using an IPv6 tunnel to carry IPv4 since IPv4 MTU config in this case allows for a value to be configured that is greater than the tunnel's maximum MTU. As a result of any of these conditions, packets may be dropped.","If a specific IPv4 MTU value is not required, it is recommended that you leave the value at the default by typing no ip mtu on the tunnel interface. If a specific value is required, it is recommended that you check the interface MTU value from the show interface tunnel command and adjust ip mtu on the tunnel interface to be lower than or equal to this."
"TUN","3","MTUCONFIGEXCEEDSL2MTU_IPV6","[chars] IPv6 MTU configured [int] exceeds tunnel maximum MTU [int]","An IPv6 MTU value is configured on the tunnel interface and this value exceeds the tunnel's maximum MTU. This message is typically observed when the tunnel header size changes or when the MTU of the underlying exit interface changes. As a result of either, the tunnel maximum MTU can change. This message can also be observed when using an IPv6 tunnel to carry IPv6 since IPv6 MTU config in this case allows for a value to be configured that is greater than the tunnel's maximum MTU. As a result of any of these conditions, packets may be dropped.","If a specific IPv6 MTU value is not required, it is recommended that you leave the value at the default by typing no ipv6 mtu on the tunnel interface. If a specific value is required, it is recommended that you check the interface MTU value from the show interface tunnel command and adjust ipv6 mtu on the tunnel interface to be lower than or equal to this."
"TUN","4","MTUCONFIGEXCEEDSTRMTU_IPV4","[chars] IPv4 MTU configured [int] exceeds tunnel transport MTU [int]","An IPv4 MTU value has been configured on the tunnel interface and this value exceeds the tunnel's transport (default) MTU. As a result, fragmentation of the transport packet may occur before this goes out of the underlying exit interface.","If a specific IPv4 MTU value is not required, it is recommended that you leave the value at the default by typing no ip mtu on the tunnel interface. If a specific value is required, it is recommended that you check the tunnel transport MTU value from the show interface tunnel command and adjust ip mtu on the tunnel interface to be lower than or equal to this."
"TUN","4","MTUCONFIGEXCEEDSTRMTU_IPV6","[chars] IPv6 MTU configured [int] exceeds tunnel transport MTU [int]","An IPv6 MTU value has been configured on the tunnel interface and this value exceeds the tunnel's transport (default) MTU. As a result, fragmentation of the transport packet may occur before this goes out of the underlying exit interface.","If a specific IPv6 MTU value is not required, it is recommended that you leave the value at the default by typing no ipv6 mtu on the tunnel interface. If a specific value is required, it is recommended that you check the tunnel transport MTU value from the show interface tunnel command and adjust ipv6 mtu on the tunnel interface to be lower than or equal to this."
"TUN","4","MTUCONFIGLESSTHAN_MINIPV4MTU","[chars] IPv4 MTU [int] is lesser than the minimum IP MTU [int], fragmentation may occur","The IPv4 MTU value calculated on the tunnel interface is less than the minimum IP MTU. The MTU of the underlying exit interface of the tunnel is too small. As a result, fragmentation of the transport packet may occur before this goes out of the underlying exit interface.","If a specific MTU value is not required for the exit interface, it is recommended that you leave the value at the default by typing no mtu on the exit interface. If a specific value is required, it is recommended that you check the MTU value from the show interface command for the exit interface and adjust mtu on the tunnel exit to be higher than this."
"TUN","4","UDLR_IDB_ERROR","UDLR [chars] - [chars]","An error was encountered on a unidirectional link routing (UDLR) interface.","No action is required."
"TUN","5","HW_IF_INDEX_ILLEGAL","Attempt to create tunnel interface for [chars] with illegal index: [dec]","The creation of a tunnel interface failed due to an invalid index.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TUN","5","INIT_ERROR","A critical error [chars]occurred during initialization","The creation of a tunnel subsystem failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TUN","5","RECURDOWN_SRC","[chars] linestate down, recursive source interface, next output [chars]","While the tunnel line state was being evaluated, a source interface was revisited.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TUN","5","TUN_DB_IF","Operation on tunnel interface table failed for [chars] - [chars]","A manipulation of the tunnel interface table failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TUN","5","TUN_HWIDB_DELETE","Failed to delete hwidb for Tunnel [dec] index [dec]","The deletion of a tunnel interface failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TUN","5","TUN_HWIDB_LIST_DELETE","Failed to delete [chars] from tunnel hwidb list","The deletion of a tunnel from the hardware IDB list failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TUN","5","TUN_HWIDB_LIST_INSERT","Failed to add [chars] to tunnel hwidb list","The insertion of a tunnel into the hardware IDB list failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TUN","5","TUN_HWIDB_RECYCLE","Failed to recycle hwidb for Tunnel [dec] index [dec]","The recycling of a tunnel interface failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TUN","5","TUN_LIST_CREATE","Failed to create tunnel list [chars]","The creation of a tunnel list failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TUN","5","TUN_SWIDB_DELETE","Failed to delete swidb for Tunnel [dec] index [dec]","The deletion of a tunnel interface failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TUN","5","TUN_SWIDB_RECYCLE","Failed to recycle swidb for Tunnel [dec] index [dec]","The recycling of a tunnel interface failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TUN","5","TUN_TABLE","Operation [chars] on tunnel table failed for [chars] - [chars]","The manipulation of the tunnel table failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TUN","5","TUN_UNIT_LIST_DELETE","Failed to delete entry unit [dec] to tunnel unit list","A deletion from the tunnel unit failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TUN","5","TUN_UNIT_LIST_INSERT","Failed to add entry unit [dec] to tunnel unit list","The insertion of the tunnel unit failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"TUNSS","6","PROTECTION_BAD_TUN_MODE","Tunnel mode [chars] not supported by tunnel protection. Protection removed.","The chosen tunnel mode is not supported by tunnel protection interfaces. Protection has been turned off and removed.","Unless protection is desired on this interface, no action is required. If protection is desired, a crypto-map must be used instead."
"TWOBIT","3","UNAVAILABLE","%s: Error encountered (fsm rc %d)","A 2bt protocol driver finite state machine error detected. This is not a fatal error.","This error means a 2bt protocol software error. However, this is not fatal since a retry mechanism ensures correct behaviour again. If this error message is repeatedly seen, copy the error message exactly as it appears on the console or in the system log, enter the show diag command to gather additional data, and contact your Cisco technical support representative with the gathered information"
"TWOBIT","3","UNAVAILABLE","%s: Invalid fsm state (%s) (state %d)","A 2bt protocol driver finite state machine error detected. This is not a fatal error.","This means there has been a glitch in the 2bt protocol negotitaion. However, this is not fatal since a retry mechanism ensures correct behaviour again. If this error message is repeatedly seen, copy the error message exactly as it appears on the console or in the system log, enter the show diag command to gather additional data, and contact your Cisco technical support representative with the gathered information"
"TWOBIT","3","UNAVAILABLE","Failed to allocate hardware timer","The 2bt protocol driver finite state machine was unable to allocate a hardware timer that it requires for operation.","This means there has been a glitch in the 2bt protocol negotitaion. This error will cause the 2 bt protocol to malfunction and cause higher layer applications that use this communication mechanism to fail. If this error message is seen, copy the error message exactly as it appears on the console or in the system log, enter the show diag command to gather additional data, and contact your Cisco technical support representative with the gathered information."
"TXCONN","3","UNAVAILABLE","Bad Transaction ID, flushing out request for client %i connected server %s, killing connection.","Bad input stream.","This is an informational message. LOG_STD_NO_ACTION"
"TXCONN","3","UNAVAILABLE","Bad license key configured for Transaction Connection.","The license key configured with the txconn license configuration command is not valid.","Check that the license key was entered correctly in the txconn license configuration command. Refer to the txconn feature documentation for information on how to obtain a valid license key."
"TXCONN","3","UNAVAILABLE","Bad remote LU '%s' configured for server %s","The remote LU configured for the txconn server is incorrect.","Contact your SNA network administrator to determine the correct name of the remote LU for DB2 on the remote database server. Be sure to check that the SNA network name is correct as well as the LU name."
"TXCONN","3","UNAVAILABLE","Exception %s from transaction %s to %s from client %i","An unexpected transaction error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. If possible, also provide the output of the debug txconn data command, and an SNA line trace between the router and the remote database server, for the period during which this message appeared."
"TXCONN","3","UNAVAILABLE","Out of resource, cannot create transaction for client %i connected server %s, killing connection.","The router is out of memory.","This is an informational message. LOG_STD_NO_ACTION"
"TXCONN","3","UNAVAILABLE","Unexpected client data, flushing out the request for client %i connected server %s.","Bad input stream.","This is an informational message. LOG_STD_NO_ACTION"
"TXCONN","3","UNAVAILABLE","Unknown mode '%s' configured for server %s","The mode configured for the txconn server was rejected by the remote database server.","Contact your SNA network administrator to determine the correct name of the mode to use to connect to DB2 on the remote database server."
"TXCONN","5","UNAVAILABLE","APPC security failed, client %i using userid '%s' for server %s","The userid and/or password passed in by the client were rejected by the remote database server.","This is an informational message only. LOG_STD_NO_ACTION"
"TXCONN","5","UNAVAILABLE","CICS server %s has become unavailable. Recovery is in progress.","A CICS server for a configured destination has become unavailable. All client connections to this server will be rejected until it becomes available again.","This is an informational message only. LOG_STD_NO_ACTION"
"TXCONN","5","UNAVAILABLE","CICS server %s is now available.","A CICS server that was previously unavailable has become available. All client connections to this server will now be accepted.","This is an informational message only. LOG_STD_NO_ACTION"
"TXCONN","5","UNAVAILABLE","Client %i connected to server %s has timed out after %TE.","The client was idle for too long, and the idle timeout configured for the txconn server expired.","This is an informational message only. LOG_STD_NO_ACTION"
"TXCONN","5","UNAVAILABLE","Transaction %x of Client %i connected to server %s has timed out after %TE.","The transaction was idle for too long, and the idle timeout configured for the txconn server expired.","This is an informational message only. LOG_STD_NO_ACTION"
"UAM","3","IMPACT_FAMILY","UAM is unable to get the impact of the upgrade on '%s' linecards family (SR is '%s')","The Upgrade Analysis Module (UAM) is unable to determine the impact of the current upgrade for the line cards belonging to the specified family. An upgrade operation will probably result in the resetting of all line cards in that family.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UAM","3","INVALID_CONTEXT","Trying to stop the upgrade, but there is no upgrade currently","An application is trying to stop an upgrade cycle, but there is no upgrade in progress.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UAM","3","INVALID_WB","Trying to set an invalid watched boolean","During runtime, the UAM is trying to release a process using an invalid internal data structure. The command line interface will probably be blocked or the standby supervisor will be unable to boot.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UBR7200","0","UNAVAILABLE","%s measured at %s is too high: shutdown temperature %s","Current temperature exceeds the max shutdown temperature","Determine cause of the high temperature and correct if possible."
"UBR7200","0","UNAVAILABLE","%s measured at %s is too high: shutdown voltage %s","Current voltage exceeds the max shutdown voltage","Determine cause of the high voltage and correct if possible."
"UBR7200","0","UNAVAILABLE","%s measured at %s is too low: shutdown voltage %s","Current voltage exceeds the min shutdown voltage","Determine cause of the low voltage and correct if possible."
"UBR7200","0","UNAVAILABLE","CMTS(%d/%d), Init failed, CSR%d=0x%04x.","Most likely Hardware failure","Replace defective Line Card"
"UBR7200","0","UNAVAILABLE","uBR requires CPU card type NPE150 or higher","NPE100 is not supported in uBR","Upgrade CPU card to NPE150 or higher"
"UBR7200","1","UNAVAILABLE","Only found %d interfaces on bay %d, shutting down bay","Most likely system or hardware failure","Replace Line Card"
"UBR7200","1","UNAVAILABLE","Only found %d interfaces on bay %d, shutting down bay","Most likely system or hardware failure","Replace Line Card"
"UBR7200","3","UNAVAILABLE","%s","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UBR7200","3","UNAVAILABLE","AWACS Slot %d is dead","Daughter board DSP hungs","Reload image, if still fail, replace defective daughter board"
"UBR7200","3","UNAVAILABLE","CMTS(%d/%d), Buffer ownership error, pak=0x%x.","Most likely hardware failure","Replace defective board"
"UBR7200","3","UNAVAILABLE","Can not remove Burst Profile. Burst Profile is in use","Current Modulation profiles defined currently use this burst profile","Remove the modulation profile(s) that use this burst profile, then reissue the command."
"UBR7200","3","UNAVAILABLE","Can't allocate MAC address for interface %u/%u","Your system is out of available MAC addresses.","Contact technical support."
"UBR7200","3","UNAVAILABLE","Cannot send maps as current_map ptr is NULL, ds-%x,current_map-%x: %s","This is an internal error, or may indicate a memory problem.","Check your available memory. If necessary, add more memory to the system."
"UBR7200","3","UNAVAILABLE","Could not start Spectrum Management process","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UBR7200","3","UNAVAILABLE","DSP FLASH memory failed","Daughter board hardware failure","Replace defective daughter board"
"UBR7200","3","UNAVAILABLE","DSP SRAM failed","Daughter board hardware failure","Replace defective daughter board"
"UBR7200","3","UNAVAILABLE","DSP SRAM semaphore failed","Daughter board hardware failure","Replace defective daughter board"
"UBR7200","3","UNAVAILABLE","DSP failed for unknown reason(0x%x)","Daughter board hardware failure","Replace defective daughter board"
"UBR7200","3","UNAVAILABLE","DSP id read 0x%x,expect 0x%x","Daughter board hardware failure","Replace defective daughter board"
"UBR7200","3","UNAVAILABLE","DSP side dual-port SRAM failed","Daughter board hardware failure","Replace defective daughter board"
"UBR7200","3","UNAVAILABLE","Device reported %#x","Most likely hardware failure","Replace defective hardware"
"UBR7200","3","UNAVAILABLE","Exceeds %d %s","The total bandwidth of fast and medium bandwidth port adapters exceed the rated capacity of this system.","Refer to the configuration guidelines for the maximum allowed high and medium bandwidth port adapters for the system."
"UBR7200","3","UNAVAILABLE","Failed downloading.","Failed DSP downloading","Reload image, if still fail replace defective daughter board"
"UBR7200","3","UNAVAILABLE","Failed end downloading.","Failed last step of DSP downloading","Reload image, if still fail replace defective daughter board"
"UBR7200","3","UNAVAILABLE","Interface %s Port U%d invalid, highest port number is U%d","Upstream port number must be valid.","Redo command with valid upstream port number."
"UBR7200","3","UNAVAILABLE","Interface %s, ARP reply from invalid source. Expected SID=%d, Actual SID=%d","There might be a spoofing attempt going on","Look for possible spoofing attempt"
"UBR7200","3","UNAVAILABLE","Interface %s, ARP request from invalid source. IP=%i, MAC=%e, Expected SID=%d, Actual SID=%d","There might be a spoofing attempt going on","Look for possible spoofing attempt"
"UBR7200","3","UNAVAILABLE","Interface %s, Failed to send intercept packet to server %i:%d","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UBR7200","3","UNAVAILABLE","Interface %s, IP address %i from MAC %e is already in use. SID = %d","There might be a spoofing attempt going on.","Look for possible spoofing attempt"
"UBR7200","3","UNAVAILABLE","Interface %s, IP packet from invalid source. IP=%i, MAC=%e, Expected Interface=%s SID=%d, Actual Interface=%s SID=%d","There might be a spoofing attempt going on.","Look for possible spoofing attempt"
"UBR7200","3","UNAVAILABLE","Interface %s, IP packet from invalid source. IP=%i, MAC=%e, Expected SID=%d, Actual SID=%d","There might be a spoofing attempt going on.","Look for possible spoofing attempt"
"UBR7200","3","UNAVAILABLE","Invalid Channel ID(%s): chid=0x%02x, cmd=0x%02x, regaddr=0x%02x","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UBR7200","3","UNAVAILABLE","Maximum number of SIDS have been allocated for interface %s","The Maxmium number of Cable Modems are on line","Assign Cable Modem to another Line Card"
"UBR7200","3","UNAVAILABLE","Number of slots in chassis is undefined.","Data stored in midplane is bad or incomplete.","Contact technical support to update your system."
"UBR7200","3","UNAVAILABLE","Plx9050 id read 0x%x,expect 0x%x","Daughter board hardware failure","Replace defective daughter board"
"UBR7200","3","UNAVAILABLE","Plx9080 id read 0x%x,expect 0x%x","Daughter board hardware failure","Replace defective daughter board"
"UBR7200","3","UNAVAILABLE","SPI BUS READ 0x%02x BYTES SHORT(%s): spistat=0x%02x, chid=0x%02x, cmd=0x%02x, regaddr=0x%02x","Read error on PHY chip serial communications bus.","Line card is defective, replace it."
"UBR7200","3","UNAVAILABLE","SPI PENDING NO READ DATA(%s): spistat=0x%02x, chid=0x%02x, cmd=0x%02x, regaddr=0x%02x","Read error on PHY chip serial communications bus.","Line card is defective, replace it."
"UBR7200","3","UNAVAILABLE","SPI PENDING READ ERROR(%s): spistat=0x%02x, chid=0x%02x, cmd=0x%02x, regaddr=0x%02x","Read error on PHY chip serial communications bus.","Line card is defective, replace it."
"UBR7200","3","UNAVAILABLE","SPI PENDING WRITE ERROR(%s): spistat=0x%02x, chid=0x%02x, cmd=0x%02x, regaddr=0x%02x","Write error on PHY chip serial communications bus.","Line card is defective, replace it."
"UBR7200","3","UNAVAILABLE","Switching to backup dsp image failed","Daughter board hardware failure","Replace defective daughter board"
"UBR7200","3","UNAVAILABLE","Unknown chassis model.","Data stored in midplane is bad or incomplete.","Contact technical support to update your system."
"UBR7200","3","UNAVAILABLE","XILINX not up, reset reg is 0x%x","Daughter board hardware failure","Replace defective daughter board"
"UBR7200","3","UNAVAILABLE","failed init download.","Failed initiating DSP downloading","Reload image, if still fail replace defective daughter board"
"UBR7200","4","UNAVAILABLE","Bad timing offset %ld detected for cable modem %e.","The cable modem is not using the correct starting offset during initial ranging. This causes a zero, negative timing offset to be recorded by the CMTS for this modem. The CMTS internal algorithm(s) that rely on the timing offset parameter, will exclude such modems from any analysis. Such bad modems may or may-not be able to function depending on their physical location on the cable plant","Locate the cable modem based on MAC address and report initial timing offset problem to the CM vendor"
"UBR7200","4","UNAVAILABLE","Cable modem %e is online on both interface %s and interface %s.","The cable modem has been detected on two interfaces.","Check for cable modems with duplicate MAC addresses."
"UBR7200","4","UNAVAILABLE","Corrupt or missing MAC address cookie using random base %e","Data stored in midplane is bad.","Contact technical support to update your system."
"UBR7200","4","UNAVAILABLE","Hardware Fault","Hardware fault in Clockcard","Replace clock card"
"UBR7200","4","UNAVAILABLE","Invalid CPU ID, assuming revision 1","CPU Revision ID is unreadable.","Update CPU board."
"UBR7200","4","UNAVAILABLE","Midplane data version mismatch.","Data stored in midplane is out of date and needs update.","Contact technical support to update your system."
"UBR7200","4","UNAVAILABLE","Old version NPE-175/225 with Rev = 0x%02x system controller. Contact upgrades-info@cisco.com for replacement","NPE board has been recalled due to an errata in the system controller chip.","Replace NPE-175/225 Board"
"UBR7200","4","UNAVAILABLE","SID cannot be resolved from the leasequery reply for IP %i","Relay-agent option might not be configured.","Make sure relay-agent option is configured. Also make sure save-relay-agent-data is enabled on CNR."
"UBR7200","4","UNAVAILABLE","Unknown MAC address block size.","Data stored in midplane is bad or incomplete.","Contact technical support to update your system."
"UBR7200","5","UNAVAILABLE","Authorization failed for Cable Modem %e on interface %s","The registration of this modem failed due to an invalid MIC string","Make sure the shared secret in the configuration file matches the shared secret configured in the ubr7200."
"UBR7200","5","UNAVAILABLE","Bad timer expiry in downstream traffic shaper process, Timer %x Error Message    %UBR7200-5-UNAVAILABLE: CMTS deleted BPI unauthorized Cable Modem %e","Unauthorized cable modem deleted to enforce CM go through BPI authorization.","Check modem interface configuration for privacy mandatory, or errors in tftp configuration file."
"UBR7200","5","UNAVAILABLE","CMTS deleted unregistered Cable Modem %e","Unregistered cable modem deleted to avoid unaccounted bandwidth usage.","Check modem i/f config for registration bypass, or errors in tftp config file."
"UBR7200","5","UNAVAILABLE","Handshake DSP is successful after %d ms delay","DSP is up and running","LOG_STD_NO_ACTION"
"UBR7200","5","UNAVAILABLE","Interface %s Current total reservation of %d bps on Port U%d, exceeds its maximum configured reservation limit of %d bps.","The currently reserved capacity on the upstream channel already exceeds the virtual reservation capacity of that upstream channel (based on configured subscription level limit).","Need to load balance modems requesting reserved upstream rate on some other upstream channel, or increase the subscription level limit on current upstream channel at increasing risk of not being able to guarantee the individual reserved rates for modems if this upstream channel is already oversubscribed beyond raw capacity"
"UBR7200","5","UNAVAILABLE","Interface %s Port U%d, changed state to %s","The upstream port was brought up or down.","LOG_STD_NO_ACTION"
"UBR7200","5","UNAVAILABLE","Interface %s Port U%d, continuous frequency hop ended at %u.%03u MHz","At least one modem came back online. This message logs the abort of continuous frequency hop.","LOG_STD_NO_ACTION"
"UBR7200","5","UNAVAILABLE","Interface %s Port U%d, continuous frequency hop started","All modems just went offline. This message logs the start of continuous frequency hop.","LOG_STD_NO_ACTION"
"UBR7200","5","UNAVAILABLE","Interface %s Port U%d, frequency changed to %u.%03u MHz","The upstream channel frequency was changed.","LOG_STD_NO_ACTION"
"UBR7200","5","UNAVAILABLE","Interface %s Port U%d, input power level changed to %d dBmV","The upstream channel input power level was changed.","LOG_STD_NO_ACTION"
"UBR7200","5","UNAVAILABLE","Interface %s Port U%d, input power level fixed at %d dBmV","Setting the upstream frequency to a fixed value caused theupstream input power level to assume a fixed value.","LOG_STD_NO_ACTION"
"UBR7200","5","UNAVAILABLE","Invalid DOCSIS Message received from a Cable Modem for interface %s","This is a DOCSIS Message, but not an appropriate message for the uBR.","Locate Cable Modem sending this message and replace with DOCSIS compliant modem."
"UBR7200","5","UNAVAILABLE","New host with IP address %i and MAC %e on SID %d is ignored.","Number of hosts on the SID has been exceeded.","Locate the Cable Modem in question"
"UBR7200","5","UNAVAILABLE","Not implemented DOCSIS MESSAGE received from a Cable Modem for interface %s","This uBR does not support this type of message.The system may be connected to a non-compliant modem.","This message is informational only. To be sure there is no problem,you may contact technical support."
"UBR7200","5","UNAVAILABLE","Recovering and switching back to regular dsp image succeeded","DSP recover operation using backup image succeeded","LOG_STD_NO_ACTION"
"UBR7200","5","UNAVAILABLE","Registration failed for Cable Modem %e on interface %s%s: %s","The registration of this modem failed due to an invalid or unsupported Class of Service setting.","Make sure the Class of Service fields in the configuration file are set correctly."
"UBR7200","5","UNAVAILABLE","Switching to backup dsp image succeeded","Switching to backup dsp image succeeded","LOG_STD_NO_ACTION"
"UBR7200","5","UNAVAILABLE","Time scheduled event, spectrum group %u, %s","A time scheduled reconfiguration event occurred on an interface.","LOG_STD_NO_ACTION"
"UBR7200","5","UNAVAILABLE","Trying to switch to backup dsp image","Trying to recover DSP using backup image","LOG_STD_NO_ACTION"
"UBR7200","5","UNAVAILABLE","Unable to create downstream traffic shaping queues Error Message    %UBR7200-5-UNAVAILABLE: Unable to fork downstream shaper process Error Message    %UBR7200-5-UNAVAILABLE: Upstream Channel Change not valid for interface %s","The software does not support this command for this interface","Please use this command on a multiple upstream Line card."
"UBR7200","6","UNAVAILABLE","%s burst's preamble length in modulation profile %d is adjusted to the operable value.","The preamble length in the burst profile has adjusted to the valid value.","Informational only"
"UBR7200","6","UNAVAILABLE","Cable Clock primary reference is midplane TDM clock","Clockcard primary reference is from midplane TDM clock","Informational only"
"UBR7200","6","UNAVAILABLE","Cable clock %s reference Loss of Signal","The clock reference was lost","Check reference source"
"UBR7200","6","UNAVAILABLE","Cable clock %s reference active","The clock reference became active","Informational only"
"UBR7200","6","UNAVAILABLE","Cable clock in Freerun mode","Clockcard is in free run mode","Informational only"
"UBR7200","6","UNAVAILABLE","Cable clock in Holdover mode","Clockcard switched to holdover mode","Check reference source"
"UBR7200","6","UNAVAILABLE","Cable clock locked to %s reference","Clockcard locked onto clock source","Informational only"
"UBR7200","6","UNAVAILABLE","Cable modem %e has been moved from interface %s to interface %s.","The cable modem has been detected ranging on a new interface.","Informational only"
"UBR7200","6","UNAVAILABLE","Current DSP version : %d, DSP flash version : %d","The current code version and the version DSP booted up with","LOG_STD_NO_ACTION"
"UBR7200","6","UNAVAILABLE","Downloading dsp code completed","Downloading dsp code completed","LOG_STD_NO_ACTION"
"UBR7200","6","UNAVAILABLE","Downloading dsp code initiated","Downloading dsp code started","LOG_STD_NO_ACTION"
"UBR7200","6","UNAVAILABLE","Midplane TDM clock reference defaults to Clockcard","Clockcard primary reference is from midplane TDM clock","Informational only"
"UCODE","3","UNAVAILABLE","%s is %s ucode not %s, microcode/hardware mismatch","The specified microcode file is for a different interface processor than specified in the configuration. The user has made a configuration error. The onboard ROM microcode will be loaded.","Reenter your microcode configuration command after confirming the interface type and reload the microcode."
"UCODE","3","UNAVAILABLE","Bad checksum in %s, found 0x%x expected 0x%x","The microcode file is corrupted in some way; the checksum computed after reading the file from Flash does not match the one in the file. The file will not be downloaded, and the onboard ROM microcode will be used instead.","Reload the microcode. If the message recurs, call your technical support representative for assistance."
"UCODE","3","UNAVAILABLE","File %s at length %d is too long for buffer (size %d)","The file is too large for the buffer. The onboard ROM microcode will be loaded.","If the error message recurs after the onboard ROM microcode is loaded, call your technical support representative for assistance."
"UCODE","3","UNAVAILABLE","Inappropriate version %u.%u for %s","An attempt was made to load an inappropriate version of microcode.","Copy the message exactly as it appears, and report it your technical support representative."
"UCODE","3","UNAVAILABLE","Invalid IPC request (%d) received from (%x)","The InterProcess Communication (IPC) service used to download microcode to certain interface processors has received an invalid message.","Verify that the proper revisions of code are selected."
"UCODE","3","UNAVAILABLE","Invalid Ucode source type (%d)","Microcode source type as specified is not supported on the given platform","Verify that the proper revisions of code are selected."
"UCODE","3","UNAVAILABLE","Invalid attempt to load ROM ucode in slot %d","Some interface processors cannot load microcode from ROM.","Remove the erroneous configuration statement."
"UCODE","3","UNAVAILABLE","Ucode file %s not found, system ucode loaded in slot %d","The file specified by the configuration was not found in Flash. The onboard ROM microcode will be loaded so the interface can remain operational.","Use show flash to determine if the file is located in Flash. If the file is there, attempt to reload the microcode. If the message recurs, call your technical support representative for assistance."
"UCODE","3","UNAVAILABLE","Ucode file %s requires %s version %d.x hardware","A mismatch was detected during an attempt to load a microcode file into an interface processor. The hardware requires a different version than the one specified.","Use the required microcode version."
"UCODE","3","UNAVAILABLE","Ucode header corrupted in %s, found 0x%x expected 0x%x","The microcode file is corrupted in some way; the checksum computed after reading the file from Flash does not match the one in the file. The file will not be downloaded, and the onboard ROM microcode will be used instead.","Reload the microcode. If the message recurs, call your technical support representative for assistance."
"UCODE","3","UNAVAILABLE","Unable to allocate memory during microcode reload","An attempt at memory allocation failed while downloading microcode to Interface processor.","Copy the message exactly as it appears, and report it your technical support representative."
"UCODE","3","UNAVAILABLE","Unable to allocate memory for ucode buffer","A buffer is required to decompress microcode before loading it into an interface processor. This buffer could not be allocated for some reason.","Copy the message exactly as it appears, and report it your technical support representative."
"UCODE","3","UNAVAILABLE","Unable to download ucode from %s in slot %d, trying %s ucode","For some reason, the microcode file specified by the configuration is not suitable for downloading, or another error occurred. The onboard ROM microcode will be loaded so the interface can remain operational.","Attempt to reload the microcode. If the message recurs, call your technical support representative for assistance."
"UCODE","3","UNAVAILABLE","Unable to initialize IPC %s services","The InterProcess Communication (IPC) service used to download microcode to certain interface processors has failed to initialize.","Certain Interface Processors will not load properly. The router must be reloaded to clear the problem."
"UCODE","3","UNAVAILABLE","Unable to obtain IPC resources","The InterProcess Communication (IPC) service used to download microcode to certain interface processors has failed to obtain a buffer.","Certain interface processors will not load properly. Try the reload command again. If this message recurs, call your technical support representative for assistance."
"UCODE","3","UNAVAILABLE","Unable to read ucode file %s from flash","For some reason, the microcode file was not read from Flash. Flash might be locked by another process or otherwise unavailable.","Use the show flash command to determine whether Flash is in use and issue another microcode reload when Flash is free. If the message recurs, call your technical support representative for assistance."
"UCODE","5","UNAVAILABLE","FDDI unit %d has obsolete microcode: please upgrade it","This message occurs when an FDDI interface processor is found running microcode that does not support microcode CMT, which is required for all software releases from 10.2 on.","Upgrade the microcode on the interface processor."
"UDLD","3","UNAVAILABLE","UDLD error handling %s interface: %s","A softare error occurred in UDLD processing associated with a specific interface.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UBL","2","SLAVE_FAIL","Could not download image due to - [chars].","The standby supervisor engine could not carry out its task of downloading an image from the active supervisor engine due to the reason mentioned in the error message. This could be due to an internal error or due to an old image running on the active supervisor engine that does not support UBL. Prior error messages might provide more information about the actual problem.","Ensure the conditions mentioned in the message are met. If preceding error messages in the log indicate that this is an internal error, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UDLD","3","UDLD_IDB_ERROR","UDLD error handling %s interface: %s","A softare error occurred in UDLD processing associated with a specific interface.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"UDLD","3","UDLD_INTERNAL_ERROR","UDLD internal error: %s","A softare sanity check failed in the course of UDLD processing.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"UDLD","3","UDLD_INTERNAL_IF_ERROR","UDLD internal error, interface %s: %s","A softare sanity check failed in the course of UDLD processing.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"UDLD","3","UDLD_NOKADIS","UDLD unable to create the kadis timer, status [dec]","A failure occurred during creation of the kadis timer from UDLD pseudo preemptive process.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"UDLD","3","UDLD_NOPREEMP","UDLD unable to create pseudo preemptive process","A failure occurred during creation of the UDLD pseudo preemptive process.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"UDLD","4","UDLD_PORT_DISABLED","UDLD disabled interface %s, %s detected","An interface was disabled because UDLD protocol detected the cause indicated on the interface indicated. Cause is likely due to bad interface hardware or cable misconfiguration. User should investigate.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"UDLD","4","UDLD_PORT_FAILURE","UDLD failure reported per user request, interface [chars], [chars] detected,","An interface failure was reported because UDLD protocol detected the cause indicated on the interface. Cause is likely due to bad interface hardware or cable misconfiguration. Interface not err-disabled as user choose to see error-report. User should investigate and take action.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"UDLD","6","UDLD_PORT_LINKDOWN","Fast UDLD cache times out for intf [chars], moves port to linkdown state","Fast UDLD cache entry for the reported interface times out. This could be due to either remote side port shut, LC OIR, or real link failure. UDLD moved the port to linkdown state for all cases. If this is not caused by a link failure, UDLD should receive a PM linkdown notification within the next 4 seconds. If UDLD does not receive any notification, then it will consider this a link failure and will err-disable the port.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"UDLD","6","UDLD_PORT_RESET","UDLD reset interface %s","A port which had been disabled for UDLD has been reset.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"UFAST_MCAST_SW-3-SW","3","PROC_START_ERROR","No process available for transmitting UplinkFast packets.","UplinkFast packets will not be transmitted as the process could not be created.","UplinkFast will not work unless you reload. If this problem persists even after reload, please contact your Cisco Technical Support representative with the configuration and technical support information."
"UFAST_MCAST_SW","4","UNAVAILABLE","No memory is available for transmitting UplinkFast packets on Vlan %d.","UplinkFast packets will not be transmitted on Vlan %d due to a lack of memory.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"UNIX","1","UNAVAILABLE","System aborted","The system aborted. Record the output from the following commands: show proc mem (repeated twice) show memory show buffers show version show runing-config.","Provide this information and the error message to your technical support representative."
"UNIXLC_SPA","3","CMDNOINT","HWIDB Null for command %d, port %#x","The Route Processor passed down a port number that is unknown on the carrier card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIXLC_SPA","3","INVALID_IF","Attempted to access HWIDB for port %u on slot %d subSlot %d","The IOU attempted to access the HWIDB associated with a non-existent port.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIXLC_SPA","3","UNIXIPCALLOCFAIL","Failed to allocate Common IPC buffer %s","The Carrier Card failed to allocate a buffer for communication with the Route Processor.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIXLC_SPA","3","UNAVAILABLE",',"Pointer to object for bay %d is NULL.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIXLC_SPA","3","UNAVAILABLE","Attempted to access HWIDB for port %u on slot %d subSlot %d","The IOU attempted to access the HWIDB associated with a non-existent port.","Copy the error message exactly as it appears, and report it to your technical support representative."
"UNIXLC_SPA","3","UNAVAILABLE","Bay %d - FCI type not set","An FCI type of zero was detected","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIXLC_SPA","3","UNAVAILABLE","Bay %d - Invalid anyphy number %u for vc %d","Interface has invalid anyphy mumber","Seach for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact your Cisco technical support representative. Be sure to provide the the information you have gathered and a 'show tech-support' to your support representative, or attach it to your case in non-zipped, plain text format (.txt)."
"UNIXLC_SPA","3","UNAVAILABLE","Bay %d 12V power is %s","SPA 12V power fault indicator","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIXLC_SPA","3","UNAVAILABLE","Bay %d initialization failure","Failed to create SPI4 subblock","Seach for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIXLC_SPA","3","UNAVAILABLE","Bay %d, spi4 configuration failure, error %d","Failed to configure SPI4 interface","Seach for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIXLC_SPA","3","UNAVAILABLE","Bay %d: %s","An unexpected error has occurred.","Seach for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIXLC_SPA","3","UNAVAILABLE","Creation: port %d vc %d","Failed to create a hwidb.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIXLC_SPA","3","UNAVAILABLE","EFC error - interface %s, vc %d, anyphy %d, err_code %d : %s","Failed to configure efc channel/parameters","Seach for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIXLC_SPA","3","UNAVAILABLE","Failed to %s SPA reference clock on %s","The SPA driver is not able to correctly configure the SPA reference clock on the specified interface. This indicates a hardware error.","No action is required."
"UNIXLC_SPA","3","UNAVAILABLE","Failed to allocate Common IPC buffer %s","The Carrier Card failed to allocate a buffer for communication with the Route Processor.","Copy the error message exactly as it appears, and report it to your technical support representative."
"UNIXLC_SPA","3","UNAVAILABLE","Failed to initialize SPA main c2w bus for subslot %d (status = %d)","The SPA driver is not able to initialize SPA main c2w. This indicates a hardware error.","No action is required."
"UNIXLC_SPA","3","UNAVAILABLE","Failed to provision EFC for interface %s (status = %d)","The SPA driver is not able to provision EFC for the interface specified in the message. This indicates a hardware error.","No action is required."
"UNIXLC_SPA","3","UNAVAILABLE","Failed to unprovision EFC for VC %s (status = %d)","The SPA driver is not able to unprovision EFC for the interface specified in the message. This indicates a hardware error.","No action is required."
"UNIXLC_SPA","3","UNAVAILABLE","Failed to update EFC flow control identifier for interface %s (status = %d)","The SPA driver is not able to update the datapath EFC flow control identifier for the interface specified in the message. This indicates a hardware error.","No action is required."
"UNIXLC_SPA","3","UNAVAILABLE","HWIDB Null for command %d, port %#x","The Route Processor passed down a port number that is unknown on the carrier card.","Copy the error message exactly as it appears, and report it to your technical support representative."
"UNIXLC_SPA","3","UNAVAILABLE","ISR return code out of range. rc=%d","The ISR error return code is out of range.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIXLC_SPA","3","UNAVAILABLE","Link record error - Bay %d vc %d, error code %d","Error processing link record structure","Seach for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact your Cisco technical support representative. Be sure to provide the the information you have gathered and a 'show tech-support' to your support representative, or attach it to your case in non-zipped, plain text format (.txt)."
"UNIXLC_SPA","3","UNAVAILABLE","SPA Sonet clock has failed (status = 0x%08x)","The SPA SONET clock has failed. SPAs that rely on the SPA SONET clock for proper operation, such as POS and ATM will be affected.","If the SPA Sonet clock does not recover, perform an OIR. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIXLC_SPA","3","UNAVAILABLE","SPA Sonet clock has recovered (status = 0x%08x)","SPA Sonet clock has recovered","No action is required."
"UNIXLC_SPA","3","UNAVAILABLE","Subslot %d, spa controller initialisation failure, error %d","Failed to initialise SPA controller","Seach for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIXLC_SPA","3","UNAVAILABLE","Subslot, spa controller EFC configuration failure, error %d","Failed to configure SPA controller EFC","Seach for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIXLC_SPA","3","UNAVAILABLE","subSlot %d, spatype 0x%x. Device error: %s","An error related to a device on the SPA is detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIXLC_SPA","4","UNAVAILABLE","Subslot %d SPA BUS access failed. No SPA present error","SPABUS has reported an error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIXLC_SPA","4","UNAVAILABLE","Subslot %d, %s SPA BUS access failed. timeout=%u err=%u par=%u err_c=0x%x addr=0x%08x data =0x%x","SPABUS has reported an error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIXLC_SPA","4","UNAVAILABLE","Total SPA bandwidth exceeds line card capacity of %lu Mbps","The total bandwidth of SPAs exceeds the rated capacityof this line card.","Refer to the line card guidelines for the maximum allowedaggregated SPA bandwidth for the line card"
"UNIXLC_SPA","4","UNAVAILABLE","Total SPA bandwidth exceeds line card capacity, full utilization of installed SPA interfaces is not supported","The total bandwidth of SPAs exceeds the rated capacityof this line card.","Refer to the line card guidelines for the maximum allowedaggregated SPA bandwidth for the line card"
"UNIXLC_SPA","6","UNAVAILABLE","Bay %d %s changed to %s","SPA OIR Sequence","No action is required."
"UNIXRP","3","CARDERR","%s","An IPC card has registered itself to the IPC master twice. The card malfunctioned and its IPC is not active.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIXRP","3","UNAVAILABLE","%s %u (%s)","Failed to create IPC seat for line card","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIXRP","3","UNAVAILABLE","%s (%u)","IPC slot error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIXRP","3","UNAVAILABLE","%s","An IPC card has registered itself to the IPC master twice. The card malfunctioned and its IPC is not active.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIX_SPA","3","POWER_CYCLE","%s occurred on Shared Port Adapter %u/%u","An error has occurred which will cause the Shared Port Adapter to be power cycled","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIXRP_SPA","3","UNAVAILABLE",',"Pointer to object for slot %d, bay %d is NULL.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIXRP_SPA","3","UNAVAILABLE","Creation: slot %d subSlot %d port %d vc %d","Failed to create an interface hwidb.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIXRP_SPA","3","UNAVAILABLE","Failed to allocate IPC buffer %s","The RP failed to allocate a buffer for communication with a SPA","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIXRP_SPA","3","UNAVAILABLE","Failed to allocate a flow control identifier for interface %s","The SPA driver is not able to allocate the datapath flow control identifier for the interface specified in the message. This indicates a software error.","No action is required."
"UNIXRP_SPA","3","UNAVAILABLE","Failed to initialize data structure for SPA port %d/%d/%d","A SPA driver was not able to properly initialize a data structure mentioned in the message. This indicates a software error.","No action is required."
"UNIXRP_SPA","3","UNAVAILABLE","Failed to provision interface %s","The SPA driver is not able to provision the interfacespecified in the message. Verify that the SPA hardware is not provisioned above the supported limit. Otherwise, this indicates a hardware error.","No action is required."
"UNIXRP_SPA","3","UNAVAILABLE","Failed to release a flow control identifier for interface %s (status = %d)","The SPA driver is not able to release the datapath flow control identifier for the interface specified in the message. This indicates a software error.","No action is required."
"UNIXRP_SPA","3","UNAVAILABLE","Failed to retrieve datapath identifier for interface %s","The SPA driver is not able to retrieve the datapath identifier for the interface specified in the message. This indicates a software error.","No action is required."
"UNIXRP_SPA","3","UNAVAILABLE","Failed to update connection identifier for interface %s","The SPA driver is not able to update the datapath connection identifier for the interface specified in the message. This indicates a software error.","No action is required."
"UNIXRP_SPA","3","UNAVAILABLE","HWIDB not found: slot %d, bay %d, port %d","A NULL hwidb is encountered","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIXRP_SPA","3","UNAVAILABLE","NULL","A SPA driver is not able to retrieve the data structure mentioned in the message. This indicates a software error.","No action is required."
"UNIXRP_SPA","3","UNAVAILABLE","Power to IPSEC-SPA-2G in %s is denied because it has exceeded the number allowed(%d)","The number of IPSEC-SPA-2G in a chassis is limited.This message is displayed when the number of IPSEC-SPA-2G inthe chassis has exceeded this limit.","Use only the number of supported IPSEC-SPA-2G"
"UNIXRP_SPA","3","UNAVAILABLE","slot %d subSlot %d, PID %s","Failed to get information about the host linecard.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIXRP_SPA","3","UNAVAILABLE","slot %d subSlot %d, spaType 0x%x","Failed to get information about the host linecard.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIXRP_SPA","3","UNAVAILABLE","slot=%d port=%d, hwidbType=0x%x, max_port_num=%d, LCtype=0x%x","The port number is out of range.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIXRP_SPA","4","UNAVAILABLE","%s: Expecting response to interface configuration command %u but received response to command %u.","An internal synchronization error occurred while configuring the interface. The configuration may not have succeeded.","Check that the running configuration for the interface is correct. If this message occurred on the standby, try reloading the standby to ensure that its configuration is in sync. If this message is repeatable, please 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIXRP_SPA","4","UNAVAILABLE","%s: No response for interface configuration command %u","A timeout occurred while RP was waiting for a response from line card. This may happen due to line card CPU being too busy to respond to the command.","No action is required."
"UNIXRP_SPA","6","UNAVAILABLE","Module %u reload due to SPA insert in %u/%u.","When inserting a SPA on this carrier card, the cardis reset.","No action is required."
"UNIX_BPD","3","UNAVAILABLE","%s: (%d)","HWIDB Lookup Error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIX_BPD","3","UNAVAILABLE","%s: (%s)","Packet Not Available","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIX_IFUTIL","3","UNAVAILABLE","%s Pool Creation Error for hwidb: %s","POOL Creation Error","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIX_IFUTIL","3","UNAVAILABLE","Pak not available, %s: %s","The running configuration was too big to be synced","No action is required."
"UNIX_SPA","3","UNAVAILABLE",',"Pointer to a SPA object is NULL.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIX_SPA","3","UNAVAILABLE","%s","Memory allocation error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIX_SPA","3","UNAVAILABLE","%s called with NULL hwidb","A NULL hwidb is encountered","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIX_SPA","3","UNAVAILABLE","%s did not complete %d/%d","An error has occured during diagnostic test.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIX_SPA","3","UNAVAILABLE","%s occurred on Shared Port Adapter %u/%u","An error has occurred which will cause the Shared Port Adapter to be power cycled","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIX_SPA","3","UNAVAILABLE","%s vector is not initialized. spaType=0x%x","A required function vector is not initialized","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIX_SPA","3","UNAVAILABLE","%s virtual function table is not initialized. spaType=0x%x","A required function table is not initialized","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIX_SPA","3","UNAVAILABLE","Data conversion error (%s, 0x%X)","An internal software error has occured when converting the data specified in the message from one representation to another.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIX_SPA","3","UNAVAILABLE","Failed to create SPA SB","Failed to create a SPA subblock.Error Message    v%UNIX_SPA-3-UNAVAILABLE: Failed to send configuration for %s to carrier-card for subslot=%d/%d Explanation    Sending configuration failed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIX_SPA","3","UNAVAILABLE","IPC failure while %s","An error has occurred while prepareing or sending an IPC message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIX_SPA","3","UNAVAILABLE","cardwide-port = %d, max cardwide-port = %d","Invalid cardwide-port number.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIX_SPA","3","UNAVAILABLE","index1= %d, index2= %d, maxIndex= %d","Invalid index range.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIX_SPA","3","UNAVAILABLE","index= %d, spaType=0x%x, slot %d subSlot %d slotunit %d vc %d","Index for the interface is not valid.Error Message    v%UNIX_SPA-3-UNAVAILABLE: interface type %s, slot %d port %d vc %d : %s Explanation    Data required to support the interface is not available.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIX_SPA","3","UNAVAILABLE","slot= %d, max slot = %d","Invalid slot number.Error Message    v%UNIX_SPA-3-UNAVAILABLE: slot=%d subslot=%d, PID=%s lc_type=0x%x. Explanation    Failed to create a SPA object.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNIX_SPA","3","UNAVAILABLE","slot=%d subslot=%d, spa_type=0x%x, lc_type=0x%x.","Failed to create a SPA object.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UNICAST_FLOOD","4","DETECTED","Host [enet] on vlan [dec] is flooding to an unknown unicast destination at a rate greater than/equal to [dec] Kfps","A host was found going up and down between ports.","Verify the reason why the host is sending traffic to an unknown unicast destination."
"UNICAST_FLOOD","4","FILTER_TABLE_FULL","The filter table is full","The system has detected too many unicast floods to unknown destinations.","Investigate the reason why so many hosts in the network are sending traffic to unknown unicast destinations."
"UNICAST_FLOOD","5","FILTER_INSTALLED","Filter for host [enet] has been installed. It will be removed in [dec] minute(s)","A host was flooding unicast packets to an unknown destination. A filter has been installed.","No action is required."
"UTIL","3","TREE","Data structure error--%s","A software error occurred, resulting in a data structure inconsistency.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"UTIL","3","UNAVAILABLE","Data structure error -- %s","A software error occurred, resulting in data structure inconsistency.","Copy the error message exactly as it appears, and report it to your technical support representative."
"UTIL","3","UNAVAILABLE","Data structure error--%s","A software error occurred, resulting in a data structure inconsistency.","Copy the error message exactly as it appears, and report it to your technical support representative. Ask for their assistance in obtaining a version of code with the error fixed."
"UTIL","3","UNAVAILABLE","internal inconsistency %d %x","A fatal software error occurred.","Copy the error message exactly as it appears, and report it to your technical support representative."
"UTIL","3","UNAVAILABLE","null pointer input to range function","An attempt was made to access a range function with a NULL pointer. The range list creation failed.","Review the error log for a corresponding malloc failed message. Copy the error message exactly as it appears, and report it to your technical support representative."
"UTIL","6","UNAVAILABLE","A pseudo-random number was generated twice in succession","A pseudo-random number generator produced the same number twice in succession.","Under normal circumstances a pseudo-random number generator will occasionally produce the same number twice in succession and this is not a problem. However if this message occurs frequently, the system should be manually reloaded. If the message is persistent across reloads, copy the error message exactly as it appears, and report it to your technical support representative."
"VACL","4","VLANACCESSMAP_ACTION_CHANGED","No redirect interfaces, map <[chars]> - sequence [dec] action set to DROP","One or more redirect interfaces were removed, leaving the redirect interface list emptyand changing the sequence action to DROP.","Update the sequence, adding one or more valid redirect interfaces to the affected VLAN access maps."
"VACL","4","VLANACCESSMAP_CWAN_DELETE","VLAN ACCESS-MAP [chars] applied on [chars] will be removed.","Logical interface(MFR,MLP) with a VACL Access-map is being removed so the associated vlan filter will be removed to avoid config errors and inconsistencies","User has to re-configure the vlan filter if the removed logical interface is being removed"
"VACL","4","VLANACCESSMAP_RDT_DELETE","[chars] [chars] is removed from redirect list of map: [chars] - sequence [dec]","One of the redirect interfaces in a VLAN access map needed to be removed from a redirect sequence. This situation can occur if the interface was deleted or became an active member of an Ethernet channel that is not supported.","Revert the state of the interface and add this redirect interface again to the redirect sequence for the affected VLAN access maps."
"VALENCIA","3","GIO","Bay [dec]: [chars].","A data corruption due to a parity error was detected on the GIO bus.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VALENCIA","3","NP","Bay [dec], [chars][dec]: [chars].","Data corruption was detected in one of the network processors.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VALENCIA","3","PL3","Bay [dec]: [chars].","A data corruption due to a parity error was detected on the PL3 interface.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VALENCIA","3","PLL_LOCK","Bay [dec]: [chars] PLL Lock Failure","The specified phase-locked loop (PLL) failed to lock.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VALENCIA","3","PPE","Bay [dec], [chars]: [chars].","Data corruption was detected in the VLAN RAM.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VALENCIA","3","SPI_FIFO","Bay [dec], [chars]: [chars] [chars].","Data corruption was detected in one of the SPI FIFOs.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VALENCIA","3","SPI_SNK","Bay [dec]: [chars].","There was an error receiving data from the SPA, possibly due to data corruption.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VALENCIA","3","SPI_SNK_CHAN","Bay [dec]: [chars] error on channel [dec].","There was an error receiving data from the SPA.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VALENCIA","3","SPI_SRC","Bay [dec]: [chars].","There was an error sending data to the SPA.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VDD","3","NULL_CB","Supplied %s control block is NULL. %s","An NULL control block was passed internally as part of an operation to read or write to the required register or memory address. As a result, the operation could not be processed and the address contents are now incorrect.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VDD","3","NULL_SPACE_CB","Supplied %s space control block is NULL. %s","An NULL space control block was passed internally as part of an operation to read or write to the required address. As a result, the operation could not be processed and the address contents are now incorrect.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VDD","3","SIZE_TOO_LARGE","An attempt was made to create a %s of size %d bits.","The virtual device driver received a request to create a data entity that is larger than allowed. Because the entry cannot be created, its data will be lost.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VFC","1","UNAVAILABLE","%s , Error interrupt occured type = 0x%x.","The DMA engine cannot get to the PCI bus, to read descriptors.","Copy the error message exactly as it appears, and report it to your technical support representative."
"VFC","1","UNAVAILABLE","%x packet(size %d) too big.","A packet greater than the 256 bytes received on this interface.","The system should recover. No action is required. If the problem reccurs, it indicates an error that might be related to data traffic patterns. Copy the error message exactly as it appears, and report it to your technical support representative."
"VFC","1","UNAVAILABLE","No more ring descriptors available on %d slot.","The VFC driver cannot queue messages onto Rossini dma engine for transmit.","Copy the error message exactly as it appears, and report it to your technical support representative. Reset the DSP's on this port module."
"VFC","1","UNAVAILABLE","VFC (%d/%d), vfc dual-ported memory unavailable.","The router or access server could not allocate dual-ported memory for the descriptors.","Copy the error message exactly as it appears, and report it to your technical support representative."
"VFC","1","UNAVAILABLE","VFC in slot %d: Incorrect %d DSP-ID passed by SPI.","The DSP ID provided by the SPI for download is not valid.","Call your technical support representative for assistance."
"VFC","1","UNAVAILABLE","vfc(%d), No dsp module has been found.","The software did not find any of DSP module plugged into the voice card.","Check the part number on the dspm card to see if it is supported in the version of IOS operational on the router or contact your technical support representative."
"VFC","1","UNAVAILABLE","vfc(%d), vfc cards has an invalid configuration.","The software did recognized more dsp interface port than it can support on this card.","Check the part number on the VIC card to see if it is supported in the version of IOS operational on the router or contact your technical support representative."
"VFC","1","UNAVAILABLE","vfc(%d), vfc dspm daughter card has an unknown id of %x","The software did not recognize the type of DSP module plugged into the voice card.","Check the part number on the dspm card to see if it is supported in the version of IOS operational on the router or contact your technical support representative."
"VFC","3","UNAVAILABLE","%s Unable to download the Application overlay firmware. Status returned 0x%x","Error initializing the DSP with the application/overlay firmware.","Power down, reinsert Port Module and reboot. If message recurs, call your technical support representative for assistance."
"VFC","3","UNAVAILABLE","%s Unable to download the Boot loader firmware, ret = 0x%x","Error initializing the DSP with the bootloader firmware.","Power down, reinsert Port Module and reboot. If message recurs, call your technical support representative for assistance."
"VFC","3","UNAVAILABLE","%s, Error analyzing the device in slot %d.","The feature card in this slot could not be recognized.","Power down, reinsert voice feature card and reboot. If message recurs, call your technical support representative for assistance."
"VFC","3","UNAVAILABLE","VFC in slot %d: PCI device not supported.","A interface controller device did not report correct device ID","Power down, reinsert Port Module and reboot. If message recurs, call your technical support representative for assistance."
"VFI","3","UNAVAILABLE","%s","An illegal event has been processed by the xconnect subsystem.","LOG_STD_NO_ACTION"
"VFI","4","CONFIG","%s","The specified configuration data for a virtual forwarding instance (VFI) is invalid.","No action is required."
"VINES","2","UNAVAILABLE","%s called with %s parameter set to %s","One of the VINES lookup functions was called with an illegal argument.","Copy the message exactly as it appears, do a memory dump up to 128 bytes and the location specified in the error message, and report this information to your technical support representative."
"VINES","2","UNAVAILABLE","Bad %s in path for neighbor entry %z","While searching the neighbor table, the code determined that a pointer that should point to a VINES path structure actually points to some other structure.","Copy the message exactly as it appears, and report it your technical support representative. If possible, clear the VINES neighbor table. This will result in a temporary loss of connectivity until all neighbors and routes are relearned."
"VINES","2","UNAVAILABLE","Bad %s in route for server entry %Z","While searching the routing table, the code determined that a pointer that should point to a VINES route structure actually points to some other structure.","Copy the message exactly as it appears, and report it your technical support representative. If possible, clear the VINES routing table. This will result in a temporary loss of connectivity until all routes are relearned."
"VINES","2","UNAVAILABLE","Caching of %s not supported on %s","The cache population routing for VINES fast switching was called for an interface that does not support VINES fast switching.","Copy the message exactly as it appears, and report it your technical support representative. If other encapsulation types are available on the interface, try using them. If this problem is not limited to one or two destinations but rather occurs with all traffic using the interface, diable VINES fast switching for the interface until you have identified the real cause of the problem."
"VINES","2","UNAVAILABLE","Cannot build cache entry (%d bytes) for %#z on %s","VINES fast switching detected that the packet destined to a given address did not have proper encapsulation information or its encapsulation size was too large to fit into the cache.","Verify that the VINES encapsulation and interface-specific mappings for the interface concerned are properly configured. Copy the message exactly as it appears, and report it your technical support representative."
"VINES","2","UNAVAILABLE","Detected a corrupted entry in the %s table","The VINES code detected that an internal table entry was corrupted.","Copy the message exactly as it appears, and report it your technical support representative. If possible, clear the VINES routing table or neighbor table, depending on the table in which the corrupted entry was observed. This will result in a temporary loss of connectivity until the routing or neighbor table is rebuilt."
"VINES","2","UNAVAILABLE","Duplicate address detected on interface %s","The router detected that its VINES address is being used by another router.","To identify the other router that is using this address, manually inspect each router's configuration. When you have identified the router with the duplicate address, issue the vines routing recompute command on both routers or issue the enable vines routing command, specifying specify a unique address. If one of the routers does not support the recompute keyword, disable VINES on that router, issue the write terminal command to save the configuration to memory, reboot the router, and then enter the vines routing command with a unique vines address on the offending routers until each router has a unique address."
"VINES","2","UNAVAILABLE","Encapsulation failed for %#z via %#z on %s","VINES fast switching encountered an encapsulation failure when building a cache entry for a neighbor.","Examine your configuration for causes of the encapsulation failure. Look for missing map statements, interfaces that have gone down, and so on. If this error results in lost connectivity, disable vines fast switching by issuing the no vines route-cache command. Because disabling fast switching will slow network perform, you should issue the vines route-cache command to re-enable fast switching as soon as you have identified the cause of the problem. If you cannot identify the cause, contact your technical support representative. Provide the output of the show vines cache, show vines neighbor, and show vines route commands for the destination address and neighboring routers you are using. Also provide the output of the show interface and show vinces interface commands for the incoming and outgoing interfaces."
"VINES","2","UNAVAILABLE","Encapsulation failed on %s for address %#z","The VINES code tried to send a packet on an interface that does not have a new encapsulation routine for outbound packets.","Toggle the problematic interface by issuing the interface shut and no shut commands, and then issue the no vines metric and vines metric command see if the problem goes away. If the problem persists, copy the message exactly as it appears, and report it your technical support representative. If possible, turn on and provide interface- specific debug traces, particularly for VINES activities."
"VINES","2","UNAVAILABLE","Error %s","The VINES code ran into a situation that should not happen. For example, an IPC port number needs to be allocated, but all 65535 port numbers are currently in use. Another possible cause is that VINES attempted to add a cache entry but had no path associated with the destination address. This may cause temporary slow performance to only those stations that have experienced this inconsistency until complete cache entries are added. However, connectivity should not be lost, because all data traffic can still be routed vvia process-level switching.","Copy the message exactly as it appears, and report it your technical support representative. If the warning message is about IPC port number depletion, use the show vines ipc command to check how many IPC ports are currently in use by which services and determine whether the IPC connections are all legitimate. To release IPC ports, issue the clear vines ipc command. If the warning message is about vines cache entries, provide the contents of the vines route cache, neighbor, and route tables immediately after the error messages appeared. If the problem persists, issue the clear vines cache command, and monitor the router if the situation improves."
"VINES","2","UNAVAILABLE","No buffers available for %s","There were no buffers available to send a VINES service query or reply.","Examine your system's memory and buffer capacity and compare it with current usage. If you notice a substantial discrepancy, monitor your system for possible memory leaks or buffer drainage and report the problem to your technical support representative, along with the output of the show memory, show memory processor, show buffers, show buffers assigned, and show buffers old commands."
"VINES","2","UNAVAILABLE","RTP timer for %s was found disabled, and was reset","An internal interface timer is not running. This condition usually occurs after an interface is reset.","No action is required. The system automatically restarts the timer."
"VINES","6","UNAVAILABLE","%s service %s routine missing %s vector","There is an inconsistency in the static VINES data structures for handling application-layer packets.","Turn on VINES service level debugging for the service reported in the error message, and copy the debug traces and the error message exactly as they appear, and report them to your technical support representative."
"VINES","6","UNAVAILABLE","%s service %s routine not found while %s","There is an inconsistency in the active VINES service description data structures. A service handler routine cannot find the description of its own service.","Copy the message exactly as it appears, and report it your technical support representative. In addition, provide the output of the show vines service command and debug vines service traces for the service reported in the error message."
"VINES","6","UNAVAILABLE","IPC port %d registered without a service","There is an inconsistency in the active VINES data structure for handling Net RPC messages. A message was received for a port that should have a service description, but that service description cannot be found.","Enter the show vines ipc command and see whether the reported IPC port has a registered service. Copy the message exactly as it appears, and report it to your technical support representative, if possible, along with output of the debug vines netrpc command."
"VINES","6","UNAVAILABLE","IPC port %d registered without an upcall (%s)","There is an inconsistency in the active VINES data structure for handling IPC data messages. A message was received for a port that should have a listener, but the listener routine cannot be found.","Examine the IPC ports currently supported on the router by issuing the show vines ipc command, and see whether the reported IPC port is indeed not active. Copy the message exactly as it appears, and report it to your technical support representative along with the output of the debug vines ipc command."
"VIP","2","NOICBS","No MEMD icbs left for PA %d Interface %d","No Switch Processor (SP) interrupt control block structure was associated with the port adaptor or the interface.","Copy the error message exactly as it appears, and report it to your technical support representative."
"VIP","3","AFOVERFLOW","VIP address filter table full","VIP Ethernet-like interface uses an internal MAC address table to filter incoming packets. Once the table is full, additional address entries are rejected. Any incoming packet with destination address not in the the table will be ignored.","The address table is consumed by various protocols, like PIM or HSRP. If too many HSRP is configured for one interface, the entry could be exhausted. The suggested solution would be to distribute some of those HSRP entries to other Ethernet interface."
"VIP","3","BADMALUCMD","Unsupported MALU command %d, arg=%#x, pascb=%#x","The Route Processor (RP) or the Route/Switch Processor (RSP) passed down a command that the software was not prepared to handle.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VIP","3","CMDNOPASCB","PASCB Null for command %d, arg=%#x","The Route Processor (RP) or the Route/Switch Processor (RSP) passed down a command that the software was unprepared to handle.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VIP","3","INVALID_BUS_NO","Invalid Bus Number %d in MVIP Mask Setting","An invalid bus number was entered in the MVIP mask setting function. The bus number should be 1 or 2 because the MVIP has only two PCI buses.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VIP","3","IO_PARITY_NOT_IMPLEMENTED","IO Memory Parity Error Test not implemented","A function to check memory parity errors was called, but the I/O Memory Parity Error Test has not been implemented","Refer to related support documents or contact your Cisco technical support representative for more information about parity error tests."
"VIP","3","LOVELETTER_STAT_SEND_ERROR","%s : Loveletter Stats Send Failed","An attempt to send a statistics love letter from the VIP has failed.","Copy the error message exactly as it appears on the console or in the system log.Issue the show controllers vip solt# tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error text or from the show controllers vip slot# tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information."
"VIP","3","LOVENOTE_ERR","Lovenote for %s not delivered to RSP","A Status update for this interface could not be sent to the RSP because of temporary non-availability of buffer headers.","If the interface has not come up after rebooting, configure shutdown and then no shutdown for the interface"
"VIP","3","LOVENOTE_SEND_ERROR","Love Note for %s - sending failed.","An attempt to send a love note from the VIP has failed.","Copy the error message exactly as it appears on the console or in the system log.Issue the show controllers vip solt# tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error text or from the show controllers vip slot# tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information."
"VIP","3","LQR_IPC_FAIL","%s","The IPC Port through which RSP will send LQRs to VIP failed to initialise. The PPP link might go down because of this error.","Disable LQM configured on the PPP link and contact Cisco Technical representative"
"VIP","3","MALLOC_FAILURE_IPC","Failed to allocate IPC message to contact process","A memory allocation failure has occurred during the processing of an IPC message.","Copy the error message exactly as it appears on the console or in the system log.Issue the show controllers vip solt# tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error text or from the show controllers vip slot# tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information."
"VIP","3","MALLOC_FAILURE_IPFAST_ENCAP","IPFAST_ENCAP:malloc failed to allocate.","A memory allocation failure has occurred in the IPFAST_ENCAP module.","Copy the error message exactly as it appears on the console or in the system log.Issue the show controllers vip solt# tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error text or from the show controllers vip slot# tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information."
"VIP","3","NODISPATCH","Dispatch vector Null, cmd=%d, dintf=%d","No command dispatch vector was found for the specified interface.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VIP","3","PA_NOT_SUPPORTED","%s PA in bay %d not supported on %s","The specified PA is not supported on the specified platform.","Refer to the appropriate support documents for more details about the platforms that are supported."
"VIP","3","SYSTEM_EXCEPTION","VIP System Exception occurred sig=%d, code=%#x, context=%#x","A system exception error has occurred in the VIP. See the VIP console for more information and for the context dump.","Copy the error message exactly as it appears on the console or in the system log. Issue the show contollers vip slot# tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error text or from the show controllers vip slot# tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information."
"VIP","3","SYSTEM_EXCEPTION","VIP System Exception occurred sig=%d, code=%#x, context=%#x","A system exception error has occurred in the VIP. See the VIP console for more information and for the context dump.","Copy the error message exactly as it appears on the console or in the system log. Issue the show contollers vip slot# tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error text or from the show controllers vip slot# tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information."
"VIP","3","UNAVAILABLE","IO Memory Parity Error Test not implemented","A function to check memory parity errors was called, but the I/O Memory Parity Error Test has not been implemented","Refer to related support documents or contact your Cisco technical support representative for more information about parity error tests."
"VIP","3","UNAVAILABLE","%s : Loveletter Stats Send Failed","An attempt to send a statistics love letter from the VIP has failed.","Copy the error message exactly as it appears on the console or in the system log.Issue the show controllers vip solt# tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error text or from the show controllers vip slot# tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information."
"VIP","3","UNAVAILABLE","%s","The IPC Port through which RSP will send LQRs to VIP failed to initialise. The PPP link might go down because of this error.","Disable LQM configured on the PPP link and contact Cisco Technical representative"
"VIP","3","UNAVAILABLE","%s PA in bay %d not supported on %s","The specified PA is not supported on the specified platform.","Refer to the appropriate support documents for more details about the platforms that are supported."
"VIP","3","UNAVAILABLE","A Cybus Error occurred.","The MVIP error interrupt handler has been called a Cybus error.","LOG_STD_VIP_RECUR_ACTION"
"VIP","3","UNAVAILABLE","A Cybus Error occurred.","The SVIP error interrupt handler has been called due to a Cybus error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VIP","3","UNAVAILABLE","A PCI bus 1 parity error. .","A PCI bus 1 parity error has been encountered.","LOG_STD_VIP_RECUR_ACTION"
"VIP","3","UNAVAILABLE","A PMA Error occurred.","The SVIP error interrupt handler has been called due to a PMA error.","LOG_STD_VIP_RECUR_ACTION"
"VIP","3","UNAVAILABLE","An unknown IPC message type %x","An unidentified IPC message in the VIP IPFAST_DS module has been received.","Copy the error message exactly as it appears on the console or in the system log.Issue the show controllers vip solt# tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error text or from the show controllers vip slot# tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information."
"VIP","3","UNAVAILABLE","Crashinfo initiation failed on the VIP.","The crash information (crashinfo) file for the VIP could not be collected because the process to collect the crashinfo file could not be propertly initiated.","LOG_STD_VIP_RECUR_ACTION"
"VIP","3","UNAVAILABLE","DRAM Reno ASIC write bus error:Error address = 0x%08x, %s.","A Reno ASIC write bus error has occurred.","LOG_STD_VIP_RECUR_ACTION"
"VIP","3","UNAVAILABLE","Dispatch vector Null, cmd=%d, dintf=%d","No command dispatch vector was found for the specified interface.","Copy the error message exactly as it appears, and report it to your technical support representative."
"VIP","3","UNAVAILABLE","Failed to allocate IPC message to contact process","A memory allocation failure has occurred during the processing of an IPC message.","Copy the error message exactly as it appears on the console or in the system log.Issue the show controllers vip solt# tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error text or from the show controllers vip slot# tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information."
"VIP","3","UNAVAILABLE","Failed to open port while connecting to process statistics: error code = %s","An error occurred during an attempt to open a port for an IPC message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VIP","3","UNAVAILABLE","Failed to send process statistics update : error code = %s","An error occurred during an attempt to send an IPC message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VIP","3","UNAVAILABLE","IO Reno ASIC bus error:Error address = 0x%08x, %s.","An I/O Reno ASIC bus error has occurred.","LOG_STD_VIP_RECUR_ACTION"
"VIP","3","UNAVAILABLE","IPFAST_DS : Bad message of size=%d received","An IPC message with an invalid buffer size has been received.The parameters that were specified on the request are inconsistent. A buffer for the IPC message had been requested, but the specified buffer size is invalid or missing. The size of the requested buffer must be specified within the request. This error is due to an internal code problem with the system.","Copy the error message exactly as it appears on the console or in the system log.Issue the show controllers vip solt# tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error text or from the show controllers vip slot# tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information."
"VIP","3","UNAVAILABLE","IPFAST_ENCAP : Bad IPC message of size=%d received","An IPC message with an invalid buffer size has been received.The parameters that were specified on the request are inconsistent. A buffer for the IPC message had been requested, but the specified buffer size is invalid or missing. The size of the requested buffer must be specified within the request. This error is due to an internal code problem with the system.","Copy the error message exactly as it appears on the console or in the system log.Issue the show controllers vip solt# tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error text or from the show controllers vip slot# tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information."
"VIP","3","UNAVAILABLE","IPFAST_ENCAP:malloc failed to allocate.","A memory allocation failure has occurred in the IPFAST_ENCAP module.","Copy the error message exactly as it appears on the console or in the system log.Issue the show controllers vip solt# tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error text or from the show controllers vip slot# tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information."
"VIP","3","UNAVAILABLE","Invalid Bus Number %d in MVIP Mask Setting","An invalid bus number was entered in the MVIP mask setting function. The bus number should be 1 or 2 because the MVIP has only two PCI buses.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VIP","3","UNAVAILABLE","Invalid queue size: value = %u","An invalid queue size has been found.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VIP","3","UNAVAILABLE","Love Note for %s - sending failed.","An attempt to send a love note from the VIP has failed.","Copy the error message exactly as it appears on the console or in the system log.Issue the show controllers vip solt# tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error text or from the show controllers vip slot# tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information."
"VIP","3","UNAVAILABLE","Lovenote for %s not delivered to RSP","A Status update for this interface could not be sent to the RSP because of temporary non-availability of buffer headers.","If the interface has not come up after rebooting, configure shutdown and then no shutdown for the interface"
"VIP","3","UNAVAILABLE","PASCB Null for command %d, arg=%#x","The Route Processor (RP) or the Route/Switch Processor (RSP) passed down a command that the software was unprepared to handle.","Copy the error message exactly as it appears, and report it to your technical support representative."
"VIP","3","UNAVAILABLE","PCI bus 0 parity error.","A PCI bus 0 parity error has been encountered.","LOG_STD_VIP_RECUR_ACTION"
"VIP","3","UNAVAILABLE","PCI bus 0 system error.","A PCI bus 0 system error has been encountered.","LOG_STD_VIP_RECUR_ACTION"
"VIP","3","UNAVAILABLE","PCI bus 1 system error.","A PCI bus 1 system error has been encountered.","LOG_STD_VIP_RECUR_ACTION"
"VIP","3","UNAVAILABLE","PCI bus 2 parity error.","A PCI bus 2 parity error has been encountered.","LOG_STD_VIP_RECUR_ACTION"
"VIP","3","UNAVAILABLE","PCI bus 2 system error.","A PCI bus 2 system error has been encountered.","LOG_STD_VIP_RECUR_ACTION"
"VIP","3","UNAVAILABLE","Packet memory ECC single-bit exception addr = %08x data = %08x","A packet memory ECC single-bit error has been detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VIP","3","UNAVAILABLE","Packet memory single-bit errors exceed maximum limit of %d","The number of packet memory ECC single-bit errors have been exceeded the maximum limit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VIP","3","UNAVAILABLE","Processor memory ECC single-bit exception addr = %08x data = %08x","A processor memory ECC single-bit error has been detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VIP","3","UNAVAILABLE","Processor memory single-bit errors exceed the maximum limit of %d","The number of Processor memory ECC single-bit errors have been exceeded the maximum limit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VIP","3","UNAVAILABLE","Received unknown IPC message type %x","An unidentified IPC message has been received in the VIP IPFAST_ENCAP module.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VIP","3","UNAVAILABLE","Reno ASIC read parity error - bytes 0 & 1.","A Reno ASIC write parity error has been encountered for bytes 0 and 1.","LOG_STD_VIP_RECUR_ACTION"
"VIP","3","UNAVAILABLE","Reno ASIC read parity error - bytes 2 & 3.","A Reno ASIC write parity error has been encountered for bytes 2 and 3.","LOG_STD_VIP_RECUR_ACTION"
"VIP","3","UNAVAILABLE","Reno ASIC write parity error - bytes 0 & 1.","A Reno ASIC write parity error has been encountered for bytes 0 and 1.","LOG_STD_VIP_RECUR_ACTION"
"VIP","3","UNAVAILABLE","Reno ASIC write parity error - bytes 2 & 3.","A Reno ASIC write parity error has been encountered for bytes 2 and 3.","LOG_STD_VIP_RECUR_ACTION"
"VIP","3","UNAVAILABLE","SVIP Reload is called.","An SVIP reload was initiated because of a VIP failure.","LOG_STD_VIP_RECUR_ACTION"
"VIP","3","UNAVAILABLE","Undefined idb type %d","This message is sent from the VIP kernel when it sees a media type other than Ethernet, Token-Ring, or serial. These are the media types supported by Cisco IOS Release 11.2 on the VIP. The message might be caused by having an older version of the software running on a device with a new VIP port adapter.","Check whether the version of the software being run supports the VIP port adapter. If an old software version does not appear to be the problem, copy the error message exactly as it appears and report it to your technical support representative."
"VIP","3","UNAVAILABLE","Unsupported MALU command %d, arg=%#x, pascb=%#x","The Route Processor (RP) or the Route/Switch Processor (RSP) passed down a command that the software was not prepared to handle.","Copy the error message exactly as it appears, and report it to your technical support representative."
"VIP","3","UNAVAILABLE","VIP System Exception occurred sig=%d, code=%#x, context=%#x","A system exception error has occurred in the VIP. See the VIP console for more information and for the context dump.","Copy the error message exactly as it appears on the console or in the system log. Issue the show contollers vip slot# tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error text or from the show controllers vip slot# tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information."
"VIP","3","UNAVAILABLE","VIP address filter table full","VIP Ethernet-like interface uses an internal MAC address table to filter incoming packets. Once the table is full, additional address entries are rejected. Any incoming packet with destination address not in the the table will be ignored.","The address table is consumed by various protocols, like PIM or HSRP. If too many HSRP is configured for one interface, the entry could be exhausted. The suggested solution would be to distribute some of those HSRP entries to other Ethernet interface."
"VIP","3","UNDEFIDBTYPE","Undefined idb type %d","This message is sent from the VIP kernel when it sees a media type other than Ethernet, Token-Ring, or serial. These are the media types supported by Cisco IOS Release 11.2 on the VIP. The message might be caused by having an older version of the software running on a device with a new VIP port adapter.","Check whether the version of the software being run supports the VIP port adapter. If an old software version does not appear to be the problem, copy the error message exactly as it appears and report it to your technical support representative."
"VIP","3","UNKNOWN_MESSAGE_IPAST_DS","An unknown IPC message type %x","An unidentified IPC message in the VIP IPFAST_DS module has been received.","Copy the error message exactly as it appears on the console or in the system log.Issue the show controllers vip solt# tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error text or from the show controllers vip slot# tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information."
"VIP","3","WRONGSIZE_IPFAST_DS","IPFAST_DS : Bad message of size=%d received","An IPC message with an invalid buffer size has been received.The parameters that were specified on the request are inconsistent. A buffer for the IPC message had been requested, but the specified buffer size is invalid or missing. The size of the requested buffer must be specified within the request. This error is due to an internal code problem with the system.","Copy the error message exactly as it appears on the console or in the system log.Issue the show controllers vip solt# tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error text or from the show controllers vip slot# tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information."
"VIP","3","WRONGSIZE_IPFAST_ENCAP","IPFAST_ENCAP : Bad IPC message of size=%d received","An IPC message with an invalid buffer size has been received.The parameters that were specified on the request are inconsistent. A buffer for the IPC message had been requested, but the specified buffer size is invalid or missing. The size of the requested buffer must be specified within the request. This error is due to an internal code problem with the system.","Copy the error message exactly as it appears on the console or in the system log.Issue the show controllers vip solt# tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error text or from the show controllers vip slot# tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information."
"VIPMLP","2","NOINTERLEAVE","%s Interleave not configured due to Insufficient memory","Interleave not configured due to Insufficient memory.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VIPMLP","2","NOVC","%s: packet received for non-existent VC %d","Virtual channel encapsulation is corrupted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VIPMLP","2","UNAVAILABLE","%s Interleave not configured due to Insufficient memory","Interleave not configured due to Insufficient memory.","Copy the error message exactly as it appears, and report it to your technical support representative."
"VIPMLP","2","UNAVAILABLE","%s: packet received for non-existent VC %d","Virtual channel encapsulation is corrupted.","Copy the error message exactly as it appears, and report it to your technical support representative."
"VLAN_MAPPING_ISSU","3","BUFFER","vlan_mapping VLAN Mapping ISSU client failed to get buffer for message, error %d","The VLAN mapping ISSU client was unable to get a buffer for building a negotiation message. As a result, the client cannot send the negotiation message to the standby unit and the standby unit cannot be brought up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"VLAN_MAPPING_ISSU","3","CAPABILITY","vlan_mapping VLAN Mapping ISSU client %s","The VLAN mapping ISSU client detected an error during capability negotiation. As a result, there is a mismatch in the client capability between the active and standby unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"VLAN_MAPPING_ISSU","3","INIT","vlan_mapping VLAN Mapping ISSU client initialization failed at %s, error %s","The VLAN mapping ISSU client could not be initialized. This condition will cause a catastrophic failure when an ISSU upgrade or downgrade is performed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VLAN_MAPPING_ISSU","3","MSG_NOT_OK","vlan_mapping VLAN Mapping ISSU client message %d is not compatible","The VLAN mapping ISSU client received an incompatible message from the peer unit. The message cannot be processed by this unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"VLAN_MAPPING_ISSU","3","MSG_SIZE","vlan_mapping VLAN Mapping ISSU client failed to get the message size for message %d","The VLAN mapping ISSU client was unable to calculate the message size for the message specified. The client will be unable to send the message to the standby unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"VLAN_MAPPING_ISSU","3","POLICY","vlan_mapping VLAN Mapping ISSU client message type %d is %s","The VLAN mapping ISSU client received a message type that it does not support. A policy is applied to make the session compatible.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu session commands and your pertinent troubleshooting logs."
"VLAN_MAPPING_ISSU","3","SEND_FAILED","vlan_mapping VLAN Mapping ISSU client failed to send a negotiation message, error %d","The VLAN mapping ISSU client could not send a session negotiation message to the peer. As a result, the standby unit cannot be brought up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show checkpoint client commands and your pertinent troubleshooting logs."
"VLAN_MAPPING_ISSU","3","SESSION","vlan_mapping VLAN Mapping ISSU client %s","The VLAN mapping ISSU client detected an error during a session negotiation with the peer unit. As a result, the standby unit cannot be brought up.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"VLAN_MAPPING_ISSU","3","TRANSFORM","vlan_mapping VLAN Mapping ISSU client %s transform failed, error %s","The VLAN mapping ISSU client could not transform the message. If the transmit transformation failed, the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, the checkpoint message cannot be applied on the standby unit. In either case, the vlan_mapping VLAN Mapping state will not be identical with the active unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"VOA","3","HIGH_ALM_THR","High Alarm Threshold for optical power on port [chars] [chars]","The high alarm threshold for the optical power level has been exceeded.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VOA","3","HIGH_WARN_THR","High Warning Threshold for optical power on port [chars] [chars]","The high warning threshold for the optical power level has been exceeded.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VOA","3","LOW_ALM_THR","Low Alarm Threshold for optical power on port [chars] [chars]","The low alarm threshold for the optical power level has been exceeded.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VOA","3","LOW_WARN_THR","Low Warning Threshold for optical power on port [chars] [chars]","The low warning threshold for the optical power level has been exceeded.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VOICE_FSM","3","UNAVAILABLE","NULL","This message can take many forms. It provides information about a software error.","Copy the error message exactly as it appears, and report it to your technical support representative."
"VOICE_FSM","5","UNAVAILABLE","NULL","Notification message.","LOG_STD_NO_ACTION."
"VOICE_RC","3","UNAVAILABLE","NULL","This message can take many forms. It provides information about a software error.","Copy the error message exactly as it appears, and report it to your technical support representative."
"VPA","1","UNAVAILABLE","%s failed to send report %d at %s - line %d","The port adaptor failed to send a report from vip.","Copy the error message exactly as it appears, and report it to your technical support representative."
"VPA","3","UNAVAILABLE","%s %d/%d got bad VC packet %08x %08x %08x %08x %08x %08x %08x %08x","An interface received a packet with bad VC encapsulation. This indicates either a software or hardware problem.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPA","3","UNAVAILABLE","%s Command Failed at %s - line %d, arg %d","The port adaptor failed to process a command.","Copy the error message exactly as it appears, and report it to your technical support representative."
"VPA","3","UNAVAILABLE","Firmware for VPA in bay %d crashed with exception %#x","The port adaptor firmware has crashed.","Copy the error message exactly as it appears, and report it to your technical support representative."
"VPA","3","UNAVAILABLE","VPA (bay %d), Init Failed at %s - line %d arg %x","The port adaptor failed to complete hardware initialization.","Copy the error message exactly as it appears, and report it to your technical support representative."
"VPA","3","UNAVAILABLE","VPA (bay %d), TDM timeslot is busy: ST=%d/TS=%d","The port adaptor failed to grand a cross connect setup request.","Copy the error message exactly as it appears, and report it to your technical support representative."
"VPA","3","UNAVAILABLE","VPA (bay %d), TDM timeslot is non busy: ST=%d/TS=%d","The port adaptor failed to grand a cross connect teardown request.","Copy the error message exactly as it appears, and report it to your technical support representative."
"VPA","3","UNAVAILABLE","VPA (bay %d), received an unexpected event=%x","The port adaptor received an unexpected event from firmware.","Copy the error message exactly as it appears, and report it to your technical support representative."
"VPA","3","UNAVAILABLE","VPA-TDM, access failed at %s - line %d, arg1=0x%08x,arg2=0x%08x","The port adaptor failed to access TDM switch.","Copy the error message exactly as it appears, and report it to your technical support representative."
"VPA","5","UNAVAILABLE","VPA (bay %d), Voice tx ring is full: dma_done=%d, last_dma_done=%d","The port adaptor's voice tx ring is full.","Copy the error message exactly as it appears, and report it to your technical support representative."
"VPA","6","UNAVAILABLE","Data call is not supported on %s.","Data call is not supported in this version of IOS.","Remove data call configuration/setup."
"VPA","6","UNAVAILABLE","No TDM backplane is supported on slot %d.","Cannot cross connect ds0 inter slot without the TDM backplane.","Copy the error message exactly as it appears, and report it to your technical support representative."
"VPA","6","UNAVAILABLE","VPA (bay %d), Data rx ring refill failed: rxd_fill_fail=%d","The port adaptor failed to refill data rx ring.","Copy the error message exactly as it appears, and report it to your technical support representative."
"VPA","6","UNAVAILABLE","VPA (bay %d), Voice rx ring refill failed: rxv_fill_fail=%d","The port adaptor failed to refill voice rx ring.","Copy the error message exactly as it appears, and report it to your technical support representative."
"VPA","6","UNAVAILABLE","Voice PA is not supported in this platform.","The port adaptor is not supported in this platform.","Copy the error message exactly as it appears, and report it to your technical support representative."
"VPD","1","UNAVAILABLE","An error was encountered during DSP initialization of ATM CES (Voice Processor Deck) port adapter at addr 0x%x.","The port adapter did not successfully initialize. This failure occurred during the DSP initialization of the port adapter.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPD","1","UNAVAILABLE","An error was encountered during initialization of ATM CES (Voice Processor Deck) port adapter in slot %d.","The port adapter did not successfully initialize. This failure occurred during the ATM CES voice processor deck initialization of the port adapter.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPD","1","UNAVAILABLE","VPD in slot %d: VIC daughter card (%s/0x%x) is unsupported","The VIC card plugged into the VPD is not of a supported type","Replace this VIC with a type that is supported by this version of IOS, or change the version of IOS to support this VIC type."
"VPD","1","UNAVAILABLE","VPD in slot %d: VIC daughter card has an unknown id of 0x%x","The software did not recognize the type of VIC card plugged into the VPD.","Check the part number on the VIC card to see if it is supported in the version of IOS operational on the router or contact your technical support representative."
"VPD","4","UNAVAILABLE","ATM CES (Voice Processor Deck) clock %d/0 Tx PLL lost lock! Priority %d %s %s - Tx PLL failed.","The clock source has failed.","If an alternate source is available, it will be used."
"VPD","4","UNAVAILABLE","ATM CES (Voice Processor Deck) clock %d/0 transitioned from Priority %d %s %s to Priority %d %s %s","This warning message indicates a change in the clock source.","No action required."
"VPD","4","UNAVAILABLE","ATM CES (Voice Processor Deck) clock source initialized to local oscillator.","Warning indicates that ATM CES (Voice Processor Deck) clock used will be internal.","No action is required."
"VOICE_RC","5","UNAVAILABLE","NULL","Notification message.","LOG_STD_NO_ACTION"
"VPD","4","CESCLK_INIT","ATM CES (Voice Processor Deck) clock source initialized to local oscillator.","Warning indicates that ATM CES (Voice Processor Deck ) clock used will be internal.","No action is required."
"VPDN","3","DROP_ADDR_MISMATCH","[chars]","The remote server changed its address.","Change initiate-to configuration at the LAC to point to the exact IP address LNS will use."
"VPDN","3","IP_SWITCH_ERR","l2x ip switching vector not installed","The platform-dependent Layer 2X IP Cisco Express Forwarding (CEF) switching module is missing.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPDN","3","NORESOURCE","[chars] [chars] [chars] no resources for user [chars][chars][chars]","The platform (for example, the Cisco Network Authentication Server and L2TP access concentrator (NAS/LAC) or the home gateway and L2TP network server (HGW/LNS)) has exhausted its resources for forwarding a VPDN user.","Check the available memory of the platform."
"VPDN","4","MIDERROR","[chars] [chars] [chars] unable to terminate user [chars][chars][chars]","The HGW/LNS was unable to complete the forwarding of the VPDN user because of an internal error. This condition may be resource-related or configuration-related. A reason string may be present in the message text to indicate the point of failure.","Check the configuration of the HGW/LNS."
"VPDN","4","REFUSED","Session for %s Refused status = %x","The remote server refused this session.","Check the configuration of the home gateway (HGW) or L2TP Network Server (LNS)."
"VPDN","4","SESSIONERROR","[chars] [chars][chars] unable to terminate user [chars][chars][chars]","The HGW/LNS was unable to complete the forwarding of the VPDN user due to an internal error. This error may be resource related or configuration related. A reason string may be present to indicate the point of failure.","Check the configuration on the HGW/LNS"
"VPDN","5","NOIDB","[chars] [chars] [chars] unable to terminate user [chars]","The HGW/LNS has exhausted its resources for creating sessions for VPDN forwarded users. It has reached the maximum number of interfaces allowed on the router.","Limit the number of interfaces to the maximum allowable interfaces."
"VPDN","5","UNREACH","[chars] [chars] [chars] is unreachable","The platform (for example, the Cisco NAS/LAC or the HGW/LNS) has timed out while it was attempting to establish a tunnel connection to a HGW/LNS or NAS/LAC. The timeout may be due to network, authentication, or authorization issues.","Check the configuration on the platform and check the network connectivity between the NAS/LAC and HGW/LNS. Check to see if the tunnel setup requires a different source IP address from that of the NAS/LAC."
"VPDN","6","AUTHENERR","[chars] [chars] [chars] cannot locate a AAA server for [chars] [chars] [chars][chars][chars]","Either the NAS/LAC or the HGW/LNS is unable to locate an AAA server for the purposes of authenticating the user or tunnel. This condition indicates that the router was unable to establish a network connection with the designated or configured server. A reason string may be present in the message text to provide further information.","Check the AAA configuration on the platform (for example, the Cisco NAS/LAC or the HGW/LNS) and check the network connectivity to the AAA servers."
"VPDN","6","AUTHENFAIL","[chars] [chars] [chars], [atalk_address]uthentication failure [chars]for [chars] [chars] [chars][chars][chars]","The platform (for example, the Cisco NAS/LAC or the HGW/LNS) has failed to authenticate a user or a tunnel, or the HGW/LNS has failed authentication with the client that initiated the session. For authentication failures of the user or tunnel, a reason string should be present in the message text to indicate the point of failure. When a client fails to authenticate the HGW, a reason string may be present, depending upon the point of failure.","Check the username configuration on the platform and, possibly, the client. If the HGW/LNS is failing authentication, removing the negotiation of outbound authentication (that is, authenticating the user only in the inbound direction) is one possible solution. If AAA is applicable to the condition, check the AAA configuration on the NAS/LAC or HGW/LNS and check the network connectivity to the AAA servers."
"VPDN","6","AUTHORERR","[chars] [chars] [chars] cannot locate a AAA server for [chars] [chars] [chars][chars][chars]","The platform (for example, the Cisco NAS/LAC or the HGW/LNS) is unable to locate a AAA server for the purposes of authorizing the user or tunnel. The router was unable to establish a network connection with the designated or configured server. A reason string may be present in the message text to provide further information.","Check the AAA configuration on the platform and check the network connectivity to the AAA servers."
"VPDN","6","AUTHORFAIL","[chars] [chars] [chars], [atalk_address]uthorization failure for [chars] [chars] [chars][chars][chars]","The platform (for example, the Cisco NAS/LAC or the HGW/LNS) has failed to authorize a user or a tunnel. A reason string may be present in the message text to indicate the point of failure.","Check the authorization configuration on the platform. If AAA is applicable to the condition, check the network connectivity to the AAA servers."
"VPDN","6","CLOSED","[chars] [chars] [chars] closed [chars] [chars] [chars][chars][chars]","The remote server, typically the HGW/LNS, closed this session. The reason for the closing is encoded in a hexadecimal format and corresponds to the particular protocol descriptions. For the L2F protocol, the values are documented in section 4.4.5 of the Internet Draft. A description string may also be present that describes the reason for the closing.","Check the configuration on the platform (for example, the configuration of the Cisco NAS/LAC or the HGW/LNS)."
"VPDN","6","DOWN","%s %s %s changed state to down %s %s %s%s%s","The remote server, typically the home gateway (HGW) and L2TP Network Server (LNS), closed this tunnel. The reason for the closure is encoded in a decimal format defined in the particular protocol specification. For example, the closure values for Layer 2 Forwarding (L2F) are documented in section 4.4.5 of the L2F Internet Draft. The closure reason may also be displayed in a description string.","Check the configuration on the network access server (NAS) and L2TP access concentrator (LAC) , or on the home gateway (HGW) and L2TP Network Server (LNS)."
"VPDN","6","MAX_SESS_EXCD","%s %s %s has exceeded configured local session-limit and rejected %s %s %s%s%s","The NAS/LAC or HGW/LNS has refused this session since the configured maximum VPDN session limit has been reached.","No action is required."
"VPDN","6","RESIZE","Updated [chars] session table size to [int]","The platform (for example, the Cisco NAS/LAC or the HGW/LNS) has altered the size of the session table using the CLI.","No action is required."
"VPDN","6","SOFTSHUT","%s %s %s has turned on softshut and rejected %s %s %s%s%s","The NAS/LAC or HGW/LNS can no longer accept new connections when the vpdn softshut command has been entered. Existing sessions will continue until termination.","To allow new connections, enter the no vpdn softshut command. Otherwise, no action is required."
"VPDN","6","TIMEOUT","[chars] [chars] [chars] disconnected [chars] [chars] [chars][chars][chars]","The platform (for example, the Cisco NAS/LAC or the HGW/LNS) has disconnected the user because of the expiration of a timer. This condition may be PPP negotiation-related or might be an absolute timeout for the session.","If the session has timed out automatically, no action is required."
"VPDN","6","VPDN_DEADCACHE_EVENT","LSG dead cache entry [IP_address] [chars]","A dead cache entry status is changed in the VPDN Load Sharing Group (LSG) table. The event could be 'Added', where a LSG entry goes Down, 'Deleted', where an entry moves out of the Down status, or 'Cleared', where an entry is cleared by a user.VPLS_NP_CLIENT MessagesThis section contains VPLS NP client messages.VPLS_NP_CLIENT-3Error Message    %VPLS_NP_CLIENT-3-INFO: [chars] Explanation    The VPLS NP client failed to initialize properly. This condition will result in improper operation of the any transport over MPLS (AToM) feature.","Reload the Cisco IOS image on the affected card or platform. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPLS_NP_CLIENT","3","NOMEM","[chars]","The VPLS NP client failed to initialize properly. This condition will result in improper operation of the AToM feature. This error may indicate that more memory must be installed on the affected card or platform in order to service all the features and related entities enabled by the configuration.","Reload the Cisco IOS image on the affected card or platform. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPLS_NP_CLIENT","4","WARN","[chars] [dec] [chars]","The entry could not be added because it is invalid.","Reload the Cisco IOS image on the affected card or platform. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPN_HW","0","SELF_TEST_FAILURE","Hardware Crypto self-test failed ([chars])","One of the hardware crypto self-tests has failed. The crypto engine is not operable in this state.","If the failure persists, contact Cisco to replace the hardware."
"VPN_HW","1","ALIGN","Slot: [dec] - Alignment failure on packet buffer: [hex]","A software error has occurred. The VPN hardware accelerator driver has detected that the buffer is not aligned correctly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPN_HW","1","ERROR","slot: [dec] - [chars]","An error occurred in the application that was using the VPN hardware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPN_HW","1","HEARTBEAT","VPN Module in slot: [dec]: Keepalive lost.","Keepalive messages have been lost, which indicates that the VPN hardware accelerator is no longer operating.","Reboot your router. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPN_HW","1","INITFAIL","Slot [dec]: [chars]","The VPN hardware accelerator driver could not initialize the accelerator at the slot specified in the error message at the specified point.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPN_HW","1","NOMEMORY","[chars] creation failed for slot [dec]","During its initialization phase, the VPN hardware driver could not allocate memory for the data structure that is specified in the error message.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPN_HW","1","OWNER","slot: [dec]: [chars] packet buffer, pak=[hex]","A software or hardware error has occurred. The VPN hardware accelerator driver has detected that the buffer ring is in an inconsistent and unrecoverable state.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPN_HW","1","PACKET_ERROR","slot: [dec] Packet Encryption/Decryption error, [chars]","An unexpected error occurred during the encryption or decryption of a packet.","This message can occur occasionally during normal operation of the system. It may occur during the transition to a new session key for a security association. In such cases, no action is required. However, if it happens frequently, or is associated with traffic disruption, then note the status value and contact your Cisco technical support representative. The VPN hardware accelerator will most likely need to be replaced."
"VPN_HW","1","TOOBIG","Slot: [dec] - [chars] received a packet with size [dec].","A packet was received that was too large. The hardware supports only the MTU size specified in the message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPN_HW","1","PACKET_ERROR","slot: %d Packet Encryption/Decryption error, %s","An unexpected error occurred during the encryption or decryption of a packet.","This message can occur occasionally during normal operation of the system. It may occur during the transition to a new session key for a Security Association. In such cases, no action is required. However, if it happens frequently, or is associated with traffic disruption, then note of the status value and contact a Cisco representative. The VPN hardware accelerator will most likely need to be replaced."
"VPN_HW","1","UNSUPP","VPN Module in slot: [dec]: [chars] ([hex]).","This revision or version of the VPN hardware accelerator in the slot specified in the error message is not supported.","Verify that the VPN hardware adapter is the proper hardware level and software revision for the running version of the Cisco IOS software. If it is, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPN_HW","3","MULTDEV","Cannot support more than one Encryption AIM","A second Encryption AIM was discovered present in the system. The Encryption AIM software only supports a single Encryption AIM. All other Encryption AIMs installed will be ignored.","Remove one of the Encryption AIMs that are installed in your system."
"VPN_HW","4","PACKET_ERROR","slot: [dec] Packet Encryption/Decryption error, [chars]","An unexpected error occurred during the encryption or decryption of a packet.","This message can occur occasionally during normal operation of the system. "
"VPN_HW","6","FIPSFAIL","FIPS test_id [dec]([chars]) Test Failure will be induced","The FIPS test was forced to fail from ROMMON.","If this condition is undesirable, do not set FIPS_FAIL using ROMMON."
"VPN_HW","6","INFO","slot: [dec] [chars]","This is an informational message from the VPN hardware accelerator driver.","No action is required."
"VPN_HW","6","INFO_LOC","Crypto engine: [chars] [chars]","This is an informational message from the VPN hardware accelerator driver.","No action is required."
"VPN_HW","6","SHUTDOWN","[chars] shutting down","The specified VPN hardware is shutting down. It may have been physically removed.","This is an informational message only. No action is required."
"VQPCLIENT","2","UNAVAILABLE","Could not allocate memory for VQP","An error occurred when the system tried to allocate memory for the VQP client.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VQPCLIENT","2","UNAVAILABLE","Could not create process for VQP. Quitting","An error occurred while creating a process for the VQP client.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VQPCLIENT","2","UNAVAILABLE","Could not obtain IP socket","An error occurred when the system attempted to open an IP socket to the VMPS.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VQPCLIENT","2","UNAVAILABLE","Host %e denied on interface %s","The VMPS has denied access for the given host MAC address to the specified interface.","No action is normally required. If you feel that the host should have been allowed access, then the configuration on the VMPS should be checked."
"VQPCLIENT","2","UNAVAILABLE","Interface %s shutdown by VMPS","The VMPS has directed that the specified interface be shut down.","No action is normally required. If you feel that the port should not have been shut down, then the configuration on the VMPS should be checked."
"VQPCLIENT","2","UNAVAILABLE","Interface %s shutdown by active host limit","The system has shut down the specified interface because too many hosts have requested access to that port.","To reactivate the port, remove the excess hosts and issue a no shut command to the interface."
"VQPCLIENT","2","UNAVAILABLE","Platform-specific VQP initialization failed. Quitting","An error occurred during initialization of the VQPC platform-specific code.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VQPCLIENT","3","UNAVAILABLE","Invalid VLAN (%s) in response","The VMPS has specified a vlan name that is unknown to the switch.","Make sure that the vlan exists on the switch. Check the VMPS configuration."
"VQPCLIENT","3","UNAVAILABLE","Invalid interface (%s) in response","The VMPS has sent an unsolicited response with an unknown interface name","Check the VMPS configuration."
"VQPCLIENT","3","UNAVAILABLE","Throttling VLAN change on %s","An attempt was made to change the vlan assignment for the specified interface more often than once every 10 seconds. The vlan change is denied.","No action is normally required. If the message recurs, check the VMPS configuration. Verify that unexpected hosts are not connected to the port."
"VQPCLIENT","7","UNAVAILABLE","Probing primary server %I","The system is trying to reestablish connectivity with the primary VMPS at the given IP address.","LOG_STD_DBG_ACTION"
"VQPCLIENT","7","UNAVAILABLE","Reconfirming VMPS responses","The switch is reconfirming all responses with the VMPS","LOG_STD_DBG_ACTION"
"VQPCLIENT","7","UNAVAILABLE","Trying next VMPS %I","The system has lost connectivity with the current VMPS and is switching to the next server in its list.","LOG_STD_DBG_ACTION"
"VPNMAP","2","REALLOC_ERROR","Exceeded number of resources to support hardware switching of VRF %s. Please unconfigure some of the existing VRFs as some entries will be software switched in the next reload.","Because no further hardware resources are available to support hardware switching of VRFs, some VRFs must be software switched. Unconfigure the mls ipv6 vrf command or some of the existing features that use those resources. Examples of features using hardware switching resources are VRF, EoMPLS, and MDT.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, remote command module, show platform software vpn mapping, show platform software vpn status, and show running-config commands and your pertinent troubleshooting logs."
"VPNMAP","2","SPACE_EXCEEDED","Exceeded number of resources to support hardware switching of VRFs. Please unconfigure some of the existing VRFs as some entries will be software switched.","Because no further hardware resources are available to support hardware switching of VRFs, some VRFs must be software switched. Unconfigure the mls ipv6 vrf command or some of the existing features that use those resources. Examples of features using hardware switching resources are VRF, EoMPLS, and MDT.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, remote command module, show platform software vpn mapping, show platform software vpn status, and show running-config commands and your pertinent troubleshooting logs."
"VPNSM","2","ACE_PKA_KAT_FAILURE","PKA: Known Answer Test failure: [chars]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","2","ACESCPERROR","Null MAC address pointer in SCP module","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI0BADPARAM","PcpManCreateTunn: cannot create tunnel with expiring Sa","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI0TCAMFAILED","SpdSpInstall: cannot install Sp [dec]: TmInsertSp failed","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI1BADPARAM","SpdSpInstall: cannot install generic SP [dec] with non-zero priority","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI1OUTOFSA","PcpQOpCreSaBegin: cannot create new Sa using SpdMan","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI10OUTOFCME","PcpManCreateAcl: cannot allocate new Acl for aclId=[int]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI11NESTOVERFLOW","SpdSaAddTmInsCb: cannot have more than [dec] pending nested callbacks from TcamMan","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI11OUTOFSEL","PcpAclGetSpSelSet: cannot clone SelSet for ACL [dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI2BADPARAM","PcpManUpdateFlow: cannot update flow [dec] with invalid ID","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI12IDNOTINUSE","PcpManRemoveAcl: cannot remove non-existing access list [int]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI12OUTOFSAPAR","SpdSaSetKeys: cannot allocate new SaPar for Sa [dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI13IDINUSE","PcpManRemoveAcl: cannot remove access list [int] while in use","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI3OUTOFSEL","PcpQOpActSaBegin: cannot allocate selector set for outer Sa in flowId [dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI14BADCMEID","PcpSpdCreateCme: cannot create Cme with ID=[dec]: too large","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI14NOLOGA","SpdSaSetParams: cannot allocate SPI with TcamMan for Sa [dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI15IDNOTINUSE","PcpManRemoveCme: cannot remove non-existing Cme [int]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI16BADPARAM","PcpManActivateFlowAsync: cannot activate flow [dec]: Sa is in the wrong state","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI16TCAMFAILED","SpdSaTmInstallIn: cannot install inbound Sa [dec] with TcamMan","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI17BADPARAM","PcpManActivateFlowAsync: cannot activate non-existing flow [dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI17TCAMFAILED","SpdSaTmInstallOut: cannot install outbound Sa [dec] with TcamMan","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI18BADPARAM","PcpManCreateSMap: cannot create outbound SPD Map [int] with ingress access list [int]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI19BADCMEID","PcpManActivateFlowAsync: cannot activate flow [dec] with non-existing Cme [dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI2BADPARAM","PcpManUpdateFlow: cannot update flow [dec] with invalid ID","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI2NESTOVERFLOW","SpdSaInitTmSaOut: outer outbound Sa [dec] of Sa [dec] is above nesting limit of [dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI20OUTOFSEL","PcpUtilSelSetFromPar: cannot allocate new selector set","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI21BADPARAM","PcpAclAppend: got too many denys for aclId=[dec], max is [dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI22BADPARAM","PcpAclAppend: got out-of-sequence line number [dec] for aclId=[dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI23IDINUSE","PcpSpdCreateCme: cannot create Cme with ID=[int]: already used","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI24BADPARAM","PcpAclAppend: got invalid ranges for selector set at lineNo=[dec], aclId=[dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI25IDINUSE","PcpAclAppend: got duplicate line number [dec] for aclId=[dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI26OUTOFSP","PcpCmeInstallNext: cannot create a new Sp","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI27BADPARAM","PcpManSetFlowKeys: cannot set keys for flow [dec]: SA is in the wrong state","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI28IDINUSE","PcpQOpCreSaBegin: cannot create second Sa for flow [dec]: conditions for transport adj. are not met","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI29SPDFAILED","PcpCmeInstallNext: cannot install Sp [dec] with SpdMan","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI3NESTOVERFLOW","SpdSaGetXformSeq: outer inbound Sa [dec] of Sa [dec] is above nesting limit of [dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI3OUTOFSEL","PcpQOpActSaBegin: cannot allocate selector set for outer Sa in flowId [dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI30BADPARAM","PcpSpdUpdateCme: cannot update already queued Cme [int]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI31BADALENUM","PcpQOpActSaBegin: cannot find access list entry number [dec] for cmeId=[dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI32BADPARAM","PcpQOpActSaBegin: cannot delete old [chars]bound flow [dec] while activating [chars]bound flow [dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI33BADPARAM","PcpCmeActivateSa: got invalid lifetime values softSecs=[int], hardSecs=[int]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI34BADPARAM","PcpCmeActivateSa: got invalid lifetime values softKBytes=[int], hardKBytes=[int]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI35BADPARAM","PcpCmeIntersectSaWithSp: cannot activate flow [dec] with selector ranges not intersecting parent Sp","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI36BADSELADDR","PcpQOpActSaBegin: cannot activate per-host flow [dec] with addresses [dec].[dec].[dec].[dec] and [dec].[dec].[dec].[dec] not included in Sp [dec] selector sets","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI37OUTOFSEL","PcpQOpActSaBegin: cannot clone selector set to activate per-host flow [dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI38BADSELADDR","PcpQOpActSaBegin: cannot activate transport mode flow [dec] with addresses [dec].[dec].[dec].[dec] and [dec].[dec].[dec].[dec] not included in Sp's selector sets","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI39BADPARAM","PcpTrInProcess: got invalid opcode [dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI4BADPARAM","PcpQOpCreSaBegin: got invalid addresses [int].[int].[int].[int] and [int].[int].[int].[int] for other Sa of flow [dec]: expected [int].[int].[int].[int] and [int].[int].[int].[int]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI40BADACLID","PcpManCreateCme: cannot create Cme with non-existing access list [int]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI41SPDFAILED","PcpQOpSaActivated: cannot finish activating Sa [dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI42QUEUEFULL","PcpCmeActivateSa: cannot activate Sa [dec]: queue is full","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI43BADPARAM","PcpAclAppend: got invalid line number [dec] for ACL [dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI44QUEUEFULL","PcpSpdCreateCme: cannot create Cme [int] (aclId=[int]): queue is full","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI45IDNOTINUSE","PcpManDestroyFlowAsync: cannot delete already deleted flow [dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI46BADPARAM","PcpQOpActSaBegin: cannot activate non-fully-specified Sa for Cme [dec] without Acl","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI47BADPARAM","PcpQOpActSaBegin: cannot activate Sa for manual Sp (cmeId=[dec],entry=[dec]), Sa already exists","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI48CMEINUSE","PcpManSetInitMode: cannot set fast init-mode in TcamMan: [dec] pending Ops, [dec] Flows and [int] Cmes already exist or TcamMan is busy","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI49BADPARAM","PcpManQueryFlow: cannot query flow [dec]: Sa is not active","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI5BADPARAM","SpdSaActivate: cannot activate Sa [dec], old Sa [dec] already has successor Sa [dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI5OUTOFSA","PcpQOpCreSaBegin: cannot create new Sa for flow [dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI50CMEINUSE","PcpQOpRemCmeBegin: cannot remove Cme [dec]: TcamMan is in Init mode","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI51BADPARAM","PcpSpdCreateCme: got invalid flags (manual,dynamic,discover,drop,clear) = ([dec],[dec],[dec],[dec],[dec]), cmeId=[dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI52IDINUSE","PcpManCreateAcl: cannot process opcode [int] for Acl [int] in state [int]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI53BADPARAM","PcpManCreateAcl: cannot create Acl with id [int] out of range [0,[int]]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI54CMENOTREADY","PcpSpdCreateCme: cannot create Cme [int] with Acl [int] when Acl state is [int]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI55SPDFAILED","PcpQOpActSaBegin: cannot begin activating Sa [dec] for flowId [dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI56IDNOTINUSE","PcpManDestroyFlowAsync: cannot delete flow [dec] already being deleted","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI57CMEINUSE","PcpManSetInitMode: cannot set normal init-mode in TcamMan: there are pending Flows or Cmes","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI58IDNOTINUSE","PcpManDestroyFlowAsync: flow [dec] already queued for deletion","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI59BADPARAM","PcpCmeActivateSa: cannot activate flow [dec] as per-host with subset of Sp as a selector set","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI6BADPARAM","PcpTrInProcess: got invalid size [dec] for opcode [dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI6OUTOFSEL","SpdSpInstall: cannot compute SP's permit-SelSets from mixed SelSet list","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI60SPDFAILED","PcpManSaUpdateError: cannot update Flow [dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI61BADPARAM","PcpQOpActSaBegin: cannot activate Sa for cmeId=[dec], entry=[dec] with bad spdId=[dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI62IDINUSE","PcpQOpCreSaBegin: cannot setup Flow [dec] in trans.adj. with outer SA in tunnel mode","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI63CMEINUSE","PcpManActivateFlowAsync: cannot activate flow [dec] while using fast policy mode","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI64BADPARAM","PcpQOpActSaBegin: got invalid ranges for selector set of fully-specified flow [dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI65BADPARAM","PcpManSetInitMode: got invalid flags [hex] for setting fast policy mode","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI66NOTREADY","PcpManUpdateFlow: cannot update flow [dec] when SA is not active","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI67BADPARAM","PcpSpdCreateSMap: cannot create SMap [int] with Acl [int] when Acl state is [int]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI68BADPARAM","PcpAclAppend: got invalid flags [hex] at lineNo=[dec], aclId=[dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI69BADPARAM","PcpManCreateCme: cannot create Cme [int] with spdId [int] out of range [0,[int]]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI7BADPARAM","PcpManSetFlowKeys: cannot set keys for flow [dec]: invalid ID","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI7OUTOFSEL","SpdSaTmInstallOut: cannot compute outbound SA's permit-SelSets from mixed SelSet list","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI70IDNOTINUSE","PcpManUpdateCme: cannot update non-existing Cme [int]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI71QUEUEFULL","PcpSpdUpdateCme: cannot update Cme [int]: queue is full","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI72QUEUEFULL","PcpSpdCreateSMap: cannot create SPD map with mapId [int]: queue is full","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI73BADPARAM","PcpSpdCreateSMap: cannot create SPD map with mapId [int] out of range [0,[int]]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI74IDINUSE","PcpSpdCreateSMap: cannot create SPD map with mapId [int] already in use","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI75TMFAILED","PcpSMapInstall: cannot insert SMap [int] with TcamMan","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI76BADPARAM","PcpSpdCreateSMap: cannot create SPD map [int] with invalid flags [hex]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI77BADPARAM","PcpManCreateSMap: cannot create SPD Map [int] using non-existent access list [int]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI78OUTOFSMAP","PcpSpdCreateSMap: cannot create SPD map [int]: out of memory","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI79BADPARAM","PcpQOpActSaBegin: cannot activate Sa for cmeId=[dec], entry=[dec] when Cme is not ready","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI80QUEUEFULL","PcpManDestroyFlowAsync: cannot delete flowId [dec]: operation queue is full","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI81IDNOTINUSE","PcpQOpDelSaBegin: cannot delete already deleted flow [dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI82QUEUEFULL","PcpManRemoveCme: cannot remove Cme with cmeId [int]: queue is full","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI83TMFAILED","PcpSpdInitialize: cannot insert SPD [int] with TcamMan","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI84BADPARAM","PcpManCreateSMap: cannot create SPD map [int] with spdId [int] out of range [0,[int]]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI85OUTOFSMAP","PcpManCreateSpd: cannot create SPD [int]: out of memory","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI86IDINUSE","PcpManActivateFlowAsync: cannot activate already active flow [dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI87BADPARAM","PcpManCreateFlow: cannot create Flow with id=[dec], max is [dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI88IDNOTINUSE","PcpManRemoveSMap: cannot remove non-existing SMap [int]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI89OUTOFCME","PcpSpdCreateCme: cannot allocate new Cme for aclId=[int]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ACEI92QUEUEFULL","PcpManCreateFlow: cannot create flowId [dec]: operation queue is full","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","ICPUBADGRESA","Invalid GRE SA - can't find match. saptr:[hex]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","3","SPI_NOT_AVAIL","SPI [hex] is not available","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","ACETCAMFULLINSMANSP","Full SA insertion for a manual SP.","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","ACETCAMPKTNOSA","Packet event for a non-existing SA.","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","ACETCAMPKTNOSP","Packet event for a non-existing SP.","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","ACEXCPUALLOC","IPC: Unable to allocate and send STATFLUSH.","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","ACEXCPUALLOC2","IPC: Unable to allocate IPC to set debug flag.","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","ACEXCPUALLOC3","IPC: Unable to allocate IPC to start 5840 test.","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","ACEXCPUCMMTU2","CFGMON: Failed to set MTU. Invalid data [dec], ifvlan [hex].","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","ACEXCPUCMRESP","XcpuCfgMonReqCallback:Can't respond to host.","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","ACEXCPUCMRESP3","XcpuCfgMonReqCallback:Global stats...Can't respond to host.","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","ACEXCPUCMRESP4","XcpuCfgMonReqCallback: PerFlow Stats....Can't respond to host.","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","ACEXCPUCMRESP5","XcpuCfgMonReqCallback: PerFlow Stats....Can't respond to host.","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","DUMPMEM","[hex]: [hex] [hex] [hex] [hex]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","EDSDEBUG","SingleBufErr:([hex])","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","FIPSCHECK2","FIPS RCVD Multi-buffer Packet.","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","FIPSCHECK3","FIPS Failed Packet Comparison.","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","FIPSCHECK4","FIPS Test Completed Successfully.","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","ICPUFRAG1","PktReasmSetAction failed.","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","ICPUPP2","SaCheckSelectors: Illegal pkt, no valid SA","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","ICPUPP3","Illegal pkt dst:[dec].[dec].[dec].[dec] proto:[dec] spi:[hex], no match on SA SPI [hex].","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","ICPUPP4","Illegal pkt dst:[dec].[dec].[dec].[dec] proto:[dec] spi:[hex], no match on SA dst[dec].[dec].[dec].[dec]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","ICPUPP8","Illegal clear pkt src:[dec].[dec].[dec].[dec] dst:[dec].[dec].[dec].[dec] proto:[dec].","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","ICPUPP9","Packet src:[dec].[dec].[dec].[dec] dst:[dec].[dec].[dec].[dec] seq num:[hex] failed replay check last seq num:[hex] for SA:[hex].","IPsec packets have failed the anti-replay check. A common cause is the use of QoS in your network. With QoS, lower priority packets can arrive late, missing the anti-replay check window. When this condition occurs, higher level protocols can request retransmission so that functionality is not lost. Time-sensitive protocols, such as voice traffic, might be degraded due to dropped or late packets.","If anti-replay checking is not needed, disable it by removing the HMAC function from the transform set."
"VPNSM","4","ICPUPP10","Packet src:[dec].[dec].[dec].[dec] dst:[dec].[dec].[dec].[dec] proto ESP, but not SA proto!","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","ICPUPP11","Packet src:[dec].[dec].[dec].[dec] dst:[dec].[dec].[dec].[dec] proto AH, but not SA proto!","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","ICPUPP12","IPPE says IPSec, not pkt src:[dec].[dec].[dec].[dec] dst:[dec].[dec].[dec].[dec] proto:[dec]!","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","ICPUPP13","Policy check failed for pkt src:[dec].[dec].[dec].[dec] dst:[dec].[dec].[dec].[dec] proto:[dec] SA index:[hex]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","ICPUPP14","Pkt src:[dec].[dec].[dec].[dec] dst:[dec].[dec].[dec].[dec] proto:[dec] match deny; SA index [hex]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","ICPUPP15","SecInfo [hex] doesn't match with SA [hex] SA index:[hex]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","ICPUPP16","Inner proto [dec] must be IPSec but is not","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","ICPUSYSIPADDRADD","PktProcAddSysIpAddr: Unable to add local IP Addr [hex]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","ICPUSYSIPADDRDEL","PktProcAddSysIpAddr: Unable to delete local IP Addr [hex]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","ISAUNCA7","PktProcAtnModSas: Mismatch valid flag unca:invalid index:[hex]","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","RECOVERYDONE","CP Lockup Recovery - Done","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","RECOVERYFRAG","Ipfrag: Unable to transmit. CP Lockup Occured.","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","RECOVERYSTART","CP Lockup Recovery - Start(OCPU)","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","4","XCPURECOVERY","Error Disabling CP","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","6","ACEPKAHWCRNGT","PKA: HW RNG has duplicate data, discarding","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","6","ACEPKARNGDUP","PKA: A pseudo-random number was generated twice in succession. [hex][hex]; 0Unrecognized format `x%p' 0Unrecognized format `x%p' idx:[hex]","An error has been reported by the firmware","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSM","6","ACEPKARNGKAT","PKA: RNG failed KAT","An error has been reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSMIOS","3","ILLEGALINTERFACE","Traffic matching crypto maps on [chars] will go through unencrypted. Please reconfigure crypto maps as required by VPN service module.","An attempt was made to apply an encryption (crypto) map set to an interface that is not a VLAN interface. When this IPsec VPN accelerator is being used, crypto map sets can only be applied to a VLAN interface that has a proper encryption (crypto) connection to a physical port. The interface has been disabled. For more information on crypto guidelines, consult the system configuration manuals.","Remove the crypto map set from the virtual interface. For more details, consult the configuration guidelines."
"VPNSMIOS","3","MACEDONCTVLALLOCFAIL","Failed to allocate Control vlan on stby","An internal error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSMIOS","3","MACEDONCTVLTIMERON","Control vlan timer is on on stby","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSMIOS","3","MACEDONNOCCONB2BERR","[chars]no crypto connect is disallowed","The system cannot remove the cryptographic connection when a module-to-module partner is still active.","Remove the module-to-module configuration before removing the cryptographic connection."
"VPNSMIOS","3","MACEDONTUNNELADDCBERR","[chars]: tunnel addcb failed: reason[[chars]] tvlan[[dec]] slot[[chars]]","An error response was received when attempting to seize the tunnel. In a virtual switch system (VSS), slot [[chars]] indicates switch/slot/subslot; otherwise it indicates slot/subslot.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSMIOS","3","MACEDONTUNNELADDERR","[chars]: tunnel add failed: reason[[chars]] ifvlan[[dec]] tvlan[[dec]] slot[[chars]] src[[IP_address]] dst[[IP_address]]","An attempt to seize the tunnel has failed. In a virtual switch system (VSS), slot [[chars]] indicates switch/slot/subslot; otherwise it indicates slot/subslot.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSMIOS","3","MACEDONTUNNELCREATEPOLOQERR","Failed to create PoloReplicateCfg Q","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSMIOS","3","MACEDONTUNNELCREATEPROCERR","Failed to create Ace Tunnel Task","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSMIOS","3","MACEDONTUNNELCREATEQERR","Failed to create watched Q","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSMIOS","3","MACEDONTUNNELCREATETIDERR","Failed to create Ace Tunnel-id bitvector","An internal error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSMIOS","3","MACEDONTUNNELDELETEIFVLANNOTFOUNDERR","[chars]: no tm found while attempting to delete from ifvlan[[dec]]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSMIOS","3","MACEDONTUNNELDELETETMNOTFOUNDERR","[chars]: no tm found while attempting to delete","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSMIOS","3","MACEDONTUNNELNOEVENTMSGHANDLERERR","msgtype[[chars]]: No event msg handler found.","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSMIOS","3","MACEDONTUNNELNOIDBERR","No tunnel idb","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSMIOS","3","MACEDONTUNNELNOTMMSGHANDLERERR","msgtype[[chars]]: No tm msg handler found.","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSMIOS","3","MACEDONTUNNELREMOVECBERR","[chars]: tunnel removecb failed: reason[[chars]] tvlan[[dec]] slot[[chars]]","An error response was received when attempting to release the tunnel. In a virtual switch system (VSS), slot [[chars]] indicates switch/slot/subslot; otherwise it indicates slot/subslot.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSMIOS","3","MACEDONTUNNELREMOVEERR","[chars]: tunnel remove failed: reason[[chars]] ifvlan[[dec]] tvlan[[dec]] slot[[chars]] src[[IP_address]] dst[[IP_address]] id[[dec]]","An attempt to release the tunnel has failed. In a virtual switch system (VSS), slot [[chars]] indicates switch/slot/subslot; otherwise it indicates slot/subslot.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSMIOS","3","MACEDONTUNNELVACLERR","vlan[[dec]]: failed to set vacl: action[[dec]] reason[[dec]]","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSMIOS","3","MACEDONTUNNELVLANERR","[chars]: allocated idb has invalid vlan id","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSMIOS","3","MACEDONTUNNELVLANIDBERR","[chars]: unable to allocate idb","An internal error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSMIOS","3","SLOTMISMATCH","[chars] has mismatch crypto engine binding. Egress interface is binded to crypto engine [int]/[int] but tunnel protection is binded to [int]/[int]. This tunnel is now shutdown.","To use VPN-SM for tunnel protection, the user must enter the crypto engine slot slot command on both the egress interface VLAN and the tunnel interface. The slot on both interfaces must match. When this requirement is not met, this message is displayed. The tunnel is now shut down.","Modify either one or both crypto engine slot values so that they match."
"VPNSMIOS","3","VLANALLOCFAIL","Failed to allocate vlan for %s","The system was unable to allocate a VLAN for internal use.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show platform hardware capacity vlan, and show vlan internal usage commands and your pertinent troubleshooting logs."
"VPNSMIOS","4","DIFFCRYPTOENGINE","[chars]. Another interface [chars] has same local-address [chars] but is on a different crypto engine [chars]","Two crypto interfaces with the same local address must be on the same crypto engine. In a virtual switch system (VSS), crypto engine [chars] indicates switch/slot/subslot; otherwise it indicates slot/subslot.","Reconfigure the crypto engine command on the interface."
"VPNSMIOS","4","LIMITFVRF","System has reached the limit of supported front-door VRF. ([dec])","The number of front-door VRFs supported by VPNSM has reached its limit.","Unconfigure any unused VRFs."
"VPNSMIOS","4","PROMISCOUSMODE","Outside port failed to be in [chars] mode","This message is relevant only if the outside port is an FEPA port.","Reconfigure the crypto connect command."
"VPNSMIOS","4","VPNSMILLEGALQOS0","VPNSM Slot: [dec] can only support [dec] cos maps in high priority queue, CoS configuration ignored, reset cos map by issuing no priority queue cos-map 1 command","An illegal configuration has been detected.","Reset the CoS map by entering the no priority-queue cos-map 1 command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSMIOSSP","6","MACEDONPOWEROFF","Non crypto image detected, disallowing power to VPN-SM module in slot [chars].","The chassis was booted up with an image that does not have the necessary crypto subsystems for the VPN-SM to run correctly. In a virtual switch system (VSS), slot [[chars]] indicates switch/slot/subslot; otherwise it indicates slot/subslot.","Contact your Cisco technical support representative to obtain the correct image. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","0","ACELOGTEST7","Log test: SEV_EMERG","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","1","ACELOGTEST6","Log test: SEV_ALERT","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","2","ACEIKEADRVPKRM","Decode of RSA Private Key %d failed","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","2","ACEIKEANVRWRT","RSA Private Key %d NOT written to NVRAM","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","2","ACEIKEANVWRT","RSA Private Key %d NOT zeroized in NVRAM","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","2","ACEIKEANVWRT2","RSA Private Key %d NOT written to NVRAM","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","2","ACEIKEAPRVCREDRV","Driver refused RSA Private Key","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","2","ACEIKEAPRVCRESES","Driver refused RSA Private Key %d","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","2","ACEIKEAPRVDRV","Driver refused RSA Private Key","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","2","ACEIKEAPRVNVRD","RSA Private Key %d NOT read from NVRAM","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","2","ACEIKEAPRVREJ","RSA Private Key %d NOT written to NVRAM","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","2","ACEIKEAPRVRMDRV","Decode of RSA Private Key %d failed","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","2","ACEIKEAPRVRMSESDRV","Decode of RSA Private Key %d failed","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","2","ACELOGTEST5","Log test: SEV_CRIT","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","2","ACENVRAMCSUM","NVRAM Checksum failed","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","2","ACENVRAMWR","Write to nvram failed","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","2","ACE_PKA_KAT_FAILURE","PKA: Known Answer Test failure: %s","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI0BADPARAM","PcpManCreateTunn: cannot create tunnel with expiring Sa","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI0TCAMFAILED","SpdSpInstall: cannot install Sp %ld: TmInsertSp failed","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI10OUTOFCME","PcpManCreateAcl: cannot allocate new Acl for aclId=%u","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI11NESTOVERFLOW","SpdSaAddTmInsCb: cannot have more than %ld pending nested callbacks from TcamMan","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI11OUTOFSEL","PcpAclGetSpSelSet: cannot clone SelSet for ACL %d","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI12IDNOTINUSE","PcpManRemoveAcl: cannot remove non-existing access list %u","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI12OUTOFSAPAR","SpdSaSetKeys: cannot allocate new SaPar for Sa %ld","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI13IDINUSE","PcpManRemoveAcl: cannot remove access list %u while in use","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI14BADCMEID","PcpSpdCreateCme: cannot create Cme with ID=%ld: too large","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI14NOLOGA","SpdSaSetParams: cannot allocate SPI with TcamMan for Sa %ld","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI15IDNOTINUSE","PcpManRemoveCme: cannot remove non-existing Cme %u","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI16BADPARAM","PcpManActivateFlowAsync: cannot activate flow %ld: Sa is in the wrong state","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI16TCAMFAILED","SpdSaTmInstallIn: cannot install inbound Sa %ld with TcamMan","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI17BADPARAM","PcpManActivateFlowAsync: cannot activate non-existing flow %ld","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI17TCAMFAILED","SpdSaTmInstallOut: cannot install outbound Sa %ld with TcamMan","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI18BADPARAM","PcpManCreateSMap: cannot create outbound SPD Map %u with ingress access list %u","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI19BADCMEID","PcpManActivateFlowAsync: cannot activate flow %ld with non-existing Cme %ld","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI1BADPARAM","SpdSpInstall: cannot install generic SP %d with non-zero priority","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI1OUTOFSA","PcpQOpCreSaBegin: cannot create new Sa using SpdMan","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI20OUTOFSEL","PcpUtilSelSetFromPar: cannot allocate new selector set","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI21BADPARAM","PcpAclAppend: got too many denys for aclId=%d, max is %d","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI22BADPARAM","PcpAclAppend: got out-of-sequence line number %d for aclId=%d","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI23IDINUSE","PcpSpdCreateCme: cannot create Cme with ID=%u: already used","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI24BADPARAM","PcpAclAppend: got invalid ranges for selector set at lineNo=%d, aclId=%d","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI25IDINUSE","PcpAclAppend: got duplicate line number %d for aclId=%d","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI26OUTOFSP","PcpCmeInstallNext: cannot create a new Sp","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI27BADPARAM","PcpManSetFlowKeys: cannot set keys for flow %ld: SA is in the wrong state","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI28IDINUSE","PcpQOpCreSaBegin: cannot create second Sa for flow %ld: conditions for transport adj. are not met","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI29SPDFAILED","PcpCmeInstallNext: cannot install Sp %d with SpdMan","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI2BADPARAM","PcpManUpdateFlow: cannot update flow %ld with invalid ID","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI2NESTOVERFLOW","SpdSaInitTmSaOut: outer outbound Sa %ld of Sa %ld is above nesting limit of %d","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI30BADPARAM","PcpSpdUpdateCme: cannot update already queued Cme %u","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI31BADALENUM","PcpQOpActSaBegin: cannot find access list entry number %d for cmeId=%d","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI32BADPARAM","PcpQOpActSaBegin: cannot delete old %sbound flow %ld while activating %sbound flow %ld","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI33BADPARAM","PcpCmeActivateSa: got invalid lifetime values softSecs=%lu, hardSecs=%lu","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI34BADPARAM","PcpCmeActivateSa: got invalid lifetime values softKBytes=%lu, hardKBytes=%lu","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI35BADPARAM","PcpCmeIntersectSaWithSp: cannot activate flow %ld with selector ranges not intersecting parent Sp","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI36BADSELADDR","PcpQOpActSaBegin: cannot activate per-host flow %ld with addresses %d.%d.%d.%d and %d.%d.%d.%d not included in Sp %d selector sets","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI37OUTOFSEL","PcpQOpActSaBegin: cannot clone selector set to activate per-host flow %ld","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI38BADSELADDR","PcpQOpActSaBegin: cannot activate transport mode flow %ld with addresses %d.%d.%d.%d and %d.%d.%d.%d not included in Sp's selector sets","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI39BADPARAM","PcpTrInProcess: got invalid opcode %d","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI3NESTOVERFLOW","SpdSaGetXformSeq: outer inbound Sa %ld of Sa %ld is above nesting limit of %d","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI3OUTOFSEL","PcpQOpActSaBegin: cannot allocate selector set for outer Sa in flowId %ld","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI40BADACLID","PcpManCreateCme: cannot create Cme with non-existing access list %u","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI41SPDFAILED","PcpQOpSaActivated: cannot finish activating Sa %ld","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI42QUEUEFULL","PcpCmeActivateSa: cannot activate Sa %ld: queue is full","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI43BADPARAM","PcpAclAppend: got invalid line number %d for ACL %d","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI44QUEUEFULL","PcpSpdCreateCme: cannot create Cme %u (aclId=%u): queue is full","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI45IDNOTINUSE","PcpManDestroyFlowAsync: cannot delete already deleted flow %ld","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI46BADPARAM","PcpQOpActSaBegin: cannot activate non-fully-specified Sa for Cme %d without Acl","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI47BADPARAM","PcpQOpActSaBegin: cannot activate Sa for manual Sp (cmeId=%d,entry=%d), Sa already exists","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI48CMEINUSE","PcpManSetInitMode: cannot set fast init-mode in TcamMan: %ld pending Ops, %ld Flows and %u Cmes already exist or TcamMan is busy","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI49BADPARAM","PcpManQueryFlow: cannot query flow %ld: Sa is not active","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI4BADPARAM","PcpQOpCreSaBegin: got invalid addresses %u.%u.%u.%u and %u.%u.%u.%u for other Sa of flow %ld: expected %u.%u.%u.%u and %u.%u.%u.%u","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI50CMEINUSE","PcpQOpRemCmeBegin: cannot remove Cme %ld: TcamMan is in Init mode","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI51BADPARAM","PcpSpdCreateCme: got invalid flags (manual,dynamic,discover,drop,clear) = (%d,%d,%d,%d,%d), cmeId=%d","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI52IDINUSE","PcpManCreateAcl: cannot process opcode %u for Acl %u in state %u","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI53BADPARAM","PcpManCreateAcl: cannot create Acl with id %u out of range [0,%u]","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI54CMENOTREADY","PcpSpdCreateCme: cannot create Cme %u with Acl %u when Acl state is %u","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI55SPDFAILED","PcpQOpActSaBegin: cannot begin activating Sa %ld for flowId %ld","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI56IDNOTINUSE","PcpManDestroyFlowAsync: cannot delete flow %ld already being deleted","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI57CMEINUSE","PcpManSetInitMode: cannot set normal init-mode in TcamMan: there are pending Flows or Cmes","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI58BADPARAM","PcpManQueryFlow: cannot query flow %ld: parent SP is not active","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI59BADPARAM","PcpCmeActivateSa: cannot activate flow %ld as per-host with subset of Sp as a selector set","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI5BADPARAM","SpdSaActivate: cannot activate Sa %ld, old Sa %ld already has successor Sa %ld","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI5OUTOFSA","PcpQOpCreSaBegin: cannot create new Sa for flow %ld","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI60SPDFAILED","PcpManSaUpdateError: cannot update Flow %ld","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI61BADPARAM","PcpQOpActSaBegin: cannot activate Sa for cmeId=%d, entry=%d with bad spdId=%ld","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI62IDINUSE","PcpQOpCreSaBegin: cannot setup Flow %ld in trans.adj. with outer SA in tunnel mode","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI63CMEINUSE","PcpManActivateFlowAsync: cannot activate flow %ld while using fast policy mode","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI64BADPARAM","PcpQOpActSaBegin: got invalid ranges for selector set of fully-specified flow %ld","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI65BADPARAM","PcpManSetInitMode: got invalid flags 0x%x for setting fast policy mode","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI66NOTREADY","PcpManUpdateFlow: cannot update flow %ld when SA is not active","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI67BADPARAM","PcpSpdCreateSMap: cannot create SMap %u with Acl %u when Acl state is %u","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI68BADPARAM","PcpAclAppend: got invalid flags 0x%x at lineNo=%d, aclId=%d","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI69BADPARAM","PcpManCreateCme: cannot create Cme %u with spdId %u out of range [0,%u]","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI6BADPARAM","PcpTrInProcess: got invalid size %d for opcode %d","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI6OUTOFSEL","SpdSpInstall: cannot compute SP's permit-SelSets from mixed SelSet list","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI70IDNOTINUSE","PcpManUpdateCme: cannot update non-existing Cme %u","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI71QUEUEFULL","PcpSpdUpdateCme: cannot update Cme %u: queue is full","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI72QUEUEFULL","PcpSpdCreateSMap: cannot create SPD map with mapId %u: queue is full","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI73BADPARAM","PcpSpdCreateSMap: cannot create SPD map with mapId %u out of range [0,%u]","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI74IDINUSE","PcpSpdCreateSMap: cannot create SPD map with mapId %u already in use","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI75TMFAILED","PcpSMapInstall: cannot insert SMap %u with TcamMan","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI76BADPARAM","PcpSpdCreateSMap: cannot create SPD map %u with invalid flags 0x%x","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI77BADPARAM","PcpManCreateSMap: cannot create SPD Map %u using non-existent access list %u","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI78OUTOFSMAP","PcpSpdCreateSMap: cannot create SPD map %u: out of memory","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI79BADPARAM","PcpQOpActSaBegin: cannot activate Sa for cmeId=%d, entry=%d when Cme is not ready","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI7BADPARAM","PcpManSetFlowKeys: cannot set keys for flow %ld: invalid ID","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI7OUTOFSEL","SpdSaTmInstallOut: cannot compute outbound SA's permit-SelSets from mixed SelSet list","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI80QUEUEFULL","PcpManDestroyFlowAsync: cannot delete flowId %ld: operation queue is full","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI81IDNOTINUSE","PcpQOpDelSaBegin: cannot delete already deleted flow %ld","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI82QUEUEFULL","PcpManRemoveCme: cannot remove Cme with cmeId %u: queue is full","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI83TMFAILED","PcpSpdInitialize: cannot insert SPD %lu with TcamMan","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI84BADPARAM","PcpManCreateSMap: cannot create SPD map %u with spdId %u out of range [0,%u]","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI85OUTOFSMAP","PcpManCreateSpd: cannot create SPD %u: out of memory","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI86IDINUSE","PcpManActivateFlowAsync: cannot activate already active flow %ld","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI87BADPARAM","PcpManCreateFlow: cannot create Flow with id=%ld, max is %ld","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI88IDNOTINUSE","PcpManRemoveSMap: cannot remove non-existing SMap %u","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI89OUTOFCME","PcpSpdCreateCme: cannot allocate new Cme for aclId=%u","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI8SPDFAILED","PcpManSetFlowKeys: cannot set keys for flow %ld using SpdMan","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI90CMEINUSE","PcpQOpRemCmeBegin: cannot remove Cme %ld while in state %d","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI91OUTOFSEL","PcpAclGetSpSelSet: cannot clone deny-SelSets for ACL %d","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI92QUEUEFULL","PcpManCreateFlow: cannot create flowId %ld: operation queue is full","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI93OUTOFSEL","PcpCmeIntersectSaWithSp: cannot clone deny selectors for flow %ld","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI9BADPARAM","PcpManQueryFlow: cannot query flow %ld: invalid ID","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEI9OUTOFSEL","SpdSaActivateOuterSa: cannot create selector set","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACELOGTEST4","Log test: SEV_ERR","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEPKARSAPRVXCR","PKA: PkaRsaPrivXcrypt() invalid input buffer length %ld","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEPKARSAPUBXCRBUFLEN","PKA: PkaRsaPubXcrypt() invalid input buffer length %ld","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEPKASK0LENCROP2","PKA: 0 length crypto operation","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEPKASK0LENCRYOP3","PKA: 0 length crypto operation","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEPKASK0LENOP","PKA: 0 length crypto operation","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEPKASK1STFRAGSHRT","PKA: 1st frag too short for crypto operation","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEPKASKDESNOTMUL82","PKA: DES/3DES data length not multiple of 8","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEPKASKDESNOTMULT8","PKA: DES/3DES data length not multiple of 8","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ACEPKASKNOCRNOAUTH","PKA: Can't have PKA_CRYPTO_NONE and PKA_HMAC_NONE","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ICPUBADGRESA","Invalid GRE SA - can't find match. saptr:0x%x","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","ICPUPP22","ICMP received, let it go clear newId %d oldid %d","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","3","SPI_NOT_AVAIL","SPI 0x%x is not available","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","ACEIPCMPINGPRE","IPC ping (%s): premature ping...awaiting response to previous ping","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","ACEIPCMPINGSEQ","IPC ping (%cCPU): seq.# does not match: Expected %d, got %d","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","ACEIPCMPINGSKIP","IPC ping (%cCPU): Skipped %d times before receiving reply","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","ACEIPCXNOBUF2","ICPU unable to allocate msg buf for Ping Reply: %ld","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","ACEIPCXNOBUF3","OCPU unable to allocate msg buf for Ping Reply: %ld","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","ACEIPCXPINGNOBUF","%d srcCPU unable to allocate msg buf for Ping Reply in CB: %ld","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","ACELOGTEST3","Log test: SEV_WARN","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","ACEPKADHRMKGIDBUSY","PkaDhRemoveKeyGroup(): DH group ID %d is busy","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","ACETCAMFULLINSMANSP","Full SA insertion for a manual SP.","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","ACETCAMPKTNOSA","IPC payload : %x","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","ACETCAMPKTNOSP","Packet event for a non-existing SP.","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","ACETCAMPKTNOSP1","EarlyPkt Exit1.","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","ACETCAMPKTNOSP2","EarlyPkt Exit2.","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","ACETCAMPKTNOSP3","EarlyPkt Exit3.","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","ACEXCPUALLOC","IPC: Unable to allocate and send STATFLUSH.","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","ACEXCPUALLOC2","IPC: Unable to allocate IPC to set debug flag.","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","ACEXCPUALLOC3","IPC: Unable to allocate IPC to start 5840 test.","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","ACEXCPUCMRESP3","XcpuCfgMonReqCallback:Global stats...Can't respond to host.","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","ACEXCPUCMRESP4","XcpuCfgMonReqCallback: DataPath Stats....Can't respond to host.","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","ACEXCPUCMRESP5","XcpuCfgMonReqCallback: PerFlow Stats....Can't respond to host.","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","ANTIREPLAYWINDOWDEFAULT","Using default replay window for SA SPI 0x%x","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","BULKIP","Wrong type %d size:5d.","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","DUMPMEM","0x%08x: 0x%08x 0x%08x 0x%08x 0x%08x","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","EDSDEBUG","Already in map: map[0x%x] newid0x%x flags:0x%x mtu:0x%x spdid:0x%x","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","FIPSCHECK2","FIPS RCVD Multi-buffer Packet.","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","FIPSCHECK3","FIPS Failed Packet Comparison.","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","FIPSCHECK4","FIPS Test Completed Successfully.","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","ICPUFRAG1","PktReasmSetAction failed.","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","ICPUPP10","Packet src:%d.%d.%d.%d dst:%d.%d.%d.%d proto ESP, but not SA proto!","The received packet's protocol does not match the security association (SA) protocol. The SA expects Authentication Header (AH), but the packet uses Encapsulating Security Payload (ESP).","Check whether the negotiated protocol matches the configured transform sets of both peers."
"VPNSPA","4","ICPUPP11","Packet src:%d.%d.%d.%d dst:%d.%d.%d.%d proto AH, but not SA proto!","The received packet's protocol does not match the SA protocol. The SA expects ESP, but the packet uses AH.","Check whether the negotiated protocol matches the configured transform sets of both peers."
"VPNSPA","4","ICPUPP12","IPPE says IPSec, not pkt src:%d.%d.%d.%d dst:%d.%d.%d.%d proto:%d!","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","ICPUPP13","Policy check failed for pkt src:%d.%d.%d.%d dst:%d.%d.%d.%d proto:%d SA index:0x%x","The decrypted packet does not match the security policy.","Check whether the security policy on both peers is symmetric."
"VPNSPA","4","ICPUPP14","Pkt src:%d.%d.%d.%d dst:%d.%d.%d.%d proto:%d match deny; SA index 0x%x","Encrypted packets were received that should have been unencrypted.","Check whether the security policy on both peers is symmetric."
"VPNSPA","4","ICPUPP15","SecInfo 0x%x doesn't match with SA 0x%x SA index:0x%x","An unexpected and unsupported nesting of SA was detected.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","ICPUPP16","Inner proto %d must be IPSec but is not","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","ICPUPP2","SaCheckSelectors: Illegal pkt, no valid SA","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","ICPUPP3","Illegal pkt dst:%d.%d.%d.%d proto:%d spi:0x%x, no match on SA SPI 0x%x.","No matching SA was found for the received encrypted packet. This message is most likely to occur during rekeying when the inbound SA is not yet established.","If the message persists and packets are being lost, check whether the CPU is overloaded or the crypto engine is oversubscribed."
"VPNSPA","4","ICPUPP4","Illegal pkt dst:%d.%d.%d.%d proto:%d spi:0x%x, no match on SA dst%d.%d.%d.%d","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","ICPUPP8","Illegal clear pkt src:%d.%d.%d.%d dst:%d.%d.%d.%d proto:%d.","Clear packets were received that should have been encrypted.","Check whether the remote peer has a correct security policy and SA to encrypt the packets."
"VPNSPA","4","ICPUPP9","Packet src:%d.%d.%d.%d dst:%d.%d.%d.%d seq num:0x%x failed replay check last seq num:0x%x for SA:0x%x.","IPsec packets have failed the anti-replay check. A common cause is the use of QoS in your network. With QoS, lower priority packets can arrive late, missing the anti-replay check window. When this condition occurs, higher level protocols can request retransmission so that functionality is not lost. Time-sensitive protocols, such as voice traffic, might be degraded due to dropped or late packets.","Increase the anti-replay window size. If anti-replay checking is not needed, disable it by removing the HMAC function from the transform set."
"VPNSPA","4","ICPUSYSIPADDRADD","PktProcAddSysIpAddr: Unable to delete sys IP Addr %d.%d.%d.%d","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","ISAUNCA7","PktProcAtnModSas: Mismatch valid flag unca:invalid index:0x%x","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","RECOVERYFRAG","Ipfrag: Unable to transmit. CP Lockup Occured.","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","SINGLEIP","Wrong type %d size:%d.","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","SPDID","XcpuSetVlanSpdId: IpcAllocFailed","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","XCPURECOVERY","Error Disabling EDDE EITD DMA","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","5","ACELOGTEST2","Log test: SEV_NOTICE","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","4","ACEPKADHGRPNTALC","PkaDhRemoveKeyGroup(): DH group ID %d not allocated","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","5","ACEPKADHGSBADID","PkaDhGenerateSession(): DH group ID %d not defined","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","5","ACEPKADHGSHIDNOALL","PkaDhGenerateShared:DH session ID %d not allocated","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","5","ACEPKADHGSIDINUSE","PKA: PkaDhGenerateSessionInt: DH session id %ld already in use","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","5","ACEPKADHGSINVID","PKA: PkaDhGenerateSessionInt: invalid DH session id %ld","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","5","ACEPKAINITCMPL","BCM5820: Initialization complete","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","5","ACEPKANOBDESC","PKA: no data buffer descriptors available","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","5","ACEPKANOMOREDHGRPS","PKA: no more DH groups available","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","5","ACEPKAPOSTRSTDELAY","PKA: BCM5820 post reset delay","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","5","ACEPKARESUB","BCM5820: Resubmitting crypto request","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","5","ACEPKARESUBPK","BCM5820: Resubmitting PK request 0x%x","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","5","ACEPKARSACKBITSNMULT","PKA: RSA key create request of %d bits not a multiple of 64","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","5","ACEPKARSACKMAXBITS","PKA: RSA key create request of %d bits exceeds max of %d bits","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","5","ACEPKARSACKTOOMANY","PKA: Too many RSA key create requests","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","5","ACEPKARSARMPSBUSYID","PKA: can't remove busy RSA private session %ld","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","5","ACEPKARST","PKA: BCM5820 in reset","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","5","ACEPKARSTCOMPL","BCM5820: Reset complete","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","6","ACEIPCSENDMSGLOCAL","%s send msg buf (local)","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","6","ACEIPCSENDMSGTOOBIG","%s unable to send msg buf (msg too big)","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","6","ACEIPCSENDMSGTOOMANYCLIENTS","%s unable to send msg buf (client id too big)","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","6","ACELOGTEST1","Log test: SEV_INFO","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","6","ACEPKAHWCRNGT","PKA: HW RNG has duplicate data, discarding","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","6","ACEPKAPKNOMCR2","PKA: no Public Key MCRs available","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","6","ACEPKARNG","PKA: seed key is same as the seed, discarding","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","6","ACEPKARNGDUP","PKA: A pseudo-random number was generated twice in succession. 0x%.8lx%.8lx; 0x%p 0x%p idx:0x%x","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","6","ACEPKARNGKAT","PKA: RNG failed KAT","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","6","ACEPKASKNOCRYCTXT","PKA: no Crypto CTXs available","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","6","ACEPKASKNOMCRS","PKA: no Crypto MCRs available","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","7","ACELOGTEST0","Log test: SEV_DEBUG","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","7","ACELOGTESTA","Log test: SEV_DEBUG A","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","7","ACELOGTESTB","Log test: SEV_DEBUG B %d %s","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","7","ACESHI","git along %d %s","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VPNSPA","7","ACESLO","nuf said","An error was reported by the firmware.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VRRP","4","BADAUTH","Bad authentication from %i, group %d, type %d","Two routers participating in Virtual Router Redundancy Protocol (VRRP) disagree on authentication.","Enter the vrrp authentication command to repair the VRRP authentication discrepancy between the local system and the system whose IP address is reported."
"VRRP","4","BADAUTHTYPE","Bad authentication from %i, group %d, type %d, expected %d","Two routers participating in VRRP disagree on the valid authentication type.","Enter the vrrp authentication command to repair the VRRP authentication discrepancy between the local system and the system whose IP address is reported."
"VRRP","6","UNAVAILABLE","%s Grp %d state %s - %s","The VRRP router has changed state","Informational only. No action required."
"VRRS","3","ERROR","Internal error, %s","An internal software error occurred.","Informational only. No action required."
"VRRS","4","WARN","Internal warning, %s","An internal software warning occurred.","Informational only. No action required."
"VRRS","6","INFO","Internal info, %s","An internal software information message occurred.","Informational only. No action required."
"VRRS","6","STATE","%s","The VRRS router has changed state.","Informational only. No action required."
"VSDA","3","ADD_LTL_INDEX_AND_FPOE","Unable to add LTL index 0x%04x and program fpoe for %u/%u","An internal error occurred.","No action is required."
"VSDA","3","GET_IDB_FAILED","Failed to get idb for port cookie (linkchange)","An internal error occurred.","No action is required."
"VSDA","3","ICC_ERR","%s","A failure occurred during the intercard communications (ICC) operation.","No action is required."
"VSDA","3","INVALID_PROC_EVENT","Got event %d:%d","The process was awakened with an invalid event.","No action is required."
"VSDA","3","INVALID_TIMER","Invalid timer %d for interface %s","A timer event occurred, but the timer type was invalid.","No action is required."
"VSDA","3","INVALID_TIMER_TYPE","Invalid timer %d processed in %s","A timer event occurred, but the timer type was invalid.","No action is required."
"VSDA","3","LINK_DOWN","Interface %s is no longer dual-active detection capable","The specified link is no longer capable of detecting dual-active situations.","No action is required."
"VSDA","3","PKT_CREATE","Can't create packet: %s","A dual-active packet cannot be created due to the reason described.","No action is required."
"VSDA","3","PKT_RX","Can't process the received packet: %s","A dual-active packet cannot be processed due to the reason described.","No action is required."
"VSDA","3","PKT_TX","Can't send packet: %s","A dual-active packet cannot be sent due to the reason described.","No action is required."
"VSDA","3","PROC_CREATE_FAILED","Unable to create process","The specified process could not be created.","No action is required."
"VSDA","3","QUEUE_CREATE_FAILED","Unable to create watched queue","The specified watched queue could not be created.","No action is required."
"VSDA","3","SET_PORT_LTL_INDEX","Unable to set LTL index for port %s to 0x%x","An internal error occurred","No action is required."
"VSDA","3","TIMER_NULL_INTFC","NULL context for timer %d in %s","A timer event occurred, but it specified a NULL interface.","No action is required."
"VSDA","3","TIMER_STARTED","Timer %u on interface %s started","The specified link is now capable of detecting dual-active situations.","No action is required."
"VSDA","3","TX_THREAD_FAILURE","Thread %u: %s","This is a general thread error message.","No action is required."
"VSDA","3","VSDA_SCP_BAD_STATUS","SCP operation ([chars]) return status [dec]","A non-blocking SCP operation of the specified type failed for dual-active fast-hello on a line card","No action is required."
"VSDA","3","VSDA_SCP_PAK_FAIL","Unable to get SCP packet for opcode [dec], operation [dec]","Packet allocation failed for sending an SCP message to do the specified operation","No action is required."
"VSDA","3","VSDA_SCP_SEND_FAIL","Unable to send SCP message for opcode [dec], operation subop [dec]","Packet send failed for the SCP message to perform the specified operation","No action is required."
"VSDA","5","LINK_UP","Interface %s is now dual-active detection capable","The specified link is now capable of detecting dual-active situations.","No action is required."
"VSEC","4","VLANACCESSLOGRF","FAILED to set VACL-LOG rate limiter. Is strongly suggested to rate limit when using this feature","The configuration for the VACL logging rate limiter has failed.","Determine the rate limiter usage, free some resources if possible, and then try to set the rate limiter again."
"VSEC","6","VLANACCESSLOGAP","vlan %d (port %d/%d) denied arp ip %i - %i, %d packet%s","A packet from the given vlan and physical port matching the vacl log criteria was detected.","No action is required."
"VSEC","6","VLANACCESSLOGDP","vlan %d (port %d/%d) denied icmp %i - %i (%d/%d), %d packet%s","A packet from the given vlan and physical port matching the vacl log criteria was detected.","No action is required."
"VSEC","6","VLANACCESSLOGNP","vlan %d (port %d/%d) denied ip protocol=%d %i - %i, %d packet%s","A packet from the given vlan and physical port matching the vacl log criteria was detected.","No action is required."
"VSEC","6","VLANACCESSLOGP","vlan %d (port %d/%d) denied %s %i(%d) - %i(%d), %d packet%s","A packet from the given vlan and physical port matching the vacl log criteria was detected.","No action is required."
"VSEC","6","VLANACCESSLOGRP","vlan %d (port %d/%d) denied igmp %i - %i (%d), %d packet%s","A packet from the given vlan and physical port matching the vacl log criteria was detected.","No action is required."
"VS_GENERIC","1","VS_HA_PS_NOT_SUPPORTED","Chassis Standby is not supported in the current release. Forcing the chassis standby in switch [dec] slot [dec] to drop to rommon","The chassis standby function is not supported in this release.","No action is required."
"VS_GENERIC","1","VS_HA_PS_RUNNING_LEGACY_IMAGE","Chassis Standby in switch [dec] slot [dec] is running non Virtual Switch image. Please remove the chassis standby.","The standby chassis is running an image that does not support virtual switch.","Remove the standby chassis."
"VS_GENERIC","3","VS_ADD_VSL_ENTRY_FAILED","Add VSL configured port for vslot [int] port [int] failed. Exceed port member count limit.","An attempt to add an entry for (vslot, port) to the VSL configured port list failed because the port member count limit was exceeded.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VS_GENERIC","3","VS_BOOLEAN_CREATE_FAILED","Unable to create watched boolean '[chars]'","The creation of the specified watched boolean failed.","No action is required."
"VS_GENERIC","3","VS_ENQUEUE_FAILED","Unable to enqueue to [chars] queue","An internal error occurred that prevented a message from being enqueued to the specified process. The packet was dropped.","No action is required."
"VS_GENERIC","3","VS_ICC_PAK_FAIL","Unable to get ICC packet for opcode [dec], operation [dec]","A packet allocation failed for sending an ICC message to do the specified operation.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VS_GENERIC","3","VS_ICC_RESP_PAK_NULL","Failed to obtain response packet","The response packet pointer is NULL. This could be due to an insufficient memory condition on the response packet sending side or to a failure to get an IPC message on the receiving side.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VS_GENERIC","3","VS_NO_PAGP_CHANNEL_HWIDB","No PAgP channel hwidb for PAgP group [dec]","An internal error occurred. Port Aggregation Protocol (PAgP) could not find the hardware interface descriptor block (IDB) for this channel group.","No action is required."
"VS_GENERIC","3","VS_PROC_CREATE_FAILED","Unable to create process '[chars]'","The creation of the specified process failed.","No action is required."
"VS_GENERIC","3","VS_QUEUE_CREATE_FAILED","Unable to create queue '[chars]'","The creation of the specified queue failed.","No action is required."
"VSL","3","VSL_PROC_ARGS_FAILED","Unable to process arguments '[chars]'","The processing of the specified arguments failed.","No action is required."
"VS_GENERIC","5","VS_CONFIG_DIRTY","Configuration has changed. [chars]","An attempt to reload was ignored due to a configuration change.","No action is required."
"VSL","2","VSL_STATUS","-======== VSL is [chars] ========-","The VSL status has changed to active (up) or inactive (down).","No action is required."
"VSL","3","PRE_PEER_COMM_TIMEOUT","A timeout occurred while waiting for vsl_pre_peer_comm_op_done","All applications failed to respond within the specified time. Operation is continuing.","No action is required."
"VSL","3","TROUBLESHOOT","Structure type [int]: [chars]","The specified structure could not be created to save VSL troubleshooting information when VSL goes down.","No action is required."
"VSL","3","VSL_ICC_PAK_FAIL","Unable to get ICC packet for opcode [dec], operation [dec]","Packet allocation failed for sending an ICC message to do the specified operation.","No action is required."
"VSL","3","VSL_ICC_SEND_FAIL","Unable to send ICC message for opcode [dec], operation subop [dec]","Packet send failed for the ICC message to perform the specified operation.","No action is required."
"VSL","3","VSL_INST_CREATE_FAIL","Failed to create VSLP instance for VSL","Unable to create a VSLP instance for VSL.","No action is required."
"VSL","3","VSL_INTERNAL_ERROR","[chars], port [dec]/[dec]","An internal error occurred.","No action is required."
"VSL","3","VSL_INVALID_PROC_EVENT","Got event [dec]:[dec]","An invalid event activated the process.","No action is required."
"VSL","3","VSL_INVALID_TIMER_CTXT","NULL or invalid timer context","A timer expiration event was received with NULL or invalid context information.","No action is required."
"VSL","3","VSL_INV_PORT_STATUS_CHANGE","Link status change ([chars]) on non-VSL port [dec]/[dec]","A link status change was detected on a port that is not a VSL member.","No action is required."
"VSL","3","VSL_KEYSTORE_ACCESS","VSL keystore access failed during %s","Unable to read the keystore or keystore is empty","Provision the Virtual Switch Link PMK with the switch pmk Privileged Exec command."
"VSL","3","VSL_MAX_PORTS","Cannot configure more than [dec] ports","A port could not be added to the VSL because the maximum number of ports in the VSL has been reached.","No action is required."
"VSL","3","VSL_MODE_BAD_STATUS","VSL-mode programming ([dec]) returned status [dec]","A VSL-mode operation of the specified type failed on a VSL line card.","No action is required."
"VSL","3","VSL_PORT_CFG_MOD_OFFLINE","Module [dec] offline when port [dec] added to VSL","A port was added to the VSL when the corresponding line card was offline.","No action is required."
"VSL","3","VSL_PROC_CREATE_FAILED","Unable to create process '[chars]'","The specified process could not be created for an unknown reason.","No action is required."
"VSL","3","VSL_REGISTRY_ADD_FAIL","[chars] registry addition failed","An addition to the given registry failed during initialization.","No action is required."
"VSL","3","VSL_RESERVED_LTL_FAIL","Unable to allocate reserved LTL indices","Platform-VSLP for VSL uses a number of reserved Local Target Logic (LTL) indices allocated by the LTL Manager. Because this allocation failed, the system can no longer function.","No action is required."
"VSL","3","VSL_ROLE_RES_BOOL_FAIL","Unable to create watched boolean for role resolution","A watched boolean for role resolution could not be created.","No action is required."
"VSL","3","VSL_SCP_BAD_STATUS","SCP operation ([chars]) return status [dec]","A nonblocking SCP operation of the specified type. failed on a VSL line card","No action is required."
"VSL","3","VSL_SCP_BLK_SEND_FAIL","[chars] for SCP opcode [dec], subopcode [dec]","Failed to do the specified operation when sending the specified SCP message through a blocking call.","No action is required."
"VSL","3","VSL_SCP_FAIL","SCP operation failed","A nonblocking SCP operation failed on a VSL line card.","No action is required."
"VSL","3","VSL_SCP_PAK_FAIL","Unable to get SCP packet for opcode [dec], operation [dec]","Packet allocation failed for sending an SCP message to do the specified operation.","No action is required."
"VSL","3","VSL_SCP_SEND_FAIL","Unable to send SCP message for opcode [dec], operation subop [dec]","Packet send failed for the SCP message to perform the specified operation.","No action is required."
"VSL","3","VSL_UNCFG_BAD_PORT","Unconfigure on non-VSL port [dec]/[dec]","An attempt was made to unconfigure a port from the VSL, but the port is not part of the VSL.","No action is required."
"VSL","3","VSL_UNCFG_FAILED","Unconfigure on VSL port [dec]/[dec] failed: [chars]","While unconfiguring a VSL port, the specified operation failed.","No action is required."
"VSL","5","VSL_CNTRL_LINK","New VSL Control Link [chars]","A new VSL control link was detected on a VSL line card.","No action is required."
"VSL_BRINGUP","3","MODULE_DOWN","Failed to bring up VSL module in slot [dec] switch [dec]. [chars]","The bringup of the specified module failed due to the reason indicated.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VSL_BRINGUP","3","NO_MODULE_UP","Failed to bring up any VSL modules on switch [dec]","An attempt to bring up any VSL line cards or supervisor engines failed due to an internal error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VSL_BRINGUP","3","PROC_CREATE_FAILED","Unable to create process '[chars]'","The creation of the specified process failed.","No action is required."
"VSL_BRINGUP","3","VS_OVERSUB_MODECHANGE_FAIL","Switching mode failed on Switch %d module %d port-group %d","The VSL bringup process was unable to change the switching mode of the indicated module.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VSL_BRINGUP","6","MODULE_UP","VSL module in slot [dec] switch [dec] brought up","The specified VSL module was brought up successfully.","No action is required."
"VSL_BRINGUP","6","NOT_VS_CAPABLE_EARL","Supervisor card does not have Virtual Switch capable EARL daughter board","The supervisor engine card does not have an EARL daughterboard capable of running in virtual switch mode. An EARL 7.5 or above is required.","Use a supported supervisor engine card for a virtual switch system."
"VSL_BRINGUP","6","PREEMPT_DISABLED","Preemption suppressed due to first time VS conversion","A higher priority standby switch will not preempt a lower priority active switch when a virtual switch (VS) system is converted for the first time from a standalone configuration.","Use the switch accept mode virtual command to merge the standby VSL configuration first. Then, if desired, use the redundancy force-switchover command to make the other switch active."
"VSL_BRINGUP","6","SUP720_VS_NOT_SUPPORT","No support for Virtual Switch on SUP720. Booting up in Standalone mode","The Supervisor Engine 720 is virtual switch capable. However, Cisco does not officially support virtual switch mode on the Supervisor Engine 720.","No action is required."
"VSLP","2","VSL_DOWN","[chars]","VSL status changed to DOWN. More detail is provided in the message.","No action is required."
"VSLP","3","ICC_ERR","[chars]","A failure occurred during the inter-card communications (ICC) operation.","No action is required."
"VSLP","3","ISSU_ERROR","%s","The virtual switch link protocol (VSLP) was unable to perform an ISSU operation.","No action is required."
"VSLP","3","PKT","VSLP packet error: [chars]","A VSLP packet error occurred for the reason described.","No action is required."
"VSLP","3","PKT_CREATE","Can't create packet: [chars]","A VSLP packet cannot be created due to the reason described.","No action is required."
"VSLP","3","PKT_RX","Can't process the received packet: [chars]","A VSLP packet cannot be processed due to the reason described.","No action is required."
"VSLP","3","PKT_TX","Can't send packet: [chars]","A VSLP packet cannot be sent due to the reason described.","No action is required."
"VSLP","3","REGISTRY_ADD_ERR","Failure in adding to [chars] registry","A function could not be added to the registry.","No action is required."
"VSLP","3","RRP_ERR_MSG","[chars]","The VSLP role resolution protocol detected an error.","No action is required."
"VSLP","3","RRP_INSTANCE_OUT_OF_BOUNDS","Instance value [dec] is outside the expected range","The instance value received is out of bounds.","No action is required."
"VSLP","3","RRP_INVALID_INSTANCE","Instance value [dec] is invalid","The instance value received corresponds to an invalid instance.","No action is required."
"VSLP","3","RRP_MEMORY_ALLOC_ERR","(Instance:[dec], Peer:[dec]): No memory available for [chars]","The VSLP could not obtain the requested memory.","No action is required."
"VSLP","3","RRP_PEER_INFO_ERR","(Instance:[dec], Peer:[dec]): Peer [chars]","The role resolution protocol has encountered an error associated with this peer.","No action is required."
"VSLP","3","RRP_PEER_INSTANCE_ERROR","(Instance:[dec], Peer:[dec], Up:[dec], Valid:[dec], Switch:[dec], Role:[chars], PeerRole:[chars]): [chars]","An error occurred pertaining to the instance and peer group specified.","No action is required."
"VSLP","3","RRP_PEER_SUP_PSLOT_ERR","save_rrp_tlv_data->peer_sup_pslot:[int], my_sup_pslot:[int]","The role resolution protocol detected a difference in the peer supervisor engine pslot.","No action is required."
"VSLP","3","RRP_RESERVED_PEER_ERR","(Instance:[dec], Peer:[dec]): Reserved peer [dec] [chars]","The role resolution protocol has detected an error related to the reserved peer.","No action is required."
"VSLP","3","RRP_SESSION_ID_ERR","(Instance:[dec], Peer:[dec]): Session id mismatch. Expected [dec], got [dec]","The VSLP role resolution protocol has detected a session ID mismatch.","No action is required."
"VSLP","3","RRP_SLOT_PORT_ERR","(Slot:[dec], Port:[dec]): [chars]","The role resolution protocol has detected an error related to the specified slot and port.","No action is required."
"VSLP","3","RRP_TIMER_CREATE_FAIL","(Instance:[dec], Peer:[dec]): Unable to create RRP timer","The role resolution protocol was unable to create a timer for the specified instance and peer.","No action is required."
"VSLP","3","RRP_UNEXPECTED_ROLE","Unexpected roles. Local role = [chars], Peer role = [chars]","The role resolution protocol has encountered inconsistent role information.","No action is required."
"VSLP","3","RRP_VALUE_ERR","[chars]: [dec]","The role resolution protocol has encountered an unknown value.","No action is required."
"VSLP","3","VSLP_BOOLEAN_CREATE_FAILED","Unable to create watched boolean '[chars]'","The specified watched boolean could not be created.","No action is required."
"VSLP","3","VSLP_INST_INVALID_CAP","Invalid capability [dec] for VSLP instance [dec]","A VSLP capability was requested that is beyond the current list of supported capabilities.","No action is required."
"VSLP","3","VSLP_INST_OUT_OF_RANGE_CREATE","Cannot create VSLP instance [dec]","A VSLP instance could not be created for the switch ID because it is not within the acceptable range.","No action is required."
"VSLP","3","VSLP_INST_OUT_OF_RANGE_DESTROY","Cannot destroy VSLP instance [dec]","The given VSLP instance could not be destroyed because it is not within the acceptable range.","No action is required."
"VSLP","3","VSLP_LMP_DOMAIN_MISMATCH","Domain ID in probe packet from peer %d is not the same as local Domain ID %d. The packet was dropped.","The virtual switch domain ID in a probe packet from the peer is not the same as the local domain ID. The packet was dropped.","Investigate and correct this misconfiguration."
"VSLP","3","VSLP_LMP_FAIL_REASON","[chars]: [chars]","This message displays the reason for a link to leave the LMP operational state.","No action is required."
"VSLP","3","VSLP_LMP_FLAG_SET","Incorrect flag value (0x%x) on port %d/%d","The system detected an unexpected value for the flag field of a VSL link. This condition is caused by an internal software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show vslp lmp summary, and show vslp lmp fsm commands and your pertinent troubleshooting logs."
"VSLP","3","VSLP_LMP_FSM_INVALID_TIMER","Invalid timer [dec] for port [dec]/[dec] in [chars] operation","A timer event occurred, but the timer type was invalid.","No action is required."
"VSLP","3","VSLP_LMP_FSM_NULL_CTXT","NULL context for FSM action [chars]","An FSM action routine was invoked, but with a NULL context argument.","No action is required."
"VSLP","3","VSLP_LMP_FSM_TIMER_BAD_CTXT","Invalid or NULL context for timer [dec] in [chars] operation","A timer event occurred, but the FSM infrastructure passed to the handler a context pointer that is currently not in use or is NULL.","No action is required."
"VSLP","3","VSLP_LMP_INVALID_PROC_EVENT","Got event [dec]:[dec]","An invalid event woke up the process.","No action is required."
"VSLP","3","VSLP_LMP_MAX_PGS","Cannot create more thatn [dec] LMP peer groups","The number of LMP peer groups has reached the maximum per-LMP instance.","No action is required."
"VSLP","3","VSLP_LMP_MAX_PORTS","Cannot configure more than [dec] ports","LMP could not be configured on a port because the maximum number of ports per-LMP instance has been reached.","No action is required."
"VSLP","3","VSLP_LMP_PG_CREATE_FAIL","Unable to create PG ([enet]:[dec]) for port [dec]/[dec]","The peer group could not be created for the given port. This port is the first port connected to this peer to move into the operational state.","No action is required."
"VSLP","3","VSLP_LMP_PG_GET_FAIL","Unable to get PG (%e) for port %d/%d","The system was unable to get the peer group for the given port.","No action is required."
"VSLP","3","VSLP_LMP_PG_INCONSISTENT","PG [enet]:[dec] should have [dec] links, but none found","A link has left a peer group that seems to have more links, but no other links were found.","No action is required."
"VSLP","3","VSLP_LMP_PG_NO_CTRL_LINK","No control link for preferred PG [dec]","A peer group with no control link has been set as the preferred peer group.","No action is required."
"VSLP","3","VSLP_LMP_PG_OUT_OF_RANGE","Peer group [dec] is out of range","A peer group has been passed to an API that is out of range.","No action is required."
"VSLP","3","VSLP_LMP_RX_BAD_FIRST_TLV","Bad first TLV ([dec]) in received packet on port [dec]/[dec]","The received LMP packet was dropped because its first type-length value (TLV) was not a Probe TLV or a Hello TLV.","No action is required."
"VSLP","3","VSLP_LMP_RX_BAD_INTERFACE","Incorrect port [dec]/[dec] for received packet","A received LMP packet was dropped because it had incorrect received packet information. The LMP packet may have been received from an interface on which VSLP is not enabled.","No action is required."
"VSLP","3","VSLP_LMP_RX_BAD_TLV_COUNT","Bad TLV count in received packet ([dec])","A received LMP packet was dropped because it had an incorrect number of type-length values (TLVs). This includes the case where no TLVs are received.","No action is required."
"VSLP","3","VSLP_LMP_RX_PLATFORM_REJECT","Platform TLV rejected for receieved [chars] packet","A received LMP packet was dropped because one or more platform type-length values (TLVs) were rejected.","No action is required."
"VSLP","3","VSLP_LMP_RX_QUEUE_FAIL","Unable to enqueue received packet for processing","An internal error occurred that prevented a packet from being enqueued to the packet processing queue. The packet was dropped.","No action is required."
"VSLP","3","VSLP_LMP_RX_XFORM","Failed to transform received %s packet","An ISSU transformation failed on the received packet. The packet was dropped","No action is required."
"VSLP","3","VSLP_LMP_SAME_SWITCH_ID","Switch id in probe packet is the same as the local switch id %d. The packet was dropped.","The switch ID in a probe packet from the peer is the same as the local switch ID. The packet was dropped.","Investigate and correct this misconfiguration"
"VSLP","3","VSLP_NULL_ENTRY","Null [chars] entry in [chars] operation","A NULL entry was passed in the specified operation.","No action is required."
"VSLP","3","VSLP_PROC_CREATE_FAILED","Unable to create process '[chars]'","The specified process could not be created due to unknown reasons.","No action is required."
"VSLP","3","VSLP_QUEUE_CREATE_FAILED","Unable to create watched queue '[chars]'","The specified watched queue could not be created due to unknown reasons.","No action is required."
"VSLP","3","VSLP_REGISTRY_ADD_FAIL","[chars] registry addition failed","The given registry addition failed during initialization.","No action is required."
"VSLP","3","VSLP_THREAD_CREATE_FAILURE","tid %u/intvl %u: %s","VSLP transmit thread creation failed for the specified reason.","No action is required."
"VSLP","3","VSLP_THREAD_FAILURE","tid %u: %s","A general VSLP transmit thread failure occurred for the specified reason.","No action is required."
"VSLP","4","ASIC_DUMP","[chars]","The VSL physical link is up and the role was not resolved in RRP.","No action is required."
"VSLP","4","VSL_PREEMPT_TIMER","Preempt timer configured to [dec] minutes. Standby will takeover as active in [dec] minute(s)","The preempt timer is configured on the standby unit. The standby unit will become active after the timer expires.","No action is required."
"VSLP","5","RRP_ACTIVE_PEER_DOWN","Communication to active peer went down. Triggering switchover...","The role resolution protocol has received an indication that communication with the active peer has gone down. This condition will trigger a switchover.","No action is required."
"VSLP","5","RRP_RT_CFG_CHG","Configured [chars] value is different from operational value. Change will take effect after config is saved and switch [dec] is reloaded.","Role resolution protocol configuration changes by user","No action is required."
"VSLP","5","RRP_MSG","[chars]","A role resolution protocol event was received.","No action is required."
"VSLP","5","RRP_NO_PEER","No VSLP peer found. Resolving role as Active","Because VSLP could not communicate with any peer, it will boot up as active.","No action is required."
"VSLP","5","RRP_PEER_TIMEOUT","VSLP peer timer expired without detecting peer. Resolving role as Active","Because the role resolution protocol could not communicate with any peer before the peer timer expiry, it will boot up as active.","No action is required."
"VSLP","5","RRP_PREEMPT","[chars]	Switch [int]: Priority [int]: Preempt [chars]	Switch [int]: Priority [int]: Preempt [chars]","Displays preemption configuration.","No action is required."
"VSLP","5","RRP_PREEMPT_IGNORE","%s","The preemption configuration is ignored due to unsaved configurations.","No action is required."
"VSLP","5","RRP_ROLE_RESOLVED","Role resolved as [chars] by VSLP","The role resolution protocol has communicated with a peer and has resolved its role.","No action is required."
"VSLP","5","RRP_RT_CFG_CHANGE","[chars]","The role resolution protocol configuration has been changed by a user.","No action is required."
"VSLP","5","RRP_UNSAVED_CONFIG","Ignoring system reload since there are unsaved configurations.Please save the relevant configurations","The role resolution protocol received an indication that the system must be reloaded due to a role change from active to standby. No reload will occur because unsaved configurations exist and would be lost.","No action is required."
"VSLP","5","RRP_WR_MEM_PROGRESS","Ignoring system reload since config save operation is in progress. Please wait till the configs are saved","The role resolution protocol (RRP) received an indication that a system reload is required due to a role change from active to standby. Since a configuration save operation is in progress, the system will not be reloaded.","No action is required."
"VSLP","5","VSL_UP","[chars]","VSL status has changed to UP, with more details provided in message.","No action is required."
"VSLP","6","ACTIVE","[chars]","Displays the state of the virtual switch active supervisor engine.","No action is required."
"VSLP","6","STANDBY","[chars]","Displays the state of the virtual switch standby supervisor engine.","No action is required."
"VSLP_ISSU","3","CAP_RESULT_INCOMPAT","VSLP ISSU client capability exchange result incompatible.","Based on the results of the capability exchange, the VSLP ISSU client is not compatible with the peer.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"VSLP_ISSU","3","INIT","VSLP ISSU client initialization failed at %s, error %s","The VSLP ISSU client could not be initialized. This condition will cause a catastrophic failure when an ISSU upgrade or downgrade is performed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VSLP_ISSU","3","INTERNAL","An internal error occurred: %s","A software error occurred during the specified operation.","No action is required."
"VSLP_ISSU","3","INVALID_PROC_EVENT","Got event %d:%d","The process was awakened with an invalid event.","No action is required."
"VSLP_ISSU","3","ISSU_ERROR","%s failed with error code %d for peer %e","An ISSU application program interface (API) was unable to perform an operation for the VSLP layer. The message includes the error code from the ISSU library.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu fsm commands and your pertinent troubleshooting logs."
"VSLP_ISSU","3","MSG_NOT_OK","VSLP ISSU client message %s is not compatible","The VSLP ISSU client received an incompatible message from the peer unit. Since the message is not compatible, it cannot be processed by this unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu message group, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"VSLP_ISSU","3","NEGO_FAILED","VSLP ISSU start nego session with peer %e with error code %s","The VSLP ISSU could not start its negotiation process.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, and show issu fsm commands and your pertinent troubleshooting logs."
"VSLP_ISSU","3","NULL_ENTRY","Null %s entry in %s","A NULL entry was passed in the specified operation.","No action is required."
"VSLP_ISSU","3","PROC_CREATE_FAILED","Unable to create process","The specified process could not be created.","No action is required."
"VSLP_ISSU","3","QUEUE_CREATE_FAILED","Unable to create watched queue","The specified watched queue could not be created.","No action is required."
"VSLP_ISSU","3","RX_BAD_INTERFACE","Incorrect port %d/%d for received packet","A VSLP ISSU packet was received that contains incorrect received packet info. This VSLP ISSU packet may have been received from an interface on which VSLP is not enabled. The packet was dropped.","No action is required."
"VSLP_ISSU","3","RX_QUEUE_FAIL","Unable to enqueue received packet for processing","An internal error occurred that prevented a packet from being enqueued to the packet processing queue for processing. The packet was dropped.","No action is required."
"VSLP_ISSU","3","SEND_FAILED","VSLP ISSU client failed to send a negotiation message","The VSLP ISSU client could not send a session negotiation message to the peer. When a problem occurs in the negotiation, the peer switch unit cannot be brought up as standby, resulting in two active switches in the system.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"VSLP_ISSU","3","SESSION","VSLP ISSU client %s","The VSLP ISSU client detected an error during a session negotiation with the peer unit. As a result, the peer switch cannot be brought up as standby and two switches will be active in the system.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu capability entries, show issu session, and show issu negotiated capability commands and your pertinent troubleshooting logs."
"VSLP_ISSU","3","TRANSFORM","VSLP ISSU client %s transform failed for %s message, error %s","The VSLP ISSU client could not transform the message. If the transmit transformation failed, the VSLP message cannot be sent to the standby unit. If the receive transformation failed, the VSLP message cannot be processed on the standby unit. In either case, the VSLP ISSU client state will not be identical with the active unit.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show logging, show issu session, and show issu negotiated version commands and your pertinent troubleshooting logs."
"VS_MERGE","3","SAME_ACT_STDBY_PO","Invalid configuration - standby VSL port channnel number [int] is same as active VSL port channel. Auto-merge process is aborted.","This is an invalid configuration. Active and standby must use different VSL port channel numbers. Auto-merge process is aborted. If this situation happens, standby switch will come up in RPR mode.","Use different port channel numbers for active and standby VSL port channels and its members. This change can be done by bringing down all VSL links so that standby switch comes up as active switch. Then enter configuration mode and make changes to use different VSL port channel number for local VSL port members. Once completed, reload this switch to start auto-merge procedure again."
"VS_MERGE","4","STDBY_VSL_PO_EXIST","Overwriting existing port channel [int] with standby VSL port channel","There exists a port channel that uses the same channel number as standby VSL port channel. Overwrite the existing port channel configuration with standby VSL port channel configuration.","If the existing port channel configuration is required, then reconfigure the port channel and its related configuration with a different port channel number"
"VS_MERGE","6","SAVE_MERGED_CFG","Saving merged configuration...","The merged configuration is being copied to startup-config.","No action is required."
"VS_MOD_PROV","3","AUTO_ADD_SLOT_FAILED","Auto module provision add failed for chassis [dec] slot [dec]","A call to add module provisioning information to a red-black tree (RBTree) has failed.","No action is required."
"VS_MOD_PROV","3","AUTO_REM_SLOT_FAILED","Auto module provision remove failed for chassis [dec] slot [dec]","Remove module provisioning slot information failed.","Reproduce the issue after execute 'debug switch virtual ridprom all'CLI on both active RP and SP before bringing up standby chassis. Collect the debug trace information from console."
"VS_MOD_PROV","3","ICC_PAK_NULL","Pak pointer for icc msg is NULL","An ICC packet buffer pointer could not be obtained.","No action is required."
"VS_MOD_PROV","3","MSGBUF_PTR_NULL","Data buffer pointer is NULL","A message or data buffer pointer could not be obtained.","No action is required."
"VS_MOD_PROV","3","MTU_ZERO","MTU size is zero due to ISSU session negotiation failure.","ISSU return negotiated message size equal to zero for this session. Most likely, there is an issue with IPC transport mechanism that causes ISSU negotiated message to time out.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"VS_MOD_PROV","3","NO_AUTO_PROV_PROC","Unable to create VS Auto Module Prov process.","The virtual switch automatic module provisioning process could not be created.","No action is required."
"VS_MOD_PROV","3","NO_AUTO_PROV_WB","Unable to create watched boolean(s). vs_auto_prov_add_wb = , vs_auto_prov_ha_wb =","The specified watched booleans could not be created.","No action is required."
"VS_MOD_PROV","3","SEND_PROV_DATA_FAILED","Sending of module provision info to ACTIVE failed.","The ICC sending of module provisioning information from the standby module to the active module failed.","No action is required."
"VSPA","3","FIPSERROR","FIPS POST Failed.","The power-on self test (POST) failed. The crypto engine is disabled.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VSPA","3","HARDWARE_ERR","WS-IPSEC-3 Error: %s","A hardware error occurred on the WS-IPSEC-3, causing an interrupt. The module will automatically reload in the case of an unrecoverable error.","Copy the error message (and any recent error messages) as it appears on the console. In case of a WS-IPSEC-3 crash, collect the crashinfo file from the sup-bootdisk. Contact your Cisco technical support representative and provide the gathered information."
"VSPA","4","FIPS_CRNG_NOTIFY","Same Random Number was generated twice in succession!","The same random number was generated twice in succession.","No action is required."
"VSPA","5","FIPSNOTIFY","FIPS POST Successful.","The power-on self test (POST) succeeded.","No action is required."
"VSPA","5","ILLEGALCLEAR","Illegal Clear Packet: Src =%u.%u.%u.%u, Dst =%u.%u.%u.%u, Proto =%u","An unexpected clear (unencrypted) packet was received from the WAN.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VSPA","5","REPLAYERR","Replay Error: Current Seq. No. =%u, Highest Seq No. =%u","A replay error was detected on IPsec inbound processing.","Make sure the IPSec packets are not being reordered in the network, such as by a QoS process."
"VSPA","5","SELCHECKERR","Selector Check Error: Src =%u.%u.%u.%u:%u, Dst =%u.%u.%u.%u:%u, Proto =%u, saidx =%u","A packet was received that did not fall within the appropriate selector range.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VSPA","5","SEQOVERFLOW","Sequence number overflow: Src =%u.%u.%u.%u, Dst =%u.%u.%u.%u, Proto =%u, saidx =%u","The sequence number in the security association has overflowed.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"VS_PARSE","3","ALLOC_ICC_PAK_FAIL","Unable to allocate memory for ICC packet","A packet allocation failed for sending an ICC message to do the specified operation.","No action is required."
"VS_PARSE","3","CONFIG_MISMATCH","[chars]","The VSL configuration in the standby module's configuration differs from either the active module's startup configuration or the active module's running configuration.","Use the show switch virtual redundancy config-mismatch command to display the mismatch configuration. If the standby configuration differed from the active's startup configuration or the active's running configuration, you must fix the discrepancy in VSL configuration between the active and standby switch. Then, enter a write mem command to update the standby's startup configuration and reload the standby."
"VS_PARSE","3","MISMATCH","%s","Configuration mismatches were detected between the active and standby units in either the running configuration, the startup configuration, or the EARL operating mode.","Enter the show switch virtual redundancy mismatch command to display the mismatch. Correct any discrepancy in the VSL configuration between the standby switch's configuration and the active switch's startup configuration or running configuration. Correct any discrepancy in the EARL operating mode between the standby switch's configuration and the active switch's configuration. Enter the write mem command and reload the standby switch."
"VS_PARSE","3","VS_HWSB_CREATE_FAIL","Unable to create VS HW SB for vslot [int], port [int]","An attempt to create a virtual switch hardware standby has failed due to unknown reasons. During virtual switch mode conversion, the standby VSL port would flap when attempting to reconfigure the port on the active. It is recommended to have at least two physical links for a virtual switch mode conversion attempt in order to avoid a dual active scenario due to this error.","No action is required."
"VS_PARSE","4","CONFIG_WARNING","%s: %d","Errors were detected while parsing the virtual switch (VS) configuration. The switch will be in standalone mode with a switch number setting.","If the VS conversion process is successful in bringing up virtual switch mode, no action is required. If the process fails, check the VS configuration."
"VS_PARSE","4","NO_VSL_CONFIG","No VSL interface is configured","There are no VSL interfaces configured. This switch cannot communicate with the other switch to form the virtual switch.","No action is required."
"VS_PARSE","4","SWITCH_NUM","%s: %d","A valid ROMMON variable SWITCH_NUMBER must be configured before the switch can be brought up as a virtual switch.","Configure a valid SWITCH_NUMBER in ROMMON."
"VS_PORT_QOS_ACL","3","PIDX_BASE_MSG_FAILED","Setting of PIDX_BASE to value [hex] failed","A message from the TCAM application to set the Tycho's PDIX_BASE has failed.","No action is required."
"VTSP","3","UNAVAILABLE","vtsp_do_call_history: %s","Allocate or insert an active VTSP call record into call history list failed.","No action is required."
"VTSP","3","UNAVAILABLE","%s","Internal Finite State Machine Error.","Contact your technical support representative, include the full text of the error message."
"VTSP","3","UNAVAILABLE","Call can't be hairpinned. cdb 0x%x, dst_cdb 0x%x, dst_call_id %d","A DSP-less call could not be hairpinned.","Check the dial-peer configuration."
"VTSP","3","UNAVAILABLE","Call hairpinning failed. cdb 0x%x, dst_cdb 0x%x, dst_call_id %d","A DSP-less call could not be hairpinned.","Under heavy traffic, this failure may happen because no TDM resources were available. Contact your technical support representative, include the full text of the error message."
"VTSP","3","UNAVAILABLE","DSP timeout on channel %s, event %d: DSP ID=0x%x: %s","Timeout on DSP response.","The DSP has been automatically reset. If problem persists, contactyour technical support representative"
"VTSP","3","UNAVAILABLE","VTSP call disconnect failed. channel id %s, ret %d","VTSP call disconnect could not be successfully passed and it may result hung calls.","Contact your technical support representative. Report the configuration and full text of the error message."
"VTSP","3","UNAVAILABLE","channel %s, DSP ID 0x%x: status=0x%x message=0x%x text=%s","The DSP reported a fatal error. All calls on the DSP were dropped and a DSP reload was attempted.","Verify that the DSP reloaded properly by attempting to place a call on the affected voice port. Contact your technical support representative, include the full text of the error message."
"VTSP","3","UNAVAILABLE","channel:%s DSP ID:0x%x Message ID:0x%x","A message could not be sent to the DSP. The call continued but may have experienced problems.","Verify that the DSP is still functioning properly by attempting to place a call on the affected voice port. Contact your technical support representative, include the full text of the error message."
"VTSP","3","UNAVAILABLE","hairpin peer cdb does not exist, cdb 0x%x, dst_call_id %d","A hairpin call setup failed because the other call leg does not exist.","Contact your technical support representative. Report the configuration, and the full text of the error message."
"VTSP","3","UNAVAILABLE","no free event structure available from %s for DSP message","There were no event structures remaining in the system pools to alert the router of a voice or signaling event.","Check that the voice port for which the event was reported is still operational. If not, clear the voice port."
"VTSP","3","UNAVAILABLE","voice port %s: call connection id [0x%x 0x%x 0x%x 0x%x]","There was a capabilities mismatch between the two call legs. capabilities are negotiated between call legs for CODEC, VAD and FAX rate.","Check that the dial peer configuration is appropriate for the interface in question. Also check that and configuration on the interface is correct."
"VTSP","3","UNAVAILABLE","vtsp_call_block allocate failed","RBTreeCreate failed.","Add more memory"
"VTSP","4","UNAVAILABLE","Invalid FSM Input on channel %s: state=%s event=%d","Internal state machine illegal input. This message represents an internal software fault and may manifest itself as dropped or hung calls.","Contact your field service representative if indication is coincident with dropped or hung calls."
"WARMUPGRADE","3","CHECKSUM","%s image checksum mismatch.","The checksum of the image in memory is different from the expected checksum","Check whether the image file is complete and uncorrupted"
"WARMUPGRADE","3","FORMAT","Unknown image file format.","Warm upgrade could not recognize the format of the image file","Check whether the specified image is a valid IOS executable in a supported format. Check release notes for supported formats"
"WARMUPGRADE","3","UNAVAILABLE","%s image checksum mismatch.","The checksum of the image in memory is different from the expected checksum","Check whether the image file is complete and uncorrupted"
"WARMUPGRADE","3","UNAVAILABLE","%s image size mismatch.","The size of the image in memory is different from the expected size","Check whether the image file is complete and uncorrupted"
"WARMUPGRADE","3","UNAVAILABLE","Image file decompression failure.","Warm upgrade could not decompress the image file","Check whether the image file is complete and uncorrupted"
"WARMUPGRADE","3","UNAVAILABLE","Image file open/read failure.","Warm upgrade could not open or read from the image file specified","Check whether the specified image is present at the desired location and has the required read permissions. If the location is remote, check whether the connectivity is there."
"WARMUPGRADE","3","UNAVAILABLE","Unknown image file format.","Warm upgrade could not recognize the format of the image file","Check whether the specified image is a valid IOS executable in a supported format. Check release notes for supported formats."
"WCCP","1","UNAVAILABLE","Failed to derive service %s%s%s from service-list %s","The WCCP Access Control List used to define the specified closed service has been modified and can no longer be used to create the service. The service has been marked as inactive. Either change the configuration to an Open service or update the ACL to correctly identify the desired service","Update the service-list ACL to correctly define the desired service"
"WCCP","1","UNAVAILABLE","Service %s%s%s lost on WCCP Client %i","WCCP has lost the service associated the specified WCCP Client","Verify the operation of the specified WCCP Client"
"WCCP","1","UNAVAILABLE","Web Cache %i lost","The router has lost contact with the specified Web Cache","Verify operation of specified Web Cache."
"WCCP","3","UNAVAILABLE","Service %s%s%s, invalid access-list entry (seq:%d reason:%s)","The Access Control List associated with the specified WCCP service contains an incompatible entry. The hardware cannot process the resultant merged access list and will fall back to software based etflow switching","Update the Access Control List to remove or change the incompatible entry"
"WCCP","3","UNAVAILABLE","Unable to add WCCP subblock on interface %s","An internal error indicating that the WCCP process was unable to attach interface specific service information","Ensure that there is enough memory available for all processes"
"WCCP","3","UNAVAILABLE","Unable to allocate WCCP subblock on interface %s","An internal error indicating that the WCCP process was unable to allocate memory to hold interface specific service information","Ensure that there is enough memory available for all processes."
"WCCP","5","UNAVAILABLE","Service %s%s%s acquired on WCCP Client %i","WCCP has acquired a service on the specified WCCP Client","LOG_STD_NO_ACTION"
"WCCP","5","UNAVAILABLE","Service %s%s%s mismatched on WCCP client %i","WCCP has rejected a mismatched service on the specified WCCP client","Amend the WCCP service definition"
"WCCP","5","UNAVAILABLE","Web Cache %i acquired","The router has acquired the specified Web Cache","LOG_STD_NO_ACTIOn."
"WSHTF","1","UNAVAILABLE","%s %d","The HT-Fpga data plane driver failed to get resources to attach its data structures to the global table. System is running low on memory","Copy the error message exactly as it appears along with the dump of show memory summary, and report it to your technical support representative."
"WSHTF","1","UNAVAILABLE","%s, buffer replacement failed, no buffers available","The HT-Fpga data plane driver could not secure replacement bufferspacket reception","The router either requires more packet memory - consider upgrade.Or some software module is holding onto the receive buffers andnot releasing them back to the driver. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"WSHTF","3","UNAVAILABLE","Device ID seen as %#x, expected %#x. Bus number %#x device number %#x.","The software could not recognize the data plane chip.","Copy the error message exactly as it appears and report it to your technical support representative."
"WSHTF","3","UNAVAILABLE","attempt to send giant packet on %s (%d bytes from %x, max allowed %d)","A process inside the router is attempting to send an oversized packet","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"WSIPC","1","UNAVAILABLE","%d/%d %s allocation failure","Memory allocation failure","Copy the error message exactly as it appears on the console or in the system log. If you cannot determine the nature of the error from the error message text, call your Cisco technical support representative and provide the representative with the gathered information."
"WSIPC","3","UNAVAILABLE","%s %s","Failed to create IPC port on RP.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"WSIPC","3","UNAVAILABLE","%s (%u)","The ID associated with an IPC card is either missing, duplicated, or cannot be created.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"WSIPC","3","UNAVAILABLE","%s (%u)","The IPC application tried to send a message that was larger than IPC could handle. The message was not transmitted.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"WSIPC","3","UNAVAILABLE","%s (%u)","The slave IPC cannot register with master.It cannot exchange messages with the master.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"WSIPC","3","UNAVAILABLE","%s (slot %d): %s","An IPC error was detected","Copy the error message exactly as it appears, and report it to your technical support representative."
"WSIPC","3","UNAVAILABLE","%s","An IPC card has registered itself to the IPC master twice. The card malfunctioned and its IPC is not active.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"WSIPC","3","UNAVAILABLE","%s","An error detected during line card ipc reinitialization after an RP switchover.","This can be because of system is operating under heavy traffic at the time of RP switchover. If line card software can not proceed after this error, linecard will be deactivated and recovered."
"WSIPC","3","UNAVAILABLE","%s","Failure to get packet buffers","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"WSIPC","3","UNAVAILABLE","%s","Nonblocking IPC command queue initialization failure.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"WSIPC","3","UNAVAILABLE","Cannot find hwidb for interface(%u/%u)","Interface identifier does not exist for the interface addressed by the corresponding IPC message.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"WSIPC","3","UNAVAILABLE","Event %u from slot%u: %s","IPC event processing operational errors.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"WSIPC","3","UNAVAILABLE","For port (%s): %s fails (cause: %s)","The IPC kernel port related system call failure.","Copy the error message exactly as it appears, and report it to your technical support representative."
"WSIPC","3","UNAVAILABLE","IPC command %u (slot%u/%u): %s","IPC command processing operational errors.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"WSIPC","3","UNAVAILABLE","Null %s ipc message","An empty IPC message, which is not expected to be received.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"WSIPC","3","UNAVAILABLE","System call for command %u (port %u/%u) : %s (Cause: %s)","IPC kernel system call error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"WSIPC","3","UNAVAILABLE","port (%s) already exists","The port to be created unexpectedly exists.","Copy the error message exactly as it appears, and report it to your technical support representative."
"WSMA","3","UNAVAILABLE","PROCESSING FAILED","The processing of WSMA DHCP Option 43 message failed.","Need to verify the WSMA DHCP option 43 message is in correct format. If not, correct it and send this message again."
"WSMA","5","UNAVAILABLE","PROCESSING DONE","The processing of WSMA DHCP Option 43 message succeeded.","None."
"WiSM","5","DUP_SRVC_IP","Service IP [IP_address] of Controller [dec]/[dec] is same as Controller [dec]/[dec]","The Cisco Wireless Services Module software detected that a controller is assigned with an IP address on its service port that is being used by another controller.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"WiSM","5","RESET","Controller [dec]/[dec] not responding, WiSM in slot [dec] is being reset","The Cisco Wireless Services Module in the specified slot is being reset because one of the controllers failed to respond to 12 consecutive keepalive requests.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"WiSM","5","STATE","Controller [dec] in slot [dec] is [chars]","A change has been detected in the Cisco Wireless Services Module controller. If the controller status is Oper-Up, WCP communication between the controller and the supervisor engine is up or else it is down.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"WS_ALARM","6","INFO","[chars] [chars] [chars] [chars] [chars]","Displays alarm assertion or deassertion information.","No action is required."
"WS_IPSEC_3","3","FIPSERROR","FIPS POST Failed.","Power On Self Test failed. Crypto engine disabled.","Contact TAC."
"WS_IPSEC_3","3","HARDWARE_ERR","WS_IPSEC_3 Error: [chars]","A hardware error occured on the WS_IPSEC_3 causing an interrupt","Copy the error message (and any recent error messages) as it appears on the console. In case of a WS_IPSEC_3 crash, collect the crashinfo file from the sup-bootdisk. Contact your Cisco technical support representative and provide the gathered information. The SPA will automatically reload itself in case of a crash"
"WS_IPSEC_3","4","FIPS_CRNG_NOTIFY","Same Random Number was generated twice in succession!","Same random number was generated twice in succession.","No Action Required."
"WS_IPSEC_3","5","FIPSNOTIFY","FIPS POST Successful.","Power On Self Test succeeded.","No Action Required."
"WS_IPSEC_3","5","ILLEGALCLEAR","Illegal Clear Packet: Src =[int].[int].[int].[int], Dst =[int].[int].[int].[int], Proto =[int]","An unexpected clear packet was received from the WAN.","If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support"
"WS_IPSEC_3","5","REPLAYERR","Replay Error: Current Seq. No. =[int], Highest Seq No. =[int]","Failed anti-replay check on IPsec inbound processing.","Make sure the IPSec packets are not reordered in the networks. Follow up with TAC."
"WS_IPSEC_3","5","SELCHECKERR","Selector Check Error: Src =[int].[int].[int].[int]:[int], Dst =[int].[int].[int].[int]:[int], Proto =[int], saidx =[int]","A packet was received that did not fall within the appropriate Selector range.","If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"WS_IPSEC_3","5","SEQOVERFLOW","Sequence number overflow: Src =[int].[int].[int].[int], Dst =[int].[int].[int].[int], Proto =[int], saidx =[int]","The sequence number in the Security Association has overflowed.","If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"X25","2","UNAVAILABLE","Interface %s, Illegal state %s when P4","An internal software error occurred.","If any of these messages recur, call your technical support representative for assistance."
"X25","3","UNAVAILABLE","in x25_timer NULL lci_idb %x","An internal software error occurred.","Copy the message exactly as it appears, and report it your technical support representative."
"X25","3","UNAVAILABLE","%d is not a valid X.25 configuration ID","This message occurs when an invalid configuration id is used","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"X25","3","UNAVAILABLE","%s : Lower layer protocol is not available","The required lower layer service is unavailable.","Check your configuration or contact your technical support representative for assistance."
"X25","3","UNAVAILABLE","%s : Unable to identify lower layer protocol","IDB is not using X25 and IDB is not capable of supporting CMNS.","Check your hardware configuration or contact your technical support representative for assistance."
"X25","3","UNAVAILABLE","%s","This message occurs when configuring an X.25 service.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"X25","3","UNAVAILABLE","%s","This message occurs when deconfiguring X.25 service.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"X25","3","UNAVAILABLE","Attempt to %s.","The user attempted an illegal configuration.","The error will indicate what illegal action was attempted. The user should check their configuration and if necesarry contact technical support representative for assistance."
"X25","3","UNAVAILABLE","Can't find bfe host address %i to delete","An internal software error occurred.","If any of these messages recur, call your technical support representative for assistance."
"X25","3","UNAVAILABLE","Error substituting regular expression for XOT DNS destination pattern","This message occurs when the regular expression substitute utility fails to arrive at X.25 hostname pattern to be sent to DNS for address resolution","Correct the X.25 route command's DNS substitution pattern"
"X25","3","UNAVAILABLE","Interface %s LCI %d Compression Version mismatch expected %x received %x","An internal software error occurred. The PBP header has a mismatched version field. The version is checked on each received packet.","Copy the message exactly as it appears, and report it your technical support representative."
"X25","3","UNAVAILABLE","Interface %s LCI %d Decompression size error","An internal software error occurred. The PBP header has an uncompressed packet size field. Each uncompressed packet size is checked against this field.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"X25","3","UNAVAILABLE","Interface %s LCI %d Decompression sync error. expected %d got %d","An internal software error occurred. The PBP header has a sync field. The sync field (8 bits) is checked on each received packet.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"X25","3","UNAVAILABLE","Interface %s LCI %d low-level stac compression error","A Stacker compression algorithm internal error or shortage of buffer space was encountered during a compression operation. This should never happen.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"X25","3","UNAVAILABLE","Interface %s, Delete: lci %d not found in %s table","An internal software error occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"X25","3","UNAVAILABLE","Interface %s, LCN %d already in timer queue, new time %#Ta","An internal software error occurred.","If any of these messages recur, call your technical support representative for assistance."
"X25","3","UNAVAILABLE","Interface %s, PVC %d, %s","A switched PVC cannot be connected. The final [chars] text string in the message represents the state of the PVC. These text strings can also appear in show x25-vc output. For more information, refer to the show x25-vc documentation in the Router Products Command Reference publication.","Validate the configuration of the PVCs at both ends of the connection, and reconfigure them if necessary."
"X40G","2","TCAM_MGR_CRIT_ERR","GTM ERROR: [chars] ([dec])","An X40G TCAM critical error was detected.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"X40G","3","TCAM_MGR_ERR","GTM ERROR: [chars] ([dec])","An X40G TCAM MGR interaction error was detected.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"X40G","3","TCAM_MGR_HW_ERR","GTM HW ERROR: [chars] ([dec]) [[dec]:[hex]]","An X40G TCAM hardware error was detected.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"X40G","3","TCAM_MGR_HW_PERR","GTM HW ERROR: [chars] ([dec])","An X40G TCAM interface parity error was detected.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"X40G","4","TCAM_MGR_ALLOC_ERR","[chars] NP ([dec]), Region Id ([dec])","An NP TCAM entry allocation failure was detected.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the remote command module sh platform software xtcammgr instance info command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the gathered information."
"X40G","5","TCAM_MGR_INFO","[chars]","An X40G TCAM driver error was detected.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"X40G_PC_QOS","3","X40G_EXCEED_NUM_QUEUES","%Exceed number of supported queues for this interface","Not available.","Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"X40G_PC_QOS","3","X40G_WRED_QLIMIT","%Queue limit and WRED cannot be configured together","Not available.","This error indicates a qos policymap configuration error occured. Qos processing on the interface might not work as expected. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"X40G_PC_QOS","4","X40G_PC_PMAP_INCOMPATIBLE","Warning - Policymap attached to port-channel EVC is incompatible with X40G member link.","Policymap attached to port-channel EVC is with an X40G member link.","Remove policymap attached to port-channel EVC before adding a X40G member link to port-channel."
"X40G_QOS","3","ACTN","[chars]","The x40g qos client detected a qos feature processing error event, specified in the message","This error indicates a qos policymap configuration error occured. Qos processing on the interface might not work as expected. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"X40G_QOS","3","CFN","[chars]","The x40g qos client detected a classification configuration error event, specified in the message.","This error indicates a qos policymap configuration error occured. Qos processing on the interface might not work as expected. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"X40G_QOS","3","NOMEM","Memory Allocation Failure - [chars])","Memory required by the qos client to service one or more Network Processors could not be allocated.","This error may indicate that more memory must be installed on the affected card or platform in order to service all the features and related entities enabled via the configuration. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"X40G_QOS","3","NP","[chars]","The x40g qos client detected an npu programming error event, specified in the message.","This error indicates a qos policymap configuration error occured. Qos processing on the interface might not work as expected. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"X40G_QOS","3","PMAP_CONFIG","[chars]","QoS processing on the interface specified in the msg is not functional","This configuration error is not considered fatal to the operation of the Network Processors. The software is designed to detect and report the error condition. Please refer to the cisco.com documentation for configuration to correct the problem."
"X40G_QOS","3","PRFL","[chars]","The x40g qos client detected a hardware profile run out. Hardware profile type is mentioned in the message","Identify the QoS hardware profile that got exhausted on the ES+ linecard. Modify the QoS configuration on the interface such that it can get a QoS profile shared with any other policymap on linecard or else remove policymap from the interface. Else Qos processing on the interface might not work as expected. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"X40G_QOS","3","SVI_PMAP","[chars]","Only one policymap is allowed to be attached to either direction of interface vlan at a time.","Please remove previous attached policymap and reattach the policymap. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"X40G_QOS","4","CFG","[chars]","When applying policymap, configuration may be changed by the NP because of hardware support","This error indicates a qos policymap configuration error occured. Qos processing on the interface might not work as expected. Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"XCONNECT","3","CONFIG","%s","An invalid XCONNECT configuration or an error in processing the XCONNECT configuration has occurred.","No action is required."
"XCONNECT","3","ILLEGAL","%s","An illegal event has been processed by the XCONNECT subsystem.","No action is required."
"XCONNECT","5","PW_STATUS","%s","An event caused the pseudowire to change status.","No action is required."
"XCONNECT","5","REDUNDANCY","%s","An event caused the XCONNECT redundancy facility to generate a switchover to the specified backup member.","No action is required."
"XCPA","3","HWVER","bay [[dec]] incompatible microcode (hw:[int].[int], [int].[int]).","An incompatability exists between the port adapter hardware and the version of microcode that the system image attempted to load.","Use the show microcode command to display the default and configured versions of microcode for this port adapter hardware type. Assure that the correct version of microcode exists in flash. Use the microcode reload command to load the microcode. If the error still occurs, record the output from the following commands: show tech, show microcode, dir slot0:, dir slot1:, show log. Provide this information to your technical support representative."
"XCVR","3","UNKNOWN_SFP_INSERTED","Unknown SFP inserted [chars]","An unknown Small Form Factor Pluggable (SFP) transceiver has been inserted.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","3","BYPASSFOFNEGO","Bypassing FOF ISSU client %s (%u) nego for XDR client %s, slot %s as FOF ISSU client is not present in %s image.","This XDR client has a dependency on another ISSU client due to having foreign-owned fields (FOFs). Because the ISSU client that owns the FOFs is not in the image, the XDR client will not wait for that client to finish ISSU negotiation. The missing client must be added to the image.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","3","CLIENTISSUBADENTITY","Unable to register ISSU entity for [chars], reason: [chars]","Unable to register this XDR client's ISSU entity due to problems with registering the item given as a reason in the error message. ISSU will stop working for this client and may lead to unpredictable behavior.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","3","CLIENTISSUBADGROUP","New m/cast group (slots [chars]) has multiple members before nego complete.","A new multicast group has been created with multiple slots before ISSU negotiation for each client has completed. This condition will lead to unpredictable results.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","3","CLIENTISSUBADNEGOMSG","Unexpected nego msg - slot [chars], client [chars], ctxt [dec]","XDR has received a negotiation message unexpectedly as this client is either not ISSU aware or has already completed negotiation for this slot. This condition is likely a precursor to unpredictable behavior for this client.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","3","CLIENTISSU_FOF_NEGOFAIL","ISSU negotiation failed for FOF client %u, for peer %s (ISSU peer %d), blocking ISSU client %s (%d) reason - %s","The ISSU negotiation failed for a client that has registered ISSU foreign-owned field (FOF) client dependencies. The dependent clients on this slot and the remote slot cannot interoperate in SSO mode. Synchronizing of information to and from this slot cannot proceed for this client and the dependent clients. Enter the show xdr multicast command for full details.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, and show xdr multicast commands and your pertinent troubleshooting logs."
"XDR","3","CLIENTISSU_FOF_REGERROR","ISSU client %s (%d), entity %d, message %d (%s), failed ISSU FOF registration: %s, reason: %s,","This ISSU client has a message containing a foreign-owned field (FOF) owned by another client, but the client failed to register this dependency. This is an internal software error.","Update to a later software release."
"XDR","3","CLIENTISSUNEGATIVEPADDING","Negative padding for [chars], slots [chars], msg [dec] (padded: [dec], unpadded: [dec])","An internal error occurred involving a mismatch of internal data structures.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","3","CLIENTISSU_NEGOFAIL","ISSU negotiation failed for [chars], slot [chars] [chars]","ISSU negotiation failed. The XDR client on this slot and the remote slot cannot interoperate in SSO mode. Synchronizing of information to and from this slot will not happen for this client and dependent clients. Seethe output of the show xdr multicast command for full details.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","3","CLIENTISSUNEGONOTDONE","Attempting to push send XDR message ([dec]) to slots [chars] for [chars] before nego complete.","An internal error occurred that may result in unpredictable behavior.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","3","CLIENTISSU_NEGOREGERROR","XDR client %s, failed ISSU negotiation result notification registration for ISSU client %s (%d), reason: %s,","This client has a dependency on the successful ISSU negotiation of another client and has failed to register this dependency. This is an internal software error.","Update to a later software release."
"XDR","3","CLIENTISSU_NEGOUNREGERROR","Failed to unregister ISSU negotiation result notification registration for ISSU client %s (%d), reason: %s,","This client has a dependency on the successful ISSU negotiation of another client and has failed to unregister this dependency when not required. This is an internal software error.","Update to a later software release."
"XDR","3","CLIENTISSUNOMSGGRP","Cannot determine ISSU message group for slot %d. Unknown %s","Because the line card type for the specified slot is not recognized, the ISSU client cannot determine the set of ISSU messages to be used between the local and remote slot. This condition might be due to a new line card type.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","3","CLIENTISSU_PUSHFAIL","Attempting to push send XDR message ([chars]) to slots [chars] via client [chars] failed due to [chars]","An internal error occurred that may result in unpredictable behavior.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","3","CLIENTISSU_REGERROR","ISSU client [dec] ([chars]), entity [dec], failed ISSU registration: [chars]","The ISSU negotiation failed for this XDR client. This is a software error.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","3","CLIENTISSUSENDFAILED","Can't send XDR client ISSU nego msg: reason [chars], slot [chars], client [chars]","XDR has failed to send an ISSU negotiation message for the given client. The slot will be marked as ISSU-unaware, and communication with this slot will proceed on that basis. However, this is likely to lead to unpredictable behavior.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","3","CLIENTISSUSTARTNEGOFAIL","Can't start nego: reason [chars], slot [chars], client [chars], sid [dec]","XDR has failed to start ISSU negotiation with the remote slot for the reason given. The slot will be marked as ISSU-unaware, and communication with this slot will proceed on that basis. However, this is likely to lead to unpredictable behavior.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","3","ISSUBADREGPARAMS","Client [chars] trying to register with incomplete ISSU support.","This client does not properly support ISSU and will be registered as not supporting ISSU.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","3","ISSUCAPNEGOFAIL","Client [chars] failed to [chars] capability/ies due to [chars]","An internal software error occurred. The capability negotiation failed unexpectedly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","3","ISSU_ENUM_ERROR","Enum for [chars] ([chars] component) is not ISSU-compliant: [chars]","The given enumeration is not ISSU-compliant for the reason given. Unpredictable behavior will result when interoperating with different Cisco IOS versions.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","3","ISSUINITFAIL","Unable to register XDR ISSU [chars], reason: [chars]","Unable to register the given XDR ISSU parameter due to the reason given. This will stop ISSU working for this client and may lead to unpredictable behavior.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","3","ISSU_NEGOFAIL","ISSU negotiation failed for XDR, slot [chars] [chars]","ISSU negotiation failed. XDR on this slot and the remote slot cannot interoperate. Synchronizing of information to and from this slot for all XDR clients will not be allowed.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","3","MSGSIZEFAIL","The IPC message size is out of boundsThe ipc_msg_size is : [dec] while the maximum size we can handle is theXDR_IPC_BUFFER_SIZE : [dec] .","The size of the IPC message that was received is larger than the maximum size that can be handled.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","3","PRIOCLIENTISSU_NEGOFAIL","ISSU negotiation failed for [chars], slot [chars] [chars]","ISSU negotiation failed for a core XDR client. XDR on this slot and the remote slot cannot interoperate in SSO mode. Synchronizing of information to and from this slot will not happen for any XDR client.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","3","XDRBADSLOT","An invalid slot %d was obtained during - %s","An invalid slot was obtained.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show xdr linecard, and show xdr multicast commands and your pertinent troubleshooting logs."
"XDR","3","XDRDEQUEUE","Failed to dequeue from [chars] with [dec] elements still queued","A queueing failure has occurred. A nonempty queue could not be dequeued.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","3","XDRIPC","XDR IPC error on multicast-group [hex] due to [chars].","A general IPC-related error occurred, which may prevent transfer of data to other peers using the IPC mechanism .","Enter the show xdr multicast command immediately after this error. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","3","XDRMCASTJOIN","Attempt to join [chars] to [chars] failed because client [chars] returned an error","An internal error occurred that may result in unpredictable XDR behavior.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","3","XDRMCASTJOINREQ","Client [chars] returned an invalid response to a join request for groups [chars] and [chars]","An internal error occurred that may result in unpredictable XDR behavior.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","3","XDRMCAST_PEER_BINDING","XDR peer [chars] bind to group [chars] (was bound to [chars]): [chars]","An internal error occurred that may result in unpredictable XDR behavior.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","3","XDRNOMEM","XDR failed to allocate memory during [chars] creation.","Allocation of memory by the XDR subsystem has failed. This failure may result in unpredictable XDR behavior.","Make sure that there is enough memory for the operations being performed by your system. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","3","XDROOS","Received an out of sequence IPC message. Expected [dec] but got [dec]","An out-of-sequence or unknown IPC message was received. This condition indicates that an IPC is not working properly.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","3","XDRPEER","An XDR peer error for slot [chars]. Due to [chars].","An error relating to an XDR peer has occurred.","Enter the show xdr linecard command. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","3","XDRQUEUE","XDR queue error: [chars].","The XDR subsystem queueing operation failed. This may result in unpredictable behavior of XDR.","Make sure that there is enough memory for the operations being performed by your machine. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","3","XDRSLOTFROMMASK","Cannot determine slot from mask [chars] (client [chars])","Mapping from slot mask to slot has failed. During ISSU negotiation, the message destination cannot be determined, and the message will be dropped.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","6","CLIENTISSUBADRCVTFM","Failed to rcv_transform message - from slot [chars], client [chars], context [dec]","The system cannot perform an ISSU receive transform. This condition is likely due to an earlier failure in negotiation, or when one side of an ISSU-enabled XDR connection is out of synchronization with the other.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","6","CLIENTISSUBADTXTFM","Failed to xmit_transform message - to slot [chars], client [chars], context [dec]","The system cannot perform an ISSU transmit transform. This condition is likely due to an earlier failure in negotiation, or when one side of an ISSU-enabled XDR connection is out of synchronization with the other.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","6","CLIENTISSU_BLOCKED","Client [chars] cannot sync info to/from slot [chars] due to ISSU negotiation failure of client [chars]","This client depends on another XDR client for which ISSU negotiation has failed. As a result, this client is prevented from communicating with the remote slot. This is due to ISSU incompatibilities between the two images. Functionality for this client will revert to RPR mode.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","6","CLIENTISSU_UNBLOCKED","Client [chars] can now sync info to/from slot [chars] due to ISSU negotiation success of client [chars]","This client depends on another XDR client for which ISSU negotiation had previously failed but has now succeeded. As a result, this client can resume communication with the remote slot. Functionality for this client will revert to SSO mode.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","6","CLIENTISSUUNREG","Failed to unregister session - client [chars], slot [chars], reason [chars]","The system was unable to unregister this session. This condition will likely cause problems when reregistering.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","6","CLIENTNOTREGONRP","Client [chars] has registered on slot [chars] before RP.","The XDR client has registered on a non-RP card before an RP card. If this has occurred while toggling the client's registration status rapidly, it may be a transient problem that will resolve itself. If not, the client's status may be unpredictable, and ISSU negotiation (if platform is ISSU-aware) may not take place correctly.","Verify whether the client's registration status is the same on both the RP and the card on which the problem is reported by comparing the output of the show xdr client all command to see if the client is present or absent in both. If so, and no other error messages have been seen, then this is a transient issue and no further action is required. Otherwise, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","6","ISSUBADRCVTFM_DUMP","CSCsh95828 detected. Please collect 'show xdr linecard', 'show monitor event-trace xdr all', and the full system log, on both the RP and the related LC, and report this occurrence. Slot %s, data 0x%08x %08x %08x %08x %08x %08x %08x %08x","This message contains a decoded packet dump and trace log information for investigating CSCsh95828.","Copy the message exactly as it appears and contact your Cisco technical support representative."
"XDR","6","ISSUBADTXTFM","Failed to xmit_transform message - slot [chars], reason [chars]","The system was unable to perform an ISSU transform on an outgoing XDR header. The message will be ignored.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","6","ISSUCLIENTABSENT","ISSU client [chars] absent on slot [chars]. Client functionality may be affected.","The remote slot does not support this ISSU client. The software will handle this by reducing client functionality locally to continue in SSO mode, or by forcing the remote peer into RPR mode as appropriate. This is expected behavior in ISSU-capable systems.","No action is required."
"XDR","6","ISSUBADRCVTFM","Failed to rcv_transform message - slot [chars], reason: [chars]","The system was unable to perform an ISSU transform on an incoming XDR header. The message will be ignored.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","6","XDRDISABLEREQUEST","Peer in slot [chars] requested to be disabled due to: [chars]. Disabling linecard","The line card has requested to be disabled due to an error condition.","Enter the show monitor event-trace xdr command from the RP and the line card in question. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","6","XDRINVALIDHDRISSU","XDR ISSU negotiation message for client ([chars]) dropped (slots:[chars] from slot:[chars] context:[int] length:[int]) due to: [chars]","The XDR ISSU negotiation message was dropped for the reason given.","If the message occurred during an ISSU upgrade then it may be safely ignored. Otherwise: Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support."
"XDR","6","XDRIPCNOTIFY","Message not sent to slot [chars] because of IPC error [chars]. Disabling linecard. (Expected during linecard OIR)","A general IPC-related error has occurred that may prevent transfer of data to other peers using the IPC mechanism.","Enter the show xdr multicast and show xdr linecard internal commands immediately after this error. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","6","XDRIPCPEER","XDR IPC error occurred for peer in slot [chars] due to [chars][chars].","A general IPC-related error has occurred that may prevent transfer of data to other peers using the IPC mechanism.","Enter the show xdr multicast and show xdr linecard commands immediately after this error. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","6","XDRLCDISABLEREQUEST","Client [chars] requested to be disabled. [chars]","The line card has requested to be disabled due to an error condition.","Enter the show monitor event-trace xdr from the RP and the line card in question. 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","6","XDRMCASTINIT","XDR mcast subsystem initilisation error: [chars]","A failure occurred that prohibits the XDR client from registering with the core.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XDR","6","XDRREGISTRATION","XDR failed to register [chars] client due to [chars]","The XDR client specified in the message text could not be registered. A failure has occurred that prohibits the XDR client from registering with the core.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs."
"XOS","7","XOS_DM_DISPATCH","xos_dm_dispatch API cannot be called that does not own the XDM, xdm pid: %d, current pid: %d","The xos_dm_dispatch API was called by a process that is not the owner of that XDM. Only process that create the XDM instance can own it.","Please check your code and avoid invoking this API in a different process context."
"XOS","7","XOS_DM_WAIT","xos_dm_wait API cannot be called by a process that does not own the XDM, xdm pid: %d, current pid: %d","The xos_dm_wait API was called by a process that is not the owner of that XDM. Only process that create the XDM instance can own it.","Please check your code and avoid invoking this API in a different process context."
"XOS","7","XOS_DM_XDISPATCH","xos_dm_xdispatch API cannot be called that does not own the XDM, xdm pid: %d, current pid: %d","The xos_dm_xdispatch API was called by a process that is not the owner of that XDM. Only process that create the XDM instance can own it.","Please check your code and avoid invoking this API in a different process context."
"XOS","7","XOS_ONINT","XOS APIs cannot be called in a interrupt path","An XOS API was called in the interrupt path, this is currently not supported.","Please check your code and avoid using this API in the interrupt path"
"XOS","7","XOS_STUCK_TMR","XOS timer expired earlier than expected expiration time tree:%p time:%d.%d","The XOS timer handler was invoked earlier than expiration value of the timer","Please check expiration timer value set on the timer. Also, some OS infrastructures can roundup expiration time so that timer handler gets invoked earlier than expected"
"AAA","0","SELECT_CALL_FAILURE","TACACS server is not available for authentication, accounting and/or authorization.","TACACS server is not available for authentication, accounting, and authorization.","Ensure that the TACACS server is available."
"AAA","5","AAA_AUTH_ADMIN_USER","Authentication [chars] for admin user '[chars]'","Authentication for an admin user.","No action is required."
"AAA","5","AAA_AUTH_NETWORK_USER","Authentication [chars] for network user '[chars]'","Authentication for a network user.","No action is required."
"AAA","4","ATTRITBUTE_LEN_EXCEED","ACL Name too long : [chars]","The ACL name is too long.","No action is required."
"AAA","4","AVP_CORRUPT","[dec]th AVP is corrupted. RADIUS msgtype=[dec]. Prev AVP=[dec]len=[dec] offset=[dec] numAVPs=[dec].","An AVP is corrupted.","No action is required."
"AAA","4","COMPUTE_AVP_SIZE_FAILED","Received bad AVP :[address] , Value Ptr =[address], Value Len=[dec].","The system has received a bad AVP.","No action is required."
"AAA","3","CONSTRUCT_UDP_RCV_SOCKET_FAILED","Could not construct UDP RCV socket. [chars].([dec]:[chars])","The system could not construct a UDP RCV socket.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AAA","4","COPY_AVP_BLOCK_FAILED","Could not copy AVPs to block. [chars]","The system could not copy the AVPs to the block.","No action is required."
"AAA","6","CREATE_AVL_TREE","Creating AVL tree with [dec] entries","The system has created an AVL tree with entries.","No action is required."
"AAA","6","CREATE_CONFIG_FILE","Creating default aaaFile.cfg","The system has created a default entity in the local database.","No action is required."
"AAA","4","CREATE_RADIUS_MES_FAILED","Could not create RADIUS message. [chars]. numAVPs:[dec].","The system could not create a RADIUS message.","No action is required."
"AAA","3","CREATE_USR_TREE_FAILED","Could not create user AVL tree. Resason:[chars].","The system could not create a user AVL tree.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AAA","6","DB_ADD_BLACKLIST_USR","Adding blacklist user '[chars]' to AAA database.","The system has added a blacklist user to the AAA database.","No action is required."
"AAA","6","DB_ADD_USER","Adding user '[chars]' to AAA database.","The system has added a user to the AAA database.","No action is required."
"AAA","3","DB_INIT_FAILED","Error [dec] initializing database module [chars].","An error has occurred while initializing the database module.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AAA","3","DB_MODULE_INIT_FAILED","Could not initialize module [chars]. [chars].","The system could not initialize a module.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AAA","3","DB_RECORD_ADD_FAILED","Could not add record to database. [chars].","The system could not add a record to the database.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AAA","6","DELETE_CLIENT_ACCOUNT_DELETED","Delete client [hex]:[hex]:[hex]:[hex]:[hex]:[hex]because user account ([chars]) has been deleted.","The system deleted the specified client because the user account was deleted.","No action is required."
"AAA","6","DELETE_CLIENT_GUEST_ACCOUNT_EXPIRE","Delete client [hex]:[hex]:[hex]:[hex]:[hex]:[hex]because guest user account ([chars]) is expired","The system has deleted a client because a guest user account had expired.","No action is required."
"AAA","3","EAPMETHOD_ADD_FAILED","Unable to add method '[chars]' to EAP profile for user '[chars]'. [chars].","The system is unable to add a method to the EAP profile for the user.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AAA","3","EAPPROF_ADD_FAILED","Unable to add EAP profile for user '[chars]'. [chars].","The system is unable to add an EAP profile for a particular user.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AAA","3","FREELIST_ADD_FAILED","Unable to add to free list. [chars].","The system is unable to add to the free list.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AAA","3","FREELIST_DEL_FAILED","Unable to delete to free list. [chars].","The system is unable to delete to the free list.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AAA","6","FUNC_RUNNING","Running [chars]...","The system is running.","No action is required."
"AAA","3","GET_GUEST_START_TIME_FAILED","Could not get start time for guest user record. [chars].","The system could not get a start time for a guest user record.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AAA","4","GET_RADIUS_PROXYSTATE_FAILED","Could not get proxy state. [chars].","The system could not get a proxy state.","No action is required."
"AAA","6","GUEST_ACCOUNT_CREATE","Guest user account ([chars]) is created with lifetime ([dec]).","A guest user account has been created.","No action is required."
"AAA","6","GUEST_ACCOUNT_EXPIRE","Guest user account ([chars]) is expired","A guest user account has been created.","No action is required."
"AAA","3","GUEST_INFO_MALLOC_FAILED","Unable to allocate memory for guest account information of user [chars].","The system is unable to allocate memory for guest account information.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AAA","4","GUESTACCT_TIMERSET_FAILED","Unable to set timer for guest accounts. [chars].","The system is unable to set the timer for guest accounts.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AAA","4","GUESTUSER_DEL_FAILED","Unable to delete the user '[chars]'. [chars].","The system is unable to delete the user from the database.","No action is required."
"AAA","4","INVALID_AUTHENTICATOR","Unable to verify RADIUS message authenticator for mobile[hex]:[hex]:[hex]:[hex]:[hex]:[hex]. [chars]","The system has detected an invalid RADIUS message authenticator for the mobile device.","No action is required."
"AAA","4","INVALID_AUTH_REQ_TYPE","Invalid RADIUS authentication type [int] in AAA request","The system has detected an invalid RADIUS authentication type in the AAA request.","No action is required."
"AAA","4","INVALID_DATA_STRUCT","Could not validate the data structure - [chars].","The system could not validate a data structure.","No action is required."
"AAA","4","INVALID_MESSAGE_AUTHENTCATOR","Invalid message authenticator received in [chars] from[dec].[dec].[dec].[dec]","The system has detected an invalid message authenticator.","No action is required."
"AAA","4","INVALID_RADIUS_PKT_SIZE","RADIUS packet too small.","A RADIUS packet is less than its minimum size.","No action is required."
"AAA","3","INVALID_REQUEST","Invalid AAA request. [chars]","The system has received an AAA request with a null or invalid payload.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AAA","4","INVALID_REQUEST_TYPE","Received an invalid request type.([hex]).","The system has received an invalid request type that is not related to AAA or accounting.","No action is required."
"AAA","3","LDAP_CONNECT_SERVER_FAILED","LDAP DB Task [[dec]]: Connect to server failed (retry [dec]), rc= [dec] ([chars])","An LDAP DB task connect to the server has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AAA","3","LDAP_COPY_ATTR_FAILED","Could not copy attributes returned by LDAP server. [chars]. Max AVPs: [int]. Max Ints: [dec].","The system could not copy attributes returned by the LDAP server.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AAA","4","LDAPMSG_SEND_FAILED","Could not send a message to LDAP task. [chars].","The system could not send a message to the LDAP task.","No action is required."
"AAA","3","LDAP_TASK_FAILED","The main LDAP task failed. [chars]. Index: [dec]. Type: [dec].","The main LDAP task failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AAA","3","LDAP_TIMER_CALLBACK_FAILED","Could not perform timer callback. [chars].","The system could not perform a timer callback.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AAA","3","LIFETIME_SET_FAILED","Unable to reset the lifetime of [chars] account [chars] in localdatabase.","The system is unable to reset the lifetime of an account in the local database.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AAA","4","LIFETIME_VALUE_CORRUPT","Corrupted value of lifetime for guest user [chars]. Recommended Action    The value of the lifetime for a guest user is corrupted.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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.Error Message    %AAA-3-MEM_ALLOC_FAILED: Error allocating [dec] bytes on stack for message. Aborting..","An error has occurred when allocating memory off the stack for a message. The system is aborting.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AAA","4","MESSAGE_TYPE_UNKNOWN","Unable to send AAA request, Unknown message type :[dec]","The system is unable to send an AAA request, because of an unknown message type.","No action is required."
"AAA","4","MSCB_NOT_FOUND","Unable to find Mobile Station Entry for [hex]:[hex]:[hex]:[hex]:[hex]:[hex] .","The system is unable to find the Mobile Station Entry.","No action is required."
"AAA","4","MSG_RECV_FAILED","Failed to receive an incoming message. Error = [dec]:[chars].","The system has failed to receive an incoming message.","No action is required."
"AAA","4","PROCESS_ACC_FAILED","The system could not process accounting type [hex]. [chars].","The system could not process an accounting type.","No action is required."
"AAA","4","PROC_PROXY_REQ_FAILED","Could not process proxy request. [chars]. RADIUSLength=[dec] , Transport Len =[dec], Message code=[dec].","The system could not process a proxy request.","No action is required."
"AAA","4","PROC_PROXY_RESP_FAILED","Could not process a proxy RADIUS response. [chars]. RADIUS Length=[dec], Transport Length=[dec], Message Code=[dec].","The system could not process a RADIUS response.","No action is required."
"AAA","4","PROC_RADIUS_RESP_FAILED","The system could not process RADIUS response. [chars]. ResponseLength: [dec], Server: [dec].[dec].[dec].[dec] , ID:[dec] , Mobile:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system could not process a RADIUS response.","No action is required."
"AAA","3","PROXY_REQ_VALID_CRED_FAILED","Could not validate proxied request credentials. [chars].STA: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system could not validate the proxy request credentials.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AAA","4","RADACCTSRVR_STATESET_FAILED","Unable to set state of RADIUS accounting server [dec] to [dec]. [chars].","The system is unable to set the state of a particular RADIUS accounting server.","No action is required."
"AAA","4","RADAUTHSRVR_STATESET_FAILED","Unable to set state of RADIUS authentication server [dec] to [dec]. [chars].","The system is unable to set the state of a particular RADIUS authentication server.","No action is required."
"AAA","4","RADCLIENT_NOT_FOUND","RADIUS client [int].[int].[int].[int] not found in client list.","A RADIUS client is not found in the client list.","No action is required."
"AAA","6","RADIUS_IN_GLOBAL_LIST","RADIUS server [int].[int].[int].[int]:[int] [chars] in global list","A RADIUS server is in the global list.","No action is required."
"AAA","4","RADIUSMSG_SEND_FAILED","Unable to send RADIUS message to [chars]([int].[int].[int].[int]):[int] (MAC:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]). Reason : [chars].","The system is unable to send a RADIUS message to a specific host.","No action is required."
"AAA","6","RADIUS_ON_WLAN","RADIUS server [int].[int].[int].[int]:[int] [chars] on WLAN [int]","A RADIUS server is on a WLAN.","No action is required."
"AAA","4","RADIUS_RESPONSE_FAILED","RADIUS server [int].[int].[int].[int]:[int] failed to respond to request(ID [int]) for STA [hex]:[hex]:[hex]:[hex]:[hex]:[hex] / user '[chars]'","A RADIUS server failed to respond to a request for STA.","No action is required."
"AAA","4","RADIUS_RES_TRUNC","Truncating RADIUS response from server at AVP code [dec] for message [dec]","The system is truncating a RADIUS response from a server at the AVP code for a message.","No action is required."
"AAA","4","RADSERVER_NOT_FOUND","Could not find appropriate RADIUS server for WLAN [dec] - [chars]","Client authentication failed because a valid RADIUS server could not be found to service the request.","Verify the RADIUS server configuration and connectivity."
"AAA","4","RCV_FROM_UNKNOWN_SERVER","Received a [chars] from unknown server [int].[int].[int].[int]:[int]","The system has received a message from an unknown server.","No action is required."
"AAA","4","RCV_FROM_WRONG_PRT","RADIUS msg received from wrong switchport, [dec], dropping","A RADIUS message has been received from a wrong switchport, and the message is being dropped.","No action is required."
"AAA","4","RCV_PKT_TO_RFC3576_PRT_FAILED","Received an unexpected [chars] from [dec].[dec].[dec].[dec]","The system has received an unexpected message.","No action is required."
"AAA","4","REBUILD_DEFAULT_CONFIG","Rebuilding the default configuration for '[chars]'","The system is rebuilding the default configuration.","No action is required."
"AAA","6","RECREATE_ADMIN_LOGIN","Recreating admin login.","The system is recreating the default admin login.","No action is required."
"AAA","6","RECREATE_ADMIN_USR","Recreated the admin user.","The system created the admin user again on the local database.","No action is required."
"AAA","4","RFC3576_REXMT_FAILED","Could not retransmit RFC-3576 message to [int].[int].[int].[int]:[int]. [chars].","The system could not retransmit the RFC-3576 message to the host.","No action is required."
"AAA","3","RFC_SOCKET_ERROR","RFC3576 socket error [dec] on socket [dec]","An RFC-3576 socket error has occurred on a socket.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AAA","4","SEND_AAA_RESPONSE_FAILED","Could not send AAA response. [chars].","The system could not send an AAA response.","No action is required."
"AAA","4","SEND_RFC_RESPONSE_FAILED","Could not send RFC-3576 response. [chars].","The system could not send the RFC-3576 response.","No action is required."
"AAA","4","SEND_TPLUS_MES_FAILED","Could not send TACACS+ message. [chars].([dec]:[chars]).","The system could not send a TACACS+ message.","No action is required."
"AAA","4","SET_SERVER_FAILED","Could not set RADIUS server. [chars].","The system could not set the RADIUS server.","No action is required."
"AAA","4","SUPPLY_UNAME_PASS","Username & password must be supplied. User : [address], Pass: [address].","The username and password must be supplied.","No action is required."
"AAA","5","SYN_CALLBACK_FAILED","AAA Sync.Callback failed. [chars].","The AAA Sync.Callback has failed.","No action is required."
"AAA","3","TEST_NULL_FAILED","Unable to allocate memory off the stack.","The system is unable to allocate memory off the stack for testing null attributes.","This is a debug message only. No action is required."
"AAA","4","TPLUS_SERVER_NOT_FOUND","TACACS+ server not found. [chars]","The TACACS+ server was not found.","No action is required."
"AAA","4","TPLUS_SWITCHOVER_FAILED","TACACS+ server switchover failed. Current server is  [dec].[dec].[dec].[dec].","The TACACS+ server switchover has failed.","No action is required."
"AAA","5","TPLUS_SWITCHOVER_SUCCESS","TACACS+ server switchover successful. New server is [dec].[dec].[dec].[dec].","The TACACS+ server switchover is successful.","No action is required."
"AAA","4","TRANSLATE_AAA_TO_RADIUS_FAILED","Could not translate AAA AVP to RADIUS AVP. [chars].Code=[dec], ValueLen=[dec], VendorId=[dec], Buf=[address], BufSize=[dec].","The system could not translate the AAA AVP to the RADIUS AVP.","No action is required."
"AAA","4","TXQUEUE_ADD_FAILED","Transmission queue full. Queue name: [chars]. Dropping sessionpackets.","When the transmission queue is full, the system drops the session packets.","No action is required."
"AAA","3","UNAME_TOO_LONG","Username too long. Username: [int].","The username is too long.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AAA","3","UPDATE_GUESTINFO_AT_LOGIN_FAILED","Unable to update guest user information at login for [chars]. [chars].","The system is unable to update guest user information at the time of logging on.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AAA","3","UPDATE_GUESTINFO_AT_LOGOUT_FAILED","Unable to update guest user information at logout for [chars]. [chars].","The system is unable to update guest user information at the time of logging out.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AAA","6","USER_AUTH_PASSED","User authenticated. Username: [chars].","The user has been authenticated.","No action is required."
"AAA","3","USER_CHAP_CHECK_FAILED","Could not check the CHAP challenge. [chars].UsernameLength:[int]. Username: [chars].","The system could not check the CHAP challenge.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AAA","3","USERDBFILE_CREATE_FAILED","Unable to create user database file. [chars].","The system is unable to create a user database file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AAA","3","USERDBFILE_LOAD_FAILED","Unable to load user database file. [chars].","The system is unable to load a user database file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AAA","3","USER_DB_INIT_FAILED","User database not initialized.","The user database is not initialized.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AAA","3","USER_NAME_INVALID","Invalid username provided. [chars].","The system has detected an invalid username.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AAA","3","USER_PASS_CHECK_FAILED","Could not check password for user. [chars].UsernameLength: [dec]. Password Length:[dec].","The system could not check the password for the user.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AAA","3","VALIDATE_MSCHAP2_CRED_FAILED","Could not validate credentials for proxied RADIUS. [chars]. STA : [hex]:[hex]:[hex]:[hex]:[hex]:[hex] (len [int])","The system could not validate credentials for proxy RADIUS.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AAA","3","VALIDATE_GUEST_SESSION_FAILED",',"This error message is logged in the message log file. The reason for this error message could be any of the following:-User account entry not present-User account not configured as guest-User information not found-Maximum guest user retries are exceeded","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"ACL","3","ACE_GET_FAILED","Failed to get ACE from ACL. [chars]","The system is unable to get an access control entry from an access control list.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"ACL","3","CONFIG_STORE_FAILED","Failed to store Acl Config to Flash [chars].","The system failed to write the ACL configuration file onto the flash.","Try again. If it fails, reset the controller."
"ACL","3","DB_LOCK_FAILED","Couldn't get exclusive access on the Acl database. [chars].","All ACLs and their rules are placed in the ACL database. To change the precedence or a rule in the ACL, the table needs to be locked by obtaining a semaphore. This process is failing.","Try again. If it fails, reset the controller."
"ACL","3","DB_UNLOCK_FAILED","Couldn't release exclusive access on the Acl database. [chars].","Releasing the ACL Table semaphore to relinquish the exclusive access has failed.","Reset the controller."
"ACL","3","ENTRY_CREATE_FAILED","Couldn't create ACL [chars]. [chars].","The system could not create an ACL.","Try another ACL name or delete the old ACL to create a new ACL."
"ACL","3","ENTRY_DELETE_FAILED","Failed to delete ACL Entry [chars]. [chars].","The system has failed to delete the ACL entry.","Free the ACL from the CPU interface, other interface, or WLAN."
"ACL","3","ENTRY_DONOT_EXIST","Unable to find an ACL by name '[chars]'.","The system is unable to get an access control list by name.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"ACL","3","GET_FREE_ACL","Couldn't get an unused ACL. [chars].","The system could not get an unused ACL.","Delete the old ACL to create a new ACL."
"ACL","3","GET_NAME_BY_ID_FAILED","Couldnt get ACL name by ID. [chars].","The system could not get an ACL name by the ID.","Provide the correct ACL ID."
"ACL","3","IMPRULE_DEL_AVOIDED","Deleting the implicit deny rule [dec] of ACL [chars] is not allowed.","Every ACL has an implicit deny-all rule that is always the last rule in the ACL (an ACL allows 64 rules). This rule cannot be deleted.","No action is required."
"ACL","3","INFO_PUSH_FAILED","Failed to push CPU Acl info the NPU","The system has failed to push CPU ACL information to the NPU.","Try again after some time. If it still fails, reset the controller."
"ACL","3","INIT_FAILED","Failure in creating Acl Database. [chars].","The system has failed to create the semaphore to protect the ACL database.","Reset the controller."
"ACL","3","IPADD_TYPE_INCORRECT","Incorrect IP address type parameter of rule [dec] of ACL [chars]","The IP addresses can only be source or destination addresses.","Try again. If it fails again, reset the controller."
"ACL","3","LOAD_CONF_FAILED","Acl config is corrupted. Resetting Acl config to default.","The ACL configuration file is corrupted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"ACL","3","RULE_ACTION_INVALID","Incorrect action [dec] to set for the rule [dec] of the ACL [chars].","The action parameter of the rule of an ACL takes on the values of PERMIT or DENY. An error is displayed if the action is neither of the two values.","Set the action with either PERMIT or DENY."
"ACL","3","RULE_CREATE_FAILED","Can not Add Rule [dec] to ACL [chars]. [chars].","The system cannot add the rule to the ACL.","The maximum rule limit is achieved. Delete the old rule and create a new rule."
"ACL","3","RULE_DONOT_EXIST","Unable to [chars] the rule no.[dec] in ACL [chars]. No such rule exist","The system is unable to carry out the operation mentioned on the particular rule in the ACL because the rule does not exist.","Check whether the ACL name and the rule index are configured correctly."
"ACL","3","RULE_PUSH_FAILED","Pushing rule [dec] of Acl [chars] to the Network Processor Failed.","ACLs are applied in the Network Processor. They have to be pushed into the NPU. Pushing the rule of the ACL has failed.","Try again. If it fails, reset the controller."
"ACL","3","SET_PORT_RANGE_FAILED","Set Port Range failed for rule [dec] of ACL [chars]. [chars].","The Set Port Range failed for the type parameter for the ACL.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"ACL","3","SET_RULE_DIR_FAILED","Incorrect direction parameter for the rule [dec] of the ACL [chars]","The direction parameter of the rule of an ACL takes on the values IN, OUT, and ANY. This error is displayed if the direction is none of the three.","Set the direction to a valid value."
"APF","3","ACCTREQ_SEND_FAILED","Unable to send Radius Accounting Request for STA [hex]:[hex]:[hex]:[hex]:[hex]:[hex]. CallingSTA:[chars], CalledSTA:[chars]. [chars].","Unable to send a Radius Accounting Request.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","ADDMOBILE_SEND_FAILED","Could not send the LWAPP Add Mobile command to the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] associated to Rogue AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]. [chars].","Could not send the LWAPP Add Mobile command to AP, either due to internal error or due to AP validation failure.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","ADD_TO_BLACKLIST_FAILED","Unable to create exclusion-list entry for mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","This is security alert. A mobile station was blacklisted but could not be added to the list due to internal error.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","6","AES_REQ_REJECT","Rejecting RSN request for unicast AES from mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Rejected RSN request from mobile, as 80211i security information element validation failed.","Check the WLAN configuration to which mobile is trying to associate. Resolve the configuration conflict."
"APF","3","AID_UPDATE_FAILED","Error updating Association ID for REAP AP Client[hex]:[hex]:[hex]:[hex]:[hex]:[hex] - AID [int]","Failed to update Association ID for REAP AP client.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","6","AIRSPC_WARP_KCID","WARP KCID: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","WARP KCID AIRSPC.","No action is required."
"APF","1","AP_AUTO_CONTAIN_MISCONFIGURED","Auto-containing misconfigured AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] as per policy.","Validation of the configuration of the AP against 3rd party Trusted AP policy failed. Auto-containing is misconfigured for AP as per policy.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","AP_DESCP_EXCEEDED","AP group name or Description should not exceed 32 characters","AP group name or Description can not exceed 32 characters in length.","Please specify AP group name upto 32 characters in length."
"APF","3","APF_WIRED_GUEST_CLIENT_CREATE_FAILURE","Unable to create wired guest client entry for [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","Internal system error","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","APF_SITE_WLAN_ENABLE_FAILS","enabling WLANs failed for AP [chars]","Enabling the WLANs on the AP failed.","Delete and re-create the AP group."
"APF","3","APF_WIRED_GUEST_EXCLUDED_CLIENT","Received a packet from excluded wired guest client [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","Internal system error","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","APPLY_ACL_POLICY_FAILED","Could not Apply ACL Policy. [chars].","ACL policy can not be exceed 32 characters in length.","Please specify ACL Policy up to 32 characters in length."
"APF","3","APPLY_OVERRIDE_FAILED","Msgdef (APPLY_OVERRIDE_FAILED, APF, LOG_ERR, (MSG_TRACEBACK), Could not Apply Override. [chars].Mobile:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], SSID: [chars].","Could not apply WLAN policy. Either the associating WLAN was deleted or disabled.","Please check the status of associating WLAN."
"APF","3","ASSLEN_DIFF_FROM_REASSLEN","Association WPA/RSN IE length [dec] is different from Reassociation IE length [dec]","WPA/RSN IE length in Reassociation request is different from WPA/RSN IE length in Association request.","If this message recurs, 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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","ASSOCREQ","[chars]","The validation of the capability field from an Association Request failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","6","ASSOCREQ_PARSE_FAILED","Error parsing Assoc Request from STA[hex]:[hex]:[hex]:[hex]:[hex]:[hex] -- IE Type [int], IE Length [int],dataLen [int]. [chars].","Error parsing Assoc Request from STA.","No action is required."
"APF","4","ASSOCREQ_PROC_FAILED","Failed to process an association request from[hex]:[hex]:[hex]:[hex]:[hex]:[hex]. WLAN:[dec], SSID:[chars]. [chars].","Processing of association request from a mobile failed. The real reason for failure is specified in the message.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","4","ATIM_FRAM_DROP","Ignoring ATIM frame..","Currently system do not process 802.11 ATIM Frames.","No action is required."
"APF","1","AUTH_FAILED","Authentication failure (status [dec]) from STA[hex]:[hex]:[hex]:[hex]:[hex]:[hex]. [chars].","An authentication failure from the STA has occured. Verify the WEP key.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","AUTHMOBILE_SEND_FAILED","Could not send the LWAPP Authenticate Mobile command to rogue AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]  for mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex]. [chars].","Could not send the LWAPP Authenticate Mobile command to rogue AP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","AUTHMSG_SEND_FAILED","Unable to send Authentication message to STA [hex]:[hex]:[hex]:[hex]:[hex]:[hex]. [chars].","Unable to send an authentication message to a station.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","4","AUTO_CONTAIN_AP_NOT_SUPPORTED","Unable to add foreign access point[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Error message generated during data validation of migrated data.","No action is required."
"APF","3","AUTO_CONT_NOT_SUPPORTED","Auto-containment of [chars] is not supported. Disabling.","This msg can be result of data validation done after migration of data to newer software version.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","AUTO_ENABLE_DOT1XAKM","Auto-enabling 802.1x AKM for WLAN '[chars]'","If no Authentication Key Management is selected then 802.1x AKM selected as a default for WLAN.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","AUTO_ENABLE_WPA2_AES","Auto-enabling WPA2 AES for WLAN '[chars]'","If WPA2/RSN is enabled then default the cipher suite to AES, if nothing is selected for WLAN.","No action is required."
"APF","1","AUTO_ENABLE_WPA_TKIP","Auto-enabling WPA TKIP for WLAN '[chars]'","If WPA is enabled then default the cipher suite to TKIP if nothing is selected for WLAN.","No action is required."
"APF","2","BAD_PMK_CACHE_ENTRY","Found a bad PMK cache entry for Station:[hex]:[hex]:[hex]:[hex]:[hex]:[hex] deleting the entry","Internal system error","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","BUILD_NETNAME_FAILED","Could not build valid network name -- using default","Could not build valid network name, using default as the network name.","No action is required."
"APF","1","CAN_NOT_ASS_WITH_ROGUE_AP","Can not associate with [chars] Rogue AP.","Association failed with a Rogue AP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","CCKM_CREATE_PTSKA_FAILED","Could not generate PTK from BTK stored. [chars].Mobile:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Could not generate PTK. Invalid unicast encryption policy for mobile station","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","0","CHANGE_DOT11G_SUPP","802.11g Support changing from [chars] to [chars]. APs will reload.","802.11g Support changes. APs will reload.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","CHANGE_ORPHAN_PKT_IP","Changing orphan packet IP address for station[hex]:[hex]:[hex]:[hex]:[hex]:[hex] from [int].[int].[int].[int] --->[int].[int].[int].[int]","The system is changing orphan packet IP address for a station.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","CHANGE_ROGUE_STATE_FAILED","Can not change state on rogue[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Can not change state on rogue.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","CHECK_EXT_SUPP_RATES_FAILED","Could not check extended supported rates. [chars]. Length :[dec]. Mobile MAC: [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","Could not check extended supported rates. Verify data rate on client.","No action is required."
"APF","3","CHECK_SUPP_RATES_FAILED","Could not check supported rates. [chars]. Length :[dec]. Mobile MAC: [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","Could not check supported rates. Verify data rate on client.","No action is required."
"APF","3","CLEAR_TKN_TABLE_ENTRY_FAILED","Trying to clean an empty token entry [dec]!.","Internal system error","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","6","CONFIG_FILE_SAVED","Config file '[chars]' saved to flash.","Config file saved on flash.","No action is required."
"APF","3","CONVERT_HEX_KEY_FAILED","Could not convert Hex Key into Binary data. [chars].","Internal system error","Please re-specify WEP Hex Key."
"APF","5","COUNTRY_NOT_FOUND","Country '[chars]' not found in country database.","A particular country is not found in country database.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","CREATE_CCKM_REASS_RESPONSE_IE_FAILED","Could not build the CCKM Reassociation response IE.[chars]. Mobile: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Could not build the CCKM Reassociation response IE.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","CREATE_DOT11i_IE_FAILED","Could not create DOT11i Info element. [chars].","Internal system error","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","CREATE_KCID_INFO_ELEMENT_FAILED","Could not create the KC-ID information element. [chars].","Internal system error","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","CREATE_OVERRIDE_FAILED","Could not Create Override. [chars].Mobile:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], SSID: [chars].","Could not Create Override.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","4","CREATE_PMK_CACHE_FAILED","Attempt to insert PMK to the key cache failed. [chars].Length: [dec]. Station:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Internal system error","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","CREATE_SITE_WITH_NAME_FAILED","Cannot create site with reserved name '[chars]'","Illegal name for new site.","Re-specify name of new site."
"APF","3","CREATE_VLAN_IP_INTERFACE_FAILED","Could not create a virtual IP interface for VLAN.[chars].","Could not create a virtual IP interface for VLAN due to config data conflict.Explanation    Check other WLANs and port config data.Error Message    %APF-3-CREATE_WARP_ADV_IE_FAILED: Unable to create WARP ADVERTISEMENT IE Explanation    Internal system error","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","CREATE_WARP_M_KCID_IE_FAILED","Unable to create WARP M-KCID IE","Unable to create WARP M-KCID IE.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","4","CREATE_WEP_CACHE_FAILED","Attempt to insert WEP key failed. [chars]. Recv Length: [dec], Send Length:[dec]. Station: [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","Attempt to insert WEP key failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","0","DISABLE_IPSEC_WLAN","Disabling Ipsec WLAN (id [dec], SSID '[chars]') [chars].","Disabling an IPsec WLAN.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","DISABLE_UNSUPPORTED_FEATURE","Feature: [chars] found enabled, which is not supported by the country([chars]) configured. Disabling it.","A particular feature was found enabled, but is not supported by the country configured. Disabling it.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","DISABLE_WLAN_FAILED","Unable to disable WLAN [dec].","Unable to disable WLAN.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","DISCONECT_MOBILE_DUE_TO_WLAN_SWITCH","Disconnecting mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex] due to switch of WLANs from [dec] to [dec]","Disconnecting a mobile due to switch of WLAN.","This is a debug message only. No action is required."
"APF","3","DOT11_AUTH_MODE_SET_FAILED","Could not set the 802.11 authentication mode. [chars]. Mode: [dec] WLAN:[chars].","Could not set the 802.11 authentication mode.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","0","DOT11G_NOT_PERMITTED","802.11g not permitted in configured country - disabling.","802.11g not permitted in configured country - disabling.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","6","DOT11N_QOS_DISABLED_NOT_PERMITTED","802.11n rates requires WMM - disabling 11n rates on WLAN","802.11n rates requires WMM - disabling 11n rates on WLAN","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","4","DOT1P_TAGS","Dot1P Tags [chars] for all APs connected to this switch","Dot1P Tags for all APs connected to a switch.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","6","DOT1X_REQ_REJECT","Rejecting request for 802.1x on port [dec] from mobile[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Rejecting request for 802.1x on a port from a mobile.","No action is required."
"APF","3","ENABLE_WLAN_FAILED","Unable to enable WLAN [dec].","Unable to enable WLAN.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","ENCRYPTPOLICY_NOT_FOUND","Unable to find Encryption Policy for Mobile: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]. Traffic Type:[chars], Security Method:[chars].","Unable to find Encryption Policy for a particular mobile station entry.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","FOREIGNAP_NOT_FOUND","Unable to locate foreign AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]for [chars].","Unable to locate foreign AP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","GET_CURR_RSSI_FAILED","Could not get most recent RSSI and its timestamp. [chars].","Could not get most recent RSSI and its timestamp.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","GET_MULTI_ENC_POL_FAILED","Could not Get Multicast Encryption Policy. [chars].WPA2:[dec].","Could not Get Multicast Encryption Policy.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","GET_SECURITY_POLICY_FAILED","Could not get security policy. [chars]. WLAN: [chars]","Could not get security policy.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","GET_TKN_BKT_FAILED","Could not get Token Bucket Entry. [chars].","Could not get Token Bucket Entry.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","6","GUEST_ASSIGNED_IP","Guest User ([chars]) with MAC Address ([hex]:[hex]:[hex]:[hex]:[hex]:[hex]) assigned IP Address ([int].[int].[int].[int])","IP address assigned to guest user.","This is a debug message only. No action is required."
"APF","3","GUEST_INIT_FAILED","Could not Create [chars]","Wired Guest Init failed.Error Message    %APF-4-IGNORE_IDLE_TIMEOUT: Ignoring Idle-Timeout event from the NPU for STA [hex]:[hex]:[hex]:[hex]:[hex]:[hex] associated to REAP AP[hex]:[hex]:[hex]:[hex]:[hex]:[hex]([int]) Explanation    Ignoring Idle-Timeout event from the NPU for STA which is associated to REAP AP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","INVALID_AUTH_MSG_LEN","Invalid authenticate message length.","Invalid authenticate message length.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","INVALID_AUTH_SEQ_NUM","Invalid authentication sequence number.","Invalid authentication sequence number.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","INVALID_CAC","Invalid Admission control ([dec]) specified for station [hex]:[hex]:[hex]:[hex]:[hex]:[hex] on AP[hex]:[hex]:[hex]:[hex]:[hex]:[hex] slotId [dec]","Invalid Admission control is specified for a station.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","INVALID_CONF_CHANNEL","Invalid configured channel on AP [chars].","Invalid configured channel on AP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","INVALID_DOT11_ENCRPT_MODE","Invalid 802.11 encryption mode ([dec]) provided for WLAN [chars]","Invalid 802.11 encryption mode is provided for WLAN.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","INVALID_ENC_POL_SET","Invalid encryption policy set for [chars].","Invalid encryption policy is set.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","INVALID_ENCRYPT_POLICY","Invalid Encryption Policy ([dec]) set for [chars] WLAN.","Invalid Encryption Policy is set for WLAN.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","0","INVALID_FRAME_LEN","Frame length out of bounds: [dec].","Frame length is out of bounds.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","4","INVALID_INFO_ELEMENT_LEN","Invalid SSID Information Element length in probe request from [chars].","Invalid SSID Information Element length in probe request.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","INVALID_MAC_FILTER_DMTR_SETTING","Invalid MAC filter delimiter setting for mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Invalid MAC filter delimiter is set for mobile.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","INVALID_MOB_STATION_STATE","Invalid mobile station state - unable to expire [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Invalid mobile station state - unable to expire.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","INVALID_MTU","Invalid MTU ([int]) Discarding packet to AP [dec].[dec]:[dec].[dec] ([dec])","Could not send packet to AP because the specified MTU is out of allowed range.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","4","INVALID_RADIO_CONFIG","Invalid configuration found for [chars] radio. [chars].","Invalid configuration found for a radio.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","INVALID_RADIO_TYPE","Invalid radio type [dec] received.","Invalid radio type is received.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","6","INVALID_RSN_IE_CAPABILITY","Received an invalid RSN IE capability. [chars].","Received an invalid RSN IE capability.","No action is required."
"APF","3","INVALID_SEC_BIT","Invalid security bit [hex] provided for WLAN [chars]","Invalid security bit is provided for WLAN.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","INVALID_SEC_COMBINATION","Cannot configure export anchor when IPv6 is enabled.","IPv6 and Export Anchors cannot be enabled on a WLAN simultaneously.","Please disable IPv6 if export anchors need to be added to the WLAN configuration."
"APF","3","INVALID_SEC_POL","Invalid Security Policy [hex] ([chars])","Invalid Security Policy.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","4","INVALID_STAAPL_IE","Received invalid STA APL IE from STA [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Received invalid STA APL IE from a STA.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","INVALID_STATUS_CODE","Invalid status code in authenticate message.","Invalid status code in authenticate message.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","LOCALHANDOFF","[chars]","Internal system error","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","MAKE_CHANGE_DOT11A_FAILED","Attempting to make changes to 802.11A while active.","Attempting to make changes to 802.11A while active.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","MAKE_CHANGE_DOT11B_FAILED","Attempting to make changes to 802.11B while active.","Attempting to make changes to 802.11B while active.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","6","MIGRATE_CONFIG","Migrating [chars] Config from Version [dec] to Version [dec]","Migrating Config from Version to Version.","No action is required."
"APF","1","MM_ANCHOR_DENIED","Anchor denied for mobile: [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","Anchor denied for a mobile.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","MOBILE_ADD_FAILED","Unable to add mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex] to PEM module.","Policy Enforcement module rejected the request to add the mobile station.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","MOBILE_ANNOUNCE_CLSN","Announce collision for mobile[hex]:[hex]:[hex]:[hex]:[hex]:[hex], deleting.","Announced collision and delete the mobile.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","6","MOBILE_CONF_ON_CTRL","Mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex] is not doing CKIP KP,which is configured on controller.","Mobile is not doing CKIP KP, which is configured on controller","No action is required."
"APF","6","MOBILE_DOING_CCKM","Mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex] is doing CCKM.","Mobile is doing CCKM.","No action is required."
"APF","6","MOBILE_DOING_CKIP","Mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex] is doing CKIPMMH-MIC, which is not configured on controller.","Mobile is doing CKIP MMH-MIC, which is not configured on controller","No action is required."
"APF","1","MOBILE_ENTRY_CREATE_FAILED","Could not create Mobile Station Entry. [chars]. Mobile:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], Type: [chars]. Mobile rejected.","Could not create Mobile Station Entry.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","MOBILE_ENTRY_NAC_STATE_SET_FAILED","Could not set NAC state for Mobile Station Entry. [chars]. Mobile:[hex]:[hex]:[hex]:[hex]:[hex]:[hex].","Could not set NAC state for mobile.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","6","MOBILE_EXCLUDED","Excluded the mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","Set the station on the exclusion list.","No action is required."
"APF","1","MOBILE_LOCATION_UPDATE_FAILED","Could not update the mobile station location. [chars].AP:[chars]. Port:[dec]. Config:[dec].","Could not update the mobile station location.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","MOBILE_NOT_AUTH","Mobile Station has not authenticated.","Mobile Station has not authenticated.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","6","MOBILE_NOT_CONF_ON_CTRL","Mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex] is doing CKIP KP,which is not configured on controller.","Mobile is doing CKIP KP, which is not configured on controller.","No action is required."
"APF","3","MOBILE_NOT_DOING_CCKM","Mobile entry in cache is not doing CCKM [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Mobile entry in cache is not doing CCKM.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","6","MOBILE_NOT_DOING_CKIP","mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex] is not doing CKIPMMH-MIC, which is configured on controller.","mobile is not doing CKIP MMH-MIC, which is configured on controller.","No action is required."
"APF","6","MOBILE_NOT_EXCLUDED","Could not exclude the mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","Could not exclude a particular mobile. Either mobile is already in exclusion-list or excluding may be disabled for this specific mobile. Alternatively, the exclusion reason may be disabled.","No action is required."
"APF","4","MOBILESTATION_NOT_FOUND","Could not find the mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex] in internal database","Could not find a particular mobile station in internal database","No action is required."
"APF","1","MOVED_ADHOC_CLIENT_TO_AUTOCONTAIN","Moved adHoc client [chars] to auto-contained state.","Moved adHoc client to auto-contained state.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","MOVED_AP_TO_AUTOCONTAIN","Moved AP [chars] to auto-contained state.","Moved AP to auto-contained state.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","MSCB_DEL_FAILED","Unable to delete the MSCB entry ([hex]:[hex]:[hex]:[hex]:[hex]:[hex]) from [chars] list.","Unable to delete the MSCB entry from list.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","MSGFAC","State change received for an unsupported radio type.","State change received for an unsupported radio type.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","NAME_PTR_MISSING","Missing ACL name pointer.","Missing ACL name pointer.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","6","NO_CONFIG_CHANGES","Not saving '[chars]' - no config changes.","Not saving - no config changes.","No action is required."
"APF","1","NOT_ADV_SSID_ON_AP","Not advertising SSID [chars] on AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] due to [chars].","Not advertising SSID on AP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","4","NOT_ADV_SSID_ON__AP","Not advertising SSID [chars] on AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] due to [chars].","Not advertising SSID on AP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","NOT_ADV_SSID_ON_REAP_AP","Not advertising SSID [chars] on REAP AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] due to [chars].","Not advertising SSID on REAP AP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","0","NOTIFICATION_TIMER_NOT_CREATED","[chars] Could not create Apf-Locp Notification timer...","Could not create APF-LOCP Notification timer.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","4","NOTIFMSG_PROC_FAILED","Failed to process a notification message (MsgLen=[int],Tag=[int],TagLen=[int]). [chars].","Failed to process a notification message.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","6","NULL_DATA_IN_ADDTS_REQ","NULL data in ADD TS Request from STA [hex]:[hex]:[hex]:[hex]:[hex]:[hex] -- dataLen [int]","NULL data in ADD TS is Request from STA.","No action is required."
"APF","4","OLD_ACE_RCL_IE_PRESENT","Old ACE RCL IE is present in mscb for station [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Old ACE RCL IE is present in mscb for a station.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","4","PARSE_BSN_PKT_FAILED","Could not parse Bsn Packet. Reason:[chars].","Could not parse Bsn Packet.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","4","PARSE_ETH0VIP_PKT_FAILED","Could not parse Eth0vIP Packet. Reason:[chars].","Could not parse Eth0vIP Packet.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","4","PARSE_NPU_PKT_FAILED","Could not parse NPU Packet. Reason:[chars].","Could not parse NPU Packet.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","PDU_ENCAP_FAILED","Failed to encapsulate a PDU for transmission to station[hex]:[hex]:[hex]:[hex]:[hex]:[hex]. [chars].","Failed to encapsulate a PDU for transmission to station.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","4","PKT_LEN_MORE_THAN_MAXDOT11MTU","Packet length [dec] greater than max 802.11 MTU","Packet length is greater than max 802.11 MTU.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","4","PROC_ACTION_FAILED","Could not process 802.11 Action. [chars]. Mobile:[chars].","Could not process 802.11 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","4","PROC_ASS_RADIUS_RES_FAILED","Could not Process Association after RADIUS response.[chars].","Could not Process Association after RADIUS response.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","PROC_CLIENT_ASS_RES_FAILED","Could not process client association response. [chars].","The system could not process a client association response.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","6","PROCESS_WME_ADDTS_REQ_FAILED","Could not Process the WME ADDTS Command. [chars].STA:[hex]:[hex]:[hex]:[hex]:[hex]:[hex] -- IE Tpye:[int]. IELength:[int].DataLen: [int]","Could not Process the WME ADDTS Command.","No action is required."
"APF","1","PROC_INSTALL_ORPHAN_IPADD_FAILED","Could not install the Orphan Packet IP address. [chars].STA:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]. Orphan PktIP:[int].[int].[int].[int]. Framed IP:[int].[int].[int].[int].","Could not install the Orphan Packet IP address.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","PROC_MM_RES_FAILED","Could not process MM response. [chars].Mobile:[hex]:[hex]:[hex]:[hex]:[hex]:[hex].","Could not process MM response.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","4","PROC_ORPHAN_MSG_DS_FAILED","Could not process frames received for unknown mobile from the DS. [chars].","Could not process frames received for unknown mobile from the DS.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","4","PROC_RADIUS__ASS_RES_FAILED","Could not process RADIUS association response. [chars].State: [dec] [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Could not process RADIUS association response.","No action is required."
"APF","1","PROC_RSN_WARP_IE_FAILED","Could not process the RSN and WARP IEs. [chars].MobileStation: [hex]:[hex]:[hex]:[hex]:[hex]:[hex], SSID:[chars].","Could not process the RSN and WARP IEs.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","6","PSK_REQ_REJECT","Rejecting request for PSK on port [dec] from mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Rejecting request for PSK on a port from a mobile.","No action is required."
"APF","3","PUT_CHANGE_ON_QUEUE_FAILED","Could not put link state changes on the queue. [chars].","Could not put link state changes on the queue.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","PWR_TRAP_SEND_FAILURE","Could not send trap for power change event on AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Internal system error","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","QOSLOAD_DEL_FAILED","Unable to remove AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]([dec]) from QOS load.","Unable to remove AP from QOS load.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","QUARANTINE_VLAN","Quarantine VLAN, force it to central switch for mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Quarantine VLAN, force it to central switch for a mobile.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","0","QUEUE_NOT_FOUND","[chars] Queue is not created yet.","Queue is not created yet.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","6","RADIUS_OVERRIDE_DISABLED","Radius overrides disabled, ignoring source [int]","RADIUS overrides disabled.","No action is required."
"APF","4","RCV_ACTION_FRM_WITH_CODE","Received Action frame with code [dec] from mobile station [chars]","Received a Action frame with code from a mobile station.","No action is required."
"APF","3","RCV_ASS_RREQ","We've received an Association request - must have been an error.","We've received an Association request - must have been an error.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","RCV_CORRUPT_PKT","Received a corrupted packet from [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - DOS?.","Received a corrupted packet.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","4","RCV_INVALID_ACTION_CODE","Received invalid action code [dec] from mobile station [chars]","Received an invalid action code from a mobile station.","No action is required."
"APF","3","RCV_INVALID_AP_STATE","Received an invalid state for AP[hex]:[hex]:[hex]:[hex]:[hex]:[hex] slot [dec]","Received an invalid state for AP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","4","RCV_INVALID_ARLDP_PKT","Received invalid ARLDP packet (received [dec] bytes, expected[dec]).","Received an invalid ARLDP packet.","No action is required."
"APF","1","RCV_INVALID_DOT1P_PRTY_TAG","Received an invalid 802.1p ([dec]) from RADIUS for[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Received an invalid 802.1p from RADIUS.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","RCV_INVALID_DSCP","Received an invalid DSCP ([dec]) from RADIUS for[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Received an invalid DSCP from RADIUS.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","RCV_INVALID_MOBILITY_MSG","Received an invalid mobility message for[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Received an invalid mobility message.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","RCV_INVALID_QOS_LEVEL","Received an invalid QoS Level ([dec]) from RADIUS for[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Received an invalid QoS Level from RADIUS.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","4","RCV_INVALID_SUPP_RATE","RLDP: received a message with an invalid supported rate.","RLDP: received a message with an invalid supported rate.","No action is required."
"APF","1","RCV_MOBILITY_RES","Received Mobility response for mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex] as anchor while in the wrong state.","Received Mobility response for a mobile as anchor while in the wrong state.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","4","RCV_PROBE_RESP","We've received a probe response - must have been an error.","We've received a probe response - must have been an error.","No action is required."
"APF","3","RCV_UNKNOWN_MSG_TYPE","Unknown message type [dec] received.","Unknown message type is received.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","4","RCV_UNSUPP_MGMT_MSG","Received an unsupported 802.11 management messagesubType[dec] from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Received an unsupported 802.11 management messagesubType from AP.","No action is required."
"APF","3","RCV_UNSUPP_MSG","Rogue Task: Received unsupported message [dec].","Rogue Task: The System has received an unsupported message.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","RCV_UNSUPPORTED_MES","Received unsupported message [dec].","Received an unsupported message.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","REGISTER_IPADD_ON_MSCB_FAILED","Could not Register IP Add on MSCB. [chars]. Address:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Could not register an IP address on MSCB.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","RETRIEVE_CKIP_ENC_POL_FAILED","Could not retrieve the CKIP unicast encryption policy.[chars]. Size: [dec].","Could not retrieve the CKIP unicast encryption policy.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","4","ROGUE_AP_ADD_FAILED","Failed to add the rogue AP [chars]. [chars].","Failed to add a rogue AP. This error may be due to too many rogue APs detected in the system.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","ROGUE_AP_CONTAIN_FAILED","Unable to contain rogue [chars]. [chars].","Unable to contain a rogue.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","ROGUE_AP_DEL_FAILED","Rogue AP entry deletion failed.","A rogue AP entry deletion has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","ROGUE_CLIENT_CONTAIN_FAILED","Unable to contain rogue client [chars]. [chars].","Unable to contain a rogue client.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","ROGUE_CLIENT_UPDATE_FAILED","Could not update rogue AP [chars] with rogue client [chars]information.","Could not update a rogue AP with the rogue client information.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","SEND_ASSOC_REQ_FAILED","Could not send a Client Association request. [chars].","Could not send an association request.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","SEND_ASSOC_RESP_FAILED","Could not send a Client Association response to [hex]:[hex]:[hex]:[hex]:[hex]:[hex]. [chars].","The system could not send an association response.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","SEND_CLIENT_ASS_REQ_FAILED","Could not send client association request. [chars].","Could not send a client association request.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","SEND_IGMP_QUERY_FAILED","Failed to send IGMP Query for roamed mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","A mobile can roam across subnets while listening to a multicast stream. When it roams across controllers, the multicast traffic has to reach the controller that the mobile is attached to. The controller sends an IGMP query to the mobile, and the controller has failed to send this IGMP query.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","SEND_PROBE_REQ_FAILED","Could not send a Client Probe request. [chars].","Could not send a probe request.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","SEND_PROBE_RESP_FAILED","Could not send a Probe Response. [chars].","Could not send a probe response.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","SEND_RADIUS_REQ_FAILED","Could not send RADIUS Request. [chars].Mobile:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Could not send a RADIUS request.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","SEND_ROGUE_CLIENT_RADIUS_REQ_FAILED","Could not send Rogue Client RADIUS Request. [chars]. Client: to [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","Could not send a rogue client RADIUS request.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","SET_AUTH_KEY_MGMT_MODE_FAILED","Could not set the WPA/WPA2 auth key management mode.[chars]. Siute: ([hex]). WLAN:[chars]","Could not set the WPA/WPA2 auth key management mode.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","SET_DOT11A_RATE_FAILED","Could not set the 802.11A operational rate. [chars].","Could not set the 802.11a operational rate.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","SET_DOT11B_RATE_FAILED","Could not set the 802.11B operational rate. [chars].","Could not set the 802.11B operational rate.","Verify the operational rate. Only 1,2,5.5,11M are supported"
"APF","3","SET_DOT11g_SUPP_FAILED","Could not set the 802.11g support. [chars].","Could not set the 802.11g support.","Change the configuration."
"APF","3","SET_FAST_ROAM_FAILED","Attempting to enable fast-roaming while Pico-Cell mode is enabled!","The system is attempting to enable fast roaming while the Pico-Cell mode is enabled.","Disable Pico-Cell mode, before enabling fast roaming."
"APF","3","SET_MSCB_MIRROR_FAILED","Unable to set mirroring for MSCB.","Unable to set mirroring for MSCB.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","SET_PICO_CELL_FAILED","Attempting to enable pico-cell while [chars] is enabled.","Attempting to enable a pico-cell while it is enabled.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","SET_PICO_CELLV2_FAILED","Attempting to enable pico-cell-V2 while [chars] is enabled.","Attempting to enable a pico-cell-V2 while it is enabled.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","SET_PSK_AUTH_MODE","Could not set the 802.11i PSK authentication mode.[chars]. Length:[int]. WLAN:[chars].","Could not set the 802.11i PSK authentication mode.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","SET_RSN_ENABLE_FAILED","Could not Enable the RSN IE. [chars].Mode: [dec].WLAN:[chars].","Could not enable the RSN IE.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","SET_SSN_ENABLE_FAILED","Could not Enable the SSN IE. [chars]. Mode:[dec]. WLAN:[chars].","Could not enable the SSN IE.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","SET_VAP_SECURITY_POL_WORD_FAILED","Error Setting Security Policy Bit [hex] (Current Policy [hex], Policy Change [hex], mode [int])","An error has occured while setting the security policy bit.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","SET_VAP_STATUS_FAILED","Could not Set the Status of Virtual Access point Entry.[chars].Static WEP:[int].Dynamic WEP:[int]. WLAN:'[chars]'","Could not set the status of the virtual access point entry.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","SET_VPN_AH_MODE_FAILED","Could not set the mode: [dec]. [chars].","Could not set the VPN AH mode.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","SET_VPN_AUTH_MODE_FAILED","Could not set the VPN authentication mode. [chars].Mode:[dec]. WLAN: [chars].","Could not set the VPN authentication mode.","Specify the VPN authentication mode again."
"APF","3","SET_VPN_ENC_MODE_FAILED","Could not set the VPN Encryption Mode. [chars].Mode: [dec].WLAN:[chars].","Could not set the VPN Encryption Mode.","Please re-specify the VPN Encryption Mode."
"APF","3","SET_VPN_IKE_AUTH_MODE_FAILED","Could not set the VPN IKE Authentication mode. [chars].Mode:[dec]. WLAN: [chars].","Could not set the VPN IKE authentication mode.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","SET_VPN_IKE_PFS_MODE_FAILED","Could not set the VPN IKE PFS mode. [chars].","Could not set the VPN IKE PFS mode.","Please check the reason, and specify the VPN IKE Authentication mode for the AP again."
"APF","3","SET_VPN_IKE_PHASE1_MODE_FAILEED","Could not set the VPN IKE Phase1 mode. [chars]. Mode:[dec]. WLAN: [chars].","Could not set the VPN IKE Phase1 mode.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","SET_VPN_IKE_SHAREDKEY_FAILED","Could not set the VPN IKE Pre-shared Key. [chars].Length: [dec]. WLAN: [chars].","Could not set the VPN IKE Pre-shared Key. Key length can not be more than 128.","Please specify the key again."
"APF","3","SET_WPA2_ENC_MODE_FAILED","Could not set the WPA2 encryption mode. [chars].Mode:[dec]. WLAN: [chars].","Could not set the WPA2 encryption mode.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","SET_WPA_ENC_MODE_FAILED","Could not set the WPA encryption mode. [chars]. Mode:[dec]. WLAN: [chars].","Could not set the WPA encryption mode.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","4","SFA_MISMATCH","SFA IE mismatch from [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - [chars]","The client does not support the features required for associating to this WLAN.","No action is required."
"APF","3","SITE_DELETE_FAILED","Site entry [dec] could not be deleted from database.","A particular site entry could not be deleted from the database.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","SITE_FAILURE","Cannot find apgroup [chars]","The system cannot find the database for the AP group.","Delete and re-create the AP group."
"APF","3","SITE_INVALID_VALUE","Invalid value in AP group","The value in the AP group is invalid.","Delete and re-create the AP group."
"APF","3","SITE_NO_AP_GROUP","Cannot find apgroup for AP","No AP group is set for the AP.","Set the AP group for the AP."
"APF","3","SITE_NOT_FOUND","Cannot find AP group","An internal error has occurred when processing AP group definitions. Groups might not be correctly configured.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","SITE_NULL_WLAN","Invalid value 0 for WLAN","WLAN 0 is not valid.","No action is required."
"APF","3","SITE_NO_NAME","Site [dec] has no name.","The site has no name.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","0","SITE_OVERRIDE_CONFIG_RESET","Resetting site override config.","The system is resetting the site override configuration.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","SOCK_OPER_FAILED","Socket operation [chars] on a socket returned failure with error [dec].","A socket operation on a socket has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","STA_IPADDR_CONFLICT","Station [hex]:[hex]:[hex]:[hex]:[hex]:[hex] connected to AP[hex]:[hex]:[hex]:[hex]:[hex]:[hex] on port [dec] is attempting to register one of our own IP addresses.","A station connected to AP is attempting to register one of our own IP addresses.","Please reconfigure the IP address of the station."
"APF","6","SUP_MOBILE_CLIENTS","Support [dec] mobile clients!","Support for mobile clients!","No action is required."
"APF","6","TKIP_REQ_REJECT","Rejecting RSN request for unicast TKIP from mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is rejecting an RSN request for the unicast TKIP from a mobile.","No action is required."
"APF","1","TRUSTED_AP_POL_FAILED","Trusted AP Policy failed for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - [chars].","A trusted AP Policy has failed for the AP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","UNABLE_ADD_ROGUE_AP_LRAD_ENTRY","Unable to add Rogue AP Lrad entry.","Unable to add a rogue AP LRAD entry.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","UNABLE_ADD_ROGUE_CLIENT_ENTRY","Unable to add new rogue Client entry [chars]","Unable to add a new rogue client entry.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","UNABLE_ADD_ROGUE_CLIENT_LRAD_ENTRY","Unable to add Rogue Client Lrad entry.","Unable to add a rogue client LRAD entry.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","UNABLE_ALLOC_MEM_OFF_STACK","Unable to allocate memory off the stack.","Unable to allocate memory off the stack.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","UNABLE_TO_CONTAIN_ROGUE_AP","Unable to contain rogue AP [chars].","Unable to contain the rogue AP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","UNABLE_TO_ENCAP_DELTS_HDR","Unable to encapsulate DELTS header for mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Internal system error","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","UNABLE_TO_ENTER_STATE_AP","Unable to properly enter state [dec] AP [chars].","Unable to properly enter the AP state.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","UNABLE_TO_ENTER_STATE_CLIENT","Unable to properly enter state [dec] client [chars].","Unable to properly enter the client state.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","UNABLE_TO_EXIT_STATE_AP","Unable to properly exit state [dec] AP [chars].","Unable to properly exit the AP state.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","4","UNABLE_TO_FIND_RSCB","Unable to find rscb for station [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Internal system error","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","UNABLE_TO_INIT_VAP","Unable to initialize VAP [chars].","Unable to initialize the VAP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","UNABLE_TO_KEEP_ROUGE_CONTAIN","Unable to keep rogue [hex]:[hex]:[hex]:[hex]:[hex]:[hex] in contained state - no available AP to contain.","Unable to keep rogue in a contained state; the system has no available AP to contain the rogue.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","UNABLE_TO_PERFORM_MAC_AUTH","Unable to perform MAC authorization on [chars]","Unable to perform MAC authorization.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","4","UNABLE_TO_SAVE_SUPP_RATES","Unable to save supported rates for station [hex]:[hex]:[hex]:[hex]:[hex]:[hex] ([int],[int])","Unable to save supported rates for a station.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","UNABLE_TO_UPDATE_ROGUE_CLIENT","Unable to update state [dec] Rogue client [chars].","Unable to update the rogue client state.","No action is required."
"APF","3","UNABLE_TO_UPDATE_STATE_ROGUE_AP","Unable to update state [dec] Rogue AP [chars].","Unable to update the rogue AP state.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","UNABLE_TO_VALIDATE_ROGUE_AP_POL","Unable to validate rogue AP policy for [chars].","Unable to validate the rogue AP policy. The system cannot auto contain the AP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","UNKNOWN_RADIO_TYPE","Unknown Radio Type.","Radio types can only be 802.11a and 802.11bg.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","UNSUPP_AUTH_ALGO_NUM","Unsupported authentication algorithm number ([dec]) from [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","The system supports only Open Authentication, Cisco-LEAP, and Shared key authentication algorithms.","No action is required."
"APF","4","UNSUPPORTED_COUNTRY","Country '[chars]' is set to be unsupported.","A particular country has been set to be unsupported.","No action is required."
"APF","3","UNSUPP_RADIO_TYPE","Unsupported Radio Type.","Radio types can only be 802.11a and 802.11bg.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","UPDATE_FOREIGN_AP_FAILED","Could not update foreign AP [chars]. [chars].","Could not update the foreign AP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","UPDATE_FOREIGN_AP_INTF_FAILED","Could not update foreign AP interface [chars]. [chars].","Could not update the foreign AP interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","4","UPDATE_MOBILE_LOCATION_FAILED","Could not update the mobile station location. [chars].AP:[chars]. Port:[dec]. Config:[dec].","Could not update the mobile station location.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","6","USE_DEFAULT_CIPHER_SUITE","Using default settings for [chars] Cipher Suite for mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Since either group or pairwise or AKM cipher suite was not included in the association request from mobile. Therefore depending on configuration using the WPA1/WPA2 default settings for the mobile.","No action is required."
"APF","1","USER_ADD_FAILED","Unable to create username [chars] for mobile[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Could not create the associated username entry for a mobile due to internal error.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","1","USER_DEL_FAILED","Unable to delete username [chars] for mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Unable to delete username entry for a mobile. Entry not found.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","VALIDATE_CCKM_REASS_REQ_ELEMENT_FAILED","Could not validate the CCKM Reassociation request element.[chars]. Mobile:[hex]:[hex]:[hex]:[hex]:[hex]:[hex].","Validation for CCKM Reassociation request element failed. Check the reason for failure in error message.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","VALIDATE_DOT11i_AUTH_FAILED","Could not validate the WPA security IE.[chars]. Mobile:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Validation for WPA security information element failed. The supported AKM types are CCKM, DOT1X and PSK.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","VALIDATE_DOT11i_CIPHERS_FAILED","Could not validate Dot11i security IE. [chars].Mobile:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Validation for Dot11i security IE failed. Received invalid RSN cipher suite or an invalid Unicast/Multicast WPA OUI code.","This is a debug message only. No action is required."
"APF","6","VALIDATE_RSN_IE_FAILED","Could not validate RSN information element. [chars].Mobile:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Invalid length for RSN information element.","This is a debug message only. No action is required."
"APF","1","VALIDATE_TRUSTED_AP_POL_FAILED","Could not validate trusted AP Policy. [chars]. Rogue Addr: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Could not validate the configuration of AP against the third party Trusted AP Policy.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","4","VAPENTRY_ADD_FAILED","Unable to create VAP profile '[chars]'. Could not insert entry into VAP Tree","Unable to create VAP profile due to internal system error.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","VAP_STATUS_SET_FAILED","Could not set VAP status. [chars]. WLAN: [chars]","Could not enable WLAN. Either preshared key is missing or the WEP key index is invalid or the static WEP key index is same as the dynamic WEP key index.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","6","WARPASSOC_SWITCH_EVENT","WARP switched [chars] for mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex]. 1xInitiateCount: [dec]...","Wireless ARP has been switched on/off for the client.","This is a debug message only. No action is required."
"APF","6","WARP_ENABLE","Enabling WARP...","Activating WARP.","This is a debug message only. No action is required."
"APF","3","WARP_INIT_FAILED","Could not initialize WARP. [chars].","Failed to initialize WARP.","This is a debug message only. No action is required."
"APF","6","WARP_KCID","WARP KCID: [hex]:[hex]:[hex] -[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex] --[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","WARP KCID information.","No action is required."
"APF","3","WATCHENTRY_CREATE_FAILED","Unable to create watchlist entry for key[hex]:[hex]:[hex]:[hex]:[hex]:[hex]. Key type: [chars].","Internal system error","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","WATCHENTRY_DEL_FAILED","Unable to delete watchlist entry for key [hex]:[hex]:[hex]:[hex]:[hex]:[hex]. [chars]","Internal system error","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","WEP_KEY_SET_FAILED","Could not set the 802.11 WEP key. [chars]. WLAN [chars]","Could not set the WEP key for the WLAN because it is an Invalid 802.11 WEP key.","This is a debug message only. No action is required."
"APF","3","WGB_ADD_WIRED_CLIENT_FAILURE","Unable to add wired client [hex]:[hex]:[hex]:[hex]:[hex]:[hex].WGB [hex]:[hex]:[hex]:[hex]:[hex]:[hex]. [chars].","Failed to add a wired client. WGB data is missing.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","WGB_DATA_MEM_ALLOC_FAILED","[chars]: Unable to allocate [dec] bytes for WGB state.","Internal system error","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"APF","4","WGB_DELETE_WIRED_CLIENT_FAILURE","[chars]: Unable to delete wired client[hex]:[hex]:[hex]:[hex]:[hex]:[hex] from WGB[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Failed to delete a wired client. The system could not find the wired client entry.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","WGB_INVALID_CLIENT_DELETE_ATTEMPT","[chars]: Attempted to delete a non wgb client as wgb client.","Internal system error","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","6","WGB_INVALID_PARAM","[chars]: Internal error, no WGB data.","Internal system error.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","WGB_INVWLAN","[chars]","Received an IAPP or mobility message where the WGB MAC and wired client MAC are erroneously the same.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","6","WGB_NOT_FOUND","WGB [hex]:[hex]:[hex]:[hex]:[hex]:[hex] not found, no update of wired client info ([hex]:[hex]:[hex]:[hex]:[hex]:[hex][dec].[dec].[dec].[dec]) in WGB table.","WGB is not found or no entry of a wired client is found in the WGB table.","This is a debug message only. No action is required."
"APF","3","WGB_PLUMB","[chars]","The system has failed to plumb in the driver the WGB wired client's AAA attributes. This is an internal system error.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","WGB_POLICY","[chars]","A WGB wired client normally inherits its associated WGB AAA attributes. This operation failed, this is an internal system error.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","WGB_UNABLE_TO_ADD_WIRED_CLIENT","[chars]: Unable to add wired client [hex]:[hex]:[hex]:[hex]:[hex]:[hex]. WGB [hex]:[hex]:[hex]:[hex]:[hex]:[hex] is either not found, or blacklisted,or is being deleted.","Failed to add wired a client. Either WGB is not found or is already excluded or is being deleted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","WGB_UNSUPPORTED_IAPP_PKT","[chars]: IAPP Error! Unsupported Pkt/Subtype ([address]:[dec]:[dec])","Received unsupported IAPP packet type or subtype.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","WGB_WIRED_CLIENT_CREATE_FAILURE","[chars]: Unable to create WGB wired client entry[hex]:[hex]:[hex]:[hex]:[hex]:[hex]!.","Internal system error.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","6","WGB_WIRED_CLIENT_ENTRY_NOT_FOUND","WGB ([hex]:[hex]:[hex]:[hex]:[hex]:[hex]) table,wired client [hex]:[hex]:[hex]:[hex]:[hex]:[hex] [dec].[dec].[dec].[dec] not found in WGB table.","Wired client not found in WGB table.","This is a debug message only. No action is required."
"APF","3","WGB_WIRED_CLIENT_MAC_CONFLICT","[chars]","Received an IAPP or Mobility message where the WGB MAC and wired client MAC are erroneously the same.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","WGB_WIRED_CLIENT_MAXED_OUT","Unable to add wired client [hex]:[hex]:[hex]:[hex]:[hex]:[hex].WGB [hex]:[hex]:[hex]:[hex]:[hex]:[hex]. [chars].","Failed to add wired client. Either reached maximum limit of wired client or due to internal system error.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","WIRED_CLIENT_MEM_ALLOC_FAILURE","[chars]: Unable to allocate WGB wired client structure!","Internal system error","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"APF","3","WIRED_CLIENT_NAC_FAILURE","[chars]: Unable to NAC OOB for  WGB wired client entry[hex]:[hex]:[hex]:[hex]:[hex]:[hex]!.","Internal system error","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","4","WLAN_NOT_ENABLED","WLAN [chars] was NOT enabled.","Internal system error","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","4","WLAN_NOT_SUPP","WLAN [dec] is not supported on Cisco AP [chars].","WLAN ID is not in valid range for a Cisco AP.","No action is required."
"APF","3","WLAN_OUT_OF_RANGE","WlanId [dec] is out of range.","WLAN ID is not in the valid range.","Configure the WLAN ID within the specified range."
"APF","4","WPS_LESS_THAN_MIN","WPS (Rogue AP Timeout=[dec]) is less than (MIN value=[dec]).Setting it to [dec]","After data upgrade rogue clean up timer is less than a minute. Setting it to minimum rogue clean up timer value.","This is a debug message only. No action is required."
"APF","2","BAD_PMK_CACHE_ENTRY","Found a bad PMK cache entry for Station:[hex]:[hex]:[hex]:[hex]:[hex]:[hex] deleting the entry","Internal system error","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","INVALID_SEC_COMBINATION","Cannot configure export anchor when IPv6 is enabled.","IPv6 and Export Anchors cannot be enabled on a WLAN simultaneously.","Please disable IPv6 if export anchors need to be added to the WLAN configuration."
"APF","0","NOTIFICATION_TIMER_NOT_CREATED","[chars] Could not create Apf-Locp Notification timer...","Could not create APF-LOCP Notification timer.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"APF","3","WIRED_CLIENT_NAC_FAILURE","[chars]: Unable to NAC OOB for  WGB wired client entry[hex]:[hex]:[hex]:[hex]:[hex]:[hex]!.","Internal system error","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AUTOINST","3","MSGTAG001","Unable to start Auto Install task.","The AutoInstall task could not be started.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AUTOINST","3","MSGTAG002","User aborted Auto Install process.","The user aborted the AutoInstall process.","No action is required."
"AUTOINST","3","MSGTAG003","No interfaces could obtain an IP address.","DHCP was not successful on any of the connected interfaces.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AUTOINST","3","MSGTAG004","Could not write resolve.conf.","DNS lookups will not work during the AutoInstall process if resolv.conf cannot be created.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"AVL","0","TREE_CORRUPT","AVL Tree [address] is corrupt","The AVL Tree is corrupt. Internal system error","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"BASE","3","FILE_WRITE_FAIL","LIF: Error writing config file [chars].","The system encountered an error when writing to the configuration file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"BASE","6","LIF_DEL","LIF: Could not find matching table entry for LIF [dec].","The system could not find a matching table entry for the LIF.","No action is required."
"BASE","3","LIF_REGISTRATION_FAIL","LIF: Unable to register for [chars] callback.","The system is unable to register for the specified callback.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"BASE","3","MAX_REGISTRATIONS","LIF registrar_ID [dec] greater than L7_LASTLIF_TYPE.","The maximum number of registrations for LIF notifications has been exceeded.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"BASE","6","REGISTRATION_EXISTS","LIF registrar_ID [dec] already registered.","The registration for the specified registration ID already exists.","No action is required."
"BCAST","4","CLIENT_NUM_GRP_EXCEEDED","NUM of multicast groups the client has joined has exceeded max allowed number","Each client is allowed to join a maximum of 16 multicast groups. The system rejects requests that are beyond this limit.","No action is required."
"BCAST","3","CONFIG_SAVE_FAIL","Failed to save the Broadcast/Multicast configuration.","The system failed to save the configuration file for broadcast and multicast related configurations.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"BCAST","3","COUNT_MISMATCH","Client count mismatched between database count and running count. Database count = %d count = %d","While adding or deleting a snooped multicast group to the database, there was a mismatch between the count in the database and the running count.","Disable and enable multicast IGMP snooping by entering the config network multicast igmp snooping {disable | enable} command."
"BCAST","4","DS_FWD_FAILED","Failed to forward multicast pkts over the DS.","The system has failed to forward multicast packets over the DS.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"BCAST","4","FAP_FWD_FAILED","Failed to forward multicast pkt to foreignAPs.","The system has failed to forward a multicast packet to foreign APs.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"BCAST","4","IGMPSEND_FAILED","Transmisstion of IGMP report packet failed","The system has failed to transmit the IGMP report packet.","No action is required."
"BCAST","3","IGMP_TYPE_MISMATCH","IGMP Type [int] for packet received from wireless is not supported","Recommended Action    No action is required.Error Message    %BCAST-3-INVALID_VLANID:  Recieved an igmp query with invalid vlanid Explanation    The system has received an IGMP query with an invalid VLAN ID. The packet will be ignored.","No action is required."
"BCAST","4","LRAD_FWD_FAILED","Failed to forward multicast pkt to LRAD","The system has failed to forward the multicast packet to LRAD.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"BCAST","3","MAC_ADDR_MISMATCH","client addr between the bcast database and the mscb fails","There is a mismatch between the BCAST database and MSCB database.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"BCAST","3","MCAST_BCAST_DISABLE","Automatically disabling multicast/broadcast forwarding (reason: [chars])","Multicast-unicast is not supported on the Cisco 2000 series controllers. If you have a configuration, multicast is automatically disabled and you cannot be enable it again until you configure a multicast group.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"BCAST","4","MGID_QUEUE_EMPTY","Mgid queue is empty!.","The MGID queue is empty. More than 4000 multicast groups in different VLANs have been assigned.","No action is required."
"BCAST","4","PKT_TYPE_NOT_EOIP","Packet over the tunnel [type [dec]] is not Ethernet over IP packet.","A packet that is not of the Ethernet over IP protocol type is being dropped in the tunneled packet processing.","No action is required."
"BCAST","4","Q_ADD_FAILED","Broadcast/Multicast queue add failed.","If the message is seen repeatedly, it means some host in the network is flooding with too many broadcast ARP requests or CDP packets.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"BCAST","4","RX_LLC","Received broadcast LLC packet.","A multicast packet has been received with the protocol type LLC.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"BCAST","4","RX_LWAPP_CTL","Received broadcast lwapp control packet.","Broadcast processing should not receive an LWAPP control packet. These packets are meant for LWAPP processing.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"BCAST","4","RX_WRONG_ETYPE","Received invalid mcast packet of type [hex].","The system has received a multicast packet with the protocol type greater than or equal to 1500.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"BCAST","4","TUNNELED_NOT_DIX","Tunneled pkt not a DIX pkt. protocol type is [dec]","The remote controller always tunnels a DIX packet. The controller drops non-DIX packets.","No action is required."
"BCAST","4","TUNNELED_NOT_MCAST","Tunneled pkt is not a multicast pkt.","A tunneled unicast packet is being dropped in the tunneled multicast processing.","No action is required."
"BCAST","3","UNSOPPORTED_RX_FLAG","Packet with unsupported RX Flag [dec]. 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.Error Message    %BCAST-3-UNSUPPORTED_MSG_TYPE: Received unsupported message (type = [dec]).","The message type in the BCAST message queue is unknown.","Error Message    %BCAST-4-VAPID_OUT_OF_RANGE: In broadcast/multicast processing client "
"BOOTP","7","BOOT_FILE_NAME","file: [chars].","The boot filename specified in the BOOTP packet appears.","No action is required."
"BOOTP","7","BOOTP_FLAGS","flags: [hex].","The flag option in the BOOTP packet appears.","No action is required."
"BOOTP","7","BOOTP_HOPS","hops: [dec].","The hops option in the BOOTP packet appears.","No action is required."
"BOOTP","7","BOOTP_HW_LEN","hlen: [dec].","The hardware address length in the bootp packet appears.","No action is required."
"BOOTP","7","BOOTP_HW_TYPE","htype: [chars].","The hardware address type in the BOOTP packet appears.","No action is required."
"BOOTP","7","BOOTP_OP_CODE","BOOTP[[chars]] op: [chars].","The BOOTP opcode appears.","No action is required."
"BOOTP","7","BOOTP_OPT_AP","[chars]:","The first vendor option appears.","No action is required."
"BOOTP","7","BOOTP_OPT_HOSTNAME","[chars]: [chars].","The hostname option in the BOOTP packet appears.","No action is required."
"BOOTP","7","BOOTP_OPT_VAL","[chars][chars]","The actual value of the vendor option appears.","No action is required."
"BOOTP","7","BOOTP_REPLY_RECVED","BOOTP Reply received","The BOOTP Reply has been received.","No action is required."
"BOOTP","7","BOOTP_SECS","secs: [dec].","The elapsed seconds in the BOOTP packet appears.","No action is required."
"BOOTP","7","BOOTP_SENT_SUCCESS","BOOTP Request Packet sent successfully","A BOOTP request packet has been sent successfully.","No action is required."
"BOOTP","0","BOOTP_TASK_CREAT_FAILED","Failed to Create BOOTP Task.","The system has failed to create a BOOTP task.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"BOOTP","3","BOOTP_TIME_OUT","Timed out waiting for BOOTP reply","The system has timed out waiting for a BOOTP reply.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"BOOTP","7","BOOTP_VEND_OPT","options:.","The vendor options in the BOOTP packet appear.","No action is required."
"BOOTP","7","BOOTP_WAIT_REPLY","Waiting for the BOOTP Reply","The system is waiting for the BOOTP reply.","No action is required."
"BOOTP","7","BOOTP_XID","xid: [hex].","The transaction ID in the BOOTP packet appears.","No action is required."
"BOOTP","7","BOOTP_YIADDR","my IP: [chars].","The yiaddr field in the BOOTP packet appears.","No action is required."
"BOOTP","7","CLIENT_HW_ADDR","hw_addr:","The BOOTP client hardware address appears.","No action is required."
"BOOTP","7","CLIENT_IP_ADDR","client IP: [chars].","The BOOTP client IP address appears.","No action is required."
"BOOTP","3","GET_BOOTP_OPT_FAILED","Failed to get the [chars] option from the BOOTP packet","The system has failed to get an option from the BOOTP packet.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"BOOTP","3","GET_BOOTP_STRUCT_FAILED","Unable to get the BOOTP structure for the [chars]","The system is unable to get the BOOTP structure.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"BOOTP","7","GWAY_IP_ADDR","gateway IP: [chars].","The gateway IP address field in the BOOTP packet appears.","No action is required."
"BOOTP","7","HW_ADDR_BYTE","[hex][chars]","Each byte in the BOOTP client hardware address appears.","No action is required."
"BOOTP","3","IP_CONF_FAILED","Configuring an IP for [chars] failed","The configuration for an IP for a particular interface has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"BOOTP","4","OPT_NOT_FOUND","The BOOTP option [char] not specified in the Vendor field","An expected BOOTP option is not specified in the Vendor field.","No action is required."
"BOOTP","7","SENDING_BOOTP_PKT","Sending Bootp Packet.","The system is sending a BOOTP packet.","No action is required."
"BOOTP","7","SERVER_IP_ADDR","server IP: [chars].","The server IP address field in the BOOTP packet appears.","No action is required."
"BOOTP","7","SERV_HOST_NAME","server: [chars].","The server hostname in the BOOTP packet appears.","No action is required."
"BOOTP","3","SET_BROADADDR_FAILED","Setting broadcast address on the socket failed.","An error occurred while setting the broadcast address on the socket failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"BOOTP","3","SET_IP_FAILED","Unable to set IP address [hex] for the [chars]","The system is unable to set the IP address.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"BOOTP","3","SOCK_BIND_FAILED","Failed to bind the socket.","The system has failed to bind the socket.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"BOOTP","3","SOCK_CREAT_FAILED","Socket creation failed for BOOTP.","Socket creation has failed for BOOTP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"BOOTP","3","SOCK_OPT_FAILED","Failed to set the option [chars] on the socket.","The system has failed to set a socket option.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"BOOTP","3","SOCK_RECV_FAILED","Receiving the BOOTP packet on a socket failed","The system has failed to receive the BOOTP packet on a socket.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"BOOTP","3","SOCK_SEND_FAILED","Sending data over the socket failed.","An error has occurred while sending data over the socket.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"BOOTP","4","TRANID_NOT_MATCH","Transaction ID [hex] of the received reply does not match the transaction ID of the response [hex]","The transaction ID of the received reply does not match the transaction ID of the response.","No action is required."
"BOOTP","7","UNKNOWN_OPT_FORMAT",".","The unknown option value is formatted.","No action is required."
"BOOTP","7","UNKNOWN_OPT_VAL","[dec]","The value of the unknown option appears.","No action is required."
"BOOTP","4","VENDOR_OPT_UNKNOWN","Unknown option: [hex]/[dec].[dec]:","Unknown options are present in the vendor field in the BOOTP packet.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"BUFF","0","BUFFER_CORRUPT","Buffer Pool id [dec] ptr [address], packet is printed on console.","The buffer pool is corrupt. An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","AP_DB_ALLOC","Unable to alloc AP entry in database for [int].[int].[int].[int]:[int]","Because of an internal error, the AP entry could not be added to the database. The AP might not work as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","AP_DB_ERR1","Unable to find AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] entry in the database, could not process [chars]","The operation that is being performed for the AP failed because the internal entry for the AP was not found. It is possible that the AP has been removed from the controller.","Use the show ap summary command to determine if the AP is still joined to the controller. If it is not, the message may be ignored. If it is still joined, restart the AP to ensure that it has the latest configuration."
"CAPWAP","3","BUFF_ALLOC","Failed to allocate buffer for [chars]","The system is out of system buffers.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","2","CAP_MSG_TRACE","[chars]","Debugging for CAPWAP packet.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","DB_CREATOR_ERR","Database entry for AP [dec]:[dec]:[dec]:[dec] is created in LWAPP, could not process [chars]","The operation that is being performed for the AP failed because the internal entry for the AP was created in LWAPP, and the message was received in CAPWAP.","Use the show ap summary command to determine if the AP is still joined to the controller. If it is not, the message may be ignored. If it is still joined, restart the AP to ensure that it will join in either CAPWAP or LWAPP."
"CAPWAP","3","DECODE_ERR","Error decoding [chars] from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The CAPWAP message that was sent by the AP was not understood by the controller. The message was dropped. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","DISC_AP_MGR_ERR1","Unable to process primary discovery request from AP on interface ([int]), VLAN ([int]), could not get AP manager [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","A discovery response could not be sent to an AP because the controller was not able to obtain the IP address of the AP manager interface.","Correct the AP manager interface configuration."
"CAPWAP","3","DISC_AP_MGR_ERR2",',"A discovery response could not be sent to an AP because the controller was not able to obtain the IP address of the AP manager interface.","Correct the AP manager interface configuration."
"CAPWAP","3","DISC_BCAST_ERR","Ignoring a discovery request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] via broadcast AP (IP = [dec].[dec].[dec].[dec]) is not in the same subnet as the controller","The controller ignored a broadcast discovery request from an AP because the AP is not on the same subnet as the controller.","No action is required."
"CAPWAP","3","DISC_INTF_ERR1","Ignoring discovery request received on non-management interface ([int]) from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","A discovery request from an AP was ignored because it was received on an invalid interface. The network configuration might be invalid.","Check the network configuration to ensure that packets from the AP are correctly routed."
"CAPWAP","3","DISC_INTF_ERR2","Ignoring discovery request received on a wrong VLAN ([dec]) on interface ([int]) from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","A discovery request from an AP was ignored because it was received on an invalid interface. The network configuration might be invalid.","Check the network configuration to ensure that packets from the AP are correctly routed."
"CAPWAP","3","DISC_MAX_AP1","Dropping discovery request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - limit for maximum APs supported [dec] reached","The maximum number of supported APs has been reached. The specified AP will not be serviced.","No action is required."
"CAPWAP","3","DISC_MAX_AP2","Dropping primary discovery request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - maximum APs joined [dec]/[dec]","The maximum number of supported APs has been reached. The specified AP will not be serviced.","No action is required."
"CAPWAP","3","DISC_MAX_DOWNLOAD","Ignoring discovery request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - maximum number of downloads ([int]) exceeded","A discovery request from an AP was rejected because the maximum number of concurrent downloads are already in progress. The AP might successfully join the controller on a later attempt.","No action is required."
"CAPWAP","3","DISC_MAX_JOIN","Rejecting discovery request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - maximum AP joins ([int]) exceeded","A discovery request from an AP was rejected because the maximum number of concurrent joins are already in progress. The AP might successfully join the controller on a later attempt.","No action is required."
"CAPWAP","4","DISC_TIME_ERR","Unable to retrieve time information while processing discovery request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Due to an internal error, the time at which the AP discovery request was received was not recorded. The AP might join the controller and function normally, but monitoring of the APs presence or absence might not work as expected.","No action is required."
"CAPWAP","3","DISC_VLAN_ERR","Received a discovery request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] on an unsupported VLAN ([int]), dropping the request","A discovery request was received on a port on which no interface was created.","Check the network configuration to ensure that packets from the AP are correctly routed."
"CAPWAP","3","DTLS_BUFF_ERR","Failed to allocate DTLS buffer to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is unable to allocate DTLS buffer for message to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","DTLS_CLOSED_ERR","[hex]:[hex]:[hex]:[hex]:[hex]:[hex]: DTLS connection closed forAP [int]:[int]:[int]:[int] ([int]), Controller: [int]:[int]:[int]:[int] ([int]) [chars]","The DTLS connection closed for the AP due to an unknown reason.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","DTLS_CONN_ERR","[hex]:[hex]:[hex]:[hex]:[hex]:[hex]: DTLS connection not found forAP [int]:[int]:[int]:[int] ([int]), Controller: [int]:[int]:[int]:[int] ([int]) [chars]","The DTLS connection was not found for the AP. Encrypting messages or processing an encrypted packet will not be possible for this AP.","Check if the AP entry is present in the database. Use the show ap summary or show dtls connection command to see if the AP entry exists in the database."
"CAPWAP","3","DTLS_DB_ERR","[hex]:[hex]:[hex]:[hex]:[hex]:[hex]: Failed to create DTLS connection for AP [int]:[int]:[int]:[int] ([int]).","The system is unable to create the DTLS database entry for the AP. The AP will not be able to join the controller.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","DTLS_DEL_ERR","Failed to disconnect DTLS connection for AP [int].[int].[int].[int] ([int]).","The system is unable to delete the DTLS database entry for the AP. The DTLS entry remains stale, and the AP might not be able to join the controller.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","ECHO_ERR","Did not receive heartbeat reply; AP: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The controller did not get a response for the AP heartbeat message. There might be connectivity issues between the AP and the controller.","Check to see if the AP has rebooted or if it has been removed from the network. Also ensure that there are no connectivity issues between the AP and the controller."
"CAPWAP","3","ENCODE_ERR","Failed to encode [chars] to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Due to an internal error, a CAPWAP message could not be transmitted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","HDR_ENCAP_ERR","Unable to encapsulate CAPWAP header for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system could not send the CAPWAP packet because of an internal error in encapsulating the packet. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","HDR_ENCAP_ERR2","Unable to encapsulate CAPWAP header for AP [int].[int].[int].[int]:[int]","The system could not send the CAPWAP packet because of an internal error in encapsulating the packet. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","IMAGE_DOWNLOAD_ERR","Refusing [chars] from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - controller image upgrade is in process","The specified request from the AP is ignored because the controller software is being upgraded. Future attempts from the AP might succeed.","No action is required."
"CAPWAP","3","IMAGE_DOWNLOAD_ERR2","Refusing image download request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - max downloads ([dec]) in progress","The system is ignoring the image download request from the AP because the maximum number of concurrent image download requests are in progress. This condition is temporary. Future attempts by the AP might succeed.","No action is required."
"CAPWAP","3","IMAGE_DOWNLOAD_ERR3","Refusing image download request from AP - unable to open image file [chars]","Due to an internal error, the image that the AP is requesting for an image download could not be obtained. The AP image download fails.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","IMAGE_DOWNLOAD_ERR4","Refusing image download request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - unable to open MD5 file [chars]","Due to an internal error, the image that the AP is requesting for an image download could not be obtained. The AP image download fails.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","INIT_ERR","Failed to initialize [chars].","Because of internal error, the module initialization failed. The AP might not be able to join the controller.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","INVALID_MSG","The system has detected an invalid message from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] type ([dec])","The information that was received on the controller was not understood. The message was dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","INVALID_MSG_TYPE","Invalid message type [dec] from [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An invalid CAPWAP message was received from the AP. The message was dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","INVALID_PAYLOAD","Invalid message element [dec] in [chars] from [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An invalid CAPWAP message element was received from the AP. The message was dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","INVALID_PAYLOAD2","Invalid message element [dec] in [chars]","An invalid CAPWAP message element was received from the AP. The message was dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","INVALID_PAYLOAD3","Invalid vendor type [dec] in [chars]","An invalid vendor type is in the CAPWAP message element from the AP. The message was dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","INVALID_PREAMBLE","Invalid preamble type ([dec]) in capwap message from [int].[int].[int].[int]:[int]","An invalid preamble type is in the CAPWAP message.The message was dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","INVALID_RET_CODE","Invalid result code [dec]. Failed to [chars]","An invalid result code resulted while processing. The message was dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","INVALID_STATE_EVENT","Invalid AP event ([dec]) and state ([dec]) combination","The event and state combination is not valid in CAPWAP. The event is ignored.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","IP_ERR","Could not plumb AP's ([hex]:[hex]:[hex]:[hex]:[hex]:[hex]) IP address ([dec].[dec].[dec].[dec]), next hop MAC ([hex]:[hex]:[hex]:[hex]:[hex]:[hex]) and VLAN ([dec]) to fast path","Because of an internal error, the IP address of the AP could not be configured in the network processor. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","IP_PROT_ERR","IP protocol ([dec]) in the received packet - from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] is not UDP, CAPWAP packets are only UDP, dropping the packet","An invalid packet received from the AP was dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","JOIN_TMR_START_ERR","Failed to start [chars] timer for AP [int].[int].[int].[int]:[int]","Because of an internal error, the timer could not be triggered. The AP might not operate as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","LRAD_MTU_ERR","Failed to set MTU [dec] for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","The path MTU for the AP could not be set properly. Fragmentation will not be at the proper MTU.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","MBUF_ERR","No more system buffers, could not receive CAPWAP packet","The system is out of system buffers.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","0","MSG_QUEUE_ERR","CAPWAP message queue has not been created","The CAPWAP subsystem has not been initialized. APs might not be able to join the controller.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","MSG_SEND_ERR2","Unable to send [chars] message to CAPWAP","The CAPWAP process might be busy. If this condition persists, it could lead to losing CAPWAP packets and dropping of AP connections. Also, APs might not getting configuration changes from the controller.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","MTU_INIT_ERR","Failed to initialize global MTU. Multicast traffic will be affected.","The initialization of the global path MTU has failed. Multicast traffic will be affected in multicast-multicast mode.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","POST_DECODE_ERR","Post decode processing failed for [chars] from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Processing of the CAPWAP message has failed after decoding the message. The AP might be disconnected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","REASSEM_LOCK_ERR","Could not obtain exclusive access to reassembly tablefor [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","Access to the internal reassembly database has failed. The CAPWAP reassembly failed, and packets might have been dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","REASSEM_MAX_FRAG","Received more fragments ([dec]) than supported. Dropping message from [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","The system has received more CAPWAP fragments than supported. The CAPWAP reassembly failed, and the packet might have been dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","REASSEM_MAX_SIZE","Unable to accomodate fragments from [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","The total size of the CAPWAP fragments is greater than the supported limit. Reassembly has failed, and the packet might be dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","REASSEM_SPACE","Unable to store capwap fragment from [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","The system has failed to store the CAPWAP fragment. Reassembly has failed, and packets might be dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","RECV_FAIL","Could not process CAPWAP packet","An internal error has occurred while processing the CAPWAP packet. The packet was dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","RESTART_ECHO_TIMER_ERR","Failed to restart heart beat timer for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is tearing down the CAPWAP connection. The system could not restart the heartbeat timer.","No action is required."
"CAPWAP","2","SEM_CREATE_ERR","Could not create semaphore [chars]","The system is unable to allocate a lock for handling operations on the internal database. The system might become unstable.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","SEM_RELEASE_ERR","Could not release exclusive access of AP entry for [hex]:[hex]:[hex]:[hex]:[hex]:[hex] in the database","Releasing access of an AP entry in the database has failed. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","SIMUL_DTLS_HANDSHAKES","Ignoring discovery request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - maximum number of simultaneous dtls sessions([int]) exceeded","A discovery request from an AP was rejected because the maximum number of concurrent DTLS handshake sessions is already in progress. The AP might successfully join the controller on a later attempt.","No action is required."
"CAPWAP","2","SOCK_ERR","Error [chars] CAPWAP socket","An internal error has occurred. The CAPWAP subsystem could not be initialized.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","SOCK_ERR2","Socket select error ([dec])","An internal error caused a temporary failure in a message handling process. The system is attempting to recover from this situation.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","SOCK_ERR3","Could not read from the CAPWAP socket","A failure occurred when processing an internal CAPWAP message. The system might become unstable.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","SOCK_ERR4","Could not read from CAPWAP socket, frame length out of bounds ([dec])","A failure occurred when processing an internal CAPWAP message. The system might become unstable.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","2","TASK_CREATE_ERR","Failed to create CAPWAP [chars] task","An internal error occurred. The CAPWAP subsystem could not be initialized. APs might not be able to join the controller.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","TEMP_AP_DB_ALLOC","Unable to alloc temporary AP entry in database for [int].[int].[int].[int]:[int]","Due to an internal error, an AP entry could not be added to the database. The AP might not join the controller.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","TMR_FREE_ERR","Failed to free [chars] timer; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An internal error occurred while processing a timer. The AP might not operate as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","TMR_START_ERR","Failed to start [chars] timer for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Due to an internal error, the timer could not be triggered. The AP might not operate as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","TMR_STOP_ERR","Failed to stop [chars] timer for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Due to an internal error, the timer stop could not be triggered. The AP might not operate as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","TX_ERR","Failed to transmit [chars] to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Because of an internal error, a CAPWAP message could not be transmitted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","TX_ERR2","Could not transmit CAPWAP control packet (error = [int])","Because of an internal error, a CAPWAP message could not be transmitted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","UDP_PORT_ERR","Received invalid UDP port ([dec]) in the packet from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex], dropping the packet","An invalid packet that was received from the AP was dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","UNSUPPORTED_TYPE","Received an invalid [chars] ([dec]): AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The information received on the controller was not understood. The message was dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CAPWAP","3","UNSUPPORTED_TYPE1","Received an invalid [chars] ([dec])","The information received on the controller was not understood. The message was dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","AP_NOT_FOUND","AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] does not exist.","The specified access point cannot be found.","Verify that this access point is registered in the current access point list on the controller."
"CCX","3","DIAG_EVENTLOG_MALLOC_FAILED","Out of memory for storing CCXv5 Event Log data from [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An internal system error has occurred.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"CCX","6","DIAG_EVENTLOG_MALLOC_SUCCESS","CCX Event Log memory allocated successfully for mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An internal system error has occurred.","This is a debug message only. No action is required."
"CCX","0","DIAG_TASK_CREATE_FAILED","Failed to create CCX diagnostic task","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","L2ROAM_GET_CFG","L2Roam Configuration file is corrupted... clearing.","The system has failed to read the L2Roam configuration file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","L2ROAM_INIT","Failed to initialize L2Roam ...","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","4","L2ROAM_LOAD_CFG","Unable to load L2Roam configuration.","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","L2ROAM_MSGID","[chars]: received invalid message id [int]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","L2ROAM_QUEUE","[chars]: message queue does not exist. Exiting...","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","L2ROAM_REG","Failed to register for LWAPP notifications.","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","0","L2ROAM_TASK_CREATE","Failed to create CCX L2Roam task [hex].","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","L2ROAM_TIMER_CREATE1","Failed to initialize L2Roam settle timer.","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","L2ROAM_TIMER_CREATE2","cannot initialize L2Roam List Update timer.","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","L2ROAM_TIMER_DEL1","Failed to delete L2Roam settle timer.","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","L2ROAM_TIMER_DEL2","Failed to delete L2Roam List Update timer.","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","L2ROAM_TIMER_START1","Failed to start L2Roam settle timer.","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","L2ROAM_TIMER_START2","Failed to start L2Roam List Update timer.","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","L2ROAM_TIMER_STOP1","Failed to stop L2Roam settle timer.","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","L2ROAM_TIMER_STOP2","Failed to stop L2Roam List Update timer.","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","L2ROAM_WRITE_CFG","Error on call to osapiFsWrite routine on config file [chars].","The system has failed to save the L2Roam configuration file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","MSGTAG001","Error on call to osapiFsWrite routine on config file [chars].","An error has occurred on a call to osapiFsWrite routine in the configuration file shown.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","MSGTAG002","CCX RM Configuration file is corrupted... clearing.","The CCX RM configuration file is corrupted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","MSGTAG003","CCX RM Client database already initialized","The CCX RM client database is already initialized.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","6","MSGTAG004","Creating AVL Tree with [dec] entries for CCX RM ClientDatabase","The system is creating an AVL Tree with the number entries shown for the CCX RM ClientDatabase.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","MSGTAG005","CCX RM Client database already initialized","The CCX RM client database is already initialized.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","6","MSGTAG006","Creating AVL Tree with [dec] entries for CCX RM ClientDatabase","The system has created an AVL Tree with the number of entries shown for CCX RM ClientDatabase.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","4","MSGTAG007","Unable to load CCX RM configuration","The system is unable to load the CCX RM configuration.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","MSGTAG008","Unable to load CCX Client RM Db(AVL Tree)","The system is unable to load the CCX Client RM Db AVL Tree.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","MSGTAG009","Unable to load CCX Bcast RM Db(AVL Tree)","The system is unable to load the CCX BCAST RM Db AVL Tree.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","MSGTAG010","Reached max Rm clients. dropping[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system has reached the maximum RM clients. The system is dropping the client shown.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","MSGTAG011","Adding to CCX RM Bcast Database failed for[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Updation of the CCX RM BCAST Database failed for[hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","4","MSGTAG012","Mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex] has unsupported CCXversion [dec]","The mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex] has an unsupported CCXversion.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","0","MSGTAG013","Failed to create CCX RM Task","The system has failed to create the CCX RM Task.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","6","MSGTAG014","Created CCX RM Task (rc=[dec])","The system has created CCX RM Task (rc=[dec]) .","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","MSGTAG015","[chars]: msg queue does not exist. Exiting...","The [chars]: msg queue does not exist. Exiting...","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","MSGTAG016","[chars]: received invalid msg id [int]","The system has received an invalid MSG ID shown.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","0","MSGTAG020","Failed to create E2E message queue","The system has failed to create an E2E message queue.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","0","MSGTAG021","Failed to create E2E message queue","The system has failed to create an E2E message queue.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","0","MSGTAG022","Failed to create E2E Task","The system has failed to create an E2E task.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","4","MSGTAG023","Unable to load e2e configuration","The system is unable to load an E2E configuration.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","MSGTAG024","Error on call to osapiFsWrite routineon config file [chars].","An error has occurred on a call to osapiFsWrite routine in the configuration file shown.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","MSGTAG025","E2E Configuration file is corrupted... clearing.","The E2E configuration file is corrupted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","0","MSGTAG026","Failed to create CCX Example Task","The system has failed to create the CCX example task.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","MSGTAG027","[chars]: msg queue does not exist. Exiting...","[chars]: msg queue does not exist.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","MSGTAG028","[chars]: received invalid msg type [int]","[chars]: The system has received invalid msg type [int]","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","4","MSGTAG029","Unable to load L2ROAM configuration","The system is unable to load the L2ROAM configuration.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","MSGTAG030","cannot initialize L2ROAM lrad Settle timer.","The system cannot initialize the L2ROAM LRAD settle timer.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","MSGTAG031","cannot start L2ROAM lrad settle timer.","The system cannot start the L2ROAM LRAD settle timer.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","MSGTAG032","cannot stop L2ROAM lrad settle timer.","The system cannot stop the L2ROAM LRAD settle timer.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","MSGTAG033","cannot uninitialize L2ROAM lrad settle timer.","The system cannot uninitialize the L2ROAM LRAD settle timer.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","MSGTAG034","cannot start L2ROAM List Update timer.","The system cannot start the L2ROAM List Update timer.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","MSGTAG035","cannot register for spam notifications.","The system cannot register for spam notifications.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","MSGTAG036","cannot initialize L2ROAM List Update timer.","The system cannot initialize the L2ROAM List Update timer.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","MSGTAG037","cannot start L2ROAM List Update timer.","The system cannot start the L2ROAM List Update timer.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","MSGTAG038","cannot stop L2ROAM List Update timer.","The system cannot stop the L2ROAM List Update timer.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","MSGTAG039","cannot uninitialize L2ROAM List Update timer.","The system cannot uninitialize the L2ROAM List Update timer.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","MSGTAG040","Error on call to osapiFsWrite routine on config file [chars].","Error on call to osapiFsWrite routine in the configuration file shown.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","MSGTAG041","L2ROAM Configuration file is corrupted... clearing.","L2ROAM Configuration file is corrupted... clearing.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","0","MSGTAG042","Failed to create CCX L2Roam Task [hex]","The system has failed to create CCX L2Roam Task [hex]","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","MSGTAG043","[chars]: msg queue does not exist. Exiting...","The system has detected that the message queue does not exist. The system is exiting.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","MSGTAG044","Error in initializing l2roam data...","The system has detected an error in initializing L2Roam data.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","3","MSGTAG045","[chars]: received invalid msg id [int]","The system has received an invalid message.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","0","MSGTAG046","Failed to create CCX S69 Task","The system has failed to create CCX S69 task.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CCX","0","MSGTAG047","Failed to create S69 message queue","The system has failed to create S69 message queue.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CDP","4","QUEUE_FULL","cdp queue is full.","The CDP queue is full. If many CDP packets come in, the CDP queue fills up quickly.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CIDS","3","ADD_RULE_FAILED","Unable to add rules for sensor [dec].[dec].[dec].[dec]\n","The system cannot add rules for the sensor.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CIDS","3","ERROR_CLEAN_UP_SENSOR","Error clean-up sensor [dec]","An error has occurred in the cleanup sensor.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CIDS","3","ERROR_RESET_RULE","Unable to reset cids rule [dec]","The system cannot reset the CIDS rule.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CIDS","3","NULL_SENSOR_POINTER","Error! NULL sensor pointer!","NULL sensor pointer!","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CIDS","3","PARSER_CLEAN_FAIL","Unable to clean cids parser","The system cannot clean the CIDS parser.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CIDS","3","PARSER_CREATE_FAIL","Unable to create cids parser","The system cannot create the CIDS parser.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CIDS","3","RESTART_TIMER_FAIL","Unable to restart timer for sensor [dec].[dec].[dec].[dec]","The system cannot restart the timer for the sensor.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CIDS","3","RULES_SETUP_FAIL","Unable to setup rules for sensor [dec].[dec].[dec].[dec]","The system is unable to set up CIDS rules.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CIDS","3","SHUN_LIST_DELETE_FAIL","ERROR! shun-list delete from AVL list failed.","The system failed to delete the shun-list from the AVL list.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CIDS","1","SHUN_LIST_ENTRY_CREATE_FAIL","Unable to create shun-list entry for ip [dec].[dec].[dec].[dec]","The system cannot create a shun-list entry.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CIDS","3","UNABLE_SSL_MUTEX_CALLBACK","Unable to ssl mutex callback for libcurl.","The system cannot perform an SSL mutex callback for libcurl.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CLI","3","INVALID_AP_KEY","Invalid AP Hash Key Provided","The system has detected an invalid AP Hash Key provided.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CLI","3","LOGIN_FAILED","Login failed. User:[chars], Service type:[dec]. [chars].","Login failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CLI","1","TRACE_LEVEL_ALERT","Level Alert.","The system has tested if the trace level Alert is enabled or not.","No action is required. This is for testing purposes only."
"CLI","2","TRACE_LEVEL_CRIT","Level Critical.","The system has tested if the trace level Critical is enabled or not.","No action is required. This is for testing purposes only."
"CLI","7","TRACE_LEVEL_DEB","Level Debug.","The system has tested if the trace level Debug is enabled or not.","No action is required. This is for testing purposes only."
"CLI","0","TRACE_LEVEL_EMER","Level Emergency.","The system has tested if the trace level Emergency is enabled or not.","No action is required. This is for testing purposes only."
"CLI","3","TRACE_LEVEL_ERR","Level Error.","The system has tested if the trace level Error is enabled or not.","No action is required. This is for testing purposes only."
"CLI","6","TRACE_LEVEL_INFO","Level information.","The system has tested if the trace level Information is enabled or not.","No action is required. This is for testing purposes only."
"CLI","5","TRACE_LEVEL_NOT","Level Notice.","The system has tested if the trace level Notice is enabled or not.","No action is required. This is for testing purposes only."
"CLI","4","TRACE_LEVEL_WARN","Level Warning.","The system has tested if the trace level Warning is enabled or not.","No action is required. This is for testing purposes only."
"CLIWEB","3","BAD_LOGO_FILENAME","File [chars] does not exist as a logo. Clearing..","The file does not exist as a logo.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CLIWEB","3","BUFFER_TOO_LONG","Buffer for [chars] too long (max = [dec] chars).","The buffer is too long.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CLIWEB","3","BUFFER_TOO_SMALL","Buffer for [chars] too small","The buffer is too small.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CLIWEB","3","INDEX_OUT_OF_RANGE","Index:[chars] out of range [dec] (max = [dec]).","The index is out of range.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CLIWEB","3","INIT_FAILED","Unable to initialize. Reason: [chars].","The system is unable to initialize.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CLIWEB","3","INVALID_PORT_SPEED","Unknown Port Speed found for interface [dec]/[dec]/[dec].","The system has found an unknown port speed for the interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CLIWEB","3","SOCKET_OPER_FAILED","Failed to [chars] the Java Socket.","A failure has occurred in a Java socket.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CLIWEB","3","WEBAUTH_ENABLE_FAILED","External Web Auth cannot be enabled. [chars].","External Web Auth cannot be enabled.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CLIWEB","3","WEBAUTH_TYPESET_FAILED","External Web Auth type cannot be set. [chars].","External Web Auth type cannot be set.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CLIWEB","3","WEBSRVR_IPSET_FAILED","Unable to set External Web Server. [chars].","The system is unable to set the External Web Server.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CNFGR","3","DUP_REGISTRATION","sysCfgChange registrar_ID [dec] already registered.","The specified Registrar ID has already registered for notifications from this module.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CNFGR","3","GET_REGISTRY_FAIL","sysCfgChange [chars] not set.","The system has failed to get the registry for the specified component.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CNFGR","0","INVALID_STARTUP_SEQ","cfgHardwareDectectCallback Invalid startup sequence.","cfgHardwareDectectCallback invalid startup sequence.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CNFGR","3","INV_COMP_ID","Invalid Component Id : [chars] ([dec]) in cfgConfiguratorInit.","The system has detected an invalid component that was requested for initialization.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CNFGR","3","L2_SYS_INIT_FAIL","Cannot initialize a required function: Layer2.","The system could not perform Layer 2 system initialization.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CNFGR","3","MAX_REGISTRATIONS","sysCfgChange registrar_ID [dec] greater then LAST_COMPONENT_ID.","Maximum number of registrations has been exceeded for this module.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"CNFGR","3","MGMT_IF_SET_FAIL","cfgHardwareDectectCallback: couldn't set mgmt vlan for vlan id [dec].","The system could not set the management interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DAPI","4","HAPI_CALLBACK_FAILED","HAPI layer has failed to receive and process the command:(CMD=[dec] , Event=[dec])","The DAPI module has received an event from a hardware port. This subsystem has invoked a corresponding callback operation of the HAPI module, which was either not properly installed during initialization or has failed to process it.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DAPI","4","HAPI_CMDCALL_FAILED","Call to HAPI layer for command:[dec] failed for user port: [int]/[int]/[int]","The DAPI module has received an event from a hardware port. This subsystem has invoked a corresponding callback operation of the HAPI module, which was either not properly installed during initialization or has failed to process it.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DEBUG","6","CLT_LOOKUP_FAIL","Client entry [hex].[hex].[hex].[hex].[hex].[hex] not found in db","The client entry has not been found in the database. The client may have disassociated with the controller.","No action is required."
"DEBUG","6","CLT_TBL_EMPTY","There are no clients in the database.","There are no clients in the database.","No action is required."
"DEBUG","4","INVALID_ELEM_ID","Received an invalid Information Element. Element id [dec] is invalid","The system has received an invalid information element.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DEBUG","4","INVALID_EVENT","Received unsupported event [dec].","The system has received an unsupported event by the task.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DEBUG","4","INVALID_LEN","Received a corrupted packet. Element Info Length [dec] received greater than DataLen [dec]","The system has received a corrupted packet.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DEBUG","4","INVALID_MODULE","Unhandled debug module [dec].","This module cannot be debugged.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DEBUG","3","MSG_POST_FAILURE","Failure to post Troubleshoot info for msg type [dec] for  MAC Address: [hex].[hex].[hex].[hex].[hex].[hex]","The system has failed to post troubleshooting information for a client. Either the client is not in the watch list or the queue for the troubleshooting task does not exist.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DEBUG","3","MSG_SEND_FAIL","Failed to send Event [chars] to Queue [chars]. Error Code is [dec]","The system is unable to send messages to the queue. The queue for the task might be full.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DEBUG","4","RMV_CLT_FAIL","Failed to remove client [hex].[hex].[hex].[hex].[hex].[hex] from watchlist","The system has failed to remove a client from the debug watchlist.","No action is required."
"DEBUG","3","START_TMR_FAIL","Trouble Shoot Timer could not be started","The system could not start the troubleshoot timer.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","3","ADD_OPTION_FAIL","Option [hex] did not fit into the packet!","The option did not fit into the packet.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","4","ADDR_NOT_ALLOCATED","No IP addresses to give -- OFFER abandoned -- packet dropped","The system has no IP addresses to give -- OFFER abandoned -- the packet has been dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","3","ADDR_NOTIN_POOL","Error: Ip Address [dec].[dec].[dec].[dec] is not in pool ([dec].[dec].[dec].[dec]-> [dec].[dec].[dec].[dec])","The IP address is not in the pool.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","4","ARP_LOOKUP_FAIL","Default gateway arp lookup failed.","The default gateway ARP lookup has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","3","ARP_SEND_FAIL",',"The system is unable to send an ARP Request.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","3","BAD_DHCP_PKT","Bad DHCP packet from [dec].[dec].[dec].[dec], dropping","The system has detected a bad DHCP packet. The system is dropping the packet.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","3","BIND_FAIL","Unable to bind the socket.","The system is unable to bind the socket.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","3","BIND_NWPORT_ERR","Binding network port failed.","Binding the network port has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","3","BIND_SRPORT_ERR","Binding service port failed.","Binding the service port has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","4","BOGUS_PKT","bogus packet, option fields too long.","The system has detected a bogus packet. The option fields are too long.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","3","BROADCAST_ADDR_NOTSET","Unable to set the broadcast address. Reason:[chars]","The system is unable to set the broadcast address.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","3","BUFF_ALLOC_ERR","Out of System buffers.","The system is out of system buffers.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","6","CHADDR_FILTER_STATE","NPU/Driver DHCP CHADDR Filter is [chars]","Informational message that indicates if the chaddr filter is enabled or not.","No action is required."
"DHCP","3","CONFIG_LOAD_FAIL","Unable to load DHCP configuration","The system is unable to load the DHCP configuration.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","3","CONFIG_SAVE_FAIL","Unable to store config file in NVRAM [chars].","The system is unable to store the configuration file in NVRAM.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","1","CRANITE_PASSTHRU","Received DHCP packet on a Cranite WLAN.","The system has received a DHCP packet on a Cranite WLAN.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","0","CREAT_TASK_FAIL","Failed to Create the task: [chars]","The system has failed to create the task.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","3","DEL_IFADDR_FAIL","Unable to delete the address on interface","The system is unable to delete the address on the interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","4","DHCP_CLEAR_FAIL","IP Address could not be de-registered for the station:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The IP address could not be unregistered.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","3","DHCP_PKT_LOOPED","Received a DHCP packet sent by the controller itself possible network loop!","A possible network loop has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","4","DHCP_PKT_OVRSIZE","Oversized DHCP packet","The system has detected an oversized DHCP packet.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","4","DHCP_PKT_WRONGSIZE","DHCP options incorrect length","The system has detected that the DHCP options have an incorrect length.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","4","DHCP_RECV_FAIL","Could not receive the dhcp packet Error.","The system could not receive the DHCP packet.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","6","DISP_SERV_ADDR","dhcp server: binding to [dec].[dec].[dec].[dec]","Informational message that indicates the IP address to which the DHCP server is binding.","No action is required."
"DHCP","3","DROP_FOREIGN_CLIENT","Dropping foreign client for dhcp retries, mac:[hex]:[hex]:[hex]:[hex]:[hex]:[hex] ip: [dec].[dec].[dec].[dec].","The system has dropped the foreign client for DHCP retries.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","4","ENCAPSULATE_FAIL","Unable to encapsulate header.","The system is unable to encapsulate the header.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","4","EXIT_PORT_NOTGET","Invalid exit port - could not resolve exit intfNum.","The system has detected an invalid exit port. The system could not resolve the exit.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","1","FORTRESS_PASSTHRU","Received DHCP packet on a Fortress WLAN.","The system has received the DHCP packet on a Fortress WLAN.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","3","GET_IFADDR_FAIL","Unable to retrieve the interface address","The system is unable to retrieve the interface address.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","3","GET_MASK_FAIL","Unable to retrieve the mask for an ip address","The system is unable to retrieve the mask for an IP address.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","4","INVALID_MSG_TYPE","Unsupported message ([hex]) -- ignoring","The system has detected an unsupported message type.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","4","INVALID_VLANID_ARP","ARP table stores invalid vlan id [dec], for the IP Addr [hex]. Expected vlan id for this ip address is [dec]","The ARP table contains a VLAN ID other than the expected ID.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","4","IPRGSTR_MSCB_FAIL","Registering IP on mscb failed for station[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Registering IP on the MSCB has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","4","LEASEIP_NEQ_CIADDR","DHCP renew/rebind error lease ip [dec].[dec].[dec].[dec] is not same as Client's ip address [dec].[dec].[dec].[dec].","The DHCP renew/rebind error lease IP is not the same as the client IP address.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","4","LEASEIP_NEQ_REQIP","Lease->ip [dec].[dec].[dec].[dec] is not same as requested ip [dec].[dec].[dec].[dec].","The lease IP is not the same as the IP requested.","No action is required."
"DHCP","4","LEASE_NOT_MATCH","Lease for [dec].[dec].[dec].[dec] does not belong to[hex]:[hex]:[hex]:[hex]:[hex]:[hex].","The DHCP lease does not match the MAC address.","No action is required."
"DHCP","4","LEASE_NOT_OBTAINED","DHCP Lease could not be allocated to the client","The DHCP lease could not be allocated to the client.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","4","MAGIC_COOKIE_INVALID","Invalid magic cookie in the DHCP packet","The system has detected an invalid magic cookie in the DHCP packet.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","4","MBL_STATION_NOTFOUND","Unable to find mscb for [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","The system is unable to find the MSCB.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","3","MSG_TRUNCATED","DHCP message getting truncated","The DHCP message is getting truncated.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","3","NETWORK_OVERLAP","Cannot have overlapping networks. Network id: [dec].[dec].[dec].[dec] in use by scope [chars]\n","The system cannot have overlapping networks. The network ID is in use by another scope.","No action is required."
"DHCP","3","NON_RELAY_PKT","The DHCP request from [dec].[dec].[dec].[dec] is a non-relay. It is dropped","The DHCP request packet has been dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","3","OPT_CHECK_EXCEED","Option checking exceeding packet limit packet Length: [dec]","The option checking exceeds the packet limit.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","3","OPT_LEN_INVALID","Option length exceeding the length of buffer for the tag [hex]","The option length exceeds the length of the buffer.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","4","OPT_LEN_ZERO","Could not add option [hex] . The length of this option is zero","The system could not add an option to the DHCP packet.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","3","RAWSOCKET_CREAT_FAIL","Unable to create raw socket.","The system is unable to create a raw socket.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","3","RAWSOCKET_SEND_FAIL","Sending packets through raw socket failed.","Sending packets through a raw socket has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","4","RELAY_SERVER_NOTGET","Unable to get the dhcp relay server's ip address","The system is unable to get the IP address of the DHCP relay server.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","3","REMOVE_LEASE_FAIL","Unable to remove [dec].[dec].[dec].[dec] from leases.","The system is unable to remove an IP address from leases.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","4","REQIP_NOT_PRESENT","Received a packet without a requested ip!.","The system has received a packet without a requested IP address.","No action is required."
"DHCP","4","RUNT_PKT_RECEIVED","DHCP proxy received runt packet, src: [dec].[dec].[dec].[dec], len =[dec]","The DHCP proxy received a runt packet.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","6","SCOPE_NOT_FOUND","Dropping packet from [dec].[dec].[dec].[dec] (unable to match to a dhcp scope)","The system is dropping a packet because it is unable to match to a DHCP scope.","No action is required."
"DHCP","4","SEND_FAIL","Unable to send DHCP packet to[hex]:[hex]:[hex]:[hex]:[hex]:[hex].","The system is unable to send the DHCP packet.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","4","SET_IPADDR_FAIL","Failed to set ip address [dec].[dec].[dec].[dec] for the interface [chars]","The system has failed to set the IP address.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","3","SOCK_CREATE_FAIL","Failed to create socket.","The system has failed to create a socket.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","3","SOCK_EXCEP","Exception occurred on the socket.","An exception has occurred on the socket.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","3","SOCK_OPT_FAIL","Failed to set the option [chars] on socket.","The system has failed to set an option on the socket.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","3","SOCK_SELECT_FAIL","select system call failed.","A select system call has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","4","UPDATE_FAP_FAIL","Unable to update foreign AP location.","The system is unable to update the foreign AP location.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","4","UPDATE_MSCB_FAIL","Failed to update MSCB state.","The system has failed to update the MSCB state.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DHCP","3","WRITE_SOCK_FAIL","write on socket failed.","A write on the socket has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1D","3","WRITE_CFG_FAIL","Failed to write config file [chars] in nv storage","The system has failed to store the configuration file in the NV storage.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1D","0","MEM_ALLOC_FAIL","[chars],Out of system memory","The system has failed to allocate memory. The system is out of system buffers.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1D","3","WRITE_CFG_FAIL","Failed to write config file [chars] in nv storage","The system has failed to store the configuration file in the NV storage.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1D","0","DATA_INIT_FAIL","Failed to allocate memory for the dot1d variables.dot1d sub-system not initialized.","The system has failed to allocate memory for the dot1d variables. The dot1d subsystem is not initialized.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1D","0","PORT_ALLOC_FAIL","Failed to allocate memory for GARP Information Declaration(GID)Port number: [hex]..","The system has failed to allocate memory for the GARP Information Declaration (GID) port.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1D","0","TASK_START_FAIL","Could not create [chars] task.Error code:[dec].The system has failed to initialize dot1d sub-system","The system could not create a task. The dot1d subsystem failed to initialize.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1D","3","BPDU_MEMGET_FAIL","Out of System buffers.","The system is out of system buffers.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1D","3","RCV_MSG_FAIL","The [chars] failed to receive a message. Internal system error.Error code:[dec].","A dot1d subsystem task has failed to receive a message. An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1D","3","RGSTR_CHANGE_FAIL","[chars].dot1d sub-system not initialized","The system is unable to register a change in the state callback. The dot1d subsystem is not initialized.","No action is required."
"DOT1D","3","SND_MSG_FAIL","Failed to send message to [chars], the message queue for the task maybe full.Error Code: [dec], Internal system error","The system has failed to send a message to a task. The message queue for the task might be full. An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1D","3","QUEUE_INIT_FAIL","Message queue  creation error.dot1d sub-system not initialized","The system has failed to initialize the dot1d message queue. The dot1d subsystem is not initialized.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1D","3","SYSINIT_GETFILE_FAIL","Failed to retrieve file from nv storage.File name [chars].dot1d sub-system not initialized","The system has failed to retrieve the file from the NV storage. The dot1d subsystem is not initialized.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1D","4","GID_ALL_USED","All Ports are used for GARP Information Declaration (GID)","All ports are used for a GARP Information Declaration (GID).","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1D","4","INVALID_BPDU_TYPE","Invalid BPDU Type [dec] received","The system has detected an invalid BPDU type received.","This is a debug message only. No action is required."
"DOT1D","6","PORT_FIND_FAIL","Port number [hex] is not found for GARP Information Declaration (GID)","A port has not been found for the GARP Information Declaration (GID).","No action is required."
"DOT1D","7","CONN_PORT_RING","GIP: Connecting Ports #[hex] to ring..","GIP: The system is connecting ports to a ring.","No action is required."
"DOT1D","7","CREATED_PORT","GID: created Port # [hex]..","GID: The system has created a port.","No action is required."
"DOT1D","7","CREATING_PORT","GID: Creating Port # [hex]..","GID: The system is creating a port.","No action is required."
"DOT1D","7","DESTROY_PORT","GID: Destroying Port # [hex]..","GID: The port has been removed.","No action is required."
"DOT1D","7","DISCON_PORT_RING","GIP: Disconnecting Ports #[hex] from ring..","GIP: Disconnecting ports from ring.","No action is required."
"DOT1D","7","HOLD_TIMER_EXP","GID: Hold Timer Expired..","GID: The hold timer has expired.","No action is required."
"DOT1D","7","JOIN_MSG_RCV","GID: Join msg is received..","GID: A join message has been received.","No action is required."
"DOT1D","7","JOIN_TIMER_EXP","GID: join Timer Expired..","GID: A join timer has expired.","No action is required."
"DOT1D","7","LEAVE_ALL_TIMER_EXP","GID: Leave All Timer Expired..","GID: A leave all timer has expired.","No action is required."
"DOT1D","7","LEAVE_EVENT_RCV","GID: Leave All event is received..","GID: A leave all event has been received.","No action is required."
"DOT1D","7","LEAVE_MSG_RCV","GID: Leave message is received..","GID: A leave message has been received.","No action is required."
"DOT1D","7","LEAVE_TIMER_EXP","GID: Leave Timer Expired..","GID: A leave timer has expired.","No action is required."
"DOT1D","7","PORT_ADD","GID: Add Port # [hex]..","GID: The system has added a port.","No action is required."
"DOT1D","7","PORT_INDEX_UNUSED","GID: Ports at index [hex] is not used..","GID: Ports at the index are not used.","No action is required."
"DOT1D","7","PROP_JOIN","GIP: propagate Join for Port #[hex]..","GIP: The system has propagated a join for the port.","No action is required."
"DOT1D","7","PROP_LEAVE","GIP: propagate Leave for Port #[hex]..","GIP: The system has propagated a leave for the port.","No action is required."
"DOT1D","7","RMV_PORT","GID: Removing Port # [hex] from the ring..","GID: The system is removing a port from the ring.","No action is required."
"DOT1D","7","START_HOLD_TIMER","GID: Start Hold Timer..","GID: A start hold timer has occurred.","No action is required."
"DOT1D","7","START_JOIN_TIMER","GID: Start Join Timer..","GID: A start join timer has occurred.","No action is required."
"DOT1D","7","START_LEAVE_TIMER","GID: Start Leave All Timer..","GID: A start leave all timer error has occurred.","No action is required."
"DOT1Q","3","FILE_WRITE_FAIL","Failed to write to a config file. File Name: [chars].","The system has failed to write to a configuration file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1Q","3","FLASH_READ_FAIL","Error retrieving file [chars] from system flash.","An error has occurred when retrieving the file from the system flash.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1Q","3","GID_FIND_PORT","Failed to find a gid port. Port # [dec].","The system has failed to find a GID port.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1Q","3","GIP_CREATE_FAIL","Failed to Create GIP..","The system has failed to create a GIP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1Q","3","GVR_CREATE_FAIL","Failed to Create GVR.","The system has failed to create a GVR.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1Q","3","GVR_TO_DTL","Failed to get the link state for an interface. Port # [dec]","The system has failed to get the link state for an interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1Q","3","INVALID_CONFIG_REQ","Invalid configuration request. Failed to send vlan configuration request","The system has detected an invalid configuration request. The system has failed to send the VLAN configuration request.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1Q","3","INVALID_CONFIG_REQ_RCV","Invalid configuration received. Failed to service vlan configuration request.","The system has detected an invalid configuration received. The system has failed to service the VLAN configuration request.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1Q","3","LAG_CALBAK_FAIL","Link Aggregation malfunctioned while initializing Vlan.","A link aggregation has malfunctioned while initializing a VLAN.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1Q","3","MBUF_GET_FAIL","Unable to transmit GVRP packet for port # [dec]. Out of system buffers.","The system is unable to transmit a GVRP packet. The system is out of system buffers.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1Q","3","MEM_ALLOC_FAIL","Failed to allocate memory.","The system has failed to allocate memory.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1Q","3","MIN_VLAN_FAIL","No VLANs created upon initialization.","No VLANs have been created upon initialization.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1Q","3","MODIFY_VLAN_FAIL","Bridge not initialized. Cannot modify vlan. Vlan Id:[dec]","The bridge has not been initialized. The system cannot modify a VLAN.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1Q","3","NOTIFY_USERS_FAIL","Failed to notify registered users. Vlan Id: [dec].Interface: [dec]","The system has failed to notify registered users.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1Q","3","UPDATE_PSTNT_FAIL","Problem updating persistent data for VLAN [dec].","There is a problem when updating persistent data for a VLAN.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1Q","3","UPDATE_TNZNT_FAIL","Problem updating transient data for VLAN [dec].","There is a problem when updating transient data for a VLAN.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1Q","3","VLAN_CONFIG_FAIL","Failed to configure Vlan. Vlan Id: [dec].","The system has failed to configure a VLAN.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1Q","3","VLAN_CREATE_MODIFY_FAIL","Failed to create or modify vlan. Vlan Id: [dec]","The system has failed to create or modify a VLAN.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1Q","3","VLAN_DELAVL_FAIL","Failed to delete a vlan Entry from the AVL tree.VLAN [dec].","The system has failed to delete a VLAN entry from the AVL tree.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1Q","3","VLAN_DEL_FAIL","Failed to delete all static vlans. Number of failures: [dec]","The system has failed to delete all static VLANs.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1Q","3","VLAN_ENTRY_FAIL","Failed while updating data for VLAN [dec] in the avl tree","The system has failed while updating data for a VLAN.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1Q","3","VLAN_FIND_FAIL","Vlan [dec] does not exist or invalid Vlan ID","The requested VLAN does not exist.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1Q","3","VLAN_MBR_SET","Failed to set an interface to vlan. Vlan Id: [dec]. Interface: [dec]","The system has failed to set an interface to the VLAN.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1Q","3","VLAN_PORTMBR_FAIL","Failed to get port membership information for vlan.Port # [dec].","The system has failed to get port membership information for a VLAN.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1Q","3","VLAN_RANGE_FAIL","Attempt to create a vlan with an invalid vlan id [dec].","The system has attempted to create a VLAN with an invalid VLAN ID.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1Q","3","VLAN_RGS_FAIL","VLAN registration failed. Registrar: [dec].","The VLAN registration failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1Q","3","VLAN_TYPEGET_FAIL","Failed to get the Vlan Type. Port # [dec].","The system has failed to get the VLAN type.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1Q","6","DB_FULL","GVRP: Data Base is FULL. Port #: [dec]","GVRP: The database is full.","No action is required."
"DOT1Q","6","MAX_VLAN_FAIL","No available entries for VLAN ID [dec]. Maximum number of Vlans allowed exceeded","These are no available entries for the VLAN ID. The maximum number of VLANs allowed have been exceeded.","No action is required."
"DOT1Q","7","CREATE_GVR","GVRP: Create GVR.","GVRP: The system has created a GVR.","No action is required."
"DOT1Q","7","DSTR_GVR","GVRP: Destroying GVR..","GVRP: The GVR has been removed.","No action is required."
"DOT1Q","7","GVR_ADD_PORT","GVRP: GVR add Port # [hex]..","GVRP: The GVR has added a port.","No action is required."
"DOT1Q","7","GVR_RMV_PORT","GVRP: GVR removed Port # [hex]..","GVRP: The GVR removed a port.","No action is required."
"DOT1Q","7","JOIN_MSG_RCV","GVRP: Join msg is received. Port #: [dec].","GVRP: A join message has been received.","No action is required."
"DOT1Q","7","LEAVE_ALL_TMR_EXP","GVR: delete attribute Timer Expired..","GVR: A delete attribute timer has expired.","No action is required."
"DOT1Q","7","LEAVE_MSG_RCV","GVRP: Leave msg is received. Port #:[dec].","GVRP: A leave message has been received.","No action is required."
"DOT1Q","7","PORT_ENABLED","Port is Enabled. Port #: [dec].","The port is enabled.","No action is required."
"DOT1Q","7","PORT_JOINING","GVRP: Port # [hex] is joining..","GVRP: The port is joining.","No action is required."
"DOT1Q","7","PORT_LEAVING","GVRP: Port # [hex] is leaving..","GVRP: The port is leaving.","No action is required."
"DOT1Q","7","TX_GVR","GVRP: Transmitting msg. Port # [dec].","GVRP: The system is transmitting a message.","No action is required."
"DOT1X","1","ABORT_AUTH",',"An internal error caused 802.1X authentication to be aborted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","1","AUTHENTICATOR_ERR","Could not function as authenticator - [chars]; client [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Client authentication failed because an internal error occurred in the 802.1X authentication process.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","1","DOT1X_CB_NULL","802.1X control block NULL for mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Client authentication failed because an internal control block was unexpectedly null.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","1","SEND_AAA_FAILED","Could not send AAA message.[chars]. Mobile: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Client authentication failed because an internal error prevented a message from being sent to the authentication server.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","1","INVALID_WPA_KEY_STATE","Received EAPOL-key message while in invalid state ([int]) - version [int], type [int], descriptor [int], client [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An authentication message was received from a client that was not expected while in the current state. The message was ignored.","If the problem persists, try upgrading the client driver software or using different client software to isolate the cause. Also investigate possible intruder activity."
"DOT1X","1","SET_BRDCST_KEY_ERR","Could not set broadcast keys for WLAN [int]; GTK length [int], Max GTK Buffer [int]","Unable to configure the broadcast keys for the WLAN.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","1","SOCK_OPER_FAILED","Socket [chars] operation failed on 802.1X socket","An internal error caused a socket processing failure.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","1","VALIDATE_REPLAY_CTR_FAILED","Could not Validate the replay counter in packet. [chars]. Got: [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]. Expected: [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]. Mobile: [hex] [hex] [hex] [hex] [hex] [hex]","Client authentication failed because an EAPOL message from the client contained an invalid replay counter.","If the problem persists, try upgrading the client driver software or using different client software to isolate the cause. Also, investigate possible intruder activity."
"DOT1X","3","AAA_SEND_ERR","Error sending AAA message - [chars]; client [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Client authentication has failed because an internal error prevented a message from being sent to the authentication server.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","3","AAA_SEND_FAILURE","Unable to send AAA message for client [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Client authentication has failed because a message could not be sent to the authentication server.","Review the message log for other messages preceding this one that might indicate a connection failure or configuration problem. Ensure that the authentication servers are properly configured and are reachable."
"DOT1X","3","ABORT_AUTH","Authentication Aborted","An internal error caused 802.1X authentication to be aborted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","3","ADD_KEYMAP_KEY_ERR","Unable to add key mapping key to EAPOL-key message for client [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Unable to add the mapping key in the EAPOL key message to the client.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","3","AUTHKEY_TX_TRANS_ERR","Authentication state transition to state [int] failed; port status [int], key available [int], key tx enabled [int]","Client authentication failed because an internal error occurred during the authentication state transition.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","3","CLIENT_NOT_FOUND","Unable to process 802.1X [int] msg - client [hex]:[hex]:[hex]:[hex]:[hex]:[hex] not found","A message on an internal queue could not be processed because the client indicated that the message was not found in the internal database.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","3","COMPUTE_PRF_FAILED","Failed to compute PRF mode [int], size [int] - [chars]","An internal error occurred when attempting to calculate a pseudorandom value.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","3","EAP_MSG_ERR","Could not process EAP message - [chars]; client [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Client authentication failed because an EAP message from the server or supplicant was not understood.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","3","EAPOL_MSG_ATTACK",',"Client authentication failed because an EAPOL message from the client contained data that should only be sent by the access point. This issue might be caused by an intruder that is spoofing authentication frames.","If the problem persists, try upgrading the client driver software or using different client software to isolate the cause. Also investigate possible intruder activity. If this does not solve the problem research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information."
"DOT1X","3","GTK_ENCRYPT_FAILED","Unable to encrypt CCKM GTK for client [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Client authentication failed because an internal error occurred when attempting to encrypt a temporal key.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","3","INTF_DEL_FAILED","Unable to delete 802.1X interface","An internal error prevented an 802.1X interface structure from being deleted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","3","INVALID_CLIENT_DOT1X_CB","Missing 802.1X control block for client [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Client authentication failed because an internal control block was unexpectedly null.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","3","INVALID_DOT1X_CB","Missing 802.1X or client control block","Client authentication failed because an internal control block was unexpectedly null.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","3","INVALID_DOT1X_Q_TYPE",',"A message on an internal message queue could not be processed because the message type was invalid.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","3","INVALID_EAP_MSG","Invalid EAP message received - [chars]; EAP Id [int], 802.1X Id [dec], client [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An invalid EAP message was received from the client. The message was ignored.","If the problem persists, try upgrading the client driver software or using different client software to isolate the cause. Also investigate possible intruder activity. If this does not solve the problem research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information."
"DOT1X","3","INVALID_EAPOL_VER","Invalid EAPOL version ([int]) in EAPOL-key message; type [int], descriptor [int], client [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Client authentication failed because of an authentication protocol error between the client and access point.","If the problem persists, try upgrading the client driver software or using different client software to isolate the cause. Also investigate possible intruder activity."
"DOT1X","3","INVALID_KEY_LEN",',"An internal error occurred when determining the key length for an encryption cipher.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","3","INVALID_KEYWRAP_ARG","Invalid key wrap parameters","Client authentication failed because an internal error caused invalid data to be passed to the key wrap algorithm.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","3","INVALID_KEYWRAP_PKT","Received invalid keywrap packet - [chars]","Client authentication failed because a received keywrap packet was invalid.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","3","INVALID_PTK_LEN",',"Client authentication failed because an internal error occurred when attempting to compute a temporal key.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","3","INVALID_RC4_KEY","Invalid EAPOL RC4 key msg from client [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - [chars]","Client authentication failed because an EAPOL RC4 key message from the client contained invalid data.","If the problem persists, try upgrading the client driver software or using different client software to isolate the cause. Also investigate possible intruder activity."
"DOT1X","3","INVALID_REPLAY_CTR","Invalid replay counter from client [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - got [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex], expected [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]","Client authentication failed because an EAPOL message from the client contained an invalid replay counter.","If the problem persists, try upgrading the client driver software or using different client software to isolate the cause. Also investigate possible intruder activity."
"DOT1X","3","INVALID_WPA_KEY_MSG","Error in received EAPOL msg - [chars]; version [int], type [int], descriptor [int], client [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Client authentication failed because of an authentication protocol error between the client and access point.","If the problem persists, try upgrading the client driver software or using different client software to isolate the cause. Also investigate possible intruder activity."
"DOT1X","3","INVALID_WPA_KEY_MSG_STATE",',"Client authentication failed because of an authentication protocol error between the client and access point.","If the problem persists, try upgrading the client driver software or using different client software to isolate the cause. Also investigate possible intruder activity."
"DOT1X","3","KEY_LEN_NOT_FOUND",',"An internal error occurred when attempting to determine the key length for an encrypted policy.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","3","MAX_EAPOL_KEY_RETRANS","Max EAPOL-key M[int] retransmissions exceeded for client [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Client authentication failed because the client did not respond to an EAPOL-key message.","Ensure that user credentials are correct on the client and on the AAA server."
"DOT1X","1","MAX_EAPOL_KEY_RETRANS_FOR_MOBILE","Max EAPOL-key M[int] retransmissions reached for mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Client authentication failed because the client did not respond to an EAPOL-key message.","Ensure that user credentials are correct on the client and on the AAA server."
"DOT1X","1","MAX_EAP_IE_RETRIES_REACHED","Reached Max EAP-Identity Request retries (num) for STA [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Client authentication failed because the client did not respond to an EAP request message.","Ensure that user credentials are correct on the client and on the AAA server."
"DOT1X","3","MAX_EAP_RETRANS","Max EAP retransmissions exceeded for client [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Client authentication failed because the client did not respond to an EAP request message.","Ensure that user credentials are correct on the client and on the AAA server."
"DOT1X","3","MAX_EAP_RETRIES","Max EAP identity request retries ([int]) exceeded for client [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Client authentication failed because the maximum number of permitted attempts was exceeded.","Ensure that user credentials are correct on the client and on the AAA server."
"DOT1X","3","MOBILE_EXCESS_RUN","Authentication has run more than [int] times - deleting client [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Client authentication failed because the authentication process failed to complete within the maximum permitted number of attempts.","Ensure that user credentials are correct on the client and on the AAA server."
"DOT1X","3","PREPARE_KEY_M5_ERR","Unable to create EAPOL-key M5 - group key not found for WLAN [int]","Client authentication failed because an internal error occurred when attempting to create an EAPOL-key message","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","3","PSK_CONFIG_ERR","Client [hex]:[hex]:[hex]:[hex]:[hex]:[hex] may be using an incorrect PSK","A client may be attempting to access the network with an improperly configured PSK.","Ensure that user credentials are correct on the client and on the AAA server."
"DOT1X","3","RCV_INVALID_CCX_IE","[chars] with [chars] CCX IE received from client [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Client authentication failed because of an authentication protocol error between the client and access point.","If the problem persists, try upgrading the client driver software or using different client software to isolate the cause. Also investigate possible intruder activity."
"DOT1X","3","RCV_INVALID_SFA_IE","[chars] with [chars] SFA IE received from client [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Client authentication failed because of an authentication protocol error between the client and access point.","If the problem persists, try upgrading the client driver software or using different client software to isolate the cause. Also investigate possible intruder activity."
"DOT1X","3","SEND_WPA_BUFF_ERR","Unable to send EAPOL-key - buffer is too small; size [int], state [int], client [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Client authentication failed because the retransmit buffer was too small to store the outbound authentication message.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","3","UNKNOWN_EAPOL_KEY_DESC",',"Client authentication failed because an EAPOL message from the client contained an invalid or unsupported key descriptor.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","3","USER_LOGIN_DENY","Authentication rejected for user [chars] - user may already be logged in","User authentication failed. The most likely cause is that the username is already in use by another client.","Ensure that unique usernames are used by each client."
"DOT1X","3","WPA_KEY_MIC_ERR","TKIP MIC errors reported in EAPOL key msg from client [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Client authentication failed because the client reported TKIP MIC errors in an EAPOL key message that it received from the controller. This issue might be caused by an intruder and countermeasures may have to be taken.","If the problem persists, try upgrading the client driver software or using different client software to isolate the cause. Also investigate possible intruder activity."
"DOT1X","3","WPA_SEND_STATE_ERR",',"Client authentication failed because the session was not in the correct state when attempting to send an EAPOL-key message.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","4","AAA_MAX_RETRY","Max AAA authentication attempts exceeded for client [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Client authentication has failed because the maximum number of authentication attempts permitted by the authentication was exceeded. If blacklisting is configured, the client will be blacklisted.","Ensure that user credentials are correct on the client and on the AAA server."
"DOT1X","4","BE_RCV_NULL_ARG","Empty message received from AAA","An AAA message with no content was received by the AAA back-end process. The message was ignored.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","4","DOT1X_MAX_RETRY","Max authentication attempts exceeded for client [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Client authentication failed because the maximum number of retries was exceeded.","Ensure that user credentials are correct on the client and on the AAA server."
"DOT1X","4","EAP_CLIENT_NO_RETRANS","EAP packet is too long for retransmission","An EAP message was sent to the client but is too large to be stored in the retransmission queue. If the message is not acknowledged as having been received by the client, it will not be retransmitted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","4","IGNORE_PREAUTH","Ignoring pre-auth request from client [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","A preauthentication request message from a client was ignored.","No action is required."
"DOT1X","4","INTF_NOT_FOUND","Unable to find 802.1X interface for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Client authentication failed because the 802.1X interface of the AP was not found. This issue might have been caused by the sudden loss of connection to the AP, where the client reassociates with another AP, or with the same AP when it recovers.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","4","INVALID_MSG_TYPE","Invalid message type [int] received from AAA","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.Error Message    %DOT1X-4-RCV_INVALID_EAPOL_PKT: Invalid EAPOL packet type [int] received from client [hex]:[hex]:[hex]:[hex]:[hex]:[hex] Explanation    An EAPOL packet with an unknown type was received from a client. The packet was ignored.","If the problem persists, try upgrading the client driver software or using different client software to isolate the cause. Also investigate possible intruder activity."
"DOT1X","4","RCV_NULL_ARG","Empty message received from AAA","An AAA message with no content was received. The message was ignored.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","4","RCV_SHORT_EAP_ATTR","Received short EAP Attribute for client [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An invalid EAP attribute was received from AAA and was ignored.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","4","RCV_UNKNOWN_AVP","Received unknown AVP ([int]/[int]) for client [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An unknown attribute-value pair was received during EAP processing. The AVP was ignored.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT1X","4","TRUNCATE_USERNAME","Truncated user name from [int] to [int] characters for client [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The username supplied by a client was longer than permitted and has been truncated.","No action is required."
"DOT1X","4","USER_MAX","Authentication rejected for user [chars] - max number of users ([int]) exceeded","User authentication failed because the maximum permitted number of users are already connected.","No action is required."
"DOT1X","6","CCKM_UPDATE","CCKM association for [hex]:[hex]:[hex]:[hex]:[hex]:[hex] updated; parameter [chars], value [int]","A CCKM association parameter has been modified.","No action is required."
"DOT1X","6","WARP_PARAM_UPDATE","WARP association for [hex]:[hex]:[hex]:[hex]:[hex]:[hex] updated; parameter [chars], value [int]","A WARP association parameter has been modified.","No action is required."
"DOT3AD","3","FAIL_CONFIG_WRITE","Failed to store config file [chars] in nv store","The system failed to store the configuration file in the NV storage.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT3AD","0","FAIL_DOT3AD_MSGQ","LAG: Unable to create msg queue for dot3ad lac task.","LAG: The system is unable to create a message queue for the dot3ad lac task. The dot3ad subsystem is not initialized.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT3AD","0","FAIL_DOT3AD_SEM","Unable to create a dot3ad semaphore.","The system is unable to initialize a dot3ad semaphore. The dot3ad subsystem is not initialized.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT3AD","3","FAIL_DOT3AD_REBOOT","LAG in transition..Swtich reboot DUE..!!","A LAG is in transition. A switch reboot is due.","No action is required."
"DOT3AD","3","FAIL_DOT3AD_SYSBUF","Out of System buffers.","The system is out of system buffers.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT3AD","0","FAIL_LAC_CREATE","Failed to create dot3ad LAC task.","The system has failed to create the dot3ad LAC task. The dot3ad subsystem is not initialized.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DOT3AD","0","FAIL_LAC_INIT","Unable to initialize dot3ad lac task.","The system is unable to initialize the dot3ad lac task. The dot3ad subsystem is not initialized.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","0","SOCK_OPER_FAILED","Socket [chars] operation failed.","A socket operation has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","1","ARP_PKT_RECVD","Received ARP packet on a [chars] WLAN.","The system has received an ARP packet through the CRANITE/FORTRESS WLAN.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","0","END_LOAD_FAILED","Failed to load Enhanced Network Driver.","The system has failed to load an enhanced network driver.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","1","ARP_POISON_DETECTED","STA [[hex]:[hex]:[hex]:[hex]:[hex]:[hex], [dec].[dec].[dec].[dec]] ARP (op [int]) received with invalid SPA [int].[int].[int].[int]/TPA [int].[int].[int].[int]","The system might have detected ARP spoofing or poisoning. However, this message does not necessarily imply that any malicious ARP spoofing has occurred. The message appears when the following conditions are true:-A WLAN is configured with DHCP Required, and a client device, after associating on that WLAN, transmits an ARP message without first completing DHCP. This may be normal behavior; it could happen, for example, when the client is statically addressed, or when the client is holding a valid DHCP lease from a prior association. The resulting message might look like this example: DTL-1-ARP_POISON_DETECTED: STA [00:01:02:0e:54:c4, 0.0.0.0] ARP (op 1) received with invalid SPA 192.168.1.152/TPA 192.168.0.206The effect of this condition is that the client will be unable to send or receive any data traffic until it acquires a valid DHCP address through the WLC. Table 10-1 lists explanations for each segment of the example message above.Table 10-1 Explanations for ARP_POISON Message SegmentsMessage SegmentExplanationDTL-1-ARP_POISON_DETECTEDThe controller received an ARP packet from a client in DHCP_REQ state.STA [00:01:02:0e:54:c4, 0.0.0.0]The client ('STA,' an 802.11 wireless station) has a MAC address of 00:01:02:0e:54:c4 and an IP address unknown to the controller ('0.0.0.0').ARP (op 1)The offending packet received from the client was an ARP request (opcode 1).invalid SPA 192.168.1.152/TPA 192.168.0.206The source IP address (SPA: 'sender protocol address') of the ARP request was 192.168.1.152. The target IP address (TPA, or 'target protocol address') of the ARP request was 192.168.0.206.","When you see this message, perform one of these tasks::"
"DTL","1","IP_CONFLICT_DETECTED","Network device with mac addr [hex]:[hex]:[hex]:[hex]:[hex]:[hex] using IP address of local interface '[chars]'.[int].[int].[int].[int] - Received ARP [chars] ([int]) on interface [int] with vlan ID [int]. IP conflict is detected","The IP address of one of the interfaces on the switch is being used by another network element.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","APENTRY_CONF_FAILED","Unable to configure an AP entry. [chars]. Intf=[dec]","The system is unable to configure an AP entry.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","APENTRY_DEL_FAILED","Unable to delete AP entry due to [chars] (=[dec])","The system is unable to delete an AP entry.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","APENTRY_ADD_FAILED","Unable to Add AP entry due to [chars] (=[dec]).","The system is unable to add an AP entry.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","ARPDATA_LOOP_DETECTED","Found an Arp Data looping from [dec]. Drop it","The system has found an ARP data loop from a particular interface. The system will drop it.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","ARP_SEND_FAILED","Could not send [chars] to [hex]:[hex]:[hex]:[hex]:[hex]:[hex]. VLAN=[dec], Intf=[dec]. [chars].","The system could not send an ARP packet.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","CALLBACK_PROC_FAILED","Callback for command:[dec] failed for user port: [int]/[int]/[int]","A DTL callback process has failed unexpectedly.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","DSINTF_SET_FAILED","Unable to configure the Distribution Service Interface [chars].","The system is unable to set the distribution service interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","DSNET_BCAST_FAILED","Failed to [chars] broadcast on the WLC.","The WLC forwards the broadcast traffic only when broadcasting is enabled. The toggling of this state has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","DSNET_CONF_FAILED","Unable to set [chars] on Distribution Service interface.","The system is unable to set the specified parameter on the distribution service interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","DSNET_MCAST_FAILED","Failed to [chars] multicast on the WLC.","The WLC forwards multicast traffic only when multicasting is enabled. Toggling this state has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","DSNET_MCAST_MODE_FAILED","Failed to set multicast mode to [chars] on the WLC.","The WLC can forward multicast packets by encapsulating the multicast packet in either a unicast LWAPP packet or a multicast LWAPP packet. Toggling this mode has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","DSPORT_DEL_FAILED","Could not delete Distribution Service port: [dec]. [chars].","The system could not delete the distribution service port.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","FAP_ADD_FAILED","Could not add a Foreign AP port. [chars]. Port Intf = [dec].","The system could not add a foreign AP port.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","FAP_DEL_FAILED","Could not delete a Foreign AP port. [chars]. Port Intf = [dec].","The system could not delete a foreign AP port.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","FDBMAC_ADD_FAILED","Unable to add an MAC entry. [chars].","The system is unable to add a MAC entry.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","INTFTBL_CONF_FAILED","Unable to configure Interface table entry.The DAPI command [chars] failed","The system is unable to configure an interface table entry.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","INVALID_ARP_TIMEOUT_ADDR","MAC entry ([hex]:[hex]:[hex]:[hex]:[hex]:[hex]) received for timeout is INVALID. Dropping it.","A MAC entry received for a timeout is INVALID. The system is dropping the entry.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","INVALID_MCAST_UPORT","Invalid usp ([int],[int],[int]) used for multicast!","An invalid user port was used for a multicast.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","INVALID_NODEINFO_TYPE","Unsupported information type([dec]) found for interface [dec].","An unsupported information type has been found.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","INVALID_PORT_INDEX","Using invalid port [int] to index Port Table","The system is using an invalid port to index the port table.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","MAC_DELETE_ALL_FAILED","Failed to delete all entries from table. Could not delete [dec] MAC entries.","The system has failed to delete all MAC entries from the table.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","MCAST_STREAM_REG_FAILED","Could not register a multicast stream on the interface [dec].","The system could not register a multicast stream.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","MIBOBJ_INIT_FAILED","DTL device failed to initialize MIB2 table.","The DTL device failed to initialize a MIB2 table.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","MSG_Q_ENQUEUE_FAILED","Failed to enqueue message to DTL message queue. Head=[hex], Tail=[hex], Count=[dec].","The system has failed to enqueue the message to the DTL message queue.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","MSG_Q_FULL","DTL msg queue is FULL. Head=[hex], Tail=[hex], Count=[dec].","The DTL message queue is full.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","NPUARP_ADD_FAILED","Unable to add an ARP entry for [dec]:[dec].[dec].[dec] to the network processor. [chars].","The system is unable to add an ARP entry to the network processor.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","NPUARP_DEL_FAILED","Unable to delete an ARP entry for [dec]:[dec].[dec].[dec] from the network processor. [chars].","The system is unable to delete an ARP entry from the network processor.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","NPUMAC_DEL_FAILED","Unable to delete the MAC address [hex]:[hex]:[hex]:[hex]:[hex]:[hex] from the network processor. [chars]","The system is unable to delete a specific MAC address entry from the network processor.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","OSARP_ADD_FAILED","Unable to add an ARP entry for [dec]:[dec].[dec].[dec] to the operating system. [chars].","The system is unable to add an ARP entry to the operating system.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","OSARP_DEL_FAILED","Unable to delete an ARP entry for [dec].[dec].[dec].[dec] from the operating system. [chars]","The system is unable to delete an ARP entry from the operating system.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","PDU_RECEIVE_FAILED","Failed to receive a PDU. USP:[dec]/[dec]/[dec]. Family=[dec], Cmd=[dec], Event=[dec].[chars]","The system has failed to receive a network packet.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","PKT_TX_ERROR","Failed to transmit a packet of type [dec],USP:[dec]/[dec]/[dec].","The system has failed to transmit a network packet on a particular device interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","RESTART_TIMER_FAILED","[chars]","The system has failed to start the ARP timeout timer.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","SCBIP_ADD_FAILED","Unable to plumb SCB IP entry with key [hex]:[hex]:[hex]:[hex]:[hex]:[hex] for station [hex]:[hex]:[hex]:[hex]:[hex]:[hex] to NPU","The system is unable to plumb the SCB IP entry to the NPU.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","SCBIP_DEL_FAILED","Unable to remove SCB IP entry for [hex]:[hex]:[hex]:[hex]:[hex]:[hex] from NPU","The system is unable to remove an SCB IP entry from the NPU.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","TBTBL_CONF_FAILED","Unable to configure token bucket table entry.The DAPI command [chars] failed","The system is unable to configure a token bucket table entry.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","TUNNEL_PKT_SEND_FAILED","Could not tunnel a packet to [hex]:[hex]:[hex]:[hex]:[hex]:[hex]. VLAN=[dec], Intf=[dec]. [chars].","The system could not tunnel a packet.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","4","ACL_SET_FAILED","Could not set an ACL entry. ACL Id=[dec]. [chars].","The system could not set an ACL entry.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","4","ARPMAP_DEL_FAILED","[chars]","The system has failed to delete the ARP MAP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","4","DSINTF_GET_FAILED","Unable to get the interface set for distribution system.","The system is unable to get the interface set for the distribution system.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","4","FDBCMD_RECV_FAIILED","Failed to process command from user port [dec]/[dec]/[dec]. Family=[dec], Cmd=[dec], Event=[dec]. [chars].","The system has failed to process a command from the user port.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","4","GRAT_ARP_NOTSENT","Did not send Gratuitous ARP to defend IP address ([int].[int].[int].[int]) of local interface '[chars]'.","A gratuitous ARP that was sent to defend the IP address was held due to rate limiting.","No action is required."
"DTL","4","INVALID_DOT1D_STATE","Received invalid DOT1D state [dec], for interface [dec].","The system has received an invalid DOT1D state for an interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","4","IPPROTO_RECV_NOT_READY","DTL interface not yet ready to accept IP frames.","The DTL interface is not ready to accept IP frames. It has not been initialized.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","6","ARP_ADD_FAILED","Unable to insert an ARP entry for [dec].[dec].[dec].[dec] to the ARP table.","The system is unable to insert an ARP entry to the ARP table.","No action is required."
"DTL","6","ARPDATA_QUEUE_OVERLOAD","ARP input q exceeds limit. Current val = [dec]","The ARP task input queue has exceeded its limit. See if there is an ARP loop in the network.","No action is required."
"DTL","6","ARP_DEL_FAILED","Could not delete the ARP entry for [dec].[dec].[dec].[dec] from the ARP table.","The ARP entry to be deleted does not exist.","No action is required."
"DTL","6","ARP_PKT_TYPE_NOT_EOIP","Received tunneled arp packet type [dec] is not EOIP","The system has received an ARP packet that should be tunneled from a foreign controller. It should contain the EOIP type.","No action is required."
"DTL","6","ARP_TABLE_FULL","ARP table is full.Could not add the new entry","The ARP table is full. The system could not add the new entry.","No action is required."
"DTL","6","ARP_WRONG_ETYPE","Received Wrong Ethertype [dec]  to arp task .","The system has received an Ethernet type that is not an ARP type.","No action is required."
"DTL","6","MAC_DELETE_FAILED","Failed to delete MAC entries in ARP Send Table.","The system has failed to delete MAC entries in the ARP send table.","No action is required."
"DTL","6","RX_ARP_LWAPP_CTL","Received lwapp ctl packet to arp task at wrong place.","The received Ethernet type is an LWAPP type. It should not be LWAPP control.","No action is required."
"DTL","6","TUNNELED_NOT_ARP","Received tunneled packet type [dec] is not a arp packet.","The system has received tunneled ARP requests that should have ARP type packets.","No action is required."
"DTL","6","TUNNELED_NOT_BCAST","Received tunneled packet type is not a broadcast packet.","The system has received tunneled ARP requests that should have broadcast packets.","No action is required."
"DTL","6","VAPID_OUT_OF_RANGE","ssid [dec] of the client is out of range","The system has received tunneled ARP requests that should be broadcast packets.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","7","ARP_DELETE_STATUS","ARP Table is Full. Deleting the entry with IP: [int].[int].[int].[int]and Mac Address: [hex]:[hex]:[hex]:[hex]:[hex]:[hex] [chars]","This is a status of the request to delete the IP/MAC entry from the ARP table.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","7","END_LOAD_DONE","Done loading Enhanced Network Driver....","The system has finished loading the enhanced network driver.","No action is required."
"DTL","7","END_LOAD_STARTED","Loading Enhanced Network Driver.","The system is loading the enhanced network driver.","No action is required."
"DTL","7","RESOLV_REQ_DROPPED","[hex]:[hex]:[hex]:[hex]:[hex]:[hex] is not a client,dropping the resolve request","The controller is dropping the ARP resolve request because the client could not be found.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTLS","3","ALLOC_FAILED","Resource allocation failed\n","The system failed to allocate a resource to complete the requested DTLS operation.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","APID_DEL_FAILED","Unable to delete AP Id entry due to [chars] (=[dec])","The system is unable to delete the AP ID entry.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","MOBTUN_ADD_FAILED","Unable to configure Mobility tunnel. [chars]. port=[dec] vlan=[dec]","The system is unable to configure the mobility tunnel.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","MOBTUN_DEL_FAILED","Unable to delete Mobility tunnel due to [chars]. port=[dec]","The system is unable to delete the mobility tunnel.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","TUN_ADD_TO_RG_FAILED","Unable to add AP to multicast replication group. [chars]. (=[dec])","The system is unable to add an AP to the multicast replication group.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTL","3","TUN_DEL_TO_RG_FAILED","Unable to delete AP from multicast replication group. [chars]. (=[dec])","The system is unable to delete an AP from the multicast replication group.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTLS","3","HANDSHAKE_FAILURE","Failed to complete DTLS handshake with peer [int].[int].[int].[int]\n","An error occurred during a DTLS handshake. The session will be closed.","Reestablish the DTLS session."
"DTLS","3","HANDSHAKE_TIMEOUT","Failed to complete DTLS handshake with peer [int].[int].[int].[int]\n","An error occurred during a DTLS handshake timeout.","Reestablish the DTLS session."
"DTLS","3","HASH","DTLS connection hash table error - [chars].\n","An error occurred when accessing the DTLS connection hash table.","No action is required."
"DTLS","3","LIBRARY_ERROR","[chars] while communicating with peer [int].[int].[int].[int]\n","An unexpected value has been returned from the underlying DTLS library.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTLS","3","PKI_ERROR","PKI initialization error : [chars] \n","An error occurred while initializing the PKI for the DTLS.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTLS","3","RECORD_ERROR","Erronous record received - [chars].\n","An invalid record has been received. It will be ignored.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"DTLS","3","UNKNOWN_CONNECTION","Local port [int] is not assocated with any established DTLS connection\n","The system cannot perform the specified operation because the specified local port is not associated with any established DTLS connection.","Use a port that is associated to an established DTLS connection."
"DTLS","4","BAD_CERT","Certificate verification failed. Peer IP: [int].[int].[int].[int]\n","The DTLS peer has presented an invalid certificate.","No action is required."
"DTLS","4","BAD_COOKIE","DTLS cookie verification failed. Peer IP: [int].[int].[int].[int]\n","The DTLS peer has presented an invalid cookie.","No action is required."
"DTLS","5","ESTABLISHED","DTLS connection established on local port [int]\n","A DTLS connection has been established on the indicated port.","No action is required."
"DTLS","5","ESTABLISHED_TO_PEER","DTLS connection established to [int].[int].[int].[int]\n","A DTLS connection has been established on a peer.","No action is required."
"DTLS","5","PEER_DISCONNECT","DTLS peer [int].[int].[int].[int] has closed connection.\n","The DTLS peer has sent a message to close the connection.","No action is required."
"DTL","6","ARP_ADD_FAILED","Unable to insert an ARP entry for [dec].[dec].[dec].[dec] to the ARP table.","The system is unable to insert an ARP entry into the ARP table.","No action is required."
"DTLS","6","DUPLICATE_RECORD","Duplicate record received - ignored.\n","A duplicate record has been received. It will be ignored.","No action is required."
"DTLS","6","RECORD_IGNORED","Record ignored - [chars].\n","The record has been ignored for the reason specified in the error message.","No action is required."
"EAP","3","MSGQUEUEFAILED","IOS Proc shim: Unable to enqueue message to proc","IOS message queue simulation: The system is unable to enqueue a message to process.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"EAP","3","NOPROCQUEUE","EAP global process Queue not enabled!","The EAP global process queue is not enabled.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"EAP","3","TIMERINITFAILED","Cannot init timer","The system cannot initialize or create a timer.","Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration."
"EMT","2","OUT_OF_MEMORY_ERROR2","Unable to allocate semaphore.","The Ethernet Multisegment Topology task has failed to initialize correctly.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"EMT","2","TASK_CREATE_ERROR","Failed to Create EMT Task..","The Ethernet Multisegment Topology task has failed to start correctly.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"EMT","2","TASK_INIT_ERROR1","Did not initialize array ptable_entry_count correctly !.","The Ethernet Multisegment Topology task has failed to initialize correctly.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"EMT","2","TASK_INIT_ERROR2","Did not initialize array ptable correctly !.","The Ethernet Multisegment Topology task has failed to initialize correctly.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"EMT","2","TIMER_CREATE_ERROR","Failed to create EMT Hello Timer","The Ethernet Multisegment Topology task failed to initialize correctly.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"EMT","3","CONFIG_SAVE_ERROR","osapiFsWrite failed on [chars].","The EMT configuration could not be saved correctly.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"EMT","3","MSG_DELIVERY_ERROR1","Cannot deliver timer message to emt task!.","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"EMT","3","MSG_DELIVERY_ERROR2","Cannot deliver enable/disable message to emt task!.","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"EMT","3","OUT_OF_MEMORY_ERROR1","Out of System buffers.","The system might be running low on memory.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"EMT","3","UNSUPPORTED_MSG_RECVD","EMT Task: Received unsupported message.","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"EMWEB","1","BUFFER_TOO_MANY","Received too many Http buffers from a session. BufCount([dec]) > Max ([dec]), BufLen= [dec]. Aborting session.","The system has received too many HTTP buffers from a session. The system is aborting the session.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"EMWEB","1","LOGIN_FAILED","Login failed. User:[chars]. [chars].","The system has failed to log on.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"EMWEB","3","ATTACK_DETECTED","Detecting an attack from [chars]. [chars]. Disconnecting","The system has detected an attack and is disconnecting.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"EMWEB","3","CERTIFICATE_NOT_FOUND","Unable to find Web Authentication Certificate.  [chars].","The system is unable to find the web authentication certificate.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"EMWEB","3","CONN_REJECT","An incoming connection has been rejected. [chars].","The system has rejected an incoming connection.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"EMWEB","3","FORM_SUBMIT_FAILED","Form submit action failed. [chars].","A form submit action has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"EMWEB","3","INVALID_SOCK_NAME","Unable to get socket name. Error: [chars].","The system is unable to get the socket name.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"EMWEB","3","RECV_FAILED","Failed to receive a web request. [chars]","The system has failed to receive a web request. The system is unable to allocate a buffer to receive the packet. This issue can occur if there is a DoS attack.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"EMWEB","4","CLI_OUTPUT_TRUNCATED","CLI output has been truncated. Line no: [dec].","The CLI output has been truncated.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"EMWEB","4","CONSOLE_CLOSED","Closing serial console connection.","The system is closing the serial console connection.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"ETHOIP","4","ARP_SEND_ERROR","Unable to send ARP Request for [int].[int].[int].[int]","An ARP request send has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"ETHOIP","2","DS_PORT_NOT_FOUND","Unable to find the DS port while trying to send an Ethernet over IP ping message.","An internal error has occurred while sending an Ethernet over IP ping message.","Configure DS port if not configured. Otherwise, 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 athttp://www.cisco.com/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"ETHOIP","2","LOCK_CREATE_ERROR","Failed to create Ethernet-over-IP ping lock.","The mobility failover and guest redundancy services did not start correctly.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"ETHOIP","2","SOCKET_OPEN_ERROR","Unable to open Ethernet-over-IP socket","A mobility failover or guest redundancy services might have been affected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"ETHOIP","2","TASK_INIT_ERROR1","Failed to create Ethernet-over-IP socket rx task.","A mobility failover and guest redundancy services did not start correctly.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"ETHOIP","2","TASK_INIT_ERROR2","Failed to create ethoip osapi queue.","A mobility failover and guest redundancy services did not start correctly.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"ETHOIP","2","TASK_INIT_ERROR3","Failed to create ethoip osapi receive task.","A mobility failover and guest redundancy services did not start correctly.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"ETHOIP","3","INVALID_PING_REPLY_RECVD2","Drop Ethernet-over-IP ping reply from [int].[int].[int].[int]; expected reply from [int].[int].[int].[int]","The Ethernet over IP task has dropped an unexpected ping reply.","No action is required."
"ETHOIP","3","INVALID_PKT_OPTYPE_RECVD","Recv Ethernet over IP pkt from [int].[int].[int].[int], unrecognized opcode [dec]","The system has received an Ethernet over IP packet of the incorrect type.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"ETHOIP","3","INVALID_PKT_RECVD","Ethernet over IP pkt too short; pkt size=[int], expected min=[int]","An invalid Ethernet over IP packet has been received.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"ETHOIP","3","INVALID_PKT_SUBTYPE_RECVD","Recv Ethernet over IP ping pkt from [int].[int].[int].[int]: ethtype=[hex], expected [hex]","The system has received an Ethernet over IP ping packet of the incorrect type.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"ETHOIP","3","MOBILITY_PEER_NOT_FOUND","ping to [int].[int].[int].[int] failed, no mobility record found for the peer.","The ping destination was not found in the mobility list.","Check the mobility list configuration on the controller."
"ETHOIP","3","OSAPI_MSG_RECV_ERROR","Could not rx osapi msg.","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"ETHOIP","3","OUT_OF_MEMORY_ERROR","Out of System buffers.","The system might be running low on memory.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"ETHOIP","3","PING_RECVD_FROM_NON_MEMBER","Drop Ethernet-over-IP ping reply from [int].[int].[int].[int]; not a mobility peer","The Ethernet over IP task has dropped a ping reply from an unknown source.","Compare the mobility list configuration on the controller with that on the ping sender."
"ETHOIP","3","PING_RESPONSE_TX_FAILED","Failed to tx a ping response to [int].[int].[int].[int], rc=[dec]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"ETHOIP","3","PING_SEND_ERROR1","Mobility ping to [int].[int].[int].[int] rejected, not a mobility peer","Internal system information","Check the mobility configuration on this WLC to see if it has the peer listed."
"ETHOIP","3","PING_SEND_ERROR2","Mobility ping to [int].[int].[int].[int] rejected, transmit count [dec] exceeds allowed value [dec].","The mping command has failed.","Enter the mping command again with a valid transmit count."
"ETHOIP","3","PING_SEND_ERROR3","Mobility ping to [int].[int].[int].[int] failed, osapi msg to mobility task failed","The mping command has failed due to internal error.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"ETHOIP","3","PING_TRANSMIT_FAILED","[chars]: Failed to tx Ethernet over IP ping rc=[dec].","An internal system error has occurred.","Check the logs preceding this error. If no possible resolution is found, 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"ETHOIP","3","PKT_RECV_ERROR","[chars]: ethoipRecvPkt returned error","An internal system error has occurred.","If this message recurs, 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"ETHOIP","3","SOCKET_READ_ERROR","read from dtl Ethernet-over-IP socket failed.","A mobility failover or guest redundancy services might be running into socket issues.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"ETHOIP","3","SOCKET_REOPEN_ERROR","Unable to re-open Ethernet-over-IP socket","A mobility failover or guest redundancy services might be running into socket issues.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"ETHOIP","3","SOCKET_SELECT_ERROR","select from Ethernet-over-IP socket failed with error [dec]","A mobility failover or guest redundancy services might be running into socket issues.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"ETHOIP","4","RECVD_PKT_FROM_NON_MEMBER","Recv Ethernet over IP ping from [int].[int].[int].[int], not from a mobility peer","This controller has received an Ethernet over IP ping from a nonmember.","Check mobility configuration on this WLC and its peer to see if it needs correction. If the problem persists, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"ETHOIP","4","GW_RESOLVE_ERROR","ping to [int].[int].[int].[int] failed, cannot resolve next-hop gw, rc=[dec]","The next hop gateway could not be resolved for the ping destination address.","Debug your network to allow the resolution of the next hop gateway to this destination."
"ETHOIP","4","RECVD_PKT_WITH_INVALID_GROUP","Recv Ethernet over IP ping from [int].[int].[int].[int]   in different Group","This controller has received an Ethernet over IP ping with the group ID that is not matching this controller.","Check the mobility configuration on this WLC and its peer to see that groups are configured properly."
"ETHOIP","4","RECVD_PKT_WITH_INVALID_VERSION","Recv Ethernet over IP ping from [int].[int].[int].[int],  with invalid version","This controller has received an Ethernet over IP ping with a version that does not match this controller.","Check the code version on this WLC and its peer to see if they match. If the problem persists, open a case with the Technical Assistance Center."
"ETHOIP","6","INVALID_PING_REPLY_RECVD1","Drop bogus Ethernet-over-IP ping reply from [int].[int].[int].[int]","The Ethernet over IP task has dropped a ping reply.","No action is required."
"ETHOIP","6","PING_REPLY_FAILED","ping reply to [int].[int].[int].[int] failed, rc=[dec]","The previous message possibly carries the reason for the ping failure.","No action is required."
"ETHOIP","6","PING_REQUEST_FAILED","ping request to [int].[int].[int].[int] failed, rc=[dec]","The previous message possibly carries the reason for the ping failure.","No action is required."
"ETHOIP","6","ARP_TO_RESOLVE_GW","Cannot reach [int].[int].[int].[int], no ARP entry for next-hop gw [int].[int].[int].[int] so tx ARP req.","An attempt is being made to resolve the next hop gateway.","No action is required."
"FDB","0","MSGTAG001","Failed to Create fdb Task..","The system has failed to create an FDB task.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"FDB","3","MSGTAG002","Error retrieving file [chars].","An error has occurred when retrieving the file [chars].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"FDB","3","MSGTAG003","LIF: Unable to register for VLAN change callback.","The system is unable to register for a VLAN change callback.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"FDB","3","MSGTAG004","Error on call to osapiFsWrite routine on config file [chars].","An error has occurred on a call to the osapiFsWrite routine in the configuration file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"FDB","3","MSGTAG005","fdb Task: Failed to create, exiting.....","The system has failed to create the FDB task and is now exiting.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"FIPS","3","AP_ZEROIZATION_FAILED","Unable to zeroize the AP key. [chars].","FIPS requires a mechanism to zeroize a critical security parameter. An error occurred while trying to zeroize the AP secret.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"FIPS","3","LOADCONF_FAILED","Unable to load configuration.","The system has failed to load the FIPS configuration.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"FIPS","3","ZEROIZATION_FAILED","Unable to reset the system key. [chars].","FIPS requires a mechanism to reset a critical security parameter. An error occurred while trying to reset the system key.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"FIPS","3","ZEROIZE_AP_FAILED","Unable to reset the AP key. [chars].","The system is unable to reset the AP key.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"FIPS","3","ZEROIZE_CFM_SEND_FAILED","Unable to reset the AP key. [chars].","An error has occurred while trying to confirm an AP key reset.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"FIPS","3","ZEROIZE_REQ_SEND_FAILED","Unable to reset the AP key. [chars].","An error has occurred while trying to send a reset key request to the AP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"FIPS","4","DUPLICATE_NDRNG_OUTPUT","Duplicate non-deterministic RNG output. Auto-seeding...","A FIPS continuous RNG test has failed. FIPS requires that two consecutive NDRNG blocks must not be the same.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"FIPS","4","DUPLICATE_RNG_OUTPUT","Duplicate FIPS 186-2 RNG output. Auto-seeding...","A FIPS continuous RNG test has failed. FIPS requires that two consecutive RNG blocks must not be the same.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"FIPS","4","PREREQMODE_SET_FAILED","Unable to set FIPS prerequisite mode because it is already [chars].","The FIPS prerequisite mode is already set.","No action is required."
"FIPS","4","RNGSEEDKEY_MATCHED","FIPS 186-2 Seed matches Seed Key. Auto-seeding...","FIPS requires that the RNG seed must not be the same as the RNG seed key.","No action is required."
"FIPS","6","AP_ZEROIZATION","AP key zeroization initiated.","FIPS requires a mechanism to zeroize a critical security parameter.","No action is required."
"HIFN","3","DHMAPMEM","error return [dec] while mapping DH structs","A call for mapping various structures for the public key and the private key has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"HIFN","3","DHMEMOVERRUN","Memory overrun in DH parameter","An error has occurred when some tasks overwrite into DH structure memories. A memory overrun has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"HIFN","3","DHSYNCEXECFAIL","error return [dec] while execution of command","A call to execute a command on the security processor has returned a failure.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"FLEXCONNECT","3","MSGTAG001","Unable to write flexconnect configuration file.","The system is unable to write the FlexConnect configuration file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"FLEXCONNECT","6","MSGTAG002","Configuration file version < 4.2.2.3","The configuration file is a version earlier than software release 4.2.2.3.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"IAPP","2","TASK_INIT_ERROR1","Failed to create IAPP socket rx task..","The IAPP task has failed to start correctly.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"IAPP","2","TASK_INIT_ERROR2","Unable to open IAPP socket","The IAPP socket has failed to open.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"IAPP","3","AP_NOT_FOUND","AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] does not exist.","An access point could not be found.","Check if this AP is registered in the current AP list on the controller and if this message recurs, 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"IAPP","3","INVALID_PKT_RECVD","invalid subType([dec]) in iappProcessLocpClientPackets","An invalid IAPP packet has been received.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"IAPP","3","MOBILE_NOT_FOUND","mobile station [hex]:[hex]:[hex]:[hex]:[hex]:[hex] does not exist.","A mobile station could not be found.","Check if this mobile station is listed in the current client list on the controller and if this message recurs, 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"IAPP","3","OUT_OF_MEMORY_ERROR","Out of System buffers.","The system might be running low on memory.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"IAPP","3","SCOKET_READ_ERROR","read from dtl IAPP socket failed.","An IAPP task is experiencing problems while processing packets.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"IAPP","3","SOCKET_OPEN_ERROR","Unable to re-open IAPP socket","An IAPP task is experiencing problems while processing packets.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"IAPP","3","SOCKET_SELECT_ERROR","select from IAPP socket failed with error [dec]","An IAPP task is experiencing problems while processing packets.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"IAPP","3","UNSUPPORTED_MSG_RECVD","unsupported message [dec] from LOCP to client","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"IDMGR","3","ID_MANAGER_INTERNAL_ERROR","[chars]","An internal error has occurred with the ID Manager.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"IDMGR","3","INTERRUPT","[chars]","There has been an attempt to get the ID at the interrupt level.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"IDMGR","3","INVALID_ID","bad id in [chars] (id: [hex])","An ID Manager error has occurred.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"IDMGR","3","INVALID_ID_TABLE_SIZE","bad new ID table size","A bad new table request to ID Manager has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"IDMGR","3","MALLOC_FAILURE","[chars]","A MALLOC failure has occurred in the ID Manager.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"INIT","0","DRIVER_OPEN_FAILED","Failed to open the driver [chars]","The system has failed to open the driver.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"INIT","0","LICENSED_CRASH","License daemon exited abnormally with signal.:%d","The license daemon has exited abnormally.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"INIT","0","LICENSED_EXIT_NORMAL","License daemon exited normally with code [dec].","The license daemon has exited normally.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"INIT","0","LICENSED_FORK_FAILED","Failed to spawn the license daemon.","The system has failed to spawn the license daemon.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"INIT","0","LICENSED_RESTART_NOTIFY","Failed to send notification of the restart event.","The system has failed to a send a notification of the restart event.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"INIT","0","LICENSED_START_FAILED","Failed to start the license daemon.","The system has failed to start the license daemon.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"INIT","0","SEM_CREAT_FAILED","Failed to create semaphore for the INIT task.","The system has failed to create a semaphore for the INIT task.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"INIT","0","SET_I2CADDR_FAILED","Failed to set the I2C device address for dual Gig card.","The system has failed to set the I2C device address for a dual Gigabit card.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"INIT","0","READ_GIGCARD_FAILED","Failed to read data from dual Gig card.","The system has failed to read data from a dual gigabit card.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"INIT","0","TASK_CREAT_FAILED","Failed to create the task [chars].","The system has failed to create a task.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"INIT","0","WRITING_INVALID_VALUE_TO_SERVICE_PORT","Writing invalid value of [hex] to control register of service port phy.","The system is writing an invalid value to the control register of the service port.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"INIT","0","WRITE_GIGCARD_FAILED","Failed to write data to dual Gig card.","The system has failed to write data to a dual gigabit card.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"INIT","2","MOUNT_FAILED","[chars][dec].","The system is unable to mount or unmount the AP image directory (/mnt/images).","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"INIT","3","CREAT_SOCK_FAILED","Failed to open socket to read MAC address from eth[dec].","The system has failed to open a socket to read the MAC address.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"INIT","3","FILE_OPEN_FAILED","Failed to open the file [chars].","The system has failed to open a file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"INIT","3","INIT_GIGCARD_FAILED","Failed to initialize dual Gig card.","The system has failed to initialize a dual Gigabit card.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"INIT","3","MDIO_CMD_INVALID","Invalid MDIO command [dec]","The system has detected an invalid MDIO command.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"INIT","3","PARSING_FAILED","Unable to parse the content of the file [chars].","The system is unable to parse the content of a file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"INIT","3","READ_EEPROM_FAILED","Failed to read MAC address from EEPROM.","The system has failed to read a MAC address from EEPROM.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"INIT","3","READ_HWADDR_FAILED","Failed to read MAC address from eth[dec].The ioctl call failed for [chars].","The system has failed to read a MAC address.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"INIT","3","TRANSCEIVER_NOT_DETECTED","No transceivers detected.","No transceivers have been detected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"INIT","3","TRANSCEIVER_DOWN","Transceiver [chars] is down","A transceiver is down.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"INIT","6","FE_MODULE_NOT_FOUND","Fast Ethernet Module not found.","A Fast Ethernet module has not been found.","No action is required."
"INIT","6","SWITCHING_TRANSCEIVER","Switching to Transceiver [chars].","The system is switching to another transceiver.","No action is required."
"INIT","6","SECURITY_MODULE_NOT_FOUND","Security Module not found.","The security module has not been found.","No action is required."
"INIT","7","INIT_LED","Initializing LEDs","The system is initializing LEDs.","No action is required."
"INIT","7","SWITCH_BOOTING","Switch booting...","The switch is booting.","No action is required."
"IOS","3","INV_CERT_LEN","LOCAL-AUTH(SHIM): Received peer cert too big (size [int])","The system has received a peer certificate that is too big.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"IOS","3","INV_PARAM","OPSSL_PARSER: Received a NULL ctx in verify callback","The system has received a null ctx in a verify callback. An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"IOS","3","PEER_CERT_DECODE_FAIL","LOCAL-AUTH(SHIM): Unable to decode peer device cert  for session [hex]","The system is unable to decode a peer device certificate for the specified session.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"IOS","3","PEER_CERT_GET_FAIL","LOCAL-AUTH(SHIM): Unable to retrieve peer device cert for session [hex]","The system is unable to retrieve a peer device certificate for the specified session.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"IOS","3","PEER_CERT_VER_FAIL","LOCAL-AUTH: Peer cert (user '[chars]') failed '[chars]' check","The system has failed to authenticate the specified user.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"IOS","3","PEER_CERT_ZERO_LEN","OPSSL_PARSER: Received a zero len cert from peer for session [hex]","The system has received a zero len certificate from a peer for the specified session.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"IPSTAT","3","STATS_CREATE_FAIL","ipStatsCreate: Could not create [chars] counters for interface [dec].","The system could not create statistical counters. An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"L7API","0","SYS_INIT_FAIL","SystemInitStatus is corrupt [hex]","The SystemInitStatus is corrupt.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"L7COMM","3","ACL_NAME_TOO_LONG","aclName too long","The ACL name is too long.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"L7COMM","3","VLAN_NAME_TOO_LONG","vlanIfName too long","The vlanIfName is too long.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LAG","0","TASK_CREATE_FAIL","Could not create Lag Task. Lag not initialized","The system could not create a LAG task. The LAG is not initialized.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LAG","0","QUEUE_CREATE_FAIL","Unable to create msg queue for Lag Task. Lag initialization failed.","The system is unable to create a message queue for the LAG task. LAG initialization has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LAG","3","CMD_WAIT_FAIL","Lag command failed to complete for Interface: [dec].","The LAG command has failed to complete for an interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LAG","3","CONFIG_INIT_FAIL","Failed to apply component startup configuration for Lag.","The system has failed to apply the component startup configuration for LAG.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LAG","3","CREATE_NEW_FAIL","Could not create LAG from NV config data entry.","The system could not create the LAG from the NV configuration data entry.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LAG","3","CRTLBLK_GET_FAIL","Cannot create LAG '[chars]'. Exceeded Maximum number of LAG interfaces possible.","The system cannot create the LAG. The maximum number of LAG interfaces have been exceeded.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LAG","3","FILE_WRITE_FAIL","Failed to write to configuration  file [chars].","The system has failed to write to the configuration file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LAG","3","INIT_FAIL","Failed to initialize Link Aggregation.","The system has failed to initialize Link Aggregation.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LAG","3","INTF_FIND_FAIL","Interface [dec] not found in LAG [dec] member list.","The interface has not been found in the LAG member list.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LAG","3","INVALID_COMMAND","Invalid command received.","An invalid command has been received.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LAG","3","INVALID_CONFIG_PARAMS","Cannot create LAG '[chars]'. Invalid configuration parameters.","The system cannot create the LAG because of invalid configuration parameters.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LAG","3","MODIFY_FAIL","Failed to modify LAG [chars]. Invalid configuration parameters. Try configuring without any members or all members must be full-duplex and have same speed. Interface: [dec]","The system has failed to modify the LAG because of invalid configuration parameters. Try configuring without any members or all members must be full duplex and have the same speed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LAG","3","MODIFY_INTERNAL_ERR","Failed to modify LAG [chars]. Internal system error. Interface: [dec]","The system has failed to modify the LAG because of an internal system error.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LAG","3","MSG_SND_FAIL","Failed to send message to Lag for a state change request. Interface: [dec]","The system has failed to send a message to the LAG for a state change request.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LAG","3","NIM_INFOGET_FAIL","Could not get NIM information for LAG interface [dec]. Failed to initialize LAG.","The system could not get NIM information for a LAG interface. The system has failed to initialize the LAG.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LAG","3","NV_READ_FAIL","Error retrieving file [chars] from flash","An error occurred while retrieving the file from the flash memory.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LAG","3","REG_CALBAK_FAIL","Unable to register for interface state changeLAG not initialized.","The system is unable to register for an interface state change. The LAG is not initialized.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LAG","4","INCOMPATIBLE_PORT_SPEED","All members of lag must have same speed. Interface [dec] has speed different from all other members of Lag. Removing from Lag.","All members of the LAG must have the same speed. One of the members of the LAG has a different speed different than all other members. The system is removing that interface from the port bundle.","No action is required."
"LAG","4","INTF_SPEED_UPDATED","Speed of interface [dec] updated with the speed of all other members of Lag.","The speed of the interface has been updated with the speed of all other members of the LAG.","No action is required."
"LAG","3","STAT_INIT_FAIL","Failed to initialize statistical counters for interface. Interface: [dec]","The system has failed to initialize statistical counters for an interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LAG","3","TASK_SYNC_FAIL","Could not synchronize the Lag TASK. Lag not initialized.","The system could not synchronize a Lag task. The Lag was not initialized.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","3","AKC_MISMATCH","Generated key [chars] does not match with the user-configured key [chars]. Sw Key: [chars]","The generated key does not match the user-configured key.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","3","CARD_MODEL_INVALID","NEC license does not support the card model [hex].","The NEC license does not support a card model.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","3","CHECKSUM_INCORRECT","NEC SKC [chars] checksum [chars] is incorrect.","The NEC SKC has an incorrect checksum.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","6","DECODE_KEY_FAILED","Failed to decode the temporary key [chars].","The system has failed to decode the temporary key.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","3","FEATURE_ID_UNKNOWN","NEC SKC [chars] has unknown feature field [chars].","The NEC SKC has an unknown feature field.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","3","FEATURE_MISMATCH","The feature [chars] in the SKC [chars] does not match the image","The feature in the SKC does not match the image.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","0","FEATURE_TURNED_OFF","NEC key [chars] with feature [chars] has [chars]. AP features are off.","The NEC key has expired or has been deleted. AP features are disabled.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","3","FILE_ACCESS_FAILED","Failed to access the compressed file [chars].","The system has failed to access the compressed file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","3","FILE_INTEGRITY_FAILED","File integrity failed.","A file integrity failure has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","3","FILE_LEN_BIG","The length of the file [chars] is [int]. It is bigger than the maximum limit [int].","The length of the file is bigger than the maximum size limit.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","3","FILE_OPEN_FAILED","Failed to open the file [chars].Error: [chars].","The system has failed to open a file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","3","FILE_READ_FAILED","Failed to read the file [chars].Error: [chars].","The system has failed to read a file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","3","FILE_RETRIEVE_FAILED","Failed to retrieve the file [chars] from NV memory.","The system has failed to retrieve the AV file from the NV memory.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","3","FILE_SIZE_MISMATCH","Actual size of the file [chars] ([dec] bytes) mismatches with the size retrieved using fstat ([dec] bytes).","The actual size of the file does not match with the size retrieved using FSTAT.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","3","FILE_WRITE_FAILED","Failed to write the config file [chars] into NV Memory.","The system has failed to write the license configuration file into the NV memory.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","3","FSTAT_FAILED","Failed to obtain the status of the file [chars].The fstat system call failed.Error: [chars].","The system has failed to obtain the status of a file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","3","GET_VER_FAILED","cannot get software release number.","The system cannot get a software release number.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","3","INVALID_VER_STR","The software release string [chars] is invalid.[chars].","The software release string is invalid.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","3","KEY_EXPIRED","NEC key [chars] with feature [chars] has [chars].","The NEC key has expired or has been deleted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","3","KEY_GEN_FAILED","Generating the license key failed. serial <[chars]> product <[dec]> sw release<[dec].[dec].[dec].[dec]> swrelease length [dec].","The license key generation has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","3","KEY_ISSUER_INVALID","The SKC key is neither temporary nor production key.It is rejected.","The SKC key is not a temporary or production key.The system has rejected the key.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","3","KEY_LEN_INVALID","[chars] [chars] has invalid length [dec].","The key code has an invalid length.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","4","LIC_AGENT_OFF","License Agent is turned off. UDI=[chars]","The license agent on this device is not running.","Check the device configuration. Enable License Agent."
"LICENSE","3","LICENSE_INTEGRITY_FAILED","License integrity failed.","A license integrity failure has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","0","LICENSE_KEY_MISMATCH","Image and NEC license key mismatch. All AP functionalities are disabled.","The image and NEC license key do not match. All the AP functionality is disabled.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","3","MEM_ALLOC_FAILED","Failed to allocate memory of [dec] bytes.","The system has failed to allocate memory.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","4","NEC_KEY_DROPPED","No memory to add NEC key [chars]; user should delete a key.","The system does not have enough memory to add the NEC key; you must delete a key.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","3","PROD_ID_MISMATCH","ProdSeries(hw=[chars] sw=[chars]) or ProdID(hw=[chars] sw=[chars]) mismatch between hw and sw keys (SKC=[chars])","The hardware and software keys do not match. The product series or the product IDs for the keys might also not match.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","7","READ_LICENSE_FILE","Reading the license file [chars].Serial No: [chars].Product : [dec]. sw release:[dec].[dec].[dec].[dec].sw release length [dec].","The system is reading the license file.","No action is required."
"LICENSE","7","REBUILDING_CFG_FILE","Rebuilding the default configuration for '[chars]'","The system is rebuilding the default license configuration file.","No action is required."
"LICENSE","3","SAVE_TMPKEY_FAILED","Failed to save the NEC temp key [chars] into config file, and clearing it from the running config.Return code [dec].","The system has failed to save the NEC temporary key into the configuration file. The system is clearing it from the running configuration.","No action is required."
"LICENSE","0","SEM_CREAT_FAILED","Failed to create license semaphore.","The system has failed to create a license semaphore.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","0","TEMP_KEY_EXPIRED","NEC temporary key [chars] expired.","A NEC temporary key has expired.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","3","TIMER_CREAT_FAILED","Failed to create a NEC license timer.","The system has failed to create a NEC license timer.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","3","TIMER_START_FAILED","Failed to start the NEC license timer.","The system has failed to start the NEC license timer.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE","3","TMP_KEY_REUSED","Rejected NEC key [chars] configuration. Re-use of the same temporary key is not allowed.","The system has rejected a NEC key configuration because reusing the same temporary key is not allowed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE_IMAGE_APPLICATION","3","FAILED","[chars], rc = [dec]","The licensing subsystem failed to create a process or a watched boolean to watch the request from the remote show subsys license commands.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LICENSE_IMAGE_APPLICATION","6","LICENSE_LEVEL","Module name = [chars] Next reboot level = [chars] and License = [chars]","This is an informational message to display the change in the next reboot license level.","No action is required."
"LICENSE_IMAGE_APPLICATION","6","LICENSE_LEVEL_CONFIG","Please issue 'license boot' config command to make extension license ([chars]) available for use.","This is an informational message to inform the user to make the extension license available to support the image level.","Configure the licensing image level."
"LICENSE_IMAGE_APPLICATION","6","NO_LICENSE","[chars] [chars].","There is no valid license available on this device.","Purchase a license to activate required features."
"LICENSE_IMAGE_APPLICATION","3","UNKNOWN_EVENT","[chars]","The image licensing subsystem received an event that it does not understand or recognize.","Capture the error message and forward it to the appropriate licensing component."
"LICENSE_IMAGE_APPLICATION","3","UNKNOWN_VERSION","[chars]","The image licensing subsystem received an event for an unknown version of a feature.","Capture the error message and forward it to the appropriate licensing component."
"LOCP","3","CERT_AAA_ERR","LOCP: LBS cert AAA Error for [chars]","LOCP: The controller LBS-SSC AuthList has failed to validate a certificate.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LOCP","3","INIT_FAIL","LOCP Task failed to initialize","The LOCP receive task has failed to initialize and cannot accept incoming LOCP messages.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LOCP","3","INV_CERT_LEN","LOCP: Received invalid peer cert (size [int])","The system has received an invalid peer certificate that is too big.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LOCP","3","PEER_CERT_VER_FAIL","LOCP: LBS cert verification failed check","LOCP: The controller has failed to validate the LBS peer certificate.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LOG","3","FILE_OPEN_FAIL","Unable to open crash file [chars]. Error: [chars]","The system is unable to open the specified crash file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LOG","3","FILE_WRITE_FAIL","Error on call to osapiFsWrite routine on config file [chars].","The system has failed to write the configuration file for the LOG subsystem.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LOG","7","SERVICE_STARTED","syslog services started!","Syslog services have started.","No action is required."
"LOG","3","RAW_FILE_OPEN_FAIL","Unable to open raw partition: [chars]. Error: [chars]","The system is unable to open the raw partition to read the watchdog data.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LOG","3","RAW_FILE_READ_FAIL","Unable to read from the raw partition: [chars]. Error: [chars]","The system is unable to read the watchdog data from the raw partition.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LOG","3","WD_FILE_CREAT_FAIL","Unable to create the watchdog file: [chars]. Error: [chars]","The system is unable to create the watchdog file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LOG","3","WD_FILE_WRITE_FAIL","Unable to write to the file: [chars]. Error: [chars]","The system is unable to write to the watchdog file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LOG","3","WD_TOTAL_INVALID","Total bytes of watchdog data read from the raw device is invlid: [dec].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.Error Message    %LRADSIM-3-AUTHREQFAIL: Unable to send authenticate message. Explanation    The system has failed to encapsulate the header in the authentication message.","This is a debug message only. No action is required."
"LRADSIM","3","INTMACFAIL","Unable to retrieve the interface MAC address.","The system is trying to retrieve the MAC address of an unplugged interface or the interface index exceeds the maximum supported interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LRADSIM","3","INVDADDR","Invalid destination address provided.","The system is trying to use an invalid IP address.","This is a debug message only. No action is required."
"LRADSIM","3","INVMS","Invalid mobile identifier provided.","The system is trying to use an invalid AP for a mobile station.","This is a debug message only. No action is required."
"LRADSIM","3","INVPARAM","Invalid parameters provided to sendDiscoveryRequest.","A bad destination address or a invalid port number was specified as a parameter to the sendDiscoveryRequest.","This is a debug message only. No action is required."
"LRADSIM","3","INVRCB","Invalid control block identifier provided.","The system is trying to find an invalid or nonexistent control block in the list.","No action is required."
"LRADSIM","3","LRADINITFAIL","Unable to create the control block.","The system is unable to get a lock for the control block or trying to corrupt the DB with an invalid control block.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LRADSIM","3","MSAUTHFAILED","Sending Auth Request for mobile [dec] on AP [dec]failed.","The system is trying to associate a mobile station on a nonexistent AP.","No action is required."
"LRADSIM","3","MSDISFAIL","Sending Discovery Request for mobile [dec] failed.","An invalid parameter has been passed to a discovery request.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LRADSIM","3","MSLISTFAIL","Failed to initialize the mobile station list.","The system is unable to create a lock for the mobile station list. This problem occurs when the system memory is full.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LRADSIM","3","NOINTFOUND","Unable to determine the number of interfaces in the system.","The system is unable to detect the number of active interface present in the system.","This is a debug message only. No action is required."
"LRADSIM","3","RCBMISMATCH","No active control block found for the ap Id [dec] Auth req can not besent for mobile Id [dec]","No active block has been found control block found for the AP and an Auth req cannot be sent for the mobile station.","No action is required."
"LRADSIM","3","SYSMEMFULL","Out of System buffers.","The system memory is full.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","AAA_ERR","Could not send AP authorization request","Due to an error in the internal state of the AP, the AP authorization request could not be sent. The AP might not be able to join the controller.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","AAA_ERR2","Invalid AAA state ('[chars]') for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The AP could not join the controller due to an internal error.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","ADD_OSSID_ERR","Unable to add [chars] SSID to override table for AP [chars]","Due to an internal error, override SSID information was not added into the database. The override SSID functionality might not work as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","AKITA_ERR","AP ([hex]:[hex]:[hex]:[hex]:[hex]:[hex]) is not supported","This version of the controller software does not support the AP.","Obtain the right version of the software that supports the AP if you want this AP in the network."
"LWAPP","3","APEVTLOGDNLDERR","Failed to download event log from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]. [chars]","The controller was unable to download the event log from the specified remote AP. The exact reason of the failure is also in the message.","Identify the reason for the failure from the message."
"LWAPP","1","AP_CONTAINED","AP [chars] is being contained on slot [dec]","The specified AP has been detected as a rogue and is being contained.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","AP_DB_CREATE_ERR","Unable to create an entry for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] in the database - [chars]","Could not add the AP into an entry in the internal database.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","AP_DB_DELETE_ERR1","Could not delete AP entry , invalid ID (x[hex])","Deleting the AP from the internal database has failed because the entry for the AP could not be found. It is possible that the AP has been removed from the controller.","Use the show ap summary command to determine if the AP is still joined to the controller. If it is not, ignore the message. If it is still joined, restart the AP to ensure that it has the latest configuration and contact technical assistance if the problem recurs."
"LWAPP","3","AP_DB_DELETE_ERR2","Unable to remove AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] [chars]","Due to an internal error, deleting the AP entry from the network processor has failed. If the AP attempts to join this controller, it might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","AP_DB_ERR1","Unable to find AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] entry in the database, could not process [chars]","The operation being performed for the AP has failed because the internal entry for the AP was not found. It is possible that the AP has been removed from the controller.","Use the show ap summary command to determine if the AP is still joined to the controller. If it is not, ignore the message. If it is still joined, restart the AP to ensure that it has the latest configuration and contact technical assistance if the problem recurs."
"LWAPP","3","AP_DB_ERR2","Unable to find AP (id [int]) in the database, [chars]","The operation being performed for the AP failed because the internal entry for the AP was not found. It is possible that the AP has been removed from the controller.","Use the show ap summary command to determine if the AP is still joined to the controller. If it is not, the message might be ignored. If it is still joined, restart the AP to ensure that it has the latest configuration and contact technical assistance if the problem recurs."
"LWAPP","3","AP_DB_FULL","Could not allocate an entry for the AP, database is full","The internal database for the AP is full, so an entry for the AP could not be added. The AP will not be able to join the controller.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","AP_DBG","Could not execute debug command, command is too long; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The remote debug command is not supported, if possible because it is too long.","No action is required."
"LWAPP","3","AP_DB_INVALID","AP information in the database is invalid","An invalid AP entry was found in the AP database. If the AP is still joined to the controller, it might not function properly.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","4","AP_JDBG_ADD_FAILED","Unable to create AP Join information entry for AP:[hex]:[hex]:[hex]:[hex]:[hex][hex], [chars]","The AP join information could not be added to the debugging database for the indicated reason. Debugging logs might be incomplete.","If the AP join information entry could not be created because the controller is already maintaining a maximum number of entries supported on the particular controller platform, ignore the message until the controller is rebooted next. This controller does not record any AP join information for any new APs deployed until the next reboot. For all other reasons specified, copy the message and contact technical assistance."
"LWAPP","4","AP_JDBG_INIT_FAILED","Unable to initialize AP join debugging infrastructure ([chars])","This AP join debugging infrastructure could not be initialized for the specified number of APs to be supported. The exact reason for the failure is specified in the message. The ability to debug AP join issues is limited.","No action is required."
"LWAPP","4","AP_JDBG_INVALID_DATA","Invalid AP join debugging data detected ([chars])","An internal error has occurred when initializing AP join information for debugging. The ability to debug AP join issues is limited.","No action is required."
"LWAPP","3","AP_LOCK_ERR","Could not obtain exclusive access to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] in the database","Access to an internal AP database has failed. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","4","AP_LOG_HOST_CFG_ERR","Unable to set system logging host configuration for AP:[hex]:[hex]:[hex]:[hex]:[hex][hex]","The controller could not configure system logging configuration for an AP. The AP might not longer be joined to a controller.","No action is required."
"LWAPP","6","AP_MODEL","[int] APs supported on platform ([chars])","Informational message that logs how the number of supported APs is being determined.","No action is required."
"LWAPP","2","AP_MODEL_ERR","Could not determine the # of APs supported from the model string ([chars])","The system is unable to find the number of APs supported from the machine model string. The system might become unstable.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","6","AP_NOT_CONTAINED","AP [chars] is not being contained on slot [dec]","The specified APis not a rogue, so it is not being contained.","No action is required."
"LWAPP","3","AP_POWER_ERR","AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] is unable to verify sufficient in-line power, radio slot [dec] is disabled","The AP power is not within requirements, so the radio slot has been disabled.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","6","AP_POWER_OK","AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] has verified sufficient in-line power, radio slot [dec] re-enabled","The AP power is within requirements, so the radio slot has been enabled.","No action is required."
"LWAPP","3","AP_REG_ERR","Could not register for AP state notification, maximum limit reached","An internal table that is used to pass state change notifications between processes is full. Configuration and state change information will not be handled properly and APs might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","AP_TYPE_ERR","AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] is not an H-REAP AP, could not process RADIUS configuration payload","The RADIUS configuration is only permitted for an H-REAP AP.","Check whether the AP is an H-REAP AP. If not, try to configure the AP in H-REAP mode if possible to enable RADIUS configuration."
"LWAPP","3","ARP_ERR","Could not resolve ARP of sniffer server IP address ([chars]), disabling sniffing on AP [chars], slot [dec]","The ARP resolution for the sniffer server has failed and has been disabled.","Check the network configuration and also the configuration of the server IP address on the controller. Ensure that the server is reachable."
"LWAPP","3","BAND_ERR","Invalid band parameter for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The traffic stream metrics status could not be sent to the specified AP due to an internal error. Traffic stream metrics might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","1","BIG_NAV","Big Nav attack detected on AP [chars], slot [dec], channel [dec], (errors [dec])","A NAV attack has been detected on the specified AP.","Check for a NAV has been attack in the network."
"LWAPP","3","BUILD_STR_ERR","[chars]","Due to an internal error, the software version information of the controller could not be obtained. The AP might not be able to join the controller.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","CCX_LINKTEST_ERR","Received unexpected CCX Linktest report message from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is dropping the unexpected CCX Linktest report message from the AP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","CCX_RM_ERR","Received an invalid CCX resource management subtype payload (radio management state [dec], slot identifier [dec])","The radio resource management message was not processed due to an invalid parameter. The CCX radio resource management might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","CERT_ERR1","Error verifying AP certificate, [chars]","Due to an internal error while processing the AP certificate. A join request has been dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","CERT_ERR2","Unable to retrieve controller's certificate for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An internal error occurred while obtaining the controller's certificate.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","CERT_ERR4","Unable to read the controller MAC address from the certificate","An internal error occurred while reading the MAC address of the controller from the certificate.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","CFG_ERR","Could not save LWAPP configuration in file [chars]","An error occurred when copying an LWAPP config file to persistent storage. Some of the LWAPP configuration might be lost and the system might not behave as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","CHKSUM_ERR","Invalid checksum in data transfer payload from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] (opcode [dec])","Due to an error in the checksum, the message from the AP has been dropped. The requested information from the AP could not be obtained.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","6","CONSOLE_LOGIN","Console login success on AP [chars]","A login attempt on the AP's console was successful.","No action is required."
"LWAPP","3","CONSOLE_LOGIN_ERR1","Console login failure on AP [chars]","A login attempt on the AP's console was unsuccessful.","Someone tried to log into the AP's console but authentication failed. If this message is seen multiple times check if someone is attempting to forcibly log into the AP's console."
"LWAPP","3","CONSOLE_LOGIN_ERR2","Unknown AP console login alarm from the AP [chars]","The AP has sent a console login alarm that the controller could not understand.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","COUNT_ERR1","AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] marked as [chars] but internal counter is zero","Due to an error, information about the type of AP is corrupted. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","COUNT_ERR2","AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] type count flag is not set","Due to an error, information about the type of AP has been corrupted. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","COUNT_ERR3","Mismatch in the internal count (used entries [dec], normal [dec], mesh [dec])","Due to an error, information about the type of the AP has been corrupted. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","COUNT_ERR4","AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] marked as normal but internal counter does not reflect this","Due to an error, information about the type of AP has been corrupted. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","CRYPTO_ERR1","Unable to encrypt crypto payload with public key for message to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An internal error occurred while encrypting a message to the AP. If the AP is already connected to the controller, it might be disconnected. If not, it might not be able to join the controller.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","CRYPTO_ERR2","Unable to encrypt crypto payload with private key for message to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An internal error occurred while encrypting a message to the AP. If the AP is already connected to the controller, it might be disconnected. If not, it might not be able to join the controller.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","DECODE_ERR","Error decoding [chars] from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The LWAPP message sent by the AP was not understood by the controller, so the message has been dropped. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","DECRYPT_ERR","Unable to decrypt [chars]; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Decryption of the LWAPP message has failed. The message has been dropped and the AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","DECRYPT_ERR1","Invalid session identifier ([dec]) - unable to decrypt packet; AP:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Due to an internal error, decryption of the LWAPP message on the controller has failed and the message has been dropped. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","DECRYPT_ERR2","Error decrypting public key in key update response from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Rekeying could fail because decrypting with a public key has failed. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","DECRYPT_ERR3","Private key decryption failed in key update response from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Rekeying could fail because decrypting with a private key has failed. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","DECRYPT_ERR5","Error decrypting packet (using old key) from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] (session identifier [hex])","Due to an internal error, the LWAPP packet could not be decrypted. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","DECRYPT_ERR8","Authentication of packet from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] failed, packet will be dropped","The LWAPP message from the AP has been dropped because of an authentication failure that led to an error in decryption. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","DECRYPT_ERR9","Unable to decrypt packet from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] with the private key","Due to an internal error, decrypting the LWAPP message with a private key has failed. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","DISC_AP_MGR_CAP","Ignoring discovery request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - no AP manager found with spare capacity","No AP manager was found with the capacity to handle another AP, so the discovery request from an AP was not accepted. The AP will continue to search for an available controller.","Verify the AP manager interface configuration. If the configuration is correct, the maximum number of supported APs has probably been reached."
"LWAPP","3","DISC_AP_MGR_ERR1","Unable to process primary discovery request from AP on interface ([int]), VLAN ([int]), could not get AP manager [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","A discovery response could not be sent to an AP because the controller was not able to obtain the IP address of the AP manager interface.","Correct the AP manager interface configuration."
"LWAPP","3","DISC_AP_MGR_ERR2","Unable to process primary discovery request from AP, AP manager IP address is invalid [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","A discovery response could not be sent to an AP because the controller was not able to obtain the IP address of the AP manager interface.","Correct the AP manager interface configuration."
"LWAPP","3","DISC_BCAST_ERR","Ignoring a discovery request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] via broadcast AP (IP = [dec].[dec].[dec].[dec]) is not in the same subnet as the controller","The controller ignored a broadcast discovery request from an AP because the AP is not on the same subnet as the controller.","No action is required."
"LWAPP","3","DISC_INTF_ERR1","Ignoring discovery request received on non-management interface ([int]) in L3 LWAPP mode","A discovery request from an AP was ignored because it was received on an invalid interface. The network configuration might be invalid.","Check the network configuration to ensure that packets from the AP are correctly routed."
"LWAPP","3","DISC_INTF_ERR2","Ignoring discovery request received on a wrong VLAN ([dec]) on interface ([int]) in L3 LWAPP mode","A discovery request from an AP was ignored because it was received on an invalid interface. Network configuration might be invalid.","Check the network configuration to ensure that packets from the AP are correctly routed."
"LWAPP","3","DISC_INTF_STATE_ERR","Unable to get [chars] state of interface '[chars]' (port [int]), not returning interface in discovery response","An internal error has occurred when obtaining the administrative state of the interface, so this was not sent in the discovery response. The AP will not be able to send a join request to that interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","0","DISC_LEN_ERR1","Invalid discovery request received from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - message length ([int]) is invalid","An incorrectly formatted discovery request was received from an AP and was ignored. The AP might not be able to join a controller.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","0","DISC_LEN_ERR2","Invalid primary discovery request received from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - message length ([int]) is invalid","An incorrectly formatted primary discovery request was received from an AP and was ignored. The AP might not be able to join a controller.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","DISC_MAX_AP1","Dropping discovery request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - limit for maximum APs supported [dec] reached","The system's maximum limit on the number of supported APs has been reached, so this AP will not be serviced.","No action is required."
"LWAPP","3","DISC_MAX_AP2","Dropping primary discovery request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - maximum APs joined [dec]/[dec]","The system's maximum limit on the number of supported APs has been reached, so this AP will not be serviced.","No action is required."
"LWAPP","3","DISC_MAX_DOWNLOAD","Ignoring discovery request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - maximum number of downloads ([int]) exceeded","A discovery request from an AP was rejected because the maximum number of concurrent downloads are already in progress. The AP might successfully join the controller on a later attempt.","No action is required."
"LWAPP","3","DISC_MAX_JOIN","Rejecting discovery request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - maximum AP joins ([int]) exceeded","A discovery request from an AP was rejected because the maximum number of concurrent joins are already in progress. The AP might successfully join the controller on a later attempt.","No action is required."
"LWAPP","3","DISC_OTAP_ERR","Ignoring OTAP discovery request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex], OTAP is disabled","The controller has received a discovery request from an AP that has learned the controller's address over the air, but Over The Air Provisioning (OTAP) is disabled on the controller.","Enable OTAP on the controller if desired; otherwise ignore this message."
"LWAPP","6","DISC_RESPONSE_SENT","Discovery Response sent successfully to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","A discovery response has been sent succesfully to the AP.","No action is required."
"LWAPP","4","DISC_TIME_ERR","Unable to retrieve time information while processing discovery request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Due to an internal error, the time at which the AP discovery request was received was not recorded. The AP might join the controller and function normally but monitoring of the AP's presence or absence might not work as expected.","No action is required."
"LWAPP","3","DISC_TYPE_ERR","Ignoring LWAPP packet from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - LWAPP packet is not a discovery or a join request (type = [dec]) and session ID is zero","An invalid LWAPP message was received from an AP and was ignored. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","DISC_VLAN_ERR","Received a discovery request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] on an unsupported VLAN ([int]), dropping the request","A discovery request was received on a port on which no interface was created.","Check the network configuration to ensure that packets from the AP are correctly routed."
"LWAPP","3","DISK_ERR","Not enough disk space to store crash file from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An internal error has occurred while attempting to store crash information from the AP to persistent storage.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","DSCP_ERR","Could not get configured DSCP map for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Due to an internal error in obtaining DSCP information for the specified AP, enterprise to enterprise DSCP functionality might not work as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","DUP_AP_IP","Duplicate IP address detected for AP [chars], IP address of AP  [chars], this is a duplicate of IP on another machine (MAC address [hex]:[hex]:[hex]:[hex]:[hex]:[hex])","A duplicate IP address has been detected for the specified AP.","Check the DHCP configuration and also change the IP address of the AP if it was configured statically."
"LWAPP","3","DUP_ERR","Received a duplicate [chars] from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","A duplicate request for a key update has been received from the AP. It is possible that the link between the AP and the controller is slow.","No action is required."
"LWAPP","3","DUP_IP","Adding client [hex]:[hex]:[hex]:[hex]:[hex]:[hex] to exclusion list due to IP Address conflict with AP '[chars]'","The AP and client have the same IP address. The Client was black listed.","Check the DHCP configuration and also change the IP address of the AP if it was configured statically."
"LWAPP","3","ECHO_ERR","Did not receive heartbeat reply; AP: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Controller did not get a response for the AP heartbeat message. There might be connectivity issues between the AP and the controller.","Check if the AP has rebooted, if it has been removed from the network, or if there are connectivity issues between the AP and the controller."
"LWAPP","3","ENCRYPT_ERR","Encryption of [chars] failed; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system could not transmit the LWAPP message so it could not be encrypted. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","ENCRYPT_ERR2","Unable to encrypt payload to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] with public key","Due to an internal error, encryption of the crypto payload with the public key has failed. This problem could lead to failures in rekeying and sending the join response.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","ENCRYPT_ERR3","Unable to encrypt payload to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] with the private key","Due to an internal error, encryption of the crypto payload with the private key failed. This could lead to failures in rekeying and also sending the join response.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","FILE_ERR","Unable to open [chars] file for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An internal error has occurred while attempting to store crash information from the AP to persistent storage. The AP crash information might be lost.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","FILE_ERR1","Unable to obtain LWAPP parameters, error opening file [chars]","An internal error occurred when retrieving LWAPP information from persistent storage. The system might become unstable.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","FILE_ERR3","[chars] [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Due to an internal error, an invalid file name was received and the controller could not send a message to the AP for obtaining the specified information.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","FILE_ERR4","Internal file error while processing image data payload message from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Due to an internal error, the AP's image information could not be obtained. A firmware download to the AP might fail.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","FILE_ERR5","File could not be opened to store [chars] information from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Due to an internal error, data from the AP could not be stored in persistent memory. Some information related to the AP might be lost.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","FILE_ERR6","Unable to write [chars] information from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] into local file","Due to an internal error, data from the AP could not be stored in persistent memory. Some information related to the AP might be lost.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","HDR_ENCAP_ERR","Unable to encapsulate LWAPP header for [chars]; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system could not send the LWAPP packet due to an internal error in encapsulating the packet. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","HDR_ERR","Received LWAPP packet with unsupported bit field ([hex],[hex]) from [hex]:[hex]:[hex]:[hex]:[hex]:[hex] to [hex]:[hex]:[hex]:[hex]:[hex]:[hex], dropping the packet","An invalid LWAPP packet has been received and the packet has been dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","HDR_ERR2","LWAPP header translation failed, dropping the packet","An internal error occurred when processing an LWAPP control packet. The LWAPP header was not understood and the packet has been dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","HDR_ERR3","Failed parsing LWAPP","Due to an internal error, LWAPP header processing has failed. The packet has been dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","HDR_PARSE_ERR","LWAPP header parsing failed, dropping the packet","Processing of an LWAPP control packet from the AP has failed because the LWAPP header was not understood. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","HREAP_ERR","Received invalid H-REAP operation for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] while processing RADIUS configuration payload (flag [hex])","Due to an internal error, the RADIUS configuration could not be updated on the specified AP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","HREAP_ERR2","Received invalid RADIUS port number (AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]) while processing RADIUS configuration payload","Due to an invalid port number, the RADIUS configuration could not be updated on the specified AP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","IMAGE_DOWNLOAD_ERR","Refusing [chars] from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - controller image upgrade is in process","The specified request from the AP is ignored because the controller's software is being upgraded. Future attempts from the AP might succeed.","No action is required."
"LWAPP","3","IMAGE_DOWNLOAD_ERR2","Refusing image download request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - max downloads ([dec]) in progress","The system is ignoring the image download request from the AP because the maximum number of concurrent image download requests are in progress. This is a temporary condition; future attempts by the AP might succeed.","No action is required."
"LWAPP","3","IMAGE_DOWNLOAD_ERR3","Refusing image download request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - unable to open image file [chars]","Due to an internal error, the image for the AP requesting image download could not be obtained. The AP image download will fail.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","IMAGE_DOWNLOAD_ERR4","Refusing image download request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - unable to open MD5 file [chars]","Due to an internal error, the image for the AP requesting image download could not be obtained. The AP image download will fail.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","INDEX_ERR","Invalid index ([int]) while [chars] per port AP load information","An internal error occurred when processing AP load information. Some AP management functions might not work as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","INVALID_AID","Received invalid association identifier ([int]) for station [hex]:[hex]:[hex]:[hex]:[hex]:[hex] on a REAP AP","An internal error caused an invalid association ID to be received from an AP for the indicated client. The client might experience communication problems.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","INVALID_AID2","Association identifier [int] for client [hex]:[hex]:[hex]:[hex]:[hex]:[hex] is already in use by [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An internal error caused an invalid association ID to be received from an AP for the indicated client. The client might experience communication problems.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","INVALID_DELIM","Invalid delimiter ([dec]) in AP authorization list","Due to an invalid delimiter specified, the AP could not be authenticated, so a join response could not be sent.","Check the delimiter configured on the controller."
"LWAPP","3","INVALID_IP","Invalid sniffer server IP address ([hex]), disabling sniffing on AP [chars], slot  [dec]","Sniffing has been disabled because the IP address of the server was invalid.","Check the configuration of the sniffer server's IP address."
"LWAPP","3","INVALID_PARAMETER","Invalid [chars]; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The specified parameter was not understood by the controller, so the message was not processed. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","INVALID_PARAMETER1","[chars] ([dec]); AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The value of parameter specified was not understood by the controller, so the message was not processed. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","INVALID_PARAMETER2","[chars] ([dec]) - [chars]; AP: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The value of parameter specified was not understood by the controller, so the message was not processed. AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","INVALID_PARAMETER3","[chars] ([dec])","The value of parameter specified was not understood by the controller, so the message was not processed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","INVALID_PARAMETER4","[chars]","The value of parameter specified was not understood by the controller, the message was not processed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","INVALID_RADIO","Received an unsupported radio ([dec]), [chars]","Performing the specified operation on the radio for the AP has failed because the radio was not understood by the controller. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","INVALID_RADIO2","Received invalid radio type ([dec]) for AP [chars] on slot [dec] , could not verify power level for the AP","Due to an internal error, an invalid radio type has been received. The specified operation could not be performed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","INVALID_SESSIONID","Received invalid session identifier in [chars] from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] (expected [dec] and got [dec])","A mismatch has occurred on the session identifier in the message from the AP. The message has been dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","INVALID_SLOT","Invalid slot identifier ([dec]) - [chars]; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The slot identifier sent by the AP was not understood by the controller, so the specified message was not processed. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","INVALID_SLOT2","Invalid slot identifier ([dec]) -  [chars] ([dec]): AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The slot identifier for the AP was not understood by the controller, so the specified message was not processed. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","INVALID_WLAN","Invalid WLAN identifier ([int]) obtained while building MFP config payload","An internal error occurred when attempting to retrieve the WLAN configuration. The MFP might not be operational or might not work as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","IP_ERR","Could not plumb AP's ([hex]:[hex]:[hex]:[hex]:[hex]:[hex]) IP address ([dec].[dec].[dec].[dec]), next hop MAC ([hex]:[hex]:[hex]:[hex]:[hex]:[hex]) and VLAN ([dec]) to fast path","Due to an internal error, the IP address of the AP could not be configured in the network processor. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","IP_PROT_ERR","IP protocol ([dec]) in the received packet - from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] is not UDP, LWAPP packets are only UDP, dropping the packet","An invalid packet received from the AP has been dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","JOIN_AP_MGR_ERR1","Could not get IP address of AP manager interface, dropping join request from AP [hex]:[hex]:[hex]:[hex]:[hex][hex]","A join response could not be sent to an AP because the controller was not able to obtain the IP address of the AP manager interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","JOIN_AP_MGR_ERR2","Received a join request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] for someone else ([dec].[dec].[dec].[dec]), dropping the packet","A join request with a destination IP address that does not match any AP manager's IP address, has been dropped.","Check the network configuration and also the configuration of the AP manager on the controller and ensure that the packets from the AP are routed correctly."
"LWAPP","3","JOIN_DB_ERR","Could not allocate an entry in the database for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - dropping the join request (# of APs joined = [dec])","An internal error has resulted in a failure while creating an entry for the AP in the database.","Check if the number of APs that are currently joined to this controller is also the maximum limit."
"LWAPP","3","JOIN_HIGH_PRIORITY_AP_ERR","Disconnecting AP [chars] since a higher priority AP with priority [dec] joined Max number of APs allowed [dec]","When an AP join priority is enabled and the controller has the maximum numbers of APs connected, a low priority AP is disconnected when a high priority AP joins.","No action is required."
"LWAPP","3","JOIN_INTF_ERR1","Received a join request on an invalid interface ([dec]) from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex], dropping the packet","The IP address of the interface on which the join request was received could not be obtained.","Check the interface configuration on the controller."
"LWAPP","3","JOIN_INVALID_ERR1","Invalid [chars] in LWAPP join request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The AP sent a join request that was invalid because it lacked certain payloads. Such requests are dropped at the controller. AP might not be able to join the controller.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","JOIN_INVALID_ERR2","Invalid [chars] ([dec]) in join request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The AP sent a join request that was invalid because lengths of certain payloads within the request were incorrect. Such requests are dropped at the controller. The AP might not be able to join the controller.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","JOIN_INVALID_SLOT","Join request from AP ([hex]:[hex]:[hex]:[hex]:[hex]:[hex]) has invalid number of slots ([dec], instead of [dec]) , dropping the packet","The number of radios that the AP supports is invalid as per what is sent in the join request. The join request has been dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","JOIN_MAC_ERR","Received a join request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] destined for [hex]:[hex]:[hex]:[hex]:[hex]:[hex] on port [int]/VLAN [int] - invalid destination MAC address, dropping the packet","The MAC address in the join request was invalid, so this request has been dropped by the controller.","Check the network configuration and ensure that the packets from the AP are routed correctly."
"LWAPP","6","JOIN_MASTER","Controller is also configured as the master, AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The controller is also configured as the master controller. Change the configuration of the controller so that it is not the master.","No action is required."
"LWAPP","3","JOIN_MAX_AP_ERR","Received a join request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - reached limit for maximum APs [dec]/[dec], dropping the packet","Each controller has a limit on the number of APs that can be supported. This limit has been reached, so the AP was not serviced.","No action is required."
"LWAPP","3","JOIN_MAX_AP_INTF_ERR","Received a join request from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex], reached limit for maximum number of APs ([dec]) on interface [dec], dropping the packet","Each interface has a limit on the number of APs that can be supported. This limit has been reached for the interface. The join request has been dropped. If the AP sends join request to another interface, a join response might be sent.","No action is required."
"LWAPP","3","JOIN_MAX_DOWNLOAD_ERR","Reached max limit ([dec]) on the number of APs that can download image, dropping join request","The controller could not respond to the join request from the AP because the current limit on the maximum number of concurrent image downloads possible has been reached. This problem might be a transient condition. If AP continues to send join requests, a join response would be sent.","No action is required."
"LWAPP","3","JOIN_MAX_JOIN_ERR","Reached max limit ([dec]) on the number of APs that can join the controller, dropping join request","The controller could not respond to the join request from the AP because the current limit on the maximum number of concurrent join requests that can be processed has been reached. This problem might be a transient condition. If AP continues to send join requests, a join response would be sent.","No action is required."
"LWAPP","3","JOIN_UNSUPP_AP","Received a join request from an unsupported AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] [chars] (model [chars]), dropping the packet","This version of the controller software does not support the AP model.","Check the documentation regarding the software version on supported AP models. Remove this AP from the network or move to a version of software that supports the AP."
"LWAPP","3","KEY_ERR1","Unable to obtain public key from the certificate of AP[hex]:[hex]:[hex]:[hex]:[hex]:[hex], [chars]","Due to an internal error, a public key for the AP could not be obtained, and a join response could not be sent to the AP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","KEY_ERR2","Invalid public key type in certificate for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Due to an invalid public key type for the AP, a join response could not be sent to the AP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","KEY_ERR3","Unable to free public key for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Due to an internal error, public key information for this AP was not removed from the database while deleting the AP. There might be problems if this AP attempts to join the controller again.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","4","L3_PACK_ERR","Received an L3 LWAPP packet in L2 LWAPP mode, dropping the packet","The controller is configured in L3 LWAPP mode so packets received for the L2 LWAPP mode are being dropped.","No action is required."
"LWAPP","6","LAG_TRAN","Link aggregation configuration is in transition","The controller's link aggregation configuration has been changed but the changes do not take effect until the next system reboot.","No action is required."
"LWAPP","2","LIST_ERR1","List is corrupted - (head [address], tail [address], count [int])","An internal error caused the list of APs maintained by the controller to become corrupted. The system might become unstable.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","2","LIST_ERR2","List is corrupted - (head [address], tail [address], count [int], p [address], p->next[address], p->prev [address])","An internal error caused the list of APs maintained by the controller to become corrupted. The system might become unstable.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","2","LIST_ERR3","List is corrupted - (head [address], tail [address], count [int], actual [int])","An internal error caused the list of APs maintained by the controller to become corrupted. The system might become unstable.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","2","LIST_ERR4","List is corrupted - (head [address], tail [address], p [address], p->next [address], p->tail[address])","An internal error caused the list of APs maintained by the controller to become corrupted. The system might become unstable.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","2","LIST_ERR5","Skipping duplicate insertion - ( head [address], tail [address], count [int],entry [address])","An internal error occurred when attempting to add an entry to the AP database. The system might become unstable.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","2","LIST_ERR6","Entry [address] not in the list - ([address], head [address], tail [address])","An internal error occurred when attempting to remove an entry from the AP database. The system might become unstable.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","LIST_ERR7","Unable to delete AP entry, index ([dec]) is greater than maximum allowed","The system is unable to delete an entry in the AP table due to an internal error.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","LIST_ERR8","Unable to delete AP entry, entry not allocated","The system is unable to a delete entry in the AP table; the entry has not been allocated.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MAX_AID","Reached max limit ([dec]) on the association ID for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","A maximum number of clients that can be supported on the AP has been reached, and association identifiers have been exhausted. A new client cannot be supported on the AP.","No action is required."
"LWAPP","3","MAX_AID2","Reached max limit on the association ID for AP (max association ID [dec])","A maximum number of clients that can be supported on the AP has been reached, and association identifiers have been exhausted. A new client cannot be supported on the AP.","No action is required."
"LWAPP","3","MBUF_ERR","No more system buffers, could not receive LWAPP packet","The system is out of system buffers.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MCAST_APP_ERR","Failed to obtain multicast appliance configuration for interface [int], using default index ([int])","Due to an internal error, the multicast appliance configuration could not be obtained. Multicast might not operate as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MEM_ERR","Unable to allocate memory [chars]; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is running on low memory.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MEM_ERR2","Unable to allocate memory for LWAPP message","System is running low on memory.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MEM_ERR3","Unable to allocate memory [chars]","The system is running low on memory.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MEM_ERR4","Unable to allocate memory [chars] (AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex])","The system is running low on memory.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MFP_ERR","MFP report count ([int]) is too big in message; AP: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Could not process an MFP report because the message is too large. The MFP might not work as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MFP_ERR1","Ignoring MFP message [chars] with invalid slot ([int]) in message from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The MFP message from the AP had an invalid slot; the MFP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MIC_COUNTER","Received MIC countermeasure, WLAN [dec], slot [dec] AP [chars] client [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","MIC errors have occurred on the specified AP. Clients might not be able to connect on the specified WLAN.","Check for attacks in the network."
"LWAPP","3","MIGRATE_ERR","Failed to migrate to regulatory domain requested for AP (name [chars], model [chars], MAC [hex]:[hex]:[hex]:[hex]:[hex]:[hex] ,serial number [chars])","An attempt to migrate to a new regulatory domain has failed on the AP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MIRROR_ERR","Setting mirroring mode failed","Due to an internal error, the configuration of the mirroring mode has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","0","MSG_QUEUE_ERR","LWAPP message queue has not been created","The LWAPP subsystem has not been initialized. APs might not be able to join the controller.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSG_RCV","Could not receive message from LWAPP queue","An internal error has occurred while reading an LWAPP message. The system will attempt to process other LWAPP messages.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSG_SEND_ERR","Unable to send [chars] message to LWAPP; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The LWAPP process might be busy. If this condition persists, it could lead to loss of LWAPP packets, dropping of AP connections, and the AP not getting configuration changes from the controller.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSG_SEND_ERR2","Unable to send [chars] message to LWAPP","The LWAPP process might be busy. If this condition persists, it could lead to loss of LWAPP packets, dropping of AP connections and AP not getting configuration changes from the controller.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","0","MSGTAG071","MESH Child [hex]:[hex]:[hex]:[hex]:[hex]:[hex] has changed route or disconnected from Parent ([chars]) [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","The MESH Child [hex]:[hex]:[hex]:[hex]:[hex]:[hex] has changed a route or disconnected from the parent ([chars]) [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","0","MSGTAG072","Parent changed excessively. AP [chars] changed parent macAddr =[hex]:[hex]:[hex]:[hex]:[hex]:[hex].","A parent changed a route excessively. The AP [chars] has changed the parent MAC address=[hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG073","Unknown Mesh Neighbor Event from the AP [chars].","An unknown mesh neighbor event has occurred from the AP [chars].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG162","Did not specify the MAC address for Mesh Neigh Request [dec]config","The system did not specify the MAC address for the mesh neighbor request [dec] the configuration.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG221","[chars]() : Could not generate nonce","[chars]() : The System Could not generate a nonce.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG257","1: msgLen [dec]","1: msgLen [dec]","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG258","2: len [dec] Type : [dec] = [dec]","2: len [dec] Type : [dec] = [dec]","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG259","1: msgLen [dec]","1: msgLen [dec]","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG260","2: len [dec] Type : [dec] = [dec]","2: len [dec] Type : [dec] = [dec]","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG261","1: msgLen [dec]","1: msgLen [dec]","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG262","2: len [dec] Type : [dec] = [dec]","2: len [dec] Type : [dec] = [dec]","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG263","1: msgLen [dec]","1: msgLen [dec]","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG264","2: len [dec] Type : [dec] = [dec]","2: len [dec] Type : [dec] = [dec]","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG265","1: msgLen [dec]","1: msgLen [dec]","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG266","2: len [dec] of [dec] Type : [dec] = [dec]","2: len [dec] of [dec] Type : [dec] = [dec]","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG267","Unable to parse LWAPP headers from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is unable to parse LWAPP headers from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG268","spamMeshSecbhStatsPayloadDecode: len received:[dec] expected=[dec] numQueues=[dec]\n","spamMeshSecbhStatsPayloadDecode: len received:[dec] expected=[dec] numQueues=[dec]\n","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG269","spamMeshSecbhStatsPayloadDecode: unexpected slotId=[dec]\n","spamMeshSecbhStatsPayloadDecode: unexpected slotId=[dec]\n","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG270","1: msgLen [dec]","1: msgLen [dec]","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG271","MESH_NODE_UPDATE_PAYLOAD: len received:[dec] expected=[dec]","MESH_NODE_UPDATE_PAYLOAD: len received:[dec] expected=[dec]","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG272","spamDecodeMeshNodeUpdate: invalid payload type=[dec]","spamDecodeMeshNodeUpdate: invalid payload type=[dec]","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG273","1: msgLen [dec]","1: msgLen [dec]","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG274","2: len [dec] of [dec] Type : [dec] = [dec]","2: len [dec] of [dec] Type : [dec] = [dec]","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG275","1: msgLen [dec]","1: msgLen [dec]","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG276","2: len [dec] of [dec] Type : [dec] = [dec]","2: len [dec] of [dec] Type : [dec] = [dec]","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG277","spamSendLinktestRequest: refusing to send request when previous request is pending ltid [dec]","spamSendLinktestRequest: refusing to send a request when a previous request is pending ltid [dec].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG278","spamDecodeLinktestResponse invalid msgLen [dec]","spamDecodeLinktestResponse invalid msgLen [dec]","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG279","spamDecodeLinktestResponse LINKTEST_CFG_PAYLOAD([dec]): invalid payload len [dec] != [dec] (msglen [dec])","spamDecodeLinktestResponse LINKTEST_CFG_PAYLOAD([dec]): invalid payload len [dec] != [dec] (msglen [dec])","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG280","spamDecodeLinktestResponse LINKTEST_RESULTS_PAYLOAD([dec]): invalid payload len [dec] != [dec]","spamDecodeLinktestResponse LINKTEST_RESULTS_PAYLOAD([dec]): invalid payload len [dec] != [dec]","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG281","Out of range linktest ID ([dec]) specified","An out of range linktest ID ([dec]) has specified.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG282","Attempt to obtain results from free linktest ID ([dec])","An attempt has been made to obtain results from the free linktest ID ([dec]).","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG283","invalid linktestId [dec]","The system has detected an invalid linktestId [dec].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG284","invalid linktestId [dec]","The system has detected an invalid linktestId [dec].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG285","invalid linktestId [dec]","The system has detected an nvalid linktestId [dec].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG286","apfApLinktestFree: attempt to free linktestId=[dec] which is already free","apfApLinktestFree: an attempt has been to free a linktestId=[dec] that is already free.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG287","FREEING LinkTest [dec]: (status [dec]) [hex]:[hex]:[hex]:[hex]:[hex]:[hex] -> [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","FREEING LinkTest [dec]: (status [dec]) [hex]:[hex]:[hex]:[hex]:[hex]:[hex] -> [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG288","aplinktest_test: apfApLinktest returned failure","aplinktest_test: apfApLinktest returned failure","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG289","aplinktest_test: apfApLinktest returned success, ltid [dec]","aplinktest_test: apfApLinktest returned success, ltid [dec]","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG290","aplinktest_test: apfApLinktest returned failure","aplinktest_test: apfApLinktest returned failure","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG291","aplinktest_test: apfApLinktest returned success, ltid [dec]","aplinktest_test: apfApLinktest returned success, ltid [dec]","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG292","[dec]: (status [dec]) [hex]:[hex]:[hex]:[hex]:[hex]:[hex] -> [hex]:[hex]:[hex]:[hex]:[hex]:[hex] [dec] [dec] [dec] [dec] [dec] [dec] [dec] [dec] [dec] [dec] [dec] [dec]","[dec]: (status [dec]) [hex]:[hex]:[hex]:[hex]:[hex]:[hex] -> [hex]:[hex]:[hex]:[hex]:[hex]:[hex] [dec] [dec] [dec] [dec] [dec] [dec] [dec] [dec] [dec] [dec] [dec] [dec]","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG293","[dec]: FREE","[dec]: FREE","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG535","AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] associated. Last AP rebooting was because RAP was using radio backhaul as uplink for 15 minutes.","The AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] has associated. The last AP reboot was because the RAP was using a radio backhaul as an uplink for 15 minutes.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG650","LWAPP Join Request Country Code invalid for Bridge AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An LWAPP join request country code is invalid for the Bridge AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG651","LWAPP Join Request Bridge Authentication failed for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An LWAPP join request bridge authentication has failed for the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG675","Mesh APs not supported in multi-country mode. Rejected AP: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Mesh APs are not supported in multi-country mode. Rejected AP: [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG702","Not creating SSID [chars] on Bridge AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] because wlan0 is not supported","This system is not creating an SSID [chars] on the Bridge AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] because WLAN0 is not supported.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG829","Unable to allocate buffer for mesh link para message to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is unable to allocate a buffer for mesh link para message to the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG830","Unable to allocate buffer for AP BH rate message to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is unable to allocate a buffer for the AP BH rate message to the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG831","Unable to allocate buffer for AP BH dev message to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is unable to allocate a buffer for the AP BH dev message to the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG832","Unable to allocate buffer for AP Bridge State message to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is unable to allocate a buffer for the AP bridge state message to the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG833","Unable to allocate buffer for AP Bridge Groupname message to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is unable to allocate a buffer for the AP bridge group name message to the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG834","Unable to allocate buffer for AP Public Safety message to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is unable to allocate a buffer for the AP public safety message to the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG881","Unable to allocate buffer for Mesh Neigh Request message to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is unable to allocate a buffer for the mesh neigh request message to the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG882","Unable to allocate buffer for Mesh Linktest Data Request message to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is unable to allocate a buffer for the mesh link test data request message to the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG883","Unable to allocate buffer for Mesh Path Request message to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is unable to allocate a buffer for the mesh path request message to the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG884","Unable to allocate buffer for Mesh Stats Request message to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is unable to allocate a buffer for th mesh stats request message to the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG885","Unable to parse LWAPP headers from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is unable to parse LWAPP headers from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG886","Received Mesh stats response from unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system has received a mesh stats response from an unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG887","Security processing of Mesh Stats Response failed from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Security processing of a mesh stats response failed from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG888","Processing of Mesh Stats Response failed from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Processing of a mesh stats response failed from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG889","Unable to allocate buffer for Mesh Security Stats Request message to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is unable to allocate a buffer for a mesh security stats request message to the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG890","Unable to parse LWAPP headers from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is unable to parse LWAPP headers from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG891","Received Mesh Security Stats response from unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system has received mesh security stats response from unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG892","Processing of Mesh Security Stats Response failed from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Processing of mesh security stats response failed from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG893","Unable to parse LWAPP headers from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is unable to parse LWAPP headers from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG894","Received Mesh Adj response from unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system has received a mesh adj response from an unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG895","Security processing of Mesh Adj Response failed from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Security processing of a mesh adj response has failed from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG896","Processing of Mesh Adj Response failed from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Processing of a mesh adj response has failed from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG897","Unable to parse LWAPP headers from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is unable to parse LWAPP headers from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG898","Received Mesh Neigh response from unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system has received a mesh neigh response from an unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG899","Security processing of Mesh Neigh Response failed from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Security processing of a mesh neigh response has failed from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG900","Processing of Mesh Neigh Response failed from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Processing of a mesh neigh response failed from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG901","Unable to allocate buffer for Mesh Linkrate Request message to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is unable to allocate a buffer for a mesh link rate request message to the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG902","Unable to parse LWAPP headers from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is unable to parse LWAPP headers from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG903","Received Mesh Linkrate response from unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system has received a mesh link rate response from an unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG904","Security processing of Mesh Linkrate Response failed from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Security processing of a mesh link rate response has failed from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG905","Processing of Mesh Linkrate Response failed from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Processing of a mesh link rate response has failed from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG906","Unable to parse LWAPP headers from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is unable to parse LWAPP headers from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG907","Received station stats update from unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system has received a station stats update from an unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG908","Unable to parse LWAPP headers from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is unable to parse LWAPP headers from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG909","Unable to parse LWAPP headers from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is unable to parse LWAPP headers from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG910","Received mesh node update from unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system has received a mesh node update from an unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG911","Processing of mesh node update failed from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Processing amesh node update failed from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG912","Unable to parse LWAPP headers from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is unable to parse LWAPP headers from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG913","Unable to parse LWAPP headers from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is unable to parse LWAPP headers from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG914","Received mesh env. update from unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system has received a mesh env. update from an unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG915","Processing of mesh env. update failed from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Processing of a mesh env. update has failed from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG916","Unable to parse LWAPP headers from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is unable to parse LWAPP headers from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG917","Failed to update CAC module with parent address: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system has failed to update the CAC module with the parent address: [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG918","Unable to parse LWAPP headers from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is unable to parse LWAPP headers from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG919","Received mesh neighs update from unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system has received a mesh neighs update from an unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG920","Processing of mesh neighs update failed from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Processing of a mesh neighs update has failed from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG921","Unable to allocate buffer for Linktest Request message to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is unable to allocate a buffer for a link test request message to the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG922","Unable to parse LWAPP headers from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is unable to parse LWAPP headers from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG923","spamDecodeLinktestResponse LINKTEST_CFG_PAYLOAD([dec]): linktest ID from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","spamDecodeLinktestResponse LINKTEST_CFG_PAYLOAD([dec]): linktest ID from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG924","spamDecodeLinktestResponse (ltid:[dec]) unexpected LINKTEST_CFG_PAYLOAD from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","spamDecodeLinktestResponse (ltid:[dec]) unexpected LINKTEST_CFG_PAYLOAD from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG925","spamDecodeLinktestResponse LINKTEST_RESULTS_PAYLOAD([dec]): invalid linktest ID([dec]) from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","spamDecodeLinktestResponse LINKTEST_RESULTS_PAYLOAD([dec]): invalid linktest ID([dec]) from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG926","spamDecodeLinktestResponse (ltid:[dec]) unexpected LINKTEST_RESULTS_PAYLOAD from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","spamDecodeLinktestResponse (ltid:[dec]) unexpected LINKTEST_RESULTS_PAYLOAD from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG927","spamDecodeLinktestResponse unrecognized payload [dec] from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","spamDecodeLinktestResponse unrecognized payload [dec] from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG928","Linktest requested for unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Link test requested for an unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG929","Linktest already running on AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Link test already running on the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG930","Linktest already running on AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Link test already running on the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG931","link test id is already in use: [dec]","Link test ID is already in use: [dec].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG932","Too many linktests running, cannot manage AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Too many link tests running; cannot manage the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG933","Unable to parse LWAPP headers from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is unable to parse LWAPP headers from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG934","Received linktest response from unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system has received a link test response from an unknown AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","MSGTAG935","Processing of linktest response failed from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Processing of a link test response has failed from the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","NPU_ERR","Invalid NPU index [int]","The system is indexing into the network processor's internal table with an invalid index.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","NPU_ERR2","All NPU indices have been used (max [dec])","The System could not create an entry for the AP in fast path because the internal database is full. The AP might not be able to join the controller.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","NPU_ERR3","Could not allocate NPU index for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Due to an internal error, the AP entry in the fast path could not be configured successfully. The AP might not be able to join the controller.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","NPU_ERR4","Failed to add NPU entry for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex], index: [int], switch IP: [int].[int].[int].[int], switch port: [int], interface num: [int], VLAN: [int] AP IP: [int].[int].[int].[int], AP Port: [int], next hop MAC: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Due to an internal error, the AP entry could not be added to the network processor. The AP might not behave as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","OFDM_ERR","Received invalid OFDM channel ([int]), unable to set the channel","An internal error occurred when attempting to configure a channel.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","OSSID_ERR","Override SSID [chars] does not exist on the controller","The system could not delete the specific override SSID from the controller's database The override SSID functionality might not work as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","PARSE_ERR","LWAPP header parsing failed for packet from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex], dropping the packet","An internal error has occurred when processing a LWAPP control packet. The LWAPP header was not understood, so the packet was dropped. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","PARSE_ERR2","LWAPP header parsing failed, dropping the packet","An internal error has occurred when processing a LWAPP control packet. The LWAPP header was not understood, so the packet was dropped. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","PARSE_ERR3","Unable to parse LWAPP headers for [chars]; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An internal error has occurred when processing a LWAPP control packet. The LWAPP header was not understood, so the packet was dropped. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","PAYLOAD_ERR","[chars] - AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Not all payloads expected in the LWAPP message are present. The controller is dropping LWAPP messages from the AP. The AP might not be able to join the controller.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","PAYLOAD_MISSING","[chars] -","Not all payloads expected in the LWAPP message are present.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","0","PDISC_LEN_ERR","Invalid primary discovery request received from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - message length ([int]) is invalid","An incorrectly formatted primary discovery request was received from an access point and was ignored.","No action is required."
"LWAPP","6","PORTMAP_ERR","Failed to obtain multicast port map for interface [int], using default index ([int])","The system could not get information on a multicast port using the information that is available for unicast. Multicast might not work as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","PROFILE_NAME_ERR","Could not find profile name for WLAN [dec] with SSID [chars]; AP: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The profile name for the WLAN could not be found in the database.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","PROFILE_NAME_ERR2","Could not find profile name for WLAN with SSID [chars]","The profile name for the WLAN could not be found in the database.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","RADIO_CRASH","Radio ([dec]) crashed and generated a core dump on AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An error has occurred on the radio for the specified AP. The AP might not function as expected.","Collect the radio crash information for the AP and contact technical assistance."
"LWAPP","2","RADIO_ERR","[chars] failure on radio slot [dec] on AP [chars]","The radio slot on the specified AP has failed. It will impact clients that are connected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","RADIO_ERR2","Unknown AP radio failed alarm ([dec]) from the AP [chars]","The AP has sent a radio failed alarm that the controller could not understand.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","2","RADIO_NOERR","AP [chars] recovered from [chars] failure on radio slot [dec]","The radio slot on the specified AP is not experiencing failures at this time.","No action is required."
"LWAPP","3","RADIUS_ERR","Could not send join reply, AP authorization failed; AP:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The join reply has not been sent to the AP because AP authentication failed.","Check the AP credentials on the RADIUS server, or the local MAC filtering table - if it was configured. Also check if RADIUS servers are configured and are reachable."
"LWAPP","3","RADIUS_PORT_ERR","Received invalid RADIUS port number for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The port number for RADIUS is incorrect. RADIUS configuration could not be configured on the AP.","Check the RADIUS configuration for the H-REAP APs configured on the controller."
"LWAPP","3","RADIUS_SECRET_ERR1","MAC filtering request dropped as shared secret for RADIUS was not found","The system is unable to find a RADIUS password, so the MAC filter authenticate request has been aborted. The AP might not be able to join the controller.","Check the RADIUS shared secret configured on the controller and the RADIUS server."
"LWAPP","3","RADIUS_SECRET_ERR2","Received invalid RADIUS shared secret; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The length of the shared secret is incorrect, so the RADIUS configuration could not be configured on the AP.","Check the RADIUS configuration for the H-REAP APs configured on the controller."
"LWAPP","3","RD_ERR","Regulatory domain of the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] does not match the country code ([chars])","A mismatch has occurred in the country code and regulatory domain configured on the AP and controller. The AP might not be able to join the controller.","Check if the correct (that intended to work with the AP) country code is configured on the controller"
"LWAPP","3","RD_ERR10","AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] is disabled - default country code is [chars]","Due to an error in the regulatory domain configured on the AP and the inability to associate a correct country code, the AP has been disabled. The AP will not be able to function as expected.","Check if the correct country code is configured on the controller"
"LWAPP","3","RD_ERR2","Regulatory domain for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]  is not updated for all slots. (Updated [dec] out of [dec] filled slots)","An error has occurred in the regulatory domain information for the slots on the AP. All of them do not have it configured. The AP might not be able to join the controller.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","RD_ERR3","Invalid regulatory domain ([hex]) sent by AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] (slot: [dec] [chars])","The regulatory domain configured on the AP slot was not understood. The AP might not be able to join the controller.","Check if the correct country code is configured on the controller."
"LWAPP","3","RD_ERR4","Invalid regulatory domain [chars] for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The regulatory domain configured on the AP was not understood. The AP might not be able to join the controller.","Check if the correct country code is configured on the controller"
"LWAPP","3","RD_ERR5","APs ([hex]:[hex]:[hex]:[hex]:[hex]:[hex] - slot [dec] [chars]) regulatory domain is not set, this is not allowed in country [chars]","Due to an error in the regulatory domain configured on the AP, the AP might not be able to join the controller.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","RD_ERR6","APs ([hex]:[hex]:[hex]:[hex]:[hex]:[hex]) regulatory domain ([chars]) is not supported in country ([chars]), slot [chars] ([dec]) supports [chars]","Due to an error in the regulatory domain configured on the AP, the AP might not be able to join the controller.","Check if the correct country code is configured on the controller"
"LWAPP","3","RD_ERR7","Invalid country code ([chars]) for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Due to an error in the regulatory domain configured on the AP, the AP might not be able to join the controller.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","RD_ERR8","Country code ([chars]) not configured for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Due to an error in the regulatory domain configured on the AP, the AP might not be able to join the controller.","Check if the correct country code is configured on the controller"
"LWAPP","3","RD_ERR9","APs [hex]:[hex]:[hex]:[hex]:[hex]:[hex] country code changed from ([chars]) to ([chars])","The country code associated with the regulatory domain configured on the AP was incorrect, so the country code has been changed. The AP might not function correctly in the region it is deployed.","The AP is functioning correctly with the changed country code, ignore this message. If the AP is not functioning correctly, contact technical assistance."
"LWAPP","3","REBOOT_ERR2","AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] joined to the controller currently experienced a reboot earlier - ([chars] [chars] [chars])","The AP was unable to service clients because as it experienced a reboot due to the reason specified in the message.","Obtain the AP crash files from the controller, and collect all the message logs. Also, if the AP experienced a reboot as a result of missing heartbeat from the controller, check the network for connectivity issues. If the AP experienced a reboot because a join response was not obtained, check connectivity issues to the AP manager interface if the controller is in L3 mode, and ensure that it is reachable. After collecting the above data, contact technical assistance if necessary."
"LWAPP","6","REBOOT_INFO1","Controller initiated reboot of AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] that has currently joined the controller - ([chars] [chars])","The last reboot for the specified AP was triggered by the controller due to configuration changes on the AP that required a reboot.","No action is required."
"LWAPP","3","RECV_FAIL","Could not process LWAPP packet","An internal error has occurred while processing the LWAPP packet. The packet was dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","REKEY_ERR","Did not receive an expected rekey message from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The AP might be disconnected because the rekeying message expected from the AP was not received.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","REPLAY_ERR","Received replay error on slot [dec], WLAN ID [dec], count [dec] from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The controller has received a replay error on the specified AP and WLAN.","Check if there is a replay attack in the network."
"LWAPP","3","ROGUE_ERR","Could not send rogue report for [hex]:[hex]:[hex]:[hex]:[hex]:[hex] from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Due to an internal error, rogue information could not be sent.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","RX_ERR","Received an unexpected LWAPP packet from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The controller had no pending messages for this AP, so the unexpected response received was dropped. It is possible that this message arrived late at the controller.","No action is required."
"LWAPP","3","RX_ERR3","Received LWAPP packet with invalid sequence number (got [dec]expected [dec]) - from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An LWAPP packet sequence mismatch has occurred, and the LWAPP packet was dropped. The AP might not function as expected.","No action is required."
"LWAPP","3","RX_ERR4","Received invalid add mobile action ([int]) from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] (read index = [int])","Adding a client to the AP has failed. The client might not be serviced as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","RX_ERR7","Received an invalid sequence number, [chars] ; AP: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The LWAPP sequencing has failed for this LWAPP message, and the message was dropped. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","RX_ERR8","Unable to receive [chars] from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Due to an internal error, the LWAPP message could not be processed by the controller. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","RX_ERR9","Received a bad sequenced [chars] message from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An LWAPP packet sequence mismatch has occurred, and a LWAPP packet was dropped.The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","1","SECURITY_ERR","Not advertising SSID [chars] on REAP AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] because L3 security is enabled","Only H-REAP APs can advertise the specified SSID due to security issues. The system is not advertising this SSID on the AP because it is not an H-REAP AP.","No action is required."
"LWAPP","2","SEM_CREATE_ERR","Could not create semaphore [chars]","The system is unable to allocate a lock for handling operations on the internal database. The system might become unstable.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","SIG_ERR","No pattern in signature with id [dec], (list id = [dec]), could not encode signature","Due to an internal error, the LWAPP message between the controller and AP was not delivered. The system might not behave as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","SIG_ERR1","Unable to find name for signature [dec] in list [dec] for report from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","The controller could not process the signature report sent by the AP. Some attacks might not be detected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","SIG_ERR10","Unable to re-enable signature processing on AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The controller could not notify the AP about the new signature. The signature processing on the AP might not work as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","SIG_ERR2","Unable to find description for signature [dec] in list [dec] for report from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The controller could not process the signature report sent by the AP. Some attacks might not be detected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","SIG_ERR3","Unknown signature track information ([dec])","The controller could not process the signature report sent by the AP. Some attacks might not be detected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","SIG_ERR4","Unknown signature report type ([dec])","The controller could not process the signature report sent by the AP. Some attacks might not be detected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","SIG_ERR5","Could not gain exclusive access to the signature database","The controller could not send a signature list to the AP due to an internal error.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","SIG_ERR6","All signatures are disabled in the [chars] signature file.","The controller could not send signature information to the AP because all signatures are disabled.","Check if all signatures are disabled, and enable them if desired."
"LWAPP","3","SIG_ERR7","Unable to send toggle signature request to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The controller has failed to change the state of the signature processing on the specified AP. The signature processing on the AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","SIG_ERR8","Unable to disable signature processing on AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Due to an internal error, the signature processing on the specified AP could not be disabled. As a result, the new signature information could not be sent to the AP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","SIG_ERR9","Error sending new signatures to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","New signature information could not be sent to the AP. The signature processing on the AP might not work as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","4","SIG_INFO1","Signature information; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex], alarm ON, [chars] sig [chars], track [chars]precedence [dec], hits [dec], slot [dec], channel [dec], most offending MAC [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Bad signature information has been detected on the specified AP.","No action is required."
"LWAPP","3","SLOT_ERR","AP ([chars]) has no radio cards","No radio cards were detected on the AP. The AP might not be able to service clients.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","2","SOCK_ERR","Error [chars] LWAPP socket","An internal error has occurred. The LWAPP subsystem could not be initialized.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","SOCK_ERR2","Socket select error ([dec])","An internal error has caused a temporary failure in a message handling process. The system is attempting to recover from this situation.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","SOCK_ERR3","Could not read from the LWAPP socket","A failure has occurred when processing an internal LWAPP message. The system might become unstable.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","SOCK_ERR4","Could not read from LWAPP socket, frame length out of bounds ([dec])","A failure has occurred when processing an internal LWAPP message. The system might become unstable.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","SSID_ERR1","Not creating SSID [chars] on AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] because WEP 128 bit encryption is not supported on the AP","The specified WLAN was not added on the AP because 128 bit encryption is not supported on the AP.","Change the number of bits in the encryption, or ignore this message if the AP does not need to advertise the SSID."
"LWAPP","3","SSID_ERR2","Not creating SSID [chars] on AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] because diagnostics channel is enabled","The specified WLAN was not added to the AP because diagnostics have been enabled on that WLAN.","If the WLAN needs to be enabled, disable the diagnostics channel on the WLAN."
"LWAPP","3","STATIC_IP_ERR","Configured static IP Address is not valid for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The IP address information sent by the AP is incorrect.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","2","TASK_CREATE_ERR","Failed to create LWAPP [chars] task","An internal error has occurred and the LWAPP subsystem could not be initialized. The APs might not be able to join the controller.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","TIME_ERR1","Unable to retrieve current time when processing [chars] from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Due to an internal error, information about the current time on the controller could not be obtained. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","TIME_ERR2","Keeping connection from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] in overload condition (max allowed APs [dec], current load [dec])","The controller is overloaded, but this echo request is being processed.","Check if another controller needs to be added to support the number of APs that are deployed."
"LWAPP","3","TIME_ERR3","Unable to retrieve time information to send AP timesync config packet","Due to an internal error, information about the controller's time could not be sent to the AP. The AP and controller time might not be synchronized and the AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","TMR_ERR","[chars] timer count ([dec]) does not match that in the AP ([dec]) AP: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Due to an internal error, this timer event was not processed. The AP might not operate as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","TMR_FREE_ERR","Failed to free [chars] timer; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An internal error occurred while processing a timer. The AP might not operate as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","TMR_START_ERR","Failed to start [chars] timer; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Due to an internal error, the timer could not be triggered. The AP might not operate as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","TX_ERR","Could not transmit LWAPP packet, transmission queue is full for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An LWAPP packet transmission has failed because the transmit queue has reached a maximum limit. It is possible that the response packets from the AP are not reaching the controller.","Check if the AP has rebooted or if it has been removed from the network. Also, check if there are connectivity issues between the AP and the controller."
"LWAPP","3","TX_ERR2","Transmission of LWAPP message failed for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Due to an internal error, the LWAPP message could not be transmitted. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","TX_ERR3","Max retransmissions for LWAPP control message reached on AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] for [chars] (number of pending messages is [dec])","The maximum number of times that an LWAPP control packet is transmitted before declaring the AP is dead has been reached for this AP. The AP might not be on the network or might have rebooted.","Check if the AP has rebooted or if it has been removed from the network. Also check if there are connectivity issues between the AP and the controller."
"LWAPP","3","TX_ERR4","Unable to retrieve AP's ([hex]:[hex]:[hex]:[hex]:[hex]:[hex]) reachability information (VLAN identifier, port number, etc) to [chars]","An LWAPP message has been dropped because the information to send the message was not available.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","TX_ERR5","Failed to transmit [chars] to AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Due to an internal error, an LWAPP message could not be transmitted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","TX_ERR6","Could not send LWAPP control packet, data length ([int]) exceeds MTU ([int]) on interface [int]","Due to an incorrect length of the LWAPP message, it has been dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","TX_ERR7","Could not transmit LWAPP control packet (error = [int])","Due to an internal error, an LWAPP message could not be transmitted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","TX_ERR8","Unable to determine MTU for interface [int]","An error has occurred while obtaining the MTU for the interface. The LWAPP message has been dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","UDP_PORT_ERR","Received invalid UDP port ([dec]) in the packet from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex], dropping the packet","An invalid packet received from the AP has been dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","UNSUPP_AP","Refusing image download request from unsupported AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The AP is not supported in the current version of the controller's software, so the request to download the image has been ignored.","No action is required."
"LWAPP","3","UNSUPPORTED_TYPE","Received an invalid [chars] ([dec]): AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The information received on the controller was not understood, so the message has been dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","UNSUPPORTED_TYPE2","Received an invalid [chars] ([dec])","The information received on the controller was not understood, so the message has been dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","UNSUPPORTED_TYPE3","Received an invalid [chars] ([dec]) or [chars] ([dec]); AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The information received on the controller was not understood, so the message has been dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","VALIDATE_ERR","Validation of [chars] failed - AP  [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Due to invalid parameters sent, the validation of the LWAPP message has failed and the message has been dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","VENDOR_ID_ERR","Invalid vendor identifier in vendor specific payload from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Due to invalid vendor information, the message from the AP has been dropped.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","VENDOR_SPEC_ERR","Failed decoding vendor specific payload","The message from the AP could not be processed due an error in the vendor-specific information.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","WLAN_ERR","Unable to find WLAN [dec] - [chars]; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An internal error has occurred because the WLAN information could not be found. The specified operation could not be performed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","WLAN_ERR2","Unable to find WLAN [dec] to be deleted; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The requested WLAN does not exist in the database, so the request to delete has been ignored.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","WLAN_ERR4","Unable to add WLAN on AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] - max limit reached","An invalid WLAN ID has been received because the controller could not configure the WLAN on the AP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","3","WLAN_ERR5","Unable to find WLAN [dec] to be updated on AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The requested WLAN does not exist in the database, so the request to update the information on the AP has been ignored.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","6","WLAN_STATUS_ERR","[chars] [dec] [chars] [dec] [chars]; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The operation attempted on the slot for the WLAN was not necessary, because the AP was already in that state, so this message has been ignored.","No action is required."
"LWAPP","6","CAPWAP_CREATED_AP","Discarding LWAPP [chars] from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] since AP entry is created in CAPWAP","The message has been received in LWAPP from the AP, but the AP entry was created by CAPWAP. The system is ignoring the message.Explanation    No action is required.Error Message    %LWAPP-6-CAPWAP_SUPP_VER: Discarding [chars] in LWAPP from AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] supporting CAPWAP Explanation    The message was received in LWAPP from an AP that supports CAPWAP. This condition might be normal. The AP will join the controller in CAPWAP after the maximum number of retries in LWAPP.","No action is required."
"LWAPP","4","MSGTAG098","Mesh AP [chars] unable to support the configured VLAN [dec].","The maximum limit on the number of VLANs has been exceeded on the specified AP or in any upstream AP.","Check the number of configured VLANs. Remove unwanted or unused VLANs."
"LWAPP","2","SPAMSEND","Sending through spam instead of capwap; AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system could not transmit the LWAPP message because it could not be encrypted. The AP might not function as expected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"LWAPP","0","RADIUS_ERR","The system could not send join reply, AP authorization failed; AP:%02x:%02x:%02x:%02x:%02x:%02x","The join reply has not been sent to the AP because AP authentication failed.","Check the AP credentials on the RADIUS server or check if the local MAC filtering table is configured. Also check if RADIUS servers are configured and are reachable."
"MIRROR","3","ADD_NODE_FAILED","Unable to add the mac address [hex]:[hex]:[hex]:[hex]:[hex]:[hex] into AVL tree.","The system is unable to add a node into the AVL tree.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MIRROR","3","AVL_DELETE_FAILED","Unable to delete the mac address [hex]:[hex]:[hex]:[hex]:[hex]:[hex] from AVL tree.","The system is unable to delete a node from the AVL tree.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MIRROR","3","AVL_INIT_FAILED","Unable to create AVLs for Mirror module.","The system is unable to create AVLs for the mirror module.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MIRROR","3","DISABLE_MIRRORPORT_FAILED","Could not disable the existing mirror port [dec].","The system could not disable the existing mirror port.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MIRROR","3","ENABLE_MIRRORPORT_FAILED","Could not set the port [dec] as mirror port.Return code:[dec]","The system could not set a port as a mirror port.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MIRROR","3","INVALID_PORT","Port [dec] is invalid.","The port is invalid.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MIRROR","3","MEM_ALLOC_FAILED","Could not allocate memory for [chars].","The system could not allocate memory for HEAP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MIRROR","3","NODE_NOT_FOUND","Unable to add the mac address [hex]:[hex]:[hex]:[hex]:[hex]:[hex] into AVL tree.","The system is unable to find a node in the AVL tree.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MIRROR","3","RETRIEVE_FILE_FAILED","Failed to retrieve the configuration file [chars].","The system has failed to retrieve the mirror configuration file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MIRROR","3","SEM_CREATE_FAILED","Unable to create semaphore for Mirror module.","The system is unable to a create semaphore for the mirror module.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MIRROR","3","STORE_FILE_FAILED","Failed to store the configuration file [chars] into NV Memory.","The system has failed to store the mirror configuration file into the NV memory.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MIRROR","3","TOGGLE_AP_FAILED","Could not toggle the AP [chars]'s mirror mode.[chars].","The system could not toggle the AP mirror mode.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MIRROR","3","TOGGLE_MIRRORMODE_FAILED","Could not toggle mirror mode for the MAC address [hex]:[hex]:[hex]:[hex]:[hex]:[hex] to [chars] state","The system could not toggle client mirroring.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MIRROR","3","TYPE_NOT_MATCH","Given mac's ([hex]:[hex]:[hex]:[hex]:[hex]:[hex]) type [dec] doesn't match with type [dec] found in the AVL tree.","The node type does not match with the node type found in the AVL tree.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MIRROR","3","UPDATE_FAP_AVL_FAILED","Could not update dynamic Foreign AP client to MAC AVL.Mac address is [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system could not update the dynamic foreign AP client to the MAC AVL.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MIRROR","3","UPDATE_FAP_NPU_FAILED","Could not update Foreign AP client's mirror status in NPU.Mac Address is [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system could not update the foreign AP client's mirror status in NPU.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","0","LISTEN_TASK_EXITED","mmListen task did not receive a task control block --exiting","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","0","MOBILITY_TASK_EXITED","mmMobility task did not receive a task control block --exiting","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","0","MULTICAST_GROUP_IP_SET_ERROR","Error in [chars] while setting local moblity group multicast IP Address [dec].[dec].[dec].[dec]. Please disable mobility multicast-mode if this error continues.","A mobile is unable to use multicast for messaging.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","1","ANCHORS_DOWN","All Export-Anchors are down on WLAN [dec]","All Export-Anchors are down on the WLAN. A loss of network connectivity has occurred between the WLC and the export anchors for this WLAN.","Debug the network and the status of the anchors for connectivity issues."
"MM","1","ANCHOR_SEND_FAILED","Unable to send Anchor Close/Transfer message to [dec].[dec].[dec].[dec] due to memory allocation failure.","The system might be running low on memory.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","1","ANCHOR_UNAVAILABLE","All export anchors are down. Cannot anchor the client.[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","No export anchors are up to anchor the client. A loss of network connectivity has occurred between the WLC and the export anchors for this WLAN.","Debug the network and the status of the anchors for connectivity issues."
"MM","1","APENTRY_ADD_FAILED","Unable to create ap-list entry for AP [hex]:[hex][hex]:[hex]:[hex][hex]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","1","CLIENT_SHUNNED","Adding client [hex]:[hex]:[hex]:[hex]:[hex]:[hex] to exclusion list as a result of an IDS shun event for [int].[int].[int].[int]","The system is adding a client to an exclusion list as a result of an IDS shun event.","No action is required."
"MM","1","EXPORT_FOREIGN_DOWN","Export FOREIGN [int].[int].[int].[int] is detected as DOWN. Status:[dec].Cleaning up client entries.","The system has detected that an export FOREIGN is DOWN. The system is cleaning up client entries.","This is a mobility failover event that has occurred due to the loss of connectivity between this WLC and one of its mobility peers. Debug your network for connectivity issues and check the status of the down mobility peer."
"MM","1","GUEST_LAN_ANCHORS_DOWN","All Export-Anchors are down on Guest LAN [dec]","All export anchors are down on the guest LAN.","If this message occurs, it implies that there is loss of network connectivity between the WLC and the export anchors for this guest LAN. Debug the network and the status of the anchors for connectivity issues."
"MM","1","IPSECPAYLOAD_BUILD_FAILED","Unable to build IPSec export data.","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","1","MOBILITYUSER_STATECREATE_FAILED","Unable to create mobility state for user [chars].","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","1","SSHRULE_CREATE_FAILED","Failed to [chars] the SSH Rule for [int].[int].[int].[int].","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","1","USER_NOT_ALLOWED","Unable to allow user [chars] into the system. [chars].","The system is unable to allow the user into the system for the reported reason.","No action is required."
"MM","2","ANCHOR_NOT_DEFINED","Auto anchor required but no anchors defined. Wlan-Id:[dec],SSID:[chars].","An auto anchor is required but no anchors are defined on the WLAN.","Define the anchors for the reported WLAN."
"MM","2","INIT_FAILED","Error while initializing mobility manager: [chars].","An error has occurred while initializing the mobility manager.","Redo the mobility configuration on the controller."
"MM","3","ACLNAM_GET_FAILED","Unable to get acl name for intfAclId [dec]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","3","ANCHOR_ADD_FAILED","Failed to add wlanId in heartbeat list: IP: [dec].[dec].[dec].[dec], WLAN ID: [dec].","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","3","ANCHOR_DEL_FAILED","Failed to delete wlan ID in heartbeat list: IP: [dec].[dec].[dec].[dec], wlanid: [dec].","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","3","APENTRY_DEL_FAILED","Could not delete an AP from the AP list.","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","3","BUFF_ALLOC_FAILED","Could not allocate a system buffer. [chars].","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","3","BUFF_DEALLOC_FAILED","Could not deallocate a system buffer. [chars].","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","3","CLIENT_DELETE_MSG_SEND_ERROR","Unable to send heartbeat list client delete message to mobility task","An internal system error occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","3","EXPORTANCHOR_REQPROC_FAILED","Anchor Export Request from controller (IP: [dec].[dec].[dec].[dec]) ignored. WLAN:[dec]. ClientSec:[hex], WlanSec:[hex]. [chars].","An anchor export request from the controller is ignored.","Change the WLAN configuration to alleviate the problem."
"MM","3","EXPORT_MSG_SEND_ERROR1","Unable to send WiredClientAnchorExport message to mobility task","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","3","EXPORT_MSG_SEND_ERROR2","Failed to send AnchorExport message, mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex] not found","The foreign anchor did not send a mobility message because the mobile was not found.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","3","INTFCHANGE_REGISTER_FAILED","Failed to register callback for interface changes","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","3","INVALID_APLISTUPD_RECVD","Received invalid ap-list-update from [int].[int].[int].[int]. Entries:[dec], Expected:[dec]. [chars].","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","3","INVALID_CIDSUPD_RECV","Received invalid cids-update from [int].[int].[int].[int]. Entries:[dec], Expected:[dec]. [chars].","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","3","INVALID_NONCE_RECVD","Received an invalid Nonce-update from [int].[int].[int].[int]. [chars].","An internal system error occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","3","INVALID_PKT_RECVD","Received an invalid packet from [dec].[dec].[dec].[dec]. Source member:[dec].[dec].[dec].[dec]. [chars].","An internal system error has occurred.","Check mobility configuration to see if it needs correction."
"MM","3","INVALID_PMKDEL_RECVD","Received PMK-delete from [int].[int].[int].[int] with no StationAddress TLV.","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","3","INVALID_PMKUPD_RECVD","Received an invalid PMK-update from [int].[int].[int].[int]. [chars].","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","3","INVALID_WEPDEL_RECVD","Received WEP-Key-delete from [int].[int].[int].[int] with no Station Address TLV","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","3","INVALID_WEPUPD_RECVD","Received an invalid WEP-Key-update from [int].[int].[int].[int]. [chars]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","3","LOCMARK_FAILED","Unable to mark the mobility location of client to unknown.","The system is unable to mark the mobility location of a client as unknown.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","3","MEM_ALLOC_ERROR1","No memory to send WiredClientAnchorExport message to mobility task for WGB [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system might be running low on memory.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","3","MEMBER_ADD_FAILED","Could not add Mobility Member. Reason: [chars], Member-Count:[dec],MAC: [hex]:[hex]:[hex]:[hex]:[hex]:[hex], IP: [dec].[dec].[dec].[dec].","The system could not add a mobility member for the listed in the message reason.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","3","MEMBER_DEL_FAILED","Could not delete Mobility Member. Member=Count:[dec], MAC:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","A mobility member deletion from the list has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","3","MM_ACL","[chars]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","3","MSG_PROC_FAILED","Unable to process the received mobility message. [chars].","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","3","MULTICAST_GROUP_SEND_ERROR","Unable to send multicast mobility message.","A mobile is unable to use multicast for messaging.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","3","NO_APLIST_TLV","Received invalid ap-list-update from [int].[int].[int].[int] with no ap-list TLV.","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","3","PEER_PING_FAILED","Mobility ping to [int].[int].[int].[int] rejected. [chars].","A mobility ping has been rejected.","Check the mping command that you entered."
"MM","3","PING_RESPONSE_DROPPED","Drop mobility ping reply from [int].[int].[int].[int]. Expected reply from [int].[int].[int].[int]. [chars].","A mobility ping response has been dropped.","No action is required."
"MM","3","PING_SEND_FAILED","Failed to send a ping [chars] packet to [int].[int].[int].[int].","The system has failed to send a ping.","Check the mobility configuration to see if it needs correction. If this message recurs, 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","3","SEND_FAILED","Unable to send [chars] to [dec].[dec].[dec].[dec]","The system is unable to send a mobility packet.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","3","SOCK_OPER_FAILED","Failed to [chars] a socket.","A socket operation has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","3","SOCK_SET_ADDRESS_OPTION_FAILED","Failed to [chars] address [dec].[dec].[dec].[dec] to the socket options.","A socket operation has failed. The multicast mode will not work for mobility.","Set the local group multicast address again. If this same message appears, disable multicast mode for mobility. 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","3","MEMORY_READ_ERROR","[chars] Encountered memory error, Please report the error if you experience a crash.","An internal system error has occurred.","This is only a debug message. No action is required. If you experience a system crash, contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","3","SOCK_INVALID_MULTICAST_ADDRESS","Mobility group local multicast address has invalid setting:[dec].[dec].[dec].[dec]. Resetting it to 0.0.0.0 and disabling mobility multicast","The mobility multicast group address configuration was found invalid. It might have been corrupted during a configuration transfer.","Configure the address again by using the config mobility multicast-mode enable multicast_address command."
"MM","3","TUNNEL_ADD_FAILED","Failed to add mobility tunnel to fast path for peer IP: [dec].[dec].[dec].[dec]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","3","TUNNEL_ID_ALLOCATE_FAILED","Failed to allocate mobility tunnel id for peer IP: [dec].[dec].[dec].[dec]","An internal system error has occurred.","If this message recurs, copy the error message."
"MM","3","WGB_ANCHOREXP","[chars]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","4","MEMBER_DOWN","[chars] path to mobility member [int].[int].[int].[int] is DOWN.","A path to a mobility member is down.","If this message occurs, it implies that there is loss of network connectivity between the WLC and one of its mobility peers. Debug the network and the status of the peers for connectivity issues."
"MM","4","HB_MEMBER_ADD_ERROR","Error adding Mobility member to heartbeat list (MAC:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], IP: [dec].[dec].[dec].[dec]).","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","4","HB_MEMBER_DELETE_ERROR","Error deleting Mobility member from heartbeat list (MAC:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], IP: [dec].[dec].[dec].[dec]).","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","4","HEARTBEAT_LIST_MEMBER_UPDATE_ERROR","Error updating Mobility member IP in heartbeat list(MAC: [hex]:[hex]:[hex]:[hex]:[hex]:[hex], oldIP: [dec].[dec].[dec].[dec], newIP: [dec].[dec].[dec].[dec]).","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","4","INVALID_ROAMRESP_RECVD","Received Roam response from [int].[int].[int].[int] with no PMK-R1 TLV","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","4","PING_FAILED","[chars] ping request to [int].[int].[int].[int] failed rc=[dec]","A ping request has failed.","If this message occurs repetitively, it implies that there might be a loss of network connectivity between the WLC and another mobility list member. We recommend that the network and the status of the member be debugged for connectivity issues."
"MM","4","PKT_DROPPED","Mobility packet dropped. [chars].","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","4","PMKCACHE_ADD_FAILED","Failed to create PMK/CCKM cache entry for station [hex]:[hex]:[hex]:[hex]:[hex]:[hex] with update from controller [int].[int].[int].[int]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","4","PMKCACHE_DEL_FAILED","Failed to delete PMK cache entry for station [hex]:[hex]:[hex]:[hex]:[hex]:[hex] with request from controller [int].[int].[int].[int]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","4","WEPCACHE_ADD_FAILED","Failed to create WEP-Key cache entry for station [hex]:[hex]:[hex]:[hex]:[hex]:[hex] with update from controller [int].[int].[int].[int]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","4","WEPCACHE_DEL_FAILED","Failed to delete WEP cache entry for station [hex]:[hex]:[hex]:[hex]:[hex]:[hex] with request from controller [int].[int].[int].[int]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MM","6","HEARTBEAT_LIST_MEMBER_UPDATED","Updating Mobility member IP in heartbeat list(MAC: [hex]:[hex]:[hex]:[hex]:[hex]:[hex], oldIP: [dec].[dec].[dec].[dec], newIP: [dec].[dec].[dec].[dec]).","Internal system information.","No action is required."
"MM","6","MEMBER_ADDED","Adding Mobility member (Index:[dec], MAC:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], IP: [dec].[dec].[dec].[dec]) in [chars].","Internal system information.","No action is required."
"MM","6","MEMBER_DELETED","Deleting Mobility member (Index:[dec], MAC:[hex]:[hex]:[hex]:[hex]:[hex]:[hex]) from [chars].","Internal system information.","No action is required."
"MM","6","MEMBER_UP","[chars] path to mobility member [int].[int].[int].[int] is UP.","A path to a mobility member is up.","No action is required."
"MM","6","MEMBER_UPDATED","Updating Mobility member (Index:[dec], MAC:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], IP: [dec].[dec].[dec].[dec]) in [chars].","Internal system information.","No action is required."
"MM","6","ANCHOR_READY","WLAN [dec] is ready to service clients as an anchor, [int].[int].[int].[int] has come up","The WLAN is ready to service clients as an anchor.","No action is required."
"MM","6","PING_RECEIVER_ENTRY_DELETED","Deleted ping receiver entry([dec].[dec].[dec].[dec]) from hearbeat list for WLAN([dec]).","Internal system information.","No action is required."
"MM","6","SOCK_SET_ADDRESS_OPTION","Setting membership for interface IP [dec].[dec].[dec].[dec] and multicast group [dec].[dec].[dec].[dec] on the mobility sockets.","Multicast group membership was set on the socket.","No action is required."
"MMC","0","NPU_INVALID_FRAME","NPU Frame block invalid","The MMC module has received an invalid frame from the network processor.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MMC","0","NPU_OPER_FAILED","NPU Operational verification failed.","The MMC module has failed to verify whether the network processor is operational or not.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MMC","2","BUFFPOOL_ALLOCATE_FAILED","Failed to allocate a pool of size [dec] bytes from a buffer pool(Id=[dec]).","The MMC module has failed to allocate some memory required by it. The traceback along with this message will suggest why it was needed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MMC","3","GMACREG_WRITE_FAILED","Setting Network processor register failed. This could be temporary problem","The MMC module has failed to set the control register of the network processor. This can be a temporary problem.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MMC","6","LINKSTATUS_CHECK_FAILED","Checking the link status of a particular port failed.","The MMC module has failed to read the link status register of the network processor.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"MMC","6","NPUMSG_READ_FAILED","Reading CPU messages from NPU failed.","The MMC module has failed to read the message queue object that contains any message sent by the network processor.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NIM","0","CREAT_TASK_FAIL","Failed to create the task [chars]","The system has failed to create the task.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NIM","0","MSGQ_CREATE_FAIL","Unable to create msg queue for nimTask.","The system is unable to create a message queue for nimTask.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NIM","0","REGISTRY_GET_FAIL","Unable to pull value from the registry for the key [chars]","The system is unable to pull a value from the registry.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NIM","3","ADMIN_STATE_INVALID","Admin State [dec] is not valid for interface [dec].","The admin state is not valid. The state is not enabled or disabled.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NIM","3","CANT_DISABLE_MCAST","Cannot disable multicast state for interface [int] when LAG is enabled","The system cannot disable multicast state when LAG is enabled.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NIM","3","CHECK_SUM_ERR","Checksum Error on config file [chars].","A checksum error has occurred on the configuration file.","No action is required."
"NIM","3","COMPONENT_ALREADY_REGISTERED","Component [dec] already registered.","The component is already registered. A component that is already registered with a state change function is trying to register again.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NIM","3","CREAT_CPUINTF_FAIL","CPU INTF Create error: Ran out of CPU Interface internal numbers.","NIM Create error: The system has run out of CPU interface internal numbers.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NIM","3","CREAT_LAGINTF_FAIL","LAG interface Create error:Ran out of LAG Interface internal numbers.","LAG interface Create error: The system has run out of LAG interface internal numbers.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NIM","3","CREAT_LOGICALINTF_FAIL","Logical interface create error:Ran out of Logical Interface internal numbers.","Logical interface create error: The system has run out of logical interface internal numbers.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NIM","3","CREAT_PHYINTF_FAIL","PHY interface Create error: Ran out of Physical Interface internal numbers.","PHY interface Create error: The system has run out of physical interface internal numbers.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NIM","3","CREAT_VLANINTF_FAIL","Logical Vlan interface Create error:Ran out of Logical Interface internal numbers.","Logical VLAN interface Create error: The system has run out of logical interface internal numbers.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NIM","3","FS_WRITE_FAIL","Writing data to the config file [chars] failed.","Writing data to the user configuration file has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NIM","3","INIT_TASK_FAIL","Task initialization failure. Waiting on handle [chars] failed","Task initializing has failed for a NIM component.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NIM","3","INVALID_CREAT_REQUEST","Invalid [chars] Create Request.","An invalid interface create request has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NIM","3","LOAD_PORTINFO_FAIL","Loading port info for port number [dec] failed. Ran out of Physical Interface internal numbers.","Loading the multicast appliance mode port configuration has failed. The system has run out of physical interface internal numbers.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NIM","3","MCAST_STATE_UNKNOWN","interface [int] has invalid mcastApplianceState [dec]","The multicast appliance state is invalid.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NIM","3","SET_AUTONEG_FAIL","Error in setting the AutoNeg status for the interface with internal interface number [dec].","An error occurred while setting the status for auto negotiation.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NIM","3","SET_INTFSPEED_FAIL","Error while setting the speed mode for the interface with internal interface number [dec].","An error occurred while setting the speed mode for the interface. The speed and the interface type are not compatible.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NIM","3","SET_MCASTSTATE_FAIL","Error while setting MCAST appliance state for the interface with internal interface number [dec].","An error occurred while setting the MCAST appliance state for an interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NIM","3","SET_MTUSIZE_FAIL","Error while setting MTU size for the interface with the internal interface number [dec].","An error occurred while setting the MTU size for the interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NIM","3","SYSINTF_TYPE_UNKNOWN","Unknown system interface type [dec].","The system has detected an unknown system interface type. The system could not find the next valid interface's internal interface number.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NIM","3","UNKNOWN_INTF_TYPE","Unknown Interface type requested.","An unknown interface type has been requested.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NIM","3","USP_PORT_ERR","Error in USP and/or port registry data.","An error has occurred in the USP and/or port registry data.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NIM","3","USP_SLOT_ERR","Error in USP and/or SYSTEM_SLOTS registry data.","An error has occurred in the USP and/or SYSTEM_SLOTS registry data.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NIM","4","ADDR_TYPE_INVALID","Address type [dec] is not valid for interface [dec].","The address type is not valid. It is not a burned-in address or a locally administered address.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NIM","4","LAG_IN_TRANSITION","LAG in transition. switch reboot DUE..!!!","LAG is in transition. A switch reboot is due.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NIM","4","MCAST_NOT_SET","Multicast appliance flag not set for interface [int]([int],[int],[int]) when LAG enabled.","The multicast appliance flag does not set when LAG is enabled.","No action is required."
"NIM","4","NAME_TYPE_INVALID","Name Type [dec] is not valid for interface [dec].","The interface name type is not valid.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NIM","4","POE_STATE_INVALID","PoE State [dec] is not valid for the interface [dec].","The PoE state is not valid. The state is not enabled or disabled.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NIM","4","TRAP_STATE_INVALID","Trap State [dec] is not valid for interface [dec].","The trap state is not valid. It is not enabled or disabled.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NIM","6","LAA_ADDR_INVALID","Locally administered address is not valid for interface [dec].","The locally administered address is not valid. The LSB of the first byte is not zero.","No action is required."
"NIM","6","MCAST_STATE_CHANGED","LAG Enabled - changed multicast state of interface [int] to ENABLED","LAG is enabled. The multicast state has changed to the Enabled state.","No action is required."
"NIM","6","STACKINTF_NOT_SUPPORTED","Creating Stack Interface currently not supported.","The system has created a stack interface that is currently not supported.","No action is required."
"NIM","6","SW_VER_ERR","Software Version Error on config file [chars].","There is a software version error in the configuration file.","No action is required."
"NMSP","3","CERT_AAA_ERR","NMSP: LBS cert AAA Error for [chars]","NMSP: The controller LBS-SSC AuthList has failed to validate a certificate.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NMSP","3","CONN_LIMIT_EXCEEDED","[chars]: Maximum connection limit of [dec] exceeded","The maximum NMSP connection limit has been exceeded.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NMSP","3","INIT_FAIL","NMSP Task failed to initialize","The NMSP receive task has failed to initialize and cannot accept incoming NMSP messages.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NMSP","3","INV_CERT_LEN","NMSP: Received invalid peer cert (size [int])","The system has received a peer certificate that contains no certificate or is too big.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NMSP","3","PEER_CERT_VER_FAIL","NMSP: LBS cert verification failed check","NMSP: The controller has failed to validate the LBS peer certificate.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NMSP","3","QUEUE_CREATE_FAIL","[chars]: Failed to create messaging Q [chars]","The system has failed to create a messaging queue.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NMSP","3","SOCK_SEL_FAIL_EBADF","[chars]: Select failed with bad file descriptor. All sockets closed","A select failed with a bad file descriptor. All NMSP sockets have been closed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NMSP","3","TASK_CREATE_FAIL","[chars]: Failed to create [chars]","The system has failed to create [chars].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"NULL","0","SOCKET_CREATE_FAILED","Socket creation failed","The NULL module has failed to create a particular socket. The traceback along with this message will suggest which socket it was.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","0","COLLECT_TASK_METRICS_FAILED","Unable to gather task metrics. [chars].","The system is unable to gather task metrics.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","0","INVALID_TIMER_HANDLE","Task is using invalid timer handle [int]/[int]","The task is using an invalid timer handle.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","0","INVALID_TIMERCB","Invalid timer control block. TcbPtr=[hex].","The system has detected an invalid timer control block, and a software timer object has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","0","MEM_ALLOC_FAILED","Failed to allocate memory for [dec] bytes.","The system has failed to allocate some memory. The system might be out of buffers. This may be temporary problem.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","0","MSGQ_CREATE_FAILED","Failed to create the message queue object: [chars]. [chars].","The system has failed to create a message queue object.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","0","MUTEX_CREATE_FAILED","Failed to create a mutual exclusion object. [chars].","The system has failed to create a mutual exclusion object.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","0","RAD_SW_UPGRADE","System has been upgrading Radio SW for more than 30 minutes.","The APs have been downloading software for the last 30 minutes. Either the network is congested or there is a mismatch between the AP image and the controller image.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","0","REAPER_START_FAILED","Unable to start the Osapi Reaper. [chars].","The system is unable to start an OSAPI Reaper.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","0","REAPWATCHER_START_FAILED","Unable to start the Osapi Reaper Watcher. [chars].","The system is unable to start an OSAPI Reaper Watcher.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","0","RESET_START_FAILED","Unable to start the System Reset. [chars].","The system is unable to start the system reset task.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","0","TASK_CREATE_FAILED","Failed to create the task object: [chars]. [chars].","The system has failed to create a task object.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","0","TASK_HUNG","Error! Hung task detected ([chars])! (user [dec]% system [dec]%)Reset!.","The system has detected a hung task.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","0","TASK_INVALID_ADDRESS","Invalid task [address] ([address] < msg < [address]) (1)","The system has detected a possibly corrupted task.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","2","TASK_PRIORITY_INFO","%s - TaskID %d ('%s') osapi_prio %u old_prio %u pthread_prio %d cur_prio %d tickleTimer %u\n","The sytem has changed the thread priority.","No action is required."
"OSAPI","0","TASKLIST_CORRUPTED","Task list corruption detected!!!.","The system has detected a corrupted task list.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","0","TIMERCB_ALLOC_FAILED","Unable to allocate timer control block.","The system is unable to allocate memory for a software timer control block.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","0","TIMERCB_FREELIST_CORRUPTED","Timer control block free list is corrupted. Head=[hex],Count=[dec],Mempool Size=[dec].","The timer control block free list is corrupted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","0","TIMER_CREATE_FAILED","Failed to create a timer.","The system could not create a software timer object.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","1","MUTEX_PRIO_CLEAR","== Unlock assert == ([chars]) prio=[dec] root=[hex] word[[dec]]=[hex].","A mutex clear lock failure has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","1","MUTEX_PRIO_SET","** Lock assert ** ([chars]) prio=[dec] root=[hex] [chars]","A mutex lock priority violation has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","1","MUTEX_PRIO_SET2","** Lock assert ** ([chars]) prio=[dec] root=[hex] word[[dec]]=[hex].","A mutex lock priority violation 2 has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","3","FILE_CREATE_FAILED","Failed to create the file : [chars]. [chars].","The system could not create a file or directory. There may be several reasons behind it, including that the system has run out of disk space.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","3","FILE_OPEN_FAILED","Failed to open the file : [chars].","The system could not open a file or directory. There may be several reasons behind it, including that the path provided does not exist.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","3","FILE_TRANSFER_ABORTED","Aborting file transfer. [chars].","The system is aborting a file transfer.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","3","FILE_WRITE_FAILED","Failed to write [dec] bytes to the file : [chars] (FileDesc:[dec]). [chars].","The system could not write to a file or directory. There may be several reasons behind it, including that the path provided does not exist.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","3","FILE_WRITENOCLOSE_FAILED","Failed to write [dec] bytes (FileDesc:[dec]). [chars].","The system could not write to a file or directory. There may be several reasons behind it, including that the path provided does not exist.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","3","INTF_IOCTL_FAILED","The I/O control operation ([chars]) has failed on the interface [chars].IpAddr:[int].[int].[int].[int] Errorcode:[dec]","The I/O control operation has failed on the interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","3","INVALID_FILE_HANDLE","The File/Socket handle is Invalid. Handle = [dec].","The file/socket handle is invalid.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","3","INVALID_PING_RESPONSE","Ping response from [int].[int].[int].[int] is invalid. [chars].","The ping response is invalid.","This is a debug message only. No action is required."
"OSAPI","3","KTHREAD_STRUCT_ALLOC_FAILED","We failed to create a struct for /proc/[chars]/status","The system failed to create a structure for storing kthread information.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","3","KTHREAD_TABLE_FULL","Need a bigger osapi_kthread_tbl to store kthread [chars] pid=[dec].","The system needs a bigger osapi_kthread_tbl to store a kthread.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","3","LINK_ERROR","Error condition detected on link [chars] (rxp [int] rxe [int]; previously rxp [int] rxe [int]","A link error has been detected on the specified link.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","3","OPEN_FAILED","Failed to open file [chars]","The system is unable to open a file with the given name.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","3","PATH_BUILD_FAILED","Failed to build the path string for [chars]","The system has failed to build a path string.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","3","PING_OPER_FAILED","Unable to start ICMP ping to host [chars]. [chars]","The system is unable to start an ICMP ping to host.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","3","ROUTE_INFO_GET_FAILED","Unable to retrieve routing information","The system is unable to retrieve routing information, and unable to access /proc/net/route.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","3","SOCKET_FAILED","Failed to open socket.","The system is unable to open a socket.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","3","SOCK_OPER_FAILED","The [chars] operation has failed on the socket descriptor [dec]. Errorcode:[dec]","An operation has failed on a socket descriptor.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","3","SYSINFO_FAILED","The system API sysinfo() returned failure. Error: [chars].","The system API has returned a failure.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","3","TASK_ADD_LOCKED","Exceeded maximum task count [int] (max [int])","The maximum number of tasks that can be created has been exceeded.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","3","TASK_GETTIME_FAILED","Failed to retrieve statistics (/proc/<pid>/stats) for task '[chars]'","The system has failed to retrieve statistics (/proc/<pid>/stats) for a task.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","3","TASK_RMV_LOCKED","Failed to delete a task osapiTaskFreeList.head [address], count [int]","The system has failed to delete a task.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","3","TASK_SET_TICKLE","Task [chars] requesting [dec] second timer. Minimum is 20. Setting to 20.","The requested timer is less than the minimum time allowed. The minimum time is 20. The system is setting the timer to 20.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","4","CPU_OVERLOAD","Warning! Task [dec] ([chars]) is taking [dec]% ([dec]% user [dec]%system)of the cpu!.","Warning! A task is overloading the CPU.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","4","FILE_MOVE_FAILED","Failed to move the file [chars] to [chars].","The system could not move or rename a file or directory. There may be several reasons behind it, including that the source path provided does not exist.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","4","GW_ADD_FAILED","Unable to add the gateway [chars]. System command returned failure. Error code:[dec]","The system is unable to add a gateway. The system command has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","4","MSGQ_DUMP_FAILED","Failed to dump the message queue history: [chars]. [chars].","The system has failed to dump the message queue history in the event of a crash.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","4","MSGQ_RECV_FAILED","Failed to receive a message from the message queue object: [chars]. [chars].","The system has failed to receive a message from a message queue object.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","4","MSGQ_SEND_FAILED","Failed to send a message to the message queue object: [chars]. [chars].","The system has failed to send a message to a message queue object.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","4","MUTEX_LOCK_FAILED","Failed to acquire a mutual exclusion object. [chars].","The system has failed to acquire a mutual exclusion object.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","4","ROUTE_ADD_FAILED","Unable to add the route (Dest:[chars], NetMask:[chars], NextHop:[chars]). System command returned failure. Errorcode:[dec]","The system is unable to add a route. The system command failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","4","ROUTE_DEL_FAILED","Unable to delete the route (Dest:[chars], NetMask:[chars], NextHop:[chars]). System command returned failure. Errorcode:[dec]","The system is unable to delete a route. The system command failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","4","TIMERTCB_NOT_ALLOCATED","Timer [int]/[int] ('[chars]') already destroyed.","A software timer object is already destroyed and cannot be used.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","4","TIMERTCB_REALLOCATED","Timer [int]/[int] ('[chars]') found to be destroyed/reallocated.","The timer is destroyed/reallocated.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","4","TIME_SHIFT_DETECTED","Detected [chars] time shift. Last: [dec].[dec]. --> Now:[dec].[dec].","The system has detected a time shift.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","5","CLEAN_TASK","Reaper cleaning up exited task '[chars]' ([address])","The reaper is cleaning up the exited task.","No action is required."
"OSAPI","5","FILE_CLOSE_FAILED","Failed to close the file descriptor: [dec].","The system could not close a file or directory. There may be several reasons behind it, including that the path provided does not exist.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","5","FILE_DEL_FAILED","Failed to delete the file : [chars]. [chars].","The system could not delete a file or directory. There may be several reasons behind it, including that the path provided does not exist.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","5","FILE_READ_FAILED","Failed to read [dec] bytes from the file : [chars] (FileDesc:[dec]). [chars].","The system could not read from a file or directory. There may be several reasons behind it, including that the path provided does not exist.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","5","FILE_READNOCLOSE_FAILED","Failed to read [dec] bytes (FileDesc:[dec]). [chars].","The system could not read from a file or directory. There may be several reasons behind it, including that the path provided does not exist.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","5","MSGQ_DEL_FAILED","Failed to delete the message queue object: [chars]. [chars].","The system has failed to delete a message queue object.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","5","MUTEX_DEL_FAILED","Failed to delete a mutual exclusion object. [chars].","The system has failed to delete a mutual exclusion object.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","5","MUTEX_UNLOCK_FAILED","Failed to release a mutual exclusion object. [chars].","The system has failed to release a mutual exclusion object.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"OSAPI","6","FILE_DOES_NOT_EXIST","File : [chars] does not exist.","The system could not find the file or directory. There may be several reasons behind it, including that certain functionality has never been configured on the system.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","0","CREATETASK","Failed to create PEM receive task.","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","0","NOQ","PEM: no message queue, exiting.","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","1","ADDNPURULE1","Unable to push temporary Fast Path rule for mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex] on AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","1","ADDNPURULE2","Unable to plumb temporary rule for mobile[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","1","ADDVPN","Unable to create IPsec rule for mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","1","ADDWEBRULE1","Unable to add web rule for mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex] on AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","1","ADDWEBRULE2","Unable to create web rule for mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex].","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","1","AEPIINIT","Bypassing AEPI process for mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The AEPI is not enabled and has been bypassed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","1","DELMSRULE1","Unable to delete policy rule [dec] for mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An internal system error has occurred.","No action is required."
"PEM","1","DELMSRULE2","Unable to delete policy rule for mobile[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An internal system error has occurred.","No action is required."
"PEM","1","DOT1XINIT1","Unable to initialize 802.1X for mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex] on AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","1","GETPOL","Unable to retrieve encrypt policy for mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system is unable to retrieve an encryption policy for the mobile.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","1","MGMTINTF","Can not get management interface.","The management interface cannot be found. It needs to be configured.","Configure the management interface."
"PEM","1","MSGTAG050","[chars]: Unable to register L2TP session","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","1","PLUMBIP","Unable to add IP address learning SCB to NPU for mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","1","SERVTYPE","Rejecting web-auth login for user '[chars]' with invalid Service-Type [dec]","The system has detected an invalid AAA service type.","No action is required."
"PEM","1","SETNAME","Unable to allow user [chars] into the system - perhaps the user is already logged onto the system?","This username might have reached its maximum number of allowed sessions. This number can be configured.","Check the configured number of allowed sessions for this user. It may be 0, or the user has already reached the maximum number of allowed sessions. If the user has reached the maximum number, disconnect one of the sessions."
"PEM","1","SNIFFAP","Unable to add sniffer AP fast path rule for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An internal system error has occurred.","No action is required."
"PEM","1","SPAMADDSTA","Unable to create SPAM Mobile State.","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","1","WEBAUTHFAIL","Web authentication failure for station [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Web authentication has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","1","WEBAUTHOFF","Unable to enforce web auth policy due to invalid state for mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Web authentication is not configured.","Configure web authentication."
"PEM","2","ADDVPN3","[chars]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","2","DELVPN1","[chars]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","2","DELVPN4","[chars]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","2","XXX","[chars]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","3","ADDNPURULE3","[chars]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","3","ADDSTA","[chars]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","3","ADDVPN2","[chars]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","3","APPLYPOL","pemLogInWebAuthUser: Failed to apply RADIUS policy.","The AAA override is not enabled or there is an incorrect configuration of the WLAN.","Check the WLAN configuration."
"PEM","3","BADWLANID1","Ignoring zero WLAN ID on AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] for mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An internal system error has occurred.","No action is required."
"PEM","3","BADWLANID2","PEM state [dec], APF state [dec], MM state [dec] for mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An internal system error has occurred.","No action is required."
"PEM","3","CFGSAVE","Error on call to osapiFsWrite routine on config file [chars].","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","3","DELIKE","[chars]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","3","DELMMVPN","[chars]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","3","DELMSRULE3","[chars]","An internal system error has occurred.","No action is required."
"PEM","3","DELSTA","[chars]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","3","DELSTA2","[chars]","The system has attempted to delete a client that does not exist. The client might have already been deleted.","No action is required."
"PEM","3","DELVPN2","[chars]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","3","DOT1XINIT2","[chars]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","3","GLOBALSTAT_GET_FAILED","Unable to get the web-customizations global status for WLAN ID [dec].","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","3","IMPORTSA","[chars]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","3","INVRULE","[chars]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","3","MSGQ","pemSysInit: couldn't create PEM message queue.","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","3","NOOVERRIDE","Failed to apply RADIUS over-ride policy for station [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An AAA override is disabled or the WLAN is incorrectly configured.","Check your WLAN configuration."
"PEM","3","PLUMB","[chars]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","3","PORTCHANGE","simMsPortChange Error in queuing pem message","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","3","REDIRRULE","[chars]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","3","TXXID","pemSend802_2XIDFrame: Out of system buffers.","The system ran out of memory.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","3","TXXID2","pemPortChangeHandler: Could not send XID frame","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","3","TXXID3","pemDispatcPortChange: Could not update NPU","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","3","TXXID4","[chars]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","3","UNKNOWNMSG","PEMRECV: Received unsupported message type [dec].","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","3","WEBEVENT","Bad return from ProcessWebEvent.","An internal system error has occurred.","No action is required."
"PEM","4","ADDVPN4","[chars]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","4","CHANGENACSTATE","Client [hex]:[hex]:[hex]:[hex]:[hex]:[hex] not found while changing NAC state","Changing the NAC state for a client has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","4","DELVPN3","[chars]","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","4","NORCV","PEMRECV: MessageReceive() failed.","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","4","TXIAPPTBL","Unable to send IAPP AssocTableReq for mobile [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","An internal system error has occurred.","No action is required."
"PEM","6","GUESTIN","Guest user logged in with user account ([chars]) MAC address [hex]:[hex]:[hex]:[hex]:[hex]:[hex], IP address [int].[int].[int].[int].","A guest user has logged in.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","6","GUESTOUT","Guest user logged out with user account ([chars]) MAC address [hex]:[hex]:[hex]:[hex]:[hex]:[hex], IP address [int].[int].[int].[int].","A guest user has logged out.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PEM","6","QVLAN_INTF_REMAP","Remapping interface ID for STA [hex]:[hex]:[hex]:[hex]:[hex]:[hex] from [int] to [int] ([chars]).","STAs that are mapped to a quarantine VLAN might need remapping to the correct interface during the quarantine phase.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PKTDEBUG","2","MSGTAG009","Failed to create PKTDEBUG socket rx task..","The PKTDEBUG task has failed to start correctly.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PKTDEBUG","2","MSGTAG010","Unable to open PKTDEBUG socket","The PKTDEBUG task has failed to start correctly.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PKTDEBUG","3","MSGTAG012","select from PKTDEBUG socket failed with error [dec]","The PKTDEBUG task is experiencing problems while processing packets.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PKTDEBUG","3","MSGTAG014","read from dtl PKTDEBUG socket failed.","The PKTDEBUG task is experiencing problems while processing packets.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PKTDEBUG","6","MSGTAG001","Starting packet log","The packet logging service has been enabled.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PKTDEBUG","6","MSGTAG002","Stopping packet log","The packet logging service has been disabled.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PKTDEBUG","6","MSGTAG003","Packet log displayed [int] of [int] packets","The packet logging service displayed the requested number of packets and will now terminate.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PMALLOC","0","ALLOC_POOL_FAILED","Out of memory! Unable to allocate a chunk for pool [dec]!.","The system is out of memory. The system is unable to allocate a chunk of memory for a pool.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PMALLOC","0","INVALID_POOL_INFO","Invalid poolinfo. Last entry in the poolinfo must be zero..","The system has detected an invalid poolinfo. The last entry in the poolinfo must be zero.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PMALLOC","0","MEM_ALLOC_FAILED","Out of memory. Unable to allocate [dec] bytes!.","The system is unable to allocate a specific number of bytes.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PMALLOC","0","MEM_THRESHOLD_REACHED","Memory threshold reached. Not allocating memory.","The memory threshold has been reached. The system is unable to allocate memory.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PMALLOC","3","MEM_MONITOR_ERROR","Memory error detected by monitor.","A memory error has been detected by the monitor.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PMALLOC","3","MEM_MONITOR_GET_CFG","Error! Cannot get memory monitor config.","The system cannot get the memory monitor configuration.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PMALLOC","3","MEM_MONITOR_LOAD_CFG","Error! Cannot load memory monitor config.","The system cannot load the memory monitor configuration.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PMALLOC","3","MEM_MONITOR_WRITE_CFG","Error! Cannot write memory monitor config.","The system cannot write the memory monitor configuration.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PMALLOC","7","MEM_ALLOC_DETAIL","Allocating [dec] bytes into [dec] byte pool.","The memory allocation details are displayed.","No action is required."
"PMALLOC","7","MEM_ALLOC_RAWPOOL","Allocating [dec] bytes into RAW pool.","The memory allocation details are displayed.","No action is required."
"POE","0","RESET_FAIL","Unable to reset the Power Supply for [dec] times. Will try to reset for another [dec] times.","A failure has occurred when resetting the POE device. The system will try to reset it again. It is a fatal error if the POE device cannot be reset after a maximum number of retries.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"POE","3","PORT_RESYNC","poePortResync returned FAILURE.","PoE port resynchronization has failed. There is an inconsistency in the internal data structures.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"POLICY","6","TRANSPORT_MODE_UPGRADE","Switch Transport Mode Upgraded to Layer 3 during Configuration","The configuration was upgraded from Layer 2 to Layer 3 transport mode. Layer 2 is no longer supported. The possible reason for this change is an image upgrade from software release 4.2.x.x.","No action is required."
"POWER","3","FAN_FAIL","[chars]","The specified fan is not functioning properly and has failed.","No action is required."
"POWER","3","PS_FAIL","[chars]","The specified power supply has failed.","No action is required."
"POWER","6","FAN_OK","[chars]","The specified fan is functioning normally and is OK.","No action is required."
"POWER","6","PS_DETECT","[chars]","This message indicates whether the power supply is present or not.","No action is required."
"POWER","6","PS_OK","[chars]","The specified power supply is functioning OK.","No action is required."
"PPTP","1","CONFIG_SAVE_ERROR","Error on call to osapiFsWrite routine on config file [chars].","PPTP configuration changes could not be saved.","Try to reconfigure PPTP parameters and save."
"PPTP","1","LOCAL_IP_NOT_FOUND","unable to determine our own local IP address - pptp will be disabled.","The system is unable to determine the local IP address - PPTP will be disabled.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PPTP","1","SOCKET_CONFIG_ERROR","unable to configure socket - pptp will be disabled...","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PPTP","1","SOCKET_CONFIG_RETRIEVE_ERROR","unable to retrieve socket configuration - pptp will be disabled...","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PPTP","1","SOCKET_OPEN_ERROR","Unable to open listener socket - pptp will be disabled...","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PPTP","1","SOCKET_SELECT_ERROR","select failed for no apparent reason - pptp will be disabled...","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PPTP","2","TASK_CREATE_ERROR","Failed to create pptp main task..","The PPTP task has failed to start correctly.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PPTP","2","TASK_INIT_ERROR1","Unable to open listener socket.","The PPTP task has failed to start correctly.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PPTP","2","TASK_INIT_ERROR2","Unable to bind listener socket.","The PPTP task has failed to start correctly.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"PPTP","2","TASK_INIT_ERROR3","Unable to listen on listener socket.","The PPTP task has failed to start correctly.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RBCP","0","MSGQ_CREAT_FAILED","Failed to create RBCP osapi Queue.","The system has failed to create the RBCP OSAPI queue.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RBCP","0","PORT_NOT_UP","Port 1 not up. Cant plumb Code version.","Port 1 is not up. The system cannot plumb the code version.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RBCP","0","PROD_VER_SET_FAILED","Driver api failed for the command [chars].Cant plumb Code version.Return Code=[dec].","The driver API has failed. The system cannot plumb the code version.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RBCP","0","RBCP_RECVQ_NULL","No RBCP Receive Queue available. Unable to receive RBCP messages","No RBCP receive queue is available. The system is unable to receive RBCP messages.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RBCP","0","RBCP_REGISTRATION_FAILED","RBCP registration failed.Return Code=[dec].","RBCP registration has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RBCP","0","TASK_CREAT_FAILED","Failed to create RBCP receive task.","The system has failed to create an RBCP receive task.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RBCP","3","PDU_TRANSMIT_FAILED","Failed to transmit the RBCP register.Return code=[dec].","The system has failed to transmit the RBCP register.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RBCP","3","RBCP_TX_FAILED","Failed to generate a  RBCP platform response.Return code=[dec].","The system has failed to generate an RBCP platform response.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RF","3","NOTIF_TID","Notification timer extended for the wrong client, cur-client=[dec], req-client=[dec]","The current RF client has attempted to extend the RF notification timer using a client ID other than its own. This is an internal software error. The message text on the console or in the system log contains the error details, such as the current client ID number and the requested client ID number.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RF","3","NOTIF_TMO","Notification timer Expired for RF Client: [chars]([dec])","The client has indicated it has work to do to RF by returning RF_OK as part of the progression, but it did not complete the work corresponding to the RF within the notification timer.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RF","5","RF_TERMINAL_STATE","Terminal state reached for ([chars])","RF has reached a terminal state for the operating mode.","This is a notification message only. No action is required."
"RFID","3","BAD_RSSI_EXPIRY","Illegal rfid expiry value [int]-- defaulting.","Illegal RFID expiry value.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RFID","3","BAD_RSSI_HALFLIFE","Illegal rfid rssi half life value [int]-- defaulting.","Illegal RFID RSSI half life value.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RFID","3","BAD_TIMEOUT","Illegal rfid timeout value [int]-- defaulting.","Illegal RFID timeout value.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RFID","3","BLUESOFT_FAIL","Unable to register for bluesoft tag data - error [dec]","The system is unable to register for the bluesoft tag data.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RFID","3","CISCO_FAIL","Unable to register for Cisco tag data - error [dec]","The system is unable to register for the Cisco tag data.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RFID","3","CONFIG_WRITE_FAIL","Unable to write rfid configuration file.","The system is unable to write the RFID configuration file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RFID","3","CREATE_DB_FAIL","Unable to create rfid database","The system is unable to create the RFID database.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RFID","3","CREATE_Q_FAIL","Unable to create rfid interface","The system is unable to create the RFID internal queue interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RFID","3","DEL_FAIL","Error! Can not delete entry from rfid Table","The system cannot delete an entry from the RFID table.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RFID","3","DUP_ENTRY","Duplicate entry found on rfid tree.","A duplicate entry has been found on the RFID tree.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RFID","3","NO_CFG_FILE","Error retrieving file [chars].","An error has occurred when retrieving the file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RFID","3","NO_LOAD_CFG","Unable to load rfid configuration","The system is unable to load the RFID configuration.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RFID","3","NOTIFICATION_TIMER_NOT_CREATED","[chars] Could not create Rfid-Locp Notification timer...","The system could not create the RFID-LOCP Notification timer.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RFID","3","TCB_FAIL","rfid rx task did not receive a task control block --exiting","The RFID rx task did not receive a task control block. The system is exiting.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RFID","3","TIMER_FAIL","unable to create rfid task timer","The system is unable to create the RFID task timer.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RMGR","0","CRITICAL_OP_FAILED","[chars] critical operation failed. System will be rebooted","An internal system error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RMGR","0","ERROR_TASK_EXITED","[chars] task did not receive a task control block --exiting","An internal system error has occurred.","The RMGR services failed to start correctly. 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RMGR","0","ERROR_TEST","[chars] $$$$$$$$$ See if we can see this--exiting","An internal system error has occurred.","This is a UT test. 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RMGR","0","RSRC_CREATION_FAILED","[chars] critical resource could not be created. System will be rebooted","An internal system error has occurred.","The RMGR critical resource creation failed. If this message recurs, 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RMGR","3","INVALID_PING_RESPONSE","Ping response from [int].[int].[int].[int] is invalid. [chars].","The ping response is invalid.","This is a debug message only. No action is required."
"RMGR","3","PING_OPER_FAILED","Unable to start ICMP ping to host [chars]. [chars]","The system is unable to start an ICMP ping to the host.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RMGR","3","RED_API_RET_ERROR","The API [chars] returns error in [chars]","The API returns the specified error.","This is a debug message only. No action is required."
"RMGR","3","RED_BAD_FUNC_ARGS","[chars]: The function argument(s) is bad","The function argument is bad.","This is a debug message only. No action is required."
"RMGR","3","RED_BAD_PARAMS","[chars]: The parameter(s) is bad or not initialized yet","The parameter is bad or is not initialized yet.","This is a debug message only. No action is required."
"RMGR","3","RED_FSM_UNUSUAL_CONDITION","[chars]: [chars]","The FSM has an important unusual condition (may not be an error).","This is a debug message only. No action is required."
"RMGR","3","RED_HEALTH_RPT","[chars]: The bitmap [hex] reported from [chars]","This is a health state report.","This is a debug message only. No action is required."
"RMGR","3","RED_HEARTBEAT_TMOUT","[chars]: Recved GW ping count [dec] phyMgr ping count [dec].","The redundancy heartbeat is a timeout.","This is a debug message only. No action is required."
"RMGR","3","RED_INCONSISTENT_VALUES","[chars]: The value [hex] and [hex] are not consistent","The values are not consistent.","This is a debug message only. No action is required."
"RMGR","3","RED_ROLE_NOTIF_TMOUT","[chars]: [chars]","The role notification is timing out without getting an ACK.","This is a debug message only. No action is required."
"RMGR","3","RED_SM_EXECUTION_ERROR","The state machine state [dec] event [dec]","This is a state machine error execution.","This is a debug message only. No action is required."
"RMGR","3","RED_SWITCH_CASE_NOT_HANDLED","[chars]: The switch case [hex] not handled","The switch case is not handled.","This is a debug message only. No action is required."
"RMGR","3","SOCK_OPER_FAILED","The [chars] operation has failed on the socket descriptor [chars]. Errorcode:[dec]","An operation has failed on a socket descriptor.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RMGR","6","RED_MOD_NAME","The configured redundancy mode is [chars]","The configured redundancy mode can be read OK.","No action is required."
"RMGR","6","RED_SM_EXECUTION","The state machine state [chars] event [chars]","This is a state machine normal execution.","No action is required."
"RMGR","0","CRITICAL_OP_FAILED","%s critical operation failed. System will be rebooted","The system encountered a critical error due to which the system will be rebooted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RRM","0","FAILEDTIMERCREATE","RRM failed to create timer","The system failed to create a timer.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RRM","3","AP_DB_ERR1","Unable to find AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] entry in the database, could not process [chars]","The operation being performed for the AP failed because the internal entry for the AP was not found. It is possible that the AP has been removed from the controller.","Use the show ap summary command to determine if the AP is still joined to the controller. If it is not, the message may be ignored. If it is still joined, restart the AP to ensure that it has the latest configuration and contact technical assistance if the problem recurs."
"RRM","3","AP_DB_ERR2","Invalid slot number [dec] for  AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] could not process [chars]","The AP has included the wrong slot number.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RRM","3","FAILEDCOVERAGEPROFILE","[chars]: Coverage profile violation on [chars] AP[hex]:[hex]:[hex]:[hex]:[hex]:[hex]::[dec]","A coverage profile violation has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RRM","3","FAILEDINTPROFILE","[chars]: Interference profile violation on [chars] AP[hex]:[hex]:[hex]:[hex]:[hex]:[hex]::[dec]","An interference profile violation has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RRM","3","FAILEDLOADPROFILE","[chars]: Load profile violation on [chars] AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]::[dec]","A load profile violation has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RRM","3","FAILEDNOISEPROFILE","[chars]: Noise profile violation on [chars] AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]::[dec]","A noise profile violation has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RRM","3","FAILEDRMCLIDB_ADD","Adding to CCX RM Client Database failed for[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","Adding to the CCX RM client database has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RRM","3","INVALIDRFDOMAINNAME","[chars]: Could not read valid RF domain name","The system has detected an invalid RF domain name.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RRM","3","MSGTAG021","[chars]: Unable to queue enchanced coverage data from AP [chars] on [chars]","[chars]: The system is unable to queue enhanced coverage data from the AP [chars] on [chars].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RRM","3","REACHEDMAXCLIENTS","Reached max Rm clients. dropping[hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system has reached the maximum number of RM clients.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RRM","3","RRM_LOGMSG","RRM LOG: [chars]","RRM LOG.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"RRM","6","GETRFDOMAINNAME","[chars]: Read RF domain name as [chars]","The system is reading the RF domain name.","This is a debug message only. No action is required."
"RRM","6","PASSEDCOVERAGEPROFILE","[chars]: Coverage profile recovery on [chars] AP[hex]:[hex]:[hex]:[hex]:[hex]:[hex]::[dec]","A coverage profile is in recovery.","This is a debug message only. No action is required."
"RRM","6","PASSEDINTPROFILE","[chars]: Interference profile recovery on [chars] AP[hex]:[hex]:[hex]:[hex]:[hex]:[hex]::[dec]","An interference profile is in recovery.","This is a debug message only. No action is required."
"RRM","6","PASSEDLOADPROFILE","[chars]: Load profile recovery on [chars] AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]::[dec]","A load profile is in recovery.","This is a debug message only. No action is required."
"RRM","6","PASSEDNOISEPROFILE","[chars]: Noise profile recovery on [chars] AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]::[dec]","A noise profile is in recovery.","This is a debug message only. No action is required."
"RRM","6","SETCHANNEL","set channel on cell [hex]:[hex]:[hex]:[hex]:[hex]:[hex]::[dec] to [dec] to reduce co-channel interference from [dec] to [dec]","The system has set the channel to reduce cochannel interference.","This is a debug message only. No action is required."
"RRM","6","SETRFDOMAINNAME","[chars]: Change RF domain name to [chars]","The system has set the RF domain name.","This is a debug message only. No action is required."
"RRM","6","SETTXPOWER","[chars]: Set transmit power on [chars] AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]::[dec] to [int]","The system has set the transmit power.","This is a debug message only. No action is required."
"RRM","6","UPDATECHANNEL","[chars]: Set channel on [chars] AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]::[dec] to [dec] by configuration change","A channel configuration change has occurred.","This is a debug message only. No action is required."
"RRM","6","UPDATETXPOWER","[chars]: Set transmit power on [chars] AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex]::[dec] to [int]","A transmit power configuration change has occurred.","This is a debug message only. No action is required."
"SIM","7","ADDR_CHANGE_DTL","Address changed to dtl successfully. [int].[int].[int].[int] ==> [int].[int].[int].[int] (rc [dec])","The address has changed to DTL successfully.","No action is required."
"SIM","3","ADDR_INFO_FAIL","Unable to retrieve client Ip info. Ip Addr: [int].[int].[int].[int]","The system is unable to retrieve the client IP information.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","4","ADD_VLAN_NPU_FAIL","Failed to add/remove/update vlan information into NPU.vlan [int], intf [int]","The system has failed to add/remove/update VLAN information into the NPU.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","APMGR_CONF_FAIL","Failed to configure AP-Manager. Cannot configure AP-Manager When LinkAggregation is enabled","The system has failed to configure the AP Manager. It cannot configure the AP Manager when Link Aggregation is enabled.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","APPLY_CONFIG_FAIL","Unable to apply SIM Configuration data","The system is unable to apply the SIM configuration data.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","ARP_SND_FAIL","Unable to send ARP Request. Local MAC: [hex]:[hex]:[hex]:[hex]:[hex]:[hex].Ip Addr: [int].[int].[int].[int]Interface # [dec]. Vlan Id: [dec]","The system is unable to send an ARP request.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","CREATE_AP_INTERFACE_FAIL","Unable to create AP manager interface","The system is unable to create an AP manager interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","CREATE_INTF_FAIL","Unable to create the [chars] interface","The system is unable to create an interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","0","CREATE_TASK_FAIL","Failed to Create Transfer Task. The cli, web or snmp may not be initialized","The system has failed to create a transfer task. The CLI, web, or SNMP may not be initialized.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","CREATE_VLAN_FAIL","Unable to create VLAN Interface [chars]","The system is unable to create a VLAN interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","DEL_INTF_APGROUPMAP_FAIL","AP Group vlan is mapped to this Interface.","An AP group VLAN is mapped to this interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","DEL_INTF_FAIL","Unable to delete interface [chars] form AVL Tree. Internal System Error","The system is unable to delete an interface from the AVL tree.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","DEL_INTF_WLANMAP_FAIL","A Wireless LAN is assigned to this Interface.","A wireless LAN is assigned to this interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","DHCP_CONF_FAIL","Unable to set service port protocol.DHCP server failed to be configured","The system is unable to set the service port protocol. The DHCP server has failed to be configured.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","DS_CONF_FAIL","Failed to configure the Distribution system Interface.Old Port: [dec]. New Port: [dec]","The system has failed to configure the distribution system interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","DS_DEL_FAIL","Failed to delete the distribution system interface [chars]. Port # [dec]","The system has failed to delete a distribution system interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","ENTRY_CREATE_FAIL","Failed to create a Qos profile. Profile Name: [chars]","The system has failed to create a QoS profile.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","FILE_OPEN_FAIL","Unable to open file <[chars]>: [dec]:[chars].","The system is unable to open a file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","FILE_READ_FAIL","Failed to read config file [chars].","The system has failed to read the configuration file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","FILE_WRITE_FAIL","Failed to Write to config file [chars].","The system has failed to write to the configuration file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","FLASH_READ_FAIL","Error loading '[chars]' file from flash","An error occurred when loading the file from the flash.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","7","GUEST_VLAN_ENABLE_FAIL","Guest VLAN enable failed since either IP or DHCP configuration could not be cleared for interface [chars].","The enabling of the guest VLAN functionality failed because either the IP or the DHCP configuration could not be cleared for the interface.","No action is required."
"SIM","3","INTF_DTL_FAIL","Failed to set the Interface in the device transformation layer.Interface Name: [chars]Failed to resolve Gateway MAC","The system has failed to set the interface in the device transformation layer. It failed to resolve the Gateway MAC.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","6","INTF_FIND_FAIL","Could not find interface [chars].","The system could not find an interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","INTFGET_GIG_ETH_FAIL","Failed to get the Interface number of the Gigabit Ethernet Port","The system has failed to get the interface number of the Gigabit Ethernet port.","No action is required."
"SIM","6","INTF_IN_USE","WLANs enabled for the interface. Disable all WLANs to configure port. Interface Name:[chars]","WLANs have been enabled for the interface.","Disable all WLANs to configure port."
"SIM","3","INTF_PORTSET_FAIL","Failed to set the port number to [dec] for the interface name '[chars]'","The system has failed to set the port number for the interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","INVALID_BAUD_RATE","Invalid baudrate [dec].Setting to default:9600 baud.","The system has detected an invalid baud rate. Possible values are 1200, 2400, 4800, 9600, 19200, 38400, 57600, and 115200. The system is setting to the default value of 9600 baud.","No action is required."
"SIM","3","INVALID_INTF","Cannot set the specified interface number","The system cannot set the specified interface number.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","INVALID_PORT","Using invalid port number. Port out of range. Port # [int]","The system is using an invalid port number. The port is out of range.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","INVALID_PORT_NUM","Invalid Port # [dec]","The system has detected an invalid port number.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","INVALID_VLANID","Using invalid VLAN ID.Vlan Id out of range. Vlan # [int]","The system is using an invalid VLAN ID. The VLAN ID is out of range.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","6","LAG_ALREADY_CONF","Link Aggregation is already set to the same Configuration.","LAG is already set to the same configuration.","No action is required."
"SIM","3","LAG_DSBL_PORT_ENBL","LAG disabled but Primary Port enabled","LAG has been disabled but the primary port has been enabled.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","LAG_ENBL_PORT_DSBL","LAG enabled but Primary Port disabled","LAG has been enabled but the primary port has been disabled.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","LAG_INIT_FAIL","Failed to initialize link aggregation. Error Code:[int]","The system has failed to initialize link aggregation.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","7","LAG_INTF_CREATED","LAG Interface (port [int]) created...","A LAG interface has been created.","No action is required."
"SIM","6","LAG_INTF_DEL","Link Aggregation Enabled.Dynamic Interface '[chars]' deleted","LAG has been enabled. All dynamic interfaces have been deleted.","No action is required."
"SIM","3","LAG_INTF_DEL_FAIL","Failed to delete interface '[chars]'","The system has failed to delete a dynamic interface while enabling LAG.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","LAG_INTF_TO_PORT_MAP","Failed to map LAG interfaces to LAG ports. Error Code [int]","The system has failed to map LAG interfaces to LAG ports. LAG has malfunctioned.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","4","LAG_IN_TRANSITION","LAG in transition. switch reboot DUE..!!!","LAG is in transition. A switch reboot is due.","No action is required."
"SIM","3","LAG_PORTADD_FAIL","Failed to add port for LAG. Error code [int]. Port # [int]","The system has failed to add a physical port to LAG.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","LAG_PORT_CHANGE_FAIL","Failed to change the Link Aggregation port status. Port # [dec]","The system has failed to change the LAG port status.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","6","LAG_WLAN_DISABLED","Link Aggregation Enabled. WLAN [int] disabled and set to interface [chars]","LAG has been enabled. The WLAN has been disabled and remapped.","No action is required."
"SIM","3","LVL7_TO_BAUD_FAIL","Invalid baud value [dec], returning baudrate of 9600.","An invalid baud value has returned a baud rate of 9600.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","MACADDR_GET_FAIL","Interface [dec] source MAC address is not found.","An interface source MAC address has not been found.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","MACADDR_READ_FAIL","Failed to retrieve MAC Address from registry","The system has failed to retrieve a MAC address.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","MAXLEN_DESC_FAIL","Failed to read/write the profile description. Profile Too Big. Profile Name:[chars]","The system has failed to read/write the profile description. The profile is too big.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","MEM_ALLOC_FAIL","Interface File migration failed - OUT OF MEMORY!!!.","An interface file migration has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","MIG_OLD_CFG","Interface File migration failed - OUT OF DATED CFG !!!.","An interface file migration has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","MLTP_UNTG_INTF","Multiple untagged interfaces on same port not allowed","Multiple untagged interfaces on the same port are not allowed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","NPU_IPADD_FAIL","Failed to add the Ip Address of a client in the NPU. IP: [int].[int].[int].[int].MAC: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system has failed to add the IP address of a client in the NPU.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","4","NPU_IPDEL_FAIL","Failed to delete the Ip Address of a client from the NPU. IP: [int].[int].[int].[int]MAC: [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","The system has failed to delete the IP address of a client from the NPU.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","7","PHASE2_LAG_INIT","Phase2 of LAG Initialization...","Phase 2 of LAG initialization has begun.","No action is required."
"SIM","7","PHASE2_LAG_INIT_DONE","Phase2 of LAG Initialization...done.","Phase 2 of LAG initialization is completed.","No action is required."
"SIM","7","PORT_CHANGED","interface '[chars]' port changed to 1","The interface port has changed to 1.","No action is required."
"SIM","7","PORT_DEL_START","Starting Port delete from NPU. vlan=[dec], intf ID=[dec]","The system is starting a port delete from the NPU.","No action is required."
"SIM","3","PORT_DOWN","Physical port [dec] is down!.","A physical port is down.","No action is required."
"SIM","6","PORT_FAIL","Port [[dec]] Out of Range for LAG. Valid Range is [dec] - [dec]","The requested port is out of range for LAG.","No action is required."
"SIM","3","PORT_GETSTATE_FAIL","Unable to get link state for port [dec] of interface[chars].","The system is unable to get the link state for a port.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","7","PORT_NPU_ADD_START","Starting Port Add To NPU. vlan=[dec], port=[dec], portBitMap=[hex]","The system is starting a port add to NPU.","No action is required."
"SIM","3","PORT_UP","Physical port [dec] is up!.","The physical port is up.","No action is required."
"SIM","7","PORT_UPDATE_START","Vlan Port Update Start. oldPort:[dec] newPort:[dec] oldVlan:[dec] newVlan:[dec] vlanName:[chars]","A VLAN port update has started.","No action is required."
"SIM","7","PORT_ZERO","Using invalid port number. Port out of range. Port # [int]","The system is using an invalid port number. The port is out of range.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","QOS_ACIMAP_FAIL","Unable to set [chars] Adjacent Channel Interference (ACI) map","The system is unable to set the profile Adjacent Channel Interference (ACI) map.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","QOS_ACM_DOT1A_FAIL","Unable to set [chars] Admission Control (ACM)","The system is unable to set Admission Control (ACM).","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","QOS_ACM_DOT1BG_FAIL","Unable to set [chars] Admission Control (ACM)","The system is unable to set Admission Control (ACM).","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","QOS_AIFS_FAIL","Unable to set [chars] Arbitration Interframe Space (AIFS)","The system is unable to set the Arbitration Interframe Space (AIFS).","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","QOS_AVGBW_FAIL","Unable to set [chars] Profile Real-Time and Data Bandwidth Contract (Average)","The system is unable to set the profile real-time and data bandwidth contract (average).","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","QOS_BURSTBW_FAIL","Unable to set [chars] Real-Time or Data Bandwidth Contract (Burst)","The system is unable to set the real-time or data bandwidth contract (burst).","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","QOS_CREATE_PROFILE","Unable to create [chars] QOS Profile","The system is unable to create a QoS profile.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","QOS_CWMAX_FAIL","Unable to set [chars] Maximum Contention Window (CwMax)","The system is unable to set the Maximum Contention Window (CwMax).","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","QOS_CWMIN_FAIL","Unable to set [chars] Minimum Contention Window (CwMin)","The system is unable to set the Minimum Contention Window (CwMin).","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","QOS_DOT1P_FAIL","Unable to set [chars] 802.1P Tag","The system is unable to set a 802.1P tag.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","QOS_DSCP_FAIL","Unable to set [chars] Differentiated Service Code Point (DSCP)","The system is unable to set a Differentiated Service Code Point (DSCP).","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","QOS_INIT_FAIL","Error! Couldn't load qos configuration at initialization","The system could not load the QoS configuration at initialization.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","6","QOS_NAME_INVALID","Qos Profile Name Invalid. Profile Name Too Long or No Profile Name Given","The QoS profile name is invalid. The profile name is too long or no profile name is given.","No action is required."
"SIM","3","QOS_PROFILE_DESC_SET","Unable to set [chars] QOS Profile Description","The system is unable to set a QoS profile description.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","QOS_QUEUE_DEPTH_FAIL","Unable to set [chars] Queue Depth","The system is unable to set the queue depth.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","QOS_RF_USAGE_FAIL","Unable to set [chars] RF Usage","The system is unable to set RF usage.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","6","QOS_SAME_PROFILE","QOS Profile Name [chars] already set. Cannot apply the same profile.","A QoS profile has already been set. The system cannot apply the same profile.","No action is required."
"SIM","3","QOS_TXOP_FAIL","Unable to set [chars] Transmission Opportunity (Txop)","The system is unable to set the Transmission Opportunity (Txop).","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","QOS_WIRED_PROTOCOL_FAIL","Unable to set [chars] Wired Protocol","The system is unable to set the Wired protocol.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","QVLAN_CREATE_FAILED","Attempt to create a new quarantine VLAN [chars] failed.","When a quarantine VLAN is assigned to an interface, the system internally creates an interface .sys.quarantine-<port.","No action is required."
"SIM","3","QVLAN_DEL_FAILED","Attempt to delete existing quarantine VLAN [chars] failed.","When the quarantine VLAN is changed on an interface, the system attempts to delete the old quarantine VLAN. This delete operation has failed.","No action is required."
"SIM","3","QVLAN_EXISTS","Attempt to assigned quarantine VLAN [int] to interface [chars] failed. VLAN [int] already exists as interface [chars].","The quarantine VLAN must not be assigned to any other port/VLAN combination.","No action is required."
"SIM","3","QVLAN_FIND2_FAILED","Unable to find quarantine vlan [int] in the interface db.","When a quarantine VLAN is assigned to an interface, the system internally creates an interface .sys.quarantine-<port.","No action is required."
"SIM","3","QVLAN_FIND_FAILED","Unable to find quarantine interface [chars] in the interface db.","When a quarantine VLAN is assigned to an interface, the system internally creates an interface.","No action is required."
"SIM","3","QVLAN_PORT_SET_FAILED","Attempt to set port number [int] for the quarantine VLAN [chars] failed.","When a quarantine VLAN is assigned to an interface, the system internally creates an interface .sys.quarantine-<port.","No action is required."
"SIM","3","QVLAN_RECURSIVE","Quarantine VLAN cannot be configured on quarantine interface [chars].","This interface was automatically created by the system. Only a limited configuration is supported on this interface.","No action is required."
"SIM","3","QVLAN_STATUS_DOWN","Quarantine VLAN for interface [chars] cannot be set because the interface is not fully configured.","Before the quarantine VLAN is configured on an interface, that interface must have its port and address information fully configured.","No action is required."
"SIM","3","ROUTE_ADD_FAIL","Failed to apply route configuration data;Route add failed.IP Address: [int].[int].[int].[int]","The system has failed to apply route configuration data.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","ROUTE_DEL_FAIL","Could not delete the route for the network [int].[int].[int].[int]","The system could not delete the route for a network.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","SET_APMGR_ADDR_FAIL","Unable to set AP manager address. Subnet:[int].[int].[int].[int] Gateway:[int].[int].[int].[int]","The system is unable to set the AP manager address.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","SET_APMGR_PORT_FAIL","Unable to set AP Manager interface port. Port # [dec]","The system is unable to set the AP manager interface port.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","SET_INTF_ADDR_FAIL","Unable to set service port interface address. Ip Address: [int].[int].[int].[int].Gateway: [int].[int].[int].[int]","The system is unable to set the service port interface address.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","6","SET_P2P_BLOCK","Peer-to-Peer blocking check in forwarding path transitioned from [chars] to [chars].","A peer to peer blocking check was enabled/disabled.","No action is required."
"SIM","3","SET_VAP_INTF_FAIL","Unable to configure a Virtual Access Point Interface. Vap Id: [int]","The system is unable to configure a virtual access point (VAP) interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","SET_VLAN_ADDR_FAIL","Unable to set VLAN Interface Address. Ip Addr:[int].[int].[int].[int]. Gateway:[int].[int].[int].[int]","The system is unable to set the VLAN interface address.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","7","START_CREATE_INTF","Started create interface. interfaceName:[chars], vlanId:[dec]","The system has started to create an interface.","No action is required."
"SIM","7","START_DEL_INTF","Started delete interface. InterfaceName:[chars]","The system has started to delete an interface.","No action is required."
"SIM","7","STARTED_PORT_VLAN_SET","Started port and vlan set. interface '[chars]' priPort = [dec] backupPort = [dec]","The system has started to set a port and VLAN.","No action is required."
"SIM","7","STARTED_VLAN_SET","Started vlan set. intf name=[chars], vlanId:[dec], immediately:[dec]","The system has started to set the VLAN.","No action is required."
"SIM","7","START_INTF_PORT_SET","Starting interface port set. interface '[chars]' priPort = [dec]","The system has started to set the interface port.","No action is required."
"SIM","4","STP_DISABLE_FAIL","Failed to disable the STP sub-system for the switch.","The system has failed to disable the STP subsystem for the switch.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","STP_PORT_MODE_FAIL","Failed to set the port mode to off for STP.","The system has failed to set the port to off for STP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","0","TIMER_CREATE_FAIL","Failed to create down timer for port [int]","The system has failed to create a software timer.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","0","TIMER_START_FAIL","Failed to start a software timer.","The system has failed to start a software timer.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","VLAN_ENTRY_FAIL","Failed to create VLAN interface [chars]","The system has failed to create a VLAN interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","VLANID_NOT_CONF","A valid VLAN ID has to be configured first before the port set. Interface Name: [chars]","A valid VLAN ID has to be configured first before the port can be set.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","VLAN_INIT_FAIL","Error! Couldn't load interface configuration at initialization","The system could not load the interface configuration at initialization.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","VLAN_INTFID_FAIL","Failed to assign Interface ID to Vlan - interface type: [dec].","The system has failed to assign an interface ID to a VLAN.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","VLAN_SAME_INTERFACE","Vlan Interface name [chars] already set. Cannot create the same interface","A VLAN Interface has already been set. The system cannot create the same interface.","No action is required."
"SIM","3","VLAN_SAME_TAG","Interfaces configured with same Vlan Tag, but on different port - Not SupportedPort # [dec], Primary Port # [dec], Vlan Id [dec]","Interfaces are configured with the same VLAN tag, but are on different ports.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","VLAN_UPDATE_FAIL","Failed to update the vlan port settings.Port # [int], vlan Id [int]","The system has failed to update the VLAN port settings.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SIM","3","WLAN_DISABLE_FAIL","Failed to disable WLAN [int]","The system has failed to disable a WLAN.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SNMP","0","SOCKET_OPER_FAILED","[chars] operation failed on a socket descriptor.","A socket failure has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SNMP","3","AVL_CREATE_FAILED","initialiseDSForEventLogInSnmp : Failed to create avl tree","The system has failed to create the AVL tree for the event log.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SNMP","3","INIT_FAILED","Failure occured during initiallization. [chars]. Action: [chars].","One or more failures have occurred during SNMP agent initiallization.","No action is required."
"SNMP","3","INVALID_TX_INTF","Invalid transmit interface. snmpdTI([dec],[dec],[dec],[dec],[dec]) != snmpdTI_local([dec],[dec],[dec],[dec],[dec]).","The interface used for transmitting an SNMP response is invalid.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SNMP","3","MSGTAG001","Timer could not be started","The timer could not be started.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SNMP","3","MSGTAG002","initialiseDSForEventLogInSnmp : Failed to create avl tree","The system has failed to create the AVL tree.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SNMP","3","MSGTAG003","initialiseDSForEventLogInSnmp : Failed to initialise timer","The system has failed to initialize the timer.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SNMP","3","MSGTAG005","Failed to get varbind for [chars], failed to send [chars] trap. Recommended Action    The system has failed to get varbind for [chars], and failed to send a [chars] trap.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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered.Error Message    %SNMP-3-MSGTAG006: Failed to send [chars] trap.","The system has failed to send a [chars] trap.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SNMP","3","MSGTAG007","Failed to get [chars] for Mac address [hex]:[hex]:[hex]:[hex]:[hex]:[hex], failed to send [chars] trap.","The system has failed to get [chars] for the MAC address [hex]:[hex]:[hex]:[hex]:[hex]:[hex], and failed to send a [chars] trap.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SNMP","3","PDU_PARSE_FAILED","Failed to parse an incoming SNMP PDU. [chars].","The system has detected an error when parsing an incoming SNMP PDU.","No action is required."
"SNMP","4","MSGTAG004","Failed to get [chars] for Mac address [hex]:[hex]:[hex]:[hex]:[hex]:[hex], for [chars] trap.","The system has failed to get [chars] for the MAC address [hex]:[hex]:[hex]:[hex]:[hex]:[hex], and for [chars] the trap.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SNMP","4","MSGTAG008","Failed to get [chars] for AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex], API return code: [dec].","The system has failed to get [chars] for the AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex], and an API return code: [dec].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SNMPUTIL","3","CONF_NOT_FOUND","Error retrieving the configuration file [chars].","An error has occurred when retrieving the SNMP configuration from NVRAM.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SNTP","3","FATAL_ERROR_OCCURED","Fatal error: [chars].","A fatal error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SNTP","3","FILE_WRITE_FAILED","Failed to write the file [chars] into NV Memory.","The system has failed to write the file into the NV memory.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SNTP","3","LOAD_CONFIG_FAILED","Unable to load SNTP configuration","The system is unable to load the SNTP configuration.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SNTP","3","MSG_TYPE_UNKNOWN","The message type received ([dec]) is unknown.","The message type received is unknown.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SNTP","3","PKT_LEN_INVALID","The NTP packet received on the socket [dec] has invalid length [dec].","The NTP packet received on a socket has an invalid length.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SNTP","3","SOCK_OPT_FAILED","Failed to set the socket option [chars] on the socket.","The system has failed to set the socket option on the socket.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SNTP","3","SWITCH_PORT_WRONG","The NTP packet received from wrong switchport, [dec].Dropping","The NTP packet has been received from the wrong switchport.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SNTP","4","ANOMALOUS_ERROR","Anomalously high error [float] > [float], but < [float].","An anomalously high error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SNTP","4","HIGH_ERROR","Excessively high error [float] > [float] > [float].","An excessively high error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SNTP","4","PKT_REJECTED","[chars].NTP packet rejected on socket [dec].","An NTP packet has been rejected on a socket.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SNTP","4","RESET_ERROR","[chars]","The system is resetting due to an error.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SNTP","6","HOST_RESOLV_FAILED","Failed to resolve the hostname:[chars].","The system has failed to resolve the hostname.","No action is required."
"SNTP","7","NO_ACCEPTABLE_PKTS","No acceptable packets received.","No acceptable packets have been received.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SNTP","7","RECV_TIME_OUT","Failed to receive data on the socket after [dec] seconds.","The system has failed to receive data on the socket.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SNTP","7","SELECT_FAILED","The select system call failed.Error code: [dec]","The select system call has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SNTP","7","SET_HW_TIME","Setting hardware time to [dec] [dec] [dec] [dec]:[dec]:[dec]","The system is setting the hardware time.","No action is required."
"SNTP","7","TOO_MANY_BAD_PKTS","Too many bad or lost packets.","The system has detected too many bad or lost packets.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SOCKET_TASK","1","SOCK_OPER_FAILED","Socket [chars] operation failed on [int]","An internal error has caused a socket processing failure.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SOCKET_TASK","3","DATA_TOO_SHORT","Received only [int] bytes on protocol socket [int]","An internal error has caused a truncated packet to be received on this socket.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SOCKET_TASK","3","INVALID_ENCAPHDR","Invalid encapsulation header","An internal error has caused invalid data to be passed in the encapsulation header from the data path.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SOCKET_TASK","6","DATA_PROCESSING_FAILED","Failed to process [int] bytes on protocol socket [int]","An error has occurred and the packet handling code cannot process a received frame.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SOCKET_TASK","6","STARTING","Starting socket task for protocol [int] (callback [address])","The system is starting the socket task for a particular protocol.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","6","ADD_CERT_INFO","Adding certificate [chars] added to policy manager","The system is adding a certificate to the policy manager.","No action is required."
"SSHPM","3","ADD_VER_CERT_FAILED","Error encountered while adding verification certificate [chars]","An internal error has occurred. An error occurred when adding a verification certificate.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","4","AES_AP_ONLY","Cisco APs will not be able to join this controller","This system does not contain Cisco certificates for Cisco APs to join.","No action is required."
"SSHPM","4","ALREADY_INIT","[chars] already initialized","An internal error has occurred A function has been called with invalid parameters.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","AP_CERT_DECODE_FAILED","Decoded AP certificate has invalid names","An internal error has occurred. The AP certificate has invalid names.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","4","AP_CERT_EXPIRED","AP certificate time [chars] - [chars] is not valid.","The AP certificate is not valid because the current time falls outside the certificate's validity interval. The controller time may not be set correctly.","Ensure that the controller time is correct."
"SSHPM","3","APPGW_CREATION_FAILED","Unable to create [chars] application gateway config","An internal error has prevented an application gateway configuration from being created.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","AUTH_GRP_ADD_FAILED","Error adding constraint to xauth authorization group","An internal error has occurred. The system has failed to add the xauth constraint to the authorization group.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","AUTH_GRP_CREATION_FAILED","Error creating xauth authorization group","An internal error has occurred. The system has failed to create xauth in the authorization group.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","BAD_CERTLEN","Error reading system certificates - certificate is too large","An internal error has occurred. Insufficient memory has been allocated to hold the certificate. The certificate may be corrupted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","BAD_CERT_MAGIC1","Certificate store Magic1 missing","An internal error has occurred. The certificate store may be corrupted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","BAD_CERT_MAGIC2","Certificate store Magic2 missing","An internal error has occurred. The certificate store may be corrupted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","BAD_CERT_SUBJET","Failed to extract Mac Address from AP certificate","An internal error has occurred. The system cannot extract the MAC Address from the AP certificate.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","BAD_CERT_TYPE","Unrecognized system certificate type [dec]","The system has failed to add a certificate into the certificate table because the certificate type is unknown.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","BAD_COMMIT_CB","SSHPM Policy commit callback with NULL context pointer","An invalid parameter was received from the policy manager callback function.","No action is required."
"SSHPM","2","BAD_DEVICE_ID_CERT","Failed to retrieve MAC address from bsnOldDefaultIdCert certificate","An internal error has occurred. The verification failed for bsnOldDefaultIdCert.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","BAD_NUM_CERT","Invalid number of certificates found","An internal error has occurred. The certificate store may be corrupted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","4","BAD_TFTP_IP","Invalid TFTP IP address [chars]","The system detects an invalid TFTP IP address string.","Check your configuration and try again."
"SSHPM","6","BLD_CERT_DELETED_INFO","Corrected credential index (build CA deleted)","A build CA certificate has been deleted from the credential index.","No action is required."
"SSHPM","3","BAD_CERT_NAME","Failed to extract Cert Name from Subject","An internal error has occurred. The system cannot extract the certificate name from the subject.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","CA_SERVER_INFO","CA-Server for [chars] not configured on system","A CA-server for multiple certificate applications has not been configured.","No action is required."
"SSHPM","6","LSC_CERT_INFO","LSC certificate [chars] not present in system","LSC certificates either are not present in the system or have not been loaded.","No action is required."
"SSHPM","6","LSC_PROV_FAIL","LSC AP Provisioning failed AP MAC: [hex]:[hex]:[hex]:[hex]:[hex]:[hex] Reason: [chars].","The LSC AP provisioning has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","6","LSC_PROV_FAIL_NO_CACERT","LSC AP Provisioning failed AP MAC: [hex]:[hex]:[hex]:[hex]:[hex]:[hex] Reason: No LSC CA CERT.","The LSC AP provisioning has failed.Explanation    Ensure the LSC CA certificate is present on the controller.Error Message    %SSHPM-6-LSC_PROV_FAIL_SYS_BUSY: LSC AP Provisioning failed AP MAC: [hex]:[hex]:[hex]:[hex]:[hex]:[hex] Reason: System Busy. Explanation    The LSC AP provisioning request cannot be handled because the controller does not have the resources.","No action is required."
"SSHPM","6","LSC_READ_CERT","SSHPM-LSC: [chars]","SSHPM-LSC: The CA key has been read from the stored file.","No action is required."
"SSHPM","6","SERVICE_DELETED","Deleting service [chars] on port [int]","This is a service deletion information message from the indicated service.","No action is required."
"SSHPM","3","CA_CERT_TABLE_FULL","Unable to find empty slot in CA certificate table","An internal error has occurred. The CA certificate table is full and it might be corrupted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","CA_CERT_TABLE_INVALID","Accessing CA certificate table before initialization","An internal error has occurred. An error has occurred while accessing the certificate table.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","0","CARD_NOT_FOUND","Slot [dec] requested but not present!","An internal error has occurred. The ESM card has not been found in the slot.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","6","CERT_COMP_MODE_INFO","Certificate compatibility mode automatically set","The new certificate has not been installed. The certificate compatibility mode is enabled automatically.","No action is required."
"SSHPM","3","CERT_CONFIG_UPDATE_FAILED","Error encountered while saving certificate configuration","An internal error has occurred. Writing into nonvolatile storage has failed. The storage may be corrupted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","CERT_DIR_TOO_LONG","Certificate directory name too long; External Key providers registration failed","The external key providers registration has failed because the certificate directory name is too long.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","CERT_LOAD_FAILED","Failed to load [chars] certificate [chars] into certificate table","An internal error has occurred. The system has failed to load a certificate into the certificate table.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","0","CERT_NOT_FOUND","Error encountered while initializing policy manager. [chars] certificates not found","An internal error has occurred. The system is unable to load the indicated system certificate.","Contact your technical support representative"
"SSHPM","3","CERT_REALLOC_FAILED","Memory re-allocation for certificate table failed while adding [chars]","An internal error has occurred. The system has failed to reallocate memory to the enlarged certificate table.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","CERT_TABLE_INVALID","Accessing certificate table before initialization","An internal error has occurred. An error has occurred while accessing the certificate table.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","CFG_LOAD_FAILED","Policy manager failed to load configuration","The SSHPM failed to start because the configuration file cannot be loaded.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","CM_ALLOCATE_FAILED","Failed to allocate certificate manager cache for [chars] certificate","An internal error has occurred while adding a certificate.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","CREDENTIAL_FILE_WRITE_FAILED","Cannot write [chars] to file [chars]","An internal error has occurred while writing to a file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","1","CREDENTIAL_NOT_UNIQUE","Credential name [chars] already exists","The certificate addition has failed because the certificate already exists.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","CREDENTIAL_STORE_FULL","Certificate addition failed because credential store is full","An internal error has occurred while adding a certificate.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","DEALLOC_ENTRY_INVALID","Unable to deallocate an invalid policy manager [chars] list entry","An internal error has occurred while deleting an invalid entry.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","DEALLOC_UNALLOC_LIST_ENTRY","Attempt to deallocate unallocated policy manager [chars] free list element","An internal error has occurred while deallocating an unallocated message free list element.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","DELETE_ENTRY_INVALID","Unable to delete an invalid policy manager [chars] list entry","An internal error has occurred while deleting an invalid entry.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","6","DELETE_INVALID_RULE","Unable to delete rule that has been marked with SSH_IPSEC_INVALID_INDEX","The system received a request to delete a rule that has already been deleted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","DELETE_MANUF_CERT","Cannot delete manufacturer certificate [chars]","An attempt was made to delete the manufacturer certificate.","No action is required."
"SSHPM","3","DELETE_UNKNOWN_CERT","Error encountered while deleting certificate [chars]. Certificate unknown","An internal error has occurred while deleting an unknown certificate.","No action is required."
"SSHPM","3","DERIVE_PUB_KEY_FAILED","Cannot derive public key for [chars] SSL certificate","An internal error has occurred while deriving a public key for the SSL certificate.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","ENTRY_HASH_NOT_FOUND","Failed to find hash entry for rule [hex], raw index = [hex], index = [hex]","An internal error has occurred while finding a hash entry.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","FATAL_CB","Policy manager callback: [chars]","A policy manager callback message was received.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","FOPEN_FAILED","Error reading file [chars]","An internal error has occurred while opening a file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","FREAD_FAILED","Error reading file [chars]","An internal error has occurred while reading a file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","FREAD_FAILED2","Error reading [chars] file. ([dec] out of [dec] bytes read)","An internal error has occurred. The nonvolatile storage may be corrupted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","FREAD_FAILED3","Error reading file. ([dec] out of [dec] bytes read)","An internal error has occurred. The nonvolatile storage may be corrupted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","FREAD_KEY_FAILED","Error reading [chars] Key. File system may be corrupted","The system has failed to read a key from the file system.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","1","FREE_LIST_ALLOCATED","Policy manager [chars] free list already allocated","An internal error has occurred while attempting to allocate a free list when it is already allocated.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","FREE_LIST_DEPLETED","Failed to allocate from policy manager [chars] free list. List has been depleted","An internal error has occurred. The policy manager free list is out of elements.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","FREE_LIST_INVALID","Policy manager [chars] free list is invalid","An internal error has occurred. The policy manager free list may be corrupted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","1","FREE_LIST_NOT_ALLOCATED","Failed to allocate from policy manager [chars] free list. List has not been allocated yet","An internal error has occurred. The system attempted to access the policy manager list, but it has not been allocated yet.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","FSEEK_FAILED","Error reading file [chars]","An internal error has occurred while reading a file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","FS_READ_CERT_FAILED","Error reading [chars] certificate [chars]. File system may be corrupted","An internal error has occurred while reading a certificate from the file system.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","FS_READ_CERT_HEADER_FAILED","Unable to read block [dec] certificate header [dec] from flash","An internal error has occurred while reading from flash. The nonvolatile storage may be corrupted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","FS_READ_KEY_FAILED","Error reading key file [chars] - file system may be corrupted","The system has failed to read a key from the file system.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","FS_WRITE_FAILED","Error encountered while saving [chars]","An internal error has occurred while writing into the nonvolatile storage. The storage may be corrupted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","FTPDATA_CONFIGURED","FTPDATA rule already configured","An internal error has occurred while attempting to enable FTPDATA when it was already enabled.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","4","GET_CERT_IDX_FAILED","Cannot find table index for certificate [chars]","An internal error has occurred while attempting to reference a certificate that does not exist.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","GET_LOCAL_TIME_FAILED","Cannot get system time for [chars] SSL certificate","An internal error has occurred while retrieving the system time for the SSL certificate.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","HTTP_ADD_BLOCK_FAILED","Failed to add block to HTTP redirect config","An internal error has occurred while configuring the HTTP redirect application gateway.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","HTTP_ADD_RULE_FAILED","Failed to add http-redir application gateway rule","An internal error has occurred while configuring the HTTP redirect application gateway.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","HTTP_CONFIGURED","HTTP rule already configured","An internal error has occurred while attempting to enable HTTP when it is already enabled.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","HTTP_MODE_GET_FAILED","Failed to retrieve Web management allowability information","An internal error has occurred while retrieving web management allowability information.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","HTTP_REDIR_BODY_FAILED","Unable to create HTTP redirection page body.","An internal error has occurred while configuring the HTTP redirect application gateway.","Verify virtual interface configuration."
"SSHPM","3","HTTP_REDIR_CLAUSE_ADD_FAILED","Failed to add clause to HTTP redirect config","An internal error has occurred while configuring the HTTP redirect application gateway.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","HTTPS_CONFIGURED","HTTPS rule already configured","An internal error has occurred while attempting to enable the HTTPS when it is already enabled.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","HTTPS_MODE_GET_FAILED","Failed to retrieve Secure web management allowability information","An internal error has occurred. The system is unable to retrieve secure web management allowability information.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","ID_CERT_TABLE_FULL","Cannot find an empty row in ID certificate table - table may be corrupted","The system cannot find an empty row in the certificate table. The certificate table may be corrupted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","ID_CERT_TABLE_INVALID","Accessing identity certificate table before initialization","An internal error has occurred while accessing the certificate table.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","IDX_FILE_CORRUPTED","Credential index file may be corrupted","An internal error has occurred while adding a certificate.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","IDX_LST_CREATION_FAILED","Policy rule table cannot be created","An internal error has prevented SSHPM from initializing.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","IKE_SA_EXPORT_FAILED","Cannot export IKE SA for peer [chars] (status: [dec])","An internal error has prevented IKE SA for the indicated peer from exporting.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","IMPORTED_SESSION_DELETE_FAILED","Failed to delete imported SA for mobile [int].[int].[int].[int]","An internal error has occurred while deleting an imported SA for the mobile.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","IMPORT_ID_CERT_FAILED","Unable to open certificate file to save the generated key","An internal error has occurred while opening a file to save the key.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","INVALID_CID","Function was called with an invalid credential ID","An internal error has occurred. A function call has an invalid parameter.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","INVALID_IP","Function called with invalid IP address range. src: [hex]:[hex] dst: [hex]:[hex].","An internal error has occurred. A function was called with invalid parameters.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","INVALID_IPSEC_PSK","Invalid PSK - not applying IPSEC rule for peer [chars]","The configuration has been aborted because the PSK is invalid.","Verify that the PSK is entered correctly."
"SSHPM","3","INVALID_L2TP_INFO","Invalid L2TP PPP signal received for [chars]","An unexpected L2TP PPP signal was received.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","INVALID_NUM_ELEM_FOR_LIST","Invalid element count requested for [chars] free list","An internal error has occurred. A function has been called with an invalid parameter.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","INVALID_PEER_IP","An attempt to register peer failed because peer address [chars] is not valid","An internal error has occurred. A function has been called with an invalid parameter.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","INVALID_PROTO","Function called with invalid protocol [dec]","An internal error has occurred. A function has been called with invalid parameters.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","INVALID_REQ_ID","An attempt to register peer [chars] failed because function was called with an invalid requester ID [dec]","An internal error has occurred. A function has been called with an invalid parameter.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","INVALID_TFTP_SERVER_IP","Invalid TFTP server address [chars]","The TFTP configuration was aborted because the TFTP server address is invalid.","Check configuration to ensure TFTP server IP address is entered correctly."
"SSHPM","3","INVALID_UDP_PORT","Cannot add UDP broadcast rule with both source and destination port set to zero","An error occurred when configuring the UDP broadcast rule. Both the source and destination port cannot be zero.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","IN_WCP_CONFIGURED","Inbound WCP rule already configured","An internal error has occurred while attempting to enable the WCP when it is already enabled.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","1","IP_PARSE_FAILED","Failed to parse IP address [chars] for http redirect","The system has failed to configure the HTTP redirect application gateway.","Verify the configuration to ensure that the IP address is correct."
"SSHPM","3","IPV4_PASS_RULE_CREATION_FAILED","Failed to create IPv4-PASS rule for IP ranges src:[chars],[chars]  dst:[chars],[chars]","An internal error has occurred while creating a pass rule.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","KEY_BUF_TOO_SMALL","Private key buffer too small to hold private read file [chars]. ([dec] < [dec])","An internal error has occurred while reading a private key.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","KEYED_PEM_DECODE_FAILED","Cannot PEM decode [chars]","The private key structure has failed to parse correctly.","Check your configuration and re-install certificate."
"SSHPM","3","KEY_READ_FAILED","Cannot read key file [chars]","An internal error has occurred while reading a private key file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","KEY_TYPE_NOT_SUPPORTED","Unsupported key format. Only RSA keys are supported","An error has occurred while handing an AP certificate because it does not use an RSA key.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","L2TP_ADD_FAILED","Error adding L2TP tunnel","An internal error has prevented an L2TP tunnel to be added.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","L2TP_ADD_SESSION_FAILED","Unable to insert an L2TP session to SSHPM LNS table","The system cannot insert a session to the SSHPM LNS table due to an internal error.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","L2TP_LINK_UPDATE_FAILED","Cannot update PEM state for L2TP session [chars], reason [chars]","An internal error has occurred while updating the PEM state for an L2TP session.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","L2TP_OPEN_FAILED","L2TP Error. Session [chars] failed to open","An internal error has occurred. The L2TP session failed to open.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","L2TP_PPP_FAILURE","L2TP PPP failure for [chars], reason [chars]","An internal error has occurred to L2TP. The connection may go down.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","L2TP_SESSION_EXISTS","Session already exists in LNS table","Another session exists in the SSHPM LNS table.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","L2TP_SESSION_TERMINATED","L2TP session open terminated for [chars]","The L2TP session was terminated because a terminate signal was received.","No action is required."
"SSHPM","3","L2TP_SESSION_UPDATE_FAILED","L2TP Error. Unable to update a foreign L2TP session","An internal error has occurred. The L2TP session table may be corrupted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","L2TP_STALE_SESSION","L2TP Error. Stale session information found","An internal error has occurred. The L2TP session table may be corrupted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","1","L2TP_XAUTH_NO_SUPPORTED","L2TP with XAUTH is not allowed","L2TP cannot be configured because L2TP with XAUTH is not allowed.","Disable XAUTH in the configuration."
"SSHPM","3","LOCAL_AUTH_CREATION_FAILED","Error creating local authentication structure","An internal error has prevented the creation of a local authentication data structure.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","LOCK_CERT_TABLE_FAILED","Unable to lock CA certificate table","An internal error has occurred while verifying the firmware signature.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","MAC_LOOKUP_FAILED","Unable to find mac address [int].[int].[int].[int]","An internal error has occurred while looking up the MAC address.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","MALLOC_FAILED","[chars]: unable to allocate memory","The system has failed to allocate memory. The system resource is low.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","MALLOC_FOR_CERT_FAILED","Unable to allocate memory for [chars] certificate","The system has failed to allocate memory for a certificate. The system resource is low","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","MALLOC_FOR_KEY_FAILED","Unable to allocate memory for [chars] key","The system has failed to allocate memory for a key. The system resource is low.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","6","MANUF_CERT_INFO","Found Manufacturing-installed device certificates","The system has found manufacturing-installed device certificates.","No action is required."
"SSHPM","3","MARSHAL_CFG_FAILED","Failed to marshal [chars] config","An internal error has occurred while configuring the application gateway.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","MD_FAILED","Failed to create certificate directory","An internal error has occurred while creating a directory on nonvolatile memory.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","MM_POLICY_ADDITION_FAILED","Error setting up inter-switch IPsec policy","An internal error has occurred while adding to the inter-switch IPsec policy.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","2","MNM_ADD_FAILED","Failed to add inter-switch IPSec policy","An internal error has occurred. The system is unable to add the inter-switch IPsec policy.","No action is required."
"SSHPM","3","MSG_LST_CREATION_FAILED","Policy manager message queue create failed","SSHPM initialization failed because the message queue failed to create.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","MSG_Q_CREATION_FAILED","Policy manager failed to allocate message queue","SSHPM failed to start because the message queue failed to create.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","MSG_RX_FAILED","Failed to receive message from [chars]","An internal error has occurred while reading from the message queue.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","MSG_SEND_FAILED","Unable to Queue Message","An internal error has occurred while sending a system message.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","MSGTAG829","ERROR: Could not add inbound TRACE ROUTE rule (ssh_pm_rule_add failed).","The system could not add an inbound trace route rule (ssh_pm_rule_add failed).","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","MSGTAG830","ERROR: Could not create inbound TRACE ROUTE rule (ssh_pm_rule_create failed).","The system could not create an inbound trace route rule (ssh_pm_rule_create failed).","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","2","NETIF_CFG_FAILED","Unable to create [chars] interface","An internal error has occurred while configuring the interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","6","NO_3RD_PARTY_CERT_INFO","No 3rd party certificate configuration found","No third-party certificate configuration has been found.","No action is required."
"SSHPM","4","NO_BUILD_CERT_INFO","Unable to locate firmware build certificate","A build certificate has not been found.","No action is required."
"SSHPM","3","NO_FREE_RULE_IDX","Failed to set up [chars] service - rule table is full","Rules for the indicated service were not configured because of an internal error.","No action is required."
"SSHPM","3","NO_KEY_PASSWD","Cannot decrypt private key because password not specified","The system has failed to decrypt a private key.","Check your configuration and reinstall the certificate."
"SSHPM","3","NO_LOCAL_IKE_SERVER","No IKE server found for local IP [chars]","An error has occurred while importing IKE SA because no IKE server can be found.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","NO_PEER_SSHPM","No SSHPM server found for peer [chars]","An error has occurred while importing IKE SA because no SSHPM server can be found for the indicated peer.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","NO_ROOM_FOR_CERT","Insufficient memory allocated to hold [chars] certificate","An internal error has occurred while accessing a certificate.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","NO_ROOM_FOR_CERT2","Insufficient memory allocated to hold [chars] certificate. ([dec] < [dec])","An internal error has occurred while accessing a certificate.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","4","NO_RULE_IDX","No matching rule index for rule [int]","An internal error has occurred while deleting a rule with the unknown indicated index.","No action is required."
"SSHPM","3","NOT_INIT","[chars] not initialized","An internal error caused a function to fail.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","NO_VIRT_IP","Virtual interface address is not configured","An error has occurred while getting the virtual interface address.","Verify the virtual interface configuration."
"SSHPM","3","NPU_NOT_RESPONDING","Error: NPU did not respond within [dec] seconds - deleting [int].[int].[int].[int]","An internal error has occurred. The NPU has failed to respond.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","2","NPU_VIRT_IP_SET_FAILED","Failed to set virtual IP addr in NPU","An internal error has occurred while setting the virtual IP address in the NPU.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","NV_GET_FAILED","Error getting file [chars] from non-volatile storage","An internal error has prevented the indicated file from being read.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","OUT_WCP_CONFIGURED","Outbound WCP rule already configured","An internal error has occurred while attempting to enable WCP when it is already enabled.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","PEM_DECODE_FAILED","Cannot PEM decode [chars] [chars]","A certificate addition has failed because it cannot be parsed correctly.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","PEM_ENCODE_FAILED","Cannot encode certificate [chars] in PEM format","An internal error has occurred while encoding a certificate to PEM format.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","PIPE_CREATION_FAILED","Policy manager failed to create pipe","SSHPM failed to start because a pipe failed to create.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","PKCS1_DECODE_PRIVATE_KEY_FAILED","Error importing private key for use by [chars] server - PKCS1 decode error","An internal error has occurred while reading a key.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","PKCS1_DEC_PRIV_KEY_FAILED2","Error importing private key. PKCS1 decode error","An internal error has occurred while reading a key.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","PKCS1_ENCODE_PRIVATE_KEY_FAILED","Error exporting private key for use by [chars] server - PKCS1 encode error","An internal error has occurred while adding a certificate.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","PKCS1_ENCODE_PRIV_KEY_FAILED2","Error exporting private key [chars] - PKCS1 encode error","An internal error has occurred while encoding a private key.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","PKEY_DECODE_FAILED","Cannot decrypt private key","The system has failed to decode a private key.","Check the configuration and reinstall the certificate."
"SSHPM","3","POLICY_ALLOCATE_FAILED","Failed to allocate policy rule","An internal error has occurred while allocating a policy entry.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","POLICY_HASH_ADD_FAILED","Failed to add policy rule to hash table","An internal error has occurred while adding a policy rule to the hash table.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","2","POLICY_INIT_FAILED","Unable to complete policy initialization","An internal error has prevented the main policy manager from initializing the child manager.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","PRIVATE_KEY_GEN_FAILED","Cannot generate private key for [chars] SSL certificate","An internal error has occurred while generating a private key for an SSL certificate.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","PUB_KEY_EXTRACT_FAILED","Failed to extract public key from AP certificate","An internal error has occurred. The system cannot extract a public key from the certificate.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","PUB_KEY_MALLOC_FAILED","Failed to allocate memory for public key hash","An internal error has occurred while allocating memory.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","RADIUS_CLT_CREATION_FAILED","Failed to create RADIUS client","An internal error has occurred while creating a RADIUS client.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","RADIUS_SRV_ADD_FAILED","Error adding RADIUS server to policy manager","An internal error has occurred while RADIUS servers to a policy manager.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","RADIUS_SRV_CREATION_FAILED","Error creating RADIUS server info","An internal error has occurred while creating RADIUS server information.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","RADIUS_SRV_INFO_ADD_FAILED","Error adding RADIUS server info","An internal error has occurred while adding RADIUS server information.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","2","RAND_INIT_FAILED","Error encountered while initializing random number generator","An internal error has prevented SSHPM from initializing. Some operation may be affected.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","RANDOM_CID_FAILED","Failed to construct CID for [chars]. Unable to get a random number","An internal error has occurred while adding a certificate.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","RAND_STIR_ERR","An internal error has occurred in random stir routine","An internal error caused a cryptographic function to fail.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","RAND_XOR_ERR","An internal error has occurred in xor-noise routine","An internal error caused a cryptographic function to fail.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","REGISTRY_ADD_FAILED","Cannot add registry entry for peer [chars]","An internal error has occurred while adding an entry for a peer.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","REGISTRY_DELETE_FAILED","Failed to delete registry entry for [chars] (status: [dec])","An internal error has occurred while deleting a registry entry.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","REGISTRY_GET_FAILED","Cannot get registry entry for peer [chars]","An internal error has occurred while retrieving a registry entry for a peer.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","REGISTRY_MEM_ALLOC_FAILED","Unable to allocate memory for policy manager registry","The system has failed to allocate memory. The system resource is low.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","REQ_SAVE_FAILED","Unable to open certificate request file to save certificate request","An internal error has occurred while opening a file to save a certificate request.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","RM_AGGR_GRP_FAILED","Failed to remove aggr-mode group","An internal error has occurred while removing the aggr-mode group.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","RM_AGGRPSK_FAILED","Failed to remove aggressive mode PSK","An internal error has occurred while removing an aggressive mode PSK.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","RM_GRP_FAILED","Failed to remove group. Handle is NULL","An internal error has occurred while removing an aggressive mode PSK group.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","RULE_ADDITION_FAILED","Error adding [chars] rule to policy manager","An internal error has prevented the indicated policy rules from being added to the policy manager.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","RULE_ADDITION_FAILED2","Error adding [chars] rule to policy manager for peer [int].[int].[int].[int]","An internal error has prevented the indicated policy rules from being added to the policy manager.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","RULE_CREATION_FAILED","[chars] rule creation failed for peer [int].[int].[int].[int]","An internal error has prevented the indicated policy rules from being created.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","RULE_CREATION_FAILED2","[chars] rule creation failed for peer [chars]","An internal error has prevented the indicated policy rules from being created.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","4","RULELIST_EXISTS","[chars] rule already exists","An internal error has occurred. The policy manager rule already exists.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","RULE_MEM_ALLOC_FAILED","Unable to allocate memory for policy manager rule","The system has failed to allocate memory. The system resource is low.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","RULE_REG_INIT_FAILED","Error encountered while initializing policy manager registry","An internal error has prevented SSHPM from initializing.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","RULE_SET_IP_FAILED","Error setting IP address [int].[int].[int].[int] for [chars] rule","An internal error has occurred. The system has failed to set the IP address for the policy manager rule.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","SA_CTX_LST_CREATION_FAILED","Policy manager security association context table cannot be created","An internal error has prevented SSHPM from initializing.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","2","SEMA_CREATION_FAILED","Cannot create semaphore [chars]","An internal error has occurred while creating a semaphore. The controller may have a stability problem.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","2","SEMA_GIVE_FAILED","Cannot give semaphore [chars]","A function failed to give a semaphore. The controller may have a stability problem.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","2","SEMA_TAKE_FAILED","Cannot take semaphore [chars]","A function failed to take a semaphore. The controller may have a stability problem.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","6","SERVICE_CREATED","Creating service [chars] on port [int]","This is a service creation information message from the indicated service.","No action is required."
"SSHPM","2","SERVICE_CREATION_FAILED","Unable to create [chars] service","An internal error has prevented the indicated service from being created.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","4","SERVICE_EXISTS","[chars] service already exists","A function is trying to create a service that already exists.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","4","SERVICE_NOT_CREATED","Error initializing [chars] service because service not created yet","An internal error has occurred because the indicated service was not created.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","6","SET_APPGW","Setting up application gateway [chars] on port [int]","This is an application gateway setup informational message.","No action is required."
"SSHPM","3","SET_APPGW_CFG_FAILED","Failed to add [chars] application gateway redirect config","An internal error has occurred while configuring an application gateway.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","SET_APPGW_FAILED","Error encountered while setting up application gateway [chars]","An internal error has prevented an application gateway service from being set up.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","SET_CERT_FROM_TIME_FAILED","Failed to set certificate 'validity not before' string to '[chars]'","An internal error has occurred. The system has failed to set the certificate validity string.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","SET_CERT_UNTIL_TIME_FAILED","Failed to set certificate 'validity not after' string to '[chars]'","An internal error has occurred. The system has failed to set the certificate validity string.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","SKB_GET_INFO_FAILED","Failed to extract information from key","An error has occurred while decoding a private key.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","SSC_INVALID","Invalid self-signed Cisco AP certificate","An AP has presented an invalid self-signed Cisco AP certificate.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","6","SSC_NOT_SUPPORTED_INFO","Controller not configured to accept self-signed AP certificate","The controller is not configured to accept a self-signed AP certificate.","No action is required."
"SSHPM","4","SSH_ALERT","[chars] [chars]","The indicated alert message has been received from the SSH library.","No action is required."
"SSHPM","3","SSH_CONFIGURED","SSH rule already configured","An internal error has occurred while attempting to enable SSH when it is already enabled.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","SSH_EMERG","[chars] [chars]","The indicated emergency message has been received from the SSH library.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","SSH_ERROR","[chars] [chars]","The indicated error message has been received from the SSH library.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","6","SSH_LOG_MSG","[chars] [chars]","The indicated informational message has been received from the SSH library.","No action is required."
"SSHPM","4","SSH_WARNING","[chars] [chars]","The indicated warning message has been received from the SSH library.","No action is required."
"SSHPM","3","SSL_CERT_MALLOC_FAILED","Cannot allocate memory for [chars] SSL certificate","An internal error has occurred while allocating memory for a certificate.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","SSL_KEY_MALLOC_FAILED","Cannot allocate memory for [chars] SSL key","Unable to allocate for SSL key.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","STAT_CERT_FAILED","Certificate file [chars] is missing","An internal error has occurred while reading a certificate file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","STAT_KEY_FAILED","Private key file [chars] is missing","An internal error has occurred while reading a private key file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","SYS_TIME_ERROR","Error getting system time for certificate validation","An internal error has occurred. The system cannot get the system time for a certificate validation.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","0","TASK_CREATION_FAILED","Failed to create policy manager [chars] task","An internal error has prevented SSHPM from initializing the indicated task.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","TASK_PRI_SET_FAILED","Error encountered while increasing policy manager task priority","An internal error has prevented a task priority to be adjusted. Some operations may be affected.","No action is required."
"SSHPM","3","TELNET_CONFIGURED","Telnet rule already configured","An internal error has occurred while attempting to enable Telnet access when it is already enabled.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","TELNET_MODE_GET_FAILED","Failed to retrieve telnet allowability information","An internal error has occurred while retrieving Telnet allowability information.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","TELNET_OVER_OOB_CONFIGURED","Telnet over OOB rule already configured","An internal error has occurred while attempting to enable Telnet over an OOB port when it is already enabled.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","TELNET_OVER_SERVICE_PORT_CONFIGURED","Telnet over service port rule already configured","An internal error has occurred while attempting to enable Telnet over a service port when it is already enabled.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","TIMER_CREATION_FAILED","Failed to create [chars] timer","An internal error has occurred. A Timer creation has failed. The controller may have a stability problem.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","TUNNEL_ADD_PEER_FAILED","Cannot add peer [chars] to tunnel","An internal error has prevented peer information from being added to the tunnel.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","TUNNEL_CREATION_FAILED","Error creating tunnel for [chars]","An internal error has occurred. The tunnel creation has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","TUNNEL_SET_CERT_FAILED","Failed to add CA certificate to tunnel for peer [chars]","An internal error has occurred. The system has failed to add a CA certificate to the tunnel.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","TUNNEL_SET_LOCAL_IP_FAILED","Error setting tunnel local IP for RADIUS server [chars]:[dec]","An internal error has occurred while setting a tunnel local IP for the RADIUS server.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","UNAUTHORIZED_CERT_SUBJECT","Unauthorized subject name found in AP certificate","The AP certificate contains an unauthorized subject name. There might be a security breach.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","UNKNOWN_CA_TYPE","Unrecognized system CA certificate type [dec]","The system has failed to add a CA certificate into a certificate table because the certificate type is unknown.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","UNKNOWN_CERT_ISSUER","Invalid AP certificate. Issuer unknown","An AP certificate is invalid because the issuer is unknown.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","1","UNKNOWN_CREDENTIAL_STATUS","Unrecognized credential status ([dec])","An internal error has occurred while attempting to save credential information with an unrecognized status.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","UNKNOWN_CREDENTIAL_TYPE","Unrecognized credential type ([dec])","An internal error has occurred. A function has been called with invalid parameters.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","UNKNOWN_WLAN_IP","WLAN IP address is not known - deferring WLAN policy initialization","The system is deferring the WLAN setup because the WLAN IP address is not known.","Verify configuration to ensure that IP address is entered correctly."
"SSHPM","4","UNLINK_FAILED","Cannot delete file [chars]","An internal error has occurred. A file deletion has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","UNSUPPORTED_MSG_TYPE","Unsupported policy manager message received (msg type = [dec])","An internal error has occurred. A message of an unsupported type has been received.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","2","VIRT_IF_CREATION_FAILED","Unable to create virtual interface","An internal error has prevented a virtual interface from being created using a saved configuration.","Verify that the configuration is correct."
"SSHPM","3","VIRT_IP_SET_FAILED","Unable to set virtual interface address","An internal error has prevented a virtual interface from being configured using a saved configuration.","Verify that the configuration is correct."
"SSHPM","3","VIRT_NAME_SET_FAILED","Unable to set virtual interface name","An internal error has prevented a virtual interface from being configured using a saved configuration.","Verify that the configuration is correct."
"SSHPM","4","WARNING_CB","Policy manager warning callback: [chars]","A policy manager warning callback message has been received.","No action is required."
"SSHPM","3","X509_CERT_ALLOCATE_FAILED","Error allocating x509 structure for [chars]","An internal error has occurred while adding a certificate.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","X509_CERT_ALLOCATE_FAILED2","Error allocating x509 structure","An internal error has occurred while adding a certificate.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","X509_CERT_DECODE_FAILED","X509 decode failed for [chars]. code [dec]","An internal error has occurred while adding a certificate.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","X509_CERT_ENCODE_FAILED","X509 encode failed for [chars]","An internal error has occurred while encoding a certificate to X509.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","X509_ENCODE_KEY_FAILED","Cannot export private key for file [chars]. Status [dec]","An internal error has occurred while exporting a private key to the correct format.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SSHPM","3","X509_KEY_DECODE_FAILED","X509 private key decode failed for certificate [chars]","An internal error has occurred. A private key import has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSNET","4","ENCAPTYPE_NOT_PROCESSED","sysnet unable to process packet with encap type [int]","The sysnet protocol demux was not able to handle a packet that it received from the forwarding code.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSNET","4","INV_ENCAP_TYPE","Unrecognized Encapsulation type [dec].","The system has detected an unrecognized encapsulation type. This could possibly be due to bad configuration.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSNET","4","INV_EXIT_PORT","Invalid exit port - could not resolve exit intfNum for vlanId [dec], intfNum [dec] Destination MAC [hex].[hex].[hex].[hex].[hex].[hex]","The system has detected an invalid exit port. The system could not resolve the exit intfNum.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSNET","3","INV_IF","Circuit Error - vlan id & intIfNum = 0.","The system has detected a circuit error. Both the VLAN ID and intIfNum are 0.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSNET","3","INV_NOTIFY_TYPE","Unknown Entry Type [dec].","The system has detected an unknown entry type.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSNET","3","INV_REGISTRATION_FN","Invalid Registration Function passed as an argument for  PDU notifications.","An invalid registration function has passed as an argument.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSNET","3","MAC_ADDR_NOT_FOUND","MAC address for the interface [dec] not found.","The MAC address for the specified interface on the controller has not been found.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSNET","3","MAX_REGISTRATION","Maximum number of notification registrations exceeded. Allowed [dec], Current [dec]. Registration Failed for [dec].","Registration has failed because the maximum number of notification registrations has been reached.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSNET","3","MBUFF_ALLOC_FAIL","Out of System buffers.","The system is out of system buffers.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSNET","4","NOTIFY_FN_EXISTS","Registration for Type [chars] already exists.","A notification registry for the specified type already exists.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","BULK_STORAGE_CONF","Failed to configure a bulk data storage media.","The system has failed to configure bulk data storage media.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","CFG_ENC_FAIL","Invalid configuration file encryption key/iv len ([int]/[int])","The system detects an invalid configuration file encryption key/iv len.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","CONFIG_ADD_FAIL","Failed to add all the configuration files to a contiguous buffer. Internal system error","The system has failed to add all the configuration files to a contiguous buffer.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","DEC_UPDATE_FAIL","Decrypt Update failed.rc = [dec]","The decrypt update has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","6","DFLT_CONF_BUILD","Creating default configuration for '[chars]'.","The systme is creating a default configuration.","No action is required."
"SYSTEM","3","ENC_GET_FAIL","No encryption key configured","No encryption key has been configured.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","ENC_UPDATE_FAIL","Encrypt Update failed. rc =[dec]","The encrypt update has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","FILE_NO_SPACE","Not enough space left for file.Space left [int]. File size [int]. File name: [chars]","Not enough space is left for the file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","FILE_OPEN_FAIL","Failed to open file [chars]..","The system has failed to open a file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","FILE_READ_FAIL","Failed to read configuration file '[chars]'","The system has failed to read a configuration file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","FILE_READ_NOCLOSE_FAIL","Failed to read a file. The file may not be opened. File name: [chars]. rc = [dec]","The system has failed to read a file. The file may not be opened.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","FILE_WRITE_FAIL","Failed to write to a configuration file. File Name: [chars]","The system has failed to write to a configuration file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","FLASH_CHK_FAIL","File '[chars]' read with invalid checksum ([hex]), should be ([hex]).Flash file system may be corrupt.","The flash file system may be corrupt.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","FLASH_CRC_FAIL","File read with invalid CRC ([hex]), should be ([hex])Flash file system may be corrupt","The file has been read with an invalid CRC. The flash file system may be corrupt.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","INVALID_BUF_LEN","Invalid buffer length [int]. Internal system error.","The system has detected an invalid buffer length.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","6","INVALID_CONF_RMV","Removing invalid configuration file '[chars]'.","The system is removing an invalid configuration file.","No action is required."
"SYSTEM","3","INVALID_CONF_VER","Invalid configuration file version [int]","The system has detected an invalid configuration file version.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","INVALID_FILE_COUNT","Invalid file count [dec] or count exceeded maximum file entries allowed.","An invalid file count or a count that exceeded the maximum file entries has been allowed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","INVALID_HMAC","Failed to verify HMAC. Internal system error.","The system has failed to verify HMAC.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","INVALID_MBUFF","Mbuf Index contains NULL tail = [address], head = [address],free = [dec]. Shared memory allocation error.","The system has detected a shared memory allocation error.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","INV_BYT_CNT","Size check failed for a system buffer. Internal system error","A size check has failed for a system buffer.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","INV_CIPHER_LEN","Invalid cipher text length [int] (should be [int]). Internal system error.","The system has detected an invalid cipher text length.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","INV_SW_VER_FORMAT","Invalid software version format.","The system has detected an invalid software version format. The format must be ver.release.maint.build.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","MBUF_ALLOC_FAIL","Cannot allocate new Mbuf.Internal system error.","The system cannot allocate a new Mbuf.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","6","MBUF_ALREADY_FREE","Mbuf already free. mbuf = [address], tail = [address], head =[address], i = [dec], free = [dec]","Mbuf is already free.","No action is required."
"SYSTEM","3","MBUFF_ALL_USED","No free Mbufs available. Shared memory allocation failed. Internal system error.","No free Mbufs are available. Shared memory allocation has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","MBUFF_BUSY","Mbuf index contains Busy tail = [address], head = [address],mbuf = [address], free = [dec]. Shared memory resource busy. Internal system error.","The system is trying to allocate a Mbuf that is already in use. The system is not allocating buffer.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","MBUFF_FATAL_ERR","Shared memory resource corrupted. Internal system error.Mbuff free: [dec]. Max Mbuff: [dec].","The shared memory resource is corrupted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","MBUFF_LOCK_FAIL","Failed to lock on shared memory resource. Internal system error.","The system has failed to lock on a shared memory resource.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","MBUFF_NULL_CHK_FAIL","Mbuf slot not NULL. Upper Limit = [hex], Lower Limit = [hex], mbuf = [address],tail = [address], head = [address], free = [dec]. Shared resource failure. Internal system error.","The system detects a shared resource allocation failure.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","MBUF_FREE_TWICE","Mbuf freed twice, prev Line [dec], curr Line [dec]. Internal system error.","The Mbuf has been freed twice.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","MBUF_RANGE_FAIL","Out of range Mbuf. Upper Limit = [hex], Lower Limit = [hex], mbuf = [address]. Internal system error","The shared memory resource is out of range.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","6","MBUFS_FREE","MbufsFree=[int], Active mbuf table, Dumping Mbuff Status","The system is dumping the Mbuf status.","No action is required."
"SYSTEM","3","MEM_ALLOC_FAIL","Failed to allocate memory.","The system has failed to allocate enough memory.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","MSG_SND_FAIL","Failed to send a message to the Print task. Unable to Print data.","The system has failed to send a message to the print task. The system is unable to print data.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","NO_CIPHER","No cipher text","The system has detected no cipher text.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","NOTIFY_SAVE_FAIL","Failed to save data for a Non-volatile component. Registrar ID: [dec].","The system has failed to save a data for a nonvolatile component.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","PASSWD_STORE_ALREADY_REG","Registrar ID [dec]. already registered.","The component could not be registered for password store transcoding.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","PASSWD_STORE_INTEGRITY_FAILED","Cannot retrieve secret from store -- integrity check failed.","The system has failed an integrity check. The secret might have been compromised.","Reconfigure the secret for security reasons."
"SYSTEM","3","PASSWD_STORE_OUT_BUF_TOO_SMALL","Output buffer too small to hold retrieved secret [int] bytes are required, but [int] provided.","There was an error retrieving the secret from the password store.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","PASSWD_STORE_REG_FAILED","Invalide registrar ID [dec].","The component could not be registered for password store transcoding.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","PASSWD_STORE_STORAGE_NOT_INITIALIZED","Store failed because storage not initialized.","An error has occurred while performing the password store operation because the storage is not initialized.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","PASSWD_STORE_STORAGE_TYPE_UNKNOWN","Unknown storage type [hex].","An error has occurred while performing the password store operation because the specified storage type is unknown.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","PASSWD_STORE_TRANSCODE_FAILED","Error encountered while transcoding secret(s) in component ID [dec].","The secret in the specified component could not be transcoded.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","PRINT_NOT_READY","Print Task Not Ready. Unable to print data.","The print task is not ready. The system is unable to print data.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","0","QUEUE_CREATE_FAIL","Failed to create a  queue. Queue Name: '[chars]'","The system has failed to create a queue.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","REGID_FAIL","Registrar ID [dec] already in use. Possible memory corruption or trying to register the component twice","The Registrar ID is already in use. There is possible memory corruption or the system is trying to register the component twice.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","REG_MAX_FAIL","Maximum number of registrations exceeded. Registrar ID:[dec] could not be registered.","The maximum number of registrations has been exceeded. The component could not be registered for NVRAM storage.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","RESTORE_DFL_CONF_FAIL","Unable to restore default configuration.Registrar ID [dec].","The system is unable to restore the default configuration.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","SYSAPI_ERR","System Error : [chars]","A system error occurred with the following string.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","6","SYSAPI_INFO","System Info : [chars]","This is a system information message with the following string.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","VER_LEN_FAIL","Build version length verification failed.","The build version length verification has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","VOL_SIZE_FAIL","Failed to get size of volume. File: [chars]","The system has failed to get size of the volume.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","VOL_WRITE_FAIL","Failed to write configuration file into flash. File Name: [chars].","The system has failed to write the configuration file into the flash.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"SYSTEM","3","SYSAPI_ERR","System Error : [chars]","A system error has occurred with the specified string.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"TFTP","3","FILE_RCV_FAIL","Error while receiving the file. File name: [chars]","An error has occurred while receiving the file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"TFTP","3","FILE_READ_FAIL","Error while reading the local file. File Desc: [dec]","An error has occurred while reading the local file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"TFTP","3","FILE_SND_FAIL","Error while sending the file. File name: [chars]","An error has occurred while sending the file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"TFTP","4","FILE_TOO_BIG","FILE is too big. MAX allowed size for this file type is [dec]blocks ([dec] bytes).","The file is too big.","No action is required."
"TFTP","3","FILE_WRITE_FAIL","Error while writing [dec] bytes to file. Tftp error.","An error has occurred while writing to a file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"TFTP","4","INV_ACK_NUM","Invalid Ack received. The Ack number doesn't match the request. Send block #[dec], got ACK for #[dec].","The system has detected an invalid ACK that is received. The ACK number does not match the request.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"TFTP","3","INV_COMMAND","Invalid tftp command: '[chars]'.","The system has detected an invalid TFTP command.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"TFTP","3","INV_OPCODE","Invalid opcode being used by tftp server or data is corrupt. Opcode: [dec]","The invalid opcode being used by the TFTP server or the data is corrupt.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"TFTP","3","INV_STR_TRM","Error while reading internal buffer!. Invalid string termination.","An error has occurred while reading the internal buffer. An invalid string termination has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"TFTP","4","INV_TFTP_MODE","Invalid tftp mode: '[chars]'. Possible modes are 'binary', 'octet' and 'ascii'","The system has detected an invalid TFTP mode. The possible modes are binary, octet, and ASCII.","No action is required."
"TFTP","4","RETRY_SOCK_RCV_FAIL","Failed to receive a message through the tftp socket. Retrying to receive data..","The system has failed to receive a message through the TFTP socket. The system is retrying to receive data.","No action is required."
"TFTP","3","SOCKET_BIND_FAIL","Failed to bind the socket for tftp. Tftp initialization failed.","The system has failed to bind the socket for TFTP. TFTP initialization has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"TFTP","3","SOCKET_CREATE_FAIL","Failed to create socket for tftp. Tftp initialization failed","The system has failed to create a socket for TFTP. TFTP initialization has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"TFTP","3","SOCK_OPT_FAIL","Failed to configure the socket for tftp. Tftp initialization failed.","The system has failed to configure the socket for TFTP. TFTP initialization has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"TFTP","3","SOCK_RCV_FAIL","Failed to receive a message through the tftp socket.Check network connection and route.Port: [int]","The system has failed to receive a message through the TFTP socket.","Check the network connection and route."
"TFTP","3","SOCK_SND_FAIL","Failed to send a message through the tftp socket. Tftp Failure.Dest Port: [int]","The system has failed to send a message through the TFTP socket.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"TFTP","3","SOCK_TIMEOUT","TFTP Timeout no reply from TFTP server.Check network connection and route to the serverTime out between each retry: [dec].","The TFTP timeout has no reply from the TFTP server.","Check the network connection and route to the server."
"TFTP","3","TFTP_SVR_ERR","TFTP Server Error: [dec]: '[chars]'.","A TFTP server error has occurred.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"TOOL","3","FILECORUPT","Footer offset ([dec]) past end of file ([dec] bytes)in file [chars]","The file is corrupted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"TOOL","3","FILEIMGSIGCORUPT","Error! Invalid image signature in file [chars]","The file is corrupted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"TOOL","3","FILEMAP","Error: Unable to map file [chars] :errcode [chars].","The system has failed to map a file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"TOOL","3","FILEOPEN","Error opening filename <[chars]>: [chars].","The system has failed to open a file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"TOOL","3","FILEREADINGPAST","Error! Reading past end of file [chars]! current = [dec] bytes, size= [dec] bytes.","The file is corrupted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"TOOL","3","FOOTERMISMATCH","Error! Footer mismatch from header! ([address] != [address].","The TLV is corrupted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"TOOL","3","INSTALLTLV","Error [dec] installing TLV.","An error occurred while installing a TLV.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"TOOL","3","SIGLENCORRUP","Error! signature length is corrupted!.","The signature length is corrupted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"TOOL","3","SIGTYPCORRUP","Error! Invalid signature type: [hex].","The signature type is corrupted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"TOOL","3","TLVACTIONERR","Error: Invalid TLV action code [dec].","An improper action was passed upon to \n. The TLV is an invalid action code.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"TRAPMGR","3","CFG_FILE_WRITE_FAILED","Error on call to osapiFsWrite routine on config file [chars].","An error has occurred while writing to the configuration file.","No action is required."
"TRAPMGR","3","DTL_EVENT_PORT_ENTRY","Failed registration for DTL_EVENT_PORT_BSR_TRAP_ENTRY.","The system has failed the registration for the DTL event port trap entry.","No action is required."
"TRAPMGR","3","DTL_EVENT_PORT_EXIT","Failed registration for DTL_EVENT_PORT_BSR_TRAP_EXIT.","The system has failed the registration for the DTL event port trap exit.","No action is required."
"UPDATE","2","BINARY_XML","[chars].","During a binary to XML configuration conversion, either a cfg or xml directory creation or temporary file creation has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"UPDATE","3","CERT_INST_FAIL","Failed to install Webauth certificate. rc = [dec]","The system has failed to install a webauth certificate.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"UPDATE","3","CP_CMD_FAIL","Error while copying webauth files to internal filesystem.","An error has occurred while copying webauth files to the internal file system.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"UPDATE","3","EOF_ERR","Error! Reading past end of file! current = [dec] bytes, size= [dec] bytes. File name: [chars]. Failed to install downloaded s/w.","The system is reading past the end of the file. The system has failed to install the downloaded software.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"UPDATE","3","FILE_OPEN_FAIL","Filed to open file [chars].","The system has failed to open a file.","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. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"UPDATE","3","FILE_READ_FAIL","Error reading certificate file <[chars]>: [chars].","An error has occurred while reading a certificate file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"UPDATE","3","FILE_REN_FAIL","Unable to Rename file [chars] to [chars]: [chars].","The system is unable to rename a file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"UPDATE","3","FILE_WRITE_FAIL","Unable to write to <[chars]>: [chars].","The system is unable to write to a file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"UPDATE","3","FOTER_MISMACH","Error! Footer mismatch from header! ([address] != [address]). Failed to install downloaded s/w.","The footer and the header do not match. The system has failed to install the downloaded software.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"UPDATE","4","GET_PRIORITY_FAIL","Failed to get the priority of the process. Defaulting to 0.Process name: Execute Script","The system has failed to get the priority of the process. The system is defaulting to the 0.Process name: Execute Script.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"UPDATE","3","IMAGE_CORRUPT","Invalid data length [hex]. Image file is corrupted!.","The system has detected an invalid data length. The image file is corrupted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"UPDATE","3","INCMPLT_READ","Warning: Truncated read: Still [dec] bytes left to read.","A file read operation did not complete. The file may be corrupt.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"UPDATE","3","INCMPLT_WRITE","Warning: Truncated write. Error writing chunk size [dec], len left = [dec], total len = [dec].","The system has detected a truncated write. An error occurred while writing to the file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"UPDATE","3","INIT_TLV_FAIL","Error [dec] installing Temporal Logic Verifier (TLV). Failed to install downloaded s/w.","The system has detected an error while installing the Temporal Logic Verifier (TLV). The system has failed to install the downloaded software.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"UPDATE","4","INV_EXT","Warning: Unknown File Type, extension: [chars].","The system has detected an unknown file extension.","No action is required."
"UPDATE","3","INV_FILE_SIGN","Error! Invalid image signature!. Image may be corrupt.","The system has detected an invalid image signature. The image may be corrupt.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"UPDATE","3","INV_FOOTER_OFF","Footer offset ([dec]) past end of file ([dec] bytes). Sanity check failed on downloaded file.","The footer is offset past the end of the file. A sanity check failed on the downloaded file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"UPDATE","3","INV_SIGN","Invalid signature type: [hex]. Image file may be corrupted.","The system has detected an invalid signature type. The image file may be corrupted.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"UPDATE","3","INV_TLV","Unknown Temporal Logic Verifier (TLV) code [dec] - ignored.","The system has detected an unknown Temporal Logic Verifier (TLV) code and has ignored it.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"UPDATE","3","LICENSE_LOAD_FAIL","Failed to load license file [chars]. rc = [dec].","The system has failed to load the license file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"UPDATE","3","MEM_MAP_FAIL","Unable to map to a shared file.File name: [chars]. [chars].","The system is unable to map to a shared file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"UPDATE","3","RAMDISK_5MB_FAIL","Error while loading webauth bundle. Could not create ramdisk of 5 MB. File name: [chars]","An error has occurred while loading a webauth bundle. The system could not create a RAM disk of 5 MB.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"UPDATE","3","RATE_DISABLE_FAIL","Failed to disable rate limiter in the NPU","The system has failed to disable a rate limiter in the NPU.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"UPDATE","3","RATE_ENABLE_FAIL","Failed to enable rate limiter in the NPU","The system has failed to enable a rate limiter in the NPU.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"UPDATE","3","RULE_DEL_FAIL","Failed to delete tftp rule for pHost=[chars] pFilename=[chars] rc2 = [dec]","The system has failed to delete a TFTP rule.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"UPDATE","0","SEM_CREATE_FAIL","Couldn't create flash access semaphore. Internal system error.","The system could not create a flash access semaphore.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"UPDATE","3","SEM_GIVE_FAIL","Failed to unlock the Tftp task. Tftp sub-system malfunctioning.","The system has failed to unlock the TFTP task. The TFTP subsystem is malfunctioning.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"UPDATE","3","SEM_TAKE_FAIL","Failed to lock on the Tftp task. Tftp sub-system malfunctioning.","The system has failed to lock on the TFTP task. The TFTP subsystem is malfunctioning.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"UPDATE","4","SET_PRIORITY_FAIL","Failed to set process priority. Process name: Execute script.","The system has failed to set the process priority. The process name is Execute script.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"UPDATE","0","TASK_CREATE_FAIL","Failed to create a task. Task Name: XFER_BLINK","The system has failed to create a task. The task name is XFER_BLINK.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"UPDATE","3","UNTAR_CMD_FAIL","Error during untar of webauth bundle. Tar returned [dec].","An error has occurred during an untar of the webauth bundle.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"UPDATE","3","MEM_ALLOC_FAIL","Could not allocate memory for filename. Bytes required [dec].","The system could not allocate memory for the FTP filename.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"UPDATE","2","MOUNT_FAILED","[chars][dec].","The system is unable to mount or unmount the AP image directory (/mnt/images).","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"USMDB","3","MSGTAG001","usmDbAclSwapRuleIndex: The two indices, [dec], are the same.","The two indices are the same.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"USMDB","3","MSGTAG002","usmDbAclSwapRuleIndex: ACL [chars] or rule [dec] does not exist.","The ACL or rule does not exist.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"USMDB","3","MSGTAG003","usmDbAclSwapRuleIndex: ACL [chars] or rule [dec] does not exist.","The ACL or rule does not exist.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"USMDB","3","MSGTAG004","invalid arg(s) passed to usmDbCertsWebadminNameGet","Invalid arguments are passed to usmDbCertsWebadminNameGet.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"USMDB","3","MSGTAG005","invalid arg(s) passed to usmDbCertsWebauthNameGet","Invalid arguments are passed to usmDbCertsWebauthNameGet.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"USMDB","3","MSGTAG006","Cannot add Mobility Member, duplicate IP, Saved Member:[hex]:[hex]:[hex]:[hex]:[hex]:[hex] Member:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], IP: [dec].[dec].[dec].[dec]","The system cannot add Mobility Member, duplicate IP, Saved Member:[hex]:[hex]:[hex]:[hex]:[hex]:[hex] Member:[hex]:[hex]:[hex]:[hex]:[hex]:[hex], IP: [dec].[dec].[dec].[dec]","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"USMDB","6","MSGTAG007","Error on call to sysapiRegistryGet routine with keyUDI_PID.","An error has occurred on a call to the sysapiRegistryGet routine with keyUDI_PID.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"USMDB","6","MSGTAG008","Error on call to sysapiRegistryGet routine with keyUDI_VID.","An error has occurred on a call to the sysapiRegistryGet routine with keyUDI_VID.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"USMDB","3","MSGTAG009","Error on call to sysapiRegistryGet routine with keySLOT_DATA_STRUCT.","An error has occurred on a call to the sysapiRegistryGet routine with keySLOT_DATA_STRUCT.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"USMDB","3","MSGTAG010","Error on call to sysapiRegistryGet routine with keyPORT_DATA_STRUCT.","An error has occurred on a call to the sysapiRegistryGet routine with keyPORT_DATA_STRUCT.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"USMDB","3","MSGTAG011","Error on call to sysapiRegistryGet routine with keySLOT_DATA_STRUCT.","An error has occurred on a call to the sysapiRegistryGet routine with keySLOT_DATA_STRUCT.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"USMDB","3","MSGTAG012","Error on call to sysapiRegistryGet routine with keyPORT_DATA_STRUCT.","An error has occurred on a call to the sysapiRegistryGet routine with keyPORT_DATA_STRUCT.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"USMDB","3","MSGTAG013","Error on call to sysapiRegistryGet routine with keySLOT_DATA_STRUCT.","An error has occurred on a call to the sysapiRegistryGet routine with keySLOT_DATA_STRUCT.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"USMDB","3","MSGTAG014","Error on call to sysapiRegistryGet routine with keyPORT_DATA_STRUCT.","An error has occurred on a call to the sysapiRegistryGet routine with keyPORT_DATA_STRUCT.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"USMDB","3","MSGTAG015","Error on call to sysapiRegistryGet routine with keySLOT_DATA_STRUCT.","An error has occurred on a call to the sysapiRegistryGet routine with keySLOT_DATA_STRUCT.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"USMDB","3","MSGTAG016","Failed to open [chars]","The system has failed to open [chars].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"USMDB","3","MSGTAG017","Couldn't create flash write semaphore.","The system could not create a flash write semaphore.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"USMDB","6","MSGTAG018","Setting hardware time to [dec] [dec] [dec] [dec]:[dec]:[dec]","The system is setting the hardware time to [dec] [dec] [dec] [dec]:[dec]:[dec].","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"USMDB","3","MSGTAG019","unabled to work out gmtime.","The system is unable to work out gmtime.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"USMDB","4","MSGTAG020","usmDbTimeGet:Buffer supplied too small [dec]<27 bytes","Buffer provided is less than the required 27 bytes.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"USMDB","4","MSGTAG028","LAG in transition.switch reboot DUE..!!!","LAG is in transition. A switch reboot is due.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"USMDB","3","MSGTAG029","License operation failed with rc : [chars]..!!!","A license operation has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WCP","3","BUFF_ALLOC_FAILED","Out of System buffers.","The system is out of system buffers.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WCP","3","BUFF_INVALID","The message buffer received for processing is invalid.","The message buffer received for processing is invalid.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WCP","3","BUFF_LEN_LOW","The length of the buffer [dec] bytes,is not enough to hold the data of size [dec] bytes.","The length of the buffer is not enough to hold the data.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WCP","0","CREAT_MUTEX_FAILED","Failed to Create SNMP mutex for WCP task.","The system has failed to create an SNMP mutex for the WCP task.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WCP","0","CREAT_TASK_FAILED","Failed to Create WCP Task.","The system has failed to create the WCP task.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WCP","3","DISABLE_VAP_FAILED","Failed to disable the Wlans associated with the interface [chars].","The system has failed to disable the WLANs associated with the interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WCP","3","GET_ADMINSTATE_ERR","Failed to get the admin state for the interface [dec].","The system has failed to get the admin state for a specified interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WCP","3","GET_GATEWAY_FAILED","Failed to get the gateway for the interface [chars].","The system has failed to get the gateway for an interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WCP","3","GET_IPADDR_FAILED","Failed to get the IP address for the interface [chars].","The system has failed to get the IP address for an interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WCP","3","GET_MASK_FAILED","Failed to get the net mask for the interface [chars].","The system has failed to get the netmask for an interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WCP","3","GET_VLAN_FAILED","Failed to get the vlan id for the interface [chars].","The system has failed to get the VLAN ID for an interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WCP","3","INTERNAL_INTF_NUM_ERR","Failed to get the first available internal interface number.","The system has failed to get the first available internal interface number.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WCP","3","INVALID_REQ_TYPE","Controller got request for invalid TLV type [chars].","The controller received a request for an invalid TLV type.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WCP","3","INVALID_SLOT_PORT","The next valid slot and port cannot be retrieved for the slot [dec] and port [dec]","The next valid slot and port cannot be retrieved.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WCP","3","IOCTL_FAILED","The ioctl system call failed for the option [chars].","The IOCTL system call has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WCP","3","KEEPALIVE_LOST","Lost keepalives from [chars].","The system has lost keepalives. The expected event on a socket did not occur.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WCP","3","MGMT_GATEWAY_ILLEGAL","Management interface gateway [chars] is illegal.","The management interface gateway is illegal.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WCP","3","MGMT_IP_ILLEGAL","Management interface IP address [chars] is illegal.","The management interface IP address is illegal.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WCP","3","MGMT_NETMASK_ILLEGAL","Management interface netmask [chars] is illegal.","The management interface netmask is illegal.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WCP","3","MSG_LEN_ZERO","The message received for processing has zero length.","The message received for processing has a zero length.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WCP","3","MSG_TYPE_UNKNOWN","Unknown message type [dec] received for processing.","An unknown message type has been received for processing by the WCP task.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WCP","3","PDU_TRANSMIT_FAILED","Failed to transmit the PDU for the command [chars].Return code:[dec].","The system has failed to transmit the WCP PDU to the SCP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WCP","3","SEM_TAKE_FAILED","Could not take a semaphore lock on the global snmp structure.","The system could not take a semaphore lock on the global SNMP structure.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WCP","3","SET_IPADDR_FAILED","Failed to set IP address for the interface [chars].","The system has failed to set the IP address for an interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WCP","3","SET_VLAN_FAILED","Failed to set vlan ID for the interface [chars].","The system has failed to set the VLAN ID for an interface.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WCP","3","SOCK_CREAT_FAILED","Failed to create a datagram socket.","The system has failed to create a datagram socket.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WCP","3","SOCK_OPT_FAILED","Failed to set the socket option [chars].","The system has failed to set the socket option.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WCP","3","SOCK_RECV_FAILED","Failed to receive a packet from ip address [chars]: port [dec].","The system has failed to receive a packet on a socket.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WCP","3","SOURCE_INVALID","The message buffer received for processing is from an invalid source.","The message buffer received for processing is from an invalid source.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WCP","7","WCP_PORT_BOUND","WCP task is bound to port number [dec].","The port number to which the WCP task is bound to is displayed.","No action is required."
"WCP","7","WCP_PROCESS_ERROR","wcp process error: The function [chars] failed.","A WCP process error has occurred.","No action is required."
"WEB","3","FORM_SUBMIT_FAILED","Form submission failed for file:[chars]. No action taken.","A form submit action has failed on the HTML file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WEB","3","INVALID_ACCESS_LEVEL","Access level is invalid for SNMPv3 user [chars].","The access level is invalid for this SNMPv3 user.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WEB","3","INVALID_AP_KEY","Invalid AP Hash Key Provided","The system has detected an invalid AP hash key.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WEB","3","INVALID_AUTH_PROTO","Invalid authentication protocol for SNMPv3 user [chars].","The authentication protocol is invalid for the SNMPv3 user.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WEB","3","INVALID_NLS_TOKEN","NLS String [[dec]] Not Found.","The NLS string has not been found.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WEB","3","INVALID_PRIV_PROTO","Unknown privacy protocol for SNMPv3 user [chars].","The system has detected an unknown privacy protocol for the SNMPv3 user.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WEB","3","INVALID_TFTP_DNLDCODE","TFTP download failed with unknown failure code.","A TFTP download has failed. The failure code is unknown.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WEB","3","INVALID_USERNAME","EwsContext cachedUsername is empty!","The cached username is empty.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WEB","3","LOCAL_AUTH_FAILED","# (prty_order_local_auth.html) Form Submission Failed. NoAction Taken..","Form submission has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WEB","3","NLS_LIST_NOT_FOUND","NLS List [[chars]] not found.","The NLS List has not been found.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WEB","3","NLS_STR_NOT_FOUND","NLS String [[dec]] Not Found for Key: [chars]","The NLS string has not been found.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WEB","3","PARTY_ORDER_NET_FAILED","# (prty_order_net.html) Form Submission Failed. No ActionTaken..","Form submission has failed.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WEB","3","USDB_SAVE_FAILED","The Local Users Database could not be saved to flash.","The local users database could not be saved to the flash.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WEB","3","USER_NOT_PRIVILEDGED","Form Submission Failed. The user doesn't have the right privileges.","Form submission has failed. The user does not have the correct privileges.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WPS","6","CONVERT_OLD_SIG_TO_NEW","Old version of signature configuration file detected.","An old version of the signature configuration file has been detected. Convert it to the new format.","This is a debug message only. No action is required."
"WPS","3","ERR_OPEN_SIG","Error opening new sig file","An error has occurred while opening a new signature file.","Make sure the signature file is downloaded properly."
"WPS","3","ERROR_MASK_NON_HEX","mask string [chars] has non-Hex digits","A mask string has the non-Hex digits.","Specify a mask string that has Hex digits."
"WPS","3","ERROR_PARSE_CST_SIG","Error parsing custom sig file.","An error has occurred while parsing the custom signature file.","Download a new custom signature file to the system."
"WPS","3","ERROR_PARSE_SIG_LINE","Error parsing at line [dec] of new sig file","An error has occurred while parsing at the line of a new signature file.","Ensure the signature line has the proper syntax."
"WPS","3","ERROR_PARSE_STD_SIG_FILE","Error parsing standard sig file.","An error has occurred while parsing a standard signature file.","Download a new standard signature file to the system."
"WPS","3","ERROR_PATTERN_NON_HEX","pattern string [chars] has non-Hex digits","A pattern string has the non-Hex digits.","Specify a pattern string with Hex digits."
"WPS","3","ERROR_RETRIEVE_FILE","Error reading file [chars] from flash","An error has occurred while retrieving a file from the flash.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WPS","3","ERROR_SEND_SIG_ADD","Error sending sig Add message to LWAPP","An error has occurred while sending a signature add message to the LWAPP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WPS","3","ERROR_SEND_SIG_DISABLE_MSG","Error sending sig disable message to LWAPP","An error has occurred while sending a signature disable message to the LWAPP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WPS","3","ERROR_SEND_SIG_ENABLE_MSG","Error sending sig enable message to LWAPP","An error has occurred while sending a signature enable message to the LWAPP.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WPS","3","ERR_PARSE_REV","Error parsing revision number","An error has occurred while parsing a signature revision number.","Make sure that the revision number is 1."
"WPS","3","ERR_RD_LN","Error reading line [dec] from new sig file","An error has occurred while reading a line from the new signature file.","Ensure the signature line has the proper syntax."
"WPS","3","ERR_READ_SIG_REV","Error reading sig revision number","An error has occurred while reading the signature revision number.","Specify the revision number at the first line of the signature file."
"WPS","3","FAIL_MERGE_SIG","unable to merge rev [chars] sig with existing sig","The system is unable to merge signatures with existing signatures.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WPS","3","FAIL_NOTIFY_LWAPP_SIG_FILE","Unable to notify LWAPP of new sig file","The system is unable to notify the LWAPP of a new signature file.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WPS","6","IDS_TOKEN_INTERVAL_DEF","Sig Interval set to default","The signature interval has been set to the default.","No action is required."
"WPS","3","INVALID_SIG_TOKEN","Invalid sig token [chars]","The system has detected an invalid signature token.","Correct the signature token that is invalid."
"WPS","3","INV_VER","Error invalid version [chars]","The error signature version is invalid.","Ensure that the revision number is 1."
"WPS","4","MFP_INVALID_EVENT_TYPE","MFP Ignoring invalid event type ([int]) from [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","MFP ignores the invalid event type.","This is a debug message only. No action is required."
"WPS","3","MFP_LINK_MISSING","MFP Missing link at the [chars] of table","MFP is missing a link in the table.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WPS","0","MFP_STAT_NO_QUEUE","MFP Stats task has no queue","The MFP statistics task has no queue.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WPS","3","MFP_UNLINK_ERR","MFP Can't unlink entry from table","MFP cannot unlink an entry from the table.","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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://tools.cisco.com/Support/BugToolKit/. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/launch.do, or contact your Cisco technical support representative and provide the representative with the information you have gathered."
"WPS","3","MISSING_SIG_TOKEN","Missing token, the symbol parsed=[chars]","A signature token is missing.","Correct the signature token that is missing."
"WPS","3","NO_SIG_REV","Sig file does not have revision number","The signature file does not have a revision number.","Specify the revision number at the first line of the signature file, which has to be a of value 1."
"WPS","3","NO_VALUE_SIG_TOKEN","No value specified for token [chars]","No value is specified for the signature token.","Specify the value for the token."
"WPS","3","READ_SIG_FILE_FAIL","Error reading line [dec] of new signature file","The system cannot read a new signature file.","Check the signature file on the line to ensure it has the proper syntax."
"WPS","4","SIG_ALARM_OFF","AP [hex]:[hex]:[hex]:[hex]:[hex]:[hex] : Alarm OFF, [chars] sig [chars], track=[chars] preced=[dec] hits=[dec] slot=[dec] channel=[dec]","The signature alarm is off.","This is a debug message only. No action is required."
"WPS","4","SIG_ALARM_OFF_CONT","...continue, source mac= [hex]:[hex]:[hex]:[hex]:[hex]:[hex]","...continue. The signature alarm is off.","This is a debug message only. No action is required."
"WPS","3","SIG_PTRN_DEL_NUM_INV","illegal number of pattern delimiters [chars].","The number of pattern delimiters is invalid.","The maximal delimiter number is 3."
"WPS","3","SIG_PTRN_INV","invalid pattern [chars] in Version 1 signature.","The signature pattern is invalid.","Correct the signature pattern."
"WPS","3","SIG_PTRN_INV_OFF","invalid offset [chars] in Version 1 signature","The signature pattern offset is invalid.","Specify the correct pattern offset."
"WPS","3","SIG_PTRN_INV_OFF_MAX","offset [chars] in Version 1 signature too big; max value = [dec]","The signature pattern offset value is invalid.","Specify the correct pattern offset value."
"WPS","3","SIG_PTRN_INV_OFF_STRT_D","invalid pattern offset Start value [dec] in Version 1 signature","The signature pattern offset start is invalid.","Specify the correct offset start value."
"WPS","3","SIG_PTRN_INV_OFF_STRT_S","invalid pattern offset Start value [chars] in Version 1 signature","The signature pattern offset start is invalid.","Specify the correct offset start value."
"WPS","3","SIG_PTRN_LEN_OVER","pattern string cannot specify more than [dec] octets in Version 1 signatures","The pattern string length is too big.","Specify the correct pattern string."
"WPS","3","SIG_PTRN_MASK_EQ","pattern string and mask must be of equal length in Version 1 signatures","The pattern string and mask must have an equal length.","Make sure that the pattern string and mask have an equal length."
"WPS","3","SIG_PTRN_MASK_EVEN","pattern string and mask must have an even number of bytes in Version 1 signatures","The pattern string and mask must have an even number of bytes.","Make sure that the pattern string and mask have an even number of bytes."
"WPS","3","SIG_PTRN_MASK_NULL","pattern string and mask have no any bytes specified","The pattern string and mask do not have any bytes specified.","Specify the pattern and mask."
"WPS","3","SIG_PTRN_MASK_STR_INV","[chars] string [chars] has non-Hex digits","The signature pattern or mask string is invalid. It has non-Hex digits.","Make sure that the signature pattern or mask string has Hex digits."
"WPS","3","SIG_PTRN_MISSING","invalid pattern [chars] in Version 1 signature: missing [chars].","The signature pattern is invalid.","Correct the signature pattern."
"WPS","3","SIG_PTRN_PARSE_FAIL","Error parsing pattern [chars] in Version 1 signature","An error has occurred while parsing the token pattern.","Specify the correct pattern."
"WPS","3","SIG_STR_INV","[chars] string must begin with '0x' in Version 1 signatures","The signature pattern is invalid.","Specify the correct signature pattern."
"WPS","3","SIG_TOKEN_DUP","Sig [chars] must be unique, the '[chars]' repeats","The signature token is not unique.","Specify a unique signature token."
"WPS","3","SIG_TOKEN_DUP_PRECED","Sig precedence must be unique, the [dec] repeats","The signature token precedence is not unique.","Specify a unique precedence ID."
"WPS","3","SIG_TOKEN_NUM_INV","Version 1 sig cannot have more than [dec] tokens per line","Version 1 signatures cannot have more than 15 tokens per line.","Specify a signature that has less than 15 tokens."
"WPS","3","SIG_TOKEN_WRONG_SIGID","Sig Id   [dec] is not valid","The signature token SigId is not valid.","Specify a valid signature ID."
"WPS","3","SIG_VER_UNSUP","Signature version number [chars] is unsupported","The signature version number is unsupported.","Make sure that the revision number is 1."
"WPS","3","TOKEN_MISSING_INVALID","Missing or invalid '[chars]' token in Version 1 sig","There is a missing or invalid token in the Version 1 signature.","Correct the invalid token."
"WPS","3","TOKEN_PARSE_FAIL","Error processing '[chars]' token in Version 1 signature","The signature token processing has failed.","Rectify the token."
"WPS","3","TYPE_TOKEN_INV_GT","In Version 1 signatures, '[chars]' can not have a value greater than [dec]","The signature token value is invalid.","Specify the correct value for the token."
"WPS","3","TYPE_TOKEN_INV_VAL1","In Version 1 signatures, '[chars]' can only have value [chars]","The signature token value is invalid.","Specify the correct value for the token."
"WPS","3","TYPE_TOKEN_INV_VAL2","In Version 1 signatures, '[chars]' can only have value [chars] or [chars]","The signature token value is invalid.","Specify the correct value for the token."
"WPS","3","TYPE_TOKEN_INV_VAL3","In Version 1 signatures, '[chars]' can only have value [chars], [chars], or [chars]","The signature token value is invalid.","Specify the correct value for the token."
"WPS","4","UNSUPPORT_SIG_VER","Unsupported sig version on line [dec], ignoring signature","There is an unsupported signature version. The system is ignoring the signature.","Make sure that the revision number is 1."
"WPS","3","VER_NOT_FOUND","Error version number not found","The signature version number has not been found.","Specify a revision number that has a value of 1."
"WPS","3","VER_NUM_MISSING_INVALID","Error at line [dec] of new signature file: version number is missing or invalid","The version number is missing or invalid.","Specify the revision number at the first line of the signature file, which has to be a value of 1."
"DSLSAR","1","DOWNGRADEDBW","PCR and SCR for VCD [dec] ([dec]/[dec]) has been reduced to [dec]k [dec]k due to insufficient upstream bandwidth","The DSL line has insufficient upstream bandwidth to support the guaranteed bandwidth that has been configured for the virtual circuits.","Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information."
"DSLSAR","1","DOWNGRADEDVC","Quality of Service (QoS) for VCD [dec] ([dec]/[dec]) has been downgraded to a UBR QoS due to insufficient upstream bandwidth","The DSL line may have trained at a lower than provisioned upstream speed.","Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information."
"PLATFORM_ENV","1","FRU_PS_SIGNAL_FAULTY","[chars] signal on power supply [dec] is faulty","The specified power supply signal is faulty. [chars] is the input or output signal value, and [dec] is the power supply number.","No action is required."
"PLATFORM_ENV","1","FRU_PS_SIGNAL_OK","[chars] signal on power supply [dec] is restored","The specified power supply signal is restored. [chars] is the input or output signal value, and [dec] is the power supply number.","Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still need assistance, open a case with the TAC, or provide your Cisco technical support representative with your information. For more information about these online tools and about contacting Cisco, see the 'Error Message Traceback Reports' section on page 1-5."
"SYS","2","MALLOCFAIL","Memory allocation of [int] bytes failed from [hex], alignment [dec] Pool: [chars] Free: [int] Cause: [chars] Alternate Pool: [chars] Free: [int] Cause: [chars] ","The requested memory allocation is not available from the specified memory pool. The current system configuration, network environment, or possibly a software error might have exhausted or fragmented the router's memory."," If you suspect a software error, 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. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit https://tools.cisco.com/bugsearch/?referring_site=emd. If you still require assistance, open a case with the Technical Assistance Center via the Internet https://tools.cisco.com/ServiceRequestTool/scm/mgmt/case, or contact your Cisco technical support representative and provide the representative with the gathered information."
"ENVMON","3","FAN_FAILED","Fan [dec] not rotating","The fan is not rotating properly.","Ensure the fan power cable is properly attached to the mainboard fan power connector. If the problem persists, it indicates a chassis that requires replacement. Contact your Cisco technical support representative to replace the chassis."
"NHRP","3","PAKREPLY","Receive [chars] packet with error - [chars]([dec])","An NHS has rejected or failed to serve the NHRP client request packet.","Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information."
"SNMP","3","AUTHFAIL","Authentication failure for SNMP req from host [dec].[dec].[dec].[dec]","An SNMP request was sent by the host at the address [dec].[dec].[dec].[dec], but the request PDU was not properly authenticated.","Make sure that the community and user name that are used in the SNMP request from the remote host have been configured on the router."
"LINK","3","BADMACREG","Interface [chars], non-existent MACADDR registry for link [dec]","An attempt to map a network level address to a MAC level address has failed.","Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information."
"SYS","3","TIMERNEG","Cannot start timer ([hex]) with negative offset ([dec]).","An internal software error has occurred.","Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information."
"LINEPROTO","5","UPDOWN","Line protocol on Interface [chars], changed state to [chars]","The data link level line protocol has changed state.","No action is required."
"VNS_AGENT","3","CORE_DEFAULT_PROF_ID_ERR","VNMC resolves default-service-profile for port, name:[chars] profile-id:[dec]","VNMC resolves default-service-profile","No action is required."
"CRYPTO","3","IKE_PAK_IN_Q_TIME_LIMIT_EXCEED","Pak spent too much time in the IKE input queues","An incoming IKE packet has spent too much time in the IKE input queues. This condition can occur when the IKE subsystem is under a heavy load because a lot of peers are trying to set up SAs at the same time and IKE is not able to handle all the incoming packets in a timely manner.","Attempt to determine why so many peers are simultaneously trying to set up SAs at the same time and, if possible, try to avoid or minimize this type of network condition."
"ILPOWER","5","IEEE_DISCONNECT","Interface [chars]: PD removed.","The powered device is not connected to the switch, or the connected powered device is being powered by an external AC power source. The switch is no longer providing power to the port. [chars] is the interface.","No action is required."
"SYS","4","CONFIG_RESOLVE_FAILURE","System config parse from ([chars]) failed","The configuration file at the URL specified in the error message could not be read.","Enter the no service config command to disable the autoloading of configuration files or investigate why the TFTP load is failing."
"CRYPTO","6","IKMP_NOT_ENCRYPTED","IKE packet from [IP_address] was not encrypted and it should've been.","A portion of the IKE is unencrypted, and a portion is encrypted. This message should have been encrypted but was not.","Contact the remote peer."
"CRYPTO","4","PKT_REPLAY_ERR","[chars] connection id=[dec]","The replay processing has failed. The failed replay processing may be a temporary condition caused by the wait for new SAs to be established. In the inbound case, this error might also be caused by an actual replay attack. This activity can be considered a hostile event.","If the problem appears to be more than a transient one, contact the peer administrator."
"SEC","6","IPACCESSLOGDP","list [chars] [chars] [chars] [IP_address] [chars]-> [IP_address] ([dec]/[dec]), [dec] packet[chars]","A packet matching the log criteria for the given access list has been detected.","No action is required."
"CRYPTO","4","IKMP_NO_SA","IKE message from [IP_address] has no SA and is not an initialization offer","IKE maintains the current state for a communication in the form of security associations. No security association exists for the specified packet, and it is not an initial offer from the peer to establish one. This situation could indicate a denial-of-service attack.","Contact the remote peer and the administrator of the remote peer."
"SEC","6","IPACCESSLOGP","list [chars] [chars] [chars] [IP_address]([dec]) [chars]-> [IP_address]([dec]), [dec] packet[chars]","A packet matching the log criteria for the given access list has been detected.","No action is required."
"CRYPTO","5","SESSION_STATUS","Peer [IP_address]:[dec] [chars] [chars] [chars] [chars] [chars] [chars] [chars] [chars]","This is a notification message for IPsec tunnel status.","No action is required."
"DHCP","6","ADDRESS_ASSIGN","Interface [chars] assigned DHCP address [IP_address], mask [IP_address], hostname [chars]","The interface has been allocated an address via DHCP.","This is an informational message. No action is required."
"LINK","5","CHANGED","Interface [chars], changed state to [chars]","The interface hardware has changed state.","Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information."
"SSH","5","ENABLED","SSH [dec].[dec] has been enabled","The SSH protocol has been enabled for connections.","This is an informational message only. No action is necessary."
"SSH","5","DISABLED","SSH [dec].[dec] has been disabled","The SSH protocol has been disabled for connections.","This is an informational message only. No action is necessary."
"SYS","5","CONFIG_I","Configured from [chars] by [chars]","The router configuration has been changed.","This is a notification message only. No action is required."
"SYS","5","RESTART","System restarted -- [chars]","A request to reload or restart the system has been made.","This is an informational message only. No action is required."
"IOS_LICENSE_IMAGE_APPLICATION","6","LICENSE_LEVEL","Module name = [chars] Next reboot level = [chars] and License = [chars]","This is an informational message to display the change in the next reboot license level.","No action is required."
"PLATFORM_ENV","6","FRU_PS_OIR","FRU Power Supply [dec] [chars].","A power supply wa inserted or removed. [dec] is the power supply. [chars] is the power supply status that can be either inserted, removed, powered on, or powered off.","No action is required."
"SYS","6","LOGGINGHOST_STARTSTOP","Logging to host [IP_address] [chars] [chars]","Syslog logging to the specified server or host has started or stopped.","No action is required."
"VIM","5","IF_ATTACHED","Interface [chars] is attached to Network Adapter [chars] [[chars]] of [[chars]] bound to [chars] on dvport id [dec] VIF-[dec] and vntag [dec] in [chars] mode","Interface has been attached","No action is required."
"VIM","5","IF_DETACHED","Interface [chars] is detached","Interface has been detached","No action is required."
"DUAL","3","SIA","Route [chars] stuck-in-active state in [chars] [dec]. Cleaning up","A hardware or software error has occurred.","Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information."
"SYS","6","CLOCKUPDATE","System clock has been updated from [chars] to [chars], configured from [chars] by [chars].","The system clock has been modified.","This is an informational message only. No action is required."
"SSH","3","KEYPAIR","Attempt to generate server keys failed - error code: [chars]","A server RSA keypair could not be generated.","If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information."
"SNMP","5","COLDSTART","SNMP agent on host [chars] is undergoing a cold start","The SNMP server has undergone a cold start.","This is a notification message only. No action is required."
"SISF","4","IP_THEFT","IP Theft [chars]","A duplicate IP address has been detected (IP theft) and blocked This can be due to a configuration error on end-device, an intentional IP theft or an IP movind too quickly","If the existing entry is REACHABLE in the binding table, and it moved to a new port consider reducing the REACHABLE timer otherwise it is either an attack or a configuration issue that must be resolved"
"SISF","4","MAC_THEFT","MAC Theft [chars]","A duplicate MAC address has been detected (MAC theft) and blocked This can be due to a configuration error on end-device, an intentional MAC theft or MAC moving too quickly","If the existing entry is REACHABLE in the binding table, and it moved to a new port consider reducing the REACHABLE timer otherwise it is either an attack or a configuration issue that must be resolved"
"SISF","4","MAC_AND_IP_THEFT","MAC_AND_IP Theft [chars]","A duplicate MAC and IP address has been detected (MAC_AND_IP theft) and blocked This can be due to a configuration error on end-device, an intentional MAC_AND_IP theft or MAC moving too quickly","If the existing entry is REACHABLE in the binding table, and it moved to a new port consider reducing the REACHABLE timer otherwise it is either an attack or a configuration issue that must be resolved"
"SISF","4","PAK_DROP","Message dropped [chars]","A message was dropped because one of the IPv6 first-hop security features said so","Look at the reason. It can either be a valid drop and the could go up to disconnect the host attached to the interface, or the policy configured on this interface is too severed and should be amended"